EDOC 1.0 NO IDEA Avatar
  1. OMG Issue

EDOC — Document Model as part of CCA does not align with the UML metamodel

Open Closed All
  • Key: EDOC-65
  • Legacy Issue Number: 5328
  • Status: closed  
  • Source: Edmond Scientific Company ( Tony Mallia)
  • Summary:

    Working through the EDOC profile ptc/02-02-05 the following issues came to light:

    The Document Model as part of CCA does not align with the UML metamodel - the CompositeData looks as if it can have a feature (Attribute) which is not "byValue" indicating that the aggregation might not be a composite. The Document Model is critical in that it must be able to map to the platform message including Java serailized objects, XML schema and DOM.

    The base Element for Key, Key Element and Key Attribute is Class. It seems more appropriate not to force the class to be stereotyped but rather the AssociationEnd or AttributeLink where the element type is used as a Key. If the class is stereotyped, then all its occurences are stereotyped and it may not be used in every case as a key.

  • Reported: EDOC 1.0b1 — Sat, 25 May 2002 04:00 GMT
  • Disposition: Resolved — EDOC 1.0
  • Disposition Summary:

    No Data Available
  • Updated: Fri, 6 Mar 2015 23:14 GMT