Hi Victor, You are right about the typed node elements, you are applying an abbreviation for describing the typed nodes, but in this case we do not use the rdf:type property. (http://www.w3.org/TR/rdf-primer/) We can not use OWL reasoner/verifier software now. However, we aim to achieve this strateg...

Hi Victor, I saw your sample of template definition and template instance. I have some comments: At the Classification template, we have this code: <p7tm:TemplateDescription rdf:about="#Classification__desc"> <rdf:type rdf:resource="&owl;Thing" /> <p7tm:valNumberOfRoles rdf:datatype="&xsd;integer">2...

Vote Option: No
Justification: It can be argued that namespaces should ultimately focus on human readability. If this implies long strings, as we see is a possibility in our dilema, I believe we could optimize transport and storage of URI's at software level.

Vote Option: No
Justification: I think that short namespaces just with the main information are enough, and we can garantee the
compatibility with the existing namespaces by software.

Vote Option: dm: only one namespace for entities, a separate dm: Justification: At my point of view, we need a separate dm: that will be namespaces of the entities, because: 1- The nature of the elements of dm: are different from the rdl: 2 - If we merge dm: and rdl: new users of the standard may lo...

Dear MMT member, To contemplate the presented model, as Victor Agroskin told(Message May 16) the template for the class CompositionOfOIM will have a template statement as a role in a template and It is not complience with part 7. I was thinking that the Templates Statements would be conected by Clas...