- From: Stephen Richard via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Jul 2019 21:08:20 +0000
- To: public-dxwg-wg@w3.org
I did indeed. foaf:Document is the Range for dcat:landingPage and for foaf:homePage, which is a property of dcat:Catalog. In practice (the dcat examples and foaf spec examples), properties that have Range foaf:Document get populated with http URI references that are urls to get the document, which might be a web page, or some other file that gets returned to the requesting client. Instantiating the class in an instance document allows inclusion of some metadata about the document, dct metadata properties in the dcat examples. The foaf:Document instances in the examples are the target of a dct:relation, which has no range specified. foaf:Document as the Range for dcat:landingPage seems to work well enough. I suppose if accessURL were reanamed 'accessPage', foaf:Document would be a more precise range, but not a big enough difference to change things at this point IMO. -- GitHub Notification of comment by smrgeoinfo Please view or discuss this issue at https://github.com/w3c/dxwg/issues/972#issuecomment-508255540 using your GitHub account
Received on Wednesday, 3 July 2019 21:08:21 UTC