You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at the spec as it stands now, I'm turning over the semantics of the DataProduct class over in my head. I always approached a data product as a dcat:Dataset. Defining it as a separate object is interesting. I'm not sure i'm convinced yet (but I am open to being convinced). Particularly, the inputDataset and outputDataset relationships are very reminiscent of prov:used and (the inverse of) prov:wasGeneratedBy which makes it sound like DataProduct is (roughly) equivalent to a prov:Activity. I would expect a (data) product to be the result of an activity, not the activity itself.
Looking at the ttl file, I find that it is in fact a subclass of dcat:Resource (which makes sense to me, it would be good to clarify this in the documentation as well). But if this is so, I would have expected either:
inputDataset and outputDataset to be modelled using prov semantics (either just as prov:wasDerivedFrom/prov/used or as a subProperty of it).
or, if the semantics is distinct from prov, that the nuance is clarified at the very least in the documentation, but ideally also through machine readable relationships (something like owl:differentFrom).
The text was updated successfully, but these errors were encountered:
clarify in the documentation that a data product is a subclass of dcat:Resource (it is in the ttl but not in the documentation)
clarify the meaning of outputDataset by either describing how it relates to prov or (upon giving it some more thought) p-plan. it seems p-plans p-plan:hasOutputVar (https://www.opmw.org/model/p-plan/#hasOutputVar) might be appropriate
All of those alignments have implications for the (exact) interpretation of what a dprod:DataProduct is, so making explicit if there is there is an alingment or of not ' why not' clarifies its meaning a lot
Looking at the spec as it stands now, I'm turning over the semantics of the DataProduct class over in my head. I always approached a data product as a dcat:Dataset. Defining it as a separate object is interesting. I'm not sure i'm convinced yet (but I am open to being convinced). Particularly, the inputDataset and outputDataset relationships are very reminiscent of prov:used and (the inverse of) prov:wasGeneratedBy which makes it sound like DataProduct is (roughly) equivalent to a prov:Activity. I would expect a (data) product to be the result of an activity, not the activity itself.
Looking at the ttl file, I find that it is in fact a subclass of dcat:Resource (which makes sense to me, it would be good to clarify this in the documentation as well). But if this is so, I would have expected either:
The text was updated successfully, but these errors were encountered: