It opens now, but there is still something wrong (but I do not know what).

Protege superclasses some of the templates with ErrorX where X is a number. Don't know what is wrong now, but it was the same error I saw earlier.

Sorry, still doesn't work. Protege error: org.semanticweb.owlapi.rdf.syntax.RDFParserException: [line=1794:column=59] IRI '#http://www.w3.org/2002/07/owl#annotatedSource' cannot be resolved against curent base IRI http://15926.org/templates-test/templates Line 1794: <p7tm:hasRole rdf:resource=" # &o...

Thanks.

My "huh" was a: I don't understand what you are talking about. Anyhow. I found the problem with the OWL file. Edit: Seems to just be one problem. The classes that Protege are showing as "error xx" have the wrong namespace in the OWL file. Example of this is: <owl:onProperty rdf:resource=" owl: annot...

That is not a very nice way to put it.

huh?

I have written sparql queries for these coloumns: Unique name Text definition Notes superclass 1 superclass 2 superclass 3 ISO 15926-2 entity classification 1 classification 2 classification 3 I always presume that the unique name can be found in the RDL by using "hasDesignation" [1]. Then I show an...

I have taken the time to make the ISO 15926-4 spreadsheets referenced here[1] machine readable so that I could compare them to the contents of the RDL at the PCA endpoint. .xls files are not very friendly to read since they support far too many features and provide to much history in the files. The ...

That worked.

I am used to reading templates as manchester syntax in Protege, so it's not too bad.

There are still some errors though. They are generated by OWL API.

Hello I was looking at the Template Specifications List (http://15926.org/15926_template_specs.php) with Lillian and it was fairly heavy reading. So I thought I would look at the OWL file instead with Protege since that often makes the data a bit easier to read. Protege 4.3 gives a string out of ran...