config.ttl file syntax problem

[mpagni12]

Current Behavior

This is a config.ttl file produced by the rdf4j-workbench (details about the repo don't matter):

@prefix config: <tag:rdf4j.org,2023:config/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<#TEST> a config:Repository;
  rdfs:label "TEST";
  config:rep.id "TEST";
  config:rep.impl [
      config:rep.type "openrdf:SailRepository";
      config:sail.impl [
          config:mem.persist true;
          config:sail.defaultQueryEvaluationMode "STRICT";
          config:sail.iterationCacheSyncThreshold "10000"^^xsd:long;
          config:sail.type "openrdf:MemoryStore"
        ]
    ] .

This config file cannot be used to create a new repo with the command

curl -H 'content-type: text/turtle' --upload-file config.ttl http://localhost:8080/rdf4j-server/repositories/TEST"

which yields the following error message

org.eclipse.rdf4j.rio.RDFParseException: Not a valid (absolute) IRI: #TEST

Expected Behavior

[] a config:Repository;

fixes the problem

Steps To Reproduce

see above

Version

eclipse/rdf4j-workbench 5.0.3

Are you interested in contributing a solution yourself?

Perhaps?

Anything else?

thank you for doing eclipse/rdf4j-workbench

[hmottestad]

I assume that this here is the offending code:

RepositoryConfigRepository

			private Resource getContext(String repositoryID) {
				String location;
				try {
					location = manager.getLocation().toURI().toString();
				} catch (MalformedURLException | URISyntaxException e) {
					assert false;
					location = "urn:" + repositoryID;
				}
				String url = Protocol.getRepositoryLocation(location, repositoryID);
				return getValueFactory().createIRI(url + "#" + repositoryID);
			}

Maybe there should be a check that the second url there is actually a valid URI, or maybe we can just check if it's empty. In which case maybe we can use urn:, since it's a bit easier to deal with everything when we don't have to worry about blank nodes.

A general issue though is that this method is used both for creating the Resource for the first time and also for creating the same Resource later on to retrieve the correct repo from the config file.

[mpagni12]

A general issue though is that this method is used both for creating the Resource for the first time and also for creating the same Resource later on to retrieve the correct repo from the config file.

Yes this is super useful to have such config file.

I understand the many difficulties with blank node, but for a config file I would say it is acceptable.

[hmottestad]

I don't think a blank node would work. But it doesn't have to be a relative URL either like it seems to be at the moment.