...

Note that the default namespace declaration on line 2 technically make the elements Ontology (lines 6 and 7) and Class (lines 9 and 11) into the fully qualified IRIs http://www.w3.org/2002/07/owl#Ontology and http://www.w3.org/2002/07/owl#Class, respectively, however, the use of any other non-OWL, unqualified XML element would inadvertently put that element into the OWL namespace, which is a violation of best practices for data governance generally, and goes against practices outlined in various W3C Recommendations and other documents, including but not limited to Cool URIs for the Semantic Web .

In order to ensure that no every XML element is inadvertently put into the wrong correct namespace, every IOF ontology MUST NOT declare a default namespace (such as the one on line 2, above). Expressed another way, every occurrence of “xmlns” MUST be followed by a colon (“:”) and a namespace prefix (such as the ones on lines 3 and 4).

Ontology Namespace Prefix

Every ontology MUST define a short, unique, meaningful, ontology-namespace prefix, like the ones found on lines 2-4such as “iof-se” on line 3, above.

Tools

Every local git repository (i.e., the one on your computer) that pushes changes to the IOF GitHub repository MUST have the EDM Council RDF Toolkit installed, such that every time an RDF/XML file is committed, that file will be automatically rewritten to conform to the policies in this document. The instructions for installing that toolkit can be found at that link.

...