Produce serializations from a script

[matt-wallis]

Currently, the definitions are contained in independent RDF/XML and Turtle serializations. Some reasons to prefer a script that generates these serializations:

• Ensure consistency between all serializations (and HTML docs too?). See #2.
• Parameterise the serializations (e.g. with URI bases and version numbers).
• Enforce standards (e.g. to ensure that all Classes, Properties, etc are defined to a consistent set of standards).
• Catch errors in the definition.
• The definition of the vocab can include elements that are purely for documentation purposes (perhaps these gat added to HTML docs that are also generated by the script), but are not intended to make their way into the RDF serializations.

The script should take as input a file which describes the vocab in an abstract way, independent of serialization. What format should this take? JSON, perhaps?

[marianamalta]

I am happy to @matt-wallis to go ahead as he sees fit.

[matt-wallis]

The script for producing serializations is being implemented as a Makefile. As well as the RDF serializations, the script also deals with the SKOS files. The following commits have contributed to this work:

• 084945048c5c55c06f851fd7894fe5d56c57ec2d "Now generates SKOS files as well as ones for the vocab."
• 9611d6ab8df8af48380c91ba8d50144d23a5afdf "Now generates a simple HTML table too."
• f70b39a8aebb9cd6a484f54b6d4ddbf4567fe057 "Makefile improvements, including help goal."
• 54749e8a04bd5952e0234e8e6e057f5b8e2884b6 "Initial version of Makefile to generate other serializations from turtle."