Re: [dxwg] dcat:landingPage - check constraints

Thanks @makxdekkers . 

Good - that helps. I don't actually have much investment in the outcome here, just aiming for clarity. 

On the first issue, perhaps the documentation of dcat:landingPage 
https://w3c.github.io/dxwg/dcat/#Property:dataset_landingpage could be improved to indicate that landing-page is usually a list of distributions or links to service-calls that provide distributions. 

I understand your backward compatibility concerns. At an earlier phase of the conversation you were keen to drop all domain constraints except the ones that were absolutely needed, but then I think you saw some risks. Fair enough. In the other W3C project I was involved in recently (SSN) the backward compatibility concerns were less because the prior version was not a W3C Recommendation, merely an incubator report, so no representations of stability had ever been made. DCAT is different. 

My general observation is that global domain constraints are unfortunately one of the most misunderstood and thus misused parts of RDF. Folk tend to think of them as just supporting data modelling, rather than asking the question "Is it OK that every time property-a is used in a dataset, the implication is that the subject is a member of class-C?" I'm more comfortable with global range constraints, since it is reasonable that the intention of a property definition is somehow tied up with the target object type. 

Thanks for pointing out the looser definition of the range of foaf:page - I hadn't processed that.

@andrea-perego I think your argument for loosening the domain of dcat:landingPage is so you could use it to point to records of services as well as datasets. That usage is parallel to the dcat:dataset link from a Catalog to a Dataset? Wouldn't it be better to officially accommodate services in the catalog? e.g. like this https://github.com/w3c/dxwg/wiki/Data-service Otherwise it feels a bit coy, sneaking in service-cataloging through 'creative' use of some existing classes and properties, rather than recognising that this is a real requirement (with two Use Cases behind it). 


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

Received on Sunday, 18 March 2018 23:37:10 UTC