xvergabe-service

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

The unique ID of the single message to return. If this ID is specified, the server MUST return only this one message or create an error response if it does not exist.

source

<xs:element name="messageID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>The unique ID of the single message to return. If this ID is specified, the server MUST return only this one message or create an error response if it does not exist.</xs:documentation>
</xs:annotation>
</xs:element>

element MessageSelector/tenderingID

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

The unique ID of the tendering procedure for which messages shall be returned. If only this ID is specified, the server MUST return all messages for the client concerning this tendering procedure.

source

<xs:element name="tenderingID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>The unique ID of the tendering procedure for which messages shall be returned. If only this ID is specified, the server MUST return all messages for the client concerning this tendering procedure.</xs:documentation>
</xs:annotation>
</xs:element>

element MessageSelector/lastKnownMessageID

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

properties

minOcc	0
maxOcc	1
content	simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

The unique ID of the latest message that the client has received in previous message exchanges. If this ID is specified, the server MUST return only the messages that were generated AFTER the message identified by this ID.

source

<xs:element name="lastKnownMessageID" type="xvergabe-datatypes:GUID" minOccurs="0">
<xs:annotation>
<xs:documentation>The unique ID of the latest message that the client has received in previous message exchanges. If this ID is specified, the server MUST return only the messages that were generated AFTER the message identified by this ID.</xs:documentation>
</xs:annotation>
</xs:element>

complexType msgTypeGetDocumentRequest

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

children

xvergabe-if-svc:ID

annotation

documentation

A request from the client to the server to download a specific document.

source

<xs:complexType name="msgTypeGetDocumentRequest">
<xs:annotation>
    <xs:documentation>A request from the client to the server to download a specific document.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="ID" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>The unique ID of the requested document. This ID should have been provided by the server in a previous message exchange.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element msgTypeGetDocumentRequest/ID

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

The unique ID of the requested document. This ID should have been provided by the server in a previous message exchange.

source

<xs:element name="ID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>The unique ID of the requested document. This ID should have been provided by the server in a previous message exchange.</xs:documentation>
</xs:annotation>
</xs:element>

complexType msgTypeGetDocumentResponse

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl xvergabe-if-svc:document

properties

base	xvergabe-if-svc:AbstractResponse

children

annotation

documentation

A response to a GetDocumentRequest.

source

<xs:complexType name="msgTypeGetDocumentResponse">
<xs:annotation>
    <xs:documentation>A response to a GetDocumentRequest.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if-svc:AbstractResponse">
      <xs:sequence>
        <xs:element name="document" type="xvergabe-if:Attachment" minOccurs="0">
          <xs:annotation>
            <xs:documentation>The requested document.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element msgTypeGetDocumentResponse/document

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xvergabe-if:attachmentID xvergabe-if:filename xvergabe-if:description xvergabe-if:attachmentData xvergabe-if:signature

properties

minOcc	0
maxOcc	1
content	complex

children

annotation

documentation

The requested document.

source

<xs:element name="document" type="xvergabe-if:Attachment" minOccurs="0">
<xs:annotation>
<xs:documentation>The requested document.</xs:documentation>
</xs:annotation>
</xs:element>

complexType msgTypeGetMessagesRequest

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

children

xvergabe-if-svc:parameter

annotation

documentation

A request from the client to the server to get messages that are available for a specified tendering procedure.

source

<xs:complexType name="msgTypeGetMessagesRequest">
<xs:annotation>
    <xs:documentation>A request from the client to the server to get messages that are available for a specified tendering procedure.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="parameter" type="xvergabe-if-svc:MessageSelector">
      <xs:annotation>
        <xs:documentation>The parameters defining which messages to include in the response. The client can specify either a single message or a set of messages from a specified tendering procedure.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element msgTypeGetMessagesRequest/parameter

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xvergabe-if-svc:MessageSelector

properties

content

complex

children

xvergabe-if-svc:messageID xvergabe-if-svc:tenderingID xvergabe-if-svc:lastKnownMessageID

annotation

documentation

The parameters defining which messages to include in the response. The client can specify either a single message or a set of messages from a specified tendering procedure.

source

<xs:element name="parameter" type="xvergabe-if-svc:MessageSelector">
<xs:annotation>
<xs:documentation>The parameters defining which messages to include in the response. The client can specify either a single message or a set of messages from a specified tendering procedure.</xs:documentation>
</xs:annotation>
</xs:element>

complexType msgTypeGetMessagesResponse

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl xvergabe-if-svc:messageBundle

properties

base	xvergabe-if-svc:AbstractResponse

children

annotation

documentation

A response to a GetMessagesResponse.

source

<xs:complexType name="msgTypeGetMessagesResponse">
<xs:annotation>
    <xs:documentation>A response to a GetMessagesResponse.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if-svc:AbstractResponse">
      <xs:sequence>
        <xs:element name="messageBundle" minOccurs="0" maxOccurs="unbounded">
          <xs:annotation>
            <xs:documentation>a message bundled with an ordernumber (for sorting the messages within the response).</xs:documentation>
          </xs:annotation>
          <xs:complexType>
            <xs:sequence>
              <xs:element name="responseMessageOrderNumber" type="xs:nonNegativeInteger">
                <xs:annotation>
                  <xs:documentation>Sequence number of a message within the set of messages contained in this response. The sequence number MUST be in chronological order of the date the message was created.</xs:documentation>
                </xs:annotation>
              </xs:element>
              <xs:element name="message" type="xvergabe-if:AbstractServerMessage">
                <xs:annotation>
                  <xs:documentation>The actual message.</xs:documentation>
                </xs:annotation>
              </xs:element>
            </xs:sequence>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element msgTypeGetMessagesResponse/messageBundle

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

properties

minOcc	0
maxOcc	unbounded
content	complex

children

xvergabe-if-svc:responseMessageOrderNumber xvergabe-if-svc:message

annotation

documentation

a message bundled with an ordernumber (for sorting the messages within the response).

source

<xs:element name="messageBundle" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
    <xs:documentation>a message bundled with an ordernumber (for sorting the messages within the response).</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:sequence>
      <xs:element name="responseMessageOrderNumber" type="xs:nonNegativeInteger">
        <xs:annotation>
          <xs:documentation>Sequence number of a message within the set of messages contained in this response. The sequence number MUST be in chronological order of the date the message was created.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="message" type="xvergabe-if:AbstractServerMessage">
        <xs:annotation>
          <xs:documentation>The actual message.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
</xs:complexType>
</xs:element>

element msgTypeGetMessagesResponse/messageBundle/responseMessageOrderNumber

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xs:nonNegativeInteger

properties

content

simple

annotation

documentation

Sequence number of a message within the set of messages contained in this response. The sequence number MUST be in chronological order of the date the message was created.

source

<xs:element name="responseMessageOrderNumber" type="xs:nonNegativeInteger">
<xs:annotation>
<xs:documentation>Sequence number of a message within the set of messages contained in this response. The sequence number MUST be in chronological order of the date the message was created.</xs:documentation>
</xs:annotation>
</xs:element>

element msgTypeGetMessagesResponse/messageBundle/message

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xvergabe-if:AbstractServerMessage

properties

content

complex

children

xvergabe-if:messageHeader

annotation

documentation

The actual message.

source

<xs:element name="message" type="xvergabe-if:AbstractServerMessage">
<xs:annotation>
<xs:documentation>The actual message.</xs:documentation>
</xs:annotation>
</xs:element>

complexType msgTypeGetOSCITransferIDRequest

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

extension of xvergabe-if:OSCITransferIDRequestType

properties

base	xvergabe-if:OSCITransferIDRequestType

children

xvergabe-if:messageHeader xvergabe-if:offer xvergabe-if:participationRequest xvergabe-if:withdrawal

annotation

documentation

A request from the client to the server to obtain a messageID in order to transfer the offer, participation request or withdrawal via OSCI Transport to the platform.
The client uses the ID delivered in the response as the subject in the OSCI message delivering the object in question. The platform SHALL pull messages / delivery receipts from the OSCI intermediary based on the ID / subject and thus create a link between the delivered object and the ID.
This MUST be the first step in the scenario delivering the object in question via OSCI-Transport.
A platform not supporting OSCI-Transport MUST send an ERROR-Response back to the client.

source

<xs:complexType name="msgTypeGetOSCITransferIDRequest">
<xs:annotation>
<xs:documentation>A request from the client to the server to obtain a messageID in order to transfer the offer, participation request or withdrawal via OSCI Transport to the platform.
The client uses the ID delivered in the response as the subject in the OSCI message delivering the object in question. The platform SHALL pull messages / delivery receipts from the OSCI intermediary based on the ID / subject and thus create a link between the delivered object and the ID.
This MUST be the first step in the scenario delivering the object in question via OSCI-Transport.
A platform not supporting OSCI-Transport MUST send an ERROR-Response back to the client.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="xvergabe-if:OSCITransferIDRequestType"/>
</xs:complexContent>
</xs:complexType>

complexType msgTypeGetOSCITransferIDResponse

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl xvergabe-if-svc:OSCITransferID

properties

base	xvergabe-if-svc:AbstractResponse

children

annotation

documentation

a servers response to a getOSCITransferIDRequest. Includes the TransferID issued by the server. MAY be omitted if there is a error (e.g. when the platform does not support OSCI Transport or if the objectID for the withdrawal request is not known to the platform).
When an error occurs, an error message MUST be present in the response. In case the OSCITransferIDRequest was initiated in order to sent a withdrawal and the objectID to withdraw was unknown to the platform, the ERROR code (mainResponseCode) must be INVALID_ID.

source

<xs:complexType name="msgTypeGetOSCITransferIDResponse">
<xs:annotation>
    <xs:documentation>a servers response to a getOSCITransferIDRequest. Includes the TransferID issued by the server. MAY be omitted if there is a error (e.g. when the platform does not support OSCI Transport or if the objectID for the withdrawal request is not known to the platform).
When an error occurs, an error message MUST be present in the response. In case the OSCITransferIDRequest was initiated in order to sent a withdrawal and the objectID to withdraw was unknown to the platform, the ERROR code (mainResponseCode) must be INVALID_ID.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if-svc:AbstractResponse">
      <xs:sequence>
        <xs:element name="OSCITransferID" type="xvergabe-datatypes:GUID" minOccurs="0">
          <xs:annotation>
            <xs:documentation>the TransferID issued by the platform. This ID MUST be used as an OSCI-subject in the OSCI-message the client sends to the OSCI intermediary.
This ID MAY be absent when an error occurs.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element msgTypeGetOSCITransferIDResponse/OSCITransferID

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

properties

minOcc	0
maxOcc	1
content	simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

the TransferID issued by the platform. This ID MUST be used as an OSCI-subject in the OSCI-message the client sends to the OSCI intermediary.
This ID MAY be absent when an error occurs.

source

<xs:element name="OSCITransferID" type="xvergabe-datatypes:GUID" minOccurs="0">
<xs:annotation>
<xs:documentation>the TransferID issued by the platform. This ID MUST be used as an OSCI-subject in the OSCI-message the client sends to the OSCI intermediary.
This ID MAY be absent when an error occurs.</xs:documentation>
</xs:annotation>
</xs:element>

complexType msgTypeGetTenderIDsRequest

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

annotation

documentation

A request from the client to the server to list the IDs of the tendering procedure the client has subscribed.

source

<xs:complexType name="msgTypeGetTenderIDsRequest">
<xs:annotation>
<xs:documentation>A request from the client to the server to list the IDs of the tendering procedure the client has subscribed.</xs:documentation>
</xs:annotation>
</xs:complexType>

complexType msgTypeGetTenderIDsResponse

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl xvergabe-if-svc:procedure

properties

base	xvergabe-if-svc:AbstractResponse

children

annotation

documentation

A response to a GetTenderIDsRequest.

source

<xs:complexType name="msgTypeGetTenderIDsResponse">
<xs:annotation>
    <xs:documentation>A response to a GetTenderIDsRequest.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if-svc:AbstractResponse">
      <xs:sequence>
        <xs:element name="procedure" minOccurs="0" maxOccurs="unbounded">
          <xs:annotation>
            <xs:documentation>List containing information about each tendering procedure the client has subscribed to.</xs:documentation>
          </xs:annotation>
          <xs:complexType>
            <xs:sequence>
              <xs:element name="tenderID" type="xvergabe-datatypes:GUID">
                <xs:annotation>
                  <xs:documentation>The unique ID of the tendering procedure.</xs:documentation>
                </xs:annotation>
              </xs:element>
              <xs:element name="tenderTitle" type="xvergabe-datatypes:String.1024">
                <xs:annotation>
                  <xs:documentation>The title of the tendering procedure.</xs:documentation>
                </xs:annotation>
              </xs:element>
              <xs:element name="lastMessageID" type="xvergabe-datatypes:GUID">
                <xs:annotation>
                  <xs:documentation>Unique ID of the latest message concerning the tendering procedure that is currently available on the platform for this user.</xs:documentation>
                </xs:annotation>
              </xs:element>
            </xs:sequence>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element msgTypeGetTenderIDsResponse/procedure

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

properties

minOcc	0
maxOcc	unbounded
content	complex

children

xvergabe-if-svc:tenderID xvergabe-if-svc:tenderTitle xvergabe-if-svc:lastMessageID

annotation

documentation

List containing information about each tendering procedure the client has subscribed to.

source

<xs:element name="procedure" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
    <xs:documentation>List containing information about each tendering procedure the client has subscribed to.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:sequence>
      <xs:element name="tenderID" type="xvergabe-datatypes:GUID">
        <xs:annotation>
          <xs:documentation>The unique ID of the tendering procedure.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="tenderTitle" type="xvergabe-datatypes:String.1024">
        <xs:annotation>
          <xs:documentation>The title of the tendering procedure.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="lastMessageID" type="xvergabe-datatypes:GUID">
        <xs:annotation>
          <xs:documentation>Unique ID of the latest message concerning the tendering procedure that is currently available on the platform for this user.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
</xs:complexType>
</xs:element>

element msgTypeGetTenderIDsResponse/procedure/tenderID

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

The unique ID of the tendering procedure.

source

<xs:element name="tenderID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>The unique ID of the tendering procedure.</xs:documentation>
</xs:annotation>
</xs:element>

element msgTypeGetTenderIDsResponse/procedure/tenderTitle

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

properties

content

simple

annotation

documentation

The title of the tendering procedure.

source

<xs:element name="tenderTitle" type="xvergabe-datatypes:String.1024">
<xs:annotation>
<xs:documentation>The title of the tendering procedure.</xs:documentation>
</xs:annotation>
</xs:element>

element msgTypeGetTenderIDsResponse/procedure/lastMessageID

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xvergabe-if-svc:inquiryMessage

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

Unique ID of the latest message concerning the tendering procedure that is currently available on the platform for this user.

source

<xs:element name="lastMessageID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>Unique ID of the latest message concerning the tendering procedure that is currently available on the platform for this user.</xs:documentation>
</xs:annotation>
</xs:element>

complexType msgTypeSendMessageRequest

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

children

annotation

documentation

A request that sends a message from the client to the server.

source

<xs:complexType name="msgTypeSendMessageRequest">
<xs:annotation>
    <xs:documentation>A request that sends a message from the client to the server.</xs:documentation>
</xs:annotation>
<xs:choice>
    <xs:element name="inquiryMessage" type="xvergabe-if:ClientInquiryMessageType">
      <xs:annotation>
        <xs:documentation>The message to send to the server.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:choice>
</xs:complexType>

element msgTypeSendMessageRequest/inquiryMessage

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xvergabe-if:ClientInquiryMessageType

properties

content

complex

children

xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment

annotation

documentation

The message to send to the server.

source

<xs:element name="inquiryMessage" type="xvergabe-if:ClientInquiryMessageType">
<xs:annotation>
<xs:documentation>The message to send to the server.</xs:documentation>
</xs:annotation>
</xs:element>

complexType msgTypeSendMessageResponse

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl

properties

base	xvergabe-if-svc:AbstractResponse

children

annotation

documentation

A response to a SendMessageResponse.

source

<xs:complexType name="msgTypeSendMessageResponse">
<xs:annotation>
<xs:documentation>A response to a SendMessageResponse.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="xvergabe-if-svc:AbstractResponse"/>
</xs:complexContent>
</xs:complexType>

complexType msgTypeSendSynchronousMessageRequest

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

children

xvergabe-if-svc:offerMessage xvergabe-if-svc:participationMessage xvergabe-if-svc:offerWithdrawalMessage xvergabe-if-svc:participationWithdrawalMessage

annotation

documentation

A request that sends a message to the server (platform) in a synchronous manner, meaning that the response includes the functional answer from the platform. Only offers, participations and withdrawal-messages MAY be sent in this way.

source

<xs:complexType name="msgTypeSendSynchronousMessageRequest">
<xs:annotation>
    <xs:documentation>A request that sends a message to the server (platform) in a synchronous manner, meaning that the response includes the functional answer from the platform. Only offers, participations and withdrawal-messages MAY be sent in this way.</xs:documentation>
</xs:annotation>
<xs:choice>
    <xs:element name="offerMessage" type="xvergabe-if:OfferMessageType">
      <xs:annotation>
        <xs:documentation>the offer message to be sent synchronously. When used in the request the Response MUST include an offerDeliveryReceiptMessage.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="participationMessage" type="xvergabe-if:ParticipationMessageType">
      <xs:annotation>
        <xs:documentation>the participation message to be sent synchronously. When used in the request the response MUST include a participationDeliveryReceiptMessage.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="offerWithdrawalMessage" type="xvergabe-if:OfferWithdrawalMessageType">
      <xs:annotation>
        <xs:documentation>the offer withdrawal message to be sent synchronously. When used in the request the response MUST include an offerWithdrawalDeliveryReceiptMessage.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="participationWithdrawalMessage" type="xvergabe-if:ParticipationWithdrawalMessageType">
      <xs:annotation>
        <xs:documentation>the participation withdrawal message to be sent synchronously. When used in the request the response MUST include a participationWithdrawalDeliveryReceiptMessage.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:choice>
</xs:complexType>

element msgTypeSendSynchronousMessageRequest/offerMessage

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xvergabe-if:OfferMessageType

properties

content

complex

children

xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment

annotation

documentation

the offer message to be sent synchronously. When used in the request the Response MUST include an offerDeliveryReceiptMessage.

source

<xs:element name="offerMessage" type="xvergabe-if:OfferMessageType">
<xs:annotation>
<xs:documentation>the offer message to be sent synchronously. When used in the request the Response MUST include an offerDeliveryReceiptMessage.</xs:documentation>
</xs:annotation>
</xs:element>

element msgTypeSendSynchronousMessageRequest/participationMessage

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xvergabe-if:ParticipationMessageType

properties

content

complex

children

xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment

annotation

documentation

the participation message to be sent synchronously. When used in the request the response MUST include a participationDeliveryReceiptMessage.

source

<xs:element name="participationMessage" type="xvergabe-if:ParticipationMessageType">
<xs:annotation>
<xs:documentation>the participation message to be sent synchronously. When used in the request the response MUST include a participationDeliveryReceiptMessage.</xs:documentation>
</xs:annotation>
</xs:element>

element msgTypeSendSynchronousMessageRequest/offerWithdrawalMessage

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xvergabe-if:OfferWithdrawalMessageType

properties

content

complex

children

xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment

annotation

documentation

the offer withdrawal message to be sent synchronously. When used in the request the response MUST include an offerWithdrawalDeliveryReceiptMessage.

source

<xs:element name="offerWithdrawalMessage" type="xvergabe-if:OfferWithdrawalMessageType">
<xs:annotation>
<xs:documentation>the offer withdrawal message to be sent synchronously. When used in the request the response MUST include an offerWithdrawalDeliveryReceiptMessage.</xs:documentation>
</xs:annotation>
</xs:element>

element msgTypeSendSynchronousMessageRequest/participationWithdrawalMessage

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xvergabe-if:ParticipationWithdrawalMessageType

properties

content

complex

children

xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment

annotation

documentation

the participation withdrawal message to be sent synchronously. When used in the request the response MUST include a participationWithdrawalDeliveryReceiptMessage.

source

<xs:element name="participationWithdrawalMessage" type="xvergabe-if:ParticipationWithdrawalMessageType">
<xs:annotation>
<xs:documentation>the participation withdrawal message to be sent synchronously. When used in the request the response MUST include a participationWithdrawalDeliveryReceiptMessage.</xs:documentation>
</xs:annotation>
</xs:element>

complexType msgTypeSendSynchronousMessageResponse

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xvergabe-if:OfferDeliveryReceiptMessageType

properties

base	xvergabe-if-svc:AbstractResponse

children

annotation

documentation

the functional/technical response to the synchronous message request.
When the request used to include an offerMessage then the response MUST include an offerDeliveryReceiptMessage.
When the request used to include an participationMessage then the response MUST include an participationDeliveryReceiptMessage.
When the request used to include an offerWithdrawalMessage then the response MUST include an offerWithdrawalDeliveryReceiptMessage.
When the request used to include an participationWithdrawalMessage then the response MUST include an participationWithdrawalDeliveryReceiptMessage.

source

<xs:complexType name="msgTypeSendSynchronousMessageResponse">
<xs:annotation>
    <xs:documentation>the functional/technical response to the synchronous message request.
When the request used to include an offerMessage then the response MUST include an offerDeliveryReceiptMessage.
When the request used to include an participationMessage then the response MUST include an participationDeliveryReceiptMessage.
When the request used to include an offerWithdrawalMessage then the response MUST include an offerWithdrawalDeliveryReceiptMessage.
When the request used to include an participationWithdrawalMessage then the response MUST include an participationWithdrawalDeliveryReceiptMessage.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if-svc:AbstractResponse">
      <xs:choice>
        <xs:element name="offerDeliveryReceiptMessage" type="xvergabe-if:OfferDeliveryReceiptMessageType" minOccurs="0">
          <xs:annotation>
            <xs:documentation>the offerDeliveryReceiptMessage delivered in response to an offerMessage (the request MUST have been an offerMessage).</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="participationDeliveryReceiptMessage" type="xvergabe-if:ParticipationDeliveryReceiptMessageType" minOccurs="0">
          <xs:annotation>
            <xs:documentation>the participationDeliveryReceiptMessage delivered in response to a participationMessage (the request MUST have been a participationMessage).</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="offerWithdrawalDeliveryReceiptMessage" type="xvergabe-if:OfferWithdrawalDeliveryReceiptMessageType" minOccurs="0">
          <xs:annotation>
            <xs:documentation>the offerWithdrawalDeliveryReceiptMessage delivered in response to an offerWithdrawalMessage (the request MUST have been an offerWithdrawalMessage).</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="participationWithdrawalDeliveryReceiptMessage" type="xvergabe-if:ParticipationWithdrawalDeliveryReceiptMessageType" minOccurs="0">
          <xs:annotation>
            <xs:documentation>the participationWithdrawalDeliveryReceiptMessage delivered in response to a participationWithdrawalMessage (the request MUST have been a participationWithdrawalMessage).</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:choice>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element msgTypeSendSynchronousMessageResponse/offerDeliveryReceiptMessage

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

properties

minOcc	0
maxOcc	1
content	complex

children

xvergabe-if:ParticipationDeliveryReceiptMessageType

annotation

documentation

the offerDeliveryReceiptMessage delivered in response to an offerMessage (the request MUST have been an offerMessage).

source

<xs:element name="offerDeliveryReceiptMessage" type="xvergabe-if:OfferDeliveryReceiptMessageType" minOccurs="0">
<xs:annotation>
<xs:documentation>the offerDeliveryReceiptMessage delivered in response to an offerMessage (the request MUST have been an offerMessage).</xs:documentation>
</xs:annotation>
</xs:element>

element msgTypeSendSynchronousMessageResponse/participationDeliveryReceiptMessage

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

properties

minOcc	0
maxOcc	1
content	complex

children

xvergabe-if:OfferWithdrawalDeliveryReceiptMessageType

annotation

documentation

the participationDeliveryReceiptMessage delivered in response to a participationMessage (the request MUST have been a participationMessage).

source

<xs:element name="participationDeliveryReceiptMessage" type="xvergabe-if:ParticipationDeliveryReceiptMessageType" minOccurs="0">
<xs:annotation>
<xs:documentation>the participationDeliveryReceiptMessage delivered in response to a participationMessage (the request MUST have been a participationMessage).</xs:documentation>
</xs:annotation>
</xs:element>

element msgTypeSendSynchronousMessageResponse/offerWithdrawalDeliveryReceiptMessage

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

properties

minOcc	0
maxOcc	1
content	complex

children

xvergabe-if:ParticipationWithdrawalDeliveryReceiptMessageType

annotation

documentation

the offerWithdrawalDeliveryReceiptMessage delivered in response to an offerWithdrawalMessage (the request MUST have been an offerWithdrawalMessage).

source

<xs:element name="offerWithdrawalDeliveryReceiptMessage" type="xvergabe-if:OfferWithdrawalDeliveryReceiptMessageType" minOccurs="0">
<xs:annotation>
<xs:documentation>the offerWithdrawalDeliveryReceiptMessage delivered in response to an offerWithdrawalMessage (the request MUST have been an offerWithdrawalMessage).</xs:documentation>
</xs:annotation>
</xs:element>

element msgTypeSendSynchronousMessageResponse/participationWithdrawalDeliveryReceiptMessage

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

properties

minOcc	0
maxOcc	1
content	complex

children

xvergabe-if-svc:tenderID xvergabe-if-svc:platformSpecificTenderID

annotation

documentation

the participationWithdrawalDeliveryReceiptMessage delivered in response to a participationWithdrawalMessage (the request MUST have been a participationWithdrawalMessage).

source

<xs:element name="participationWithdrawalDeliveryReceiptMessage" type="xvergabe-if:ParticipationWithdrawalDeliveryReceiptMessageType" minOccurs="0">
<xs:annotation>
<xs:documentation>the participationWithdrawalDeliveryReceiptMessage delivered in response to a participationWithdrawalMessage (the request MUST have been a participationWithdrawalMessage).</xs:documentation>
</xs:annotation>
</xs:element>

complexType msgTypeSubscriptionRequest

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

children

annotation

documentation

A request from the client to the server to subscribe messages about a given tendering procedure. After a successful subscription request, the client can call the operation getTenderIDs to obtain messages concerning the specified tendering procedure.

source

<xs:complexType name="msgTypeSubscriptionRequest">
<xs:annotation>
    <xs:documentation>A request from the client to the server to subscribe messages about a given tendering procedure. After a successful subscription request, the client can call the operation getTenderIDs to obtain messages concerning the specified tendering procedure.</xs:documentation>
</xs:annotation>
<xs:choice>
    <xs:element name="tenderID" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>The ID of the tendering procedure whose messages to subscribe. A Server MUST support this parameter.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="platformSpecificTenderID" type="xvergabe-datatypes:String.4096">
      <xs:annotation>
        <xs:documentation>The platform specific ID of the tendering procedure whose messages to subscribe. A Server MUST support this parameter since it used for enrollment of the client</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:choice>
</xs:complexType>

element msgTypeSubscriptionRequest/tenderID

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

The ID of the tendering procedure whose messages to subscribe. A Server MUST support this parameter.

source

<xs:element name="tenderID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>The ID of the tendering procedure whose messages to subscribe. A Server MUST support this parameter.</xs:documentation>
</xs:annotation>
</xs:element>

element msgTypeSubscriptionRequest/platformSpecificTenderID

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

properties

content

simple

annotation

documentation

The platform specific ID of the tendering procedure whose messages to subscribe. A Server MUST support this parameter since it used for enrollment of the client

source

<xs:element name="platformSpecificTenderID" type="xvergabe-datatypes:String.4096">
<xs:annotation>
<xs:documentation>The platform specific ID of the tendering procedure whose messages to subscribe. A Server MUST support this parameter since it used for enrollment of the client</xs:documentation>
</xs:annotation>
</xs:element>

complexType msgTypeSubscriptionResponse

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl xvergabe-if-svc:procedure

properties

base	xvergabe-if-svc:AbstractResponse

children

annotation

documentation

A response to a SubscriptionRequest.

source

<xs:complexType name="msgTypeSubscriptionResponse">
<xs:annotation>
    <xs:documentation>A response to a SubscriptionRequest.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if-svc:AbstractResponse">
      <xs:sequence>
        <xs:element name="procedure" minOccurs="0" maxOccurs="unbounded">
          <xs:annotation>
            <xs:documentation>List containing information about the tendering procedures the client has subscribed to.</xs:documentation>
          </xs:annotation>
          <xs:complexType>
            <xs:sequence>
              <xs:element name="tenderID" type="xvergabe-datatypes:GUID">
                <xs:annotation>
                  <xs:documentation>The unique ID of the tendering procedure.</xs:documentation>
                </xs:annotation>
              </xs:element>
              <xs:element name="tenderTitle" type="xvergabe-datatypes:String.1024">
                <xs:annotation>
                  <xs:documentation>The title of the tendering procedure.</xs:documentation>
                </xs:annotation>
              </xs:element>
              <xs:element name="lastMessageID" type="xvergabe-datatypes:GUID">
                <xs:annotation>
                  <xs:documentation>Unique ID of the latest message concerning the tendering procedure that is currently available on the platform for this user.</xs:documentation>
                </xs:annotation>
              </xs:element>
            </xs:sequence>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element msgTypeSubscriptionResponse/procedure

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

properties

minOcc	0
maxOcc	unbounded
content	complex

children

xvergabe-if-svc:tenderID xvergabe-if-svc:tenderTitle xvergabe-if-svc:lastMessageID

annotation

documentation

List containing information about the tendering procedures the client has subscribed to.

source

<xs:element name="procedure" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
    <xs:documentation>List containing information about the tendering procedures the client has subscribed to.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:sequence>
      <xs:element name="tenderID" type="xvergabe-datatypes:GUID">
        <xs:annotation>
          <xs:documentation>The unique ID of the tendering procedure.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="tenderTitle" type="xvergabe-datatypes:String.1024">
        <xs:annotation>
          <xs:documentation>The title of the tendering procedure.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="lastMessageID" type="xvergabe-datatypes:GUID">
        <xs:annotation>
          <xs:documentation>Unique ID of the latest message concerning the tendering procedure that is currently available on the platform for this user.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
</xs:complexType>
</xs:element>

element msgTypeSubscriptionResponse/procedure/tenderID

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

The unique ID of the tendering procedure.

source

<xs:element name="tenderID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>The unique ID of the tendering procedure.</xs:documentation>
</xs:annotation>
</xs:element>

element msgTypeSubscriptionResponse/procedure/tenderTitle

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

properties

content

simple

annotation

documentation

The title of the tendering procedure.

source

<xs:element name="tenderTitle" type="xvergabe-datatypes:String.1024">
<xs:annotation>
<xs:documentation>The title of the tendering procedure.</xs:documentation>
</xs:annotation>
</xs:element>

element msgTypeSubscriptionResponse/procedure/lastMessageID

diagram

namespace

http://xvergabe.org/xsd/client-interface/service/4

type

xvergabe-datatypes:name xvergabe-datatypes:fileSize xvergabe-datatypes:attachmentIdentifier

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

Unique ID of the latest message concerning the tendering procedure that is currently available on the platform for this user.

source

complexType ExistingObjectReference

diagram

namespace

http://xvergabe.org/datatypes/xsd/4/

children

annotation

documentation

Refers to an attachment in an XML file.

source

<xs:complexType name="ExistingObjectReference">
<xs:annotation>
    <xs:documentation>Refers to an attachment in an XML file.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="name" type="xvergabe-datatypes:String.1024" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The name for this reference.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="fileSize" type="xs:nonNegativeInteger">
      <xs:annotation>
        <xs:documentation>The size of the referenced attachment in bytes.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="attachmentIdentifier" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>The GUID of the attachment this ExistingObjectReference refers to. This may be either used in a client message to refer the attachment directly (the attachment is part of the message) or in a server message to reference documents to access by the getDocuments-Operation.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element ExistingObjectReference/name

diagram

namespace

http://xvergabe.org/datatypes/xsd/4/

type

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

The name for this reference.

source

<xs:element name="name" type="xvergabe-datatypes:String.1024" minOccurs="0">
<xs:annotation>
<xs:documentation>The name for this reference.</xs:documentation>
</xs:annotation>
</xs:element>

element ExistingObjectReference/fileSize

diagram

namespace

http://xvergabe.org/datatypes/xsd/4/

type

xs:nonNegativeInteger

properties

content

simple

annotation

documentation

The size of the referenced attachment in bytes.

source

<xs:element name="fileSize" type="xs:nonNegativeInteger">
<xs:annotation>
<xs:documentation>The size of the referenced attachment in bytes.</xs:documentation>
</xs:annotation>
</xs:element>

element ExistingObjectReference/attachmentIdentifier

diagram

namespace

http://xvergabe.org/datatypes/xsd/4/

type

xvergabe-docs:title xvergabe-docs:manifest xvergabe-docs:creationTime

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

The GUID of the attachment this ExistingObjectReference refers to. This may be either used in a client message to refer the attachment directly (the attachment is part of the message) or in a server message to reference documents to access by the getDocuments-Operation.

source

<xs:element name="attachmentIdentifier" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>The GUID of the attachment this ExistingObjectReference refers to. This may be either used in a client message to refer the attachment directly (the attachment is part of the message) or in a server message to reference documents to access by the getDocuments-Operation.</xs:documentation>
</xs:annotation>
</xs:element>

complexType XMLSignature

diagram

namespace

http://xvergabe.org/datatypes/xsd/4/

annotation

appinfo

<implementationHint>MUST contain the type http://www.w3.org/2000/09/xmldsig#Signature. The
signature SHOULD be applied to all elements parallel to the element using this type.
A further technical constraint of this type is not possible due to restrictions of the XÖV model.</implementationHint>

documentation

MUST contain the type http://www.w3.org/2000/09/xmldsig#Signature. The
signature SHOULD be applied to all elements parallel to the element using this type.
A further technical constraint of this type is not possible due to restrictions of the XÖV model.

source

<xs:complexType name="XMLSignature">
<xs:annotation>
    <xs:appinfo>
      <implementationHint>MUST contain the type http://www.w3.org/2000/09/xmldsig#Signature. The
signature SHOULD be applied to all elements parallel to the element using this type.
A further technical constraint of this type is not possible due to restrictions of the XÖV model.</implementationHint>
    </xs:appinfo>
    <xs:documentation>MUST contain the type http://www.w3.org/2000/09/xmldsig#Signature. The
signature SHOULD be applied to all elements parallel to the element using this type.
A further technical constraint of this type is not possible due to restrictions of the XÖV model.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:any namespace="##any" processContents="strict" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>

simpleType DateTimeTZ

namespace

http://xvergabe.org/datatypes/xsd/4/

type

restriction of xs:dateTime

properties

base	xs:dateTime

facets

Kind	Value	Annotation
pattern	([1-9][0-9]{3,}\|0[0-9]{3})-(0[1-9]\|1[0-2])-(0[1-9]\|[12][0-9]\|3[01])T(([01][0-9]\|2[0-3]):[0-5][0-9]:[0-5][0-9](\.[0-9]+)?\|(24:00:00(\.0+)?))(Z\|(\+\|-)((0[0-9]\|1[0-3]):[0-5][0-9]\|14:00))

annotation

documentation

Datatype derived from W3C-simpleType dateTime. Enforces timezone indication in the value.
Timevalue of 24:00:00 represents the end of the day. Timevalue of 00:00:00 represents the beginning of the day.
Values "2015-01-01T24:00:00Z" and "2015-01-02T00:00:00Z" are identical points in time.

source

<xs:simpleType name="DateTimeTZ">
<xs:annotation>
<xs:documentation>Datatype derived from W3C-simpleType dateTime. Enforces timezone indication in the value.
Timevalue of 24:00:00 represents the end of the day. Timevalue of 00:00:00 represents the beginning of the day.
Values "2015-01-01T24:00:00Z" and "2015-01-02T00:00:00Z" are identical points in time.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:dateTime">
<xs:pattern value="([1-9][0-9]{3,}|0[0-9]{3})-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])T(([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9](\.[0-9]+)?|(24:00:00(\.0+)?))(Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00))"/>
</xs:restriction>
</xs:simpleType>

simpleType GUID

namespace

http://xvergabe.org/datatypes/xsd/4/

type

restriction of xs:string

properties

base

xs:string

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

A GUID is a 128 Bit number used as unique identifier for objects. The format and algorithm to create a GUID is defined in RFC 4122. Within the XVergabe specification GUIDs are used as identifiers for objects within the XML structure.

source

<xs:simpleType name="GUID">
<xs:annotation>
<xs:documentation>A GUID is a 128 Bit number used as unique identifier for objects. The format and algorithm to create a GUID is defined in RFC 4122. Within the XVergabe specification GUIDs are used as identifiers for objects within the XML structure.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:pattern value="[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}"/>
</xs:restriction>
</xs:simpleType>

simpleType String.0

namespace

http://xvergabe.org/datatypes/xsd/4/

type

restriction of xs:string

properties

base

xs:string

annotation

documentation

Datatype used for typing empty elements without violating Naming and Design rules. Hence the length of the string is always 0.

source

<xs:simpleType name="String.0">
<xs:annotation>
<xs:documentation>Datatype used for typing empty elements without violating Naming and Design rules. Hence the length of the string is always 0.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:maxLength value="0"/>
</xs:restriction>
</xs:simpleType>

simpleType String.1024

namespace

http://xvergabe.org/datatypes/xsd/4/

type

restriction of xs:string

properties

base

xs:string

annotation

documentation

Extension of the standard string type with a length limit of 1024 characters.

source

<xs:simpleType name="String.1024">
<xs:annotation>
<xs:documentation>Extension of the standard string type with a length limit of 1024 characters.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:maxLength value="1024"/>
</xs:restriction>
</xs:simpleType>

simpleType String.255

namespace

http://xvergabe.org/datatypes/xsd/4/

type

restriction of xs:string

properties

base

xs:string

annotation

documentation

Extension of the standard string type with a length limit of 255 characters.

source

<xs:simpleType name="String.255">
<xs:annotation>
<xs:documentation>Extension of the standard string type with a length limit of 255 characters.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:maxLength value="255"/>
</xs:restriction>
</xs:simpleType>

simpleType String.4096

namespace

http://xvergabe.org/datatypes/xsd/4/

type

restriction of xs:string

properties

base

xs:string

annotation

documentation

Extension of the standard string type with a length limit of 4096 characters.

source

<xs:simpleType name="String.4096">
<xs:annotation>
<xs:documentation>Extension of the standard string type with a length limit of 4096 characters.</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:maxLength value="4096"/>
</xs:restriction>
</xs:simpleType>

element ParticipationContent

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

extension of xvergabe-docs:ContentType

properties

content

complex

children

annotation

documentation

Provides meta information about the files contained in an participation container. This meta data may help software products to process the files correctly. An XML file named "participationcontent.xml" containing an element of this type as root element MUST be included in the PRIMARY participation container (as part of its zip file) to provide additional information for processing software.
The file MAY NOT be part of the SECONDARY participation container. Thus the fileassociation within the manifest MUST be given over the complete set of participationrequest documents (even though not all of them are carried within the primary container necessarily).

In case of a requested container signature, only this file MUST be signed.

source

<xs:element name="ParticipationContent">
<xs:annotation>
    <xs:documentation>Provides meta information about the files contained in an participation container. This meta data may help software products to process the files correctly. An XML file named "participationcontent.xml" containing an element of this type as root element MUST be included in the PRIMARY participation container (as part of its zip file) to provide additional information for processing software.
The file MAY NOT be part of the SECONDARY participation container. Thus the fileassociation within the manifest MUST be given over the complete set of participationrequest documents (even though not all of them are carried within the primary container necessarily).

In case of a requested container signature, only this file MUST be signed.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:complexContent>
      <xs:extension base="xvergabe-docs:ContentType"/>
    </xs:complexContent>
</xs:complexType>
</xs:element>

complexType ContentType

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:title xvergabe-docs:manifest xvergabe-docs:creationTime

annotation

documentation

general Type which defines the shared attributes/elements of OfferContent as well as ParticipationContent.

source

<xs:complexType name="ContentType">
<xs:annotation>
    <xs:documentation>general Type which defines the shared attributes/elements of OfferContent as well as ParticipationContent.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="title" type="xvergabe-datatypes:String.1024">
      <xs:annotation>
        <xs:documentation>title of the offer/participation request given by the economic operator</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="manifest" type="xvergabe-docs:ManifestType">
      <xs:annotation>
        <xs:documentation>a manifest/table of contents of the offer/paritcipationRequest linking the included files to the requested documentreferences within an ITT/ITP.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="creationTime" type="xvergabe-datatypes:DateTimeTZ">
      <xs:annotation>
        <xs:documentation>Timestamp the offercontent.xml/participationcontent.xml file describing the offer/participationRequest was created.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element ContentType/title

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:ManifestType

properties

content

simple

annotation

documentation

title of the offer/participation request given by the economic operator

source

<xs:element name="title" type="xvergabe-datatypes:String.1024">
<xs:annotation>
<xs:documentation>title of the offer/participation request given by the economic operator</xs:documentation>
</xs:annotation>
</xs:element>

element ContentType/manifest

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

complex

children

xvergabe-docs:fileAssociation

annotation

documentation

a manifest/table of contents of the offer/paritcipationRequest linking the included files to the requested documentreferences within an ITT/ITP.

source

<xs:element name="manifest" type="xvergabe-docs:ManifestType">
<xs:annotation>
<xs:documentation>a manifest/table of contents of the offer/paritcipationRequest linking the included files to the requested documentreferences within an ITT/ITP.</xs:documentation>
</xs:annotation>
</xs:element>

element ContentType/creationTime

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:documentID xvergabe-docs:category xvergabe-docs:categorySortIndex xvergabe-docs:displayName xvergabe-docs:processingApplicationURL xvergabe-docs:belongsToPrimaryContainer xvergabe-docs:minimumSignatureLevelDocument xvergabe-docs:document

properties

content

simple

facets

Kind	Value	Annotation
pattern	([1-9][0-9]{3,}\|0[0-9]{3})-(0[1-9]\|1[0-2])-(0[1-9]\|[12][0-9]\|3[01])T(([01][0-9]\|2[0-3]):[0-5][0-9]:[0-5][0-9](\.[0-9]+)?\|(24:00:00(\.0+)?))(Z\|(\+\|-)((0[0-9]\|1[0-3]):[0-5][0-9]\|14:00))

annotation

documentation

Timestamp the offercontent.xml/participationcontent.xml file describing the offer/participationRequest was created.

source

<xs:element name="creationTime" type="xvergabe-datatypes:DateTimeTZ">
<xs:annotation>
<xs:documentation>Timestamp the offercontent.xml/participationcontent.xml file describing the offer/participationRequest was created.</xs:documentation>
</xs:annotation>
</xs:element>

complexType DocumentsPackageContent

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

annotation

documentation

Actual content of the documents package.

source

<xs:complexType name="DocumentsPackageContent">
<xs:annotation>
    <xs:documentation>Actual content of the documents package.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="documentID" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>A unique Identifier for the provided or required document. The id will be used by the Economic Operator in the manifest file within the offer/participation request in order to reference specific files.
When the ITT/ITP is versioned the identifier MUST stay the same for allready existing documents AND for documents which are updated/revised in the new version. For those updated/revised documents provided by the CA to the EO the dateOfPublication has to be different in order to display the version change</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="category" type="xvergabe-datatypes:String.255" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Categoryname of the document given/used by the contracting authority.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="categorySortIndex" type="xs:nonNegativeInteger" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Index used for sorting documents within a category.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="displayName" type="xvergabe-datatypes:String.255">
      <xs:annotation>
        <xs:documentation>The name of the document as it SHOULD be displayed in the client.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="processingApplicationURL" type="xs:anyURI" minOccurs="0">
      <xs:annotation>
        <xs:documentation>If the document needs a special software to be viewed, this URL provides a link to this software (information about obtaining the software).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="belongsToPrimaryContainer" type="xs:boolean" default="true">
      <xs:annotation>
        <xs:documentation>flag indicating that this document when to be returned belongs to the primary offer (resp. participation request) container. the primary container shall include all documents which are relevant for the opening where the secondary container shall include further attachments or documents which are added to the offer/participation request by the economic operator (not demanded by ITT or ITP).
however, if electronicalSubmission/onlyPrimaryContainerAllowed is set to true, this value here is overruled since all documents must be part of the primaryContainer.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="minimumSignatureLevelDocument" type="xvergabe-cl:Code.SignatureLevelType">
      <xs:annotation>
        <xs:documentation>The expected minimum level of signature certificates used for signature of the document to be returned in the participation/offer container. A value of NONE means not to sign the file at all. All other values imply a signature over the document to be returned in the container.
This is purely for informational purposes. A Client (and/or its user) may decide to sign otherwise (or not at all). The decision about the legal implications/acceptance of the participation request is up to the Contracting Authority.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="document" type="xvergabe-docs:DocumentsPackageContentDocument">
      <xs:annotation>
        <xs:documentation>The actual document.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element DocumentsPackageContent/documentID

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

A unique Identifier for the provided or required document. The id will be used by the Economic Operator in the manifest file within the offer/participation request in order to reference specific files.
When the ITT/ITP is versioned the identifier MUST stay the same for allready existing documents AND for documents which are updated/revised in the new version. For those updated/revised documents provided by the CA to the EO the dateOfPublication has to be different in order to display the version change

source

<xs:element name="documentID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>A unique Identifier for the provided or required document. The id will be used by the Economic Operator in the manifest file within the offer/participation request in order to reference specific files.
When the ITT/ITP is versioned the identifier MUST stay the same for allready existing documents AND for documents which are updated/revised in the new version. For those updated/revised documents provided by the CA to the EO the dateOfPublication has to be different in order to display the version change</xs:documentation>
</xs:annotation>
</xs:element>

element DocumentsPackageContent/category

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

Categoryname of the document given/used by the contracting authority.

source

<xs:element name="category" type="xvergabe-datatypes:String.255" minOccurs="0">
<xs:annotation>
<xs:documentation>Categoryname of the document given/used by the contracting authority.</xs:documentation>
</xs:annotation>
</xs:element>

element DocumentsPackageContent/categorySortIndex

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:nonNegativeInteger

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

Index used for sorting documents within a category.

source

<xs:element name="categorySortIndex" type="xs:nonNegativeInteger" minOccurs="0">
<xs:annotation>
<xs:documentation>Index used for sorting documents within a category.</xs:documentation>
</xs:annotation>
</xs:element>

element DocumentsPackageContent/displayName

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

simple

annotation

documentation

The name of the document as it SHOULD be displayed in the client.

source

<xs:element name="displayName" type="xvergabe-datatypes:String.255">
<xs:annotation>
<xs:documentation>The name of the document as it SHOULD be displayed in the client.</xs:documentation>
</xs:annotation>
</xs:element>

element DocumentsPackageContent/processingApplicationURL

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:anyURI

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

If the document needs a special software to be viewed, this URL provides a link to this software (information about obtaining the software).

source

<xs:element name="processingApplicationURL" type="xs:anyURI" minOccurs="0">
<xs:annotation>
<xs:documentation>If the document needs a special software to be viewed, this URL provides a link to this software (information about obtaining the software).</xs:documentation>
</xs:annotation>
</xs:element>

element DocumentsPackageContent/belongsToPrimaryContainer

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:boolean

properties

content	simple
default	true

annotation

documentation

flag indicating that this document when to be returned belongs to the primary offer (resp. participation request) container. the primary container shall include all documents which are relevant for the opening where the secondary container shall include further attachments or documents which are added to the offer/participation request by the economic operator (not demanded by ITT or ITP).
however, if electronicalSubmission/onlyPrimaryContainerAllowed is set to true, this value here is overruled since all documents must be part of the primaryContainer.

source

<xs:element name="belongsToPrimaryContainer" type="xs:boolean" default="true">
<xs:annotation>
<xs:documentation>flag indicating that this document when to be returned belongs to the primary offer (resp. participation request) container. the primary container shall include all documents which are relevant for the opening where the secondary container shall include further attachments or documents which are added to the offer/participation request by the economic operator (not demanded by ITT or ITP).
however, if electronicalSubmission/onlyPrimaryContainerAllowed is set to true, this value here is overruled since all documents must be part of the primaryContainer.</xs:documentation>
</xs:annotation>
</xs:element>

element DocumentsPackageContent/minimumSignatureLevelDocument

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

complex

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:signatureLevelType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.

xvergabe-docs:DocumentsPackageContentDocument

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

Die konkrete Version der zu nutzenden Codeliste wird mit diesem XML-Attribut übertragen.

Analog zum listURI ist die Bestimmung der Version einer Codeliste bei der Übertragung eines Codes zwingend. Die Version kann jedoch ebenfalls bereits im XÖV-Standard festgelegt werden (es handelt sich in diesem Fall um einen Code-Typ 1 oder 2).

annotation

documentation

The expected minimum level of signature certificates used for signature of the document to be returned in the participation/offer container. A value of NONE means not to sign the file at all. All other values imply a signature over the document to be returned in the container.
This is purely for informational purposes. A Client (and/or its user) may decide to sign otherwise (or not at all). The decision about the legal implications/acceptance of the participation request is up to the Contracting Authority.

source

<xs:element name="minimumSignatureLevelDocument" type="xvergabe-cl:Code.SignatureLevelType">
<xs:annotation>
<xs:documentation>The expected minimum level of signature certificates used for signature of the document to be returned in the participation/offer container. A value of NONE means not to sign the file at all. All other values imply a signature over the document to be returned in the container.
This is purely for informational purposes. A Client (and/or its user) may decide to sign otherwise (or not at all). The decision about the legal implications/acceptance of the participation request is up to the Contracting Authority.</xs:documentation>
</xs:annotation>
</xs:element>

element DocumentsPackageContent/document

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

complex

children

xvergabe-docs:providedDocument xvergabe-docs:requiredDocument

annotation

documentation

The actual document.

source

<xs:element name="document" type="xvergabe-docs:DocumentsPackageContentDocument">
<xs:annotation>
<xs:documentation>The actual document.</xs:documentation>
</xs:annotation>
</xs:element>

complexType DocumentsPackageContentDocument

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:providedDocument xvergabe-docs:requiredDocument

annotation

documentation

Contains information about a single document that is part of a DocumentsPackageContent. this i merely a choice if the document is provided by the contracting authority or if the economic operator is asked by the contracting authority to submit the document as part of the tender/particaption request (so called requested document).

source

<xs:complexType name="DocumentsPackageContentDocument">
<xs:annotation>
    <xs:documentation>Contains information about a single document that is part of a DocumentsPackageContent. this i merely a choice if the document is provided by the contracting authority or if the economic operator is asked by the contracting authority to submit the document as part of the tender/particaption request (so called requested document).</xs:documentation>
</xs:annotation>
<xs:choice>
    <xs:element name="providedDocument" type="xvergabe-docs:DocumentsPackageContentProvidedDocument">
      <xs:annotation>
        <xs:documentation>Information about the provided document. A document which is provided by the contracting Authority and which MIGHT need to be returned as part of the offer/participation request of and by the economic operator.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="requiredDocument" type="xvergabe-docs:DocumentsPackageContentRequiredDocument">
      <xs:annotation>
        <xs:documentation>Information about a document an economic operated is requested to include as part of his/her offer or participation request.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:choice>
</xs:complexType>

element DocumentsPackageContentDocument/providedDocument

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:DocumentsPackageContentProvidedDocument

properties

content

complex

children

xvergabe-datatypes:name xvergabe-datatypes:fileSize xvergabe-datatypes:attachmentIdentifier xvergabe-docs:dateOfPublication xvergabe-docs:mustBeReturned xvergabe-docs:applyTransformation

annotation

documentation

Information about the provided document. A document which is provided by the contracting Authority and which MIGHT need to be returned as part of the offer/participation request of and by the economic operator.

source

<xs:element name="providedDocument" type="xvergabe-docs:DocumentsPackageContentProvidedDocument">
<xs:annotation>
<xs:documentation>Information about the provided document. A document which is provided by the contracting Authority and which MIGHT need to be returned as part of the offer/participation request of and by the economic operator.</xs:documentation>
</xs:annotation>
</xs:element>

element DocumentsPackageContentDocument/requiredDocument

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:DocumentsPackageContentRequiredDocument

properties

content

complex

children

xvergabe-docs:name xvergabe-docs:description

annotation

documentation

Information about a document an economic operated is requested to include as part of his/her offer or participation request.

source

<xs:element name="requiredDocument" type="xvergabe-docs:DocumentsPackageContentRequiredDocument">
<xs:annotation>
<xs:documentation>Information about a document an economic operated is requested to include as part of his/her offer or participation request.</xs:documentation>
</xs:annotation>
</xs:element>

complexType DocumentsPackageContentProvidedDocument

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

extension of xvergabe-datatypes:ExistingObjectReference

properties

base	xvergabe-datatypes:ExistingObjectReference

children

xvergabe-datatypes:name xvergabe-datatypes:fileSize xvergabe-datatypes:attachmentIdentifier xvergabe-docs:dateOfPublication xvergabe-docs:mustBeReturned xvergabe-docs:applyTransformation

annotation

documentation

A provided document is a document that the contracting authority provides and which MIGHT needs to be filled out by the economic operator and returned to the contracting authority as part of an offer / participation request.
thus the document itself MAY NOT be part of the ITT/ITP message itself but it MUST be available as a separate document/attachment via the getDocument()-operation.

source

<xs:complexType name="DocumentsPackageContentProvidedDocument">
<xs:annotation>
    <xs:documentation>A provided document is a document that the contracting authority provides and which MIGHT needs to be filled out by the economic operator and returned to the contracting authority as part of an offer / participation request.
thus the document itself MAY NOT be part of the ITT/ITP message itself but it MUST be available as a separate document/attachment via the getDocument()-operation.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-datatypes:ExistingObjectReference">
      <xs:sequence>
        <xs:element name="dateOfPublication" type="xvergabe-datatypes:DateTimeTZ">
          <xs:annotation>
            <xs:documentation>timestamp at which a document has been made available</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="mustBeReturned" type="xs:boolean" default="true">
          <xs:annotation>
            <xs:documentation>indicator that the referenced document has to be returned by the Economic Operator within the offer/participation request (most likely after processing and filling out the document)</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="applyTransformation" type="xvergabe-docs:TransformationDetails" minOccurs="0">
          <xs:annotation>
            <xs:documentation>If the document has to be transformed to be part of the offer / participation request, the information needed for the transformation SHALL be supplied here.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element DocumentsPackageContentProvidedDocument/dateOfPublication

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:TransformationDetails

properties

content

simple

facets

Kind	Value	Annotation
pattern	([1-9][0-9]{3,}\|0[0-9]{3})-(0[1-9]\|1[0-2])-(0[1-9]\|[12][0-9]\|3[01])T(([01][0-9]\|2[0-3]):[0-5][0-9]:[0-5][0-9](\.[0-9]+)?\|(24:00:00(\.0+)?))(Z\|(\+\|-)((0[0-9]\|1[0-3]):[0-5][0-9]\|14:00))

annotation

documentation

timestamp at which a document has been made available

source

<xs:element name="dateOfPublication" type="xvergabe-datatypes:DateTimeTZ">
<xs:annotation>
<xs:documentation>timestamp at which a document has been made available</xs:documentation>
</xs:annotation>
</xs:element>

element DocumentsPackageContentProvidedDocument/mustBeReturned

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:boolean

properties

content	simple
default	true

annotation

documentation

indicator that the referenced document has to be returned by the Economic Operator within the offer/participation request (most likely after processing and filling out the document)

source

<xs:element name="mustBeReturned" type="xs:boolean" default="true">
<xs:annotation>
<xs:documentation>indicator that the referenced document has to be returned by the Economic Operator within the offer/participation request (most likely after processing and filling out the document)</xs:documentation>
</xs:annotation>
</xs:element>

element DocumentsPackageContentProvidedDocument/applyTransformation

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

minOcc	0
maxOcc	1
content	complex

children

xvergabe-docs:targetFilename xvergabe-docs:targetExtension xvergabe-docs:targetMiMEType xvergabe-docs:targetProcessingApplicationURL

annotation

documentation

If the document has to be transformed to be part of the offer / participation request, the information needed for the transformation SHALL be supplied here.

source

<xs:element name="applyTransformation" type="xvergabe-docs:TransformationDetails" minOccurs="0">
<xs:annotation>
<xs:documentation>If the document has to be transformed to be part of the offer / participation request, the information needed for the transformation SHALL be supplied here.</xs:documentation>
</xs:annotation>
</xs:element>

complexType DocumentsPackageContentRequiredDocument

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:name xvergabe-docs:description

annotation

documentation

A required document is a placeholder for a document that the bidder is required to deliver, but which the bidder creates himself.

source

<xs:complexType name="DocumentsPackageContentRequiredDocument">
<xs:annotation>
    <xs:documentation>A required document is a placeholder for a document that the bidder is required to deliver, but which the bidder creates himself.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="name" type="xvergabe-datatypes:String.255">
      <xs:annotation>
        <xs:documentation>The expected file name of the document when submitting an offer / participation request.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="description" type="xvergabe-datatypes:String.1024">
      <xs:annotation>
        <xs:documentation>Description of the document the bidder has to deliver.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element DocumentsPackageContentRequiredDocument/name

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

simple

annotation

documentation

The expected file name of the document when submitting an offer / participation request.

source

<xs:element name="name" type="xvergabe-datatypes:String.255">
<xs:annotation>
<xs:documentation>The expected file name of the document when submitting an offer / participation request.</xs:documentation>
</xs:annotation>
</xs:element>

element DocumentsPackageContentRequiredDocument/description

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:credentialID xvergabe-docs:encryptionOrder

properties

content

simple

annotation

documentation

Description of the document the bidder has to deliver.

source

<xs:element name="description" type="xvergabe-datatypes:String.1024">
<xs:annotation>
<xs:documentation>Description of the document the bidder has to deliver.</xs:documentation>
</xs:annotation>
</xs:element>

complexType EncryptionKeyDetails

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

annotation

documentation

Information about the key used for encrypting offers and participation requests. It is possible to specify more than one key for a multiple encryption.

source

<xs:complexType name="EncryptionKeyDetails">
<xs:annotation>
    <xs:documentation>Information about the key used for encrypting offers and participation requests. It is possible to specify more than one key for a multiple encryption.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="credentialID" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>Reference to the unique ID of the CredentialItem that contains the public key to use for encryption.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="encryptionOrder" type="xs:nonNegativeInteger" minOccurs="0">
      <xs:annotation>
        <xs:documentation>If more than one key is specified, the order in which to use these keys while encrypted is specified by this field.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element EncryptionKeyDetails/credentialID

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:filename xvergabe-docs:documentID xvergabe-docs:hashValue

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

Reference to the unique ID of the CredentialItem that contains the public key to use for encryption.

source

<xs:element name="credentialID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>Reference to the unique ID of the CredentialItem that contains the public key to use for encryption.</xs:documentation>
</xs:annotation>
</xs:element>

element EncryptionKeyDetails/encryptionOrder

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:nonNegativeInteger

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

If more than one key is specified, the order in which to use these keys while encrypted is specified by this field.

source

<xs:element name="encryptionOrder" type="xs:nonNegativeInteger" minOccurs="0">
<xs:annotation>
<xs:documentation>If more than one key is specified, the order in which to use these keys while encrypted is specified by this field.</xs:documentation>
</xs:annotation>
</xs:element>

complexType FileAssociationType

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

annotation

documentation

mapping between files and the documentID supplied within the ITP/ITT.

source

<xs:complexType name="FileAssociationType">
<xs:annotation>
    <xs:documentation>mapping between files and the documentID supplied within the ITP/ITT.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="filename" type="xvergabe-datatypes:String.255">
      <xs:annotation>
        <xs:documentation>The name of the file within the archive.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="documentID" type="xvergabe-datatypes:GUID" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>The documentID that was specified in an ITT/ITP for the provided/requested document. When the document was not requested nor provided but supplied additionally by the economic operator the documentID MUST not be given.
One physical document MAY reference more than one documentIDs (provided/requested document) at the same time.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="hashValue" type="xs:hexBinary">
      <xs:annotation>
        <xs:documentation>the SHA512-hashvalue built over the file.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element FileAssociationType/filename

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

simple

annotation

documentation

The name of the file within the archive.

source

<xs:element name="filename" type="xvergabe-datatypes:String.255">
<xs:annotation>
<xs:documentation>The name of the file within the archive.</xs:documentation>
</xs:annotation>
</xs:element>

element FileAssociationType/documentID

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:subject xvergabe-docs:inquiryBody xvergabe-docs:documentReference xvergabe-docs:lotReference

properties

minOcc	0
maxOcc	unbounded
content	simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

The documentID that was specified in an ITT/ITP for the provided/requested document. When the document was not requested nor provided but supplied additionally by the economic operator the documentID MUST not be given.
One physical document MAY reference more than one documentIDs (provided/requested document) at the same time.

source

<xs:element name="documentID" type="xvergabe-datatypes:GUID" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>The documentID that was specified in an ITT/ITP for the provided/requested document. When the document was not requested nor provided but supplied additionally by the economic operator the documentID MUST not be given.
One physical document MAY reference more than one documentIDs (provided/requested document) at the same time.</xs:documentation>
</xs:annotation>
</xs:element>

element FileAssociationType/hashValue

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:hexBinary

properties

content

simple

annotation

documentation

the SHA512-hashvalue built over the file.

source

<xs:element name="hashValue" type="xs:hexBinary">
<xs:annotation>
<xs:documentation>the SHA512-hashvalue built over the file.</xs:documentation>
</xs:annotation>
</xs:element>

complexType Inquiry

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

annotation

documentation

The actual textual content of an Inquiry document. If the text is an answer to a previously exchanged question, the question SHOULD be repeated in this text.

source

<xs:complexType name="Inquiry">
<xs:annotation>
    <xs:documentation>The actual textual content of an Inquiry document. If the text is an answer to a previously exchanged question, the question SHOULD be repeated in this text.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="subject" type="xvergabe-datatypes:String.255">
      <xs:annotation>
        <xs:documentation>The subject of the inquiry.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="inquiryBody" type="xvergabe-datatypes:String.4096">
      <xs:annotation>
        <xs:documentation>The actual content of the inquiry.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="documentReference" type="xvergabe-datatypes:ExistingObjectReference" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>optional references to attachments belonging to the inquiry.
In case of a client inquiry (meaning the inquiry is sent by the client to the server) the referenced attachments MUST be carried within the ClientInquiry-Message.
In case of a server inquiry (meaning the inquiry is sent by the server to the client) the referenced attachments MAY NOT be carried within the ServerInquiry-Message but MUST be made available as separate documents through the getDocument-operation.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="lotReference" type="xvergabe-datatypes:GUID" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>optional References to lot(s) the inquiry is about.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element Inquiry/subject

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

simple

annotation

documentation

The subject of the inquiry.

source

<xs:element name="subject" type="xvergabe-datatypes:String.255">
<xs:annotation>
<xs:documentation>The subject of the inquiry.</xs:documentation>
</xs:annotation>
</xs:element>

element Inquiry/inquiryBody

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

simple

annotation

documentation

The actual content of the inquiry.

source

<xs:element name="inquiryBody" type="xvergabe-datatypes:String.4096">
<xs:annotation>
<xs:documentation>The actual content of the inquiry.</xs:documentation>
</xs:annotation>
</xs:element>

element Inquiry/documentReference

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-datatypes:name xvergabe-datatypes:fileSize xvergabe-datatypes:attachmentIdentifier

properties

minOcc	0
maxOcc	unbounded
content	complex

children

annotation

documentation

optional references to attachments belonging to the inquiry.
In case of a client inquiry (meaning the inquiry is sent by the client to the server) the referenced attachments MUST be carried within the ClientInquiry-Message.
In case of a server inquiry (meaning the inquiry is sent by the server to the client) the referenced attachments MAY NOT be carried within the ServerInquiry-Message but MUST be made available as separate documents through the getDocument-operation.

source

<xs:element name="documentReference" type="xvergabe-datatypes:ExistingObjectReference" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>optional references to attachments belonging to the inquiry.
In case of a client inquiry (meaning the inquiry is sent by the client to the server) the referenced attachments MUST be carried within the ClientInquiry-Message.
In case of a server inquiry (meaning the inquiry is sent by the server to the client) the referenced attachments MAY NOT be carried within the ServerInquiry-Message but MUST be made available as separate documents through the getDocument-operation.</xs:documentation>
</xs:annotation>
</xs:element>

element Inquiry/lotReference

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

minOcc	0
maxOcc	unbounded
content	simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

optional References to lot(s) the inquiry is about.

source

<xs:element name="lotReference" type="xvergabe-datatypes:GUID" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>optional References to lot(s) the inquiry is about.</xs:documentation>
</xs:annotation>
</xs:element>

complexType InquiryDocumentType

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:subject xvergabe-docs:inquiryBody xvergabe-docs:documentReference xvergabe-docs:lotReference

annotation

documentation

An InquiryDocument serves as vessel for general inquiries and answers that can be sent from client to server and vice versa. An inquiry can reference a previously exchanged document.

source

<xs:complexType name="InquiryDocumentType">
<xs:annotation>
    <xs:documentation>An InquiryDocument serves as vessel for general inquiries and answers that can be sent from client to server and vice versa. An inquiry can reference a previously exchanged document.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="inquiry" type="xvergabe-docs:Inquiry">
      <xs:annotation>
        <xs:documentation>The actual inquiry document.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element InquiryDocumentType/inquiry

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:Inquiry

properties

content

complex

children

annotation

documentation

The actual inquiry document.

source

<xs:element name="inquiry" type="xvergabe-docs:Inquiry">
<xs:annotation>
<xs:documentation>The actual inquiry document.</xs:documentation>
</xs:annotation>
</xs:element>

complexType InvitationToParticipationDocumentType

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:submissionDetails xvergabe-docs:participationDocument

annotation

documentation

An InvitationToParticipation contains the documents and meta data needed for bidder to be able to submit a request to participate in a tendering procedure with participation contest. The participation documents are not included directly in this document but instead their GUIDs are referenced, so that a client can call the getDocument operation to download these documents.
An InvitationToParticipation can be sent to the same client multiple times if the participation documents change. Each InvitationToParticipation SHOULD then contain a FULL set of the participation documents. A client can determine which tendering documents he still has to download by comparing the GUIDs of the referenced documents.

source

<xs:complexType name="InvitationToParticipationDocumentType">
<xs:annotation>
    <xs:documentation>An InvitationToParticipation contains the documents and meta data needed for bidder to be able to submit a request to participate in a tendering procedure with participation contest. The participation documents are not included directly in this document but instead their GUIDs are referenced, so that a client can call the getDocument operation to download these documents.
An InvitationToParticipation can be sent to the same client multiple times if the participation documents change. Each InvitationToParticipation SHOULD then contain a FULL set of the participation documents. A client can determine which tendering documents he still has to download by comparing the GUIDs of the referenced documents.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="submissionDetails" type="xvergabe-docs:ParticipationSubmissionDetails">
      <xs:annotation>
        <xs:documentation>Contains information enabling a bidder to submit a participation request.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="participationDocument" type="xvergabe-docs:DocumentsPackageContent" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>the documents provided or requested by the Contracting Authority from the Economic Operator for the participation request.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element InvitationToParticipationDocumentType/submissionDetails

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:ParticipationSubmissionDetails

properties

content

complex

children

xvergabe-docs:postalSubmission xvergabe-docs:electronicalSubmission

annotation

documentation

Contains information enabling a bidder to submit a participation request.

source

<xs:element name="submissionDetails" type="xvergabe-docs:ParticipationSubmissionDetails">
<xs:annotation>
<xs:documentation>Contains information enabling a bidder to submit a participation request.</xs:documentation>
</xs:annotation>
</xs:element>

element InvitationToParticipationDocumentType/participationDocument

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:DocumentsPackageContent

properties

minOcc	0
maxOcc	unbounded
content	complex

children

annotation

documentation

the documents provided or requested by the Contracting Authority from the Economic Operator for the participation request.

source

<xs:element name="participationDocument" type="xvergabe-docs:DocumentsPackageContent" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>the documents provided or requested by the Contracting Authority from the Economic Operator for the participation request.</xs:documentation>
</xs:annotation>
</xs:element>

complexType InvitationToTenderDocumentType

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:lot xvergabe-docs:negotiationRound xvergabe-docs:tenderSubmissionDetails xvergabe-docs:tenderDocument

annotation

documentation

source

<xs:complexType name="InvitationToTenderDocumentType">
<xs:annotation>
    <xs:documentation>An InvitationToTender contains the tendering documents necessary for a bidder to submit an offer to a tendering procedure. The tendering documents are not included directly in this document but instead their GUIDs are referenced, so that a client can call the getDocument operation to download these documents. The tendering documents are divided in documents that must be returned as part of an offer, documents that must be transformed and returned as part of an offer and documents that the bidder provides without being explicitly requested to do so.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="lot" type="xvergabe-datatypes:GUID" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>References to lot(s) (given in the TMI) the ITT and tender documents are about.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="negotiationRound" type="xs:positiveInteger" minOccurs="0">
      <xs:annotation>
        <xs:documentation>information about the negotiationround the ITT/tender documents are meant for.
Only applicable if procedureTyp = NEGOTIATED_PROCEDURE or NEGOTIATED_PROCEDURE_WITH_PARTICIPATION_CONTEST.
This is a counter increased with each negotiation round. A client SHALL compare this value against the negotiationround-counter within the TMI for the procedure (or lot if applicable). If the negotiation round counter in the TMI differs from this value (is higher), than the client SHALL refrain from creating an offer.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="tenderSubmissionDetails" type="xvergabe-docs:TenderSubmissionDetails"/>
    <xs:element name="tenderDocument" type="xvergabe-docs:DocumentsPackageContent" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>

element InvitationToTenderDocumentType/lot

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:TenderSubmissionDetails

properties

minOcc	0
maxOcc	unbounded
content	simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

References to lot(s) (given in the TMI) the ITT and tender documents are about.

source

<xs:element name="lot" type="xvergabe-datatypes:GUID" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>References to lot(s) (given in the TMI) the ITT and tender documents are about.</xs:documentation>
</xs:annotation>
</xs:element>

element InvitationToTenderDocumentType/negotiationRound

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:positiveInteger

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

information about the negotiationround the ITT/tender documents are meant for.
Only applicable if procedureTyp = NEGOTIATED_PROCEDURE or NEGOTIATED_PROCEDURE_WITH_PARTICIPATION_CONTEST.
This is a counter increased with each negotiation round. A client SHALL compare this value against the negotiationround-counter within the TMI for the procedure (or lot if applicable). If the negotiation round counter in the TMI differs from this value (is higher), than the client SHALL refrain from creating an offer.

source

<xs:element name="negotiationRound" type="xs:positiveInteger" minOccurs="0">
<xs:annotation>
<xs:documentation>information about the negotiationround the ITT/tender documents are meant for.
Only applicable if procedureTyp = NEGOTIATED_PROCEDURE or NEGOTIATED_PROCEDURE_WITH_PARTICIPATION_CONTEST.
This is a counter increased with each negotiation round. A client SHALL compare this value against the negotiationround-counter within the TMI for the procedure (or lot if applicable). If the negotiation round counter in the TMI differs from this value (is higher), than the client SHALL refrain from creating an offer.</xs:documentation>
</xs:annotation>
</xs:element>

element InvitationToTenderDocumentType/tenderSubmissionDetails

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

complex

children

xvergabe-docs:submissionOfAlternativeTendersAccepted xvergabe-docs:postalSubmission xvergabe-docs:electronicalSubmission

source

<xs:element name="tenderSubmissionDetails" type="xvergabe-docs:TenderSubmissionDetails"/>

element InvitationToTenderDocumentType/tenderDocument

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:DocumentsPackageContent

properties

minOcc	0
maxOcc	unbounded
content	complex

children

source

<xs:element name="tenderDocument" type="xvergabe-docs:DocumentsPackageContent" minOccurs="0" maxOccurs="unbounded"/>

complexType LotOverview

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:lotID xvergabe-docs:lotName xvergabe-docs:lotNumber xvergabe-docs:lotStatus xvergabe-docs:lotTimeLimit xvergabe-docs:lotNegotiationRoundCounter

annotation

documentation

Information about the lots of the tendering procedure.

source

<xs:complexType name="LotOverview">
<xs:annotation>
    <xs:documentation>Information about the lots of the tendering procedure.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="lotID" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>Unique identifier of the lot.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="lotName" type="xvergabe-datatypes:String.1024" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Name of the lot.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="lotNumber" type="xvergabe-datatypes:String.255" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Sequential number of the lot, unique for the tendering procedure, starting with 1.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="lotStatus" type="xvergabe-cl:Code.StatusType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The current status of the specific lot within tendering procedure. this is most likely only applicable when the lots are being negotiated seperatly within a negotiated procedure and/or the lots have lot-specific time limits.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="lotTimeLimit" type="xvergabe-docs:TimeLimitType" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>lot specific time limits. May differ from each other within the same procedure. Lot specific time limits override procedure wide time limits.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="lotNegotiationRoundCounter" type="xs:positiveInteger" minOccurs="0">
      <xs:annotation>
        <xs:documentation>information about the lotspecific negotiationround. Only applicable if procedureTyp = NEGOTIATED_PROCEDURE or NEGOTIATED_PROCEDURE_WITH_PARTICIPATION_CONTEST AND the negotiation rounds/timelimits are lot specific.
This is a counter increased with each negotiation round within this lot. A client SHALL compare this value against the negotiationround-counter within the appropriate ITT for this lot. If the client has no ITT for this lots negotiation round he SHALL refrain from creating an offer.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element LotOverview/lotID

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

Unique identifier of the lot.

source

<xs:element name="lotID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>Unique identifier of the lot.</xs:documentation>
</xs:annotation>
</xs:element>

element LotOverview/lotName

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

Name of the lot.

source

<xs:element name="lotName" type="xvergabe-datatypes:String.1024" minOccurs="0">
<xs:annotation>
<xs:documentation>Name of the lot.</xs:documentation>
</xs:annotation>
</xs:element>

element LotOverview/lotNumber

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-cl:Code.StatusType

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

Sequential number of the lot, unique for the tendering procedure, starting with 1.

source

<xs:element name="lotNumber" type="xvergabe-datatypes:String.255" minOccurs="0">
<xs:annotation>
<xs:documentation>Sequential number of the lot, unique for the tendering procedure, starting with 1.</xs:documentation>
</xs:annotation>
</xs:element>

element LotOverview/lotStatus

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

minOcc	0
maxOcc	1
content	complex

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:statusType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xvergabe-docs:TimeLimitType

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

The current status of the specific lot within tendering procedure. this is most likely only applicable when the lots are being negotiated seperatly within a negotiated procedure and/or the lots have lot-specific time limits.

source

<xs:element name="lotStatus" type="xvergabe-cl:Code.StatusType" minOccurs="0">
<xs:annotation>
<xs:documentation>The current status of the specific lot within tendering procedure. this is most likely only applicable when the lots are being negotiated seperatly within a negotiated procedure and/or the lots have lot-specific time limits.</xs:documentation>
</xs:annotation>
</xs:element>

element LotOverview/lotTimeLimit

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

minOcc	0
maxOcc	unbounded
content	complex

children

xvergabe-docs:timeLimitType xvergabe-docs:timeLimit

annotation

documentation

lot specific time limits. May differ from each other within the same procedure. Lot specific time limits override procedure wide time limits.

source

<xs:element name="lotTimeLimit" type="xvergabe-docs:TimeLimitType" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>lot specific time limits. May differ from each other within the same procedure. Lot specific time limits override procedure wide time limits.</xs:documentation>
</xs:annotation>
</xs:element>

element LotOverview/lotNegotiationRoundCounter

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:positiveInteger

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

information about the lotspecific negotiationround. Only applicable if procedureTyp = NEGOTIATED_PROCEDURE or NEGOTIATED_PROCEDURE_WITH_PARTICIPATION_CONTEST AND the negotiation rounds/timelimits are lot specific.
This is a counter increased with each negotiation round within this lot. A client SHALL compare this value against the negotiationround-counter within the appropriate ITT for this lot. If the client has no ITT for this lots negotiation round he SHALL refrain from creating an offer.

source

<xs:element name="lotNegotiationRoundCounter" type="xs:positiveInteger" minOccurs="0">
<xs:annotation>
<xs:documentation>information about the lotspecific negotiationround. Only applicable if procedureTyp = NEGOTIATED_PROCEDURE or NEGOTIATED_PROCEDURE_WITH_PARTICIPATION_CONTEST AND the negotiation rounds/timelimits are lot specific.
This is a counter increased with each negotiation round within this lot. A client SHALL compare this value against the negotiationround-counter within the appropriate ITT for this lot. If the client has no ITT for this lots negotiation round he SHALL refrain from creating an offer.</xs:documentation>
</xs:annotation>
</xs:element>

complexType ManifestType

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:fileAssociation

annotation

documentation

the manifest/table of contents of the offer/participation request.

source

<xs:complexType name="ManifestType">
<xs:annotation>
    <xs:documentation>the manifest/table of contents of the offer/participation request.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="fileAssociation" type="xvergabe-docs:FileAssociationType" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>list of files of the offer/participationrequest linked to the document reference</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element ManifestType/fileAssociation

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:FileAssociationType

properties

minOcc	0
maxOcc	unbounded
content	complex

children

xvergabe-docs:filename xvergabe-docs:documentID xvergabe-docs:hashValue

annotation

documentation

list of files of the offer/participationrequest linked to the document reference

source

<xs:element name="fileAssociation" type="xvergabe-docs:FileAssociationType" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>list of files of the offer/participationrequest linked to the document reference</xs:documentation>
</xs:annotation>
</xs:element>

complexType OfferContentType

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

extension of xvergabe-docs:ContentType

properties

base	xvergabe-docs:ContentType

children

xvergabe-docs:title xvergabe-docs:manifest xvergabe-docs:creationTime xvergabe-docs:isMainOffer xvergabe-docs:accordingLot

annotation

documentation

Provides meta information about the files contained in an offer container. This meta data may help software products to process the files correctly. An XML file named "offercontent.xml" containing an element of this type as root MUST be included in EACH offer container (as part of its zip file) to provide additional information for processing software.

source

<xs:complexType name="OfferContentType">
<xs:annotation>
    <xs:documentation>Provides meta information about the files contained in an offer container. This meta data may help software products to process the files correctly. An XML file named "offercontent.xml" containing an element of this type as root MUST be included in EACH offer container (as part of its zip file) to provide additional information for processing software.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-docs:ContentType">
      <xs:sequence>
        <xs:element name="isMainOffer" type="xs:boolean" default="true">
          <xs:annotation>
            <xs:documentation>indicator whether the offer is the main offer or an alternative one.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="accordingLot" type="xvergabe-datatypes:GUID" minOccurs="0" maxOccurs="unbounded">
          <xs:annotation>
            <xs:documentation>Specifies the ID of the lot(s) that the archive (offer) described by this OfferContent relates to. MUST reference lot-GUIDs that were previously communicated by the server within TMIs.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element OfferContentType/isMainOffer

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:boolean

properties

content	simple
default	true

annotation

documentation

indicator whether the offer is the main offer or an alternative one.

source

<xs:element name="isMainOffer" type="xs:boolean" default="true">
<xs:annotation>
<xs:documentation>indicator whether the offer is the main offer or an alternative one.</xs:documentation>
</xs:annotation>
</xs:element>

element OfferContentType/accordingLot

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:OK xvergabe-docs:WARNING xvergabe-docs:ERROR xvergabe-docs:responseInformation xvergabe-docs:processedOfferDetails xvergabe-docs:platformSpecificReceipt xvergabe-docs:platformSpecificReceiptReport

properties

minOcc	0
maxOcc	unbounded
content	simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

Specifies the ID of the lot(s) that the archive (offer) described by this OfferContent relates to. MUST reference lot-GUIDs that were previously communicated by the server within TMIs.

source

<xs:element name="accordingLot" type="xvergabe-datatypes:GUID" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>Specifies the ID of the lot(s) that the archive (offer) described by this OfferContent relates to. MUST reference lot-GUIDs that were previously communicated by the server within TMIs.</xs:documentation>
</xs:annotation>
</xs:element>

complexType OfferDeliveryReceiptDocumentType

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

extension of xvergabe-docs:ResponseDocumentType

properties

base	xvergabe-docs:ResponseDocumentType

children

annotation

documentation

An OfferDeliveryReceipt is a receipt that is sent from server to client after the client has submitted an offer. This receipt confirms the successful processing of the offer. The receipt repeats the processing details given by the client and enriches them with the ID the server assigned to the offer.
The receipt includes the Response-Informations given in the messagecontext for delivery of said information in other contexts. So when the DeliveryReceipt is to be exchanged synchronously it MUST include the same Responseinformations twice: once on the messagelevel and once again in the document level.

source

<xs:complexType name="OfferDeliveryReceiptDocumentType">
<xs:annotation>
    <xs:documentation>An OfferDeliveryReceipt is a receipt that is sent from server to client after the client has submitted an offer. This receipt confirms the successful processing of the offer. The receipt repeats the processing details given by the client and enriches them with the ID the server assigned to the offer.
The receipt includes the Response-Informations given in the messagecontext for delivery of said information in other contexts. So when the DeliveryReceipt is to be exchanged synchronously it MUST include the same Responseinformations twice: once on the messagelevel and once again in the document level.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-docs:ResponseDocumentType">
      <xs:sequence>
        <xs:element name="processedOfferDetails" type="xvergabe-docs:ProcessedOfferDetails">
          <xs:annotation>
            <xs:documentation>Details of the offer processing result.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="platformSpecificReceipt" type="xvergabe-datatypes:ExistingObjectReference" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Contains a platform-specific receipt in a format chosen by the platform. This receipt may for example contain signed and timestamped information to prove that the offer has been properly received. when present the platformSpecificReceipt MUST be made available through getDocuments()-operation.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="platformSpecificReceiptReport" type="xvergabe-datatypes:ExistingObjectReference">
          <xs:annotation>
            <xs:documentation>Contains a platform-specific report of the receipt in a user-readable format chosen by the platform (pdf, html, ...). This report may for example be directly displayed in the bidder client.
when provided the PlatformSpecificReceiptReport MUST be made available through the getDocuments()-operation</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element OfferDeliveryReceiptDocumentType/processedOfferDetails

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:ProcessedOfferDetails

properties

content

complex

children

xvergabe-docs:offerMessageID xvergabe-docs:processedOfferID xvergabe-docs:receivedDateTime xvergabe-docs:receivedInTime

annotation

documentation

Details of the offer processing result.

source

<xs:element name="processedOfferDetails" type="xvergabe-docs:ProcessedOfferDetails">
<xs:annotation>
<xs:documentation>Details of the offer processing result.</xs:documentation>
</xs:annotation>
</xs:element>

element OfferDeliveryReceiptDocumentType/platformSpecificReceipt

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-datatypes:name xvergabe-datatypes:fileSize xvergabe-datatypes:attachmentIdentifier

properties

minOcc	0
maxOcc	1
content	complex

children

annotation

documentation

Contains a platform-specific receipt in a format chosen by the platform. This receipt may for example contain signed and timestamped information to prove that the offer has been properly received. when present the platformSpecificReceipt MUST be made available through getDocuments()-operation.

source

<xs:element name="platformSpecificReceipt" type="xvergabe-datatypes:ExistingObjectReference" minOccurs="0">
<xs:annotation>
<xs:documentation>Contains a platform-specific receipt in a format chosen by the platform. This receipt may for example contain signed and timestamped information to prove that the offer has been properly received. when present the platformSpecificReceipt MUST be made available through getDocuments()-operation.</xs:documentation>
</xs:annotation>
</xs:element>

element OfferDeliveryReceiptDocumentType/platformSpecificReceiptReport

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-datatypes:name xvergabe-datatypes:fileSize xvergabe-datatypes:attachmentIdentifier

properties

content

complex

children

annotation

documentation

Contains a platform-specific report of the receipt in a user-readable format chosen by the platform (pdf, html, ...). This report may for example be directly displayed in the bidder client.
when provided the PlatformSpecificReceiptReport MUST be made available through the getDocuments()-operation

source

<xs:element name="platformSpecificReceiptReport" type="xvergabe-datatypes:ExistingObjectReference">
<xs:annotation>
<xs:documentation>Contains a platform-specific report of the receipt in a user-readable format chosen by the platform (pdf, html, ...). This report may for example be directly displayed in the bidder client.
when provided the PlatformSpecificReceiptReport MUST be made available through the getDocuments()-operation</xs:documentation>
</xs:annotation>
</xs:element>

complexType OfferDocumentType

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:accordingITTMsgID xvergabe-docs:offerObject

annotation

documentation

An offer document contains a description of the actual offer from a bidder. The actual offer
is part of the encrypted offer container(s) attached to the offer message. These containers are PKCS#7 encrypted ZIP files containing the files described/requested/provided by the ITT. Those containers MUST also include a structured Content description in form of OfferContent.xml holding an OfferContent-Element.
An offer MUST be submitted in whole and MUST NOT be splitted over several Offer documents. A signature must be applied to the offer BEFORE encryption (this does not apply if the offer is submitted via OSCI).

source

<xs:complexType name="OfferDocumentType">
<xs:annotation>
    <xs:documentation>An offer document contains a description of the actual offer from a bidder. The actual offer
is part of the encrypted offer container(s) attached to the offer message. These containers are PKCS#7 encrypted ZIP files containing the files described/requested/provided by the ITT. Those containers MUST also include a structured Content description in form of OfferContent.xml holding an OfferContent-Element.
An offer MUST be submitted in whole and MUST NOT be splitted over several Offer documents. A signature must be applied to the offer BEFORE encryption (this does not apply if the offer is submitted via OSCI).</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="accordingITTMsgID" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>ID of the latest InvitationToTender message the client received from the server. This InvitationToTender message is thus the basis for the creation of the offer. The server SHOULD use this ID to check if the offer was submitted on the most current version of the tendering documents.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="offerObject" type="xvergabe-docs:OfferObject">
      <xs:annotation>
        <xs:documentation>Contains the reference(s) to the offer itself.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element OfferDocumentType/accordingITTMsgID

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:OfferObject

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

source

<xs:element name="accordingITTMsgID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>ID of the latest InvitationToTender message the client received from the server. This InvitationToTender message is thus the basis for the creation of the offer. The server SHOULD use this ID to check if the offer was submitted on the most current version of the tendering documents.</xs:documentation>
</xs:annotation>
</xs:element>

element OfferDocumentType/offerObject

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

complex

children

xvergabe-docs:primaryContainer xvergabe-docs:secondaryContainer

annotation

documentation

Contains the reference(s) to the offer itself.

source

<xs:element name="offerObject" type="xvergabe-docs:OfferObject">
<xs:annotation>
<xs:documentation>Contains the reference(s) to the offer itself.</xs:documentation>
</xs:annotation>
</xs:element>

complexType OfferObject

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:primaryContainer xvergabe-docs:secondaryContainer

annotation

documentation

Merely a vessel to point to the offer/participation containers attached to the message.

source

<xs:complexType name="OfferObject">
<xs:annotation>
    <xs:documentation>Merely a vessel to point to the offer/participation containers attached to the message.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="primaryContainer" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>reference to the primary Offer Container (or Participation Request Container) represented by an attachment to the message. thus the GUID here MUST reference an ID of an attachment to the message carrying the offerObject (or participationObject)
the primary container holds all documents needed for opening of the tender/participation request as requested in the itt/ITP.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="secondaryContainer" type="xvergabe-datatypes:GUID" minOccurs="0">
      <xs:annotation>
        <xs:documentation>reference to the secondary Offer (or Participation Request) Container represented by an attachment to the message. thus the GUID here MUST reference an ID of an attachment to the message carrying the offerObject (or participationObject)
the secondary container holds all documents not essentially needed for opening the tender (participation request) as requested in the itt (or ITP) or documents the economic operator added to the tender/participation request (beyond the documents requested in the ITT/ITP).</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element OfferObject/primaryContainer

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

reference to the primary Offer Container (or Participation Request Container) represented by an attachment to the message. thus the GUID here MUST reference an ID of an attachment to the message carrying the offerObject (or participationObject)
the primary container holds all documents needed for opening of the tender/participation request as requested in the itt/ITP.

source

<xs:element name="primaryContainer" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>reference to the primary Offer Container (or Participation Request Container) represented by an attachment to the message. thus the GUID here MUST reference an ID of an attachment to the message carrying the offerObject (or participationObject)
the primary container holds all documents needed for opening of the tender/participation request as requested in the itt/ITP.</xs:documentation>
</xs:annotation>
</xs:element>

element OfferObject/secondaryContainer

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:OK xvergabe-docs:WARNING xvergabe-docs:ERROR xvergabe-docs:responseInformation xvergabe-docs:processedParticipationDetails xvergabe-docs:platformSpecificReceipt xvergabe-docs:platformSpecificReceiptReport

properties

minOcc	0
maxOcc	1
content	simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

reference to the secondary Offer (or Participation Request) Container represented by an attachment to the message. thus the GUID here MUST reference an ID of an attachment to the message carrying the offerObject (or participationObject)
the secondary container holds all documents not essentially needed for opening the tender (participation request) as requested in the itt (or ITP) or documents the economic operator added to the tender/participation request (beyond the documents requested in the ITT/ITP).

source

<xs:element name="secondaryContainer" type="xvergabe-datatypes:GUID" minOccurs="0">
<xs:annotation>
<xs:documentation>reference to the secondary Offer (or Participation Request) Container represented by an attachment to the message. thus the GUID here MUST reference an ID of an attachment to the message carrying the offerObject (or participationObject)
the secondary container holds all documents not essentially needed for opening the tender (participation request) as requested in the itt (or ITP) or documents the economic operator added to the tender/participation request (beyond the documents requested in the ITT/ITP).</xs:documentation>
</xs:annotation>
</xs:element>

complexType ParticipationDeliveryReceiptDocumentType

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

extension of xvergabe-docs:ResponseDocumentType

properties

base	xvergabe-docs:ResponseDocumentType

children

annotation

documentation

A ParticipationDeliveryReceipt is a receipt that is sent from server to client after the client has submitted a Participation request. This receipt confirms the successful processing of the Participation request. The receipt repeats the processing details given by the client and enriches them with the ID the server assigned to the Participation request.
The receipt includes the Response-Informations given in the messagecontext for delivery of said information in other contexts. So when the DeliveryReceipt is to be exchanged synchronously it MUST include the same Responseinformations twice: once on the messagelevel and once again in the document level.

source

<xs:complexType name="ParticipationDeliveryReceiptDocumentType">
<xs:annotation>
    <xs:documentation>A ParticipationDeliveryReceipt is a receipt that is sent from server to client after the client has submitted a Participation request. This receipt confirms the successful processing of the Participation request. The receipt repeats the processing details given by the client and enriches them with the ID the server assigned to the Participation request.
The receipt includes the Response-Informations given in the messagecontext for delivery of said information in other contexts. So when the DeliveryReceipt is to be exchanged synchronously it MUST include the same Responseinformations twice: once on the messagelevel and once again in the document level.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-docs:ResponseDocumentType">
      <xs:sequence>
        <xs:element name="processedParticipationDetails" type="xvergabe-docs:ProcessedParticipationDetails">
          <xs:annotation>
            <xs:documentation>Details of the Participation processing result.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="platformSpecificReceipt" type="xvergabe-datatypes:ExistingObjectReference" minOccurs="0"/>
        <xs:element name="platformSpecificReceiptReport" type="xvergabe-datatypes:ExistingObjectReference">
          <xs:annotation>
            <xs:documentation>Contains a platform-specific report of the receipt in a user-readable format chosen by the platform (pdf, html, ...). This report may for example be directly displayed in the bidder client.
When present, the referenced platformSpecificReceiptReport MUST be made available through the getDocuments()-operations by the platform.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element ParticipationDeliveryReceiptDocumentType/processedParticipationDetails

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:ProcessedParticipationDetails

properties

content

complex

children

xvergabe-docs:participationMessageID xvergabe-docs:processedParticipationID xvergabe-docs:receivedDateTime xvergabe-docs:receivedInTime

annotation

documentation

Details of the Participation processing result.

source

<xs:element name="processedParticipationDetails" type="xvergabe-docs:ProcessedParticipationDetails">
<xs:annotation>
<xs:documentation>Details of the Participation processing result.</xs:documentation>
</xs:annotation>
</xs:element>

element ParticipationDeliveryReceiptDocumentType/platformSpecificReceipt

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-datatypes:name xvergabe-datatypes:fileSize xvergabe-datatypes:attachmentIdentifier

properties

minOcc	0
maxOcc	1
content	complex

children

source

<xs:element name="platformSpecificReceipt" type="xvergabe-datatypes:ExistingObjectReference" minOccurs="0"/>

element ParticipationDeliveryReceiptDocumentType/platformSpecificReceiptReport

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-datatypes:name xvergabe-datatypes:fileSize xvergabe-datatypes:attachmentIdentifier

properties

content

complex

children

annotation

documentation

Contains a platform-specific report of the receipt in a user-readable format chosen by the platform (pdf, html, ...). This report may for example be directly displayed in the bidder client.
When present, the referenced platformSpecificReceiptReport MUST be made available through the getDocuments()-operations by the platform.

source

<xs:element name="platformSpecificReceiptReport" type="xvergabe-datatypes:ExistingObjectReference">
<xs:annotation>
<xs:documentation>Contains a platform-specific report of the receipt in a user-readable format chosen by the platform (pdf, html, ...). This report may for example be directly displayed in the bidder client.
When present, the referenced platformSpecificReceiptReport MUST be made available through the getDocuments()-operations by the platform.</xs:documentation>
</xs:annotation>
</xs:element>

complexType ParticipationDocumentType

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:accordingITPMsgID xvergabe-docs:participationObject

annotation

documentation

A participation document contains a description of the actual participation request by an economic operator. The actual participation request is part of the encrypted participation container(s) attached to the participation message. These containers are PKCS#7 encrypted ZIP files containing the files described/requested/provided by the ITP. Those containers MUST also include a structured Content description in form of a ParticipationContent.xml file holding a ParticipationContent-Element.
A participation request MUST be submitted in whole and MUST NOT be splitted over several participation documents. A signature (if needed) must be applied to the participation BEFORE encryption (this does not apply if the participation is submitted via OSCI).

source

<xs:complexType name="ParticipationDocumentType">
<xs:annotation>
    <xs:documentation>A participation document contains a description of the actual participation request by an economic operator. The actual participation request is part of the encrypted participation container(s) attached to the participation message. These containers are PKCS#7 encrypted ZIP files containing the files described/requested/provided by the ITP. Those containers MUST also include a structured Content description in form of a ParticipationContent.xml file holding a ParticipationContent-Element.
A participation request MUST be submitted in whole and MUST NOT be splitted over several participation documents. A signature (if needed) must be applied to the participation BEFORE encryption (this does not apply if the participation is submitted via OSCI).</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="accordingITPMsgID" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>ID of the latest InvitationToParticipation message the client received from the server. This InvitationToParticipation message is thus the basis for the creation of the participation request. The server SHOULD use this ID to check if the offer was submitted on the most current version of the participation documents.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="participationObject" type="xvergabe-docs:OfferObject">
      <xs:annotation>
        <xs:documentation>Contains the participation request itself.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element ParticipationDocumentType/accordingITPMsgID

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:OfferObject

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

source

<xs:element name="accordingITPMsgID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>ID of the latest InvitationToParticipation message the client received from the server. This InvitationToParticipation message is thus the basis for the creation of the participation request. The server SHOULD use this ID to check if the offer was submitted on the most current version of the participation documents.</xs:documentation>
</xs:annotation>
</xs:element>

element ParticipationDocumentType/participationObject

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

complex

children

xvergabe-docs:primaryContainer xvergabe-docs:secondaryContainer

annotation

documentation

Contains the participation request itself.

source

<xs:element name="participationObject" type="xvergabe-docs:OfferObject">
<xs:annotation>
<xs:documentation>Contains the participation request itself.</xs:documentation>
</xs:annotation>
</xs:element>

complexType ParticipationSubmissionDetails

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:postalSubmission xvergabe-docs:electronicalSubmission

annotation

documentation

Contains information enabling a bidder to submit a participation request.

source

<xs:complexType name="ParticipationSubmissionDetails">
<xs:annotation>
    <xs:documentation>Contains information enabling a bidder to submit a participation request.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="postalSubmission" type="xvergabe-docs:ParticipationSubmissionDetailsPostal" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Information about postal submission if applicable.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="electronicalSubmission" type="xvergabe-docs:ParticipationSubmissionDetailsElectronical" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Information about electronical submission if applicable.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element ParticipationSubmissionDetails/postalSubmission

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:ParticipationSubmissionDetailsPostal

properties

minOcc	0
maxOcc	1
content	complex

children

xvergabe-docs:numberOfCopies

annotation

documentation

Information about postal submission if applicable.

source

<xs:element name="postalSubmission" type="xvergabe-docs:ParticipationSubmissionDetailsPostal" minOccurs="0">
<xs:annotation>
<xs:documentation>Information about postal submission if applicable.</xs:documentation>
</xs:annotation>
</xs:element>

element ParticipationSubmissionDetails/electronicalSubmission

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:ParticipationSubmissionDetailsElectronical

properties

minOcc	0
maxOcc	1
content	complex

children

xvergabe-docs:minimumSignatureLevelContainer xvergabe-docs:minimumSignatureLevelForWithdrawal xvergabe-docs:onlyPrimaryContainerAllowed xvergabe-docs:encryptionKey xvergabe-docs:osciSubmission

annotation

documentation

Information about electronical submission if applicable.

source

<xs:element name="electronicalSubmission" type="xvergabe-docs:ParticipationSubmissionDetailsElectronical" minOccurs="0">
<xs:annotation>
<xs:documentation>Information about electronical submission if applicable.</xs:documentation>
</xs:annotation>
</xs:element>

complexType ParticipationSubmissionDetailsElectronical

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:minimumSignatureLevelContainer xvergabe-docs:minimumSignatureLevelForWithdrawal xvergabe-docs:onlyPrimaryContainerAllowed xvergabe-docs:encryptionKey xvergabe-docs:osciSubmission

annotation

documentation

Information about the electronical submission of a participation request.

source

<xs:complexType name="ParticipationSubmissionDetailsElectronical">
<xs:annotation>
    <xs:documentation>Information about the electronical submission of a participation request.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="minimumSignatureLevelContainer" type="xvergabe-cl:Code.SignatureLevelType">
      <xs:annotation>
        <xs:documentation>The expected minimum level of signature certificate used for signature of the participation container (not the documents themself). A value of NONE means not to sign the container at all. All other values imply a signature over the participation xml file within the participation container.
This is purely for informational purposes. A Client (and/or its user) may decide to sign otherwise (or not at all). The decision about the legal implications/acceptance of the participation request is up to the Contracting Authority.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="minimumSignatureLevelForWithdrawal" type="xvergabe-cl:Code.SignatureLevelType">
      <xs:annotation>
        <xs:documentation>The expected minimum level of signature certificates with which participation request withdrawals SHALL be signed. This is purely for informational purposes. A Client (and/or its user) may decide to sign otherwise (or not at all). The decision about the legal implications/acceptance of the withdrawal is up to the Contracting Authority.
When the asked-for signature level is not NONE, the client SHALL supply a signed document attached to the ParticipationWithdrawal-Message. The files' content is not in scope of this specification.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="onlyPrimaryContainerAllowed" type="xs:boolean">
      <xs:annotation>
        <xs:documentation>flag indicating that the platform does not expect and allows a secondary participationContainer. the client MUST put all documents in the primary (and only) container.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="encryptionKey" type="xvergabe-docs:EncryptionKeyDetails" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>the encryptionKey(s) used to encrypt the participationRequest</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="osciSubmission" type="xvergabe-docs:TenderSubmissionDetailsOSCI" minOccurs="0">
      <xs:annotation>
        <xs:documentation>when the participationRequest has to be submitted via OSCI-Transport, technical parameters used for delivery MUST be supplied here.
the participation Request submission via OSCI-Transport implies that participation request withdrawals are to be sent via OSCI-Transport aswell.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element ParticipationSubmissionDetailsElectronical/minimumSignatureLevelContainer

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

complex

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:signatureLevelType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

The expected minimum level of signature certificate used for signature of the participation container (not the documents themself). A value of NONE means not to sign the container at all. All other values imply a signature over the participation xml file within the participation container.
This is purely for informational purposes. A Client (and/or its user) may decide to sign otherwise (or not at all). The decision about the legal implications/acceptance of the participation request is up to the Contracting Authority.

source

<xs:element name="minimumSignatureLevelContainer" type="xvergabe-cl:Code.SignatureLevelType">
<xs:annotation>
<xs:documentation>The expected minimum level of signature certificate used for signature of the participation container (not the documents themself). A value of NONE means not to sign the container at all. All other values imply a signature over the participation xml file within the participation container.
This is purely for informational purposes. A Client (and/or its user) may decide to sign otherwise (or not at all). The decision about the legal implications/acceptance of the participation request is up to the Contracting Authority.</xs:documentation>
</xs:annotation>
</xs:element>

element ParticipationSubmissionDetailsElectronical/minimumSignatureLevelForWithdrawal

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

complex

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:signatureLevelType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xvergabe-docs:EncryptionKeyDetails

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

The expected minimum level of signature certificates with which participation request withdrawals SHALL be signed. This is purely for informational purposes. A Client (and/or its user) may decide to sign otherwise (or not at all). The decision about the legal implications/acceptance of the withdrawal is up to the Contracting Authority.
When the asked-for signature level is not NONE, the client SHALL supply a signed document attached to the ParticipationWithdrawal-Message. The files' content is not in scope of this specification.

source

<xs:element name="minimumSignatureLevelForWithdrawal" type="xvergabe-cl:Code.SignatureLevelType">
<xs:annotation>
<xs:documentation>The expected minimum level of signature certificates with which participation request withdrawals SHALL be signed. This is purely for informational purposes. A Client (and/or its user) may decide to sign otherwise (or not at all). The decision about the legal implications/acceptance of the withdrawal is up to the Contracting Authority.
When the asked-for signature level is not NONE, the client SHALL supply a signed document attached to the ParticipationWithdrawal-Message. The files' content is not in scope of this specification.</xs:documentation>
</xs:annotation>
</xs:element>

element ParticipationSubmissionDetailsElectronical/onlyPrimaryContainerAllowed

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:boolean

properties

content

simple

annotation

documentation

flag indicating that the platform does not expect and allows a secondary participationContainer. the client MUST put all documents in the primary (and only) container.

source

<xs:element name="onlyPrimaryContainerAllowed" type="xs:boolean">
<xs:annotation>
<xs:documentation>flag indicating that the platform does not expect and allows a secondary participationContainer. the client MUST put all documents in the primary (and only) container.</xs:documentation>
</xs:annotation>
</xs:element>

element ParticipationSubmissionDetailsElectronical/encryptionKey

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

minOcc	1
maxOcc	unbounded
content	complex

children

xvergabe-docs:credentialID xvergabe-docs:encryptionOrder

annotation

documentation

the encryptionKey(s) used to encrypt the participationRequest

source

<xs:element name="encryptionKey" type="xvergabe-docs:EncryptionKeyDetails" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>the encryptionKey(s) used to encrypt the participationRequest</xs:documentation>
</xs:annotation>
</xs:element>

element ParticipationSubmissionDetailsElectronical/osciSubmission

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:TenderSubmissionDetailsOSCI

properties

minOcc	0
maxOcc	1
content	complex

children

xvergabe-docs:intermediaryURI xvergabe-docs:intermediaryPublicKeyReference xvergabe-docs:addresseePublicKeyReference xvergabe-docs:useTransportEncryption xvergabe-docs:intermediarySupportsCryptographicTimestamps xvergabe-docs:verificationServiceURI

annotation

documentation

when the participationRequest has to be submitted via OSCI-Transport, technical parameters used for delivery MUST be supplied here.
the participation Request submission via OSCI-Transport implies that participation request withdrawals are to be sent via OSCI-Transport aswell.

source

<xs:element name="osciSubmission" type="xvergabe-docs:TenderSubmissionDetailsOSCI" minOccurs="0">
<xs:annotation>
<xs:documentation>when the participationRequest has to be submitted via OSCI-Transport, technical parameters used for delivery MUST be supplied here.
the participation Request submission via OSCI-Transport implies that participation request withdrawals are to be sent via OSCI-Transport aswell.</xs:documentation>
</xs:annotation>
</xs:element>

complexType ParticipationSubmissionDetailsPostal

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:numberOfCopies

annotation

documentation

Information about the postal submission of a participation request.

source

<xs:complexType name="ParticipationSubmissionDetailsPostal">
<xs:annotation>
    <xs:documentation>Information about the postal submission of a participation request.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="numberOfCopies" type="xs:nonNegativeInteger" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The number of copies to provide in a postal submission of a participation request.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element ParticipationSubmissionDetailsPostal/numberOfCopies

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:nonNegativeInteger

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

The number of copies to provide in a postal submission of a participation request.

source

<xs:element name="numberOfCopies" type="xs:nonNegativeInteger" minOccurs="0">
<xs:annotation>
<xs:documentation>The number of copies to provide in a postal submission of a participation request.</xs:documentation>
</xs:annotation>
</xs:element>

complexType platformInformationDetails

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:uploadLimit

annotation

documentation

Information about the platform (server).

source

<xs:complexType name="platformInformationDetails">
<xs:annotation>
    <xs:documentation>Information about the platform (server).</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="uploadLimit" type="xvergabe-docs:UploadLimit" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>List of platform-specific upload limits.
The limit when referring to size limits are referring to the gross size of the according artefact (eg. attachment). this means the size including all transformations (like base64) is referred to.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element platformInformationDetails/uploadLimit

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:UploadLimit

properties

minOcc	0
maxOcc	unbounded
content	complex

children

xvergabe-docs:limitType xvergabe-docs:limitValue

annotation

documentation

List of platform-specific upload limits.
The limit when referring to size limits are referring to the gross size of the according artefact (eg. attachment). this means the size including all transformations (like base64) is referred to.

source

<xs:element name="uploadLimit" type="xvergabe-docs:UploadLimit" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>List of platform-specific upload limits.
The limit when referring to size limits are referring to the gross size of the according artefact (eg. attachment). this means the size including all transformations (like base64) is referred to.</xs:documentation>
</xs:annotation>
</xs:element>

complexType procedureWideStatusAndTimeLimits

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:procedureStatus xvergabe-docs:procedureTimeLimit xvergabe-docs:negotiationRoundCounter

annotation

documentation

When no Lot-specific timelimits and lot-specific statuses need to be implemented, this information MUST be given to inform the client about the current status and timelimits of the procedure (and if given: ALL lots).

source

<xs:complexType name="procedureWideStatusAndTimeLimits">
<xs:annotation>
    <xs:documentation>When no Lot-specific timelimits and lot-specific statuses need to be implemented, this information MUST be given to inform the client about the current status and timelimits of the procedure (and if given: ALL lots).</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="procedureStatus" type="xvergabe-cl:Code.StatusType">
      <xs:annotation>
        <xs:documentation>Procedurewide status. MAY ONLY be omitted when lot-specific time limits and statusinformation are to be implemented within the procedure</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="procedureTimeLimit" type="xvergabe-docs:TimeLimitType" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>procedure wide timelimit(s). MAY ONLY be omitted when lot specific time limits need to be implemented.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="negotiationRoundCounter" type="xs:positiveInteger" minOccurs="0">
      <xs:annotation>
        <xs:documentation>information about the procedure wide negotiationround. Only applicable if procedureTyp = NEGOTIATED_PROCEDURE or NEGOTIATED_PROCEDURE_WITH_PARTICIPATION_CONTEST AND the negotiation rounds/timelimits are NOT lot specific (all lots (if any) are negotiated at the same time within the same limits).
This is a counter increased with each negotiation round within the procedure. A client SHALL compare this value against the negotiationround-counter within the appropriate ITT for this procedure. If the client has no ITT for this negotiation round he SHALL refrain from creating an offer.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element procedureWideStatusAndTimeLimits/procedureStatus

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-cl:Code.StatusType

properties

content

complex

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:statusType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xvergabe-docs:TimeLimitType

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

Procedurewide status. MAY ONLY be omitted when lot-specific time limits and statusinformation are to be implemented within the procedure

source

<xs:element name="procedureStatus" type="xvergabe-cl:Code.StatusType">
<xs:annotation>
<xs:documentation>Procedurewide status. MAY ONLY be omitted when lot-specific time limits and statusinformation are to be implemented within the procedure</xs:documentation>
</xs:annotation>
</xs:element>

element procedureWideStatusAndTimeLimits/procedureTimeLimit

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

minOcc	1
maxOcc	unbounded
content	complex

children

xvergabe-docs:timeLimitType xvergabe-docs:timeLimit

annotation

documentation

procedure wide timelimit(s). MAY ONLY be omitted when lot specific time limits need to be implemented.

source

<xs:element name="procedureTimeLimit" type="xvergabe-docs:TimeLimitType" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>procedure wide timelimit(s). MAY ONLY be omitted when lot specific time limits need to be implemented.</xs:documentation>
</xs:annotation>
</xs:element>

element procedureWideStatusAndTimeLimits/negotiationRoundCounter

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:positiveInteger

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

information about the procedure wide negotiationround. Only applicable if procedureTyp = NEGOTIATED_PROCEDURE or NEGOTIATED_PROCEDURE_WITH_PARTICIPATION_CONTEST AND the negotiation rounds/timelimits are NOT lot specific (all lots (if any) are negotiated at the same time within the same limits).
This is a counter increased with each negotiation round within the procedure. A client SHALL compare this value against the negotiationround-counter within the appropriate ITT for this procedure. If the client has no ITT for this negotiation round he SHALL refrain from creating an offer.

source

<xs:element name="negotiationRoundCounter" type="xs:positiveInteger" minOccurs="0">
<xs:annotation>
<xs:documentation>information about the procedure wide negotiationround. Only applicable if procedureTyp = NEGOTIATED_PROCEDURE or NEGOTIATED_PROCEDURE_WITH_PARTICIPATION_CONTEST AND the negotiation rounds/timelimits are NOT lot specific (all lots (if any) are negotiated at the same time within the same limits).
This is a counter increased with each negotiation round within the procedure. A client SHALL compare this value against the negotiationround-counter within the appropriate ITT for this procedure. If the client has no ITT for this negotiation round he SHALL refrain from creating an offer.</xs:documentation>
</xs:annotation>
</xs:element>

complexType ProcessedOfferDetails

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:offerMessageID xvergabe-docs:processedOfferID xvergabe-docs:receivedDateTime xvergabe-docs:receivedInTime

annotation

documentation

Information about the received offer(message) for which the receipt is being made out. This information includes an ID the server assigned to the submitted offer, the ID of the message the offer has been sent with (repetition of the clients offerMessageID), and the date and time (non qualified timestamp) the offer has been received.

source

<xs:complexType name="ProcessedOfferDetails">
<xs:annotation>
    <xs:documentation>Information about the received offer(message) for which the receipt is being made out. This information includes an ID the server assigned to the submitted offer, the ID of the message the offer has been sent with (repetition of the clients offerMessageID), and the date and time (non qualified timestamp) the offer has been received.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="offerMessageID" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>the ID of the message the offer has been sent by the economic operator. this needs to be referenced here since the deliveryReceipt is not only delivered synchronous but asynchronous aswell and thus needs a link to the original sending instance of the message</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="processedOfferID" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>the ID under which the platform processed and saved the offer sent by the economic operator. This ID has to be referenced when withdrawing.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="receivedDateTime" type="xvergabe-datatypes:DateTimeTZ">
      <xs:annotation>
        <xs:documentation>Date and time of the reception of the offer.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="receivedInTime" type="xs:boolean">
      <xs:annotation>
        <xs:documentation>indicator whether the offer was received in time (before the submission deadline) or not.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element ProcessedOfferDetails/offerMessageID

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

the ID of the message the offer has been sent by the economic operator. this needs to be referenced here since the deliveryReceipt is not only delivered synchronous but asynchronous aswell and thus needs a link to the original sending instance of the message

source

<xs:element name="offerMessageID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>the ID of the message the offer has been sent by the economic operator. this needs to be referenced here since the deliveryReceipt is not only delivered synchronous but asynchronous aswell and thus needs a link to the original sending instance of the message</xs:documentation>
</xs:annotation>
</xs:element>

element ProcessedOfferDetails/processedOfferID

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

the ID under which the platform processed and saved the offer sent by the economic operator. This ID has to be referenced when withdrawing.

source

<xs:element name="processedOfferID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>the ID under which the platform processed and saved the offer sent by the economic operator. This ID has to be referenced when withdrawing.</xs:documentation>
</xs:annotation>
</xs:element>

element ProcessedOfferDetails/receivedDateTime

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:participationMessageID xvergabe-docs:processedParticipationID xvergabe-docs:receivedDateTime xvergabe-docs:receivedInTime

properties

content

simple

facets

Kind	Value	Annotation
pattern	([1-9][0-9]{3,}\|0[0-9]{3})-(0[1-9]\|1[0-2])-(0[1-9]\|[12][0-9]\|3[01])T(([01][0-9]\|2[0-3]):[0-5][0-9]:[0-5][0-9](\.[0-9]+)?\|(24:00:00(\.0+)?))(Z\|(\+\|-)((0[0-9]\|1[0-3]):[0-5][0-9]\|14:00))

annotation

documentation

Date and time of the reception of the offer.

source

<xs:element name="receivedDateTime" type="xvergabe-datatypes:DateTimeTZ">
<xs:annotation>
<xs:documentation>Date and time of the reception of the offer.</xs:documentation>
</xs:annotation>
</xs:element>

element ProcessedOfferDetails/receivedInTime

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:boolean

properties

content

simple

annotation

documentation

indicator whether the offer was received in time (before the submission deadline) or not.

source

<xs:element name="receivedInTime" type="xs:boolean">
<xs:annotation>
<xs:documentation>indicator whether the offer was received in time (before the submission deadline) or not.</xs:documentation>
</xs:annotation>
</xs:element>

complexType ProcessedParticipationDetails

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

annotation

documentation

Repetition of the information the client has previously sent to the server within the ParticipationProcessingDetails. This information is enriched with an ID the server assigned to the submitted Participation.

source

<xs:complexType name="ProcessedParticipationDetails">
<xs:annotation>
    <xs:documentation>Repetition of the information the client has previously sent to the server within the ParticipationProcessingDetails. This information is enriched with an ID the server assigned to the submitted Participation.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="participationMessageID" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>the ID of the message the participation request has been sent by the economic operator. this needs to be referenced here since the deliveryReceipt is not only delivered synchronous but asynchronous aswell and thus needs a link to the original sending instance of the message</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="processedParticipationID" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>the ID under which the platform processed and saved the participation sent by the economic operator. This ID has to be referenced when withdrawing.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="receivedDateTime" type="xvergabe-datatypes:DateTimeTZ">
      <xs:annotation>
        <xs:documentation>Date and time of the reception of the Participation.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="receivedInTime" type="xs:boolean">
      <xs:annotation>
        <xs:documentation>indicator whether the participation request was received in time (before the submission deadline) or not.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element ProcessedParticipationDetails/participationMessageID

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

the ID of the message the participation request has been sent by the economic operator. this needs to be referenced here since the deliveryReceipt is not only delivered synchronous but asynchronous aswell and thus needs a link to the original sending instance of the message

source

<xs:element name="participationMessageID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>the ID of the message the participation request has been sent by the economic operator. this needs to be referenced here since the deliveryReceipt is not only delivered synchronous but asynchronous aswell and thus needs a link to the original sending instance of the message</xs:documentation>
</xs:annotation>
</xs:element>

element ProcessedParticipationDetails/processedParticipationID

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

the ID under which the platform processed and saved the participation sent by the economic operator. This ID has to be referenced when withdrawing.

source

<xs:element name="processedParticipationID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>the ID under which the platform processed and saved the participation sent by the economic operator. This ID has to be referenced when withdrawing.</xs:documentation>
</xs:annotation>
</xs:element>

element ProcessedParticipationDetails/receivedDateTime

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:withdrawalMessageID xvergabe-docs:withdrawalReceivedDateTime xvergabe-docs:withdrawalReceivedInTime

properties

content

simple

facets

Kind	Value	Annotation
pattern	([1-9][0-9]{3,}\|0[0-9]{3})-(0[1-9]\|1[0-2])-(0[1-9]\|[12][0-9]\|3[01])T(([01][0-9]\|2[0-3]):[0-5][0-9]:[0-5][0-9](\.[0-9]+)?\|(24:00:00(\.0+)?))(Z\|(\+\|-)((0[0-9]\|1[0-3]):[0-5][0-9]\|14:00))

annotation

documentation

Date and time of the reception of the Participation.

source

<xs:element name="receivedDateTime" type="xvergabe-datatypes:DateTimeTZ">
<xs:annotation>
<xs:documentation>Date and time of the reception of the Participation.</xs:documentation>
</xs:annotation>
</xs:element>

element ProcessedParticipationDetails/receivedInTime

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:boolean

properties

content

simple

annotation

documentation

indicator whether the participation request was received in time (before the submission deadline) or not.

source

<xs:element name="receivedInTime" type="xs:boolean">
<xs:annotation>
<xs:documentation>indicator whether the participation request was received in time (before the submission deadline) or not.</xs:documentation>
</xs:annotation>
</xs:element>

complexType ProcessedWithdrawalDetails

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

annotation

documentation

Repetition of the information the client has previously sent to the server within the OfferWithdrawal. This information is enriched with an ID the server assigned to the submitted OfferWithdrawal.

source

<xs:complexType name="ProcessedWithdrawalDetails">
<xs:annotation>
    <xs:documentation>Repetition of the information the client has previously sent to the server within the OfferWithdrawal. This information is enriched with an ID the server assigned to the submitted OfferWithdrawal.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="withdrawalMessageID" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>the ID of the message the withdrawal was been sent by the economic operator. this needs to be referenced here since the deliveryReceipt is not only delivered synchronous but asynchronous aswell and thus needs a link to the original sending instance of the message</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="withdrawalReceivedDateTime" type="xvergabe-datatypes:DateTimeTZ">
      <xs:annotation>
        <xs:documentation>The date and time the withdrawal has been received.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="withdrawalReceivedInTime" type="xs:boolean">
      <xs:annotation>
        <xs:documentation>indicator whether the withdrawal was received in time (before the submission deadline) or not.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element ProcessedWithdrawalDetails/withdrawalMessageID

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

the ID of the message the withdrawal was been sent by the economic operator. this needs to be referenced here since the deliveryReceipt is not only delivered synchronous but asynchronous aswell and thus needs a link to the original sending instance of the message

source

<xs:element name="withdrawalMessageID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>the ID of the message the withdrawal was been sent by the economic operator. this needs to be referenced here since the deliveryReceipt is not only delivered synchronous but asynchronous aswell and thus needs a link to the original sending instance of the message</xs:documentation>
</xs:annotation>
</xs:element>

element ProcessedWithdrawalDetails/withdrawalReceivedDateTime

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:OK xvergabe-docs:WARNING xvergabe-docs:ERROR xvergabe-docs:responseInformation

properties

content

simple

facets

Kind	Value	Annotation
pattern	([1-9][0-9]{3,}\|0[0-9]{3})-(0[1-9]\|1[0-2])-(0[1-9]\|[12][0-9]\|3[01])T(([01][0-9]\|2[0-3]):[0-5][0-9]:[0-5][0-9](\.[0-9]+)?\|(24:00:00(\.0+)?))(Z\|(\+\|-)((0[0-9]\|1[0-3]):[0-5][0-9]\|14:00))

annotation

documentation

The date and time the withdrawal has been received.

source

<xs:element name="withdrawalReceivedDateTime" type="xvergabe-datatypes:DateTimeTZ">
<xs:annotation>
<xs:documentation>The date and time the withdrawal has been received.</xs:documentation>
</xs:annotation>
</xs:element>

element ProcessedWithdrawalDetails/withdrawalReceivedInTime

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:boolean

properties

content

simple

annotation

documentation

indicator whether the withdrawal was received in time (before the submission deadline) or not.

source

<xs:element name="withdrawalReceivedInTime" type="xs:boolean">
<xs:annotation>
<xs:documentation>indicator whether the withdrawal was received in time (before the submission deadline) or not.</xs:documentation>
</xs:annotation>
</xs:element>

complexType ResponseDocumentType

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

annotation

documentation

A Response document serves as a technical response to messages and is sent from the server exclusively. The Response document is not part of a tendering procedure. Instead it contains information about success or error while processing a message.

source

<xs:complexType name="ResponseDocumentType">
<xs:annotation>
    <xs:documentation>A Response document serves as a technical response to messages and is sent from the server exclusively. The Response document is not part of a tendering procedure. Instead it contains information about success or error while processing a message.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:choice>
      <xs:annotation>
        <xs:documentation>the actual indicator whether the transaction the response is issued for succeeded, failed or succeeded with warnings.</xs:documentation>
      </xs:annotation>
      <xs:element name="OK" type="xvergabe-datatypes:String.0">
        <xs:annotation>
          <xs:documentation>indicates that the transaction the response is issued for, succeeded without limitations.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="WARNING" type="xvergabe-cl:Code.WarningCodeType" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>indicates that the transaction the response is issued for succeeded with limitations. The limitation/warning is specified by a defined code.
Additional information SHALL be given in responseInformation.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="ERROR" type="xvergabe-cl:Code.ErrorCodeType">
        <xs:annotation>
          <xs:documentation>indicates that the transaction the response is issued for failed. The error is specified by a defined code.
Additional information MUST be given in responseInformation.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="responseInformation" type="xvergabe-datatypes:String.4096" minOccurs="0">
      <xs:annotation>
        <xs:documentation>An informational text about the result of the processing of the message.
This text SHALL be given by the server in case of WARNING and ERROR.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element ResponseDocumentType/OK

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-datatypes:String.0

properties

content

simple

annotation

documentation

indicates that the transaction the response is issued for, succeeded without limitations.

source

<xs:element name="OK" type="xvergabe-datatypes:String.0">
<xs:annotation>
<xs:documentation>indicates that the transaction the response is issued for, succeeded without limitations.</xs:documentation>
</xs:annotation>
</xs:element>

element ResponseDocumentType/WARNING

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-cl:Code.WarningCodeType

properties

minOcc	1
maxOcc	unbounded
content	complex

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:warningCodeType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xvergabe-cl:Code.ErrorCodeType

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

indicates that the transaction the response is issued for succeeded with limitations. The limitation/warning is specified by a defined code.
Additional information SHALL be given in responseInformation.

source

<xs:element name="WARNING" type="xvergabe-cl:Code.WarningCodeType" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>indicates that the transaction the response is issued for succeeded with limitations. The limitation/warning is specified by a defined code.
Additional information SHALL be given in responseInformation.</xs:documentation>
</xs:annotation>
</xs:element>

element ResponseDocumentType/ERROR

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

complex

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:errorCodeType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

indicates that the transaction the response is issued for failed. The error is specified by a defined code.
Additional information MUST be given in responseInformation.

source

<xs:element name="ERROR" type="xvergabe-cl:Code.ErrorCodeType">
<xs:annotation>
<xs:documentation>indicates that the transaction the response is issued for failed. The error is specified by a defined code.
Additional information MUST be given in responseInformation.</xs:documentation>
</xs:annotation>
</xs:element>

element ResponseDocumentType/responseInformation

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

An informational text about the result of the processing of the message.
This text SHALL be given by the server in case of WARNING and ERROR.

source

<xs:element name="responseInformation" type="xvergabe-datatypes:String.4096" minOccurs="0">
<xs:annotation>
<xs:documentation>An informational text about the result of the processing of the message.
This text SHALL be given by the server in case of WARNING and ERROR.</xs:documentation>
</xs:annotation>
</xs:element>

complexType ResultNoticeDocumentType

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

extension of xvergabe-docs:InquiryDocumentType

properties

base	xvergabe-docs:InquiryDocumentType

children

xvergabe-docs:tenderID xvergabe-docs:tenderingSubject xvergabe-docs:contractingAuthorityName xvergabe-docs:referenceNumber xvergabe-docs:contractType xvergabe-docs:procedureType xvergabe-docs:tenderingNoticeURL xvergabe-docs:lot xvergabe-docs:procedureWideStatusAndTimeLimits

annotation

documentation

A ResultNotice serves to inform a bidder about the result of tendering procedure (i.e. whether the contract is awarded to the bidder or not) or the result of a participation contest (i.e. whether the bidder is allowed to take part in the participation contest or not). The ResultNotice document extends the InquiryDocumentType so that the actual content of the notice can be included in an InquiryDocument.

source

<xs:complexType name="ResultNoticeDocumentType">
<xs:annotation>
<xs:documentation>A ResultNotice serves to inform a bidder about the result of tendering procedure (i.e. whether the contract is awarded to the bidder or not) or the result of a participation contest (i.e. whether the bidder is allowed to take part in the participation contest or not). The ResultNotice document extends the InquiryDocumentType so that the actual content of the notice can be included in an InquiryDocument.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="xvergabe-docs:InquiryDocumentType"/>
</xs:complexContent>
</xs:complexType>

complexType TenderMetaInformationDetails

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

annotation

documentation

Contains information about the concerned tendering procedure.

source

<xs:complexType name="TenderMetaInformationDetails">
<xs:annotation>
    <xs:documentation>Contains information about the concerned tendering procedure.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="tenderID" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>The unique identifier of the tendering procedure.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="tenderingSubject" type="xvergabe-datatypes:String.4096">
      <xs:annotation>
        <xs:documentation>The actual subject of the tendering procedure.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="contractingAuthorityName" type="xvergabe-datatypes:String.1024" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Name of the contracting authority that issued the tendering procedure.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="referenceNumber" type="xvergabe-datatypes:String.255" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The reference number of the tendering procedure.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="contractType" type="xvergabe-cl:Code.ContractType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The type of contract that is the subject of the tendering procedure.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="procedureType" type="xvergabe-cl:Code.ProcedureType">
      <xs:annotation>
        <xs:documentation>The type of the tendering procedure itself (public, restricted, ...).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="tenderingNoticeURL" type="xs:anyURI" minOccurs="0">
      <xs:annotation>
        <xs:documentation>URL that points to a HTML representation of the notice / announcement of the tendering procedure. Thus URI-scheme SHALL be http(s)</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="lot" type="xvergabe-docs:LotOverview" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>Optional lotinformations for lots within the procedure.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="procedureWideStatusAndTimeLimits" type="xvergabe-docs:procedureWideStatusAndTimeLimits" minOccurs="0">
      <xs:annotation>
        <xs:documentation>When no Lot-specific timelimits and lot-specific statuses need to be implemented, this information MUST be given to inform the client about the current status and timelimits of the procedure (and if given: ALL lots).</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element TenderMetaInformationDetails/tenderID

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

The unique identifier of the tendering procedure.

source

<xs:element name="tenderID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>The unique identifier of the tendering procedure.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderMetaInformationDetails/tenderingSubject

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

simple

annotation

documentation

The actual subject of the tendering procedure.

source

<xs:element name="tenderingSubject" type="xvergabe-datatypes:String.4096">
<xs:annotation>
<xs:documentation>The actual subject of the tendering procedure.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderMetaInformationDetails/contractingAuthorityName

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

Name of the contracting authority that issued the tendering procedure.

source

<xs:element name="contractingAuthorityName" type="xvergabe-datatypes:String.1024" minOccurs="0">
<xs:annotation>
<xs:documentation>Name of the contracting authority that issued the tendering procedure.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderMetaInformationDetails/referenceNumber

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-cl:Code.ContractType

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

The reference number of the tendering procedure.

source

<xs:element name="referenceNumber" type="xvergabe-datatypes:String.255" minOccurs="0">
<xs:annotation>
<xs:documentation>The reference number of the tendering procedure.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderMetaInformationDetails/contractType

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

minOcc	0
maxOcc	1
content	complex

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:contractType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xvergabe-cl:Code.ProcedureType

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

The type of contract that is the subject of the tendering procedure.

source

<xs:element name="contractType" type="xvergabe-cl:Code.ContractType" minOccurs="0">
<xs:annotation>
<xs:documentation>The type of contract that is the subject of the tendering procedure.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderMetaInformationDetails/procedureType

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

complex

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:procedureType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xvergabe-docs:LotOverview

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

The type of the tendering procedure itself (public, restricted, ...).

source

<xs:element name="procedureType" type="xvergabe-cl:Code.ProcedureType">
<xs:annotation>
<xs:documentation>The type of the tendering procedure itself (public, restricted, ...).</xs:documentation>
</xs:annotation>
</xs:element>

element TenderMetaInformationDetails/tenderingNoticeURL

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:anyURI

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

URL that points to a HTML representation of the notice / announcement of the tendering procedure. Thus URI-scheme SHALL be http(s)

source

<xs:element name="tenderingNoticeURL" type="xs:anyURI" minOccurs="0">
<xs:annotation>
<xs:documentation>URL that points to a HTML representation of the notice / announcement of the tendering procedure. Thus URI-scheme SHALL be http(s)</xs:documentation>
</xs:annotation>
</xs:element>

element TenderMetaInformationDetails/lot

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

minOcc	0
maxOcc	unbounded
content	complex

children

xvergabe-docs:lotID xvergabe-docs:lotName xvergabe-docs:lotNumber xvergabe-docs:lotStatus xvergabe-docs:lotTimeLimit xvergabe-docs:lotNegotiationRoundCounter

annotation

documentation

Optional lotinformations for lots within the procedure.

source

<xs:element name="lot" type="xvergabe-docs:LotOverview" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>Optional lotinformations for lots within the procedure.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderMetaInformationDetails/procedureWideStatusAndTimeLimits

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:procedureWideStatusAndTimeLimits

properties

minOcc	0
maxOcc	1
content	complex

children

xvergabe-docs:procedureStatus xvergabe-docs:procedureTimeLimit xvergabe-docs:negotiationRoundCounter

annotation

documentation

source

<xs:element name="procedureWideStatusAndTimeLimits" type="xvergabe-docs:procedureWideStatusAndTimeLimits" minOccurs="0">
<xs:annotation>
<xs:documentation>When no Lot-specific timelimits and lot-specific statuses need to be implemented, this information MUST be given to inform the client about the current status and timelimits of the procedure (and if given: ALL lots).</xs:documentation>
</xs:annotation>
</xs:element>

complexType TenderMetaInformationDocumentType

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:tenderMetaInformationDetails xvergabe-docs:platformInformationDetails

annotation

documentation

A TenderMetaInformation contains meta data about a tendering procedure like the name, deadlines and the current status. A TenderMetaInformation is sent from a server to its clients and serves the clients as technical basis for further message exchange within the concerned tendering procedure. The TenderMetaInformation document is not part of the tendering documents. Instead it is intended as technical document to exchange meta data.

source

<xs:complexType name="TenderMetaInformationDocumentType">
<xs:annotation>
    <xs:documentation>A TenderMetaInformation contains meta data about a tendering procedure like the name, deadlines and the current status. A TenderMetaInformation is sent from a server to its clients and serves the clients as technical basis for further message exchange within the concerned tendering procedure. The TenderMetaInformation document is not part of the tendering documents. Instead it is intended as technical document to exchange meta data.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="tenderMetaInformationDetails" type="xvergabe-docs:TenderMetaInformationDetails">
      <xs:annotation>
        <xs:documentation>Contains information about the concerned tendering procedure.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="platformInformationDetails" type="xvergabe-docs:platformInformationDetails" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Contains information about the tendering platform (server) which may be relevant in the message exchange between server and client.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element TenderMetaInformationDocumentType/tenderMetaInformationDetails

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:TenderMetaInformationDetails

properties

content

complex

children

annotation

documentation

Contains information about the concerned tendering procedure.

source

<xs:element name="tenderMetaInformationDetails" type="xvergabe-docs:TenderMetaInformationDetails">
<xs:annotation>
<xs:documentation>Contains information about the concerned tendering procedure.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderMetaInformationDocumentType/platformInformationDetails

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:platformInformationDetails

properties

minOcc	0
maxOcc	1
content	complex

children

xvergabe-docs:uploadLimit

annotation

documentation

Contains information about the tendering platform (server) which may be relevant in the message exchange between server and client.

source

<xs:element name="platformInformationDetails" type="xvergabe-docs:platformInformationDetails" minOccurs="0">
<xs:annotation>
<xs:documentation>Contains information about the tendering platform (server) which may be relevant in the message exchange between server and client.</xs:documentation>
</xs:annotation>
</xs:element>

complexType TenderSubmissionDetails

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:submissionOfAlternativeTendersAccepted xvergabe-docs:postalSubmission xvergabe-docs:electronicalSubmission

annotation

documentation

Information about the submission formalities of a tendering procedure.

source

<xs:complexType name="TenderSubmissionDetails">
<xs:annotation>
    <xs:documentation>Information about the submission formalities of a tendering procedure.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="submissionOfAlternativeTendersAccepted" type="xs:boolean">
      <xs:annotation>
        <xs:documentation>Defines if the submission of alternative offers is allowed.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="postalSubmission" type="xvergabe-docs:TenderSubmissionDetailsPostal" minOccurs="0"/>
    <xs:element name="electronicalSubmission" type="xvergabe-docs:TenderSubmissionDetailsElectronical" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Information about the electronical submission formalities of the tendering procedure if applicable.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element TenderSubmissionDetails/submissionOfAlternativeTendersAccepted

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:boolean

properties

content

simple

annotation

documentation

Defines if the submission of alternative offers is allowed.

source

<xs:element name="submissionOfAlternativeTendersAccepted" type="xs:boolean">
<xs:annotation>
<xs:documentation>Defines if the submission of alternative offers is allowed.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderSubmissionDetails/postalSubmission

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:TenderSubmissionDetailsPostal

properties

minOcc	0
maxOcc	1
content	complex

children

xvergabe-docs:numberOfCopies xvergabe-docs:isBackup xvergabe-docs:includeElectronicalTenderDocuments

source

<xs:element name="postalSubmission" type="xvergabe-docs:TenderSubmissionDetailsPostal" minOccurs="0"/>

element TenderSubmissionDetails/electronicalSubmission

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:TenderSubmissionDetailsElectronical

properties

minOcc	0
maxOcc	1
content	complex

children

xvergabe-docs:minimumSignatureLevelContainer xvergabe-docs:minimumSignatureLevelForWithdrawal xvergabe-docs:onlyPrimaryContainerAllowed xvergabe-docs:encryptionKey xvergabe-docs:osciSubmission

annotation

documentation

Information about the electronical submission formalities of the tendering procedure if applicable.

source

<xs:element name="electronicalSubmission" type="xvergabe-docs:TenderSubmissionDetailsElectronical" minOccurs="0">
<xs:annotation>
<xs:documentation>Information about the electronical submission formalities of the tendering procedure if applicable.</xs:documentation>
</xs:annotation>
</xs:element>

complexType TenderSubmissionDetailsElectronical

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:minimumSignatureLevelContainer xvergabe-docs:minimumSignatureLevelForWithdrawal xvergabe-docs:onlyPrimaryContainerAllowed xvergabe-docs:encryptionKey xvergabe-docs:osciSubmission

annotation

documentation

Information about the electronical submission formalities of the tendering procedure. Documents can be submitted either directly to the platform (plain scenario) or indirectly via OSCI (OSCI scenario).

source

<xs:complexType name="TenderSubmissionDetailsElectronical">
<xs:annotation>
    <xs:documentation>Information about the electronical submission formalities of the tendering procedure. Documents can be submitted either directly to the platform (plain scenario) or indirectly via OSCI (OSCI scenario).</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="minimumSignatureLevelContainer" type="xvergabe-cl:Code.SignatureLevelType">
      <xs:annotation>
        <xs:documentation>The expected minimum level of signature certificate used for signature of the offer container (not the documents themself). A value of NONE means not to sign the container at all. All other values imply a signature over the offer xml file within the offer container.
This is purely for informational purposes. A Client (and/or its user) may decide to sign otherwise (or not at all). The decision about the legal implications/acceptance of the participation request is up to the Contracting Authority.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="minimumSignatureLevelForWithdrawal" type="xvergabe-cl:Code.SignatureLevelType">
      <xs:annotation>
        <xs:documentation>The expected minimum level of signature certificates with which offer withdrawals SHALL be signed. This is purely for informational purposes. A Client (and/or its user) may decide to sign otherwise (or not at all). The decision about the legal implications/acceptance of the withdrawal is up to the Contracting Authority.
When the asked-for signature level is not NONE, the client SHALL supply a signed document attached to the OfferWithdrawal-Message. The files' content is not in scope of this specification.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="onlyPrimaryContainerAllowed" type="xs:boolean">
      <xs:annotation>
        <xs:documentation>flag indicating that the platform does not expect and allows a secondary offerContainer. the client MUST put all documents in the primary (and only) container.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="encryptionKey" type="xvergabe-docs:EncryptionKeyDetails" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>the encryptionKey(s) used to encrypt the offer.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="osciSubmission" type="xvergabe-docs:TenderSubmissionDetailsOSCI" minOccurs="0">
      <xs:annotation>
        <xs:documentation>when the offer has to be submitted via OSCI-Transport, technical parameters used for delivery MUST be supplied here.
the offer submission via OSCI-Transport implies that offer withdrawals are to be sent via OSCI-Transport aswell.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element TenderSubmissionDetailsElectronical/minimumSignatureLevelContainer

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

complex

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:signatureLevelType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

The expected minimum level of signature certificate used for signature of the offer container (not the documents themself). A value of NONE means not to sign the container at all. All other values imply a signature over the offer xml file within the offer container.
This is purely for informational purposes. A Client (and/or its user) may decide to sign otherwise (or not at all). The decision about the legal implications/acceptance of the participation request is up to the Contracting Authority.

source

<xs:element name="minimumSignatureLevelContainer" type="xvergabe-cl:Code.SignatureLevelType">
<xs:annotation>
<xs:documentation>The expected minimum level of signature certificate used for signature of the offer container (not the documents themself). A value of NONE means not to sign the container at all. All other values imply a signature over the offer xml file within the offer container.
This is purely for informational purposes. A Client (and/or its user) may decide to sign otherwise (or not at all). The decision about the legal implications/acceptance of the participation request is up to the Contracting Authority.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderSubmissionDetailsElectronical/minimumSignatureLevelForWithdrawal

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

complex

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:signatureLevelType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xvergabe-docs:EncryptionKeyDetails

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

The expected minimum level of signature certificates with which offer withdrawals SHALL be signed. This is purely for informational purposes. A Client (and/or its user) may decide to sign otherwise (or not at all). The decision about the legal implications/acceptance of the withdrawal is up to the Contracting Authority.
When the asked-for signature level is not NONE, the client SHALL supply a signed document attached to the OfferWithdrawal-Message. The files' content is not in scope of this specification.

source

<xs:element name="minimumSignatureLevelForWithdrawal" type="xvergabe-cl:Code.SignatureLevelType">
<xs:annotation>
<xs:documentation>The expected minimum level of signature certificates with which offer withdrawals SHALL be signed. This is purely for informational purposes. A Client (and/or its user) may decide to sign otherwise (or not at all). The decision about the legal implications/acceptance of the withdrawal is up to the Contracting Authority.
When the asked-for signature level is not NONE, the client SHALL supply a signed document attached to the OfferWithdrawal-Message. The files' content is not in scope of this specification.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderSubmissionDetailsElectronical/onlyPrimaryContainerAllowed

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:boolean

properties

content

simple

annotation

documentation

flag indicating that the platform does not expect and allows a secondary offerContainer. the client MUST put all documents in the primary (and only) container.

source

<xs:element name="onlyPrimaryContainerAllowed" type="xs:boolean">
<xs:annotation>
<xs:documentation>flag indicating that the platform does not expect and allows a secondary offerContainer. the client MUST put all documents in the primary (and only) container.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderSubmissionDetailsElectronical/encryptionKey

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

minOcc	1
maxOcc	unbounded
content	complex

children

xvergabe-docs:credentialID xvergabe-docs:encryptionOrder

annotation

documentation

the encryptionKey(s) used to encrypt the offer.

source

<xs:element name="encryptionKey" type="xvergabe-docs:EncryptionKeyDetails" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>the encryptionKey(s) used to encrypt the offer.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderSubmissionDetailsElectronical/osciSubmission

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:TenderSubmissionDetailsOSCI

properties

minOcc	0
maxOcc	1
content	complex

children

annotation

documentation

when the offer has to be submitted via OSCI-Transport, technical parameters used for delivery MUST be supplied here.
the offer submission via OSCI-Transport implies that offer withdrawals are to be sent via OSCI-Transport aswell.

source

<xs:element name="osciSubmission" type="xvergabe-docs:TenderSubmissionDetailsOSCI" minOccurs="0">
<xs:annotation>
<xs:documentation>when the offer has to be submitted via OSCI-Transport, technical parameters used for delivery MUST be supplied here.
the offer submission via OSCI-Transport implies that offer withdrawals are to be sent via OSCI-Transport aswell.</xs:documentation>
</xs:annotation>
</xs:element>

complexType TenderSubmissionDetailsOSCI

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

annotation

documentation

Contains information about the submission of an offer or participation request via OSCI.

source

<xs:complexType name="TenderSubmissionDetailsOSCI">
<xs:annotation>
    <xs:documentation>Contains information about the submission of an offer or participation request via OSCI.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="intermediaryURI" type="xs:anyURI">
      <xs:annotation>
        <xs:documentation>URI of the OSCI intermediary to use.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="intermediaryPublicKeyReference" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>refernce to a credential object carried within this message holding the public key of the intermediary used for transportEncryption and Signature verification</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="addresseePublicKeyReference" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>identifier used as a reference to a credential object carried in the same message holding the adressees public key used for payload encryption and adressing purposes.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="useTransportEncryption" type="xs:boolean" default="true">
      <xs:annotation>
        <xs:documentation>flag indicating whether the OSCI message needs to be encrypted on transport level or if its sufficient to encrypt the payload for the addressee.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="intermediarySupportsCryptographicTimestamps" type="xs:boolean" default="true">
      <xs:annotation>
        <xs:documentation>indicator whether the OSCI intermediary supports cryptographic timestamps (timestamps which are signed). when true the intermediary MUST support deliveryRequests asking for cryptographic timestamps within the osci delivery receipt.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="verificationServiceURI" type="xs:anyURI" minOccurs="0">
      <xs:annotation>
        <xs:documentation>optional URI to a verificationService which might verify the clients certificate.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element TenderSubmissionDetailsOSCI/intermediaryURI

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:anyURI

properties

content

simple

annotation

documentation

URI of the OSCI intermediary to use.

source

<xs:element name="intermediaryURI" type="xs:anyURI">
<xs:annotation>
<xs:documentation>URI of the OSCI intermediary to use.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderSubmissionDetailsOSCI/intermediaryPublicKeyReference

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

refernce to a credential object carried within this message holding the public key of the intermediary used for transportEncryption and Signature verification

source

<xs:element name="intermediaryPublicKeyReference" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>refernce to a credential object carried within this message holding the public key of the intermediary used for transportEncryption and Signature verification</xs:documentation>
</xs:annotation>
</xs:element>

element TenderSubmissionDetailsOSCI/addresseePublicKeyReference

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:numberOfCopies xvergabe-docs:isBackup xvergabe-docs:includeElectronicalTenderDocuments

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

identifier used as a reference to a credential object carried in the same message holding the adressees public key used for payload encryption and adressing purposes.

source

<xs:element name="addresseePublicKeyReference" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>identifier used as a reference to a credential object carried in the same message holding the adressees public key used for payload encryption and adressing purposes.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderSubmissionDetailsOSCI/useTransportEncryption

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:boolean

properties

content	simple
default	true

annotation

documentation

flag indicating whether the OSCI message needs to be encrypted on transport level or if its sufficient to encrypt the payload for the addressee.

source

<xs:element name="useTransportEncryption" type="xs:boolean" default="true">
<xs:annotation>
<xs:documentation>flag indicating whether the OSCI message needs to be encrypted on transport level or if its sufficient to encrypt the payload for the addressee.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderSubmissionDetailsOSCI/intermediarySupportsCryptographicTimestamps

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:boolean

properties

content	simple
default	true

annotation

documentation

indicator whether the OSCI intermediary supports cryptographic timestamps (timestamps which are signed). when true the intermediary MUST support deliveryRequests asking for cryptographic timestamps within the osci delivery receipt.

source

<xs:element name="intermediarySupportsCryptographicTimestamps" type="xs:boolean" default="true">
<xs:annotation>
<xs:documentation>indicator whether the OSCI intermediary supports cryptographic timestamps (timestamps which are signed). when true the intermediary MUST support deliveryRequests asking for cryptographic timestamps within the osci delivery receipt.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderSubmissionDetailsOSCI/verificationServiceURI

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:anyURI

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

optional URI to a verificationService which might verify the clients certificate.

source

<xs:element name="verificationServiceURI" type="xs:anyURI" minOccurs="0">
<xs:annotation>
<xs:documentation>optional URI to a verificationService which might verify the clients certificate.</xs:documentation>
</xs:annotation>
</xs:element>

complexType TenderSubmissionDetailsPostal

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

annotation

documentation

Information about the postal submission formalities of the tendering procedure.

source

<xs:complexType name="TenderSubmissionDetailsPostal">
<xs:annotation>
    <xs:documentation>Information about the postal submission formalities of the tendering procedure.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="numberOfCopies" type="xs:nonNegativeInteger" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Specifies the number of copies to include in a postal submission.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="isBackup" type="xs:boolean">
      <xs:annotation>
        <xs:documentation>Specifies whether the postal submission is simply a backup to the electronical submission to be able to fall back in case of transmission errors.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="includeElectronicalTenderDocuments" type="xs:boolean">
      <xs:annotation>
        <xs:documentation>Specifies whether the offer documents must be included in electronical form even when submitting postal.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element TenderSubmissionDetailsPostal/numberOfCopies

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:nonNegativeInteger

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

Specifies the number of copies to include in a postal submission.

source

<xs:element name="numberOfCopies" type="xs:nonNegativeInteger" minOccurs="0">
<xs:annotation>
<xs:documentation>Specifies the number of copies to include in a postal submission.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderSubmissionDetailsPostal/isBackup

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:boolean

properties

content

simple

annotation

documentation

Specifies whether the postal submission is simply a backup to the electronical submission to be able to fall back in case of transmission errors.

source

<xs:element name="isBackup" type="xs:boolean">
<xs:annotation>
<xs:documentation>Specifies whether the postal submission is simply a backup to the electronical submission to be able to fall back in case of transmission errors.</xs:documentation>
</xs:annotation>
</xs:element>

element TenderSubmissionDetailsPostal/includeElectronicalTenderDocuments

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:boolean

properties

content

simple

annotation

documentation

Specifies whether the offer documents must be included in electronical form even when submitting postal.

source

<xs:element name="includeElectronicalTenderDocuments" type="xs:boolean">
<xs:annotation>
<xs:documentation>Specifies whether the offer documents must be included in electronical form even when submitting postal.</xs:documentation>
</xs:annotation>
</xs:element>

complexType TimeLimitType

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:timeLimitType xvergabe-docs:timeLimit

annotation

documentation

A time limit within the tendering procedure.

source

<xs:complexType name="TimeLimitType">
<xs:annotation>
    <xs:documentation>A time limit within the tendering procedure.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="timeLimitType" type="xvergabe-cl:Code.TimeLimitType">
      <xs:annotation>
        <xs:documentation>The type of the time limit.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="timeLimit" type="xvergabe-datatypes:DateTimeTZ">
      <xs:annotation>
        <xs:documentation>The date/timestamp of the time limit.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element TimeLimitType/timeLimitType

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-cl:Code.TimeLimitType

properties

content

complex

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:timeLimitType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

The type of the time limit.

source

<xs:element name="timeLimitType" type="xvergabe-cl:Code.TimeLimitType">
<xs:annotation>
<xs:documentation>The type of the time limit.</xs:documentation>
</xs:annotation>
</xs:element>

element TimeLimitType/timeLimit

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:targetFilename xvergabe-docs:targetExtension xvergabe-docs:targetMiMEType xvergabe-docs:targetProcessingApplicationURL

properties

content

simple

facets

Kind	Value	Annotation
pattern	([1-9][0-9]{3,}\|0[0-9]{3})-(0[1-9]\|1[0-2])-(0[1-9]\|[12][0-9]\|3[01])T(([01][0-9]\|2[0-3]):[0-5][0-9]:[0-5][0-9](\.[0-9]+)?\|(24:00:00(\.0+)?))(Z\|(\+\|-)((0[0-9]\|1[0-3]):[0-5][0-9]\|14:00))

annotation

documentation

The date/timestamp of the time limit.

source

<xs:element name="timeLimit" type="xvergabe-datatypes:DateTimeTZ">
<xs:annotation>
<xs:documentation>The date/timestamp of the time limit.</xs:documentation>
</xs:annotation>
</xs:element>

complexType TransformationDetails

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

annotation

documentation

Contains information about a transformation of a document which needs to be applied by the client/bidder for the offer/participation request.

source

<xs:complexType name="TransformationDetails">
<xs:annotation>
    <xs:documentation>Contains information about a transformation of a document which needs to be applied by the client/bidder for the offer/participation request.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="targetFilename" type="xvergabe-datatypes:String.255" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The expected filename of the document in the offer / participation request. Only applicable if the displayName of the providedDocument shall be different form the document name in the offer/participation request.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="targetExtension" type="xvergabe-datatypes:String.255" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The expected file extension of the document in the offer / participation request.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="targetMiMEType" type="xvergabe-datatypes:String.255" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The expected MIME type of the document in the offer / participation request.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="targetProcessingApplicationURL" type="xs:anyURI" minOccurs="0">
      <xs:annotation>
        <xs:documentation>URL used as identifier of the application that is needed to open the document after it has been transformed.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element TransformationDetails/targetFilename

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

The expected filename of the document in the offer / participation request. Only applicable if the displayName of the providedDocument shall be different form the document name in the offer/participation request.

source

<xs:element name="targetFilename" type="xvergabe-datatypes:String.255" minOccurs="0">
<xs:annotation>
<xs:documentation>The expected filename of the document in the offer / participation request. Only applicable if the displayName of the providedDocument shall be different form the document name in the offer/participation request.</xs:documentation>
</xs:annotation>
</xs:element>

element TransformationDetails/targetExtension

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

The expected file extension of the document in the offer / participation request.

source

<xs:element name="targetExtension" type="xvergabe-datatypes:String.255" minOccurs="0">
<xs:annotation>
<xs:documentation>The expected file extension of the document in the offer / participation request.</xs:documentation>
</xs:annotation>
</xs:element>

element TransformationDetails/targetMiMEType

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:limitType xvergabe-docs:limitValue

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

The expected MIME type of the document in the offer / participation request.

source

<xs:element name="targetMiMEType" type="xvergabe-datatypes:String.255" minOccurs="0">
<xs:annotation>
<xs:documentation>The expected MIME type of the document in the offer / participation request.</xs:documentation>
</xs:annotation>
</xs:element>

element TransformationDetails/targetProcessingApplicationURL

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:anyURI

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

URL used as identifier of the application that is needed to open the document after it has been transformed.

source

<xs:element name="targetProcessingApplicationURL" type="xs:anyURI" minOccurs="0">
<xs:annotation>
<xs:documentation>URL used as identifier of the application that is needed to open the document after it has been transformed.</xs:documentation>
</xs:annotation>
</xs:element>

complexType UploadLimit

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

annotation

documentation

A platform-specific upload limit limiting the size of various documents.

source

<xs:complexType name="UploadLimit">
<xs:annotation>
    <xs:documentation>A platform-specific upload limit limiting the size of various documents.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="limitType" type="xvergabe-cl:Code.UploadLimitType">
      <xs:annotation>
        <xs:documentation>The type of upload limit.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="limitValue" type="xs:nonNegativeInteger">
      <xs:annotation>
        <xs:documentation>The value of the upload limit without specifying a unit. The unit of the upload limit results from the limitType.
The limit when referring to size limits are referring to the gross size of the according artefact (eg. attachment). this means the size including all transformations (like base64) is referred to.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element UploadLimit/limitType

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-cl:Code.UploadLimitType

properties

content

complex

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:uploadLimitType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xvergabe-docs:OK xvergabe-docs:WARNING xvergabe-docs:ERROR xvergabe-docs:responseInformation xvergabe-docs:processedWithdrawalDetails xvergabe-docs:platformSpecificReceipt xvergabe-docs:platformSpecificReceiptReport

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

The type of upload limit.

source

<xs:element name="limitType" type="xvergabe-cl:Code.UploadLimitType">
<xs:annotation>
<xs:documentation>The type of upload limit.</xs:documentation>
</xs:annotation>
</xs:element>

element UploadLimit/limitValue

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xs:nonNegativeInteger

properties

content

simple

annotation

documentation

The value of the upload limit without specifying a unit. The unit of the upload limit results from the limitType.
The limit when referring to size limits are referring to the gross size of the according artefact (eg. attachment). this means the size including all transformations (like base64) is referred to.

source

<xs:element name="limitValue" type="xs:nonNegativeInteger">
<xs:annotation>
<xs:documentation>The value of the upload limit without specifying a unit. The unit of the upload limit results from the limitType.
The limit when referring to size limits are referring to the gross size of the according artefact (eg. attachment). this means the size including all transformations (like base64) is referred to.</xs:documentation>
</xs:annotation>
</xs:element>

complexType WithdrawalDeliveryReceiptDocumentType

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

extension of xvergabe-docs:ResponseDocumentType

properties

base	xvergabe-docs:ResponseDocumentType

children

annotation

documentation

A WithdrawalDeliveryReceipt is a receipt that is sent from server to client after the client has submitted a Withdrawal. This receipt confirms the successful processing of the withdrawal. The receipt repeats the processing details given by the client and enriches them with the ID the server assigned to the Withdrawal document.
The receipt includes the Response-Informations given in the messagecontext for delivery of said information in other contexts. So when the DeliveryReceipt is to be exchanged synchronously it MUST include the same Responseinformations twice: once on the messagelevel and once again in the document level.

source

<xs:complexType name="WithdrawalDeliveryReceiptDocumentType">
<xs:annotation>
    <xs:documentation>A WithdrawalDeliveryReceipt is a receipt that is sent from server to client after the client has submitted a Withdrawal. This receipt confirms the successful processing of the withdrawal. The receipt repeats the processing details given by the client and enriches them with the ID the server assigned to the Withdrawal document.
The receipt includes the Response-Informations given in the messagecontext for delivery of said information in other contexts. So when the DeliveryReceipt is to be exchanged synchronously it MUST include the same Responseinformations twice: once on the messagelevel and once again in the document level.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-docs:ResponseDocumentType">
      <xs:sequence>
        <xs:element name="processedWithdrawalDetails" type="xvergabe-docs:ProcessedWithdrawalDetails"/>
        <xs:element name="platformSpecificReceipt" type="xvergabe-datatypes:ExistingObjectReference" minOccurs="0"/>
        <xs:element name="platformSpecificReceiptReport" type="xvergabe-datatypes:ExistingObjectReference">
          <xs:annotation>
            <xs:documentation>Contains a platform-specific report of the receipt in a user-readable format chosen by the platform (pdf, html, ...). This report may for example be directly displayed in the bidder client. When present, the platform MUST make the referenced platformSpecificReceiptReport available through the getDocuments()-operation</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element WithdrawalDeliveryReceiptDocumentType/processedWithdrawalDetails

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-docs:ProcessedWithdrawalDetails

properties

content

complex

children

xvergabe-docs:withdrawalMessageID xvergabe-docs:withdrawalReceivedDateTime xvergabe-docs:withdrawalReceivedInTime

source

<xs:element name="processedWithdrawalDetails" type="xvergabe-docs:ProcessedWithdrawalDetails"/>

element WithdrawalDeliveryReceiptDocumentType/platformSpecificReceipt

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-datatypes:name xvergabe-datatypes:fileSize xvergabe-datatypes:attachmentIdentifier

properties

minOcc	0
maxOcc	1
content	complex

children

source

<xs:element name="platformSpecificReceipt" type="xvergabe-datatypes:ExistingObjectReference" minOccurs="0"/>

element WithdrawalDeliveryReceiptDocumentType/platformSpecificReceiptReport

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-datatypes:name xvergabe-datatypes:fileSize xvergabe-datatypes:attachmentIdentifier

properties

content

complex

children

annotation

documentation

Contains a platform-specific report of the receipt in a user-readable format chosen by the platform (pdf, html, ...). This report may for example be directly displayed in the bidder client. When present, the platform MUST make the referenced platformSpecificReceiptReport available through the getDocuments()-operation

source

<xs:element name="platformSpecificReceiptReport" type="xvergabe-datatypes:ExistingObjectReference">
<xs:annotation>
<xs:documentation>Contains a platform-specific report of the receipt in a user-readable format chosen by the platform (pdf, html, ...). This report may for example be directly displayed in the bidder client. When present, the platform MUST make the referenced platformSpecificReceiptReport available through the getDocuments()-operation</xs:documentation>
</xs:annotation>
</xs:element>

complexType WithdrawalDocumentType

diagram

namespace

http://xvergabe.org/documents/xsd/4

children

xvergabe-docs:objectIDToWithdraw xvergabe-docs:withdrawalReason xvergabe-docs:withdrawalDateTime

annotation

documentation

A Withdrawal document contains the intention of a client to withdraw a previously submitted offer or participation request.

source

<xs:complexType name="WithdrawalDocumentType">
<xs:annotation>
    <xs:documentation>A Withdrawal document contains the intention of a client to withdraw a previously submitted offer or participation request.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="objectIDToWithdraw" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>the processedOfferID or processedParticipationID to withdraw given out by the platform to the economic operator in the offerDeliveryReceipt or participationDeliveryReceipt.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="withdrawalReason" type="xvergabe-datatypes:String.4096" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The reasons for the withdrawal.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="withdrawalDateTime" type="xvergabe-datatypes:DateTimeTZ">
      <xs:annotation>
        <xs:documentation>The date and time of the withdrawal.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element WithdrawalDocumentType/objectIDToWithdraw

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

the processedOfferID or processedParticipationID to withdraw given out by the platform to the economic operator in the offerDeliveryReceipt or participationDeliveryReceipt.

source

<xs:element name="objectIDToWithdraw" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>the processedOfferID or processedParticipationID to withdraw given out by the platform to the economic operator in the offerDeliveryReceipt or participationDeliveryReceipt.</xs:documentation>
</xs:annotation>
</xs:element>

element WithdrawalDocumentType/withdrawalReason

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

The reasons for the withdrawal.

source

<xs:element name="withdrawalReason" type="xvergabe-datatypes:String.4096" minOccurs="0">
<xs:annotation>
<xs:documentation>The reasons for the withdrawal.</xs:documentation>
</xs:annotation>
</xs:element>

element WithdrawalDocumentType/withdrawalDateTime

diagram

namespace

http://xvergabe.org/documents/xsd/4

type

xvergabe-if:attachmentID xvergabe-if:filename xvergabe-if:description xvergabe-if:attachmentData xvergabe-if:signature

properties

content

simple

facets

Kind	Value	Annotation
pattern	([1-9][0-9]{3,}\|0[0-9]{3})-(0[1-9]\|1[0-2])-(0[1-9]\|[12][0-9]\|3[01])T(([01][0-9]\|2[0-3]):[0-5][0-9]:[0-5][0-9](\.[0-9]+)?\|(24:00:00(\.0+)?))(Z\|(\+\|-)((0[0-9]\|1[0-3]):[0-5][0-9]\|14:00))

annotation

documentation

The date and time of the withdrawal.

source

<xs:element name="withdrawalDateTime" type="xvergabe-datatypes:DateTimeTZ">
<xs:annotation>
<xs:documentation>The date and time of the withdrawal.</xs:documentation>
</xs:annotation>
</xs:element>

element messages.Attachment

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

extension of xvergabe-if:Attachment

properties

content

complex

children

annotation

documentation

Possible root element containing a message of type Attachment. This element is not strictly necessary but is a restriction to be XÖV compliant.

source

<xs:element name="messages.Attachment">
<xs:annotation>
    <xs:documentation>Possible root element containing a message of type Attachment. This element is not strictly necessary but is a restriction to be XÖV compliant.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:complexContent>
      <xs:extension base="xvergabe-if:Attachment"/>
    </xs:complexContent>
</xs:complexType>
</xs:element>

element messages.ClientInquiry

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

extension of xvergabe-if:ClientInquiryMessageType

properties

content

complex

children

xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment

annotation

documentation

Possible root element containing a message of type ClientInquiryMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.

source

<xs:element name="messages.ClientInquiry">
<xs:annotation>
    <xs:documentation>Possible root element containing a message of type ClientInquiryMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:complexContent>
      <xs:extension base="xvergabe-if:ClientInquiryMessageType"/>
    </xs:complexContent>
</xs:complexType>
</xs:element>

element messages.InvitationToParticipation

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

extension of xvergabe-if:InvitationToParticipationMessageType

properties

content

complex

children

annotation

documentation

Possible root element containing a message of type InvitationToParticipationMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.

source

<xs:element name="messages.InvitationToParticipation">
<xs:annotation>
    <xs:documentation>Possible root element containing a message of type InvitationToParticipationMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:complexContent>
      <xs:extension base="xvergabe-if:InvitationToParticipationMessageType"/>
    </xs:complexContent>
</xs:complexType>
</xs:element>

element messages.InvitationToTender

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

extension of xvergabe-if:InvitationToTenderMessageType

properties

content

complex

children

xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment

annotation

documentation

Possible root element containing a message of type InvitationToTenderMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.

source

<xs:element name="messages.InvitationToTender">
<xs:annotation>
    <xs:documentation>Possible root element containing a message of type InvitationToTenderMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:complexContent>
      <xs:extension base="xvergabe-if:InvitationToTenderMessageType"/>
    </xs:complexContent>
</xs:complexType>
</xs:element>

element messages.Offer

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

extension of xvergabe-if:OfferMessageType

properties

content

complex

children

annotation

documentation

Possible root element containing a message of type OfferMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.

source

<xs:element name="messages.Offer">
<xs:annotation>
    <xs:documentation>Possible root element containing a message of type OfferMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:complexContent>
      <xs:extension base="xvergabe-if:OfferMessageType"/>
    </xs:complexContent>
</xs:complexType>
</xs:element>

element messages.OfferDeliveryReceipt

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

extension of xvergabe-if:OfferDeliveryReceiptMessageType

properties

content

complex

children

xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment

annotation

documentation

Possible root element containing a message of type OfferDeliveryReceiptMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.

source

<xs:element name="messages.OfferDeliveryReceipt">
<xs:annotation>
    <xs:documentation>Possible root element containing a message of type OfferDeliveryReceiptMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:complexContent>
      <xs:extension base="xvergabe-if:OfferDeliveryReceiptMessageType"/>
    </xs:complexContent>
</xs:complexType>
</xs:element>

element messages.OfferWithdrawal

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

extension of xvergabe-if:OfferWithdrawalMessageType

properties

content

complex

children

annotation

documentation

Possible root element containing a message of typeOfferWithdrawalMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.

source

<xs:element name="messages.OfferWithdrawal">
<xs:annotation>
    <xs:documentation>Possible root element containing a message of typeOfferWithdrawalMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:complexContent>
      <xs:extension base="xvergabe-if:OfferWithdrawalMessageType"/>
    </xs:complexContent>
</xs:complexType>
</xs:element>

element messages.OfferWithdrawalDeliveryReceipt

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

extension of xvergabe-if:OfferWithdrawalDeliveryReceiptMessageType

properties

content

complex

children

xvergabe-if:messageHeader xvergabe-if:offer xvergabe-if:participationRequest xvergabe-if:withdrawal

annotation

documentation

Possible root element containing a message of type OfferWithdrawalDeliveryReceiptMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.

source

<xs:element name="messages.OfferWithdrawalDeliveryReceipt">
<xs:annotation>
    <xs:documentation>Possible root element containing a message of type OfferWithdrawalDeliveryReceiptMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:complexContent>
      <xs:extension base="xvergabe-if:OfferWithdrawalDeliveryReceiptMessageType"/>
    </xs:complexContent>
</xs:complexType>
</xs:element>

element messages.OSCITransferID

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

extension of xvergabe-if:OSCITransferIDRequestType

properties

content

complex

children

annotation

documentation

Possible root element containing a message of type OSCITransferIDRequestType. This element is not strictly necessary but is a restriction to be XÖV compliant.

source

<xs:element name="messages.OSCITransferID">
<xs:annotation>
    <xs:documentation>Possible root element containing a message of type OSCITransferIDRequestType. This element is not strictly necessary but is a restriction to be XÖV compliant.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:complexContent>
      <xs:extension base="xvergabe-if:OSCITransferIDRequestType"/>
    </xs:complexContent>
</xs:complexType>
</xs:element>

element messages.Participation

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

extension of xvergabe-if:ParticipationMessageType

properties

content

complex

children

xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment

annotation

documentation

Possible root element containing a message of type ParticipationMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.

source

<xs:element name="messages.Participation">
<xs:annotation>
    <xs:documentation>Possible root element containing a message of type ParticipationMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:complexContent>
      <xs:extension base="xvergabe-if:ParticipationMessageType"/>
    </xs:complexContent>
</xs:complexType>
</xs:element>

element messages.ParticipationDeliveryReceipt

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

extension of xvergabe-if:ParticipationDeliveryReceiptMessageType

properties

content

complex

children

xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment

annotation

documentation

Possible root element containing a message of type ParticipationDeliveryReceiptMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.

source

<xs:element name="messages.ParticipationDeliveryReceipt">
<xs:annotation>
    <xs:documentation>Possible root element containing a message of type ParticipationDeliveryReceiptMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:complexContent>
      <xs:extension base="xvergabe-if:ParticipationDeliveryReceiptMessageType"/>
    </xs:complexContent>
</xs:complexType>
</xs:element>

element messages.ParticipationWithdrawal

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

extension of xvergabe-if:ParticipationWithdrawalMessageType

properties

content

complex

children

annotation

documentation

Possible root element containing a message of type ParticipationWithdrawalMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.

source

<xs:element name="messages.ParticipationWithdrawal">
<xs:annotation>
    <xs:documentation>Possible root element containing a message of type ParticipationWithdrawalMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:complexContent>
      <xs:extension base="xvergabe-if:ParticipationWithdrawalMessageType"/>
    </xs:complexContent>
</xs:complexType>
</xs:element>

element messages.ParticipationWithdrawalDeliveryReceipt

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

extension of xvergabe-if:ParticipationWithdrawalDeliveryReceiptMessageType

properties

content

complex

children

annotation

documentation

Possible root element containing a message of type ParticipationWithdrawalDeliveryReceiptMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.

source

<xs:element name="messages.ParticipationWithdrawalDeliveryReceipt">
<xs:annotation>
    <xs:documentation>Possible root element containing a message of type ParticipationWithdrawalDeliveryReceiptMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:complexContent>
      <xs:extension base="xvergabe-if:ParticipationWithdrawalDeliveryReceiptMessageType"/>
    </xs:complexContent>
</xs:complexType>
</xs:element>

element messages.ResultNotice

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

extension of xvergabe-if:ResultNoticeMessageType

properties

content

complex

children

annotation

documentation

Possible root element containing a message of type ResultNoticeMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.

source

<xs:element name="messages.ResultNotice">
<xs:annotation>
    <xs:documentation>Possible root element containing a message of type ResultNoticeMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:complexContent>
      <xs:extension base="xvergabe-if:ResultNoticeMessageType"/>
    </xs:complexContent>
</xs:complexType>
</xs:element>

element messages.ServerInquiry

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

extension of xvergabe-if:ServerInquiryMessageType

properties

content

complex

children

annotation

documentation

Possible root element containing a message of type ServerInquiryMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.

source

<xs:element name="messages.ServerInquiry">
<xs:annotation>
    <xs:documentation>Possible root element containing a message of type ServerInquiryMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:complexContent>
      <xs:extension base="xvergabe-if:ServerInquiryMessageType"/>
    </xs:complexContent>
</xs:complexType>
</xs:element>

element messages.TenderMetaInformation

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

extension of xvergabe-if:TenderMetaInformationMessageType

properties

content

complex

children

xvergabe-if:messageHeader

annotation

documentation

Possible root element containing a message of type TenderMetaInformationMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.

source

<xs:element name="messages.TenderMetaInformation">
<xs:annotation>
    <xs:documentation>Possible root element containing a message of type TenderMetaInformationMessageType. This element is not strictly necessary but is a restriction to be XÖV compliant.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:complexContent>
      <xs:extension base="xvergabe-if:TenderMetaInformationMessageType"/>
    </xs:complexContent>
</xs:complexType>
</xs:element>

complexType AbstractClientMessage

diagram

namespace

http://xvergabe.org/interface/xsd/4

properties

abstract

true

children

annotation

documentation

Extension point for all messages that are sent from client to server. The main difference to AbstractServerMessage is that this message type may contain attachments.

source

<xs:complexType name="AbstractClientMessage" abstract="true">
<xs:annotation>
    <xs:documentation>Extension point for all messages that are sent from client to server. The main difference to AbstractServerMessage is that this message type may contain attachments.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="messageHeader" type="xvergabe-if:MessageHeader">
      <xs:annotation>
        <xs:documentation>Meta data of a message. This meta data mainly serves to identify sender and receiver of a message and to make it possible for client and server to match the message to their database.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element AbstractClientMessage/messageHeader

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:MessageHeader

properties

content

complex

children

xvergabe-if:tenderingProcedureID xvergabe-if:messageInfo xvergabe-if:senderInfo xvergabe-if:credentialItem

annotation

documentation

Meta data of a message. This meta data mainly serves to identify sender and receiver of a message and to make it possible for client and server to match the message to their database.

source

<xs:element name="messageHeader" type="xvergabe-if:MessageHeader">
<xs:annotation>
<xs:documentation>Meta data of a message. This meta data mainly serves to identify sender and receiver of a message and to make it possible for client and server to match the message to their database.</xs:documentation>
</xs:annotation>
</xs:element>

complexType AbstractServerMessage

diagram

namespace

http://xvergabe.org/interface/xsd/4

properties

abstract

true

children

xvergabe-if:messageHeader

annotation

documentation

This is the extension point for all messages that are sent from the server to a client. The main difference to AbstractClientMessage is, that no attachments are allowed, since the client get access attachments via the getDocuments operation.

source

<xs:complexType name="AbstractServerMessage" abstract="true">
<xs:annotation>
    <xs:documentation>This is the extension point for all messages that are sent from the server to a client. The main difference to AbstractClientMessage is, that no attachments are allowed, since the client get access attachments via the getDocuments operation.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="messageHeader" type="xvergabe-if:MessageHeader">
      <xs:annotation>
        <xs:documentation>Header that contains meta information about a message.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element AbstractServerMessage/messageHeader

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:MessageHeader

properties

content

complex

children

xvergabe-if:tenderingProcedureID xvergabe-if:messageInfo xvergabe-if:senderInfo xvergabe-if:credentialItem

annotation

documentation

Header that contains meta information about a message.

source

<xs:element name="messageHeader" type="xvergabe-if:MessageHeader">
<xs:annotation>
<xs:documentation>Header that contains meta information about a message.</xs:documentation>
</xs:annotation>
</xs:element>

complexType Attachment

diagram

namespace

http://xvergabe.org/interface/xsd/4

children

xvergabe-if:attachmentID xvergabe-if:filename xvergabe-if:description xvergabe-if:attachmentData xvergabe-if:signature

annotation

documentation

Attachment to a message / document. An attachment can either be plain (unencrypted) or encrypted and contains the data itself and some meta data.

source

<xs:complexType name="Attachment">
<xs:annotation>
    <xs:documentation>Attachment to a message / document. An attachment can either be plain (unencrypted) or encrypted and contains the data itself and some meta data.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="attachmentID" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>Unique identifier for an attachment. By this identifier the attachment can be referenced from other contexts</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="filename" type="xvergabe-datatypes:String.255">
      <xs:annotation>
        <xs:documentation>Full file name including the file extension.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="description" type="xvergabe-datatypes:String.1024" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Textual description of the attachment.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="attachmentData" type="xvergabe-mtom:AttachmentMIMEType">
      <xs:annotation>
        <xs:documentation>attachment data (the file itself). for encrypted attachments this MUST be PKCS#7 content.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="signature" type="xvergabe-datatypes:XMLSignature" minOccurs="0">
      <xs:annotation>
        <xs:documentation>optional signature of the attachment.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element Attachment/attachmentID

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

Unique identifier for an attachment. By this identifier the attachment can be referenced from other contexts

source

<xs:element name="attachmentID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>Unique identifier for an attachment. By this identifier the attachment can be referenced from other contexts</xs:documentation>
</xs:annotation>
</xs:element>

element Attachment/filename

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

simple

annotation

documentation

Full file name including the file extension.

source

<xs:element name="filename" type="xvergabe-datatypes:String.255">
<xs:annotation>
<xs:documentation>Full file name including the file extension.</xs:documentation>
</xs:annotation>
</xs:element>

element Attachment/description

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-mtom:AttachmentMIMEType

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

Textual description of the attachment.

source

<xs:element name="description" type="xvergabe-datatypes:String.1024" minOccurs="0">
<xs:annotation>
<xs:documentation>Textual description of the attachment.</xs:documentation>
</xs:annotation>
</xs:element>

element Attachment/attachmentData

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

complex

children

xvergabe-mtom:attachmentMTOM

annotation

documentation

attachment data (the file itself). for encrypted attachments this MUST be PKCS#7 content.

source

<xs:element name="attachmentData" type="xvergabe-mtom:AttachmentMIMEType">
<xs:annotation>
<xs:documentation>attachment data (the file itself). for encrypted attachments this MUST be PKCS#7 content.</xs:documentation>
</xs:annotation>
</xs:element>

element Attachment/signature

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-datatypes:XMLSignature

properties

minOcc	0
maxOcc	1
content	complex

annotation

documentation

optional signature of the attachment.

source

<xs:element name="signature" type="xvergabe-datatypes:XMLSignature" minOccurs="0">
<xs:annotation>
<xs:documentation>optional signature of the attachment.</xs:documentation>
</xs:annotation>
</xs:element>

complexType ClientInquiryMessageType

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment

properties

base	xvergabe-if:AbstractClientMessage

children

annotation

documentation

Message that contains an inquiry (or an answer to an inquiry) that is sent from client to server.

source

<xs:complexType name="ClientInquiryMessageType">
<xs:annotation>
    <xs:documentation>Message that contains an inquiry (or an answer to an inquiry) that is sent from client to server.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if:AbstractClientMessage">
      <xs:sequence>
        <xs:element name="document" type="xvergabe-docs:InquiryDocumentType">
          <xs:annotation>
            <xs:documentation>An InquiryDocument serves as vessel for general inquiries and answers that can be sent from client to server and vice versa. An inquiry can reference a previously exchanged document.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="attachment" type="xvergabe-if:Attachment" minOccurs="0" maxOccurs="unbounded">
          <xs:annotation>
            <xs:documentation>attachment to the inquiry. when given it needs to be referenced from the inquirydocument within.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element ClientInquiryMessageType/document

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-docs:InquiryDocumentType

properties

content

complex

children

annotation

documentation

An InquiryDocument serves as vessel for general inquiries and answers that can be sent from client to server and vice versa. An inquiry can reference a previously exchanged document.

source

<xs:element name="document" type="xvergabe-docs:InquiryDocumentType">
<xs:annotation>
<xs:documentation>An InquiryDocument serves as vessel for general inquiries and answers that can be sent from client to server and vice versa. An inquiry can reference a previously exchanged document.</xs:documentation>
</xs:annotation>
</xs:element>

element ClientInquiryMessageType/attachment

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:attachmentID xvergabe-if:filename xvergabe-if:description xvergabe-if:attachmentData xvergabe-if:signature

properties

minOcc	0
maxOcc	unbounded
content	complex

children

annotation

documentation

attachment to the inquiry. when given it needs to be referenced from the inquirydocument within.

source

<xs:element name="attachment" type="xvergabe-if:Attachment" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>attachment to the inquiry. when given it needs to be referenced from the inquirydocument within.</xs:documentation>
</xs:annotation>
</xs:element>

complexType CredentialItem

diagram

namespace

http://xvergabe.org/interface/xsd/4

children

xvergabe-if:credentialID xvergabe-if:usage xvergabe-if:credentialData

annotation

documentation

Data that is needed for security-relevant processing of the message (encryption, decryption, signing, signature validation, authentication). Format of the credentialData MUST be DER-encrypted certificate.

source

<xs:complexType name="CredentialItem">
<xs:annotation>
    <xs:documentation>Data that is needed for security-relevant processing of the message (encryption, decryption, signing, signature validation, authentication). Format of the credentialData MUST be DER-encrypted certificate.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="credentialID" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>Unique Identifier for the credential item so it can be referenced from other contexts.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="usage" type="xvergabe-cl:Code.CredentialUsage" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>The task the credential data is to be used for.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="credentialData" type="xvergabe-mtom:AttachmentMIMEType">
      <xs:annotation>
        <xs:documentation>the base64 encoded data of the credential, e.g. bas64 encoded x509-cert. Format of the data MUST be a DER-encoded certificate. So the credentialdata is a base64 encoded representation of a DER-encoded bytestream representing a certificate.</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element CredentialItem/credentialID

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-cl:Code.CredentialUsage

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

Unique Identifier for the credential item so it can be referenced from other contexts.

source

<xs:element name="credentialID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>Unique Identifier for the credential item so it can be referenced from other contexts.</xs:documentation>
</xs:annotation>
</xs:element>

element CredentialItem/usage

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

minOcc	1
maxOcc	unbounded
content	complex

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:credentialusage

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xvergabe-mtom:AttachmentMIMEType

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

The task the credential data is to be used for.

source

<xs:element name="usage" type="xvergabe-cl:Code.CredentialUsage" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>The task the credential data is to be used for.</xs:documentation>
</xs:annotation>
</xs:element>

element CredentialItem/credentialData

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

complex

children

xvergabe-mtom:attachmentMTOM

annotation

documentation

the base64 encoded data of the credential, e.g. bas64 encoded x509-cert. Format of the data MUST be a DER-encoded certificate. So the credentialdata is a base64 encoded representation of a DER-encoded bytestream representing a certificate.

source

<xs:element name="credentialData" type="xvergabe-mtom:AttachmentMIMEType">
<xs:annotation>
<xs:documentation>the base64 encoded data of the credential, e.g. bas64 encoded x509-cert. Format of the data MUST be a DER-encoded certificate. So the credentialdata is a base64 encoded representation of a DER-encoded bytestream representing a certificate.</xs:documentation>
</xs:annotation>
</xs:element>

complexType InvitationToParticipationMessageType

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

base	xvergabe-if:AbstractServerMessage

children

xvergabe-docs:InvitationToParticipationDocumentType

annotation

documentation

Message that contains an invitation to participation along with the participation documents that is sent from server to client.

source

<xs:complexType name="InvitationToParticipationMessageType">
<xs:annotation>
    <xs:documentation>Message that contains an invitation to participation along with the participation documents that is sent from server to client.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if:AbstractServerMessage">
      <xs:sequence>
        <xs:element name="document" type="xvergabe-docs:InvitationToParticipationDocumentType">
          <xs:annotation>
            <xs:documentation>An InvitationToParticipation contains the documents and meta data needed for bidder to be able to submit a request to participate in a tendering procedure with participation contest. The participation documents are not included directly in this document but instead their GUIDs are referenced, so that a client can call the getDocument operation to download these documents. An InvitationToParticipation can be sent to the same client multiple times if the participation documents change. Each InvitationToParticipation SHOULD then contain a FULL set of the participation documents. A client can determine which tendering documents he still has to download by comparing the GUIDs of the referenced documents.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element InvitationToParticipationMessageType/document

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

complex

children

xvergabe-docs:submissionDetails xvergabe-docs:participationDocument

annotation

documentation

An InvitationToParticipation contains the documents and meta data needed for bidder to be able to submit a request to participate in a tendering procedure with participation contest. The participation documents are not included directly in this document but instead their GUIDs are referenced, so that a client can call the getDocument operation to download these documents. An InvitationToParticipation can be sent to the same client multiple times if the participation documents change. Each InvitationToParticipation SHOULD then contain a FULL set of the participation documents. A client can determine which tendering documents he still has to download by comparing the GUIDs of the referenced documents.

source

<xs:element name="document" type="xvergabe-docs:InvitationToParticipationDocumentType">
<xs:annotation>
<xs:documentation>An InvitationToParticipation contains the documents and meta data needed for bidder to be able to submit a request to participate in a tendering procedure with participation contest. The participation documents are not included directly in this document but instead their GUIDs are referenced, so that a client can call the getDocument operation to download these documents. An InvitationToParticipation can be sent to the same client multiple times if the participation documents change. Each InvitationToParticipation SHOULD then contain a FULL set of the participation documents. A client can determine which tendering documents he still has to download by comparing the GUIDs of the referenced documents.</xs:documentation>
</xs:annotation>
</xs:element>

complexType InvitationToTenderMessageType

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

base	xvergabe-if:AbstractServerMessage

children

xvergabe-docs:InvitationToTenderDocumentType

annotation

documentation

Message that contains an invitation to a tendering procedure (a request to submit an offer) along with the tendering documents that is sent from server to client.

source

<xs:complexType name="InvitationToTenderMessageType">
<xs:annotation>
    <xs:documentation>Message that contains an invitation to a tendering procedure (a request to submit an offer) along with the tendering documents that is sent from server to client.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if:AbstractServerMessage">
      <xs:sequence>
        <xs:element name="document" type="xvergabe-docs:InvitationToTenderDocumentType">
          <xs:annotation>
            <xs:documentation>An InvitationToTender contains the tendering documents necessary for a bidder to submit an offer to a tendering procedure. The tendering documents are not included directly in this document but instead their GUIDs are referenced, so that a client can call the getDocument operation to download these documents. The tendering documents are divided in documents that must be returned as part of an offer, documents that must be transformed and returned as part of an offer and documents that the bidder provides without being explicitly requested to do so. An InvitationToTender can be sent to the same client multiple times if the tendering documents change. Each InvitationToTender SHOULD then contain a FULL set of the tendering documents. A client can determine which tendering documents he still has to download by comparing the GUIDs of the referenced documents.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element InvitationToTenderMessageType/document

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

complex

children

xvergabe-docs:lot xvergabe-docs:negotiationRound xvergabe-docs:tenderSubmissionDetails xvergabe-docs:tenderDocument

annotation

documentation

An InvitationToTender contains the tendering documents necessary for a bidder to submit an offer to a tendering procedure. The tendering documents are not included directly in this document but instead their GUIDs are referenced, so that a client can call the getDocument operation to download these documents. The tendering documents are divided in documents that must be returned as part of an offer, documents that must be transformed and returned as part of an offer and documents that the bidder provides without being explicitly requested to do so. An InvitationToTender can be sent to the same client multiple times if the tendering documents change. Each InvitationToTender SHOULD then contain a FULL set of the tendering documents. A client can determine which tendering documents he still has to download by comparing the GUIDs of the referenced documents.

source

<xs:element name="document" type="xvergabe-docs:InvitationToTenderDocumentType">
<xs:annotation>
<xs:documentation>An InvitationToTender contains the tendering documents necessary for a bidder to submit an offer to a tendering procedure. The tendering documents are not included directly in this document but instead their GUIDs are referenced, so that a client can call the getDocument operation to download these documents. The tendering documents are divided in documents that must be returned as part of an offer, documents that must be transformed and returned as part of an offer and documents that the bidder provides without being explicitly requested to do so. An InvitationToTender can be sent to the same client multiple times if the tendering documents change. Each InvitationToTender SHOULD then contain a FULL set of the tendering documents. A client can determine which tendering documents he still has to download by comparing the GUIDs of the referenced documents.</xs:documentation>
</xs:annotation>
</xs:element>

complexType MessageHeader

diagram

namespace

http://xvergabe.org/interface/xsd/4

children

xvergabe-if:tenderingProcedureID xvergabe-if:messageInfo xvergabe-if:senderInfo xvergabe-if:credentialItem

annotation

documentation

Header that contains meta information about a message.

source

<xs:complexType name="MessageHeader">
<xs:annotation>
    <xs:documentation>Header that contains meta information about a message.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="tenderingProcedureID" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>this ID identifies the procedure the message is being sent for (or in).</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="messageInfo" type="xvergabe-if:MessageInfo">
      <xs:annotation>
        <xs:documentation>information about the message</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="senderInfo" type="xvergabe-if:SenderInfo">
      <xs:annotation>
        <xs:documentation>information about the sender and the sending application</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="credentialItem" type="xvergabe-if:CredentialItem" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>

element MessageHeader/tenderingProcedureID

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:messageID xvergabe-if:issueDateTime

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

this ID identifies the procedure the message is being sent for (or in).

source

<xs:element name="tenderingProcedureID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>this ID identifies the procedure the message is being sent for (or in).</xs:documentation>
</xs:annotation>
</xs:element>

element MessageHeader/messageInfo

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:MessageInfo

properties

content

complex

children

annotation

documentation

information about the message

source

<xs:element name="messageInfo" type="xvergabe-if:MessageInfo">
<xs:annotation>
<xs:documentation>information about the message</xs:documentation>
</xs:annotation>
</xs:element>

element MessageHeader/senderInfo

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:SenderInfo

properties

content

complex

children

xvergabe-if:senderName xvergabe-if:vendor xvergabe-if:product xvergabe-if:productVersion xvergabe-if:productInstance xvergabe-if:supportURL

annotation

documentation

information about the sender and the sending application

source

<xs:element name="senderInfo" type="xvergabe-if:SenderInfo">
<xs:annotation>
<xs:documentation>information about the sender and the sending application</xs:documentation>
</xs:annotation>
</xs:element>

element MessageHeader/credentialItem

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:CredentialItem

properties

minOcc	0
maxOcc	unbounded
content	complex

children

xvergabe-if:credentialID xvergabe-if:usage xvergabe-if:credentialData

source

<xs:element name="credentialItem" type="xvergabe-if:CredentialItem" minOccurs="0" maxOccurs="unbounded"/>

complexType MessageInfo

diagram

namespace

http://xvergabe.org/interface/xsd/4

children

xvergabe-if:messageID xvergabe-if:issueDateTime

annotation

documentation

Basic information about a message.

source

<xs:complexType name="MessageInfo">
<xs:annotation>
    <xs:documentation>Basic information about a message.</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="messageID" type="xvergabe-datatypes:GUID">
      <xs:annotation>
        <xs:documentation>ID of the message given by the sending application</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="issueDateTime" type="xvergabe-datatypes:DateTimeTZ">
      <xs:annotation>
        <xs:documentation>timestamp when the message has been issued/created by the sending application</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element MessageInfo/messageID

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

ID of the message given by the sending application

source

<xs:element name="messageID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>ID of the message given by the sending application</xs:documentation>
</xs:annotation>
</xs:element>

element MessageInfo/issueDateTime

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	([1-9][0-9]{3,}\|0[0-9]{3})-(0[1-9]\|1[0-2])-(0[1-9]\|[12][0-9]\|3[01])T(([01][0-9]\|2[0-3]):[0-5][0-9]:[0-5][0-9](\.[0-9]+)?\|(24:00:00(\.0+)?))(Z\|(\+\|-)((0[0-9]\|1[0-3]):[0-5][0-9]\|14:00))

annotation

documentation

timestamp when the message has been issued/created by the sending application

source

<xs:element name="issueDateTime" type="xvergabe-datatypes:DateTimeTZ">
<xs:annotation>
<xs:documentation>timestamp when the message has been issued/created by the sending application</xs:documentation>
</xs:annotation>
</xs:element>

complexType OfferDeliveryReceiptMessageType

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

base	xvergabe-if:AbstractServerMessage

children

xvergabe-docs:OfferDeliveryReceiptDocumentType

annotation

documentation

Message that contains a delivery receipt to a submitted offer that is sent from server to client.

source

<xs:complexType name="OfferDeliveryReceiptMessageType">
<xs:annotation>
    <xs:documentation>Message that contains a delivery receipt to a submitted offer that is sent from server to client.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if:AbstractServerMessage">
      <xs:sequence>
        <xs:element name="document" type="xvergabe-docs:OfferDeliveryReceiptDocumentType">
          <xs:annotation>
            <xs:documentation>An OfferDeliveryReceipt is a receipt that is sent from server to client after the client has submitted an offer. This receipt confirms the successful processing of the offer. The receipt repeats the processing details given by the client and enriches them with the ID the server assigned to the offer.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element OfferDeliveryReceiptMessageType/document

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

complex

children

annotation

documentation

source

<xs:element name="document" type="xvergabe-docs:OfferDeliveryReceiptDocumentType">
<xs:annotation>
<xs:documentation>An OfferDeliveryReceipt is a receipt that is sent from server to client after the client has submitted an offer. This receipt confirms the successful processing of the offer. The receipt repeats the processing details given by the client and enriches them with the ID the server assigned to the offer.</xs:documentation>
</xs:annotation>
</xs:element>

complexType OfferMessageType

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment

properties

base	xvergabe-if:AbstractClientMessage

children

annotation

documentation

Message that contains an offer to a tendering procedure that is sent from client to server.

source

<xs:complexType name="OfferMessageType">
<xs:annotation>
    <xs:documentation>Message that contains an offer to a tendering procedure that is sent from client to server.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if:AbstractClientMessage">
      <xs:sequence>
        <xs:element name="document" type="xvergabe-docs:OfferDocumentType">
          <xs:annotation>
            <xs:documentation>An Offer document contains an actual offer that is submitted to the server by a bidder client.
An offer must be submitted in whole and MUST NOT be splitted over several Offer documents. A signature must be applied to the offer BEFORE encryption (this does not apply if the offer is submitted via OSCI).</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="attachment" type="xvergabe-if:Attachment" maxOccurs="2">
          <xs:annotation>
            <xs:documentation>offer container holding the encrypted offer. MIGHT be separated into two containers according to the ITT. each Container represents a PKCS#7 encrypted container holding a ZIP file which holds the files of the offer according to the ITT. Each container MUST include an OfferContent.xml file in the zip archive according to this spec.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element OfferMessageType/document

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-docs:OfferDocumentType

properties

content

complex

children

xvergabe-docs:accordingITTMsgID xvergabe-docs:offerObject

annotation

documentation

An Offer document contains an actual offer that is submitted to the server by a bidder client.
An offer must be submitted in whole and MUST NOT be splitted over several Offer documents. A signature must be applied to the offer BEFORE encryption (this does not apply if the offer is submitted via OSCI).

source

<xs:element name="document" type="xvergabe-docs:OfferDocumentType">
<xs:annotation>
<xs:documentation>An Offer document contains an actual offer that is submitted to the server by a bidder client.
An offer must be submitted in whole and MUST NOT be splitted over several Offer documents. A signature must be applied to the offer BEFORE encryption (this does not apply if the offer is submitted via OSCI).</xs:documentation>
</xs:annotation>
</xs:element>

element OfferMessageType/attachment

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:attachmentID xvergabe-if:filename xvergabe-if:description xvergabe-if:attachmentData xvergabe-if:signature

properties

minOcc	1
maxOcc	2
content	complex

children

annotation

documentation

offer container holding the encrypted offer. MIGHT be separated into two containers according to the ITT. each Container represents a PKCS#7 encrypted container holding a ZIP file which holds the files of the offer according to the ITT. Each container MUST include an OfferContent.xml file in the zip archive according to this spec.

source

<xs:element name="attachment" type="xvergabe-if:Attachment" maxOccurs="2">
<xs:annotation>
<xs:documentation>offer container holding the encrypted offer. MIGHT be separated into two containers according to the ITT. each Container represents a PKCS#7 encrypted container holding a ZIP file which holds the files of the offer according to the ITT. Each container MUST include an OfferContent.xml file in the zip archive according to this spec.</xs:documentation>
</xs:annotation>
</xs:element>

complexType OfferWithdrawalDeliveryReceiptMessageType

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

base	xvergabe-if:AbstractServerMessage

children

xvergabe-docs:WithdrawalDeliveryReceiptDocumentType

annotation

documentation

Message that contains a delivery receipt to the withdrawal of an offer that is sent from server to client.

source

<xs:complexType name="OfferWithdrawalDeliveryReceiptMessageType">
<xs:annotation>
    <xs:documentation>Message that contains a delivery receipt to the withdrawal of an offer that is sent from server to client.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if:AbstractServerMessage">
      <xs:sequence>
        <xs:element name="document" type="xvergabe-docs:WithdrawalDeliveryReceiptDocumentType">
          <xs:annotation>
            <xs:documentation>A WithdrawalDeliveryReceipt is a receipt that is sent from server to client after the client has submitted a Withdrawal. This receipt confirms the successful processing of the withdrawal. The receipt repeats the processing details given by the client and enriches them with the ID the server assigned to the Withdrawal document.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element OfferWithdrawalDeliveryReceiptMessageType/document

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

complex

children

annotation

documentation

source

<xs:element name="document" type="xvergabe-docs:WithdrawalDeliveryReceiptDocumentType">
<xs:annotation>
<xs:documentation>A WithdrawalDeliveryReceipt is a receipt that is sent from server to client after the client has submitted a Withdrawal. This receipt confirms the successful processing of the withdrawal. The receipt repeats the processing details given by the client and enriches them with the ID the server assigned to the Withdrawal document.</xs:documentation>
</xs:annotation>
</xs:element>

complexType OfferWithdrawalMessageType

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment

properties

base	xvergabe-if:AbstractClientMessage

children

annotation

documentation

Message that contains a request to withdraw an offer that is sent from client to server.

source

<xs:complexType name="OfferWithdrawalMessageType">
<xs:annotation>
    <xs:documentation>Message that contains a request to withdraw an offer that is sent from client to server.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if:AbstractClientMessage">
      <xs:sequence>
        <xs:element name="document" type="xvergabe-docs:WithdrawalDocumentType">
          <xs:annotation>
            <xs:documentation>A Withdrawal document contains the intention of a client to withdraw a previously submitted offer.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="attachment" type="xvergabe-if:Attachment" minOccurs="0" maxOccurs="unbounded">
          <xs:annotation>
            <xs:documentation>attachment(s) to the withdrawal. May include further reasoning for the withdrawal by the economic operator.
In case the ITP requested a signed withdrawal (minimumWithdrawalSignatureLevel was not NONE), the withdrawal message SHALL include at least one attachment which is signed according to this requirement).</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element OfferWithdrawalMessageType/document

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-docs:WithdrawalDocumentType

properties

content

complex

children

xvergabe-docs:objectIDToWithdraw xvergabe-docs:withdrawalReason xvergabe-docs:withdrawalDateTime

annotation

documentation

A Withdrawal document contains the intention of a client to withdraw a previously submitted offer.

source

<xs:element name="document" type="xvergabe-docs:WithdrawalDocumentType">
<xs:annotation>
<xs:documentation>A Withdrawal document contains the intention of a client to withdraw a previously submitted offer.</xs:documentation>
</xs:annotation>
</xs:element>

element OfferWithdrawalMessageType/attachment

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:attachmentID xvergabe-if:filename xvergabe-if:description xvergabe-if:attachmentData xvergabe-if:signature

properties

minOcc	0
maxOcc	unbounded
content	complex

children

annotation

documentation

attachment(s) to the withdrawal. May include further reasoning for the withdrawal by the economic operator.
In case the ITP requested a signed withdrawal (minimumWithdrawalSignatureLevel was not NONE), the withdrawal message SHALL include at least one attachment which is signed according to this requirement).

source

<xs:element name="attachment" type="xvergabe-if:Attachment" minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>attachment(s) to the withdrawal. May include further reasoning for the withdrawal by the economic operator.
In case the ITP requested a signed withdrawal (minimumWithdrawalSignatureLevel was not NONE), the withdrawal message SHALL include at least one attachment which is signed according to this requirement).</xs:documentation>
</xs:annotation>
</xs:element>

complexType OSCITransferIDRequestType

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:messageHeader xvergabe-if:offer xvergabe-if:participationRequest xvergabe-if:withdrawal

properties

base	xvergabe-if:AbstractClientMessage

children

annotation

documentation

Message that contains the request for an issueing of an OSCI Transfer ID. This message is being sent before the OSCI-delivery is taking place. The client indicates whether he wants to submit an offer, a participation request or wants to withdraw any of those. The server SHALL create a new TransferID and deliver this to the client. The client then uses this TransferID as the OSCI-subject within the osci-delivery-message.
The server SHALL verify the request (e.g. if the object to withdraw exists), thus the server MAY reject a request accordingly.

source

<xs:complexType name="OSCITransferIDRequestType">
<xs:annotation>
    <xs:documentation>Message that contains the request for an issueing of an OSCI Transfer ID. This message is being sent before the OSCI-delivery is taking place. The client indicates whether he wants to submit an offer, a participation request or wants to withdraw any of those. The server SHALL create a new TransferID and deliver this to the client. The client then uses this TransferID as the OSCI-subject within the osci-delivery-message.
The server SHALL verify the request (e.g. if the object to withdraw exists), thus the server MAY reject a request accordingly.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if:AbstractClientMessage">
      <xs:sequence>
        <xs:choice>
          <xs:annotation>
            <xs:documentation>inner structure to differentiate between the types the OSCI-delivery contains (offer/participation request/withdrawal)</xs:documentation>
          </xs:annotation>
          <xs:element name="offer">
            <xs:annotation>
              <xs:documentation>classifies the forthcoming OSCI-transfer as a delivery method for the offer.
The client MUST supply the messageID of the ITT the offer satisfies.
The server MAY reject an OSCI-TransferID-Request for a belated offer transaction (OSCI-TransferID-Request is sent after the submission deadline within the procedure). If the server is not rejecting those requests it MUST warn the client about the belated transaction.
The server SHALL warn the client about an outdated offer aswell (the offer is referencing an old or unknown ITT).</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="accordingITTMsgID" type="xvergabe-datatypes:GUID">
                  <xs:annotation>
                    <xs:documentation>ID of the latest InvitationToTender message the client received from the server. This InvitationToTender message is thus the basis for the creation of the offer. The server SHOULD use this ID to check if the offer was submitted on the most current version of the tendering documents.
The Server SHALL warn the client when an outdated or unknown ITT-Message is referenced. The server MAY NOT reject the Issue-Request in this case.</xs:documentation>
                  </xs:annotation>
                </xs:element>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="participationRequest">
            <xs:annotation>
              <xs:documentation>classifies the forthcoming OSCI-transfer as a deliveryMethod for the participationRequest.
The client MUST supply the messageID of the ITP the participation request satisfies.
The server MAY reject an OSCI-TransferID-Request for a belated participation transaction (OSCI-TransferID-Request is sent after the submission deadline for participation requests within the procedure). If the server is not rejecting those requests it MUST warn the client about the belated transaction.
The server SHALL warn the client about an outdated participation aswell (the participation is referencing an old or unknown ITP).</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="accordingITPMsgID" type="xvergabe-datatypes:GUID">
                  <xs:annotation>
                    <xs:documentation>ID of the latest InvitationToParticipation message the client received from the server. This InvitationToParticipation message is thus the basis for the creation of the participation request. The server SHOULD use this ID to check if the participation request was submitted on the most current version of the participation documents.
The Server SHALL warn the client when an outdated or unknown ITP-Message is referenced. The server MAY NOT reject the Issue-Request in this case.</xs:documentation>
                  </xs:annotation>
                </xs:element>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
          <xs:element name="withdrawal">
            <xs:annotation>
              <xs:documentation>classifies the forthcoming OSCI-transfer as a delivery method for a withdrawal (of an offer or participationRequest). carries the ID of the object to withdraw.
when the object ID is not known to the platform for the user, it MUST respond with an ERROR.</xs:documentation>
            </xs:annotation>
            <xs:complexType>
              <xs:sequence>
                <xs:element name="objectID" type="xvergabe-datatypes:GUID">
                  <xs:annotation>
                    <xs:documentation>the identifier of the object to withdraw (e.g. offerID or participationID as issued by the server)</xs:documentation>
                  </xs:annotation>
                </xs:element>
              </xs:sequence>
            </xs:complexType>
          </xs:element>
        </xs:choice>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element OSCITransferIDRequestType/offer

diagram

namespace

http://xvergabe.org/interface/xsd/4

properties

content

complex

children

xvergabe-if:accordingITTMsgID

annotation

documentation

classifies the forthcoming OSCI-transfer as a delivery method for the offer.
The client MUST supply the messageID of the ITT the offer satisfies.
The server MAY reject an OSCI-TransferID-Request for a belated offer transaction (OSCI-TransferID-Request is sent after the submission deadline within the procedure). If the server is not rejecting those requests it MUST warn the client about the belated transaction.
The server SHALL warn the client about an outdated offer aswell (the offer is referencing an old or unknown ITT).

source

<xs:element name="offer">
<xs:annotation>
    <xs:documentation>classifies the forthcoming OSCI-transfer as a delivery method for the offer.
The client MUST supply the messageID of the ITT the offer satisfies.
The server MAY reject an OSCI-TransferID-Request for a belated offer transaction (OSCI-TransferID-Request is sent after the submission deadline within the procedure). If the server is not rejecting those requests it MUST warn the client about the belated transaction.
The server SHALL warn the client about an outdated offer aswell (the offer is referencing an old or unknown ITT).</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:sequence>
      <xs:element name="accordingITTMsgID" type="xvergabe-datatypes:GUID">
        <xs:annotation>
          <xs:documentation>ID of the latest InvitationToTender message the client received from the server. This InvitationToTender message is thus the basis for the creation of the offer. The server SHOULD use this ID to check if the offer was submitted on the most current version of the tendering documents.
The Server SHALL warn the client when an outdated or unknown ITT-Message is referenced. The server MAY NOT reject the Issue-Request in this case.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
</xs:complexType>
</xs:element>

element OSCITransferIDRequestType/offer/accordingITTMsgID

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:accordingITPMsgID

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

ID of the latest InvitationToTender message the client received from the server. This InvitationToTender message is thus the basis for the creation of the offer. The server SHOULD use this ID to check if the offer was submitted on the most current version of the tendering documents.
The Server SHALL warn the client when an outdated or unknown ITT-Message is referenced. The server MAY NOT reject the Issue-Request in this case.

source

element OSCITransferIDRequestType/participationRequest

diagram

namespace

http://xvergabe.org/interface/xsd/4

properties

content

complex

children

annotation

documentation

classifies the forthcoming OSCI-transfer as a deliveryMethod for the participationRequest.
The client MUST supply the messageID of the ITP the participation request satisfies.
The server MAY reject an OSCI-TransferID-Request for a belated participation transaction (OSCI-TransferID-Request is sent after the submission deadline for participation requests within the procedure). If the server is not rejecting those requests it MUST warn the client about the belated transaction.
The server SHALL warn the client about an outdated participation aswell (the participation is referencing an old or unknown ITP).

source

<xs:element name="participationRequest">
<xs:annotation>
    <xs:documentation>classifies the forthcoming OSCI-transfer as a deliveryMethod for the participationRequest.
The client MUST supply the messageID of the ITP the participation request satisfies.
The server MAY reject an OSCI-TransferID-Request for a belated participation transaction (OSCI-TransferID-Request is sent after the submission deadline for participation requests within the procedure). If the server is not rejecting those requests it MUST warn the client about the belated transaction.
The server SHALL warn the client about an outdated participation aswell (the participation is referencing an old or unknown ITP).</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:sequence>
      <xs:element name="accordingITPMsgID" type="xvergabe-datatypes:GUID">
        <xs:annotation>
          <xs:documentation>ID of the latest InvitationToParticipation message the client received from the server. This InvitationToParticipation message is thus the basis for the creation of the participation request. The server SHOULD use this ID to check if the participation request was submitted on the most current version of the participation documents.
The Server SHALL warn the client when an outdated or unknown ITP-Message is referenced. The server MAY NOT reject the Issue-Request in this case.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
</xs:complexType>
</xs:element>

element OSCITransferIDRequestType/participationRequest/accordingITPMsgID

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

ID of the latest InvitationToParticipation message the client received from the server. This InvitationToParticipation message is thus the basis for the creation of the participation request. The server SHOULD use this ID to check if the participation request was submitted on the most current version of the participation documents.
The Server SHALL warn the client when an outdated or unknown ITP-Message is referenced. The server MAY NOT reject the Issue-Request in this case.

source

<xs:element name="accordingITPMsgID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>ID of the latest InvitationToParticipation message the client received from the server. This InvitationToParticipation message is thus the basis for the creation of the participation request. The server SHOULD use this ID to check if the participation request was submitted on the most current version of the participation documents.
The Server SHALL warn the client when an outdated or unknown ITP-Message is referenced. The server MAY NOT reject the Issue-Request in this case.</xs:documentation>
</xs:annotation>
</xs:element>

element OSCITransferIDRequestType/withdrawal

diagram

namespace

http://xvergabe.org/interface/xsd/4

properties

content

complex

children

xvergabe-if:objectID

annotation

documentation

classifies the forthcoming OSCI-transfer as a delivery method for a withdrawal (of an offer or participationRequest). carries the ID of the object to withdraw.
when the object ID is not known to the platform for the user, it MUST respond with an ERROR.

source

<xs:element name="withdrawal">
<xs:annotation>
    <xs:documentation>classifies the forthcoming OSCI-transfer as a delivery method for a withdrawal (of an offer or participationRequest). carries the ID of the object to withdraw.
when the object ID is not known to the platform for the user, it MUST respond with an ERROR.</xs:documentation>
</xs:annotation>
<xs:complexType>
    <xs:sequence>
      <xs:element name="objectID" type="xvergabe-datatypes:GUID">
        <xs:annotation>
          <xs:documentation>the identifier of the object to withdraw (e.g. offerID or participationID as issued by the server)</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
</xs:complexType>
</xs:element>

element OSCITransferIDRequestType/withdrawal/objectID

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

simple

facets

Kind	Value	Annotation
pattern	[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}

annotation

documentation

the identifier of the object to withdraw (e.g. offerID or participationID as issued by the server)

source

<xs:element name="objectID" type="xvergabe-datatypes:GUID">
<xs:annotation>
<xs:documentation>the identifier of the object to withdraw (e.g. offerID or participationID as issued by the server)</xs:documentation>
</xs:annotation>
</xs:element>

complexType ParticipationDeliveryReceiptMessageType

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

base	xvergabe-if:AbstractServerMessage

children

xvergabe-docs:ParticipationDeliveryReceiptDocumentType

annotation

documentation

Message that contains a delivery receipt to a participation request that is sent from server to client.

source

<xs:complexType name="ParticipationDeliveryReceiptMessageType">
<xs:annotation>
    <xs:documentation>Message that contains a delivery receipt to a participation request that is sent from server to client.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if:AbstractServerMessage">
      <xs:sequence>
        <xs:element name="document" type="xvergabe-docs:ParticipationDeliveryReceiptDocumentType">
          <xs:annotation>
            <xs:documentation>A ParticipationDeliveryReceipt is a receipt that is sent from server to client after the client has submitted a Participation request. This receipt confirms the successful processing of the Participation request. The receipt repeats the processing details given by the client and enriches them with the ID the server assigned to the Participation request.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element ParticipationDeliveryReceiptMessageType/document

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

complex

children

annotation

documentation

source

<xs:element name="document" type="xvergabe-docs:ParticipationDeliveryReceiptDocumentType">
<xs:annotation>
<xs:documentation>A ParticipationDeliveryReceipt is a receipt that is sent from server to client after the client has submitted a Participation request. This receipt confirms the successful processing of the Participation request. The receipt repeats the processing details given by the client and enriches them with the ID the server assigned to the Participation request.</xs:documentation>
</xs:annotation>
</xs:element>

complexType ParticipationMessageType

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment

properties

base	xvergabe-if:AbstractClientMessage

children

annotation

documentation

Message that contains a request to participation that is sent from client to server.

source

<xs:complexType name="ParticipationMessageType">
<xs:annotation>
    <xs:documentation>Message that contains a request to participation that is sent from client to server.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if:AbstractClientMessage">
      <xs:sequence>
        <xs:element name="document" type="xvergabe-docs:ParticipationDocumentType">
          <xs:annotation>
            <xs:documentation>A participation document contains an actual participation request that is submitted to the server by a bidder client.
A participation request must be submitted in whole and MUST NOT be splitted over several Participation documents. A signature must be applied to the offer BEFORE encryption (this does not apply if the participation request is submitted via OSCI).</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="attachment" type="xvergabe-if:Attachment" maxOccurs="2">
          <xs:annotation>
            <xs:documentation>participation container holding the encrypted participation request. MIGHT be separated into two containers according to the ITP. each Container represents a PKCS#7 encrypted container holding a ZIP file which holds the files of the participation request according to the ITP. Each container MUST include a ParticipationContent.xml file in the zip archive according to this spec.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element ParticipationMessageType/document

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-docs:ParticipationDocumentType

properties

content

complex

children

xvergabe-docs:accordingITPMsgID xvergabe-docs:participationObject

annotation

documentation

A participation document contains an actual participation request that is submitted to the server by a bidder client.
A participation request must be submitted in whole and MUST NOT be splitted over several Participation documents. A signature must be applied to the offer BEFORE encryption (this does not apply if the participation request is submitted via OSCI).

source

<xs:element name="document" type="xvergabe-docs:ParticipationDocumentType">
<xs:annotation>
<xs:documentation>A participation document contains an actual participation request that is submitted to the server by a bidder client.
A participation request must be submitted in whole and MUST NOT be splitted over several Participation documents. A signature must be applied to the offer BEFORE encryption (this does not apply if the participation request is submitted via OSCI).</xs:documentation>
</xs:annotation>
</xs:element>

element ParticipationMessageType/attachment

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:attachmentID xvergabe-if:filename xvergabe-if:description xvergabe-if:attachmentData xvergabe-if:signature

properties

minOcc	1
maxOcc	2
content	complex

children

annotation

documentation

participation container holding the encrypted participation request. MIGHT be separated into two containers according to the ITP. each Container represents a PKCS#7 encrypted container holding a ZIP file which holds the files of the participation request according to the ITP. Each container MUST include a ParticipationContent.xml file in the zip archive according to this spec.

source

<xs:element name="attachment" type="xvergabe-if:Attachment" maxOccurs="2">
<xs:annotation>
<xs:documentation>participation container holding the encrypted participation request. MIGHT be separated into two containers according to the ITP. each Container represents a PKCS#7 encrypted container holding a ZIP file which holds the files of the participation request according to the ITP. Each container MUST include a ParticipationContent.xml file in the zip archive according to this spec.</xs:documentation>
</xs:annotation>
</xs:element>

complexType ParticipationWithdrawalDeliveryReceiptMessageType

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

base	xvergabe-if:AbstractServerMessage

children

xvergabe-docs:WithdrawalDeliveryReceiptDocumentType

annotation

documentation

Message that contains a delivery receipt to a participation withdrawal request that is sent from server to client.

source

<xs:complexType name="ParticipationWithdrawalDeliveryReceiptMessageType">
<xs:annotation>
    <xs:documentation>Message that contains a delivery receipt to a participation withdrawal request that is sent from server to client.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if:AbstractServerMessage">
      <xs:sequence>
        <xs:element name="document" type="xvergabe-docs:WithdrawalDeliveryReceiptDocumentType">
          <xs:annotation>
            <xs:documentation>A WithdrawalDeliveryReceipt is a receipt that is sent from server to client after the client has submitted a Withdrawal. This receipt confirms the successful processing of the withdrawal. The receipt repeats the processing details given by the client and enriches them with the ID the server assigned to the Withdrawal document.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element ParticipationWithdrawalDeliveryReceiptMessageType/document

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

complex

children

annotation

documentation

source

complexType ParticipationWithdrawalMessageType

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment

properties

base	xvergabe-if:AbstractClientMessage

children

annotation

documentation

Message that contains a request to withdraw participation that is sent from client to server.

source

<xs:complexType name="ParticipationWithdrawalMessageType">
<xs:annotation>
    <xs:documentation>Message that contains a request to withdraw participation that is sent from client to server.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if:AbstractClientMessage">
      <xs:sequence>
        <xs:element name="document" type="xvergabe-docs:WithdrawalDocumentType">
          <xs:annotation>
            <xs:documentation>A Withdrawal document contains the intention of a client to withdraw a previously submitted participation request.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="attachment" type="xvergabe-if:Attachment" minOccurs="0" maxOccurs="unbounded">
          <xs:annotation>
            <xs:documentation>attachment(s) to the withdrawal. May include further reasoning for the withdrawal by the economic operator.
In case the ITP requested a signed withdrawal (minimumWithdrawalSignatureLevel was not NONE), the withdrawal message SHALL include at least one attachment which is signed according to this requirement).</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element ParticipationWithdrawalMessageType/document

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-docs:WithdrawalDocumentType

properties

content

complex

children

xvergabe-docs:objectIDToWithdraw xvergabe-docs:withdrawalReason xvergabe-docs:withdrawalDateTime

annotation

documentation

A Withdrawal document contains the intention of a client to withdraw a previously submitted participation request.

source

<xs:element name="document" type="xvergabe-docs:WithdrawalDocumentType">
<xs:annotation>
<xs:documentation>A Withdrawal document contains the intention of a client to withdraw a previously submitted participation request.</xs:documentation>
</xs:annotation>
</xs:element>

element ParticipationWithdrawalMessageType/attachment

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xvergabe-if:attachmentID xvergabe-if:filename xvergabe-if:description xvergabe-if:attachmentData xvergabe-if:signature

properties

minOcc	0
maxOcc	unbounded
content	complex

children

annotation

documentation

source

complexType ResultNoticeMessageType

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

base	xvergabe-if:AbstractServerMessage

children

xvergabe-docs:ResultNoticeDocumentType

annotation

documentation

Contains a notice that informs a bidder about the result of a tendering procedure.

source

<xs:complexType name="ResultNoticeMessageType">
<xs:annotation>
    <xs:documentation>Contains a notice that informs a bidder about the result of a tendering procedure.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if:AbstractServerMessage">
      <xs:sequence>
        <xs:element name="document" type="xvergabe-docs:ResultNoticeDocumentType">
          <xs:annotation>
            <xs:documentation>A ResultNotice serves to inform a bidder about the result of tendering procedure (i.e. whether the contract is awarded to the bidder or not) or the result of a participation contest (i.e. whether the bidder is allowed to take part in the participation contest or not). The ResultNotice document extends the InquiryDocumentType so that the actual content of the notice can be included in an InquiryDocument.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element ResultNoticeMessageType/document

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

complex

children

xvergabe-if:senderName xvergabe-if:vendor xvergabe-if:product xvergabe-if:productVersion xvergabe-if:productInstance xvergabe-if:supportURL

annotation

documentation

source

<xs:element name="document" type="xvergabe-docs:ResultNoticeDocumentType">
<xs:annotation>
<xs:documentation>A ResultNotice serves to inform a bidder about the result of tendering procedure (i.e. whether the contract is awarded to the bidder or not) or the result of a participation contest (i.e. whether the bidder is allowed to take part in the participation contest or not). The ResultNotice document extends the InquiryDocumentType so that the actual content of the notice can be included in an InquiryDocument.</xs:documentation>
</xs:annotation>
</xs:element>

complexType SenderInfo

diagram

namespace

http://xvergabe.org/interface/xsd/4

children

annotation

documentation

Information about the sender and the sending application

source

<xs:complexType name="SenderInfo">
<xs:annotation>
    <xs:documentation>Information about the sender and the sending application</xs:documentation>
</xs:annotation>
<xs:sequence>
    <xs:element name="senderName" type="xvergabe-datatypes:String.1024">
      <xs:annotation>
        <xs:documentation>Name of the Sender, e.g. the name of the sending Contracting Authority or the sending Economic Operator</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="vendor" type="xvergabe-datatypes:String.1024">
      <xs:annotation>
        <xs:documentation>name of the vendor of the sending application</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="product" type="xvergabe-datatypes:String.1024">
      <xs:annotation>
        <xs:documentation>productname of the sending application</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="productVersion" type="xvergabe-datatypes:String.255">
      <xs:annotation>
        <xs:documentation>versionnumber of the sending application</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="productInstance" type="xvergabe-datatypes:String.1024" minOccurs="0">
      <xs:annotation>
        <xs:documentation>name of the instance of the sending application</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="supportURL" type="xs:anyURI">
      <xs:annotation>
        <xs:documentation>URL to contact the support of the sending application</xs:documentation>
      </xs:annotation>
    </xs:element>
</xs:sequence>
</xs:complexType>

element SenderInfo/senderName

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

simple

annotation

documentation

Name of the Sender, e.g. the name of the sending Contracting Authority or the sending Economic Operator

source

<xs:element name="senderName" type="xvergabe-datatypes:String.1024">
<xs:annotation>
<xs:documentation>Name of the Sender, e.g. the name of the sending Contracting Authority or the sending Economic Operator</xs:documentation>
</xs:annotation>
</xs:element>

element SenderInfo/vendor

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

simple

annotation

documentation

name of the vendor of the sending application

source

<xs:element name="vendor" type="xvergabe-datatypes:String.1024">
<xs:annotation>
<xs:documentation>name of the vendor of the sending application</xs:documentation>
</xs:annotation>
</xs:element>

element SenderInfo/product

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

simple

annotation

documentation

productname of the sending application

source

<xs:element name="product" type="xvergabe-datatypes:String.1024">
<xs:annotation>
<xs:documentation>productname of the sending application</xs:documentation>
</xs:annotation>
</xs:element>

element SenderInfo/productVersion

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

simple

annotation

documentation

versionnumber of the sending application

source

<xs:element name="productVersion" type="xvergabe-datatypes:String.255">
<xs:annotation>
<xs:documentation>versionnumber of the sending application</xs:documentation>
</xs:annotation>
</xs:element>

element SenderInfo/productInstance

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

minOcc	0
maxOcc	1
content	simple

annotation

documentation

name of the instance of the sending application

source

<xs:element name="productInstance" type="xvergabe-datatypes:String.1024" minOccurs="0">
<xs:annotation>
<xs:documentation>name of the instance of the sending application</xs:documentation>
</xs:annotation>
</xs:element>

element SenderInfo/supportURL

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

xs:anyURI

properties

content

simple

annotation

documentation

URL to contact the support of the sending application

source

<xs:element name="supportURL" type="xs:anyURI">
<xs:annotation>
<xs:documentation>URL to contact the support of the sending application</xs:documentation>
</xs:annotation>
</xs:element>

complexType ServerInquiryMessageType

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

base	xvergabe-if:AbstractServerMessage

children

xvergabe-docs:InquiryDocumentType

annotation

documentation

Message that contains an inquiry (or an answer to an inquiry) that is sent from server to client.

source

<xs:complexType name="ServerInquiryMessageType">
<xs:annotation>
    <xs:documentation>Message that contains an inquiry (or an answer to an inquiry) that is sent from server to client.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if:AbstractServerMessage">
      <xs:sequence>
        <xs:element name="document" type="xvergabe-docs:InquiryDocumentType">
          <xs:annotation>
            <xs:documentation>An InquiryDocument serves as vessel for general inquiries and answers sent from server to client. An inquiry can reference a previously exchanged document.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element ServerInquiryMessageType/document

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

complex

children

annotation

documentation

An InquiryDocument serves as vessel for general inquiries and answers sent from server to client. An inquiry can reference a previously exchanged document.

source

<xs:element name="document" type="xvergabe-docs:InquiryDocumentType">
<xs:annotation>
<xs:documentation>An InquiryDocument serves as vessel for general inquiries and answers sent from server to client. An inquiry can reference a previously exchanged document.</xs:documentation>
</xs:annotation>
</xs:element>

complexType TenderMetaInformationMessageType

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

base	xvergabe-if:AbstractServerMessage

children

xvergabe-docs:TenderMetaInformationDocumentType

annotation

documentation

Message that contains meta information about a tendering procedure that is distributed from server to clients.

source

<xs:complexType name="TenderMetaInformationMessageType">
<xs:annotation>
    <xs:documentation>Message that contains meta information about a tendering procedure that is distributed from server to clients.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:extension base="xvergabe-if:AbstractServerMessage">
      <xs:sequence>
        <xs:element name="document" type="xvergabe-docs:TenderMetaInformationDocumentType">
          <xs:annotation>
            <xs:documentation>A TenderMetaInformation contains meta data about a tendering procedure like the name, deadlines and the current status. A TenderMetaInformation is sent from a server to its clients and serves the clients as technical basis for further message exchange within the concerned tendering procedure. The TenderMetaInformation document is not part of the tendering documents. Instead it is intended as technical document to exchange meta data.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
</xs:complexContent>
</xs:complexType>

element TenderMetaInformationMessageType/document

diagram

namespace

http://xvergabe.org/interface/xsd/4

type

properties

content

complex

children

xvergabe-docs:tenderMetaInformationDetails xvergabe-docs:platformInformationDetails

annotation

documentation

source

<xs:element name="document" type="xvergabe-docs:TenderMetaInformationDocumentType">
<xs:annotation>
<xs:documentation>A TenderMetaInformation contains meta data about a tendering procedure like the name, deadlines and the current status. A TenderMetaInformation is sent from a server to its clients and serves the clients as technical basis for further message exchange within the concerned tendering procedure. The TenderMetaInformation document is not part of the tendering documents. Instead it is intended as technical document to exchange meta data.</xs:documentation>
</xs:annotation>
</xs:element>

complexType Code.ContractType

diagram

namespace

http://xvergabe.org/codelists/xsd/4

type

restriction of xoev-code:Code

properties

base	xoev-code:Code

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:contractType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

The type of the tendering contract.

source

<xs:complexType name="Code.ContractType">
<xs:annotation>
    <xs:documentation>The type of the tendering contract.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:restriction base="xoev-code:Code">
      <xs:sequence>
        <xs:element name="code" form="unqualified">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>In diesem XML-Element wird der Code einer Codeliste übermittelt.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:token">
              <xs:enumeration value="SERVICES">
                <xs:annotation>
                  <xs:documentation>a services contract</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="SUPPLIES">
                <xs:annotation>
                  <xs:documentation>a supplies contract</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="WORKS">
                <xs:annotation>
                  <xs:documentation>A building / construction / works contract.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
        <xs:element name="name" type="xs:normalizedString" form="unqualified" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
      <xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:contractType">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute name="listVersionID" type="xs:normalizedString" use="optional" fixed="1.0">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Die konkrete Version der zu nutzenden Codeliste wird mit diesem XML-Attribut übertragen.

Analog zum listURI ist die Bestimmung der Version einer Codeliste bei der Übertragung eines Codes zwingend. Die Version kann jedoch ebenfalls bereits im XÖV-Standard festgelegt werden (es handelt sich in diesem Fall um einen Code-Typ 1 oder 2).</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
</xs:complexContent>
</xs:complexType>

attribute Code.ContractType/@listURI

type

xs:anyURI

properties

use	optional
fixed	urn:org:xvergabe:codelists:contractType

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

<xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:contractType">
<xs:annotation>
<xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
<xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
</xs:annotation>
</xs:attribute>

attribute Code.ContractType/@listVersionID

type

xs:normalizedString

properties

use	optional
fixed	1.0

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

<xs:attribute name="listVersionID" type="xs:normalizedString" use="optional" fixed="1.0">
<xs:annotation>
<xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
<xs:documentation>Die konkrete Version der zu nutzenden Codeliste wird mit diesem XML-Attribut übertragen.

Analog zum listURI ist die Bestimmung der Version einer Codeliste bei der Übertragung eines Codes zwingend. Die Version kann jedoch ebenfalls bereits im XÖV-Standard festgelegt werden (es handelt sich in diesem Fall um einen Code-Typ 1 oder 2).</xs:documentation>
</xs:annotation>
</xs:attribute>

element Code.ContractType/code

diagram

type

restriction of xs:token

properties

content	simple
form	unqualified

facets

Kind

Value

Annotation

enumeration

SERVICES

documentation

a services contract

enumeration

SUPPLIES

documentation

a supplies contract

enumeration

WORKS

documentation

A building / construction / works contract.

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

In diesem XML-Element wird der Code einer Codeliste übermittelt.

source

element Code.ContractType/name

diagram

type

xs:normalizedString

properties

minOcc	0
maxOcc	1
content	simple
form	unqualified

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.

source

<xs:element name="name" type="xs:normalizedString" form="unqualified" minOccurs="0">
<xs:annotation>
<xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
<xs:documentation>Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.</xs:documentation>
</xs:annotation>
</xs:element>

complexType Code.CredentialUsage

diagram

namespace

http://xvergabe.org/codelists/xsd/4

type

restriction of xoev-code:Code

properties

base	xoev-code:Code

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:credentialusage

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

The task the credential data is to be used for.

source

<xs:complexType name="Code.CredentialUsage">
<xs:annotation>
    <xs:documentation>The task the credential data is to be used for.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:restriction base="xoev-code:Code">
      <xs:sequence>
        <xs:element name="code" form="unqualified">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>In diesem XML-Element wird der Code einer Codeliste übermittelt.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:token">
              <xs:enumeration value="ENCRYPTION">
                <xs:annotation>
                  <xs:documentation>The credentials are to be used for the encryption or decryption of a document.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="SIGNATURE">
                <xs:annotation>
                  <xs:documentation>The credentials are to be used for validating the signature of a document.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
        <xs:element name="name" type="xs:normalizedString" form="unqualified" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
      <xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:credentialusage">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute name="listVersionID" type="xs:normalizedString" use="optional" fixed="1.0">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Die konkrete Version der zu nutzenden Codeliste wird mit diesem XML-Attribut übertragen.

Analog zum listURI ist die Bestimmung der Version einer Codeliste bei der Übertragung eines Codes zwingend. Die Version kann jedoch ebenfalls bereits im XÖV-Standard festgelegt werden (es handelt sich in diesem Fall um einen Code-Typ 1 oder 2).</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
</xs:complexContent>
</xs:complexType>

attribute Code.CredentialUsage/@listURI

type

xs:anyURI

properties

use	optional
fixed	urn:org:xvergabe:codelists:credentialusage

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

<xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:credentialusage">
<xs:annotation>
<xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
<xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
</xs:annotation>
</xs:attribute>

attribute Code.CredentialUsage/@listVersionID

type

xs:normalizedString

properties

use	optional
fixed	1.0

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

element Code.CredentialUsage/code

diagram

type

restriction of xs:token

properties

content	simple
form	unqualified

facets

Kind

Value

Annotation

enumeration

ENCRYPTION

documentation

The credentials are to be used for the encryption or decryption of a document.

enumeration

SIGNATURE

documentation

The credentials are to be used for validating the signature of a document.

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

In diesem XML-Element wird der Code einer Codeliste übermittelt.

source

element Code.CredentialUsage/name

diagram

type

xs:normalizedString

properties

minOcc	0
maxOcc	1
content	simple
form	unqualified

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.

source

complexType Code.EncryptionAlgorithm

diagram

namespace

http://xvergabe.org/codelists/xsd/4

type

restriction of xoev-code:Code

properties

base	xoev-code:Code

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:encryptionalgorithm

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

Definition of an encryption algorithm.

source

<xs:complexType name="Code.EncryptionAlgorithm">
<xs:annotation>
    <xs:documentation>Definition of an encryption algorithm.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:restriction base="xoev-code:Code">
      <xs:sequence>
        <xs:element name="code" form="unqualified">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>In diesem XML-Element wird der Code einer Codeliste übermittelt.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:token">
              <xs:enumeration value="3DES">
                <xs:annotation>
                  <xs:appinfo>
                    <codeName>Triple DES</codeName>
                  </xs:appinfo>
                  <xs:documentation>Triple DES</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="AES">
                <xs:annotation>
                  <xs:appinfo>
                    <codeName>Advanced Encryption Standard</codeName>
                  </xs:appinfo>
                  <xs:documentation>Advanced Encryption Standard</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="BLOWFISH">
                <xs:annotation>
                  <xs:appinfo>
                    <codeName>Blowfish</codeName>
                  </xs:appinfo>
                  <xs:documentation>Blowfish</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="DES">
                <xs:annotation>
                  <xs:appinfo>
                    <codeName>Data Encryption Standard</codeName>
                  </xs:appinfo>
                  <xs:documentation>Data Encryption Standard</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="IDEA">
                <xs:annotation>
                  <xs:appinfo>
                    <codeName>International Data Encryption Algorithm</codeName>
                  </xs:appinfo>
                  <xs:documentation>International Data Encryption Algorithm</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="RSA">
                <xs:annotation>
                  <xs:appinfo>
                    <codeName>Rivest, Shamir, Adleman</codeName>
                  </xs:appinfo>
                  <xs:documentation>Rivest, Shamir, Adleman</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="TWOFISH">
                <xs:annotation>
                  <xs:appinfo>
                    <codeName>Twofish</codeName>
                  </xs:appinfo>
                  <xs:documentation>Twofish</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
        <xs:element name="name" type="xs:normalizedString" form="unqualified" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
      <xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:encryptionalgorithm">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute name="listVersionID" type="xs:normalizedString" use="optional" fixed="1.0">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Die konkrete Version der zu nutzenden Codeliste wird mit diesem XML-Attribut übertragen.

Analog zum listURI ist die Bestimmung der Version einer Codeliste bei der Übertragung eines Codes zwingend. Die Version kann jedoch ebenfalls bereits im XÖV-Standard festgelegt werden (es handelt sich in diesem Fall um einen Code-Typ 1 oder 2).</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
</xs:complexContent>
</xs:complexType>

attribute Code.EncryptionAlgorithm/@listURI

type

xs:anyURI

properties

use	optional
fixed	urn:org:xvergabe:codelists:encryptionalgorithm

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

<xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:encryptionalgorithm">
<xs:annotation>
<xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
<xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
</xs:annotation>
</xs:attribute>

attribute Code.EncryptionAlgorithm/@listVersionID

type

xs:normalizedString

properties

use	optional
fixed	1.0

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

element Code.EncryptionAlgorithm/code

diagram

type

restriction of xs:token

properties

content	simple
form	unqualified

facets

Kind

Value

Annotation

enumeration

3DES

appinfo

<codeName>Triple DES</codeName>

documentation

Triple DES

enumeration

AES

appinfo

<codeName>Advanced Encryption Standard</codeName>

documentation

Advanced Encryption Standard

enumeration

BLOWFISH

appinfo

<codeName>Blowfish</codeName>

documentation

Blowfish

enumeration

DES

appinfo

<codeName>Data Encryption Standard</codeName>

documentation

Data Encryption Standard

enumeration

IDEA

appinfo

<codeName>International Data Encryption Algorithm</codeName>

documentation

International Data Encryption Algorithm

enumeration

RSA

appinfo

<codeName>Rivest, Shamir, Adleman</codeName>

documentation

Rivest, Shamir, Adleman

enumeration

TWOFISH

appinfo

<codeName>Twofish</codeName>

documentation

Twofish

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

In diesem XML-Element wird der Code einer Codeliste übermittelt.

source

element Code.EncryptionAlgorithm/name

diagram

type

xs:normalizedString

properties

minOcc	0
maxOcc	1
content	simple
form	unqualified

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.

source

complexType Code.ErrorCodeType

diagram

namespace

http://xvergabe.org/codelists/xsd/4

type

restriction of xoev-code:Code

properties

base	xoev-code:Code

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:errorCodeType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

Error codes to be used in a response for a failed transaction.
When used, a response information text MUST be given in addition.

source

<xs:complexType name="Code.ErrorCodeType">
<xs:annotation>
    <xs:documentation>Error codes to be used in a response for a failed transaction.
When used, a response information text MUST be given in addition.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:restriction base="xoev-code:Code">
      <xs:sequence>
        <xs:element name="code" form="unqualified">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>In diesem XML-Element wird der Code einer Codeliste übermittelt.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:token">
              <xs:enumeration value="ATTACHMENTS_EXCEED_MAX_SIZE_FOR_ALL_ATTACHMENTS">
                <xs:annotation>
                  <xs:documentation>error indicating that the total size of all attached files to the clients message exceed the limits of the platform as defined in the TMI.
The platform SHALL name the defined size limit and the exceeding size of all attached files within "responseInformation".</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="ATTACHMENT_EXCEEDS_MAX_SIZE_PER_ATTACHMENT">
                <xs:annotation>
                  <xs:documentation>error indicating that the size of at least one attached file to the clients message exceeds the limit of the platform as defined in the TMI. The platform SHALL name the attachment identifier, the defined size limit and the exceeding size of the attached file within "responseInformation".</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="AUTHENTICATION_ERROR">
                <xs:annotation>
                  <xs:documentation>indicates that the user could not be authenticated. the reasons for this can be various (e.g wrong username and/or password, password must be renewed). the platform MAY give detailed information about the cause of this error in "response information".</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="AUTHORIZATION_ERROR">
                <xs:annotation>
                  <xs:documentation>indicates the occurence of an authorization problem. this is most likely the case when a successfully authenticated user tries to access a ressource (tendering procedure or document) without the right to do so (e.g. the successfully authenticated user trys to send a message within a tendering procedure he has not subscribed to).</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="INVALID_ACTION_FOR_CURRENT_PROCEDURE_STATUS">
                <xs:annotation>
                  <xs:documentation>this error indicates a violation of the procedure status model. it occurs when a client tries to execute an operation or sends a message which is not allowed in the current state of the procedure (e.g. the client tries to subscribe himself to a procedure being closed allready).
The platform MUST inform the client about the cause of the problem (the status of the procedure) within "response information".
In the special case of belated submissions of offers (or participation requests) - WITHIN the respective evaluation phase - a platform MAY either accept the submission (produce a WARNING) or reject the submission with the special ERROR code SUBMISSION_AFTER_DEADLINE.
In the special case of extremely belated submissions of offers (or participation requests) - AFTER the respective evaluation phase - a platform MUST reject the submission with the special ERROR code SUBMISSION_AFTER_EVALUATION_PHASE.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="INVALID_DOCUMENT_ID">
                <xs:annotation>
                  <xs:documentation>error indicating that the client wanted to access a document via getDocuments from the platform and used a wrong (non-existent) documentID.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="INVALID_LASTKNOWNMSG_ID">
                <xs:annotation>
                  <xs:documentation>an error which might occur in the context of a getMessages-transaction in the case the client references a messageId to be the latest one he has knowledge of within a procedure but the platform does not know this messageId (unknown message id) or the messageID does not belong to the given tenderingProcedureID. The platform MUST supply additional information about the cause in "response information"</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="INVALID_MESSAGE_ID">
                <xs:annotation>
                  <xs:documentation>an error which might occur in the context of a getMessages-transaction in the case the client references a certain messageId but the platform does not know this messageId (unknown message id) or the messageID does not belong to a message sent to this particular client. The platform MUST supply additional information about the cause in "response information"</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="INVALID_OBJECTID_FOR_WITHDRAWAL">
                <xs:annotation>
                  <xs:documentation>an error which might occur in the context of a withdrawal when the client wishes to withdraw an offer/participation request but the referenced offer/participation request is not known to the platform, identifies something else (e.g. a message) but not an offer or participation request or does not belong to the client.
This error may thus occur within a sendSynchronous-Response-Message or a getOSCITransferID-Response-Message.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="INVALID_TENDERING_PROCEDURE_ID">
                <xs:annotation>
                  <xs:documentation>an error indicating a wrongfully referenced tendering procedure id, e.g. one which is unknown to the platform.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="SECONDARY_CONTAINER_NOT_SUPPORTED">
                <xs:annotation>
                  <xs:documentation>error indicating that the offer or participation message was not constructed according to the rules of the ITT/ITP message regarding the number of containers.
The error is encountered when a client tries to submit an offer/participation consisting of a primary AND a secondary container while the ITT/ITP specified that the platform is not able to process secondaryContainers (onlyPrimaryContainerAllowed is set to true).</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="SUBMISSION_AFTER_DEADLINE">
                <xs:annotation>
                  <xs:documentation>specialized error code of INVALID_ACTION_FOR_CURRENT_PROCEDURE_STATUS in case of a belated submission of offers/participation requests - within the corresponding evaluation phase. this error might occur when the platform rejects the submission in this phase. The error can only occur within a getOSCITransferID- or sendSynchronousMessage-Response.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="SUBMISSION_AFTER_EVALUATION_PHASE">
                <xs:annotation>
                  <xs:documentation>specialized error code of INVALID_ACTION_FOR_CURRENT_PROCEDURE_STATUS in case of an extremely belated submission of offers/participation requests - AFTER the corresponding evaluation phase. Every platform shall reject submissions then. The error can only occur within a getOSCITransferID- or sendSynchronousMessage-Response.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="VALIDATION_ERROR">
                <xs:annotation>
                  <xs:documentation>error indicating that the client message cannot be validated correctly (e.g. syntax error). It might also occur when a client message is syntactically correct but is missing referenced objects (e.g. the client message references attachments but is missing those referenced attachments).</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="WRONG_ENCRYPTION_RECIPIENTS">
                <xs:annotation>
                  <xs:documentation>error indicating that the offer/participation request container(s) is/are wrongfully encrypted, i.e. not encrypted for the encryption key(s) from the ITT/ITP message. It may only occur in an sendSynchronousResponse-Message.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="WRONG_TRANSPORT_PROTOCOL">
                <xs:annotation>
                  <xs:documentation>indicates that the client tries to submit an offer, participation request or withdrawal via sendSynchronousMessage although the platform/CA defined OSCI-Transport to be used within ITT and/or ITP. It might also occur when no electronical submission of offers is wanted (only postal delivery).</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
        <xs:element name="name" type="xs:normalizedString" form="unqualified" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
      <xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:errorCodeType">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute name="listVersionID" type="xs:normalizedString" use="optional" fixed="1.0">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Die konkrete Version der zu nutzenden Codeliste wird mit diesem XML-Attribut übertragen.

Analog zum listURI ist die Bestimmung der Version einer Codeliste bei der Übertragung eines Codes zwingend. Die Version kann jedoch ebenfalls bereits im XÖV-Standard festgelegt werden (es handelt sich in diesem Fall um einen Code-Typ 1 oder 2).</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
</xs:complexContent>
</xs:complexType>

attribute Code.ErrorCodeType/@listURI

type

xs:anyURI

properties

use	optional
fixed	urn:org:xvergabe:codelists:errorCodeType

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

<xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:errorCodeType">
<xs:annotation>
<xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
<xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
</xs:annotation>
</xs:attribute>

attribute Code.ErrorCodeType/@listVersionID

type

xs:normalizedString

properties

use	optional
fixed	1.0

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

element Code.ErrorCodeType/code

diagram

type

restriction of xs:token

properties

content	simple
form	unqualified

facets

Kind

Value

Annotation

enumeration

ATTACHMENTS_EXCEED_MAX_SIZE_FOR_ALL_ATTACHMENTS

documentation

error indicating that the total size of all attached files to the clients message exceed the limits of the platform as defined in the TMI.
The platform SHALL name the defined size limit and the exceeding size of all attached files within "responseInformation".

enumeration

ATTACHMENT_EXCEEDS_MAX_SIZE_PER_ATTACHMENT

documentation

error indicating that the size of at least one attached file to the clients message exceeds the limit of the platform as defined in the TMI. The platform SHALL name the attachment identifier, the defined size limit and the exceeding size of the attached file within "responseInformation".

enumeration

AUTHENTICATION_ERROR

documentation

indicates that the user could not be authenticated. the reasons for this can be various (e.g wrong username and/or password, password must be renewed). the platform MAY give detailed information about the cause of this error in "response information".

enumeration

AUTHORIZATION_ERROR

documentation

indicates the occurence of an authorization problem. this is most likely the case when a successfully authenticated user tries to access a ressource (tendering procedure or document) without the right to do so (e.g. the successfully authenticated user trys to send a message within a tendering procedure he has not subscribed to).

enumeration

INVALID_ACTION_FOR_CURRENT_PROCEDURE_STATUS

documentation

this error indicates a violation of the procedure status model. it occurs when a client tries to execute an operation or sends a message which is not allowed in the current state of the procedure (e.g. the client tries to subscribe himself to a procedure being closed allready).
The platform MUST inform the client about the cause of the problem (the status of the procedure) within "response information".
In the special case of belated submissions of offers (or participation requests) - WITHIN the respective evaluation phase - a platform MAY either accept the submission (produce a WARNING) or reject the submission with the special ERROR code SUBMISSION_AFTER_DEADLINE.
In the special case of extremely belated submissions of offers (or participation requests) - AFTER the respective evaluation phase - a platform MUST reject the submission with the special ERROR code SUBMISSION_AFTER_EVALUATION_PHASE.

enumeration

INVALID_DOCUMENT_ID

documentation

error indicating that the client wanted to access a document via getDocuments from the platform and used a wrong (non-existent) documentID.

enumeration

INVALID_LASTKNOWNMSG_ID

documentation

an error which might occur in the context of a getMessages-transaction in the case the client references a messageId to be the latest one he has knowledge of within a procedure but the platform does not know this messageId (unknown message id) or the messageID does not belong to the given tenderingProcedureID. The platform MUST supply additional information about the cause in "response information"

enumeration

INVALID_MESSAGE_ID

documentation

an error which might occur in the context of a getMessages-transaction in the case the client references a certain messageId but the platform does not know this messageId (unknown message id) or the messageID does not belong to a message sent to this particular client. The platform MUST supply additional information about the cause in "response information"

enumeration

INVALID_OBJECTID_FOR_WITHDRAWAL

documentation

an error which might occur in the context of a withdrawal when the client wishes to withdraw an offer/participation request but the referenced offer/participation request is not known to the platform, identifies something else (e.g. a message) but not an offer or participation request or does not belong to the client.
This error may thus occur within a sendSynchronous-Response-Message or a getOSCITransferID-Response-Message.

enumeration

INVALID_TENDERING_PROCEDURE_ID

documentation

an error indicating a wrongfully referenced tendering procedure id, e.g. one which is unknown to the platform.

enumeration

SECONDARY_CONTAINER_NOT_SUPPORTED

documentation

error indicating that the offer or participation message was not constructed according to the rules of the ITT/ITP message regarding the number of containers.
The error is encountered when a client tries to submit an offer/participation consisting of a primary AND a secondary container while the ITT/ITP specified that the platform is not able to process secondaryContainers (onlyPrimaryContainerAllowed is set to true).

enumeration

SUBMISSION_AFTER_DEADLINE

documentation

specialized error code of INVALID_ACTION_FOR_CURRENT_PROCEDURE_STATUS in case of a belated submission of offers/participation requests - within the corresponding evaluation phase. this error might occur when the platform rejects the submission in this phase. The error can only occur within a getOSCITransferID- or sendSynchronousMessage-Response.

enumeration

SUBMISSION_AFTER_EVALUATION_PHASE

documentation

specialized error code of INVALID_ACTION_FOR_CURRENT_PROCEDURE_STATUS in case of an extremely belated submission of offers/participation requests - AFTER the corresponding evaluation phase. Every platform shall reject submissions then. The error can only occur within a getOSCITransferID- or sendSynchronousMessage-Response.

enumeration

VALIDATION_ERROR

documentation

error indicating that the client message cannot be validated correctly (e.g. syntax error). It might also occur when a client message is syntactically correct but is missing referenced objects (e.g. the client message references attachments but is missing those referenced attachments).

enumeration

WRONG_ENCRYPTION_RECIPIENTS

documentation

error indicating that the offer/participation request container(s) is/are wrongfully encrypted, i.e. not encrypted for the encryption key(s) from the ITT/ITP message. It may only occur in an sendSynchronousResponse-Message.

enumeration

WRONG_TRANSPORT_PROTOCOL

documentation

indicates that the client tries to submit an offer, participation request or withdrawal via sendSynchronousMessage although the platform/CA defined OSCI-Transport to be used within ITT and/or ITP. It might also occur when no electronical submission of offers is wanted (only postal delivery).

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

In diesem XML-Element wird der Code einer Codeliste übermittelt.

source

<xs:element name="code" form="unqualified">
<xs:annotation>
    <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
    <xs:documentation>In diesem XML-Element wird der Code einer Codeliste übermittelt.</xs:documentation>
</xs:annotation>
<xs:simpleType>
    <xs:restriction base="xs:token">
      <xs:enumeration value="ATTACHMENTS_EXCEED_MAX_SIZE_FOR_ALL_ATTACHMENTS">
        <xs:annotation>
          <xs:documentation>error indicating that the total size of all attached files to the clients message exceed the limits of the platform as defined in the TMI.
The platform SHALL name the defined size limit and the exceeding size of all attached files within "responseInformation".</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="ATTACHMENT_EXCEEDS_MAX_SIZE_PER_ATTACHMENT">
        <xs:annotation>
          <xs:documentation>error indicating that the size of at least one attached file to the clients message exceeds the limit of the platform as defined in the TMI. The platform SHALL name the attachment identifier, the defined size limit and the exceeding size of the attached file within "responseInformation".</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="AUTHENTICATION_ERROR">
        <xs:annotation>
          <xs:documentation>indicates that the user could not be authenticated. the reasons for this can be various (e.g wrong username and/or password, password must be renewed). the platform MAY give detailed information about the cause of this error in "response information".</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="AUTHORIZATION_ERROR">
        <xs:annotation>
          <xs:documentation>indicates the occurence of an authorization problem. this is most likely the case when a successfully authenticated user tries to access a ressource (tendering procedure or document) without the right to do so (e.g. the successfully authenticated user trys to send a message within a tendering procedure he has not subscribed to).</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="INVALID_ACTION_FOR_CURRENT_PROCEDURE_STATUS">
        <xs:annotation>
          <xs:documentation>this error indicates a violation of the procedure status model. it occurs when a client tries to execute an operation or sends a message which is not allowed in the current state of the procedure (e.g. the client tries to subscribe himself to a procedure being closed allready).
The platform MUST inform the client about the cause of the problem (the status of the procedure) within "response information".
In the special case of belated submissions of offers (or participation requests) - WITHIN the respective evaluation phase - a platform MAY either accept the submission (produce a WARNING) or reject the submission with the special ERROR code SUBMISSION_AFTER_DEADLINE.
In the special case of extremely belated submissions of offers (or participation requests) - AFTER the respective evaluation phase - a platform MUST reject the submission with the special ERROR code SUBMISSION_AFTER_EVALUATION_PHASE.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="INVALID_DOCUMENT_ID">
        <xs:annotation>
          <xs:documentation>error indicating that the client wanted to access a document via getDocuments from the platform and used a wrong (non-existent) documentID.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="INVALID_LASTKNOWNMSG_ID">
        <xs:annotation>
          <xs:documentation>an error which might occur in the context of a getMessages-transaction in the case the client references a messageId to be the latest one he has knowledge of within a procedure but the platform does not know this messageId (unknown message id) or the messageID does not belong to the given tenderingProcedureID. The platform MUST supply additional information about the cause in "response information"</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="INVALID_MESSAGE_ID">
        <xs:annotation>
          <xs:documentation>an error which might occur in the context of a getMessages-transaction in the case the client references a certain messageId but the platform does not know this messageId (unknown message id) or the messageID does not belong to a message sent to this particular client. The platform MUST supply additional information about the cause in "response information"</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="INVALID_OBJECTID_FOR_WITHDRAWAL">
        <xs:annotation>
          <xs:documentation>an error which might occur in the context of a withdrawal when the client wishes to withdraw an offer/participation request but the referenced offer/participation request is not known to the platform, identifies something else (e.g. a message) but not an offer or participation request or does not belong to the client.
This error may thus occur within a sendSynchronous-Response-Message or a getOSCITransferID-Response-Message.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="INVALID_TENDERING_PROCEDURE_ID">
        <xs:annotation>
          <xs:documentation>an error indicating a wrongfully referenced tendering procedure id, e.g. one which is unknown to the platform.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="SECONDARY_CONTAINER_NOT_SUPPORTED">
        <xs:annotation>
          <xs:documentation>error indicating that the offer or participation message was not constructed according to the rules of the ITT/ITP message regarding the number of containers.
The error is encountered when a client tries to submit an offer/participation consisting of a primary AND a secondary container while the ITT/ITP specified that the platform is not able to process secondaryContainers (onlyPrimaryContainerAllowed is set to true).</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="SUBMISSION_AFTER_DEADLINE">
        <xs:annotation>
          <xs:documentation>specialized error code of INVALID_ACTION_FOR_CURRENT_PROCEDURE_STATUS in case of a belated submission of offers/participation requests - within the corresponding evaluation phase. this error might occur when the platform rejects the submission in this phase. The error can only occur within a getOSCITransferID- or sendSynchronousMessage-Response.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="SUBMISSION_AFTER_EVALUATION_PHASE">
        <xs:annotation>
          <xs:documentation>specialized error code of INVALID_ACTION_FOR_CURRENT_PROCEDURE_STATUS in case of an extremely belated submission of offers/participation requests - AFTER the corresponding evaluation phase. Every platform shall reject submissions then. The error can only occur within a getOSCITransferID- or sendSynchronousMessage-Response.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="VALIDATION_ERROR">
        <xs:annotation>
          <xs:documentation>error indicating that the client message cannot be validated correctly (e.g. syntax error). It might also occur when a client message is syntactically correct but is missing referenced objects (e.g. the client message references attachments but is missing those referenced attachments).</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="WRONG_ENCRYPTION_RECIPIENTS">
        <xs:annotation>
          <xs:documentation>error indicating that the offer/participation request container(s) is/are wrongfully encrypted, i.e. not encrypted for the encryption key(s) from the ITT/ITP message. It may only occur in an sendSynchronousResponse-Message.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="WRONG_TRANSPORT_PROTOCOL">
        <xs:annotation>
          <xs:documentation>indicates that the client tries to submit an offer, participation request or withdrawal via sendSynchronousMessage although the platform/CA defined OSCI-Transport to be used within ITT and/or ITP. It might also occur when no electronical submission of offers is wanted (only postal delivery).</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
</xs:element>

element Code.ErrorCodeType/name

diagram

type

xs:normalizedString

properties

minOcc	0
maxOcc	1
content	simple
form	unqualified

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.

source

complexType Code.ProcedureType

diagram

namespace

http://xvergabe.org/codelists/xsd/4

type

restriction of xoev-code:Code

properties

base	xoev-code:Code

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:procedureType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

Definition of the type of a tendering procedure.

source

<xs:complexType name="Code.ProcedureType">
<xs:annotation>
    <xs:documentation>Definition of the type of a tendering procedure.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:restriction base="xoev-code:Code">
      <xs:sequence>
        <xs:element name="code" form="unqualified">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>In diesem XML-Element wird der Code einer Codeliste übermittelt.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:token">
              <xs:enumeration value="NEGOTIATED_PROCEDURE">
                <xs:annotation>
                  <xs:documentation>negotiated procedure (de: Verhandlungsverfahren ohne Teilnahmewettbewerb, unter- und oberschwellig)</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="NEGOTIATED_PROCEDURE_WITH_PARTICIPATION_CONTEST">
                <xs:annotation>
                  <xs:documentation>negotiated procedure with participation contest (de: Verhandlungsverfahren mit vorgeschaltenem Teilnahmewettbewerb, unter- und oberschwellig)</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="OPEN_PROCEDURE">
                <xs:annotation>
                  <xs:documentation>open procedure (DE: offenes Verfahren, oberschwellig)</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="PUBLIC_TENDER">
                <xs:annotation>
                  <xs:documentation>public tender (DE: öffentliche Ausschreibung, unterschwellig)</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="RESTRICTED_PROCEDURE">
                <xs:annotation>
                  <xs:documentation>restricted procedure (DE: nichtoffenes Verfahren mit Teilnahmewettbewerb, oberschwellig)</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="RESTRICTED_TENDER">
                <xs:annotation>
                  <xs:documentation>restricted tender (DE: beschränkte Ausschreibung, unterschwellig)</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="RESTRICTED_TENDER_WITH_PARTICIPATION_CONTEST">
                <xs:annotation>
                  <xs:documentation>restricted tender with participation contest (DE: beschränkte Ausschreibung mit vorgeschaltetem Teilnahmewettbewerb, unterschwellig)</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="SINGLE_TENDER_ACTION">
                <xs:annotation>
                  <xs:documentation>single tender action (DE: freihändige Vergabe ohne Teilnahmewettbewerb, unterschwellig)</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="SINGLE_TENDER_ACTION_WITH_PARTICIPATION_CONTEST">
                <xs:annotation>
                  <xs:documentation>single tender action with participation contest (DE: freihändige Vergabe mit vorgeschaltenem Teilnahmewettbewerb, unterschwellig)</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
        <xs:element name="name" type="xs:normalizedString" form="unqualified" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
      <xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:procedureType">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute name="listVersionID" type="xs:normalizedString" use="optional" fixed="1.0">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Die konkrete Version der zu nutzenden Codeliste wird mit diesem XML-Attribut übertragen.

Analog zum listURI ist die Bestimmung der Version einer Codeliste bei der Übertragung eines Codes zwingend. Die Version kann jedoch ebenfalls bereits im XÖV-Standard festgelegt werden (es handelt sich in diesem Fall um einen Code-Typ 1 oder 2).</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
</xs:complexContent>
</xs:complexType>

attribute Code.ProcedureType/@listURI

type

xs:anyURI

properties

use	optional
fixed	urn:org:xvergabe:codelists:procedureType

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

<xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:procedureType">
<xs:annotation>
<xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
<xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
</xs:annotation>
</xs:attribute>

attribute Code.ProcedureType/@listVersionID

type

xs:normalizedString

properties

use	optional
fixed	1.0

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

element Code.ProcedureType/code

diagram

type

restriction of xs:token

properties

content	simple
form	unqualified

facets

Kind

Value

Annotation

enumeration

NEGOTIATED_PROCEDURE

documentation

negotiated procedure (de: Verhandlungsverfahren ohne Teilnahmewettbewerb, unter- und oberschwellig)

enumeration

NEGOTIATED_PROCEDURE_WITH_PARTICIPATION_CONTEST

documentation

negotiated procedure with participation contest (de: Verhandlungsverfahren mit vorgeschaltenem Teilnahmewettbewerb, unter- und oberschwellig)

enumeration

OPEN_PROCEDURE

documentation

open procedure (DE: offenes Verfahren, oberschwellig)

enumeration

PUBLIC_TENDER

documentation

public tender (DE: öffentliche Ausschreibung, unterschwellig)

enumeration

RESTRICTED_PROCEDURE

documentation

restricted procedure (DE: nichtoffenes Verfahren mit Teilnahmewettbewerb, oberschwellig)

enumeration

RESTRICTED_TENDER

documentation

restricted tender (DE: beschränkte Ausschreibung, unterschwellig)

enumeration

RESTRICTED_TENDER_WITH_PARTICIPATION_CONTEST

documentation

restricted tender with participation contest (DE: beschränkte Ausschreibung mit vorgeschaltetem Teilnahmewettbewerb, unterschwellig)

enumeration

SINGLE_TENDER_ACTION

documentation

single tender action (DE: freihändige Vergabe ohne Teilnahmewettbewerb, unterschwellig)

enumeration

SINGLE_TENDER_ACTION_WITH_PARTICIPATION_CONTEST

documentation

single tender action with participation contest (DE: freihändige Vergabe mit vorgeschaltenem Teilnahmewettbewerb, unterschwellig)

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

In diesem XML-Element wird der Code einer Codeliste übermittelt.

source

element Code.ProcedureType/name

diagram

type

xs:normalizedString

properties

minOcc	0
maxOcc	1
content	simple
form	unqualified

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.

source

complexType Code.SignatureLevelType

diagram

namespace

http://xvergabe.org/codelists/xsd/4

type

restriction of xoev-code:Code

properties

base	xoev-code:Code

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:signatureLevelType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

Information about the level of an applied or expected signature.

source

<xs:complexType name="Code.SignatureLevelType">
<xs:annotation>
    <xs:documentation>Information about the level of an applied or expected signature.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:restriction base="xoev-code:Code">
      <xs:sequence>
        <xs:element name="code" form="unqualified">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>In diesem XML-Element wird der Code einer Codeliste übermittelt.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:token">
              <xs:enumeration value="ADVANCED">
                <xs:annotation>
                  <xs:documentation>An advanced electronical signature is required.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="NONE">
                <xs:annotation>
                  <xs:documentation>No signature is required</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="QUALIFIED">
                <xs:annotation>
                  <xs:documentation>A qualified electronical signature is required.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
        <xs:element name="name" type="xs:normalizedString" form="unqualified" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
      <xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:signatureLevelType">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute name="listVersionID" type="xs:normalizedString" use="optional" fixed="1.0">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Die konkrete Version der zu nutzenden Codeliste wird mit diesem XML-Attribut übertragen.

Analog zum listURI ist die Bestimmung der Version einer Codeliste bei der Übertragung eines Codes zwingend. Die Version kann jedoch ebenfalls bereits im XÖV-Standard festgelegt werden (es handelt sich in diesem Fall um einen Code-Typ 1 oder 2).</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
</xs:complexContent>
</xs:complexType>

attribute Code.SignatureLevelType/@listURI

type

xs:anyURI

properties

use	optional
fixed	urn:org:xvergabe:codelists:signatureLevelType

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

<xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:signatureLevelType">
<xs:annotation>
<xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
<xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
</xs:annotation>
</xs:attribute>

attribute Code.SignatureLevelType/@listVersionID

type

xs:normalizedString

properties

use	optional
fixed	1.0

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

element Code.SignatureLevelType/code

diagram

type

restriction of xs:token

properties

content	simple
form	unqualified

facets

Kind

Value

Annotation

enumeration

ADVANCED

documentation

An advanced electronical signature is required.

enumeration

NONE

documentation

No signature is required

enumeration

QUALIFIED

documentation

A qualified electronical signature is required.

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

In diesem XML-Element wird der Code einer Codeliste übermittelt.

source

element Code.SignatureLevelType/name

diagram

type

xs:normalizedString

properties

minOcc	0
maxOcc	1
content	simple
form	unqualified

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.

source

complexType Code.StatusType

diagram

namespace

http://xvergabe.org/codelists/xsd/4

type

restriction of xoev-code:Code

properties

base	xoev-code:Code

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:statusType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

Definition of the state of a tendering procedure.

source

<xs:complexType name="Code.StatusType">
<xs:annotation>
    <xs:documentation>Definition of the state of a tendering procedure.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:restriction base="xoev-code:Code">
      <xs:sequence>
        <xs:element name="code" form="unqualified">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>In diesem XML-Element wird der Code einer Codeliste übermittelt.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:token">
              <xs:enumeration value="BIDDING_PHASE">
                <xs:annotation>
                  <xs:documentation>In this status, it is NOT valid anymore for a client to send Participation documents. It is however possible for a client to send Offer documents. This is the initial status of tendering procedures without participation contest.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="CANCELLATION">
                <xs:annotation>
                  <xs:documentation>In this status, the tendering procedure has been cancelled. The tendering procedure has been deleted or archived and it is NOT possible anymore for a client to communicate with the server about this tendering procedure.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="CLOSED">
                <xs:annotation>
                  <xs:documentation>In this status, the tendering procedure has been closed. It is NOT possible anymore for a client to communicate with the server about this tendering procedure.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="PARTICIPATION_EVALUATION_PHASE">
                <xs:annotation>
                  <xs:documentation>In this status, the tendering procedure has passed the PARTICIPATION_PHASE. It is NOT valid anymore for a client to send Participation documents. It is NOT YET possible for a client to send Offer documents. This status is only valid for tendering procedures with participation contest.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="PARTICIPATION_PHASE">
                <xs:annotation>
                  <xs:documentation>In this status, it is valid for a client to send Participation documents. It is NOT possible for a client to send Offer documents. This status is only valid for tendering procedures with participation competition. This is the initial status of tendering procedures with participation contest.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="TENDER_EVALUATION_PHASE">
                <xs:annotation>
                  <xs:documentation>In this status, the tendering procedure has passed the BIDDING_PHASE. It is NOT valid anymore for a client to send Offer documents.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
        <xs:element name="name" type="xs:normalizedString" form="unqualified" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
      <xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:statusType">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute name="listVersionID" type="xs:normalizedString" use="optional" fixed="1.0">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Die konkrete Version der zu nutzenden Codeliste wird mit diesem XML-Attribut übertragen.

Analog zum listURI ist die Bestimmung der Version einer Codeliste bei der Übertragung eines Codes zwingend. Die Version kann jedoch ebenfalls bereits im XÖV-Standard festgelegt werden (es handelt sich in diesem Fall um einen Code-Typ 1 oder 2).</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
</xs:complexContent>
</xs:complexType>

attribute Code.StatusType/@listURI

type

xs:anyURI

properties

use	optional
fixed	urn:org:xvergabe:codelists:statusType

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

<xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:statusType">
<xs:annotation>
<xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
<xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
</xs:annotation>
</xs:attribute>

attribute Code.StatusType/@listVersionID

type

xs:normalizedString

properties

use	optional
fixed	1.0

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

element Code.StatusType/code

diagram

type

restriction of xs:token

properties

content	simple
form	unqualified

facets

Kind

Value

Annotation

enumeration

BIDDING_PHASE

documentation

In this status, it is NOT valid anymore for a client to send Participation documents. It is however possible for a client to send Offer documents. This is the initial status of tendering procedures without participation contest.

enumeration

CANCELLATION

documentation

In this status, the tendering procedure has been cancelled. The tendering procedure has been deleted or archived and it is NOT possible anymore for a client to communicate with the server about this tendering procedure.

enumeration

CLOSED

documentation

In this status, the tendering procedure has been closed. It is NOT possible anymore for a client to communicate with the server about this tendering procedure.

enumeration

PARTICIPATION_EVALUATION_PHASE

documentation

In this status, the tendering procedure has passed the PARTICIPATION_PHASE. It is NOT valid anymore for a client to send Participation documents. It is NOT YET possible for a client to send Offer documents. This status is only valid for tendering procedures with participation contest.

enumeration

PARTICIPATION_PHASE

documentation

In this status, it is valid for a client to send Participation documents. It is NOT possible for a client to send Offer documents. This status is only valid for tendering procedures with participation competition. This is the initial status of tendering procedures with participation contest.

enumeration

TENDER_EVALUATION_PHASE

documentation

In this status, the tendering procedure has passed the BIDDING_PHASE. It is NOT valid anymore for a client to send Offer documents.

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

In diesem XML-Element wird der Code einer Codeliste übermittelt.

source

element Code.StatusType/name

diagram

type

xs:normalizedString

properties

minOcc	0
maxOcc	1
content	simple
form	unqualified

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.

source

complexType Code.TimeLimitType

diagram

namespace

http://xvergabe.org/codelists/xsd/4

type

restriction of xoev-code:Code

properties

base	xoev-code:Code

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:timeLimitType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

Definition of the type of a time limit.

source

<xs:complexType name="Code.TimeLimitType">
<xs:annotation>
    <xs:documentation>Definition of the type of a time limit.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:restriction base="xoev-code:Code">
      <xs:sequence>
        <xs:element name="code" form="unqualified">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>In diesem XML-Element wird der Code einer Codeliste übermittelt.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:token">
              <xs:enumeration value="AWARDING">
                <xs:annotation>
                  <xs:documentation>The deadline for the final awarding of the procedure.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="PARTICIPATION">
                <xs:annotation>
                  <xs:documentation>The deadline for submission of participation requests.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="PROVIDING">
                <xs:annotation>
                  <xs:documentation>The deadline for the economic operator to provide information concerning the procedure (e.g. answers to bidder inquiries).</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="REQUESTING">
                <xs:annotation>
                  <xs:documentation>The deadline for the bidders to submit inquiries concerning the tendering procedure.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="SUBMISSION">
                <xs:annotation>
                  <xs:documentation>The deadline for submission of offers.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
        <xs:element name="name" type="xs:normalizedString" form="unqualified" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
      <xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:timeLimitType">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute name="listVersionID" type="xs:normalizedString" use="optional" fixed="1.0">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Die konkrete Version der zu nutzenden Codeliste wird mit diesem XML-Attribut übertragen.

Analog zum listURI ist die Bestimmung der Version einer Codeliste bei der Übertragung eines Codes zwingend. Die Version kann jedoch ebenfalls bereits im XÖV-Standard festgelegt werden (es handelt sich in diesem Fall um einen Code-Typ 1 oder 2).</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
</xs:complexContent>
</xs:complexType>

attribute Code.TimeLimitType/@listURI

type

xs:anyURI

properties

use	optional
fixed	urn:org:xvergabe:codelists:timeLimitType

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

<xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:timeLimitType">
<xs:annotation>
<xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
<xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
</xs:annotation>
</xs:attribute>

attribute Code.TimeLimitType/@listVersionID

type

xs:normalizedString

properties

use	optional
fixed	1.0

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

element Code.TimeLimitType/code

diagram

type

restriction of xs:token

properties

content	simple
form	unqualified

facets

Kind

Value

Annotation

enumeration

AWARDING

documentation

The deadline for the final awarding of the procedure.

enumeration

PARTICIPATION

documentation

The deadline for submission of participation requests.

enumeration

PROVIDING

documentation

The deadline for the economic operator to provide information concerning the procedure (e.g. answers to bidder inquiries).

enumeration

REQUESTING

documentation

The deadline for the bidders to submit inquiries concerning the tendering procedure.

enumeration

SUBMISSION

documentation

The deadline for submission of offers.

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

In diesem XML-Element wird der Code einer Codeliste übermittelt.

source

element Code.TimeLimitType/name

diagram

type

xs:normalizedString

properties

minOcc	0
maxOcc	1
content	simple
form	unqualified

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.

source

complexType Code.UploadLimitType

diagram

namespace

http://xvergabe.org/codelists/xsd/4

type

restriction of xoev-code:Code

properties

base	xoev-code:Code

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:uploadLimitType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

Definition of the type of an upload limit.

source

<xs:complexType name="Code.UploadLimitType">
<xs:annotation>
    <xs:documentation>Definition of the type of an upload limit.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:restriction base="xoev-code:Code">
      <xs:sequence>
        <xs:element name="code" form="unqualified">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>In diesem XML-Element wird der Code einer Codeliste übermittelt.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:token">
              <xs:enumeration value="MAXIMUM_SIZE_ALL_ATTACHMENTS">
                <xs:annotation>
                  <xs:documentation>The maximum total size of all attachments within a message in bytes. The limit is referring to the gross size of all attachment (after/including base64 encoding).</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="MAXIMUM_SIZE_PER_ATTACHMENT">
                <xs:annotation>
                  <xs:documentation>The maximum size of an attachment within a message in bytes. The limit is referring to the gross size of the attachment (after/including base64 encoding).</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
        <xs:element name="name" type="xs:normalizedString" form="unqualified" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
      <xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:uploadLimitType">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute name="listVersionID" type="xs:normalizedString" use="optional" fixed="1.0">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Die konkrete Version der zu nutzenden Codeliste wird mit diesem XML-Attribut übertragen.

Analog zum listURI ist die Bestimmung der Version einer Codeliste bei der Übertragung eines Codes zwingend. Die Version kann jedoch ebenfalls bereits im XÖV-Standard festgelegt werden (es handelt sich in diesem Fall um einen Code-Typ 1 oder 2).</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
</xs:complexContent>
</xs:complexType>

attribute Code.UploadLimitType/@listURI

type

xs:anyURI

properties

use	optional
fixed	urn:org:xvergabe:codelists:uploadLimitType

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

<xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:uploadLimitType">
<xs:annotation>
<xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
<xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
</xs:annotation>
</xs:attribute>

attribute Code.UploadLimitType/@listVersionID

type

xs:normalizedString

properties

use	optional
fixed	1.0

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

element Code.UploadLimitType/code

diagram

type

restriction of xs:token

properties

content	simple
form	unqualified

facets

Kind

Value

Annotation

enumeration

MAXIMUM_SIZE_ALL_ATTACHMENTS

documentation

The maximum total size of all attachments within a message in bytes. The limit is referring to the gross size of all attachment (after/including base64 encoding).

enumeration

MAXIMUM_SIZE_PER_ATTACHMENT

documentation

The maximum size of an attachment within a message in bytes. The limit is referring to the gross size of the attachment (after/including base64 encoding).

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

In diesem XML-Element wird der Code einer Codeliste übermittelt.

source

element Code.UploadLimitType/name

diagram

type

xs:normalizedString

properties

minOcc	0
maxOcc	1
content	simple
form	unqualified

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.

source

complexType Code.WarningCodeType

diagram

namespace

http://xvergabe.org/codelists/xsd/4

type

restriction of xoev-code:Code

properties

base	xoev-code:Code

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

urn:org:xvergabe:codelists:warningCodeType

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

xs:normalizedString

optional

1.0

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

annotation

documentation

CodeList of Warning codes to be used in a response for a transaction which succeeded with limitations. When used, a response information text SHALL be given in addition.

source

<xs:complexType name="Code.WarningCodeType">
<xs:annotation>
    <xs:documentation>CodeList of Warning codes to be used in a response for a transaction which succeeded with limitations. When used, a response information text SHALL be given in addition.</xs:documentation>
</xs:annotation>
<xs:complexContent>
    <xs:restriction base="xoev-code:Code">
      <xs:sequence>
        <xs:element name="code" form="unqualified">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>In diesem XML-Element wird der Code einer Codeliste übermittelt.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:token">
              <xs:enumeration value="ALREADY_SUBSCRIBED">
                <xs:annotation>
                  <xs:documentation>this warning indicates that the client is already subscribed to the procedure he asked to subscribe to. This warning shall be submitted by the platform when the client tries to subscribe to a procedure he successfully subscribed before.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="INVALID_ITP_ID">
                <xs:annotation>
                  <xs:documentation>warning indicating that a referenced ITP-MessageID is not known by the platform (or is not issued to the client or renders another object (eg. an ITT-Message)). This warning may occur in the context of submitting a participation request. Thus it can only occur in a getOSCITransferID- and sendSynchronousMessage-Response.
The platform MAY NOT reject the participation request in this case (hence this being a warning and not an error).</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="INVALID_ITT_ID">
                <xs:annotation>
                  <xs:documentation>warning indicating that a referenced ITT-MessageID is not known by the platform (or is not issued to the client or renders another object (eg. an ITP-Message)). This warning may occur in the context of submitting an offer. Thus it can only occur in a getOSCITransferID- and sendSynchronousMessage-Response.
The platform MAY NOT reject the offer in this case (hence this being a warning and not an error).</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="NEWER_ITP_VERSION_AVAILABLE">
                <xs:annotation>
                  <xs:documentation>warning indicating that the referenced ITP-Message when submitting a participation request is outdated, i.e. a newer ITP-version has been released/submitted to the client but the clients participation request is made out to the older version.
This warning may only occur within a getOSCITransferID- or sendSynchronousMessage-Response.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="NEWER_ITT_VERSION_AVAILABLE">
                <xs:annotation>
                  <xs:documentation>warning indicating that the referenced ITT-Message when submitting an offer is outdated, i.e. a newer ITT-version has been released/submitted to the client but the clients offer is made out to the older version.
This warning may only occur within a getOSCITransferID- or sendSynchronousMessage-Response.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="OFFER_CONTAINER_MISSING">
                <xs:annotation>
                  <xs:documentation>warning indicating that the clients offer is not structured according to the ITT. It occurs in the case, the ITT defines files to be included in the primary container AND (other) files to be included in the secondary one, but the clients offer consists only of 1 attachment and not as expected two.
It can only occur in a sendSynchronousMessage-Response.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="OFFER_CONTAINER_UNENCRYPTED">
                <xs:annotation>
                  <xs:documentation>warning indicating that the clients offer is not encrypted although the ITT defined encryption parameters.
It can only occur in a sendSynchronousMessage-Response.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="PARTICIPATION_REQUEST_ALREADY_SUBMITTED_WITHOUT_WITHDRAWAL">
                <xs:annotation>
                  <xs:documentation>warning occurring when submitting a participation request indicating that the client has submitted a participation request already without withdrawing it first.
It can only occur in getOSCITransferID- or sendSynchronousMessage-Responses.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="PARTICIPATION_REQUEST_CONTAINER_MISSING">
                <xs:annotation>
                  <xs:documentation>warning indicating that the clients participation request is not structured according to the ITP. It occurs in the case, the ITP defines files to be included in the primary container AND (other) files to be included in the secondary one, but the clients participation message consists only of 1 attachment and not as expected two.
It can only occur in a sendSynchronousMessage-Response.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="PARTICIPATION_REQUEST_CONTAINER_UNENCRYPTED">
                <xs:annotation>
                  <xs:documentation>warning indicating that the clients participation request is not encrypted although the ITP defined encryption parameters.
It can only occur in a sendSynchronousMessage-Response.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="SIGNATURE_LEVEL_DOESNT_MATCH">
                <xs:annotation>
                  <xs:documentation>warning indicating that the signature level of an attached document to a withdrawal message does not match the informations from ITT/ITP message.
It may only occur within sendSynchronousMessage-Responses.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="SUBMISSION_AFTER_DEADLINE">
                <xs:annotation>
                  <xs:documentation>this warning occurs in the special case of a belated submission of offers/participation requests when the platform decides to accept the submission even though the according deadline has passed (the procedure is in the corresponding evaluation phase).
It might only occur within getOSCITransferID- and sendSynchronousMessage-Responses.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="SUBSCRIPTION_PENDING">
                <xs:annotation>
                  <xs:documentation>this warning indicates that the subscription request of an authenticated client has to be approved by the contracting authority. Thus the warning may only occur within a subscriptionResponse-Message.
In case the contracting authority approves the request, the client can synchronize messages within the given procedure after the approval (he wont get another notify). In case the contracting authority denies the request, the client may never synchronize messages in this given procedure. The client will be notified out of band (e.g. via mail) by the contracting authority.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
        <xs:element name="name" type="xs:normalizedString" form="unqualified" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
            <xs:documentation>Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
      <xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:warningCodeType">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute name="listVersionID" type="xs:normalizedString" use="optional" fixed="1.0">
        <xs:annotation>
          <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
          <xs:documentation>Die konkrete Version der zu nutzenden Codeliste wird mit diesem XML-Attribut übertragen.

Analog zum listURI ist die Bestimmung der Version einer Codeliste bei der Übertragung eines Codes zwingend. Die Version kann jedoch ebenfalls bereits im XÖV-Standard festgelegt werden (es handelt sich in diesem Fall um einen Code-Typ 1 oder 2).</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:restriction>
</xs:complexContent>
</xs:complexType>

attribute Code.WarningCodeType/@listURI

type

xs:anyURI

properties

use	optional
fixed	urn:org:xvergabe:codelists:warningCodeType

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

<xs:attribute name="listURI" type="xs:anyURI" use="optional" fixed="urn:org:xvergabe:codelists:warningCodeType">
<xs:annotation>
<xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
<xs:documentation>Mit diesem XML-Attribut wird die Kennung der Codeliste übermittelt, in deren Kontext der jeweilige Code zu interpretieren ist. Die Kennung identifiziert die Codeliste, nicht jedoch deren Version eindeutig.

Wird bereits im Rahmen des XÖV-Standards eine Kennung vorgegeben (es handelt sich in diesem Fall um einen Code-Typ 1, 2 oder 3) darf auf eine nochmalige Angabe der Kennung bei der Übermittlung eines Codes verzichtet werden. Aus diesem Grund ist das XML-Attribut listURI zunächst als optional deklariert.</xs:documentation>
</xs:annotation>
</xs:attribute>

attribute Code.WarningCodeType/@listVersionID

type

xs:normalizedString

properties

use	optional
fixed	1.0

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

source

element Code.WarningCodeType/code

diagram

type

restriction of xs:token

properties

content	simple
form	unqualified

facets

Kind

Value

Annotation

enumeration

ALREADY_SUBSCRIBED

documentation

this warning indicates that the client is already subscribed to the procedure he asked to subscribe to. This warning shall be submitted by the platform when the client tries to subscribe to a procedure he successfully subscribed before.

enumeration

INVALID_ITP_ID

documentation

warning indicating that a referenced ITP-MessageID is not known by the platform (or is not issued to the client or renders another object (eg. an ITT-Message)). This warning may occur in the context of submitting a participation request. Thus it can only occur in a getOSCITransferID- and sendSynchronousMessage-Response.
The platform MAY NOT reject the participation request in this case (hence this being a warning and not an error).

enumeration

INVALID_ITT_ID

documentation

warning indicating that a referenced ITT-MessageID is not known by the platform (or is not issued to the client or renders another object (eg. an ITP-Message)). This warning may occur in the context of submitting an offer. Thus it can only occur in a getOSCITransferID- and sendSynchronousMessage-Response.
The platform MAY NOT reject the offer in this case (hence this being a warning and not an error).

enumeration

NEWER_ITP_VERSION_AVAILABLE

documentation

warning indicating that the referenced ITP-Message when submitting a participation request is outdated, i.e. a newer ITP-version has been released/submitted to the client but the clients participation request is made out to the older version.
This warning may only occur within a getOSCITransferID- or sendSynchronousMessage-Response.

enumeration

NEWER_ITT_VERSION_AVAILABLE

documentation

warning indicating that the referenced ITT-Message when submitting an offer is outdated, i.e. a newer ITT-version has been released/submitted to the client but the clients offer is made out to the older version.
This warning may only occur within a getOSCITransferID- or sendSynchronousMessage-Response.

enumeration

OFFER_CONTAINER_MISSING

documentation

warning indicating that the clients offer is not structured according to the ITT. It occurs in the case, the ITT defines files to be included in the primary container AND (other) files to be included in the secondary one, but the clients offer consists only of 1 attachment and not as expected two.
It can only occur in a sendSynchronousMessage-Response.

enumeration

OFFER_CONTAINER_UNENCRYPTED

documentation

warning indicating that the clients offer is not encrypted although the ITT defined encryption parameters.
It can only occur in a sendSynchronousMessage-Response.

enumeration

PARTICIPATION_REQUEST_ALREADY_SUBMITTED_WITHOUT_WITHDRAWAL

documentation

warning occurring when submitting a participation request indicating that the client has submitted a participation request already without withdrawing it first.
It can only occur in getOSCITransferID- or sendSynchronousMessage-Responses.

enumeration

PARTICIPATION_REQUEST_CONTAINER_MISSING

documentation

warning indicating that the clients participation request is not structured according to the ITP. It occurs in the case, the ITP defines files to be included in the primary container AND (other) files to be included in the secondary one, but the clients participation message consists only of 1 attachment and not as expected two.
It can only occur in a sendSynchronousMessage-Response.

enumeration

PARTICIPATION_REQUEST_CONTAINER_UNENCRYPTED

documentation

warning indicating that the clients participation request is not encrypted although the ITP defined encryption parameters.
It can only occur in a sendSynchronousMessage-Response.

enumeration

SIGNATURE_LEVEL_DOESNT_MATCH

documentation

warning indicating that the signature level of an attached document to a withdrawal message does not match the informations from ITT/ITP message.
It may only occur within sendSynchronousMessage-Responses.

enumeration

SUBMISSION_AFTER_DEADLINE

documentation

this warning occurs in the special case of a belated submission of offers/participation requests when the platform decides to accept the submission even though the according deadline has passed (the procedure is in the corresponding evaluation phase).
It might only occur within getOSCITransferID- and sendSynchronousMessage-Responses.

enumeration

SUBSCRIPTION_PENDING

documentation

this warning indicates that the subscription request of an authenticated client has to be approved by the contracting authority. Thus the warning may only occur within a subscriptionResponse-Message.
In case the contracting authority approves the request, the client can synchronize messages within the given procedure after the approval (he wont get another notify). In case the contracting authority denies the request, the client may never synchronize messages in this given procedure. The client will be notified out of band (e.g. via mail) by the contracting authority.

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

In diesem XML-Element wird der Code einer Codeliste übermittelt.

source

<xs:element name="code" form="unqualified">
<xs:annotation>
    <xs:documentation>Dokumentation aus XOEV-Bibliothek:</xs:documentation>
    <xs:documentation>In diesem XML-Element wird der Code einer Codeliste übermittelt.</xs:documentation>
</xs:annotation>
<xs:simpleType>
    <xs:restriction base="xs:token">
      <xs:enumeration value="ALREADY_SUBSCRIBED">
        <xs:annotation>
          <xs:documentation>this warning indicates that the client is already subscribed to the procedure he asked to subscribe to. This warning shall be submitted by the platform when the client tries to subscribe to a procedure he successfully subscribed before.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="INVALID_ITP_ID">
        <xs:annotation>
          <xs:documentation>warning indicating that a referenced ITP-MessageID is not known by the platform (or is not issued to the client or renders another object (eg. an ITT-Message)). This warning may occur in the context of submitting a participation request. Thus it can only occur in a getOSCITransferID- and sendSynchronousMessage-Response.
The platform MAY NOT reject the participation request in this case (hence this being a warning and not an error).</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="INVALID_ITT_ID">
        <xs:annotation>
          <xs:documentation>warning indicating that a referenced ITT-MessageID is not known by the platform (or is not issued to the client or renders another object (eg. an ITP-Message)). This warning may occur in the context of submitting an offer. Thus it can only occur in a getOSCITransferID- and sendSynchronousMessage-Response.
The platform MAY NOT reject the offer in this case (hence this being a warning and not an error).</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="NEWER_ITP_VERSION_AVAILABLE">
        <xs:annotation>
          <xs:documentation>warning indicating that the referenced ITP-Message when submitting a participation request is outdated, i.e. a newer ITP-version has been released/submitted to the client but the clients participation request is made out to the older version.
This warning may only occur within a getOSCITransferID- or sendSynchronousMessage-Response.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="NEWER_ITT_VERSION_AVAILABLE">
        <xs:annotation>
          <xs:documentation>warning indicating that the referenced ITT-Message when submitting an offer is outdated, i.e. a newer ITT-version has been released/submitted to the client but the clients offer is made out to the older version.
This warning may only occur within a getOSCITransferID- or sendSynchronousMessage-Response.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="OFFER_CONTAINER_MISSING">
        <xs:annotation>
          <xs:documentation>warning indicating that the clients offer is not structured according to the ITT. It occurs in the case, the ITT defines files to be included in the primary container AND (other) files to be included in the secondary one, but the clients offer consists only of 1 attachment and not as expected two.
It can only occur in a sendSynchronousMessage-Response.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="OFFER_CONTAINER_UNENCRYPTED">
        <xs:annotation>
          <xs:documentation>warning indicating that the clients offer is not encrypted although the ITT defined encryption parameters.
It can only occur in a sendSynchronousMessage-Response.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="PARTICIPATION_REQUEST_ALREADY_SUBMITTED_WITHOUT_WITHDRAWAL">
        <xs:annotation>
          <xs:documentation>warning occurring when submitting a participation request indicating that the client has submitted a participation request already without withdrawing it first.
It can only occur in getOSCITransferID- or sendSynchronousMessage-Responses.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="PARTICIPATION_REQUEST_CONTAINER_MISSING">
        <xs:annotation>
          <xs:documentation>warning indicating that the clients participation request is not structured according to the ITP. It occurs in the case, the ITP defines files to be included in the primary container AND (other) files to be included in the secondary one, but the clients participation message consists only of 1 attachment and not as expected two.
It can only occur in a sendSynchronousMessage-Response.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="PARTICIPATION_REQUEST_CONTAINER_UNENCRYPTED">
        <xs:annotation>
          <xs:documentation>warning indicating that the clients participation request is not encrypted although the ITP defined encryption parameters.
It can only occur in a sendSynchronousMessage-Response.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="SIGNATURE_LEVEL_DOESNT_MATCH">
        <xs:annotation>
          <xs:documentation>warning indicating that the signature level of an attached document to a withdrawal message does not match the informations from ITT/ITP message.
It may only occur within sendSynchronousMessage-Responses.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="SUBMISSION_AFTER_DEADLINE">
        <xs:annotation>
          <xs:documentation>this warning occurs in the special case of a belated submission of offers/participation requests when the platform decides to accept the submission even though the according deadline has passed (the procedure is in the corresponding evaluation phase).
It might only occur within getOSCITransferID- and sendSynchronousMessage-Responses.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="SUBSCRIPTION_PENDING">
        <xs:annotation>
          <xs:documentation>this warning indicates that the subscription request of an authenticated client has to be approved by the contracting authority. Thus the warning may only occur within a subscriptionResponse-Message.
In case the contracting authority approves the request, the client can synchronize messages within the given procedure after the approval (he wont get another notify). In case the contracting authority denies the request, the client may never synchronize messages in this given procedure. The client will be notified out of band (e.g. via mail) by the contracting authority.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
    </xs:restriction>
</xs:simpleType>
</xs:element>

element Code.WarningCodeType/name

diagram

type

xs:normalizedString

properties

minOcc	0
maxOcc	1
content	simple
form	unqualified

annotation

documentation

Dokumentation aus XOEV-Bibliothek:

documentation

Mit diesem optionalen XML-Element kann die Beschreibung des Codes, wie in der jeweiligen Beschreibungsspalte der Codeliste vorgegeben, übermittelt werden.

source

complexType AttachmentMIMEType

diagram
namespace	http://xvergabe.org/datatypes/xsd/4/mtom
children	xvergabe-mtom:attachmentMTOM
source	<xs:complexType name="AttachmentMIMEType"> <xs:sequence> <xs:element name="attachmentMTOM" type="xs:base64Binary" minOccurs="1" maxOccurs="1" xmime:expectedContentTypes="application/octet-stream"/> </xs:sequence> </xs:complexType>

element AttachmentMIMEType/attachmentMTOM

diagram

namespace

http://xvergabe.org/datatypes/xsd/4/mtom

type

xs:base64Binary

properties

content

simple

source

<xs:element name="attachmentMTOM" type="xs:base64Binary" minOccurs="1" maxOccurs="1" xmime:expectedContentTypes="application/octet-stream"/>

complexType Code

diagram

namespace

http://xoev.de/schemata/code/1_0

children

attributes

Name

Type

Use

Default

Fixed

Annotation

listURI

xs:anyURI

optional

documentation