CR13 Asset. Modify range of the property dcat:landingPage


The current range of the property dcat:landingPage associated to the class adms:Asset is foaf:Document. However, this obliges metadata publisher to describe a foaf:Document to reference a simple URL. This is very cumbersome. The usage note states though the value expected is a web page.






Tue, 05/01/2016 - 14:13

Proposed resolution: Changing the range of dcat:landingPage would be a violation of DCAT. The fact that the range of this property is a foaf:Document does not imply that the data needs to contain more than a URI as providing dct:title for the class Documentation is not mandatory.

Wed, 06/01/2016 - 17:05

But still, it means that for every URL you want to provide, you need to create another foaf:Document, even if you don’t put any title. I understand the violation limitation, of course.


But for my personal understanding, I would be grateful if you could explain to me why the range of dcat:landingPage has been decided to be foaf:Document (well I guess dcat:landingPage is a subproperty of foaf:page but still). It is a simple URL, right? So why not having simply put rdfs:label or something closer to the URL format?

Sun, 10/01/2016 - 11:34

Thibaut, the assertion that the range of dcat:landingPage is foaf:Document does not say that whatever is on the right side of that statement must be a foaf:Document. Inference rules say that whatever is given as the object of the triple is by definition a foaf:Document.

In fact, the definion just says that you shouldn't try to stick in the URI for something that is not a document on the Web.

Wed, 20/01/2016 - 09:41

Hi Makx,


Thanks a lot for the explanation. It makes sense to me now. In that case I guess we could close this issue.

Sun, 07/02/2016 - 12:09

Issue closed. Won't fix.

Mon, 08/02/2016 - 08:52

Login or create an account to comment.