GEMS 1.2 RTF Avatar
  1. OMG Issue

GEMS12 — Defining arrays of ParameterSets in GEMS-XML is unclear

  • Key: GEMS12-11
  • Legacy Issue Number: 15497
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    Unlike a normal Parameter with multiplicity greater than 1, a ParameterSet array contains ParameterSet elements. These each have a name and multiplicity with then that need to be ignored.
    Proposed Resolution: Add the following comment to the XSD for a ParameterSet:
    NOTE: If the multiplicity is set, then the contained ParameterSet's are entries in the
    array and the name & multiplicity (if specified) are ignored.

  • Reported: GEMS 1.1 — Thu, 2 Sep 2010 04:00 GMT
  • Disposition: Resolved — GEMS 1.2
  • Disposition Summary:

    The issue here is that normally an element of an array parameter does not itself have a name or multiplicity. When translating between GEMS-XML and GEMS-ASCII there is no mapping for these. However, in GEMS-XML the XML schema allows for their existence.
    For example, a normal parameter array is defined as follows in GEMS-XML:

    <Parameter name="myarray" multiplicity="2">
    <long>1</long>
    <long>2</long>
    </Parameter>

    In contrast, a parameter set array is defined as follows in GEMS-XML:

    <ParameterSet multiplicity="2" name="setlist">
    <ParameterSet>
    <Parameter name="param1">
    <hex_value bit_length="2">0F</hex_value>
    </Parameter>
    <Parameter name="param2">
    <string>text1</string>
    </Parameter>
    </ParameterSet>
    <ParameterSet>
    <Parameter name="param1">
    <hex_value bit_length="2">1F</hex_value>
    </Parameter>
    <Parameter name="param2">
    <string>text2</string>
    </Parameter>
    </ParameterSet>
    </ParameterSet>

    Per the XML schema, it is legal to add a multiplicity and name to the internal ParameterSet elements. This is effectively an extra layer of nesting that is not required in the GEMS-ASCII version and no mapping existing for the name and multiplicity.
    To clarify the specification a comment shall be added to section 7.1.1.3 indicating that these values will be ignored.
    To further help clarify this, an additional parameter set array will be added to the SetConfigMessage example in section 7.2.4.1.

  • Updated: Fri, 6 Mar 2015 20:58 GMT