By "dm: namespace for JORD" I just mean that in JORD triples 201 types are identified in http://rds.posccaesar.org/2008/02/OWL/ISO-15926-2_2003#
But I'm not thinking in terms of RDL's here. Here I'm thinking more in terms of Semantic Web (probable unexpected from me )
There are resources representing 201 EXPRESS types. Each may have many URIs, but only two should be used in my opinion (in http://rds.posccaesar.org/2008/02/OWL/ISO-15926-2_2003# and http://standards.iso.org/iso/ts/15926/- ... data-model# namespaces). In the context of JORD or any other library or data source these resources are referenced as objects in rdf:type predicates.
There is no need for them to "be" anywhere in RDL or on endpoint. They are prebuilt in our .15926 Editor, for example.
There can be many places where some useful facts are recorded for these resources, here are some of these places:
http://rds.posccaesar.org/2008/07/OWL/I ... nnotations
http://rds.posccaesar.org/2008/07/OWL/I ... Membership
http://rds.posccaesar.org/2008/07/OWL/I ... Candidates
You can import this fact sets in other ontologies, and there is no way to import an endpoint anywhere, as far as I know.
Projects like OWL 2 can bring us more useful facts, representing more subtle meanings of Part 2 English text (for example).
This is an approach, as far as I understand, proclaimed also for template model and proto and initial template set in Part 8:
In what senseThe dm, p7tm, p7tpl and meta are files and not SPARQL endpoints. This is because given that these declarations
are immutable, it can be assumed these files will be locally cached by implementing systems. These files are present on the
CD-ROM of this part of ISO 15926.