Graph people talk turtle but most people prefer json that is why we left the examples as is.
DQV for computedOn, measurementOf etc. is an external open standard so the examples show how DQV can be used to describe quality on the data product. Similar with odrl. We are not including these standards in DPROD but we are showing how all these standards work together
Blank nodes are not my favorite as well and I always avoid them in implementation but for readability purposes we followed them in the examples
I agree to 1. but suggest to simply add both as - I guess - you are trying to cater graph and non-graph people
reg. 2. I suggest to showcase an example integration with a real target ontology then; instead of making up non-existing concepts in defined namespaces
cf. https://github.com/rpietzsch/data-product/pull/1/files
I tried to make sense of the examples and encountered some issues:
ttl
for human use (if for technical purposejson
is needed it is only one rapper / riot / jena call away)ttl
json
distribution of the examples I suggest to makettl
the authoritative format and generate the json on every pushdprod:
although they do not seam to exist there yet either:rdf:computedOn
rdf:isMeasurementOf
rdf:Metric
rdf:title
tordfs:label
(maybedct:title
is what you intended, but inconsistent with the other examples)