Re: [dxwg] Use PROV-O to satisfy provenance requirements

Just to note, if we want use DQV, and it imports QB, this makes it easy for us to use QB to define finer grained semantics (not that there is much better choice).  It has pretty much everything we need IMHO - the ability to define subsets, bind schemas to vocabularies.  What it is missing is a canonical way to bind a rdf property name to a structural element in non RDF encodings - or to put it the other way, we need to be able to describe data set structures independently of the encoding of distributions and create resource identifiers for structural elements.  What is a candidate vocabulary for this. 

The issues I have found looking at profiles in the context of QB is one needs to define an entailment regime for inheritance/dependency in the constraint model - much the same way SKOS defines how skos:broader and skos:broaderTransitive relate.   This is pretty much exactly the same problem we have for profiles in general, and profile description languages will need to follow.  Using QB would make profile description relatively simple - so if it can get elevated to at least documented BP guidance thats great, and making sure dcat allow this, and does not overspecify half-solutions is the key.

-- 
GitHub Notification of comment by rob-metalinkage
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/128#issuecomment-366106999 using your GitHub account

Received on Friday, 16 February 2018 00:20:31 UTC