Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

range of idx:hasTarget and idx:hasSubIndex are wrong #42

Closed
pchampin opened this issue Jun 28, 2024 · 4 comments
Closed

range of idx:hasTarget and idx:hasSubIndex are wrong #42

pchampin opened this issue Jun 28, 2024 · 4 comments

Comments

@pchampin
Copy link
Collaborator

the current ontology says:

idx:hasTarget   rdfs:hasRange xsd:anyUri .
idx:hasSubIndex rdfs:hasRange xsd:anyUri .

This is incorrect. It means that the values of these properties should be literals with the datatype »sd:anyUri. And semantically, it would mean that the target / subindex is the URI itself, rather than the resource identified by that URI.

@pchampin
Copy link
Collaborator Author

The correct range for idx:hasSubIndex should obviously be idx:Index.

@pchampin
Copy link
Collaborator Author

For the range of idx:hasTarget, I see several options:

  • we set it to ldp:RdfSource, because the intent is to point to RDF documents, but it then restricts our vocabulary to LDP- or Solid-managed resources, which seems overly constrained;
  • we leave it unspecified, or set it to rdfs:Resource (which amounts to the same), but then it is overly unconstrained;
  • we mint our own IRI for "any HTTP(s) resource that deferences to some RDF syntax" (I didn't find any matching term on LOV)

My preference would be to go for option two (unspecified) for the moment, and in parallel we create an erratum for the RDF WG, suggesting that the rdf: namespace should contain an IRI for the concept of RDF Source, and we eventually use this one.

lecoqlibre added a commit that referenced this issue Jun 28, 2024
@lecoqlibre
Copy link
Collaborator

Done both. Used option 2 regarding idx:hasTarget. Waiting for the erratum.

@pchampin
Copy link
Collaborator Author

Waiting for the erratum.

In fact I raised an issue instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants