Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Properties
Source
Used by
Main schema DelineationObjectAcknowledgementMK_V1p0.xsd
Namespace urn:metsateho:delineationobject
Properties
attribute form default: unqualified
element form default: qualified
version: draft_1.0
Element DelineationObjectAcknowledgementMK
Namespace urn:metsateho:delineationobject
Diagram
Diagram index0.tmp#id23 index1.tmp#id4 index1.tmp#id10 index1.tmp#id22 index1.tmp#id3
Type DelineationObjectAcknowledgementMKType
Properties
content: complex
Model Header , DelineationObjectAcknowledgement , Extension{0,1}
Children DelineationObjectAcknowledgement, Extension, Header
Instance
 
<DelineationObjectAcknowledgementMK version="" versionDate="">
  <Header>{1,1}</Header>
  <DelineationObjectAcknowledgement>{1,1}</DelineationObjectAcknowledgement>
  <Extension extensionAction="">{0,1}</Extension>
</DelineationObjectAcknowledgementMK>
Attributes
QName Type Fixed Default Use Annotation
version StanForD2010VersionType required
1.0 version number The version number of the message in format: "major"."minor", where "major" is a sequential number of the major version (start from 1) and "minor" is a sequential number of the minor version.>
versionDate xsd:date required
1.0 yyyy-mm-dd Date of version
Source
 
<xsd:element name="DelineationObjectAcknowledgementMK" type="DelineationObjectAcknowledgementMKType"/>
Element DelineationObjectAcknowledgementMKType / Header
Namespace urn:metsateho:delineationobject
Diagram
Diagram index1.tmp#id6 index1.tmp#id7 index1.tmp#id8 index1.tmp#id5
Type HeaderType
Properties
content: complex
Model MessageID , OriginalMessageID , MessageCreationTime
Children MessageCreationTime, MessageID, OriginalMessageID
Instance
 
<Header>
  <MessageID>{1,1}</MessageID>
  <OriginalMessageID>{1,1}</OriginalMessageID>
  <MessageCreationTime>{1,1}</MessageCreationTime>
</Header>
Source
 
<xsd:element name="Header" type="HeaderType"/>
Element HeaderType / MessageID
Namespace urn:metsateho:delineationobject
Annotations
free text Unique identity of message.
Diagram
Diagram
Type xsd:string
Properties
content: simple
Source
 
<xsd:element name="MessageID" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>
      <doc:Unit>free text</doc:Unit>
      <doc:Description>Unique identity of message.</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element HeaderType / OriginalMessageID
Namespace urn:metsateho:delineationobject
Annotations
free text Unique identity of received DelienationObjectMK-message. This identifier is received from sender in MessageID-element of corresbonding DelienationObjectMK-message.
Diagram
Diagram
Type xsd:string
Properties
content: simple
Source
 
<xsd:element name="OriginalMessageID" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>
      <doc:Unit>free text</doc:Unit>
      <doc:Description>Unique identity of received DelienationObjectMK-message. This identifier is received from sender in MessageID-element of  corresbonding  DelienationObjectMK-message.</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element HeaderType / MessageCreationTime
Namespace urn:metsateho:delineationobject
Annotations
yyyy-mm-ddThh:mm:ss[+|-]hh:mm Transmission time and date of DelineationObjectAcknowledgementMK message. Time stamp must have the following times registered: local time ±offset from UTC.
Diagram
Diagram index0.tmp#id9
Type StanForD2010DateTimeType
Properties
content: simple
Facets
pattern .+T.+[+-].+
Source
 
<xsd:element name="MessageCreationTime" type="StanForD2010DateTimeType">
  <xsd:annotation>
    <xsd:documentation>
      <doc:Unit>yyyy-mm-ddThh:mm:ss[+|-]hh:mm</doc:Unit>
      <doc:Description>Transmission time and date of DelineationObjectAcknowledgementMK  message.  Time stamp must have the following times registered: local time ±offset from UTC.</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element DelineationObjectAcknowledgementMKType / DelineationObjectAcknowledgement
Namespace urn:metsateho:delineationobject
Diagram
Diagram index1.tmp#id12 index1.tmp#id13 index1.tmp#id18 index1.tmp#id11
Type DelineationObjectAcknowledgementType
Properties
content: complex
Model OrderID{0,1} , DelineationObjectStatus , Extension{0,1}
Children DelineationObjectStatus, Extension, OrderID
Instance
 
<DelineationObjectAcknowledgement>
  <OrderID>{0,1}</OrderID>
  <DelineationObjectStatus>{1,1}</DelineationObjectStatus>
  <Extension extensionAction="">{0,1}</Extension>
</DelineationObjectAcknowledgement>
Source
 
<xsd:element name="DelineationObjectAcknowledgement" type="DelineationObjectAcknowledgementType"/>
Element DelineationObjectAcknowledgementType / OrderID
Namespace urn:metsateho:delineationobject
Annotations
free text Globally unique identifier for delineation object. This identifier is provided to sender when delineation object is received to delineation process.
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
 
<xsd:element name="OrderID" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>
      <doc:Unit>free text</doc:Unit>
      <doc:Description>Globally unique identifier for delineation object. This identifier is provided to sender when delineation object is received to delineation process.</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element DelineationObjectAcknowledgementType / DelineationObjectStatus
Namespace urn:metsateho:delineationobject
Diagram
Diagram index1.tmp#id15 index1.tmp#id17 index1.tmp#id14
Type DelineationObjectStatusType
Properties
content: complex
Model StatusCode , StatusDescription{0,1}
Children StatusCode, StatusDescription
Instance
 
<DelineationObjectStatus>
  <StatusCode>{1,1}</StatusCode>
  <StatusDescription>{0,1}</StatusDescription>
</DelineationObjectStatus>
Source
 
<xsd:element name="DelineationObjectStatus" type="DelineationObjectStatusType"/>
Element DelineationObjectStatusType / StatusCode
Namespace urn:metsateho:delineationobject
Annotations
enumeration list Status code of processing delineation object. Allowed values are: "OK", "Delineation object processing error", "Delineation object is in processing"
Diagram
Diagram
Type StatusCodeType
Type hierarchy
Properties
content: simple
Facets
enumeration OK
enumeration Validation error
Source
 
<xsd:element name="StatusCode">
  <xsd:annotation>
    <xsd:documentation>
      <doc:Unit>enumeration list</doc:Unit>
      <doc:Description>Status code of processing delineation object. Allowed values are: "OK", "Delineation object processing error", "Delineation object is in processing"</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="StatusCodeType"/>
  </xsd:simpleType>
</xsd:element>
Element DelineationObjectStatusType / StatusDescription
Namespace urn:metsateho:delineationobject
Annotations
free textt Status description of receiving of message
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
 
<xsd:element name="StatusDescription" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>
      <doc:Unit>free textt</doc:Unit>
      <doc:Description>Status description of receiving of message</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element DelineationObjectAcknowledgementType / Extension
Namespace urn:metsateho:delineationobject
Annotations
1.0 Extension element can include whatever data the users want. The only requirement is that it is well-formed XML i.e. it is tagged
Diagram
Diagram index0.tmp#id20 index0.tmp#id19
Type ExtensionType
Properties
content: complex
minOccurs: 0
Model ANY element from ANY namespace
Attributes
QName Type Fixed Default Use Annotation
extensionAction ExtensionActionType optional
1.0 list Enumeration list. Allowed values are: "Copy" and "Ignore". The purpose of this attribute is to inform the receiver of the message that sender want to get back the copy of the content of the extension structure. For example if we have product specifiic information in extension structure send in pin-message we might want that back in hpr-message.
Source
 
<xsd:element name="Extension" type="ExtensionType" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>
      <doc:VersionCreated>1.0</doc:VersionCreated>
      <doc:Description>Extension element can include whatever data the users want. The only requirement is that it is well-formed XML i.e. it is tagged</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element DelineationObjectAcknowledgementMKType / Extension
Namespace urn:metsateho:delineationobject
Annotations
1.0 Extension element can include whatever data the users want. The only requirement is that it is well-formed XML i.e. it is tagged
Diagram
Diagram index0.tmp#id20 index0.tmp#id19
Type ExtensionType
Properties
content: complex
minOccurs: 0
Model ANY element from ANY namespace
Attributes
QName Type Fixed Default Use Annotation
extensionAction ExtensionActionType optional
1.0 list Enumeration list. Allowed values are: "Copy" and "Ignore". The purpose of this attribute is to inform the receiver of the message that sender want to get back the copy of the content of the extension structure. For example if we have product specifiic information in extension structure send in pin-message we might want that back in hpr-message.
Source
 
<xsd:element name="Extension" type="ExtensionType" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>
      <doc:VersionCreated>1.0</doc:VersionCreated>
      <doc:Description>Extension element can include whatever data the users want. The only requirement is that it is well-formed XML i.e. it is tagged</doc:Description>
    </xsd:documentation>
  </xsd:annotation>
</xsd:element>
Complex Type DelineationObjectAcknowledgementMKType
Namespace urn:metsateho:delineationobject
Diagram
Diagram index0.tmp#id23 index1.tmp#id4 index1.tmp#id10 index1.tmp#id22
Used by
Model Header , DelineationObjectAcknowledgement , Extension{0,1}
Children DelineationObjectAcknowledgement, Extension, Header
Attributes
QName Type Fixed Default Use Annotation
version StanForD2010VersionType required
1.0 version number The version number of the message in format: "major"."minor", where "major" is a sequential number of the major version (start from 1) and "minor" is a sequential number of the minor version.>
versionDate xsd:date required
1.0 yyyy-mm-dd Date of version
Source
 
<xsd:complexType name="DelineationObjectAcknowledgementMKType">
  <xsd:sequence>
    <xsd:element name="Header" type="HeaderType"/>
    <xsd:element name="DelineationObjectAcknowledgement" type="DelineationObjectAcknowledgementType"/>
    <xsd:element name="Extension" type="ExtensionType" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>
          <doc:VersionCreated>1.0</doc:VersionCreated>
          <doc:Description>Extension element can include whatever data the users want. The only requirement is that it is well-formed XML i.e. it is tagged</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
  </xsd:sequence>
  <xsd:attributeGroup ref="MessageAttributeGroup"/>
</xsd:complexType>
Complex Type HeaderType
Namespace urn:metsateho:delineationobject
Diagram
Diagram index1.tmp#id6 index1.tmp#id7 index1.tmp#id8
Used by
Model MessageID , OriginalMessageID , MessageCreationTime
Children MessageCreationTime, MessageID, OriginalMessageID
Source
 
<xsd:complexType name="HeaderType">
  <xsd:sequence>
    <xsd:element name="MessageID" type="xsd:string">
      <xsd:annotation>
        <xsd:documentation>
          <doc:Unit>free text</doc:Unit>
          <doc:Description>Unique identity of message.</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="OriginalMessageID" type="xsd:string">
      <xsd:annotation>
        <xsd:documentation>
          <doc:Unit>free text</doc:Unit>
          <doc:Description>Unique identity of received DelienationObjectMK-message. This identifier is received from sender in MessageID-element of  corresbonding  DelienationObjectMK-message.</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="MessageCreationTime" type="StanForD2010DateTimeType">
      <xsd:annotation>
        <xsd:documentation>
          <doc:Unit>yyyy-mm-ddThh:mm:ss[+|-]hh:mm</doc:Unit>
          <doc:Description>Transmission time and date of DelineationObjectAcknowledgementMK  message.  Time stamp must have the following times registered: local time ±offset from UTC.</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
  </xsd:sequence>
</xsd:complexType>
Complex Type DelineationObjectAcknowledgementType
Namespace urn:metsateho:delineationobject
Diagram
Diagram index1.tmp#id12 index1.tmp#id13 index1.tmp#id18
Used by
Model OrderID{0,1} , DelineationObjectStatus , Extension{0,1}
Children DelineationObjectStatus, Extension, OrderID
Source
 
<xsd:complexType name="DelineationObjectAcknowledgementType">
  <xsd:sequence>
    <xsd:element name="OrderID" type="xsd:string" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>
          <doc:Unit>free text</doc:Unit>
          <doc:Description>Globally unique identifier for delineation object. This identifier is provided to sender when delineation object is received to delineation process.</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="DelineationObjectStatus" type="DelineationObjectStatusType"/>
    <xsd:element name="Extension" type="ExtensionType" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>
          <doc:VersionCreated>1.0</doc:VersionCreated>
          <doc:Description>Extension element can include whatever data the users want. The only requirement is that it is well-formed XML i.e. it is tagged</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
  </xsd:sequence>
</xsd:complexType>
Complex Type DelineationObjectStatusType
Namespace urn:metsateho:delineationobject
Diagram
Diagram index1.tmp#id15 index1.tmp#id17
Used by
Model StatusCode , StatusDescription{0,1}
Children StatusCode, StatusDescription
Source
 
<xsd:complexType name="DelineationObjectStatusType">
  <xsd:sequence>
    <xsd:element name="StatusCode">
      <xsd:annotation>
        <xsd:documentation>
          <doc:Unit>enumeration list</doc:Unit>
          <doc:Description>Status code of processing delineation object. Allowed values are: "OK", "Delineation object processing error", "Delineation object is in processing"</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
      <xsd:simpleType>
        <xsd:restriction base="StatusCodeType"/>
      </xsd:simpleType>
    </xsd:element>
    <xsd:element name="StatusDescription" type="xsd:string" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation>
          <doc:Unit>free textt</doc:Unit>
          <doc:Description>Status description of receiving of message</doc:Description>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
  </xsd:sequence>
</xsd:complexType>
Simple Type StatusCodeType
Namespace urn:metsateho:delineationobject
Diagram
Diagram
Type restriction of xsd:string
Facets
enumeration OK
enumeration Validation error
Used by
Source
 
<xsd:simpleType name="StatusCodeType">
  <xsd:restriction base="xsd:string">
    <xsd:enumeration value="OK"/>
    <xsd:enumeration value="Validation error"/>
  </xsd:restriction>
</xsd:simpleType>
XML Schema documentation generated by ® XML Editor.