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

How to make git diffs and turtle files more readable #4

Open
jesper-friis opened this issue Apr 26, 2021 · 0 comments
Open

How to make git diffs and turtle files more readable #4

jesper-friis opened this issue Apr 26, 2021 · 0 comments
Labels
question Further information is requested

Comments

@jesper-friis
Copy link
Contributor

Due to the EMMO convention to name all concepts in the ontology with unique UUIDs instead of readable names, the source file become very difficult to read. That leads to unreadable diffs, making the review process very hard. It also makes writing SPARQL queries very difficult.

My advise is to drop the UUIDs and name the concepts after their prefLabel.

This is an ongoing discussion in the EMMO group. There will probably not be any changes in the near future.

We could decide to drop the UUIDs in the microstructure domain ontology. But that would not solve the problem, since all references (including relations) to EMMO top and middle would still be unreadable UUIDs.

Other alternatives:

Write the ontology in Python

  • Pros:
    • git friendly
    • easy to read source
  • Cons:
    • all changes to the ontology must be done in Python, creating an additional barrier for non-Python users to develop the ontology
    • the ontology cannot be distributed as-is on github, but has to be "compiled" into turtle for distribution (e.g. on GitHub Pages)

Add a pre-commit / post-pull hooks that always saves/reads the ontology to/from standard format

  • Pros:
    • possible to replace all UUIDs with readable names in the checked-out sources, given that we also checks out EMMO
    • possible to always store in a standard format avoiding false differences (makes the review process much easier)
  • Cons
    • does not solve unreadable diffs
    • complicated, may be error prone
    • an extra barrier to learn for contributors

Remarks

I don't think that the two alternatives mentioned above are worth the effort. It would be much easier and more explicit to simply replace the UUIDs with prefLabels. Note that this will not solve the issue of false diffs due to Protege serialising the ontology slightly different depending on OWLAPI version and how you save. But it will make the diffs much easier to read. It can further be minimised by standardising on OWLAPI version and how to save the ontology.

@jesper-friis jesper-friis added the question Further information is requested label Apr 26, 2021
@jesper-friis jesper-friis changed the title Unreadable diffs and turtle files How to make git diffs and turtle files more readable Apr 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant