Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A more explicit allignment between dprod and prov would be helpful to understand the meaning of DataProduct better #76

Open
joepvgenuchten opened this issue Sep 20, 2024 · 3 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@joepvgenuchten
Copy link

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).
@VladimirAlexiev
Copy link

@Sveino (electrical CIM/CGMES architect) said a similar thing

@rivettp
Copy link
Contributor

rivettp commented Sep 27, 2024

In other words we need to describe how inputDataSet relates to PROV.

@rivettp rivettp added the documentation Improvements or additions to documentation label Sep 27, 2024
@joepvgenuchten
Copy link
Author

joepvgenuchten commented Sep 27, 2024

That, and:

  • 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

4 participants