Re: [dxwg] Clarify scope of DCAT - Datasets, Distributions, Services?

1. OK - remove sub-class axiom from `dcat:Catalog`

2. That limitation was not the intention. I was just taking an incremental approach: right now we know about Data Services, so we add them; later we may know about other things, so we can add them then. 

A challenge in modeling is whether to be parsimonious - only model the things we know about now - else attempt to provide a generic home for things we haven't yet encountered, but have a hunch about. These days I tend to err towards the former, and take good care of what we do know about, and leave the unknowns for the future.  I lean towards having well-named predicates so went for `dcat-s:dataService` to link to a `dcat-s:DataService` by analogy with `dcat:dataset` that links to `dcat:Dataset`. It might be generalized a little, but then we end up at `dcat:WebService` ... which is already deprecated! (Can you un-deprecate something??)

3. OK - but again, I think I would add a specific (recursive) property for that. Specialized properties make for more compact queries and paths. 

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

Received on Monday, 26 March 2018 22:26:06 UTC