Ontology publishing pipeline

[dr-shorthair]

Publishing a new (version of an) RDF vocabulary or ontology includes a number of steps, the most important of which are

• putting the RDF source in the release location
• creating documentation (web-page) and putting that in the release location

Depending on the publication method, this might involve loading files in a web server, or merely merging them into the correct branch on GitHub ...

To resolve this we need to

1. determine the publication platform
2. configure the tools to push things there.

Note

1. https://raw.githack.com/ allows publication direct from GitHub with the proper headers, and @nicholascar has agreed that ontologies and vocabularies published by AGLDWG at http://catalogue.linked.data.gov.au/ontologies could be published this way.
2. pyLODE can write out .md representations, that are then easy to tweak (e.g. to insert figures), but best if it runs on the desktop (which isn't easy at present)

There will also be various other sub-tasks, such as

• verify that the ontology loads without unexpected errors in major platforms (TopBraid, Protege)
• serialize in canonical form (OWLAPI) so diffs are easy to read - post-commit hook?
• add a 'release' tag in Git
• generate key diagrams for the documentation
• generate HTML or .md documentation of ontology using (py)LODE

[jyucsiro]

@dr-shorthair try this pylode windows exe I created from the pyLODE repo...
pylode.zip

[jyucsiro]

@dr-shorthair try this one - now with md templates!

pylode.zip

[dr-shorthair]

Success! though slightly odd diagnostics

[dr-shorthair]

Completed attempts here:
https://github.com/AGLDWG/asgs-ont/blob/master/asgs.md
https://raw.githack.com/AGLDWG/asgs-ont/master/asgs.html