Re: Best practices for versioning and documenting ontologies for Sem Web

Am 30.01.2017 um 00:19 schrieb Munson J.E.:
> Dear team
>
> My name is Jo Munson and I am currently a PhD candidate at the University of Southampton.
> We are currently working with an external organisation looking to put a 'real life' ontology together and am writing to ask whether there are any tools / best practices for
> versioning and documenting from your perspective (for commercial/public use, not just in a research context).
>
> Many thanks for your time
>
> Jo
>
> Web Science PhD Candidate
> University of Southampton
>
Dear Jo,

we also have a tool to throw into the ring, which is called Quit (Quads 
in Git). It basically provides a SPARQL-Endpoint (Query and Update) 
which is running on top of a Git repository. All changes are 
automatically tracked in the Git repository, which can then be pushed 
and pulled between collaborating parties.

The SPARQL interface is provided by: https://github.com/AKSW/QuitStore
With QuitDiff you can also compare arbitrary versions: 
https://github.com/AKSW/QuitDiff
QuitMerge is used to merge diverged branches: 
https://github.com/AKSW/QuitMerge (Currently the Three-Way-Merge)

For reading we also have:
- https://svn.aksw.org/papers/2016/Semantics_Quit/public.pdf
- https://svn.aksw.org/papers/2016/Semantics_Demo_QuitDiff/public.pdf

Kind regards,
Natanael


---

I want to invite you to the following Calls for Papers:

LEDSPLaY17 - Workshop on Linked Enterprise Data Services, Provenance, 
Linking and QualitY
https://informatik2017.de/ws29-ledsplay17/

FDM2017 - Digitale Prozesse und Informationssysteme im 
Forschungsdatenmanagement
https://informatik2017.de/ws-18-fdm2017/

Received on Monday, 13 February 2017 13:58:52 UTC