Re: [dxwg] dcat:landingPage - check constraints

In Geoplatform profile, we introduced a superclass of dcat:Dataset called Asset. We use the property landing page to indicate that there is a web page that represents the asset.  In the case of a Map or Layer (subclasses of Asset), the landing page typically corresponds to a map viewer with the map or a layer (ex: https://geoplatform.maps.arcgis.com/home/webmap/viewer.html?webmap=b2c3ef22c8c14c2da57b243f2d04bd86), or a page describing the metadata about the artifact. 
I think dcat:landingPage provides a more precise semantic than foaf:page. It is very close to foaf:homepage (we may want to introduce owl:equivalentProperty or skos:closeMatch/exactMatch axiom)

Thus here are my recommendations:

1) Remove the domain dcat:Dataset from dcat:landingPage
2) Keep the range to foaf:Document
3) fixed the subproperty to foaf:page instead of foaf:Page. 


-- 
GitHub Notification of comment by fellahst
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/122#issuecomment-374003819 using your GitHub account

Received on Sunday, 18 March 2018 14:31:43 UTC