Issue 1497: Naming of Tags (mof-rtf) Source: (, ) Nature: Revision Severity: Minor Summary: Summary: The MOF Model allows Tags to be attached to any model element. This provides a mechanism for extending the MOF Model with extra meta-meta-information that (for example) could pertain to model server code generation. Tags are currently unrestricted name value pairs. However, in order to ensure interoperability of Tags, there needs to be agreement on their "meaning". The first step to ensuring this is to define conventions for Tag names. These should allow tag names that 1) apply to all kinds of meta-model, 2) are defined for specific families of meta-models (e.g. when the MOF Model is re-used in another OMG spec), 3) are defined by a vendors product line, or 4) are defined by the end user. Resolution: closed issue, resolved Revised Text: Actions taken: June 4, 1998: received issue May 8, 2000: closed issue Discussion: 1 Additional Text: 2 There are many possible conventions for tag name format. For example: 3 Java-like: 4 "org.omg.MOF.some_tag" "org.omg.BOCA.some_other_tag" "com.rational.rose.screen_position" "au.edu.dstc.elvin_event_type" 5 Domain name : tag name:6 "omg.org:MOF.some_tag" "omg.org:BOCA.some_other_tag" "rational.com:rose.screen_position" "dstc.edu.au:elvin_event_type" 7 Etcetera 8 Proposed resolution: accept in principle pending concrete proposal. Implementation: Added text to Section 3.4.23, “Tag,” on page 3-68 to recommend that Tags be named in the Java-style (using the reversed Internet do-main name as a prefix). Done. [SC] End of Annotations:===== Return-Path: To: mof-rtf@omg.org, issues@omg.org Subject: MOF-RTF Issue: Naming of Tags errors-to: request@omg.org priority: bulk Date: Thu, 04 Jun 1998 11:53:50 +1000 From: Stephen Crawley Source: DSTC (Dr. Stephen Crawley, crawley@dstc.edu.au) Nature: Revision Severity: Minor Summary: The MOF Model allows Tags to be attached to any model element. This provides a mechanism for extending the MOF Model with extra meta-meta-information that (for example) could pertain to model server code generation. Tags are currently unrestricted name value pairs. However, in order to ensure interoperability of Tags, there needs to be agreement on their "meaning". The first step to ensuring this is to define conventions for Tag names. These should allow tag names that 1) apply to all kinds of meta-model, 2) are defined for specific families of meta-models (e.g. when the MOF Model is re-used in another OMG spec), 3) are defined by a vendors product line, or 4) are defined by the end user. Additional Text: There are many possible conventions for tag name format. For example: Java-like: "org.omg.MOF.some_tag" "org.omg.BOCA.some_other_tag" "com.rational.rose.screen_position" "au.edu.dstc.elvin_event_type" Domain name : tag name: "omg.org:MOF.some_tag" "omg.org:BOCA.some_other_tag" "rational.com:rose.screen_position" "dstc.edu.au:elvin_event_type" Etcetera Return-Path: Date: Thu, 30 Jul 1998 07:07:04 -0700 From: GK Khalsa Organization: Object Radiance, Inc. To: "mof-rtf@omg.org" Subject: Discussion of Issue 1497 Discussion of Issue 1497: Naming of Tags Clarification -- the issue should pertain to the tagId attribute, not the Tag's name attribute. Because each name must be unique, the "name-value" association provided by a tag is actually provided by the tagId-values attributes. -- GK Khalsa khalsa@objectrad.com Object Radiance, Inc. v: +1 909 677 2518 Murrieta, CA USA f: +1 909 677 1478