Qualifier mapping of tool differs from spec

Submitted by Josef Kaltwasser on Wednesday, 19 May, 2010 - 17:04
Issue ID
Bug report

The tool maps qualifiers to XML attributes with the name of the qualifier, e.g.:
  <xs:complexType name="_VmsPictogramDisplayAreaIndexPictogramDisplayAreaSettings">
      <xs:element name="pictogramDisplayAreaSettings" type="D2LogicalModel:PictogramDisplayAreaSettings" minOccurs="1" maxOccurs="1" />
    <xs:attribute name="pictogramDisplayAreaIndex" type="xs:int" use="required" />

for the qualifier pictogtramDisplayAreaIndex,
whereas the methodology states that all qualifiers shall be mapped to an XML attribute with fixed name "index":

<xs:complexType name="_<name>">
    <xs:element name="<name1>" type="<name2>" minOccurs="1" maxOccurs="1" />
  <xs:attribute name="index" type="xs:int" use="required" />

Whether this is seen as a bug in the tool or a bug in the description is arbitrary, just that currently the two are not consistent!

{"changeLogs":[{"date":1528113638247,"assignedOLD":"","assigned":"Josef Kaltwasser (18)","statusOLD":"- None -","status":"Closed","priorityOLD":"- None -","priority":"Normal","categoryOLD":"- Select a value -","category":"Bug report","componentOLD":"- Select a value -","component":"Methodology"},{"date":1537270891141}]}

Posted by Anonymous (not verified) on January 24, 2028 Permalink

I recall that I raised this issue about the name of the qualifier at a TG meeting and requested that it be allowed to be specific to the association since it makes it clearer, certainly when describing the model which qualifier is being refered to, especially when a class has more than one association which uses a qualifier. The tool was changed accordingly, hence I would suggest that the methodology document be aligned.

Posted by jaderberg on January 24, 2028 Permalink

Yes, agree with Tim. This have changed.

I change it to a bug in the Methodology..

Posted by Josef Kaltwasser on October 24, 2027 Permalink

Qualifier mapping will retain the name from the UML qualifier in v2.0.