Comments (12)
Consider using PROV here
from robot.
When ontologies are merged, should be possible to see original IRIs (but in a less hacky way than OWLTools - OBOFoundry/OBOFoundry.github.io#424 )
We really need standard URIs for the properties, as well as for ontology IRIs. Coordinate with ontobee. E.g. things are merged into a named graph e.g..
http://purl.obolibrary.org/obo/cl.owl --> http://purl.obolibrary.org/obo/merged/CL
from robot.
This would be particularly useful for ontology annotations for import modules - need to at least know the versionIRI of the source ontology
from robot.
Assigning @rctauber. Order of operations is important, so we should probably use an RDF List, but I'm a little worried that will confuse tools.
from robot.
Not really in favor of RDF lists. Hard to work with in OWL for one thing. I think we should stick to standards, and PROV is a good standard here. Some thoughts:
https://docs.google.com/document/d/1dchZkhqOCBgZJJ0UVkWON9y9xibXVXkqJFc0ceidbOc/edit
Swe should probably only have minimal info in the header and a seeAlso triple or similar pointing to the PROV graph
from robot.
Ok, but do we only care about the last ROBOT operation, and not chains of operations?
from robot.
from robot.
That Google Doc isn't public.
I'm fine with PROV, I just haven't used it much yet.
I thought the goal was to keep this information in the OWL file. I'd prefer not to use an external file. Maybe we need to specify the use cases. If we don't need a lot of detail, that's fine, but if it's all being done automatically then more detail shouldn't hurt.
I still think it's important to maintain sequence. I'd be happy with a timestamp, so that consumers can sort the operations.
from robot.
In the OWL/ZIP issue @cmungall linked to this example of a JSON-LD PROV file: https://github.com/ResearchObject/bagit-ro/blob/master/example1/metadata/provenance/results.prov.jsonld
from robot.
doc public now
I think it's definitely generally very useful to have at least prov:wasDerivedFrom for import modules and the results of merges directly in the ontology.
I'm also OK including the full graph but this may be perceived as too much clutter/overhead for a level of detail rarely required. But don't have such strong opinions. In the past we avoided administrative instances in the ontology since it causes HermiT to trigger a slower inference algorithm but don't think that's an issue now.
from robot.
mail list convo: https://lists.w3.org/Archives/Public/semantic-web/2017Nov/0099.html
from robot.
OK I managed to make this ticket quite complicated...
I retitled it to reflect scope and split out a separate simpler ticket here: #655
from robot.
Related Issues (20)
- Export command does not export a column for "rdfs:isDefinedBy" HOT 1
- Integration test for extract subset failing in CI HOT 5
- `analyze`: Add command for measuring the impact/power of individual axioms.
- ROBOT query --update strips prefixes when output is not .owl (RDF/XML) HOT 3
- Ignoring duplicate exact synonyms that are acronyms in robot report HOT 8
- Should `validate-profile` recognize `owl:onProperties`? HOT 6
- Including object properties HOT 4
- Having robot capture kinds of dbxref annotation HOT 2
- relax is currently incomplete HOT 4
- Extract produces strangeness -> OBO Graph error HOT 6
- Alternative ways of removing imports HOT 4
- diff feature request: sort axioms in Added and Removed sections in Markdown output HOT 4
- Add `--allow-duplicate-entities` as option in ROBOT rename HOT 4
- robot remove --axioms external is removing an internal axiom HOT 4
- 'MISSING MIREOT TERMS ERROR' that can't be resolved HOT 3
- BUG: robot template with class expressions duplicates classes as datatypes HOT 12
- Implement a cycle check over relation graph HOT 1
- Unclear expressivity results from robot measure HOT 6
- reduce not removing axioms where one relationship is a subproperty of another between the same two classes
- How to trigger datatype property range review? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from robot.