Hans, hasObject is better, but not perfect. Ur-class is an object of all OIMs. Subclasses we discuss are included in OIMs (EnumeratedSets) in various combinations, it is possible to imagine OIM1 consisting of Class1, Class2, Class3, and OIM2 consisting of Class1, Class3 and Class4. Are you ready to ...

I'll vote for the use of the 1st namespace, http://rds.posccaesar.org/2008/02/OWL/ISO-15926-2_2003# However I don't like the distinction between "entity data types as ISO 15926 classes in the Core RDL" and "classes in the part 2 data model". I think that two SameAs relationships have to be added to ...

For a template DefiningAClassVariant role name hasOIMPosessor is not a good one. This class is not a "posessor" of OIM, rather an opposite is true. I'll propose the simple name hasSubclass. Also a template SpecializationFromUrClass is required, with two roles hasUrClass and hasSubclass. It'll be nic...

http://15926.org/templatespecs/CL-DEFN-01.xml The intent is to make a definition with a subtype of class of EXPRESS information representation. The role valDefinition is restricted by dm:ClassOfExpressInformationRepresentation. However it seems that the only real subtype that can be used for definit...

I see one important problem of cardinality-type roles in template signatures. If we leave role types as dm:Cardinality, it'll be required to learn by heart (or hardcode in the software) the URIs of the most used ones. Is it worth the efforts to decompose templates to the level of hasmaximum and hasm...

One question about generic class model example (2nd picture). There is a greyed out sample template SpecializationByCompoundType in the lower right corner. Its hasUrClass role goes to the 'handle' OIM class. It is a mistake? Shouldn't it go to the proper UR-Class of T-101? The 'handle' OIM class is ...

Hans,

Template statements are as eternal as all other items in 15926 world. You can deprecate an identified relationship if available, or you can deprecate template instance, but the only ontologically true solution is an ur-class. Which has the problem you just described.

Hans,

I had made too broad statement about universal restrictions, shame on me. The problem is indeed solved much simpler by skolemized entity, the only problem I see is its presence in the template signature.

Hans, I'm supporting your suggestion on ur-class. But we are discussing here the question of an explicit role for a ClassOfIndirectProperty in a template signature. We've "P-101 ur-class". We've its two specializations: "P-101 class created 01.01.2012" and "P-101 class created 02.01.2012". We've two...

No, the need for a hasDefined role is not yet clear for me. All the temporal issues (arising from the need to enhance the model during the design time) can be resolved through ur-class specialization indeed. However the relationship (CoR) which signifies the kind of indirect property in question doe...