<xs:attributeGroup name="MinMaxGroup">
<xs:annotation>
<xs:documentation>The unit to be used is the one associated with the object. If the unit has to be provided or if mulitple limits are to be expressed, a rule needs be used.</xs:documentation>
</xs:annotation>
<xs:attribute name="Quantity" type="QuantityCodeType" use="optional">
<xs:annotation>
<xs:documentation>Request: the requested quantity Response: the actual quantity associated with the component This value can be used in complement with the other attributes to provided additional information (min, max, preference, ...)</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attributeGroup ref="QuantityGroup"/>
<xs:attribute name="Min" type="QuantityCodeType" use="optional">
<xs:annotation>
<xs:documentation>Minimum number of units associated with the quantity</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="Max" type="QuantityCodeType" use="optional">
<xs:annotation>
<xs:documentation>Maximum number of units .</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="Extremity" type="ExtremityCodeType" use="optional">
<xs:annotation>
<xs:documentation>**************************************- When a range is provided with a Min - Max, boundaries may or may not be included in the range. How extremities should be handled is provided here: **************************************- **> None: ]Min,Max[ **> Left: ]Min,Max] **> Right: [Min,Max[ **> Both: [Min,Max] Default or omitted = Both **************************************-</xs:documentation>
<xs:documentation>**************************************- Maintenance: DF/2003-11-13: Comment copied from type definition **************************************-</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="Step" type="xs:decimal" use="optional"/>
</xs:attributeGroup> |