<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xvergabe-docs="http://xvergabe.org/documents/xsd/4" xmlns:xvergabe-cl="http://xvergabe.org/codelists/xsd/4" xmlns:xvergabe-if="http://xvergabe.org/interface/xsd/4" targetNamespace="http://xvergabe.org/documents/xsd/4" version="4.0" elementFormDefault="qualified" attributeFormDefault="unqualified">
  <xs:import schemaLocation="./xvergabe-codelists.xsd" namespace="http://xvergabe.org/codelists/xsd/4" />
  <xs:import schemaLocation="./xvergabe-codelists.xsd" namespace="http://xvergabe.org/codelists/xsd/4" />
  <xs:import schemaLocation="./xvergabe-datatypes.xsd" namespace="http://xvergabe.org/interface/xsd/4" />
  <xs:import schemaLocation="./xvergabe-datatypes.xsd" namespace="http://xvergabe.org/interface/xsd/4" />
  <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-if: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-if: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>
  <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-if: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" minOccurs="0" type="xvergabe-if:String.255">
        <xs:annotation>
          <xs:documentation>Categoryname of the document given/used by the contracting authority.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="categorySortIndex" minOccurs="0" type="xs:nonNegativeInteger">
        <xs:annotation>
          <xs:documentation>Index used for sorting documents within a category.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="displayName" type="xvergabe-if: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" minOccurs="0" type="xs:anyURI">
        <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" default="false" type="xs:boolean">
        <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).</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="mustBeSigned" type="xs:boolean">
        <xs:annotation>
          <xs:documentation>indicator whether the document (either required or to-be-returned-provided) SHALL be signed by the economic operator. 
SubmissionDetailsElectronical/applyContainerSignature overrides this element, meaning: when applyContainerSignature is true, no individual files SHALL be signed within the container.</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>
  <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>
  <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-if:ExistingObjectReference">
        <xs:sequence>
          <xs:element name="dateOfPublication" type="xvergabe-if:DateTimeTZ">
            <xs:annotation>
              <xs:documentation>timestamp at which a document has been made available</xs:documentation>
            </xs:annotation>
          </xs:element>
          <xs:element name="mustBeReturned" default="true" type="xs:boolean">
            <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" minOccurs="0" type="xvergabe-docs:TransformationDetails">
            <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>
  <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-if: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-if: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>
  <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-if: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" minOccurs="0" type="xs:nonNegativeInteger">
        <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>
  <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-if:String.255">
        <xs:annotation>
          <xs:documentation>The name of the file within the archive.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="documentID" minOccurs="0" maxOccurs="unbounded" type="xvergabe-if:GUID">
        <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>
  <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-if:String.255">
        <xs:annotation>
          <xs:documentation>The subject of the inquiry.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="inquiryBody" type="xs:string">
        <xs:annotation>
          <xs:appinfo>
            <implementationHint>This element MUST wrap Information according to xvg-if:FormattedText within a CDATA-Section!</implementationHint>
          </xs:appinfo>
          <xs:documentation>The actual content of the inquiry.
The actual type within this element MUST be xvg-if:FormattedText wrapped in a CDATA section!</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="documentReference" minOccurs="0" maxOccurs="unbounded" type="xvergabe-if:ExistingObjectReference">
        <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" minOccurs="0" maxOccurs="unbounded" type="xvergabe-if:GUID">
        <xs:annotation>
          <xs:documentation>optional References to lot(s) the inquiry is about.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
  <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="signatureDetails" minOccurs="0" type="xvergabe-if:XMLSignature">
        <xs:annotation>
          <xs:documentation>Signature of the inquiry document.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <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>
  <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" maxOccurs="unbounded" type="xvergabe-docs:DocumentsPackageContent">
        <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>
  <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" minOccurs="0" maxOccurs="unbounded" type="xvergabe-if:GUID">
        <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" minOccurs="0" type="xs:positiveInteger">
        <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" maxOccurs="unbounded" type="xvergabe-docs:DocumentsPackageContent" />
    </xs:sequence>
  </xs:complexType>
  <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-if:GUID">
        <xs:annotation>
          <xs:documentation>Unique identifier of the lot.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="lotName" minOccurs="0" type="xvergabe-if:String.1024">
        <xs:annotation>
          <xs:documentation>Name of the lot.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="lotNumber" minOccurs="0" type="xvergabe-if:String.255">
        <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" minOccurs="0" type="xvergabe-cl:Code.StatusType">
        <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" minOccurs="0" maxOccurs="unbounded" type="xvergabe-docs:TimeLimitType">
        <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" minOccurs="0" type="xs:positiveInteger">
        <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>
  <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" minOccurs="0" maxOccurs="unbounded" type="xvergabe-docs:FileAssociationType">
        <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>
  <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" default="true" type="xs:boolean">
            <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" minOccurs="0" maxOccurs="unbounded" type="xvergabe-if:GUID">
            <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>
  <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.</xs:documentation>
    </xs:annotation>
    <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" minOccurs="0" type="xvergabe-if:ExistingObjectReference">
        <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-if: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:complexType>
  <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-if: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>
  <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-if: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" minOccurs="0" type="xvergabe-if:GUID">
        <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>
  <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.</xs:documentation>
    </xs:annotation>
    <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" minOccurs="0" type="xvergabe-if:ExistingObjectReference" />
      <xs:element name="platformSpecificReceiptReport" type="xvergabe-if: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:complexType>
  <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="participationProcessingDetails" type="xvergabe-docs:ParticipationProcessingDetails">
        <xs:annotation>
          <xs:documentation>Contains processing information about the participation request for the server.</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>
  <xs:complexType name="ParticipationProcessingDetails">
    <xs:annotation>
      <xs:documentation>Contains information about the processing of a participation request that may be viewed before the actual opening of the participation request. This information is NOT encrypted and can be used by the server for processing the participation request correctly.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="accordingITPMsgID" type="xvergabe-if: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="participationTitle" type="xvergabe-if:String.255">
        <xs:annotation>
          <xs:documentation>Title of the participation request defined by the bidder or the bidder client.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="appliedSignatureLevel" type="xvergabe-cl:Code.SignatureLevelType">
        <xs:annotation>
          <xs:documentation>The signature level used for the signature of the participation request.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="participationSendDateTime" type="xvergabe-if:DateTimeTZ">
        <xs:annotation>
          <xs:documentation>The date and time the participation request was submitted.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
  <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" minOccurs="0" type="xvergabe-docs:ParticipationSubmissionDetailsPostal">
        <xs:annotation>
          <xs:documentation>Information about postal submission if applicable.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="electronicalSubmission" minOccurs="0" type="xvergabe-docs:ParticipationSubmissionDetailsElectronical">
        <xs:annotation>
          <xs:documentation>Information about electronical submission if applicable.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
  <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="minimumSignatureLevel" type="xvergabe-cl:Code.SignatureLevelType">
        <xs:annotation>
          <xs:documentation>The expected minimum level of signature certificates with which participation documents 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 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="applyContainerSignature" default="false" type="xs:boolean">
        <xs:annotation>
          <xs:documentation>when set to true the economic operator MAY NOT sign individual files within the participation container but only the ParticipationContent.xml file therein using PKCS#7 Enveloping Signature. 
This also means that the mustBeSigned attribute within the DocumentPackageContent (within participationdocument) MAY NOT be set within the ITP.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="hybridEncryptionExpected" type="xs:boolean">
        <xs:annotation>
          <xs:documentation>indicator whether the participationRequest has to be encrypted in a hybrid way, meaning the participation req. itself MUST be encrypted with a symmetric key (generated by the client) and this key MUST then be encrypted asymmetrically with the public key supplied within the ITP.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="encryptionKey" maxOccurs="unbounded" type="xvergabe-docs:EncryptionKeyDetails">
        <xs:annotation>
          <xs:documentation>the encryptionKey(s) used to encrypt the participationRequest</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="osciSubmission" minOccurs="0" type="xvergabe-docs:TenderSubmissionDetailsOSCI">
        <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>
  <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" minOccurs="0" type="xs:nonNegativeInteger">
        <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>
  <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-if: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-if: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-if: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>
  <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:complexContent>
      <xs:extension base="xvergabe-docs:ParticipationProcessingDetails">
        <xs:sequence>
          <xs:element name="participationMessageID" type="xvergabe-if: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-if: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-if: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:extension>
    </xs:complexContent>
  </xs:complexType>
  <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-if: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-if: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>
  <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-if: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">
          <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" minOccurs="0" type="xvergabe-if:String.4096">
        <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>
  <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>
  <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-if:GUID">
        <xs:annotation>
          <xs:documentation>The unique identifier of the tendering procedure.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="tenderingSubject" type="xvergabe-if:String.4096">
        <xs:annotation>
          <xs:documentation>The actual subject of the tendering procedure.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="contractingAuthorityName" minOccurs="0" type="xvergabe-if:String.1024">
        <xs:annotation>
          <xs:documentation>Name of the contracting authority that issued the tendering procedure.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="referenceNumber" minOccurs="0" type="xvergabe-if:String.255">
        <xs:annotation>
          <xs:documentation>The reference number of the tendering procedure.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="contractType" minOccurs="0" type="xvergabe-cl:Code.ContractType">
        <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" minOccurs="0" type="xs:anyURI">
        <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" minOccurs="0" maxOccurs="unbounded" type="xvergabe-docs:LotOverview">
        <xs:annotation>
          <xs:documentation>Optional lotinformations for lots within the procedure.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="procedureWideStatusAndTimeLimits" minOccurs="0" type="xvergabe-docs: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:element>
    </xs:sequence>
  </xs:complexType>
  <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" minOccurs="0" type="xvergabe-docs:platformInformationDetails">
        <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>
  <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" minOccurs="0" type="xvergabe-docs:TenderSubmissionDetailsPostal" />
      <xs:element name="electronicalSubmission" minOccurs="0" type="xvergabe-docs:TenderSubmissionDetailsElectronical">
        <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>
  <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="minimumSignatureLevel" type="xvergabe-cl:Code.SignatureLevelType">
        <xs:annotation>
          <xs:documentation>The expected minimum level of signature certificates with which offer documents 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 offer 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="applyContainerSignature" default="false" type="xs:boolean">
        <xs:annotation>
          <xs:documentation>when set to true the economic operator MAY NOT sign individual files within the offer container but only the OfferContent.xml file therein using PKCS#7 Enveloping Signature. 
This also means that the mustBeSigned attribute within the DocumentPackageContent (within tenderdocument) MAY NOT be set within the ITT.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="hybridEncryptionExpected" type="xs:boolean">
        <xs:annotation>
          <xs:documentation>indicator whether the tender has to be encrypted in a hybrid way, meaning the tender itself MUST be encrypted with a symmetric key (generated by the client) and this key MUST then be encrypted asymmetrically with the public key supplied within the ITT.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="encryptionKey" maxOccurs="unbounded" type="xvergabe-docs:EncryptionKeyDetails">
        <xs:annotation>
          <xs:documentation>the encryptionKey(s) used to encrypt the offer.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="osciSubmission" minOccurs="0" type="xvergabe-docs:TenderSubmissionDetailsOSCI">
        <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>
  <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-if: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-if: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" default="true" type="xs:boolean">
        <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" default="true" type="xs:boolean">
        <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" minOccurs="0" type="xs:anyURI">
        <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>
  <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" minOccurs="0" type="xs:nonNegativeInteger">
        <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>
  <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-if:DateTimeTZ">
        <xs:annotation>
          <xs:documentation>The date/timestamp of the time limit.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
  <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" minOccurs="0" type="xvergabe-if:String.255">
        <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" minOccurs="0" type="xvergabe-if:String.255">
        <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" minOccurs="0" type="xvergabe-if:String.255">
        <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" minOccurs="0" type="xs:anyURI">
        <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>
  <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>
  <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.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="processedWithdrawalDetails" type="xvergabe-docs:ProcessedWithdrawalDetails" />
      <xs:element name="platformSpecificReceipt" minOccurs="0" type="xvergabe-if:ExistingObjectReference" />
      <xs:element name="platformSpecificReceiptReport" type="xvergabe-if: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:complexType>
  <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-if: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" minOccurs="0" type="xvergabe-if:String.4096">
        <xs:annotation>
          <xs:documentation>The reasons for the withdrawal.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="withdrawalDateTime" type="xvergabe-if:DateTimeTZ">
        <xs:annotation>
          <xs:documentation>The date and time of the withdrawal.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
  <xs:complexType name="platformInformationDetails">
    <xs:annotation>
      <xs:documentation>Information about the platform (server).</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="uploadLimit" minOccurs="0" maxOccurs="unbounded" type="xvergabe-docs:UploadLimit">
        <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>
  <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" maxOccurs="unbounded" type="xvergabe-docs:TimeLimitType">
        <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" minOccurs="0" type="xs:positiveInteger">
        <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>
  <xs:element name="OfferContent">
    <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 the PRIMARY offer container (as part of its zip file) to provide additional information for processing software.
The offercontent.xml file MAY NOT be part of the SECONDARY offer container. Thus the fileassociation within the manifest MUST be given over the complete set of offer 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:OfferContentType" />
      </xs:complexContent>
    </xs:complexType>
  </xs:element>
  <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>
  <xs:element name="documents.Inquiry">
    <xs:annotation>
      <xs:documentation>Root element of an Inquiry document.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
      <xs:complexContent>
        <xs:extension base="xvergabe-docs:InquiryDocumentType" />
      </xs:complexContent>
    </xs:complexType>
  </xs:element>
  <xs:element name="documents.InvitationToParticipation">
    <xs:annotation>
      <xs:documentation>Root element of an InvitationToParticipationDocument.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
      <xs:complexContent>
        <xs:extension base="xvergabe-docs:InvitationToParticipationDocumentType" />
      </xs:complexContent>
    </xs:complexType>
  </xs:element>
  <xs:element name="documents.InvitationToTender">
    <xs:annotation>
      <xs:documentation>Root element of an InvitationToTender document.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
      <xs:complexContent>
        <xs:extension base="xvergabe-docs:InvitationToTenderDocumentType" />
      </xs:complexContent>
    </xs:complexType>
  </xs:element>
  <xs:element name="documents.Offer">
    <xs:annotation>
      <xs:documentation>Root element of an Offer document.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
      <xs:complexContent>
        <xs:extension base="xvergabe-docs:OfferDocumentType" />
      </xs:complexContent>
    </xs:complexType>
  </xs:element>
  <xs:element name="documents.OfferDeliveryReceipt">
    <xs:annotation>
      <xs:documentation>Root element of an OfferDeliveryReceipt document.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
      <xs:complexContent>
        <xs:extension base="xvergabe-docs:OfferDeliveryReceiptDocumentType" />
      </xs:complexContent>
    </xs:complexType>
  </xs:element>
  <xs:element name="documents.OfferWithdrawal">
    <xs:annotation>
      <xs:documentation>Root element of an OfferWithdrawal document.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
      <xs:complexContent>
        <xs:extension base="xvergabe-docs:WithdrawalDocumentType" />
      </xs:complexContent>
    </xs:complexType>
  </xs:element>
  <xs:element name="documents.OfferWithdrawalDeliveryReceipt">
    <xs:annotation>
      <xs:documentation>Root element of an OfferWithdrawalDeliveryReceipt.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
      <xs:complexContent>
        <xs:extension base="xvergabe-docs:WithdrawalDeliveryReceiptDocumentType" />
      </xs:complexContent>
    </xs:complexType>
  </xs:element>
  <xs:element name="documents.Participation">
    <xs:annotation>
      <xs:documentation>root element of a participation request document.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
      <xs:complexContent>
        <xs:extension base="xvergabe-docs:ParticipationDocumentType" />
      </xs:complexContent>
    </xs:complexType>
  </xs:element>
  <xs:element name="documents.ParticipationDeliveryReceipt">
    <xs:annotation>
      <xs:documentation>Root element of an ParticipationDeliveryReceipt document.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
      <xs:complexContent>
        <xs:extension base="xvergabe-docs:ParticipationDeliveryReceiptDocumentType" />
      </xs:complexContent>
    </xs:complexType>
  </xs:element>
  <xs:element name="documents.ParticipationWithdrawal">
    <xs:annotation>
      <xs:documentation>Root element of a ParticipationWithdrawal document.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
      <xs:complexContent>
        <xs:extension base="xvergabe-docs:WithdrawalDocumentType" />
      </xs:complexContent>
    </xs:complexType>
  </xs:element>
  <xs:element name="documents.ParticipationWithdrawalDeliveryReceipt">
    <xs:annotation>
      <xs:documentation>Root element of a ParticipationWithdrawalDeliveryReceipt.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
      <xs:complexContent>
        <xs:extension base="xvergabe-docs:WithdrawalDeliveryReceiptDocumentType" />
      </xs:complexContent>
    </xs:complexType>
  </xs:element>
  <xs:element name="documents.Response">
    <xs:annotation>
      <xs:documentation>Root element of a Response document.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
      <xs:complexContent>
        <xs:extension base="xvergabe-docs:ResponseDocumentType" />
      </xs:complexContent>
    </xs:complexType>
  </xs:element>
  <xs:element name="documents.ResultNotice">
    <xs:annotation>
      <xs:documentation>Root element of a ResultNotice document.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
      <xs:complexContent>
        <xs:extension base="xvergabe-docs:ResultNoticeDocumentType" />
      </xs:complexContent>
    </xs:complexType>
  </xs:element>
  <xs:element name="documents.TenderMetaInformation">
    <xs:annotation>
      <xs:documentation>Root element of a TenderMetaInformation document.</xs:documentation>
    </xs:annotation>
    <xs:complexType>
      <xs:complexContent>
        <xs:extension base="xvergabe-docs:TenderMetaInformationDocumentType" />
      </xs:complexContent>
    </xs:complexType>
  </xs:element>
</xs:schema>

