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

Propose the Framework #10

Open
diegoesteves opened this issue Nov 2, 2015 · 1 comment
Open

Propose the Framework #10

diegoesteves opened this issue Nov 2, 2015 · 1 comment

Comments

@diegoesteves
Copy link

No description provided.

@mommi84
Copy link
Member

mommi84 commented Nov 9, 2015

As previously agreed, still giving priority to the discussion about the vocabulary terms, we should check whether our schema is consistent with respect to the most important upper-level ontologies. Here is a tentative of mapping to PROV-O.

mls:Task rdfs:subClassOf prov:Entity .
mls:Algorithm rdfs:subClassOf prov:Entity .
mls:Process rdfs:subClassOf prov:Activity .
mls:Implementation rdfs:subClassOf prov:Agent .

which leads to:

mls:Algorithm --prov:wasDerivedFrom-----> mls:Task
mls:Algorithm --prov:wasAttributedTo----> mls:Implementation
mls:Process ----prov:wasAssociatedWith--> mls:Implementation
mls:Process ----prov:used---------------> mls:Algorithm

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

No branches or pull requests

2 participants