- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Mar 2018 02:38:47 +0000
- To: public-dxwg-wg@w3.org
This is a fair bit more structure imposed on dcat usage, for more flexibility. It is not incompatible with also specialising dataAccessURL for these key cases. I think you would need to model the equivalence in a way they entail each other. the role can be best qualified by pointing to an actionable specification (i.e. a profile) rather than another external vocabulary, this way we get basic type information from the subclass and a more descriptive extension mechanism, and no need to maintain a separate classification vocabulary. People can subclass accessURL and force entailment to provide finer grained (e.g. SPARQL endpoint - which can be described by void:sparqlEndpoint) Maintaining an extensible vocabulary is problematic - some superclasses is relatively easy for a limited lifespan WG -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/124#issuecomment-369455305 using your GitHub account
Received on Thursday, 1 March 2018 02:38:52 UTC