Issue 10694: Clarify usage of Fully qualified names in the model tags in section 3.2.2.3 (data-distribution-rtf) Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com) Nature: Clarification Severity: Summary: Problem: The XML as described in section 3.2.2.3 and sub section has a problem in relation to IDL modules. How to represent to valuetypes named Foo which are defined in different modules for example? It is currently not clear how this should be done. It is our suggestion to clarify that fully qualified names should be used in IDL sense. Where a valuetype Foo in module Test would be referred to as "Test::Foo". The subsections of section 3.2.2.3 should state for each element attribute if fully qualified names must be used. Solution: In section 3.2.2.3 replace: Model tags are specified by means of XML declarations that must be compliant with the DTD listed in the following section; subsequent sections give details on the constructs. With: Model tags are specified by means of XML declarations that must be compliant with the DTD listed in the following section; subsequent sections give details on the constructs. The elements in the DTD often have attributes which give the name of IDL defined entities. To correctly identify such entities, fully qualified names (in IDL sense) should be used as much as possible. For example a valuetype Foo in module Test would be referred to as "Test::Foo". In section 3.2.2.3.2.2 EnumDef replace: This tag contains an attribute name (scoped name of the IDL enumeration) and as many value sub-tags that needed to give values. With: This tag contains an attribute name (fully qualified name of the IDL enumeration) and as many value sub-tags that needed to give values. In section 3.2.2.3.2.3 TemplateDef replace: This tag contains three attributes: o name - gives the scoped name of the type. o pattern - gives the construct pattern. The supported constructs are: List, StrMap, IntMap, and Set. o itemType - gives the type of each element in the collection. With: This tag contains three attributes: o name - gives the fully qualified name of the type. o pattern - gives the construct pattern. The supported constructs are: List, StrMap, IntMap, and Set. o itemType - gives the fully qualified type name of each element in the collection. In section 3.2.2.3.2.4 AssociationDef replace: o class - contains the scoped name of the class. With: o class - contains the fully qualified name of the class. In section 3.2.2.3.2.5 compoRelationDef replace: o class - contains the scoped name of the class. With: o class - contains the fully qualified name of the class. In section 3.2.2.3.2.6 ClassMapping replace: This tag contains one attribute name that gives the scoped name of the class and: With: This tag contains one attribute name that gives the fully qualified name of the class and: In section 3.2.2.3.2.7 MainTopic replace: This tag gives the main DCPS Topic, to which that class refers. The main Topic is the topic that gives the existence of a object (an object is declared as existing if, and only if, there is an instance in that Topic matching its key value. It comprises one attribute (name) that gives the name of the Topic, one (optional) attribute (typename) that gives the name of the type (if this attribute is not supplied the type name is considered to be equal to the topic name) and: With: This tag gives the main DCPS Topic, to which that class refer. The main Topic is the topic that gives the existence of an object (an object is declared as existing if, and only if, there is an instance in that Topic matching its key value). It comprises one attribute (name) that gives the name of the Topic (must adhere to topic naming rules, see section B-3 regarding the TOPICNAME), one (optional) attribute (typename) that gives the fully qualified name of the type (if this attribute is not supplied the type name is considered to be equal to the topic name) and: Resolution: Revised Text: Actions taken: February 12, 2007: received issue Discussion: End of Annotations:===== iler: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Mon, 12 Feb 2007 16:32:40 -0500 To: issues@omg.org, dana Morris From: Juergen Boldt Subject: issue 10694 -- DDS RTF issue X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at omg.org This is issue # 10694 From: "Erik Hendriks" Clarify usage of Fully qualified names in the model tags in section 3.2.2.3 Problem: The XML as described in section 3.2.2.3 and sub section has a problem in relation to IDL modules. How to represent to valuetypes named Foo which are defined in different modules for example? It is currently not clear how this should be done. It is our suggestion to clarify that fully qualified names should be used in IDL sense. Where a valuetype Foo in module Test would be referred to as "Test::Foo". The subsections of section 3.2.2.3 should state for each element attribute if fully qualified names must be used. Solution: In section 3.2.2.3 replace: Model tags are specified by means of XML declarations that must be compliant with the DTD listed in the following section; subsequent sections give details on the constructs. With: Model tags are specified by means of XML declarations that must be compliant with the DTD listed in the following section; subsequent sections give details on the constructs. The elements in the DTD often have attributes which give the name of IDL defined entities. To correctly identify such entities, fully qualified names (in IDL sense) should be used as much as possible. For example a valuetype Foo in module Test would be referred to as "Test::Foo". In section 3.2.2.3.2.2 EnumDef replace: This tag contains an attribute name (scoped name of the IDL enumeration) and as many value sub-tags that needed to give values. With: This tag contains an attribute name (fully qualified name of the IDL enumeration) and as many value sub-tags that needed to give values. In section 3.2.2.3.2.3 TemplateDef replace: This tag contains three attributes: o name - gives the scoped name of the type. o pattern - gives the construct pattern. The supported constructs are: List, StrMap, IntMap, and Set. o itemType - gives the type of each element in the collection. With: This tag contains three attributes: o name - gives the fully qualified name of the type. o pattern - gives the construct pattern. The supported constructs are: List, StrMap, IntMap, and Set. o itemType - gives the fully qualified type name of each element in the collection. In section 3.2.2.3.2.4 AssociationDef replace: o class - contains the scoped name of the class. With: o class - contains the fully qualified name of the class. In section 3.2.2.3.2.5 compoRelationDef replace: o class - contains the scoped name of the class. With: o class - contains the fully qualified name of the class. In section 3.2.2.3.2.6 ClassMapping replace: This tag contains one attribute name that gives the scoped name of the class and: With: This tag contains one attribute name that gives the fully qualified name of the class and: In section 3.2.2.3.2.7 MainTopic replace: This tag gives the main DCPS Topic, to which that class refers. The main Topic is the topic that gives the existence of a object (an object is declared as existing if, and only if, there is an instance in that Topic matching its key value. It comprises one attribute (name) that gives the name of the Topic, one (optional) attribute (typename) that gives the name of the type (if this attribute is not supplied the type name is considered to be equal to the topic name) and: With: This tag gives the main DCPS Topic, to which that class refer. The main Topic is the topic that gives the existence of an object (an object is declared as existing if, and only if, there is an instance in that Topic matching its key value). It comprises one attribute (name) that gives the name of the Topic (must adhere to topic naming rules, see section B-3 regarding the TOPICNAME), one (optional) attribute (typename) that gives the fully qualified name of the type (if this attribute is not supplied the type name is considered to be equal to the topic name) and: Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org