MatchGroup

**************************************-
***************************************** In a request :
***************************************** To express match information for the
response via the following information Filter : how to filter : via inclusion or
exclusion Match : how to enforce : May or Must Preferred : among the different
choice, the described one is the preferred one
***************************************** *****************************************
In a response : ***************************************** To express whether data
matches request or not. match can only be present if request must not be exact.
preferred can be present in all cases *****************************************
**************************************-

**************************************- Maintenance: DF/2003-11-13:
Comment copied from type definition **************************************-

Attribute Group Information

Attributes

QName Type Fixed Default Use Inheritable Annotation
Filter FilterCodeType optional
**************************************-
***************************************** In a request :
***************************************** used in conjunction with Match. **>
If Match is omitted, or Match=false and Filter is used, Filter does not need to
be enforced, but MAY be and is rather considered as a preference. The Match
attribute in the response may indicate whether the filter has been applied or
not. **> if Match=true, the Filter and the Rules MUST be applied
*****************************************
***************************************** In a response :
***************************************** The associated information corresponds
to data that should (Include) or should not (Exclude) be used (flight number
restrictions, black out dates, ...) **> Omitted : Filter=Include
*****************************************
**************************************-
**************************************- Maintenance:
DF/2003-11-13: Comment copied from type definition
**************************************-
Match xs:boolean optional
***************************************** In a request :
***************************************** **> true : response MUST match
input parameters exactly. Otherwise it should not be present. **> false :
response MAY match input parameters. **> omitted : Accuracy is left at the
disposal of the hosts. Match criteria can be further defined through limits and
rules. *****************************************
***************************************** In a response :
***************************************** **> true : response matches input
parameters exactly. true can be present in a response whatever the value in the
request. **> false : response does not match input parameters. false can only
be present if Match was false or omitted in the request. **> omitted:no
information is provided by host *****************************************
Preferred xs:boolean optional
**************************************-
***************************************** In a request :
***************************************** mentions that the associated element
is the preferred choice. This can also be achieved through the Index
attribute.*****************************************
***************************************** In a response :
***************************************** information only : preferred choice
has been returned. This is for easier parsing purposes
*****************************************
**************************************-
**************************************- Maintenance:
DF/2003-11-13: Comment copied from type definition
**************************************-

Used By

Complex Type AtomType

Source

<xs:attributeGroup name="MatchGroup">
  <xs:annotation>
    <xs:documentation>**************************************- ***************************************** In a request : ***************************************** To express match information for the response via the following information Filter : how to filter : via inclusion or exclusion Match : how to enforce : May or Must Preferred : among the different choice, the described one is the preferred one ***************************************** ***************************************** In a response : ***************************************** To express whether data matches request or not. match can only be present if request must not be exact. preferred can be present in all cases ***************************************** **************************************-</xs:documentation>
    <xs:documentation>**************************************- Maintenance: DF/2003-11-13: Comment copied from type definition **************************************-</xs:documentation>
  </xs:annotation>
  <xs:attribute name="Filter" type="FilterCodeType" use="optional">
    <xs:annotation>
      <xs:documentation>**************************************- ***************************************** In a request : ***************************************** used in conjunction with Match. **> If Match is omitted, or Match=false and Filter is used, Filter does not need to be enforced, but MAY be and is rather considered as a preference. The Match attribute in the response may indicate whether the filter has been applied or not. **> if Match=true, the Filter and the Rules MUST be applied ***************************************** ***************************************** In a response : ***************************************** The associated information corresponds to data that should (Include) or should not (Exclude) be used (flight number restrictions, black out dates, ...) **> Omitted : Filter=Include ***************************************** **************************************-</xs:documentation>
      <xs:documentation>**************************************- Maintenance: DF/2003-11-13: Comment copied from type definition **************************************-</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="Match" type="xs:boolean" use="optional">
    <xs:annotation>
      <xs:documentation>***************************************** In a request : ***************************************** **> true : response MUST match input parameters exactly. Otherwise it should not be present. **> false : response MAY match input parameters. **> omitted : Accuracy is left at the disposal of the hosts. Match criteria can be further defined through limits and rules. ***************************************** ***************************************** In a response : ***************************************** **> true : response matches input parameters exactly. true can be present in a response whatever the value in the request. **> false : response does not match input parameters. false can only be present if Match was false or omitted in the request. **> omitted:no information is provided by host *****************************************</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="Preferred" type="xs:boolean" use="optional">
    <xs:annotation>
      <xs:documentation>**************************************- ***************************************** In a request : ***************************************** mentions that the associated element is the preferred choice. This can also be achieved through the Index attribute.***************************************** ***************************************** In a response : ***************************************** information only : preferred choice has been returned. This is for easier parsing purposes ***************************************** **************************************-</xs:documentation>
      <xs:documentation>**************************************- Maintenance: DF/2003-11-13: Comment copied from type definition **************************************-</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:attributeGroup>