-
Notifications
You must be signed in to change notification settings - Fork 47
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
Incorrect type for *URL properties - should be owl:DatatypeProperty with range xsd:anyURI #249
Comments
Maybe also |
In #241 (comment) @andrea-perego wrote:
|
@andrea-perego wrote:
I guess the problem is that the existing implementation have
rather than
That is definitely an incompatibility.
True. I'm primarily seeking consistency with the definitions, but of course that cannot be at the expense of functionality. And even if we do find some errors and infelicities, some we just have to accept as history. Note that the documentation is ambiguous: in the RDF representation of DCAT-2014 in the definition of
I need to understand the details here. We have (provisionally) added a new property |
On the last point above, see #124 (comment)
|
I agree that the labels for the properties However, I agree with @andrea-perego that we shouldn't break current implementations. We could move outside of OWL DL and support properties with the two types, but I don't think we should do that and add more complexity. If the problem is the usage note, I suggest we change it to make clear that we expect the value to be an individual. To find examples, I've been exploring the European Data Portal SPARQL endpoint. As @dr-shorthair mentioned, the current use is e.g. : I could not find examples of 'cross-linking of related resources (as services and distributions)' (especially because the endpoint actually hangs with more complex queries). @andrea-perego maybe you can point us to examples of that? |
I'm OK to withdraw this issue, primarily because of the backward compatibility issue. This was a historical mistake that it is too late to fix. However,
|
Yes, I agree we should keep backward compatibility and with the two points you mentioned. I can send a PR to fix the usage notes. Also, the point that @andrea-perego made about cross-linking with other resources could justify these properties being |
Resolved - see https://www.w3.org/2018/06/14-dxwgdcat-minutes.html#x09 |
The properties
dcat:accessURL
,dcat:downloadURL
anddcat:landingPage
are currently specified asowl:ObjectProperty
even though the description makes it clear that only a URI value is expected. The correct way to handle that is for them to beowl:DatatypeProperty
with rangexsd:anyURI
.Leaving them as
owl:ObjectProperty
means that an embedded/blank node is allowed, which is not the intention.This pattern should also be used for the new property proposed for data services
dcat:endpointURL
(ordcat:endpointLocation
- see #241The text was updated successfully, but these errors were encountered: