Schema xvergabe-service.xsd

schema location:	..\xsd\xvergabe-service.xsd
attributeFormDefault:	unqualified
elementFormDefault:	qualified
targetNamespace:	http://xvergabe.org/xsd/client-interface/service/4

Elements	Complex types
msgGetDocumentRequest	AbstractResponse
msgGetDocumentResponse	MessageSelector
msgGetMessagesRequest	msgTypeGetDocumentRequest
msgGetMessagesResponse	msgTypeGetDocumentResponse
msgGetOSCITransferIDRequest	msgTypeGetMessagesRequest
msgGetOSCITransferIDResponse	msgTypeGetMessagesResponse
msgGetTenderIDsRequest	msgTypeGetOSCITransferIDRequest
msgGetTenderIDsResponse	msgTypeGetOSCITransferIDResponse
msgSendMessageRequest	msgTypeGetTenderIDsRequest
msgSendMessageResponse	msgTypeGetTenderIDsResponse
msgSendSynchronousMessageRequest	msgTypeSendMessageRequest
msgSendSynchronousMessageResponse	msgTypeSendMessageResponse
msgSubscriptionRequest	msgTypeSendSynchronousMessageRequest
msgSubscriptionResponse	msgTypeSendSynchronousMessageResponse
	msgTypeSubscriptionRequest
	msgTypeSubscriptionResponse

schema location:	..\xsd\xvergabe-documents.xsd
attributeFormDefault:	unqualified
elementFormDefault:	qualified
targetNamespace:	http://xvergabe.org/documents/xsd/4

Elements	Complex types
documents.Inquiry	ContentType
documents.InvitationToParticipation	DocumentsPackageContent
documents.InvitationToTender	DocumentsPackageContentDocument
documents.Offer	DocumentsPackageContentProvidedDocument
documents.OfferDeliveryReceipt	DocumentsPackageContentRequiredDocument
documents.OfferWithdrawal	EncryptionKeyDetails
documents.OfferWithdrawalDeliveryReceipt	FileAssociationType
documents.Participation	Inquiry
documents.ParticipationDeliveryReceipt	InquiryDocumentType
documents.ParticipationWithdrawal	InvitationToParticipationDocumentType
documents.ParticipationWithdrawalDeliveryReceipt	InvitationToTenderDocumentType
documents.Response	LotOverview
documents.ResultNotice	ManifestType
documents.TenderMetaInformation	OfferContentType
OfferContent	OfferDeliveryReceiptDocumentType
ParticipationContent	OfferDocumentType
	OfferObject
	ParticipationDeliveryReceiptDocumentType
	ParticipationDocumentType
	ParticipationProcessingDetails
	ParticipationSubmissionDetails
	ParticipationSubmissionDetailsElectronical
	ParticipationSubmissionDetailsPostal
	platformInformationDetails
	procedureWideStatusAndTimeLimits
	ProcessedOfferDetails
	ProcessedParticipationDetails
	ProcessedWithdrawalDetails
	ResponseDocumentType
	ResultNoticeDocumentType
	TenderMetaInformationDetails
	TenderMetaInformationDocumentType
	TenderSubmissionDetails
	TenderSubmissionDetailsElectronical
	TenderSubmissionDetailsOSCI
	TenderSubmissionDetailsPostal
	TimeLimitType
	TransformationDetails
	UploadLimit
	WithdrawalDeliveryReceiptDocumentType
	WithdrawalDocumentType

schema location:	..\xsd\xvergabe-datatypes.xsd
attributeFormDefault:	unqualified
elementFormDefault:	qualified
targetNamespace:	http://xvergabe.org/interface/xsd/4

Complex types	Simple types
ExistingObjectReference	DateTimeTZ
FormattedText	GUID
XMLSignature	String.0
	String.1024
	String.255
	String.4096

schema location:	..\xsd\xvergabe-messages.xsd
attributeFormDefault:	unqualified
elementFormDefault:	qualified
targetNamespace:	http://xvergabe.org/interface/xsd/4

Elements	Complex types
messages.Attachment	AbstractClientMessage
messages.ClientInquiry	AbstractServerMessage
messages.InvitationToParticipation	Attachment
messages.InvitationToTender	ClientInquiryMessageType
messages.Offer	CredentialItem
messages.OfferDeliveryReceipt	InvitationToParticipationMessageType
messages.OfferWithdrawal	InvitationToTenderMessageType
messages.OfferWithdrawalDeliveryReceipt	MessageHeader
messages.OSCITransferID	MessageInfo
messages.Participation	OfferDeliveryReceiptMessageType
messages.ParticipationDeliveryReceipt	OfferMessageType
messages.ParticipationWithdrawal	OfferWithdrawalDeliveryReceiptMessageType
messages.ParticipationWithdrawalDeliveryReceipt	OfferWithdrawalMessageType
messages.ResultNotice	OSCITransferIDRequestType
messages.ServerInquiry	ParticipationDeliveryReceiptMessageType
messages.TenderMetaInformation	ParticipationMessageType
	ParticipationWithdrawalDeliveryReceiptMessageType
	ParticipationWithdrawalMessageType
	ResultNoticeMessageType
	SenderInfo
	ServerInquiryMessageType
	TenderMetaInformationMessageType

schema location:	..\xsd\xvergabe-codelists.xsd
attributeFormDefault:	unqualified
elementFormDefault:	qualified
targetNamespace:	http://xvergabe.org/codelists/xsd/4

Complex types

Code.ContractType

Code.CredentialUsage

Code.EncryptionAlgorithm

Code.ErrorCodeType

Code.ProcedureType

Code.SignatureLevelType

Code.StatusType

Code.TimeLimitType

Code.UploadLimitType

Code.WarningCodeType

schema location:	..\ext\xhtml1-transitional-redefined-basictype.xsd
attributeFormDefault:	unqualified
elementFormDefault:	unqualified
targetNamespace:	http://xvergabe.org/client-interface/basic-xhtml-redefinition/4

Complex types

BasicXHTML

schema location:	http://xoev.de/schemata/code/1_0/xoev-code.xsd
attributeFormDefault:	unqualified
elementFormDefault:	qualified
targetNamespace:	http://xoev.de/schemata/code/1_0

Complex types

Code

schema location:	..\ext\xhtml1-transitional-redefined.xsd
attributeFormDefault:	unqualified
elementFormDefault:	unqualified
targetNamespace:	http://www.w3.org/1999/xhtml

Groups	Attr. groups
block (r)	attrs (r)
blocktext (r)	coreattrs (r)
fontstyle (r)	TextAlign (r)
fontstyle.basic (r)
inline (r)
lists (r)
misc (r)
misc.inline (r)
phrase (r)
phrase.basic (r)
special (r)
special.basic (r)

schema location:	http://www.w3.org/2002/08/xhtml/xhtml1-transitional.xsd
attributeFormDefault:
elementFormDefault:	qualified
targetNamespace:	http://www.w3.org/1999/xhtml

Elements	Groups	Complex types	Simple types	Attr. groups
a	block	a.content	CAlign	attrs
abbr	blocktext	button.content	Character	cellhalign
acronym	fontstyle	Flow	Charset	cellvalign
address	fontstyle.basic	form.content	Charsets	coreattrs
applet	fontstyle.extra	Inline	Color	events
area	head.misc	pre.content	ContentType	focus
b	heading		ContentTypes	i18n
base	inline		Coords	TextAlign
basefont	inline.forms		Datetime
bdo	lists		FrameTarget
big	misc		ImgAlign
blockquote	misc.inline		InputType
body	phrase		LAlign
br	phrase.basic		LanguageCode
button	phrase.extra		Length
caption	special		LinkTypes
center	special.basic		LIStyle
cite	special.extra		MediaDesc
code			MultiLength
col			Number
colgroup			OLStyle
dd			Pixels
del			Scope
dfn			Script
dir			Shape
div			StyleSheet
dl			tabindexNumber
dt			TAlign
em			Text
fieldset			TFrame
font			TRules
form			ULStyle
h1			URI
h2			UriList
h3
h4
h5
h6
head
hr
html
i
iframe
img
input
ins
isindex
kbd
label
legend
li
link
map
menu
meta
noframes
noscript
object
ol
optgroup
option
p
param
pre
q
s
samp
script
select
small
span
strike
strong
style
sub
sup
table
tbody
td
textarea
tfoot
th
thead
title
tr
tt
u
ul
var

schema location:	..\..\..\Program Files (x86)\Altova\Common2015\Schemas\schema\files\W3C_2001\xml.xsd
attributeFormDefault:
elementFormDefault:
targetNamespace:	http://www.w3.org/XML/1998/namespace

Attributes	Attr. groups
base	specialAttrs
id
lang
space

element msgGetDocumentRequest

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
type	extension of xvergabe-if-svc:msgTypeGetDocumentRequest
properties	content  complex
children	xvergabe-if-svc:ID
annotation	documentation Root element for a request to the operation getDocument.
source	<xs:element name="msgGetDocumentRequest">   <xs:annotation>     <xs:documentation>Root element for a request to the operation getDocument.</xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:complexContent>       <xs:extension base="xvergabe-if-svc:msgTypeGetDocumentRequest"/>     </xs:complexContent>   </xs:complexType> </xs:element>

element msgGetDocumentResponse

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
type	extension of xvergabe-if-svc:msgTypeGetDocumentResponse
properties	content  complex
children	xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl xvergabe-if-svc:document
annotation	documentation Root element for a response of the operation getDocument.
source	<xs:element name="msgGetDocumentResponse">   <xs:annotation>     <xs:documentation>Root element for a response of the operation getDocument.</xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:complexContent>       <xs:extension base="xvergabe-if-svc:msgTypeGetDocumentResponse"/>     </xs:complexContent>   </xs:complexType> </xs:element>

element msgGetMessagesRequest

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
type	extension of xvergabe-if-svc:msgTypeGetMessagesRequest
properties	content  complex
children	xvergabe-if-svc:parameter
annotation	documentation Root element for a request to the operation getMessages.
source	<xs:element name="msgGetMessagesRequest">   <xs:annotation>     <xs:documentation>Root element for a request to the operation getMessages.</xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:complexContent>       <xs:extension base="xvergabe-if-svc:msgTypeGetMessagesRequest"/>     </xs:complexContent>   </xs:complexType> </xs:element>

element msgGetMessagesResponse

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
type	extension of xvergabe-if-svc:msgTypeGetMessagesResponse
properties	content  complex
children	xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl xvergabe-if-svc:messageBundle
annotation	documentation Root element for a response of the operation getMessages.
source	<xs:element name="msgGetMessagesResponse">   <xs:annotation>     <xs:documentation>Root element for a response of the operation getMessages.</xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:complexContent>       <xs:extension base="xvergabe-if-svc:msgTypeGetMessagesResponse"/>     </xs:complexContent>   </xs:complexType> </xs:element>

element msgGetOSCITransferIDRequest

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
type	extension of xvergabe-if-svc:msgTypeGetOSCITransferIDRequest
properties	content  complex
children	xvergabe-if:messageHeader xvergabe-if:offer xvergabe-if:participationRequest xvergabe-if:withdrawal
annotation	documentation Root element for a request to the operation getOSCITransferID
source	<xs:element name="msgGetOSCITransferIDRequest">   <xs:annotation>     <xs:documentation>Root element for a request to the operation getOSCITransferID</xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:complexContent>       <xs:extension base="xvergabe-if-svc:msgTypeGetOSCITransferIDRequest"/>     </xs:complexContent>   </xs:complexType> </xs:element>

element msgGetOSCITransferIDResponse

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
type	extension of xvergabe-if-svc:msgTypeGetOSCITransferIDResponse
properties	content  complex
children	xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl xvergabe-if-svc:OSCITransferID
annotation	documentation Root element for a response to the operation getOSCITransferID
source	<xs:element name="msgGetOSCITransferIDResponse">   <xs:annotation>     <xs:documentation>Root element for a response to the operation getOSCITransferID</xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:complexContent>       <xs:extension base="xvergabe-if-svc:msgTypeGetOSCITransferIDResponse"/>     </xs:complexContent>   </xs:complexType> </xs:element>

element msgGetTenderIDsRequest

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
type	extension of xvergabe-if-svc:msgTypeGetTenderIDsRequest
properties	content  complex
annotation	documentation Root element for a request to the operation getTenderIDs.
source	<xs:element name="msgGetTenderIDsRequest">   <xs:annotation>     <xs:documentation>Root element for a request to the operation getTenderIDs.</xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:complexContent>       <xs:extension base="xvergabe-if-svc:msgTypeGetTenderIDsRequest"/>     </xs:complexContent>   </xs:complexType> </xs:element>

element msgGetTenderIDsResponse

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
type	extension of xvergabe-if-svc:msgTypeGetTenderIDsResponse
properties	content  complex
children	xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl xvergabe-if-svc:procedure
annotation	documentation Root element for a response of the operation getTenderIDs.
source	<xs:element name="msgGetTenderIDsResponse">   <xs:annotation>     <xs:documentation>Root element for a response of the operation getTenderIDs.</xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:complexContent>       <xs:extension base="xvergabe-if-svc:msgTypeGetTenderIDsResponse"/>     </xs:complexContent>   </xs:complexType> </xs:element>

element msgSendMessageRequest

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
type	extension of xvergabe-if-svc:msgTypeSendMessageRequest
properties	content  complex
children	xvergabe-if-svc:inquiryMessage
annotation	documentation Root element for a request to the operation sendMessage.
source	<xs:element name="msgSendMessageRequest">   <xs:annotation>     <xs:documentation>Root element for a request to the operation sendMessage.</xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:complexContent>       <xs:extension base="xvergabe-if-svc:msgTypeSendMessageRequest"/>     </xs:complexContent>   </xs:complexType> </xs:element>

element msgSendMessageResponse

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
type	extension of xvergabe-if-svc:msgTypeSendMessageResponse
properties	content  complex
children	xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl
annotation	documentation Root element for a response of the operation sendMessage.
source	<xs:element name="msgSendMessageResponse">   <xs:annotation>     <xs:documentation>Root element for a response of the operation sendMessage.</xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:complexContent>       <xs:extension base="xvergabe-if-svc:msgTypeSendMessageResponse"/>     </xs:complexContent>   </xs:complexType> </xs:element>

element msgSendSynchronousMessageRequest

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
type	extension of xvergabe-if-svc:msgTypeSendSynchronousMessageRequest
properties	content  complex
children	xvergabe-if-svc:offerMessage xvergabe-if-svc:participationMessage xvergabe-if-svc:offerWithdrawalMessage xvergabe-if-svc:participationWithdrawalMessage
annotation	documentation Root element for a request to the operation sendSynchronousMessage.
source	<xs:element name="msgSendSynchronousMessageRequest">   <xs:annotation>     <xs:documentation>Root element for a request to the operation sendSynchronousMessage.</xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:complexContent>       <xs:extension base="xvergabe-if-svc:msgTypeSendSynchronousMessageRequest"/>     </xs:complexContent>   </xs:complexType> </xs:element>

element msgSendSynchronousMessageResponse

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
type	extension of xvergabe-if-svc:msgTypeSendSynchronousMessageResponse
properties	content  complex
children	xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl xvergabe-if-svc:offerDeliveryReceiptMessage xvergabe-if-svc:participationDeliveryReceiptMessage xvergabe-if-svc:offerWithdrawalDeliveryReceiptMessage xvergabe-if-svc:participationWithdrawalDeliveryReceiptMessage
annotation	documentation Root element for a response of the operation sendSynchronousMessage.
source	<xs:element name="msgSendSynchronousMessageResponse">   <xs:annotation>     <xs:documentation>Root element for a response of the operation sendSynchronousMessage.</xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:complexContent>       <xs:extension base="xvergabe-if-svc:msgTypeSendSynchronousMessageResponse"/>     </xs:complexContent>   </xs:complexType> </xs:element>

element msgSubscriptionRequest

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
type	extension of xvergabe-if-svc:msgTypeSubscriptionRequest
properties	content  complex
children	xvergabe-if-svc:tenderID xvergabe-if-svc:platformSpecificTenderID
annotation	documentation Root element for a request to the operation subscribe. Subsrciption can occur by specifying the XVergabe ID or a (potentially more user friendly) platform specific ID of the tendering procedure.
source	<xs:element name="msgSubscriptionRequest">   <xs:annotation>     <xs:documentation>Root element for a request to the operation subscribe. Subsrciption can occur by specifying the XVergabe ID or a (potentially more user friendly) platform specific ID of the tendering procedure.</xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:complexContent>       <xs:extension base="xvergabe-if-svc:msgTypeSubscriptionRequest"/>     </xs:complexContent>   </xs:complexType> </xs:element>

element msgSubscriptionResponse

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
type	extension of xvergabe-if-svc:msgTypeSubscriptionResponse
properties	content  complex
children	xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl xvergabe-if-svc:procedure
annotation	documentation Root element for a response of the operation subscribe.
source	<xs:element name="msgSubscriptionResponse">   <xs:annotation>     <xs:documentation>Root element for a response of the operation subscribe.</xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:complexContent>       <xs:extension base="xvergabe-if-svc:msgTypeSubscriptionResponse"/>     </xs:complexContent>   </xs:complexType> </xs:element>

complexType AbstractResponse

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
properties	abstract  true
children	xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl
annotation	documentation Abstract response type providing general information about the status of the response. All responses in this web service extend from this type.
source	<xs:complexType name="AbstractResponse" abstract="true">   <xs:annotation>     <xs:documentation>Abstract response type providing general information about the status of the response. All responses in this web service extend from this type.</xs:documentation>   </xs:annotation>   <xs:sequence>     <xs:element name="responseStatus" type="xvergabe-docs:ResponseDocumentType">       <xs:annotation>         <xs:documentation>ResponseDocument containing information about the status of the response (error, warning, etc.).</xs:documentation>       </xs:annotation>     </xs:element>     <xs:element name="redirectUrl" type="xs:anyURI" minOccurs="0">       <xs:annotation>         <xs:documentation>If the server does not support direct subscription to a tendering procedure the server MAY provide a URL in this field that points to a web application that provides this functionality or displays a text explaining how to subscribe.</xs:documentation>       </xs:annotation>     </xs:element>   </xs:sequence> </xs:complexType>

element AbstractResponse/responseStatus

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
type	xvergabe-docs:ResponseDocumentType
properties	content  complex
children	xvergabe-docs:OK xvergabe-docs:WARNING xvergabe-docs:ERROR xvergabe-docs:responseInformation
annotation	documentation ResponseDocument containing information about the status of the response (error, warning, etc.).
source	<xs:element name="responseStatus" type="xvergabe-docs:ResponseDocumentType">   <xs:annotation>     <xs:documentation>ResponseDocument containing information about the status of the response (error, warning, etc.).</xs:documentation>   </xs:annotation> </xs:element>

element AbstractResponse/redirectUrl

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
type	xs:anyURI
properties	minOcc  0 maxOcc  1 content  simple
annotation	documentation If the server does not support direct subscription to a tendering procedure the server MAY provide a URL in this field that points to a web application that provides this functionality or displays a text explaining how to subscribe.
source	<xs:element name="redirectUrl" type="xs:anyURI" minOccurs="0">   <xs:annotation>     <xs:documentation>If the server does not support direct subscription to a tendering procedure the server MAY provide a URL in this field that points to a web application that provides this functionality or displays a text explaining how to subscribe.</xs:documentation>   </xs:annotation> </xs:element>

complexType MessageSelector

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
children	xvergabe-if-svc:messageID xvergabe-if-svc:tenderingID xvergabe-if-svc:lastKnownMessageID
annotation	documentation Parameters that define constraints for the selection of a set of messages.
source	<xs:complexType name="MessageSelector">   <xs:annotation>     <xs:documentation>Parameters that define constraints for the selection of a set of messages.</xs:documentation>   </xs:annotation>   <xs:choice>     <xs:element name="messageID" type="xvergabe-if: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>     <xs:sequence>       <xs:element name="tenderingID" type="xvergabe-if: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>       <xs:element name="lastKnownMessageID" type="xvergabe-if: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>     </xs:sequence>   </xs:choice> </xs:complexType>

element MessageSelector/messageID

diagram
namespace	http://xvergabe.org/xsd/client-interface/service/4
type	xvergabe-if:GUID
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-if: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	xvergabe-if:GUID
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-if: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	xvergabe-if:GUID
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-if: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-if: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	xvergabe-if:GUID
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-if: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	extension of xvergabe-if-svc:AbstractResponse
properties	base  xvergabe-if-svc:AbstractResponse
children	xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl xvergabe-if-svc:document
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:Attachment
properties	minOcc  0 maxOcc  1 content  complex
children	xvergabe-if:attachmentID xvergabe-if:filename xvergabe-if:description xvergabe-if:attachmentData xvergabe-if:signature
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	extension of xvergabe-if-svc:AbstractResponse
properties	base  xvergabe-if-svc:AbstractResponse
children	xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl xvergabe-if-svc:messageBundle
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	extension of xvergabe-if-svc:AbstractResponse
properties	base  xvergabe-if-svc:AbstractResponse
children	xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl xvergabe-if-svc:OSCITransferID
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-if: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	xvergabe-if:GUID
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-if: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	extension of xvergabe-if-svc:AbstractResponse
properties	base  xvergabe-if-svc:AbstractResponse
children	xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl xvergabe-if-svc:procedure
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-if:GUID">                 <xs:annotation>                   <xs:documentation>The unique ID of the tendering procedure.</xs:documentation>                 </xs:annotation>               </xs:element>               <xs:element name="tenderTitle" type="xvergabe-if:String.1024">                 <xs:annotation>                   <xs:documentation>The title of the tendering procedure.</xs:documentation>                 </xs:annotation>               </xs:element>               <xs:element name="lastMessageID" type="xvergabe-if: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-if:GUID">         <xs:annotation>           <xs:documentation>The unique ID of the tendering procedure.</xs:documentation>         </xs:annotation>       </xs:element>       <xs:element name="tenderTitle" type="xvergabe-if:String.1024">         <xs:annotation>           <xs:documentation>The title of the tendering procedure.</xs:documentation>         </xs:annotation>       </xs:element>       <xs:element name="lastMessageID" type="xvergabe-if: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	xvergabe-if:GUID
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-if: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	xvergabe-if:String.1024
properties	content  simple
annotation	documentation The title of the tendering procedure.
source	<xs:element name="tenderTitle" type="xvergabe-if: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:GUID
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-if: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	xvergabe-if-svc:inquiryMessage
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	extension of xvergabe-if-svc:AbstractResponse
properties	base  xvergabe-if-svc:AbstractResponse
children	xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl
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	extension of xvergabe-if-svc:AbstractResponse
properties	base  xvergabe-if-svc:AbstractResponse
children	xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl xvergabe-if-svc:offerDeliveryReceiptMessage xvergabe-if-svc:participationDeliveryReceiptMessage xvergabe-if-svc:offerWithdrawalDeliveryReceiptMessage xvergabe-if-svc:participationWithdrawalDeliveryReceiptMessage
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">           <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">           <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">           <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">           <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	xvergabe-if:OfferDeliveryReceiptMessageType
properties	content  complex
children	xvergabe-if:messageHeader xvergabe-if:document
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">   <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	xvergabe-if:ParticipationDeliveryReceiptMessageType
properties	content  complex
children	xvergabe-if:messageHeader xvergabe-if:document
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">   <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	xvergabe-if:OfferWithdrawalDeliveryReceiptMessageType
properties	content  complex
children	xvergabe-if:messageHeader xvergabe-if:document
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">   <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	xvergabe-if:ParticipationWithdrawalDeliveryReceiptMessageType
properties	content  complex
children	xvergabe-if:messageHeader xvergabe-if:document
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">   <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	xvergabe-if-svc:tenderID xvergabe-if-svc:platformSpecificTenderID
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-if: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-if: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	xvergabe-if:GUID
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-if: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	xvergabe-if:String.4096
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-if: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	extension of xvergabe-if-svc:AbstractResponse
properties	base  xvergabe-if-svc:AbstractResponse
children	xvergabe-if-svc:responseStatus xvergabe-if-svc:redirectUrl xvergabe-if-svc:procedure
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">           <xs:annotation>             <xs:documentation>List containing information about the tendering procedure the client has subscribed to.</xs:documentation>           </xs:annotation>           <xs:complexType>             <xs:sequence>               <xs:element name="tenderID" type="xvergabe-if:GUID">                 <xs:annotation>                   <xs:documentation>The unique ID of the tendering procedure.</xs:documentation>                 </xs:annotation>               </xs:element>               <xs:element name="tenderTitle" type="xvergabe-if:String.1024">                 <xs:annotation>                   <xs:documentation>The title of the tendering procedure.</xs:documentation>                 </xs:annotation>               </xs:element>               <xs:element name="lastMessageID" type="xvergabe-if: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  1 content  complex
children	xvergabe-if-svc:tenderID xvergabe-if-svc:tenderTitle xvergabe-if-svc:lastMessageID
annotation	documentation List containing information about the tendering procedure the client has subscribed to.
source	<xs:element name="procedure" minOccurs="0">   <xs:annotation>     <xs:documentation>List containing information about the tendering procedure the client has subscribed to.</xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:sequence>       <xs:element name="tenderID" type="xvergabe-if:GUID">         <xs:annotation>           <xs:documentation>The unique ID of the tendering procedure.</xs:documentation>         </xs:annotation>       </xs:element>       <xs:element name="tenderTitle" type="xvergabe-if:String.1024">         <xs:annotation>           <xs:documentation>The title of the tendering procedure.</xs:documentation>         </xs:annotation>       </xs:element>       <xs:element name="lastMessageID" type="xvergabe-if: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	xvergabe-if:GUID
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-if: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	xvergabe-if:String.1024
properties	content  simple
annotation	documentation The title of the tendering procedure.
source	<xs:element name="tenderTitle" type="xvergabe-if: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-if:GUID
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-if: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>

element documents.Inquiry

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	extension of xvergabe-docs:InquiryDocumentType
properties	content  complex
children	xvergabe-docs:signatureDetails xvergabe-docs:inquiry
annotation	documentation Root element of an Inquiry document.
source	<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>

element documents.InvitationToParticipation

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	extension of xvergabe-docs:InvitationToParticipationDocumentType
properties	content  complex
children	xvergabe-docs:submissionDetails xvergabe-docs:participationDocument
annotation	documentation Root element of an InvitationToParticipationDocument.
source	<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>

element documents.InvitationToTender

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	extension of xvergabe-docs:InvitationToTenderDocumentType
properties	content  complex
children	xvergabe-docs:lot xvergabe-docs:negotiationRound xvergabe-docs:tenderSubmissionDetails xvergabe-docs:tenderDocument
annotation	documentation Root element of an InvitationToTender document.
source	<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>

element documents.Offer

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	extension of xvergabe-docs:OfferDocumentType
properties	content  complex
children	xvergabe-docs:accordingITTMsgID xvergabe-docs:offerObject
annotation	documentation Root element of an Offer document.
source	<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>

element documents.OfferDeliveryReceipt

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	extension of xvergabe-docs:OfferDeliveryReceiptDocumentType
properties	content  complex
children	xvergabe-docs:processedOfferDetails xvergabe-docs:platformSpecificReceipt xvergabe-docs:platformSpecificReceiptReport
annotation	documentation Root element of an OfferDeliveryReceipt document.
source	<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>

element documents.OfferWithdrawal

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	extension of xvergabe-docs:WithdrawalDocumentType
properties	content  complex
children	xvergabe-docs:objectIDToWithdraw xvergabe-docs:withdrawalReason xvergabe-docs:withdrawalDateTime
annotation	documentation Root element of an OfferWithdrawal document.
source	<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>

element documents.OfferWithdrawalDeliveryReceipt

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	extension of xvergabe-docs:WithdrawalDeliveryReceiptDocumentType
properties	content  complex
children	xvergabe-docs:processedWithdrawalDetails xvergabe-docs:platformSpecificReceipt xvergabe-docs:platformSpecificReceiptReport
annotation	documentation Root element of an OfferWithdrawalDeliveryReceipt.
source	<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>

element documents.Participation

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	extension of xvergabe-docs:ParticipationDocumentType
properties	content  complex
children	xvergabe-docs:participationProcessingDetails xvergabe-docs:participationObject
annotation	documentation root element of a participation request document.
source	<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>

element documents.ParticipationDeliveryReceipt

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	extension of xvergabe-docs:ParticipationDeliveryReceiptDocumentType
properties	content  complex
children	xvergabe-docs:processedParticipationDetails xvergabe-docs:platformSpecificReceipt xvergabe-docs:platformSpecificReceiptReport
annotation	documentation Root element of an ParticipationDeliveryReceipt document.
source	<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>

element documents.ParticipationWithdrawal

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	extension of xvergabe-docs:WithdrawalDocumentType
properties	content  complex
children	xvergabe-docs:objectIDToWithdraw xvergabe-docs:withdrawalReason xvergabe-docs:withdrawalDateTime
annotation	documentation Root element of a ParticipationWithdrawal document.
source	<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>

element documents.ParticipationWithdrawalDeliveryReceipt

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	extension of xvergabe-docs:WithdrawalDeliveryReceiptDocumentType
properties	content  complex
children	xvergabe-docs:processedWithdrawalDetails xvergabe-docs:platformSpecificReceipt xvergabe-docs:platformSpecificReceiptReport
annotation	documentation Root element of a ParticipationWithdrawalDeliveryReceipt.
source	<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>

element documents.Response

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	extension of xvergabe-docs:ResponseDocumentType
properties	content  complex
children	xvergabe-docs:OK xvergabe-docs:WARNING xvergabe-docs:ERROR xvergabe-docs:responseInformation
annotation	documentation Root element of a Response document.
source	<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>

element documents.ResultNotice

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	extension of xvergabe-docs:ResultNoticeDocumentType
properties	content  complex
children	xvergabe-docs:signatureDetails xvergabe-docs:inquiry
annotation	documentation Root element of a ResultNotice document.
source	<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>

element documents.TenderMetaInformation

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	extension of xvergabe-docs:TenderMetaInformationDocumentType
properties	content  complex
children	xvergabe-docs:tenderMetaInformationDetails xvergabe-docs:platformInformationDetails
annotation	documentation Root element of a TenderMetaInformation document.
source	<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>

element OfferContent

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	extension of xvergabe-docs:OfferContentType
properties	content  complex
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 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.
source	<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>

element ParticipationContent

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	extension of xvergabe-docs:ContentType
properties	content  complex
children	xvergabe-docs:title xvergabe-docs:manifest xvergabe-docs:creationTime
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-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>

element ContentType/title

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:String.1024
properties	content  simple
annotation	documentation title of the offer/participation request given by the economic operator
source	<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>

element ContentType/manifest

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-docs:ManifestType
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-if:DateTimeTZ
properties	content  simple
facets	Kind  Value  Annotation pattern  ([0-9]{4})-(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]|(24:00:00))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-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>

complexType DocumentsPackageContent

diagram
namespace	http://xvergabe.org/documents/xsd/4
children	xvergabe-docs:documentID xvergabe-docs:category xvergabe-docs:categorySortIndex xvergabe-docs:displayName xvergabe-docs:processingApplicationURL xvergabe-docs:belongsToPrimaryContainer xvergabe-docs:mustBeSigned xvergabe-docs:document
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-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" type="xvergabe-if: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-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" 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="false">       <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>

element DocumentsPackageContent/documentID

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:GUID
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-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>

element DocumentsPackageContent/category

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:String.255
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-if: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	xvergabe-if:String.255
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-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>

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  false
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).
source	<xs:element name="belongsToPrimaryContainer" type="xs:boolean" default="false">   <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>

element DocumentsPackageContent/mustBeSigned

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xs:boolean
properties	content  simple
annotation	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.
source	<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>

element DocumentsPackageContent/document

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-docs:DocumentsPackageContentDocument
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-if:name xvergabe-if:fileSize xvergabe-if: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-if:ExistingObjectReference
properties	base  xvergabe-if:ExistingObjectReference
children	xvergabe-if:name xvergabe-if:fileSize xvergabe-if: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-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" 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-if:DateTimeTZ
properties	content  simple
facets	Kind  Value  Annotation pattern  ([0-9]{4})-(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]|(24:00:00))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-if: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	xvergabe-docs:TransformationDetails
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-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>

element DocumentsPackageContentRequiredDocument/name

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:String.255
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-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>

element DocumentsPackageContentRequiredDocument/description

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:String.1024
properties	content  simple
annotation	documentation Description of the document the bidder has to deliver.
source	<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>

complexType EncryptionKeyDetails

diagram
namespace	http://xvergabe.org/documents/xsd/4
children	xvergabe-docs:credentialID xvergabe-docs:encryptionOrder
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-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" 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-if:GUID
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-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>

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	xvergabe-docs:filename xvergabe-docs:documentID xvergabe-docs:hashValue
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-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" type="xvergabe-if: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	xvergabe-if:String.255
properties	content  simple
annotation	documentation The name of the file within the archive.
source	<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>

element FileAssociationType/documentID

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:GUID
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-if: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	xvergabe-docs:subject xvergabe-docs:inquiryBody xvergabe-docs:documentReference xvergabe-docs:lotReference
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-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" type="xvergabe-if: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-if: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	xvergabe-if:String.255
properties	content  simple
annotation	documentation The subject of the inquiry.
source	<xs:element name="subject" type="xvergabe-if: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	xs:string
properties	content  simple
annotation	appinfo <implementationHint>This element MUST wrap Information according to xvg-if:FormattedText within a CDATA-Section!</implementationHint> documentation The actual content of the inquiry. The actual type within this element MUST be xvg-if:FormattedText wrapped in a CDATA section!
source	<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>

element Inquiry/documentReference

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:ExistingObjectReference
properties	minOcc  0 maxOcc  unbounded content  complex
children	xvergabe-if:name xvergabe-if:fileSize xvergabe-if:attachmentIdentifier
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-if: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	xvergabe-if:GUID
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-if: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:signatureDetails xvergabe-docs:inquiry
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="signatureDetails" type="xvergabe-if:XMLSignature" minOccurs="0">       <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>

element InquiryDocumentType/signatureDetails

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:XMLSignature
properties	minOcc  0 maxOcc  1 content  complex
annotation	documentation Signature of the inquiry document.
source	<xs:element name="signatureDetails" type="xvergabe-if:XMLSignature" minOccurs="0">   <xs:annotation>     <xs:documentation>Signature of the inquiry document.</xs:documentation>   </xs:annotation> </xs:element>

element InquiryDocumentType/inquiry

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-docs:Inquiry
properties	content  complex
children	xvergabe-docs:subject xvergabe-docs:inquiryBody xvergabe-docs:documentReference xvergabe-docs:lotReference
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" 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  1 maxOcc  unbounded content  complex
children	xvergabe-docs:documentID xvergabe-docs:category xvergabe-docs:categorySortIndex xvergabe-docs:displayName xvergabe-docs:processingApplicationURL xvergabe-docs:belongsToPrimaryContainer xvergabe-docs:mustBeSigned xvergabe-docs:document
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" 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 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.
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-if: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" maxOccurs="unbounded"/>   </xs:sequence> </xs:complexType>

element InvitationToTenderDocumentType/lot

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:GUID
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-if: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	xvergabe-docs:TenderSubmissionDetails
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  1 maxOcc  unbounded content  complex
children	xvergabe-docs:documentID xvergabe-docs:category xvergabe-docs:categorySortIndex xvergabe-docs:displayName xvergabe-docs:processingApplicationURL xvergabe-docs:belongsToPrimaryContainer xvergabe-docs:mustBeSigned xvergabe-docs:document
source	<xs:element name="tenderDocument" type="xvergabe-docs:DocumentsPackageContent" 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-if:GUID">       <xs:annotation>         <xs:documentation>Unique identifier of the lot.</xs:documentation>       </xs:annotation>     </xs:element>     <xs:element name="lotName" type="xvergabe-if:String.1024" minOccurs="0">       <xs:annotation>         <xs:documentation>Name of the lot.</xs:documentation>       </xs:annotation>     </xs:element>     <xs:element name="lotNumber" type="xvergabe-if: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	xvergabe-if:GUID
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-if: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	xvergabe-if:String.1024
properties	minOcc  0 maxOcc  1 content  simple
annotation	documentation Name of the lot.
source	<xs:element name="lotName" type="xvergabe-if: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-if:String.255
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-if: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	xvergabe-cl:Code.StatusType
properties	minOcc  0 maxOcc  1 content  complex
children	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:statusType   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. listVersionID   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 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	xvergabe-docs:TimeLimitType
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-if: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-if:GUID
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-if: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
children	xvergabe-docs:processedOfferDetails xvergabe-docs:platformSpecificReceipt xvergabe-docs:platformSpecificReceiptReport
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.
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.</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" type="xvergabe-if: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-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>

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-if:ExistingObjectReference
properties	minOcc  0 maxOcc  1 content  complex
children	xvergabe-if:name xvergabe-if:fileSize xvergabe-if:attachmentIdentifier
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-if: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-if:ExistingObjectReference
properties	content  complex
children	xvergabe-if:name xvergabe-if:fileSize xvergabe-if:attachmentIdentifier
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-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>

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-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>

element OfferDocumentType/accordingITTMsgID

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:GUID
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.
source	<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>

element OfferDocumentType/offerObject

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-docs:OfferObject
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-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" type="xvergabe-if: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	xvergabe-if:GUID
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-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>

element OfferObject/secondaryContainer

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:GUID
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-if: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
children	xvergabe-docs:processedParticipationDetails xvergabe-docs:platformSpecificReceipt xvergabe-docs:platformSpecificReceiptReport
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.
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.</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" type="xvergabe-if:ExistingObjectReference" minOccurs="0"/>     <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>

element ParticipationDeliveryReceiptDocumentType/processedParticipationDetails

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-docs:ProcessedParticipationDetails
properties	content  complex
children	xvergabe-docs:accordingITPMsgID xvergabe-docs:participationTitle xvergabe-docs:appliedSignatureLevel xvergabe-docs:participationSendDateTime 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-if:ExistingObjectReference
properties	minOcc  0 maxOcc  1 content  complex
children	xvergabe-if:name xvergabe-if:fileSize xvergabe-if:attachmentIdentifier
source	<xs:element name="platformSpecificReceipt" type="xvergabe-if:ExistingObjectReference" minOccurs="0"/>

element ParticipationDeliveryReceiptDocumentType/platformSpecificReceiptReport

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:ExistingObjectReference
properties	content  complex
children	xvergabe-if:name xvergabe-if:fileSize xvergabe-if:attachmentIdentifier
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-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>

complexType ParticipationDocumentType

diagram
namespace	http://xvergabe.org/documents/xsd/4
children	xvergabe-docs:participationProcessingDetails 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="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>

element ParticipationDocumentType/participationProcessingDetails

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-docs:ParticipationProcessingDetails
properties	content  complex
children	xvergabe-docs:accordingITPMsgID xvergabe-docs:participationTitle xvergabe-docs:appliedSignatureLevel xvergabe-docs:participationSendDateTime
annotation	documentation Contains processing information about the participation request for the server.
source	<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>

element ParticipationDocumentType/participationObject

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-docs:OfferObject
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 ParticipationProcessingDetails

diagram
namespace	http://xvergabe.org/documents/xsd/4
children	xvergabe-docs:accordingITPMsgID xvergabe-docs:participationTitle xvergabe-docs:appliedSignatureLevel xvergabe-docs:participationSendDateTime
annotation	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.
source	<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>

element ParticipationProcessingDetails/accordingITPMsgID

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:GUID
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 offer was submitted on the most current version of the participation documents.
source	<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>

element ParticipationProcessingDetails/participationTitle

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:String.255
properties	content  simple
annotation	documentation Title of the participation request defined by the bidder or the bidder client.
source	<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>

element ParticipationProcessingDetails/appliedSignatureLevel

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-cl:Code.SignatureLevelType
properties	content  complex
children	code name
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. listVersionID   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 signature level used for the signature of the participation request.
source	<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>

element ParticipationProcessingDetails/participationSendDateTime

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:DateTimeTZ
properties	content  simple
facets	Kind  Value  Annotation pattern  ([0-9]{4})-(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]|(24:00:00))Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00)
annotation	documentation The date and time the participation request was submitted.
source	<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>

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:minimumSignatureLevel xvergabe-docs:minimumSignatureLevelForWithdrawal xvergabe-docs:applyContainerSignature xvergabe-docs:hybridEncryptionExpected 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:minimumSignatureLevel xvergabe-docs:minimumSignatureLevelForWithdrawal xvergabe-docs:applyContainerSignature xvergabe-docs:hybridEncryptionExpected 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="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" type="xs:boolean" default="false">       <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" 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/minimumSignatureLevel

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-cl:Code.SignatureLevelType
properties	content  complex
children	code name
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. listVersionID   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 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.
source	<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>

element ParticipationSubmissionDetailsElectronical/minimumSignatureLevelForWithdrawal

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-cl:Code.SignatureLevelType
properties	content  complex
children	code name
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. listVersionID   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 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/applyContainerSignature

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xs:boolean
properties	content  simple default  false
annotation	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.
source	<xs:element name="applyContainerSignature" type="xs:boolean" default="false">   <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>

element ParticipationSubmissionDetailsElectronical/hybridEncryptionExpected

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xs:boolean
properties	content  simple
annotation	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.
source	<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>

element ParticipationSubmissionDetailsElectronical/encryptionKey

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-docs:EncryptionKeyDetails
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	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:statusType   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. listVersionID   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 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	xvergabe-docs:TimeLimitType
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-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>

element ProcessedOfferDetails/offerMessageID

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:GUID
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-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>

element ProcessedOfferDetails/processedOfferID

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:GUID
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-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>

element ProcessedOfferDetails/receivedDateTime

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:DateTimeTZ
properties	content  simple
facets	Kind  Value  Annotation pattern  ([0-9]{4})-(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]|(24:00:00))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-if: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
type	extension of xvergabe-docs:ParticipationProcessingDetails
properties	base  xvergabe-docs:ParticipationProcessingDetails
children	xvergabe-docs:accordingITPMsgID xvergabe-docs:participationTitle xvergabe-docs:appliedSignatureLevel xvergabe-docs:participationSendDateTime xvergabe-docs:participationMessageID xvergabe-docs:processedParticipationID xvergabe-docs:receivedDateTime xvergabe-docs:receivedInTime
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: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>

element ProcessedParticipationDetails/participationMessageID

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:GUID
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-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>

element ProcessedParticipationDetails/processedParticipationID

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:GUID
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-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>

element ProcessedParticipationDetails/receivedDateTime

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:DateTimeTZ
properties	content  simple
facets	Kind  Value  Annotation pattern  ([0-9]{4})-(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]|(24:00:00))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-if: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	xvergabe-docs:withdrawalMessageID xvergabe-docs:withdrawalReceivedDateTime xvergabe-docs:withdrawalReceivedInTime
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-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>

element ProcessedWithdrawalDetails/withdrawalMessageID

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:GUID
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-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>

element ProcessedWithdrawalDetails/withdrawalReceivedDateTime

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:DateTimeTZ
properties	content  simple
facets	Kind  Value  Annotation pattern  ([0-9]{4})-(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]|(24:00:00))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-if: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	xvergabe-docs:OK xvergabe-docs:WARNING xvergabe-docs:ERROR xvergabe-docs:responseInformation
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-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" type="xvergabe-if: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-if: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-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>

element ResponseDocumentType/WARNING

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-cl:Code.WarningCodeType
properties	content  complex
children	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:warningCodeType   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. listVersionID   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 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">   <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	xvergabe-cl:Code.ErrorCodeType
properties	content  complex
children	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:errorCodeType   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. listVersionID   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 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	xvergabe-if:String.4096
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-if: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:signatureDetails xvergabe-docs:inquiry
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	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 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-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" type="xvergabe-if: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-if: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	xvergabe-if:GUID
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-if: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	xvergabe-if:String.4096
properties	content  simple
annotation	documentation The actual subject of the tendering procedure.
source	<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>

element TenderMetaInformationDetails/contractingAuthorityName

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:String.1024
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-if: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-if:String.255
properties	minOcc  0 maxOcc  1 content  simple
annotation	documentation The reference number of the tendering procedure.
source	<xs:element name="referenceNumber" type="xvergabe-if: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	xvergabe-cl:Code.ContractType
properties	minOcc  0 maxOcc  1 content  complex
children	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:contractType   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. listVersionID   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 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	xvergabe-cl:Code.ProcedureType
properties	content  complex
children	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:procedureType   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. listVersionID   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 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	xvergabe-docs:LotOverview
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 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: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	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 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:minimumSignatureLevel xvergabe-docs:minimumSignatureLevelForWithdrawal xvergabe-docs:applyContainerSignature xvergabe-docs:hybridEncryptionExpected 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:minimumSignatureLevel xvergabe-docs:minimumSignatureLevelForWithdrawal xvergabe-docs:applyContainerSignature xvergabe-docs:hybridEncryptionExpected 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="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" type="xs:boolean" default="false">       <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" 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/minimumSignatureLevel

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-cl:Code.SignatureLevelType
properties	content  complex
children	code name
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. listVersionID   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 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.
source	<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>

element TenderSubmissionDetailsElectronical/minimumSignatureLevelForWithdrawal

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-cl:Code.SignatureLevelType
properties	content  complex
children	code name
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. listVersionID   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 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/applyContainerSignature

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xs:boolean
properties	content  simple default  false
annotation	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.
source	<xs:element name="applyContainerSignature" type="xs:boolean" default="false">   <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>

element TenderSubmissionDetailsElectronical/hybridEncryptionExpected

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xs:boolean
properties	content  simple
annotation	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.
source	<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>

element TenderSubmissionDetailsElectronical/encryptionKey

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-docs:EncryptionKeyDetails
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	xvergabe-docs:intermediaryURI xvergabe-docs:intermediaryPublicKeyReference xvergabe-docs:addresseePublicKeyReference xvergabe-docs:useTransportEncryption xvergabe-docs:intermediarySupportsCryptographicTimestamps xvergabe-docs:verificationServiceURI
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	xvergabe-docs:intermediaryURI xvergabe-docs:intermediaryPublicKeyReference xvergabe-docs:addresseePublicKeyReference xvergabe-docs:useTransportEncryption xvergabe-docs:intermediarySupportsCryptographicTimestamps xvergabe-docs:verificationServiceURI
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-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" 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	xvergabe-if:GUID
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-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>

element TenderSubmissionDetailsOSCI/addresseePublicKeyReference

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:GUID
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-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>

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	xvergabe-docs:numberOfCopies xvergabe-docs:isBackup xvergabe-docs:includeElectronicalTenderDocuments
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-if: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	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:timeLimitType   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. listVersionID   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 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-if:DateTimeTZ
properties	content  simple
facets	Kind  Value  Annotation pattern  ([0-9]{4})-(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]|(24:00:00))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-if: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	xvergabe-docs:targetFilename xvergabe-docs:targetExtension xvergabe-docs:targetMiMEType xvergabe-docs:targetProcessingApplicationURL
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-if: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-if: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-if: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	xvergabe-if:String.255
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-if: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	xvergabe-if:String.255
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-if: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-if:String.255
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-if: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	xvergabe-docs:limitType xvergabe-docs:limitValue
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	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:uploadLimitType   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. listVersionID   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 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
children	xvergabe-docs:processedWithdrawalDetails xvergabe-docs:platformSpecificReceipt xvergabe-docs:platformSpecificReceiptReport
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.
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.</xs:documentation>   </xs:annotation>   <xs:sequence>     <xs:element name="processedWithdrawalDetails" type="xvergabe-docs:ProcessedWithdrawalDetails"/>     <xs:element name="platformSpecificReceipt" type="xvergabe-if:ExistingObjectReference" minOccurs="0"/>     <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>

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-if:ExistingObjectReference
properties	minOcc  0 maxOcc  1 content  complex
children	xvergabe-if:name xvergabe-if:fileSize xvergabe-if:attachmentIdentifier
source	<xs:element name="platformSpecificReceipt" type="xvergabe-if:ExistingObjectReference" minOccurs="0"/>

element WithdrawalDeliveryReceiptDocumentType/platformSpecificReceiptReport

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:ExistingObjectReference
properties	content  complex
children	xvergabe-if:name xvergabe-if:fileSize xvergabe-if:attachmentIdentifier
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-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>

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-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" type="xvergabe-if: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-if: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	xvergabe-if:GUID
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-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>

element WithdrawalDocumentType/withdrawalReason

diagram
namespace	http://xvergabe.org/documents/xsd/4
type	xvergabe-if:String.4096
properties	minOcc  0 maxOcc  1 content  simple
annotation	documentation The reasons for the withdrawal.
source	<xs:element name="withdrawalReason" type="xvergabe-if: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:DateTimeTZ
properties	content  simple
facets	Kind  Value  Annotation pattern  ([0-9]{4})-(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]|(24:00:00))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-if:DateTimeTZ">   <xs:annotation>     <xs:documentation>The date and time of the withdrawal.</xs:documentation>   </xs:annotation> </xs:element>

complexType ExistingObjectReference

diagram
namespace	http://xvergabe.org/interface/xsd/4
children	xvergabe-if:name xvergabe-if:fileSize xvergabe-if:attachmentIdentifier
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-if: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-if: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/interface/xsd/4
type	xvergabe-if:String.1024
properties	minOcc  0 maxOcc  1 content  simple
annotation	documentation The name for this reference.
source	<xs:element name="name" type="xvergabe-if: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/interface/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/interface/xsd/4
type	xvergabe-if:GUID
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-if: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 FormattedText

diagram
namespace	http://xvergabe.org/interface/xsd/4
type	extension of BasicXHTML
properties	base  bxhtml:BasicXHTML
children	p h1 h2 h3 h4 h5 h6 ul ol hr br i b u em strong
annotation	documentation text which might be structured by a limited set of XHTML tags (p, h1..h6, b, strong, u, em, i, ol, li, ul, br, hr). the structuring is handled by an external schema redefinition of XHTML1 transitional. Elements using this Datatype MUST be wrapped within a CDATA-section.
source	<xs:complexType name="FormattedText">   <xs:annotation>     <xs:documentation>text which might be structured by a limited set of XHTML tags (p, h1..h6, b, strong, u, em, i, ol, li, ul, br, hr). the structuring is handled by an external schema redefinition of XHTML1 transitional. Elements using this Datatype MUST be wrapped within a CDATA-section.</xs:documentation>   </xs:annotation>   <xs:complexContent>     <xs:extension base="bxhtml:BasicXHTML"/>   </xs:complexContent> </xs:complexType>

complexType XMLSignature

diagram
namespace	http://xvergabe.org/interface/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/interface/xsd/4
type	restriction of xs:dateTime
properties	base  xs:dateTime
facets	Kind  Value  Annotation pattern  ([0-9]{4})-(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]|(24:00:00))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="([0-9]{4})-(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]|(24:00:00))Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00) "/>   </xs:restriction> </xs:simpleType>

simpleType GUID

namespace	http://xvergabe.org/interface/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/interface/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/interface/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/interface/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/interface/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 messages.Attachment

diagram
namespace	http://xvergabe.org/interface/xsd/4
type	extension of xvergabe-if:Attachment
properties	content  complex
children	xvergabe-if:attachmentID xvergabe-if:filename xvergabe-if:description xvergabe-if:attachmentData xvergabe-if:signature
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	xvergabe-if:messageHeader xvergabe-if:document
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
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	xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment
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
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	xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment
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:document
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	xvergabe-if:messageHeader xvergabe-if:offer xvergabe-if:participationRequest xvergabe-if:withdrawal
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
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	xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment
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	xvergabe-if:messageHeader xvergabe-if:document
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	xvergabe-if:messageHeader xvergabe-if:document
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	xvergabe-if:messageHeader xvergabe-if:document
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 xvergabe-if:document
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	xvergabe-if:messageHeader
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-if: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-if: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-if:String.1024" minOccurs="0">       <xs:annotation>         <xs:documentation>Textual description of the attachment.</xs:documentation>       </xs:annotation>     </xs:element>     <xs:element name="attachmentData" type="xs:base64Binary">       <xs:annotation>         <xs:documentation>base64 encoded attachment data (the file itself). for encrypted attachments this MUST be PKCS#7 content (base64 encoded).</xs:documentation>       </xs:annotation>     </xs:element>     <xs:element name="signature" type="xvergabe-if: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	xvergabe-if:GUID
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-if: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	xvergabe-if:String.255
properties	content  simple
annotation	documentation Full file name including the file extension.
source	<xs:element name="filename" type="xvergabe-if: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-if:String.1024
properties	minOcc  0 maxOcc  1 content  simple
annotation	documentation Textual description of the attachment.
source	<xs:element name="description" type="xvergabe-if: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	xs:base64Binary
properties	content  simple
annotation	documentation base64 encoded attachment data (the file itself). for encrypted attachments this MUST be PKCS#7 content (base64 encoded).
source	<xs:element name="attachmentData" type="xs:base64Binary">   <xs:annotation>     <xs:documentation>base64 encoded attachment data (the file itself). for encrypted attachments this MUST be PKCS#7 content (base64 encoded).</xs:documentation>   </xs:annotation> </xs:element>

element Attachment/signature

diagram
namespace	http://xvergabe.org/interface/xsd/4
type	xvergabe-if:XMLSignature
properties	minOcc  0 maxOcc  1 content  complex
annotation	documentation optional signature of the attachment.
source	<xs:element name="signature" type="xvergabe-if: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	extension of xvergabe-if:AbstractClientMessage
properties	base  xvergabe-if:AbstractClientMessage
children	xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment
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	xvergabe-docs:signatureDetails xvergabe-docs:inquiry
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:Attachment
properties	minOcc  0 maxOcc  unbounded content  complex
children	xvergabe-if:attachmentID xvergabe-if:filename xvergabe-if:description xvergabe-if:attachmentData xvergabe-if:signature
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-if: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="xs:base64Binary">       <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-if:GUID
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-if: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	xvergabe-cl:Code.CredentialUsage
properties	minOcc  1 maxOcc  unbounded content  complex
children	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:credentialusage   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. listVersionID   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 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	xs:base64Binary
properties	content  simple
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="xs:base64Binary">   <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	extension of xvergabe-if:AbstractServerMessage
properties	base  xvergabe-if:AbstractServerMessage
children	xvergabe-if:messageHeader xvergabe-if:document
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	xvergabe-docs:InvitationToParticipationDocumentType
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	extension of xvergabe-if:AbstractServerMessage
properties	base  xvergabe-if:AbstractServerMessage
children	xvergabe-if:messageHeader xvergabe-if:document
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	xvergabe-docs:InvitationToTenderDocumentType
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-if: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:GUID
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-if: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	xvergabe-if:messageID xvergabe-if:sendingDateTime
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:sendingDateTime
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-if:GUID">       <xs:annotation>         <xs:documentation>ID of the message given by the sending application</xs:documentation>       </xs:annotation>     </xs:element>     <xs:element name="sendingDateTime" type="xvergabe-if:DateTimeTZ">       <xs:annotation>         <xs:documentation>timestamp given by the sending application about the time of sending of the message</xs:documentation>       </xs:annotation>     </xs:element>   </xs:sequence> </xs:complexType>

element MessageInfo/messageID

diagram
namespace	http://xvergabe.org/interface/xsd/4
type	xvergabe-if:GUID
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-if:GUID">   <xs:annotation>     <xs:documentation>ID of the message given by the sending application</xs:documentation>   </xs:annotation> </xs:element>

element MessageInfo/sendingDateTime

diagram
namespace	http://xvergabe.org/interface/xsd/4
type	xvergabe-if:DateTimeTZ
properties	content  simple
facets	Kind  Value  Annotation pattern  ([0-9]{4})-(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]|(24:00:00))Z|(\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00)
annotation	documentation timestamp given by the sending application about the time of sending of the message
source	<xs:element name="sendingDateTime" type="xvergabe-if:DateTimeTZ">   <xs:annotation>     <xs:documentation>timestamp given by the sending application about the time of sending of the message</xs:documentation>   </xs:annotation> </xs:element>

complexType OfferDeliveryReceiptMessageType

diagram
namespace	http://xvergabe.org/interface/xsd/4
type	extension of xvergabe-if:AbstractServerMessage
properties	base  xvergabe-if:AbstractServerMessage
children	xvergabe-if:messageHeader xvergabe-if:document
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	xvergabe-docs:OfferDeliveryReceiptDocumentType
properties	content  complex
children	xvergabe-docs:processedOfferDetails xvergabe-docs:platformSpecificReceipt xvergabe-docs:platformSpecificReceiptReport
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.
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	extension of xvergabe-if:AbstractClientMessage
properties	base  xvergabe-if:AbstractClientMessage
children	xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment
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 (base64-encoded) 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:Attachment
properties	minOcc  1 maxOcc  2 content  complex
children	xvergabe-if:attachmentID xvergabe-if:filename xvergabe-if:description xvergabe-if:attachmentData xvergabe-if:signature
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 (base64-encoded) 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 (base64-encoded) 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	extension of xvergabe-if:AbstractServerMessage
properties	base  xvergabe-if:AbstractServerMessage
children	xvergabe-if:messageHeader xvergabe-if:document
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	xvergabe-docs:WithdrawalDeliveryReceiptDocumentType
properties	content  complex
children	xvergabe-docs:processedWithdrawalDetails xvergabe-docs:platformSpecificReceipt xvergabe-docs:platformSpecificReceiptReport
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.
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	extension of xvergabe-if:AbstractClientMessage
properties	base  xvergabe-if:AbstractClientMessage
children	xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment
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:Attachment
properties	minOcc  0 maxOcc  unbounded content  complex
children	xvergabe-if:attachmentID xvergabe-if:filename xvergabe-if:description xvergabe-if:attachmentData xvergabe-if:signature
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	extension of xvergabe-if:AbstractClientMessage
properties	base  xvergabe-if:AbstractClientMessage
children	xvergabe-if:messageHeader xvergabe-if:offer xvergabe-if:participationRequest xvergabe-if:withdrawal
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-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. 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-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 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-if: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-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. 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:GUID
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	<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. 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>

element OSCITransferIDRequestType/participationRequest

diagram
namespace	http://xvergabe.org/interface/xsd/4
properties	content  complex
children	xvergabe-if:accordingITPMsgID
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-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 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	xvergabe-if:GUID
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-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 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-if: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	xvergabe-if:GUID
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-if: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	extension of xvergabe-if:AbstractServerMessage
properties	base  xvergabe-if:AbstractServerMessage
children	xvergabe-if:messageHeader xvergabe-if:document
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	xvergabe-docs:ParticipationDeliveryReceiptDocumentType
properties	content  complex
children	xvergabe-docs:processedParticipationDetails xvergabe-docs:platformSpecificReceipt xvergabe-docs:platformSpecificReceiptReport
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.
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	extension of xvergabe-if:AbstractClientMessage
properties	base  xvergabe-if:AbstractClientMessage
children	xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment
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 (base64-encoded) 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:participationProcessingDetails 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:Attachment
properties	minOcc  1 maxOcc  2 content  complex
children	xvergabe-if:attachmentID xvergabe-if:filename xvergabe-if:description xvergabe-if:attachmentData xvergabe-if:signature
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 (base64-encoded) 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 (base64-encoded) 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	extension of xvergabe-if:AbstractServerMessage
properties	base  xvergabe-if:AbstractServerMessage
children	xvergabe-if:messageHeader xvergabe-if:document
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	xvergabe-docs:WithdrawalDeliveryReceiptDocumentType
properties	content  complex
children	xvergabe-docs:processedWithdrawalDetails xvergabe-docs:platformSpecificReceipt xvergabe-docs:platformSpecificReceiptReport
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.
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 ParticipationWithdrawalMessageType

diagram
namespace	http://xvergabe.org/interface/xsd/4
type	extension of xvergabe-if:AbstractClientMessage
properties	base  xvergabe-if:AbstractClientMessage
children	xvergabe-if:messageHeader xvergabe-if:document xvergabe-if:attachment
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:Attachment
properties	minOcc  0 maxOcc  unbounded content  complex
children	xvergabe-if:attachmentID xvergabe-if:filename xvergabe-if:description xvergabe-if:attachmentData xvergabe-if:signature
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 ResultNoticeMessageType

diagram
namespace	http://xvergabe.org/interface/xsd/4
type	extension of xvergabe-if:AbstractServerMessage
properties	base  xvergabe-if:AbstractServerMessage
children	xvergabe-if:messageHeader xvergabe-if:document
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	xvergabe-docs:ResultNoticeDocumentType
properties	content  complex
children	xvergabe-docs:signatureDetails xvergabe-docs:inquiry
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: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	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: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-if: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-if: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-if:String.1024">       <xs:annotation>         <xs:documentation>productname of the sending application</xs:documentation>       </xs:annotation>     </xs:element>     <xs:element name="productVersion" type="xvergabe-if:String.255">       <xs:annotation>         <xs:documentation>versionnumber of the sending application</xs:documentation>       </xs:annotation>     </xs:element>     <xs:element name="productInstance" type="xvergabe-if: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	xvergabe-if:String.1024
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-if: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	xvergabe-if:String.1024
properties	content  simple
annotation	documentation name of the vendor of the sending application
source	<xs:element name="vendor" type="xvergabe-if: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	xvergabe-if:String.1024
properties	content  simple
annotation	documentation productname of the sending application
source	<xs:element name="product" type="xvergabe-if: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	xvergabe-if:String.255
properties	content  simple
annotation	documentation versionnumber of the sending application
source	<xs:element name="productVersion" type="xvergabe-if: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	xvergabe-if:String.1024
properties	minOcc  0 maxOcc  1 content  simple
annotation	documentation name of the instance of the sending application
source	<xs:element name="productInstance" type="xvergabe-if: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	extension of xvergabe-if:AbstractServerMessage
properties	base  xvergabe-if:AbstractServerMessage
children	xvergabe-if:messageHeader xvergabe-if:document
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	xvergabe-docs:InquiryDocumentType
properties	content  complex
children	xvergabe-docs:signatureDetails xvergabe-docs:inquiry
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	extension of xvergabe-if:AbstractServerMessage
properties	base  xvergabe-if:AbstractServerMessage
children	xvergabe-if:messageHeader xvergabe-if:document
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	xvergabe-docs:TenderMetaInformationDocumentType
properties	content  complex
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: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	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:contractType   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. listVersionID   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 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 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.
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 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).
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	<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>

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	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:credentialusage   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. listVersionID   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 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 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.
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 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).
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.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	<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>

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	<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.EncryptionAlgorithm

diagram
namespace	http://xvergabe.org/codelists/xsd/4
type	restriction of xoev-code:Code
properties	base  xoev-code:Code
children	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:encryptionalgorithm   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. listVersionID   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 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 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.
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 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).
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.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	<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>

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	<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.ErrorCodeType

diagram
namespace	http://xvergabe.org/codelists/xsd/4
type	restriction of xoev-code:Code
properties	base  xoev-code:Code
children	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:errorCodeType   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. listVersionID   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 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="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="REGISTRATION_REQUIRED">                 <xs:annotation>                   <xs:documentation>an indicator for the client that the desired action can only be done after registration. the error is most likely to occur when a client tries to call a webservice operation without usercredentials (usernametoken). The platform SHALL include the link to the registration site within "redirectURL"</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 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.
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 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).
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.ErrorCodeType/code

diagram
type	restriction of xs:token
properties	content  simple form  unqualified
facets	Kind  Value  Annotation 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  REGISTRATION_REQUIRED documentation an indicator for the client that the desired action can only be done after registration. the error is most likely to occur when a client tries to call a webservice operation without usercredentials (usernametoken). The platform SHALL include the link to the registration site within "redirectURL" 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="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="REGISTRATION_REQUIRED">         <xs:annotation>           <xs:documentation>an indicator for the client that the desired action can only be done after registration. the error is most likely to occur when a client tries to call a webservice operation without usercredentials (usernametoken). The platform SHALL include the link to the registration site within "redirectURL"</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	<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.ProcedureType

diagram
namespace	http://xvergabe.org/codelists/xsd/4
type	restriction of xoev-code:Code
properties	base  xoev-code:Code
children	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:procedureType   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. listVersionID   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 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 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.
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 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).
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.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	<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>

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	<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.SignatureLevelType

diagram
namespace	http://xvergabe.org/codelists/xsd/4
type	restriction of xoev-code:Code
properties	base  xoev-code:Code
children	code name
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. listVersionID   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 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 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.
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 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).
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.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	<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>

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	<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.StatusType

diagram
namespace	http://xvergabe.org/codelists/xsd/4
type	restriction of xoev-code:Code
properties	base  xoev-code:Code
children	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:statusType   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. listVersionID   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 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 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.
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 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).
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.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	<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>

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	<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.TimeLimitType

diagram
namespace	http://xvergabe.org/codelists/xsd/4
type	restriction of xoev-code:Code
properties	base  xoev-code:Code
children	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:timeLimitType   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. listVersionID   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 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 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.
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 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).
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.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	<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>

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	<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.UploadLimitType

diagram
namespace	http://xvergabe.org/codelists/xsd/4
type	restriction of xoev-code:Code
properties	base  xoev-code:Code
children	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:uploadLimitType   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. listVersionID   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 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 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.
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 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).
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.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	<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>

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	<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.WarningCodeType

diagram
namespace	http://xvergabe.org/codelists/xsd/4
type	restriction of xoev-code:Code
properties	base  xoev-code:Code
children	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional      urn:org:xvergabe:codelists:warningCodeType   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. listVersionID   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 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="ATTACHMENTS_EXCEED_MAX_SIZE_FOR_ALL_ATTACHMENTS">                 <xs:annotation>                   <xs:documentation>warning 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>warning 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="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_ALLREADY_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 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.
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 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).
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.WarningCodeType/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 warning 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 warning 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  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_ALLREADY_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="ATTACHMENTS_EXCEED_MAX_SIZE_FOR_ALL_ATTACHMENTS">         <xs:annotation>           <xs:documentation>warning 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>warning 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="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_ALLREADY_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	<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 BasicXHTML

diagram
namespace	http://xvergabe.org/client-interface/basic-xhtml-redefinition/4
type	restriction of Flow
properties	base  xhtml:Flow
children	p h1 h2 h3 h4 h5 h6 ul ol hr br i b u em strong
source	<xs:complexType name="BasicXHTML">   <xs:complexContent>     <xs:restriction base="xhtml:Flow">       <xs:choice minOccurs="0" maxOccurs="unbounded">         <xs:group ref="xhtml:block"/>         <xs:group ref="xhtml:inline"/>         <xs:group ref="xhtml:misc"/>       </xs:choice>     </xs:restriction>   </xs:complexContent> </xs:complexType>

complexType Code

diagram
namespace	http://xoev.de/schemata/code/1_0
children	code name
attributes	Name   Type   Use   Default   Fixed   Annotation listURI   xs:anyURI   optional         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. listVersionID   xs:normalizedString   optional         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 Der XÖV-Datentyp Code ermöglicht die Übermittlung von Werten, so genannter Codes, aus vordefinierten Codelisten. Eine Codeliste ist eine Liste von Codes und der Beschreibung ihrer jeweiligen Bedeutung.clRef Eine entscheidende Eigenschaft des Datentyps ist die Möglichkeit auf differenzierte Weise Bezug zu Codelisten zu nehmen (Code-Typ 1 bis 4).clTypenRef In jedem Fall erlauben die übermittelten Daten eine eindeutige Identifizierung der zugrundeliegenden Codeliste.
source	<xs:complexType name="Code">   <xs:annotation>     <xs:documentation>Der XÖV-Datentyp Code ermöglicht die Übermittlung von Werten, so genannter Codes, aus vordefinierten Codelisten. Eine Codeliste ist eine Liste von Codes und der Beschreibung ihrer jeweiligen Bedeutung.clRef Eine entscheidende Eigenschaft des Datentyps ist die Möglichkeit auf differenzierte Weise Bezug zu Codelisten zu nehmen (Code-Typ 1 bis 4).clTypenRef In jedem Fall erlauben die übermittelten Daten eine eindeutige Identifizierung der zugrundeliegenden Codeliste.</xs:documentation>   </xs:annotation>   <xs:sequence>     <xs:element name="code" type="xs:token" form="unqualified">       <xs:annotation>         <xs:documentation>In diesem XML-Element wird der Code einer Codeliste übermittelt.</xs:documentation>       </xs:annotation>     </xs:element>     <xs:element name="name" type="xs:normalizedString" form="unqualified" minOccurs="0">       <xs:annotation>         <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">     <xs:annotation>       <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">     <xs:annotation>       <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:complexType>

attribute Code/@listURI

type	xs:anyURI
properties	use  optional
annotation	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.
source	<xs:attribute name="listURI" type="xs:anyURI" use="optional">   <xs:annotation>     <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/@listVersionID

type	xs:normalizedString
properties	use  optional
annotation	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).
source	<xs:attribute name="listVersionID" type="xs:normalizedString" use="optional">   <xs:annotation>     <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/code

diagram
type	xs:token
properties	content  simple form  unqualified
annotation	documentation In diesem XML-Element wird der Code einer Codeliste übermittelt.
source	<xs:element name="code" type="xs:token" form="unqualified">   <xs:annotation>     <xs:documentation>In diesem XML-Element wird der Code einer Codeliste übermittelt.</xs:documentation>   </xs:annotation> </xs:element>

element Code/name

diagram
type	xs:normalizedString
properties	minOcc  0 maxOcc  1 content  simple form  unqualified
annotation	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>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>

redefinition of group block

diagram
children	p h1 h2 h3 h4 h5 h6 ul ol hr
source	<xs:group name="block">   <xs:choice>     <xs:element ref="xhtml:p"/>     <xs:group ref="xhtml:heading"/>     <xs:group ref="xhtml:lists"/>     <xs:group ref="xhtml:blocktext"/>   </xs:choice> </xs:group>

redefinition of group blocktext

diagram
children	hr
source	<xs:group name="blocktext">   <xs:choice>     <xs:element ref="xhtml:hr"/>   </xs:choice> </xs:group>

redefinition of group fontstyle

diagram
children	i b u
source	<xs:group name="fontstyle">   <xs:choice>     <xs:group ref="xhtml:fontstyle.basic"/>   </xs:choice> </xs:group>

redefinition of group fontstyle.basic

diagram
children	i b u
source	<xs:group name="fontstyle.basic">   <xs:choice>     <xs:element ref="xhtml:i"/>     <xs:element ref="xhtml:b"/>     <xs:element ref="xhtml:u"/>   </xs:choice> </xs:group>

redefinition of group inline

diagram
children	br i b u em strong
source	<xs:group name="inline">   <xs:choice>     <xs:group ref="xhtml:special"/>     <xs:group ref="xhtml:fontstyle"/>     <xs:group ref="xhtml:phrase"/>   </xs:choice> </xs:group>

redefinition of group lists

diagram
children	ul ol
source	<xs:group name="lists">   <xs:choice>     <xs:element ref="xhtml:ul"/>     <xs:element ref="xhtml:ol"/>   </xs:choice> </xs:group>

redefinition of group misc

diagram
source	<xs:group name="misc">   <xs:choice>     <xs:group ref="xhtml:misc.inline"/>   </xs:choice> </xs:group>

redefinition of group misc.inline

diagram
source	<xs:group name="misc.inline">   <xs:choice/> </xs:group>

redefinition of group phrase

diagram
children	em strong
source	<xs:group name="phrase">   <xs:choice>     <xs:group ref="xhtml:phrase.basic"/>   </xs:choice> </xs:group>

redefinition of group phrase.basic

diagram
children	em strong
source	<xs:group name="phrase.basic">   <xs:choice>     <xs:element ref="xhtml:em"/>     <xs:element ref="xhtml:strong"/>   </xs:choice> </xs:group>

redefinition of group special

diagram
children	br
source	<xs:group name="special">   <xs:choice>     <xs:group ref="xhtml:special.basic"/>   </xs:choice> </xs:group>

redefinition of group special.basic

diagram
children	br
source	<xs:group name="special.basic">   <xs:choice>     <xs:element ref="xhtml:br"/>   </xs:choice> </xs:group>

redefinition of attributeGroup attrs

source

<xs:attributeGroup name="attrs"/>

redefinition of attributeGroup coreattrs

source

<xs:attributeGroup name="coreattrs"/>

redefinition of attributeGroup TextAlign

source

<xs:attributeGroup name="TextAlign"/>

element a

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of a.content
properties	content  complex mixed  true
children	br i b u em strong input select textarea label button
attributes	Name   Type   Use   Default   Fixed   Annotation accesskey   Character            tabindex   tabindexNumber            onfocus   Script            onblur   Script            charset   Charset            type   ContentType            name   xs:NMTOKEN            href   URI            hreflang   LanguageCode            rel   LinkTypes            rev   LinkTypes            shape   Shape      rect      coords   Coords            target   FrameTarget
annotation	documentation       content is "Inline" except that anchors shouldn't be nested
source	<xs:element name="a">   <xs:annotation>     <xs:documentation>       content is "Inline" except that anchors shouldn't be nested       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="a.content">         <xs:attributeGroup ref="attrs"/>         <xs:attributeGroup ref="focus"/>         <xs:attribute name="charset" type="Charset"/>         <xs:attribute name="type" type="ContentType"/>         <xs:attribute name="name" type="xs:NMTOKEN"/>         <xs:attribute name="href" type="URI"/>         <xs:attribute name="hreflang" type="LanguageCode"/>         <xs:attribute name="rel" type="LinkTypes"/>         <xs:attribute name="rev" type="LinkTypes"/>         <xs:attribute name="shape" type="Shape" default="rect"/>         <xs:attribute name="coords" type="Coords"/>         <xs:attribute name="target" type="FrameTarget"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute a/@charset

type	Charset
source	<xs:attribute name="charset" type="Charset"/>

attribute a/@type

type	ContentType
source	<xs:attribute name="type" type="ContentType"/>

attribute a/@name

type	xs:NMTOKEN
source	<xs:attribute name="name" type="xs:NMTOKEN"/>

attribute a/@href

type	URI
source	<xs:attribute name="href" type="URI"/>

attribute a/@hreflang

type	LanguageCode
source	<xs:attribute name="hreflang" type="LanguageCode"/>

attribute a/@rel

type	LinkTypes
source	<xs:attribute name="rel" type="LinkTypes"/>

attribute a/@rev

type	LinkTypes
source	<xs:attribute name="rev" type="LinkTypes"/>

attribute a/@shape

type	Shape
properties	default  rect
facets	Kind  Value  Annotation enumeration  rect enumeration  circle enumeration  poly enumeration  default
source	<xs:attribute name="shape" type="Shape" default="rect"/>

attribute a/@coords

type	Coords
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)(,\s*[-+]?(\d+|\d+(\.\d+)?%))*
source	<xs:attribute name="coords" type="Coords"/>

attribute a/@target

type	FrameTarget
facets	Kind  Value  Annotation pattern  _(blank|self|parent|top)|[A-Za-z]\c*
source	<xs:attribute name="target" type="FrameTarget"/>

element abbr

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       abbreviation
source	<xs:element name="abbr">   <xs:annotation>     <xs:documentation>       abbreviation       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element acronym

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       acronym
source	<xs:element name="acronym">   <xs:annotation>     <xs:documentation>       acronym       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element address

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex mixed  true
children	br i b u em strong p
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       information on author
source	<xs:element name="address">   <xs:annotation>     <xs:documentation>       information on author       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:choice minOccurs="0" maxOccurs="unbounded">       <xs:group ref="inline"/>       <xs:group ref="misc.inline"/>       <xs:element ref="p"/>     </xs:choice>     <xs:attributeGroup ref="attrs"/>   </xs:complexType> </xs:element>

element applet

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex mixed  true
children	param p h1 h2 h3 h4 h5 h6 ul ol hr form br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation codebase   URI            archive               code               object               alt   Text            name   xs:NMTOKEN            width   Length   required         height   Length   required         align   ImgAlign            hspace   Pixels            vspace   Pixels
source	<xs:element name="applet">   <xs:complexType mixed="true">     <xs:choice minOccurs="0" maxOccurs="unbounded">       <xs:element ref="param"/>       <xs:group ref="block"/>       <xs:element ref="form"/>       <xs:group ref="inline"/>       <xs:group ref="misc"/>     </xs:choice>     <xs:attributeGroup ref="coreattrs"/>     <xs:attribute name="codebase" type="URI"/>     <xs:attribute name="archive"/>     <xs:attribute name="code"/>     <xs:attribute name="object"/>     <xs:attribute name="alt" type="Text"/>     <xs:attribute name="name" type="xs:NMTOKEN"/>     <xs:attribute name="width" type="Length" use="required"/>     <xs:attribute name="height" type="Length" use="required"/>     <xs:attribute name="align" type="ImgAlign"/>     <xs:attribute name="hspace" type="Pixels"/>     <xs:attribute name="vspace" type="Pixels"/>   </xs:complexType> </xs:element>

attribute applet/@codebase

type	URI
source	<xs:attribute name="codebase" type="URI"/>

attribute applet/@archive

source

<xs:attribute name="archive"/>

attribute applet/@code

source

<xs:attribute name="code"/>

attribute applet/@object

source

<xs:attribute name="object"/>

attribute applet/@alt

type	Text
source	<xs:attribute name="alt" type="Text"/>

attribute applet/@name

type	xs:NMTOKEN
source	<xs:attribute name="name" type="xs:NMTOKEN"/>

attribute applet/@width

type	Length
properties	use  required
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="width" type="Length" use="required"/>

attribute applet/@height

type	Length
properties	use  required
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="height" type="Length" use="required"/>

attribute applet/@align

type	ImgAlign
facets	Kind  Value  Annotation enumeration  top enumeration  middle enumeration  bottom enumeration  left enumeration  right
source	<xs:attribute name="align" type="ImgAlign"/>

attribute applet/@hspace

type	Pixels
source	<xs:attribute name="hspace" type="Pixels"/>

attribute applet/@vspace

type	Pixels
source	<xs:attribute name="vspace" type="Pixels"/>

element area

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
attributes	Name   Type   Use   Default   Fixed   Annotation accesskey   Character            tabindex   tabindexNumber            onfocus   Script            onblur   Script            shape   Shape      rect      coords   Coords            href   URI            nohref   derived by: xs:token            alt   Text   required         target   FrameTarget
source	<xs:element name="area">   <xs:complexType>     <xs:attributeGroup ref="attrs"/>     <xs:attributeGroup ref="focus"/>     <xs:attribute name="shape" type="Shape" default="rect"/>     <xs:attribute name="coords" type="Coords"/>     <xs:attribute name="href" type="URI"/>     <xs:attribute name="nohref">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="nohref"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute name="alt" type="Text" use="required"/>     <xs:attribute name="target" type="FrameTarget"/>   </xs:complexType> </xs:element>

attribute area/@shape

type	Shape
properties	default  rect
facets	Kind  Value  Annotation enumeration  rect enumeration  circle enumeration  poly enumeration  default
source	<xs:attribute name="shape" type="Shape" default="rect"/>

attribute area/@coords

type	Coords
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)(,\s*[-+]?(\d+|\d+(\.\d+)?%))*
source	<xs:attribute name="coords" type="Coords"/>

attribute area/@href

type	URI
source	<xs:attribute name="href" type="URI"/>

attribute area/@nohref

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  nohref
source	<xs:attribute name="nohref">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="nohref"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute area/@alt

type	Text
properties	use  required
source	<xs:attribute name="alt" type="Text" use="required"/>

attribute area/@target

type	FrameTarget
facets	Kind  Value  Annotation pattern  _(blank|self|parent|top)|[A-Za-z]\c*
source	<xs:attribute name="target" type="FrameTarget"/>

element b

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       bold font
source	<xs:element name="b">   <xs:annotation>     <xs:documentation>       bold font       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element base

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
attributes	Name   Type   Use   Default   Fixed   Annotation id   xs:ID            href   URI            target   FrameTarget
annotation	documentation       document base URI
source	<xs:element name="base">   <xs:annotation>     <xs:documentation>       document base URI       </xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:attribute name="id" type="xs:ID"/>     <xs:attribute name="href" type="URI"/>     <xs:attribute name="target" type="FrameTarget"/>   </xs:complexType> </xs:element>

attribute base/@id

type	xs:ID
source	<xs:attribute name="id" type="xs:ID"/>

attribute base/@href

type	URI
source	<xs:attribute name="href" type="URI"/>

attribute base/@target

type	FrameTarget
facets	Kind  Value  Annotation pattern  _(blank|self|parent|top)|[A-Za-z]\c*
source	<xs:attribute name="target" type="FrameTarget"/>

element basefont

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
attributes	Name   Type   Use   Default   Fixed   Annotation id   xs:ID            size      required         color   Color            face
annotation	documentation       base font size
source	<xs:element name="basefont">   <xs:annotation>     <xs:documentation>       base font size       </xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:attribute name="id" type="xs:ID"/>     <xs:attribute name="size" use="required"/>     <xs:attribute name="color" type="Color"/>     <xs:attribute name="face"/>   </xs:complexType> </xs:element>

attribute basefont/@id

type	xs:ID
source	<xs:attribute name="id" type="xs:ID"/>

attribute basefont/@size

properties	use  required
source	<xs:attribute name="size" use="required"/>

attribute basefont/@color

type	Color
facets	Kind  Value  Annotation pattern  [A-Za-z]+|#[0-9A-Fa-f]{3}|#[0-9A-Fa-f]{6}
source	<xs:attribute name="color" type="Color"/>

attribute basefont/@face

source

<xs:attribute name="face"/>

element bdo

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation onclick   Script            ondblclick   Script            onmousedown   Script            onmouseup   Script            onmouseover   Script            onmousemove   Script            onmouseout   Script            onkeypress   Script            onkeydown   Script            onkeyup   Script            lang   LanguageCode            xml:lang   derived by: xs:language            documentation <div> <h3>lang (as an attribute name)</h3> <p>        denotes an attribute whose value        is a language code for the natural language of the content of        any element; its value is inherited.  This name is reserved        by virtue of its definition in the XML specification.</p> </div> <div> <h4>Notes</h4> <p>       Attempting to install the relevant ISO 2- and 3-letter       codes as the enumerated possible values is probably never       going to be a realistic possibility.       </p> <p>       See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">        http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>       and the IANA language subtag registry at       <a href="http://www.iana.org/assignments/language-subtag-registry">        http://www.iana.org/assignments/language-subtag-registry</a>       for further information.      </p> <p>       The union allows for the 'un-declaration' of xml:lang with       the empty string.      </p> </div> dir   derived by: xs:token   required
annotation	documentation       I18N BiDi over-ride
source	<xs:element name="bdo">   <xs:annotation>     <xs:documentation>       I18N BiDi over-ride       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="coreattrs"/>         <xs:attributeGroup ref="events"/>         <xs:attribute name="lang" type="LanguageCode"/>         <xs:attribute ref="xml:lang"/>         <xs:attribute name="dir" use="required">           <xs:simpleType>             <xs:restriction base="xs:token">               <xs:enumeration value="ltr"/>               <xs:enumeration value="rtl"/>             </xs:restriction>           </xs:simpleType>         </xs:attribute>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute bdo/@lang

type	LanguageCode
source	<xs:attribute name="lang" type="LanguageCode"/>

attribute bdo/@dir

type	restriction of xs:token
properties	use  required
facets	Kind  Value  Annotation enumeration  ltr enumeration  rtl
source	<xs:attribute name="dir" use="required">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="ltr"/>       <xs:enumeration value="rtl"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

element big

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       bigger font
source	<xs:element name="big">   <xs:annotation>     <xs:documentation>       bigger font       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element blockquote

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Flow
properties	content  complex mixed  true
children	p h1 h2 h3 h4 h5 h6 ul ol hr form br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation cite   URI
source	<xs:element name="blockquote">   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Flow">         <xs:attributeGroup ref="attrs"/>         <xs:attribute name="cite" type="URI"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute blockquote/@cite

type	URI
source	<xs:attribute name="cite" type="URI"/>

element body

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Flow
properties	content  complex mixed  true
children	p h1 h2 h3 h4 h5 h6 ul ol hr form br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation onload   Script            onunload   Script            background   URI            bgcolor   Color            text   Color            link   Color            vlink   Color            alink   Color
source	<xs:element name="body">   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Flow">         <xs:attributeGroup ref="attrs"/>         <xs:attribute name="onload" type="Script"/>         <xs:attribute name="onunload" type="Script"/>         <xs:attribute name="background" type="URI"/>         <xs:attribute name="bgcolor" type="Color"/>         <xs:attribute name="text" type="Color"/>         <xs:attribute name="link" type="Color"/>         <xs:attribute name="vlink" type="Color"/>         <xs:attribute name="alink" type="Color"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute body/@onload

type	Script
source	<xs:attribute name="onload" type="Script"/>

attribute body/@onunload

type	Script
source	<xs:attribute name="onunload" type="Script"/>

attribute body/@background

type	URI
source	<xs:attribute name="background" type="URI"/>

attribute body/@bgcolor

type	Color
facets	Kind  Value  Annotation pattern  [A-Za-z]+|#[0-9A-Fa-f]{3}|#[0-9A-Fa-f]{6}
source	<xs:attribute name="bgcolor" type="Color"/>

attribute body/@text

type	Color
facets	Kind  Value  Annotation pattern  [A-Za-z]+|#[0-9A-Fa-f]{3}|#[0-9A-Fa-f]{6}
source	<xs:attribute name="text" type="Color"/>

attribute body/@link

type	Color
facets	Kind  Value  Annotation pattern  [A-Za-z]+|#[0-9A-Fa-f]{3}|#[0-9A-Fa-f]{6}
source	<xs:attribute name="link" type="Color"/>

attribute body/@vlink

type	Color
facets	Kind  Value  Annotation pattern  [A-Za-z]+|#[0-9A-Fa-f]{3}|#[0-9A-Fa-f]{6}
source	<xs:attribute name="vlink" type="Color"/>

attribute body/@alink

type	Color
facets	Kind  Value  Annotation pattern  [A-Za-z]+|#[0-9A-Fa-f]{3}|#[0-9A-Fa-f]{6}
source	<xs:attribute name="alink" type="Color"/>

element br

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
attributes	Name   Type   Use   Default   Fixed   Annotation clear   derived by: xs:token      none
annotation	documentation       forced line break
source	<xs:element name="br">   <xs:annotation>     <xs:documentation>       forced line break       </xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:attributeGroup ref="coreattrs"/>     <xs:attribute name="clear" default="none">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="left"/>           <xs:enumeration value="all"/>           <xs:enumeration value="right"/>           <xs:enumeration value="none"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>   </xs:complexType> </xs:element>

attribute br/@clear

type	restriction of xs:token
properties	default  none
facets	Kind  Value  Annotation enumeration  left enumeration  all enumeration  right enumeration  none
source	<xs:attribute name="clear" default="none">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="left"/>       <xs:enumeration value="all"/>       <xs:enumeration value="right"/>       <xs:enumeration value="none"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

element button

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of button.content
properties	content  complex mixed  true
children	p h1 h2 h3 h4 h5 h6 div ul ol hr table br span bdo object applet img map i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation accesskey   Character            tabindex   tabindexNumber            onfocus   Script            onblur   Script            name               value               type   derived by: xs:token      submit      disabled   derived by: xs:token
annotation	documentation       Content is "Flow" excluding a, form and form controls
source	<xs:element name="button">   <xs:annotation>     <xs:documentation>       Content is "Flow" excluding a, form and form controls       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="button.content">         <xs:attributeGroup ref="attrs"/>         <xs:attributeGroup ref="focus"/>         <xs:attribute name="name"/>         <xs:attribute name="value"/>         <xs:attribute name="type" default="submit">           <xs:simpleType>             <xs:restriction base="xs:token">               <xs:enumeration value="button"/>               <xs:enumeration value="submit"/>               <xs:enumeration value="reset"/>             </xs:restriction>           </xs:simpleType>         </xs:attribute>         <xs:attribute name="disabled">           <xs:simpleType>             <xs:restriction base="xs:token">               <xs:enumeration value="disabled"/>             </xs:restriction>           </xs:simpleType>         </xs:attribute>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute button/@name

source

<xs:attribute name="name"/>

attribute button/@value

source

<xs:attribute name="value"/>

attribute button/@type

type	restriction of xs:token
properties	default  submit
facets	Kind  Value  Annotation enumeration  button enumeration  submit enumeration  reset
source	<xs:attribute name="type" default="submit">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="button"/>       <xs:enumeration value="submit"/>       <xs:enumeration value="reset"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute button/@disabled

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  disabled
source	<xs:attribute name="disabled">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="disabled"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

element caption

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation align   CAlign
source	<xs:element name="caption">   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>         <xs:attribute name="align" type="CAlign"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute caption/@align

type	CAlign
facets	Kind  Value  Annotation enumeration  top enumeration  bottom enumeration  left enumeration  right
source	<xs:attribute name="align" type="CAlign"/>

element center

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Flow
properties	content  complex mixed  true
children	p h1 h2 h3 h4 h5 h6 ul ol hr form br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       center content
source	<xs:element name="center">   <xs:annotation>     <xs:documentation>       center content       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Flow">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element cite

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       citation
source	<xs:element name="cite">   <xs:annotation>     <xs:documentation>       citation       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element code

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       program code
source	<xs:element name="code">   <xs:annotation>     <xs:documentation>       program code       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element col

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
attributes	Name   Type   Use   Default   Fixed   Annotation span   Number      1      width   MultiLength            align   derived by: xs:token            char   Character            charoff   Length            valign   derived by: xs:token
annotation	documentation       col elements define the alignment properties for cells in       one or more columns.       The width attribute specifies the width of the columns, e.g.           width=64        width in screen pixels           width=0.5*      relative width of 0.5       The span attribute causes the attributes of one       col element to apply to more than one column.
source	<xs:element name="col">   <xs:annotation>     <xs:documentation>       col elements define the alignment properties for cells in       one or more columns.       The width attribute specifies the width of the columns, e.g.           width=64        width in screen pixels           width=0.5*      relative width of 0.5       The span attribute causes the attributes of one       col element to apply to more than one column.       </xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:attributeGroup ref="attrs"/>     <xs:attribute name="span" type="Number" default="1"/>     <xs:attribute name="width" type="MultiLength"/>     <xs:attributeGroup ref="cellhalign"/>     <xs:attributeGroup ref="cellvalign"/>   </xs:complexType> </xs:element>

attribute col/@span

type	Number
properties	default  1
facets	Kind  Value  Annotation pattern  [0-9]+
source	<xs:attribute name="span" type="Number" default="1"/>

attribute col/@width

type	MultiLength
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)|[1-9]?(\d+)?\*
source	<xs:attribute name="width" type="MultiLength"/>

element colgroup

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
children	col
attributes	Name   Type   Use   Default   Fixed   Annotation span   Number      1      width   MultiLength            align   derived by: xs:token            char   Character            charoff   Length            valign   derived by: xs:token
annotation	documentation       colgroup groups a set of col elements. It allows you to group       several semantically related columns together.
source	<xs:element name="colgroup">   <xs:annotation>     <xs:documentation>       colgroup groups a set of col elements. It allows you to group       several semantically related columns together.       </xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:sequence>       <xs:element ref="col" minOccurs="0" maxOccurs="unbounded"/>     </xs:sequence>     <xs:attributeGroup ref="attrs"/>     <xs:attribute name="span" type="Number" default="1"/>     <xs:attribute name="width" type="MultiLength"/>     <xs:attributeGroup ref="cellhalign"/>     <xs:attributeGroup ref="cellvalign"/>   </xs:complexType> </xs:element>

attribute colgroup/@span

type	Number
properties	default  1
facets	Kind  Value  Annotation pattern  [0-9]+
source	<xs:attribute name="span" type="Number" default="1"/>

attribute colgroup/@width

type	MultiLength
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)|[1-9]?(\d+)?\*
source	<xs:attribute name="width" type="MultiLength"/>

element dd

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Flow
properties	content  complex mixed  true
children	p h1 h2 h3 h4 h5 h6 ul ol hr form br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
source	<xs:element name="dd">   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Flow">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element del

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Flow
properties	content  complex mixed  true
children	p h1 h2 h3 h4 h5 h6 ul ol hr form br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation cite   URI            datetime   Datetime
source	<xs:element name="del">   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Flow">         <xs:attributeGroup ref="attrs"/>         <xs:attribute name="cite" type="URI"/>         <xs:attribute name="datetime" type="Datetime"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute del/@cite

type	URI
source	<xs:attribute name="cite" type="URI"/>

attribute del/@datetime

type	Datetime
source	<xs:attribute name="datetime" type="Datetime"/>

element dfn

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       definitional
source	<xs:element name="dfn">   <xs:annotation>     <xs:documentation>       definitional       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element dir

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
children	li
attributes	Name   Type   Use   Default   Fixed   Annotation compact   derived by: xs:token
annotation	documentation       multiple column list (DEPRECATED)
source	<xs:element name="dir">   <xs:annotation>     <xs:documentation>       multiple column list (DEPRECATED)       </xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:sequence>       <xs:element ref="li" maxOccurs="unbounded"/>     </xs:sequence>     <xs:attributeGroup ref="attrs"/>     <xs:attribute name="compact">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="compact"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>   </xs:complexType> </xs:element>

attribute dir/@compact

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  compact
source	<xs:attribute name="compact">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="compact"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

element div

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Flow
properties	content  complex mixed  true
children	p h1 h2 h3 h4 h5 h6 ul ol hr form br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       generic language/style container
source	<xs:element name="div">   <xs:annotation>     <xs:documentation>       generic language/style container            </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Flow">         <xs:attributeGroup ref="attrs"/>         <xs:attributeGroup ref="TextAlign"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element dl

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
children	dt dd
attributes	Name   Type   Use   Default   Fixed   Annotation compact   derived by: xs:token
source	<xs:element name="dl">   <xs:complexType>     <xs:choice maxOccurs="unbounded">       <xs:element ref="dt"/>       <xs:element ref="dd"/>     </xs:choice>     <xs:attributeGroup ref="attrs"/>     <xs:attribute name="compact">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="compact"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>   </xs:complexType> </xs:element>

attribute dl/@compact

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  compact
source	<xs:attribute name="compact">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="compact"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

element dt

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
source	<xs:element name="dt">   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element em

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       emphasis
source	<xs:element name="em">   <xs:annotation>     <xs:documentation>       emphasis       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element fieldset

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex mixed  true
children	legend p h1 h2 h3 h4 h5 h6 ul ol hr form br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       The fieldset element is used to group form fields.       Only one legend element should occur in the content       and if present should only be preceded by whitespace.       NOTE: this content model is different from the XHTML 1.0 DTD,       closer to the intended content model in HTML4 DTD
source	<xs:element name="fieldset">   <xs:annotation>     <xs:documentation>       The fieldset element is used to group form fields.       Only one legend element should occur in the content       and if present should only be preceded by whitespace.       NOTE: this content model is different from the XHTML 1.0 DTD,       closer to the intended content model in HTML4 DTD       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:sequence>       <xs:element ref="legend"/>       <xs:choice minOccurs="0" maxOccurs="unbounded">         <xs:group ref="block"/>         <xs:element ref="form"/>         <xs:group ref="inline"/>         <xs:group ref="misc"/>       </xs:choice>     </xs:sequence>     <xs:attributeGroup ref="attrs"/>   </xs:complexType> </xs:element>

element font

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation lang   LanguageCode            xml:lang   derived by: xs:language            documentation <div> <h3>lang (as an attribute name)</h3> <p>        denotes an attribute whose value        is a language code for the natural language of the content of        any element; its value is inherited.  This name is reserved        by virtue of its definition in the XML specification.</p> </div> <div> <h4>Notes</h4> <p>       Attempting to install the relevant ISO 2- and 3-letter       codes as the enumerated possible values is probably never       going to be a realistic possibility.       </p> <p>       See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">        http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>       and the IANA language subtag registry at       <a href="http://www.iana.org/assignments/language-subtag-registry">        http://www.iana.org/assignments/language-subtag-registry</a>       for further information.      </p> <p>       The union allows for the 'un-declaration' of xml:lang with       the empty string.      </p> </div> dir   derived by: xs:token            size               color   Color            face
annotation	documentation       local change to font
source	<xs:element name="font">   <xs:annotation>     <xs:documentation>       local change to font       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="coreattrs"/>         <xs:attributeGroup ref="i18n"/>         <xs:attribute name="size"/>         <xs:attribute name="color" type="Color"/>         <xs:attribute name="face"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute font/@size

source

<xs:attribute name="size"/>

attribute font/@color

type	Color
facets	Kind  Value  Annotation pattern  [A-Za-z]+|#[0-9A-Fa-f]{3}|#[0-9A-Fa-f]{6}
source	<xs:attribute name="color" type="Color"/>

attribute font/@face

source

<xs:attribute name="face"/>

element form

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of form.content
properties	content  complex mixed  true
children	p h1 h2 h3 h4 h5 h6 ul ol hr br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation action   URI   required         method   derived by: xs:token      get      enctype   ContentType      application/x-www-form-urlencoded      onsubmit   Script            onreset   Script            accept   ContentTypes            accept-charset   Charsets            target   FrameTarget
source	<xs:element name="form">   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="form.content">         <xs:attributeGroup ref="attrs"/>         <xs:attribute name="action" type="URI" use="required"/>         <xs:attribute name="method" default="get">           <xs:simpleType>             <xs:restriction base="xs:token">               <xs:enumeration value="get"/>               <xs:enumeration value="post"/>             </xs:restriction>           </xs:simpleType>         </xs:attribute>         <xs:attribute name="enctype" type="ContentType" default="application/x-www-form-urlencoded"/>         <xs:attribute name="onsubmit" type="Script"/>         <xs:attribute name="onreset" type="Script"/>         <xs:attribute name="accept" type="ContentTypes"/>         <xs:attribute name="accept-charset" type="Charsets"/>         <xs:attribute name="target" type="FrameTarget"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute form/@action

type	URI
properties	use  required
source	<xs:attribute name="action" type="URI" use="required"/>

attribute form/@method

type	restriction of xs:token
properties	default  get
facets	Kind  Value  Annotation enumeration  get enumeration  post
source	<xs:attribute name="method" default="get">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="get"/>       <xs:enumeration value="post"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute form/@enctype

type	ContentType
properties	default  application/x-www-form-urlencoded
source	<xs:attribute name="enctype" type="ContentType" default="application/x-www-form-urlencoded"/>

attribute form/@onsubmit

type	Script
source	<xs:attribute name="onsubmit" type="Script"/>

attribute form/@onreset

type	Script
source	<xs:attribute name="onreset" type="Script"/>

attribute form/@accept

type	ContentTypes
source	<xs:attribute name="accept" type="ContentTypes"/>

attribute form/@accept-charset

type	Charsets
source	<xs:attribute name="accept-charset" type="Charsets"/>

attribute form/@target

type	FrameTarget
facets	Kind  Value  Annotation pattern  _(blank|self|parent|top)|[A-Za-z]\c*
source	<xs:attribute name="target" type="FrameTarget"/>

element h1

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
source	<xs:element name="h1">   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>         <xs:attributeGroup ref="TextAlign"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element h2

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
source	<xs:element name="h2">   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>         <xs:attributeGroup ref="TextAlign"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element h3

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
source	<xs:element name="h3">   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>         <xs:attributeGroup ref="TextAlign"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element h4

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
source	<xs:element name="h4">   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>         <xs:attributeGroup ref="TextAlign"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element h5

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
source	<xs:element name="h5">   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>         <xs:attributeGroup ref="TextAlign"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element h6

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
source	<xs:element name="h6">   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>         <xs:attributeGroup ref="TextAlign"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element head

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
children	script style meta link object isindex title base
attributes	Name   Type   Use   Default   Fixed   Annotation lang   LanguageCode            xml:lang   derived by: xs:language            documentation <div> <h3>lang (as an attribute name)</h3> <p>        denotes an attribute whose value        is a language code for the natural language of the content of        any element; its value is inherited.  This name is reserved        by virtue of its definition in the XML specification.</p> </div> <div> <h4>Notes</h4> <p>       Attempting to install the relevant ISO 2- and 3-letter       codes as the enumerated possible values is probably never       going to be a realistic possibility.       </p> <p>       See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">        http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>       and the IANA language subtag registry at       <a href="http://www.iana.org/assignments/language-subtag-registry">        http://www.iana.org/assignments/language-subtag-registry</a>       for further information.      </p> <p>       The union allows for the 'un-declaration' of xml:lang with       the empty string.      </p> </div> dir   derived by: xs:token            id   xs:ID            profile   URI
annotation	documentation       content model is "head.misc" combined with a single       title and an optional base element in any order
source	<xs:element name="head">   <xs:annotation>     <xs:documentation>       content model is "head.misc" combined with a single       title and an optional base element in any order       </xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:sequence>       <xs:group ref="head.misc"/>       <xs:choice>         <xs:sequence>           <xs:element ref="title"/>           <xs:group ref="head.misc"/>           <xs:sequence minOccurs="0">             <xs:element ref="base"/>             <xs:group ref="head.misc"/>           </xs:sequence>         </xs:sequence>         <xs:sequence>           <xs:element ref="base"/>           <xs:group ref="head.misc"/>           <xs:element ref="title"/>           <xs:group ref="head.misc"/>         </xs:sequence>       </xs:choice>     </xs:sequence>     <xs:attributeGroup ref="i18n"/>     <xs:attribute name="id" type="xs:ID"/>     <xs:attribute name="profile" type="URI"/>   </xs:complexType> </xs:element>

attribute head/@id

type	xs:ID
source	<xs:attribute name="id" type="xs:ID"/>

attribute head/@profile

type	URI
source	<xs:attribute name="profile" type="URI"/>

element hr

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
attributes	Name   Type   Use   Default   Fixed   Annotation align   derived by: xs:token            noshade   derived by: xs:token            size   Pixels            width   Length
source	<xs:element name="hr">   <xs:complexType>     <xs:attributeGroup ref="attrs"/>     <xs:attribute name="align">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="left"/>           <xs:enumeration value="center"/>           <xs:enumeration value="right"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute name="noshade">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="noshade"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute name="size" type="Pixels"/>     <xs:attribute name="width" type="Length"/>   </xs:complexType> </xs:element>

attribute hr/@align

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  left enumeration  center enumeration  right
source	<xs:attribute name="align">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="left"/>       <xs:enumeration value="center"/>       <xs:enumeration value="right"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute hr/@noshade

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  noshade
source	<xs:attribute name="noshade">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="noshade"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute hr/@size

type	Pixels
source	<xs:attribute name="size" type="Pixels"/>

attribute hr/@width

type	Length
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="width" type="Length"/>

element html

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
children	head body
attributes	Name   Type   Use   Default   Fixed   Annotation lang   LanguageCode            xml:lang   derived by: xs:language            documentation <div> <h3>lang (as an attribute name)</h3> <p>        denotes an attribute whose value        is a language code for the natural language of the content of        any element; its value is inherited.  This name is reserved        by virtue of its definition in the XML specification.</p> </div> <div> <h4>Notes</h4> <p>       Attempting to install the relevant ISO 2- and 3-letter       codes as the enumerated possible values is probably never       going to be a realistic possibility.       </p> <p>       See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">        http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>       and the IANA language subtag registry at       <a href="http://www.iana.org/assignments/language-subtag-registry">        http://www.iana.org/assignments/language-subtag-registry</a>       for further information.      </p> <p>       The union allows for the 'un-declaration' of xml:lang with       the empty string.      </p> </div> dir   derived by: xs:token            id   xs:ID
source	<xs:element name="html">   <xs:complexType>     <xs:sequence>       <xs:element ref="head"/>       <xs:element ref="body"/>     </xs:sequence>     <xs:attributeGroup ref="i18n"/>     <xs:attribute name="id" type="xs:ID"/>   </xs:complexType> </xs:element>

attribute html/@id

type	xs:ID
source	<xs:attribute name="id" type="xs:ID"/>

element i

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       italic font
source	<xs:element name="i">   <xs:annotation>     <xs:documentation>       italic font       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element iframe

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Flow
properties	content  complex mixed  true
children	p h1 h2 h3 h4 h5 h6 ul ol hr form br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation longdesc   URI            name   xs:NMTOKEN            src   URI            frameborder   derived by: xs:token      1      marginwidth   Pixels            marginheight   Pixels            scrolling   derived by: xs:token      auto      align   ImgAlign            height   Length            width   Length
annotation	documentation       inline subwindow
source	<xs:element name="iframe">   <xs:annotation>     <xs:documentation>       inline subwindow       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Flow">         <xs:attributeGroup ref="coreattrs"/>         <xs:attribute name="longdesc" type="URI"/>         <xs:attribute name="name" type="xs:NMTOKEN"/>         <xs:attribute name="src" type="URI"/>         <xs:attribute name="frameborder" default="1">           <xs:simpleType>             <xs:restriction base="xs:token">               <xs:enumeration value="1"/>               <xs:enumeration value="0"/>             </xs:restriction>           </xs:simpleType>         </xs:attribute>         <xs:attribute name="marginwidth" type="Pixels"/>         <xs:attribute name="marginheight" type="Pixels"/>         <xs:attribute name="scrolling" default="auto">           <xs:simpleType>             <xs:restriction base="xs:token">               <xs:enumeration value="yes"/>               <xs:enumeration value="no"/>               <xs:enumeration value="auto"/>             </xs:restriction>           </xs:simpleType>         </xs:attribute>         <xs:attribute name="align" type="ImgAlign"/>         <xs:attribute name="height" type="Length"/>         <xs:attribute name="width" type="Length"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute iframe/@longdesc

type	URI
source	<xs:attribute name="longdesc" type="URI"/>

attribute iframe/@name

type	xs:NMTOKEN
source	<xs:attribute name="name" type="xs:NMTOKEN"/>

attribute iframe/@src

type	URI
source	<xs:attribute name="src" type="URI"/>

attribute iframe/@frameborder

type	restriction of xs:token
properties	default  1
facets	Kind  Value  Annotation enumeration  1 enumeration  0
source	<xs:attribute name="frameborder" default="1">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="1"/>       <xs:enumeration value="0"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute iframe/@marginwidth

type	Pixels
source	<xs:attribute name="marginwidth" type="Pixels"/>

attribute iframe/@marginheight

type	Pixels
source	<xs:attribute name="marginheight" type="Pixels"/>

attribute iframe/@scrolling

type	restriction of xs:token
properties	default  auto
facets	Kind  Value  Annotation enumeration  yes enumeration  no enumeration  auto
source	<xs:attribute name="scrolling" default="auto">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="yes"/>       <xs:enumeration value="no"/>       <xs:enumeration value="auto"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute iframe/@align

type	ImgAlign
facets	Kind  Value  Annotation enumeration  top enumeration  middle enumeration  bottom enumeration  left enumeration  right
source	<xs:attribute name="align" type="ImgAlign"/>

attribute iframe/@height

type	Length
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="height" type="Length"/>

attribute iframe/@width

type	Length
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="width" type="Length"/>

element img

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
attributes	Name   Type   Use   Default   Fixed   Annotation src   URI   required         alt   Text   required         name   xs:NMTOKEN            longdesc   URI            height   Length            width   Length            usemap   URI            documentation           usemap points to a map element which may be in this document           or an external document, although the latter is not widely supported           ismap   derived by: xs:token            align   ImgAlign            border   Length            hspace   Pixels            vspace   Pixels
source	<xs:element name="img">   <xs:complexType>     <xs:attributeGroup ref="attrs"/>     <xs:attribute name="src" type="URI" use="required"/>     <xs:attribute name="alt" type="Text" use="required"/>     <xs:attribute name="name" type="xs:NMTOKEN"/>     <xs:attribute name="longdesc" type="URI"/>     <xs:attribute name="height" type="Length"/>     <xs:attribute name="width" type="Length"/>     <xs:attribute name="usemap" type="URI">       <xs:annotation>         <xs:documentation>           usemap points to a map element which may be in this document           or an external document, although the latter is not widely supported           </xs:documentation>       </xs:annotation>     </xs:attribute>     <xs:attribute name="ismap">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="ismap"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute name="align" type="ImgAlign"/>     <xs:attribute name="border" type="Length"/>     <xs:attribute name="hspace" type="Pixels"/>     <xs:attribute name="vspace" type="Pixels"/>   </xs:complexType> </xs:element>

attribute img/@src

type	URI
properties	use  required
source	<xs:attribute name="src" type="URI" use="required"/>

attribute img/@alt

type	Text
properties	use  required
source	<xs:attribute name="alt" type="Text" use="required"/>

attribute img/@name

type	xs:NMTOKEN
source	<xs:attribute name="name" type="xs:NMTOKEN"/>

attribute img/@longdesc

type	URI
source	<xs:attribute name="longdesc" type="URI"/>

attribute img/@height

type	Length
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="height" type="Length"/>

attribute img/@width

type	Length
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="width" type="Length"/>

attribute img/@usemap

type	URI
annotation	documentation           usemap points to a map element which may be in this document           or an external document, although the latter is not widely supported
source	<xs:attribute name="usemap" type="URI">   <xs:annotation>     <xs:documentation>           usemap points to a map element which may be in this document           or an external document, although the latter is not widely supported           </xs:documentation>   </xs:annotation> </xs:attribute>

attribute img/@ismap

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  ismap
source	<xs:attribute name="ismap">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="ismap"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute img/@align

type	ImgAlign
facets	Kind  Value  Annotation enumeration  top enumeration  middle enumeration  bottom enumeration  left enumeration  right
source	<xs:attribute name="align" type="ImgAlign"/>

attribute img/@border

type	Length
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="border" type="Length"/>

attribute img/@hspace

type	Pixels
source	<xs:attribute name="hspace" type="Pixels"/>

attribute img/@vspace

type	Pixels
source	<xs:attribute name="vspace" type="Pixels"/>

element input

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
attributes	Name   Type   Use   Default   Fixed   Annotation accesskey   Character            tabindex   tabindexNumber            onfocus   Script            onblur   Script            type   InputType      text      name               documentation           the name attribute is required for all but submit & reset           value               checked   derived by: xs:token            disabled   derived by: xs:token            readonly   derived by: xs:token            size               maxlength   Number            src   URI            alt               usemap   URI            onselect   Script            onchange   Script            accept   ContentTypes            align   ImgAlign
annotation	documentation       form control
source	<xs:element name="input">   <xs:annotation>     <xs:documentation>       form control       </xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:attributeGroup ref="attrs"/>     <xs:attributeGroup ref="focus"/>     <xs:attribute name="type" type="InputType" default="text"/>     <xs:attribute name="name">       <xs:annotation>         <xs:documentation>           the name attribute is required for all but submit &amp; reset           </xs:documentation>       </xs:annotation>     </xs:attribute>     <xs:attribute name="value"/>     <xs:attribute name="checked">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="checked"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute name="disabled">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="disabled"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute name="readonly">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="readonly"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute name="size"/>     <xs:attribute name="maxlength" type="Number"/>     <xs:attribute name="src" type="URI"/>     <xs:attribute name="alt"/>     <xs:attribute name="usemap" type="URI"/>     <xs:attribute name="onselect" type="Script"/>     <xs:attribute name="onchange" type="Script"/>     <xs:attribute name="accept" type="ContentTypes"/>     <xs:attribute name="align" type="ImgAlign"/>   </xs:complexType> </xs:element>

attribute input/@type

type	InputType
properties	default  text
facets	Kind  Value  Annotation enumeration  text enumeration  password enumeration  checkbox enumeration  radio enumeration  submit enumeration  reset enumeration  file enumeration  hidden enumeration  image enumeration  button
source	<xs:attribute name="type" type="InputType" default="text"/>

attribute input/@name

annotation	documentation           the name attribute is required for all but submit & reset
source	<xs:attribute name="name">   <xs:annotation>     <xs:documentation>           the name attribute is required for all but submit &amp; reset           </xs:documentation>   </xs:annotation> </xs:attribute>

attribute input/@value

source

<xs:attribute name="value"/>

attribute input/@checked

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  checked
source	<xs:attribute name="checked">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="checked"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute input/@disabled

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  disabled
source	<xs:attribute name="disabled">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="disabled"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute input/@readonly

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  readonly
source	<xs:attribute name="readonly">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="readonly"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute input/@size

source

<xs:attribute name="size"/>

attribute input/@maxlength

type	Number
facets	Kind  Value  Annotation pattern  [0-9]+
source	<xs:attribute name="maxlength" type="Number"/>

attribute input/@src

type	URI
source	<xs:attribute name="src" type="URI"/>

attribute input/@alt

source

<xs:attribute name="alt"/>

attribute input/@usemap

type	URI
source	<xs:attribute name="usemap" type="URI"/>

attribute input/@onselect

type	Script
source	<xs:attribute name="onselect" type="Script"/>

attribute input/@onchange

type	Script
source	<xs:attribute name="onchange" type="Script"/>

attribute input/@accept

type	ContentTypes
source	<xs:attribute name="accept" type="ContentTypes"/>

attribute input/@align

type	ImgAlign
facets	Kind  Value  Annotation enumeration  top enumeration  middle enumeration  bottom enumeration  left enumeration  right
source	<xs:attribute name="align" type="ImgAlign"/>

element ins

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Flow
properties	content  complex mixed  true
children	p h1 h2 h3 h4 h5 h6 ul ol hr form br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation cite   URI            datetime   Datetime
source	<xs:element name="ins">   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Flow">         <xs:attributeGroup ref="attrs"/>         <xs:attribute name="cite" type="URI"/>         <xs:attribute name="datetime" type="Datetime"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute ins/@cite

type	URI
source	<xs:attribute name="cite" type="URI"/>

attribute ins/@datetime

type	Datetime
source	<xs:attribute name="datetime" type="Datetime"/>

element isindex

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
attributes	Name   Type   Use   Default   Fixed   Annotation lang   LanguageCode            xml:lang   derived by: xs:language            documentation <div> <h3>lang (as an attribute name)</h3> <p>        denotes an attribute whose value        is a language code for the natural language of the content of        any element; its value is inherited.  This name is reserved        by virtue of its definition in the XML specification.</p> </div> <div> <h4>Notes</h4> <p>       Attempting to install the relevant ISO 2- and 3-letter       codes as the enumerated possible values is probably never       going to be a realistic possibility.       </p> <p>       See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">        http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>       and the IANA language subtag registry at       <a href="http://www.iana.org/assignments/language-subtag-registry">        http://www.iana.org/assignments/language-subtag-registry</a>       for further information.      </p> <p>       The union allows for the 'un-declaration' of xml:lang with       the empty string.      </p> </div> dir   derived by: xs:token            prompt   Text
annotation	documentation       single-line text input control (DEPRECATED)
source	<xs:element name="isindex">   <xs:annotation>     <xs:documentation>       single-line text input control (DEPRECATED)       </xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:attributeGroup ref="coreattrs"/>     <xs:attributeGroup ref="i18n"/>     <xs:attribute name="prompt" type="Text"/>   </xs:complexType> </xs:element>

attribute isindex/@prompt

type	Text
source	<xs:attribute name="prompt" type="Text"/>

element kbd

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       something user would type
source	<xs:element name="kbd">   <xs:annotation>     <xs:documentation>       something user would type       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element label

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation for   xs:IDREF            accesskey   Character            onfocus   Script            onblur   Script
annotation	documentation       Each label must not contain more than ONE field       Label elements shouldn't be nested.
source	<xs:element name="label">   <xs:annotation>     <xs:documentation>       Each label must not contain more than ONE field       Label elements shouldn't be nested.       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>         <xs:attribute name="for" type="xs:IDREF"/>         <xs:attribute name="accesskey" type="Character"/>         <xs:attribute name="onfocus" type="Script"/>         <xs:attribute name="onblur" type="Script"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute label/@for

type	xs:IDREF
source	<xs:attribute name="for" type="xs:IDREF"/>

attribute label/@accesskey

type	Character
source	<xs:attribute name="accesskey" type="Character"/>

attribute label/@onfocus

type	Script
source	<xs:attribute name="onfocus" type="Script"/>

attribute label/@onblur

type	Script
source	<xs:attribute name="onblur" type="Script"/>

element legend

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation accesskey   Character            align   LAlign
annotation	documentation       fieldset label
source	<xs:element name="legend">   <xs:annotation>     <xs:documentation>       fieldset label       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>         <xs:attribute name="accesskey" type="Character"/>         <xs:attribute name="align" type="LAlign"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute legend/@accesskey

type	Character
source	<xs:attribute name="accesskey" type="Character"/>

attribute legend/@align

type	LAlign
facets	Kind  Value  Annotation enumeration  top enumeration  bottom enumeration  left enumeration  right
source	<xs:attribute name="align" type="LAlign"/>

element li

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Flow
properties	content  complex mixed  true
children	p h1 h2 h3 h4 h5 h6 ul ol hr form br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation type   LIStyle            value   Number
annotation	documentation       list item
source	<xs:element name="li">   <xs:annotation>     <xs:documentation>       list item       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Flow">         <xs:attributeGroup ref="attrs"/>         <xs:attribute name="type" type="LIStyle"/>         <xs:attribute name="value" type="Number"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute li/@type

type	LIStyle
source	<xs:attribute name="type" type="LIStyle"/>

attribute li/@value

type	Number
facets	Kind  Value  Annotation pattern  [0-9]+
source	<xs:attribute name="value" type="Number"/>

element link

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
attributes	Name   Type   Use   Default   Fixed   Annotation charset   Charset            href   URI            hreflang   LanguageCode            type   ContentType            rel   LinkTypes            rev   LinkTypes            media   MediaDesc            target   FrameTarget
annotation	documentation       Relationship values can be used in principle:       a) for document specific toolbars/menus when used          with the link element in document head e.g.            start, contents, previous, next, index, end, help       b) to link to a separate style sheet (rel="stylesheet")       c) to make a link to a script (rel="script")       d) by stylesheets to control how collections of          html nodes are rendered into printed documents       e) to make a link to a printable version of this document          e.g. a PostScript or PDF version (rel="alternate" media="print")
source	<xs:element name="link">   <xs:annotation>     <xs:documentation>       Relationship values can be used in principle:       a) for document specific toolbars/menus when used          with the link element in document head e.g.            start, contents, previous, next, index, end, help       b) to link to a separate style sheet (rel="stylesheet")       c) to make a link to a script (rel="script")       d) by stylesheets to control how collections of          html nodes are rendered into printed documents       e) to make a link to a printable version of this document          e.g. a PostScript or PDF version (rel="alternate" media="print")       </xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:attributeGroup ref="attrs"/>     <xs:attribute name="charset" type="Charset"/>     <xs:attribute name="href" type="URI"/>     <xs:attribute name="hreflang" type="LanguageCode"/>     <xs:attribute name="type" type="ContentType"/>     <xs:attribute name="rel" type="LinkTypes"/>     <xs:attribute name="rev" type="LinkTypes"/>     <xs:attribute name="media" type="MediaDesc"/>     <xs:attribute name="target" type="FrameTarget"/>   </xs:complexType> </xs:element>

attribute link/@charset

type	Charset
source	<xs:attribute name="charset" type="Charset"/>

attribute link/@href

type	URI
source	<xs:attribute name="href" type="URI"/>

attribute link/@hreflang

type	LanguageCode
source	<xs:attribute name="hreflang" type="LanguageCode"/>

attribute link/@type

type	ContentType
source	<xs:attribute name="type" type="ContentType"/>

attribute link/@rel

type	LinkTypes
source	<xs:attribute name="rel" type="LinkTypes"/>

attribute link/@rev

type	LinkTypes
source	<xs:attribute name="rev" type="LinkTypes"/>

attribute link/@media

type	MediaDesc
facets	Kind  Value  Annotation pattern  [^,]+(,\s*[^,]+)*
source	<xs:attribute name="media" type="MediaDesc"/>

attribute link/@target

type	FrameTarget
facets	Kind  Value  Annotation pattern  _(blank|self|parent|top)|[A-Za-z]\c*
source	<xs:attribute name="target" type="FrameTarget"/>

element map

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
children	p h1 h2 h3 h4 h5 h6 ul ol hr form area
attributes	Name   Type   Use   Default   Fixed   Annotation lang   LanguageCode            xml:lang   derived by: xs:language            documentation <div> <h3>lang (as an attribute name)</h3> <p>        denotes an attribute whose value        is a language code for the natural language of the content of        any element; its value is inherited.  This name is reserved        by virtue of its definition in the XML specification.</p> </div> <div> <h4>Notes</h4> <p>       Attempting to install the relevant ISO 2- and 3-letter       codes as the enumerated possible values is probably never       going to be a realistic possibility.       </p> <p>       See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">        http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>       and the IANA language subtag registry at       <a href="http://www.iana.org/assignments/language-subtag-registry">        http://www.iana.org/assignments/language-subtag-registry</a>       for further information.      </p> <p>       The union allows for the 'un-declaration' of xml:lang with       the empty string.      </p> </div> dir   derived by: xs:token            onclick   Script            ondblclick   Script            onmousedown   Script            onmouseup   Script            onmouseover   Script            onmousemove   Script            onmouseout   Script            onkeypress   Script            onkeydown   Script            onkeyup   Script            id   xs:ID   required         class               style   StyleSheet            title   Text            name
source	<xs:element name="map">   <xs:complexType>     <xs:choice>       <xs:choice maxOccurs="unbounded">         <xs:group ref="block"/>         <xs:element ref="form"/>         <xs:group ref="misc"/>       </xs:choice>       <xs:element ref="area" maxOccurs="unbounded"/>     </xs:choice>     <xs:attributeGroup ref="i18n"/>     <xs:attributeGroup ref="events"/>     <xs:attribute name="id" type="xs:ID" use="required"/>     <xs:attribute name="class"/>     <xs:attribute name="style" type="StyleSheet"/>     <xs:attribute name="title" type="Text"/>     <xs:attribute name="name"/>   </xs:complexType> </xs:element>

attribute map/@id

type	xs:ID
properties	use  required
source	<xs:attribute name="id" type="xs:ID" use="required"/>

attribute map/@class

source

<xs:attribute name="class"/>

attribute map/@style

type	StyleSheet
source	<xs:attribute name="style" type="StyleSheet"/>

attribute map/@title

type	Text
source	<xs:attribute name="title" type="Text"/>

attribute map/@name

source

<xs:attribute name="name"/>

element menu

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
children	li
attributes	Name   Type   Use   Default   Fixed   Annotation compact   derived by: xs:token
annotation	documentation       single column list (DEPRECATED)
source	<xs:element name="menu">   <xs:annotation>     <xs:documentation>       single column list (DEPRECATED)       </xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:sequence>       <xs:element ref="li" maxOccurs="unbounded"/>     </xs:sequence>     <xs:attributeGroup ref="attrs"/>     <xs:attribute name="compact">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="compact"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>   </xs:complexType> </xs:element>

attribute menu/@compact

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  compact
source	<xs:attribute name="compact">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="compact"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

element meta

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
attributes	Name   Type   Use   Default   Fixed   Annotation lang   LanguageCode            xml:lang   derived by: xs:language            documentation <div> <h3>lang (as an attribute name)</h3> <p>        denotes an attribute whose value        is a language code for the natural language of the content of        any element; its value is inherited.  This name is reserved        by virtue of its definition in the XML specification.</p> </div> <div> <h4>Notes</h4> <p>       Attempting to install the relevant ISO 2- and 3-letter       codes as the enumerated possible values is probably never       going to be a realistic possibility.       </p> <p>       See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">        http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>       and the IANA language subtag registry at       <a href="http://www.iana.org/assignments/language-subtag-registry">        http://www.iana.org/assignments/language-subtag-registry</a>       for further information.      </p> <p>       The union allows for the 'un-declaration' of xml:lang with       the empty string.      </p> </div> dir   derived by: xs:token            id   xs:ID            http-equiv               name               content      required         scheme
annotation	documentation       generic metainformation
source	<xs:element name="meta">   <xs:annotation>     <xs:documentation>       generic metainformation       </xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:attributeGroup ref="i18n"/>     <xs:attribute name="id" type="xs:ID"/>     <xs:attribute name="http-equiv"/>     <xs:attribute name="name"/>     <xs:attribute name="content" use="required"/>     <xs:attribute name="scheme"/>   </xs:complexType> </xs:element>

attribute meta/@id

type	xs:ID
source	<xs:attribute name="id" type="xs:ID"/>

attribute meta/@http-equiv

source

<xs:attribute name="http-equiv"/>

attribute meta/@name

source

<xs:attribute name="name"/>

attribute meta/@content

properties	use  required
source	<xs:attribute name="content" use="required"/>

attribute meta/@scheme

source

<xs:attribute name="scheme"/>

element noframes

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Flow
properties	content  complex mixed  true
children	p h1 h2 h3 h4 h5 h6 ul ol hr form br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       alternate content container for non frame-based rendering
source	<xs:element name="noframes">   <xs:annotation>     <xs:documentation>       alternate content container for non frame-based rendering       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Flow">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element noscript

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Flow
properties	content  complex mixed  true
children	p h1 h2 h3 h4 h5 h6 ul ol hr form br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       alternate content container for non script-based rendering
source	<xs:element name="noscript">   <xs:annotation>     <xs:documentation>       alternate content container for non script-based rendering       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Flow">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element object

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex mixed  true
children	param p h1 h2 h3 h4 h5 h6 ul ol hr form br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation declare   derived by: xs:token            classid   URI            codebase   URI            data   URI            type   ContentType            codetype   ContentType            archive   UriList            standby   Text            height   Length            width   Length            usemap   URI            name   xs:NMTOKEN            tabindex   Number            align   ImgAlign            border   Pixels            hspace   Pixels            vspace   Pixels
source	<xs:element name="object">   <xs:complexType mixed="true">     <xs:choice minOccurs="0" maxOccurs="unbounded">       <xs:element ref="param"/>       <xs:group ref="block"/>       <xs:element ref="form"/>       <xs:group ref="inline"/>       <xs:group ref="misc"/>     </xs:choice>     <xs:attributeGroup ref="attrs"/>     <xs:attribute name="declare">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="declare"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute name="classid" type="URI"/>     <xs:attribute name="codebase" type="URI"/>     <xs:attribute name="data" type="URI"/>     <xs:attribute name="type" type="ContentType"/>     <xs:attribute name="codetype" type="ContentType"/>     <xs:attribute name="archive" type="UriList"/>     <xs:attribute name="standby" type="Text"/>     <xs:attribute name="height" type="Length"/>     <xs:attribute name="width" type="Length"/>     <xs:attribute name="usemap" type="URI"/>     <xs:attribute name="name" type="xs:NMTOKEN"/>     <xs:attribute name="tabindex" type="Number"/>     <xs:attribute name="align" type="ImgAlign"/>     <xs:attribute name="border" type="Pixels"/>     <xs:attribute name="hspace" type="Pixels"/>     <xs:attribute name="vspace" type="Pixels"/>   </xs:complexType> </xs:element>

attribute object/@declare

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  declare
source	<xs:attribute name="declare">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="declare"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute object/@classid

type	URI
source	<xs:attribute name="classid" type="URI"/>

attribute object/@codebase

type	URI
source	<xs:attribute name="codebase" type="URI"/>

attribute object/@data

type	URI
source	<xs:attribute name="data" type="URI"/>

attribute object/@type

type	ContentType
source	<xs:attribute name="type" type="ContentType"/>

attribute object/@codetype

type	ContentType
source	<xs:attribute name="codetype" type="ContentType"/>

attribute object/@archive

type	UriList
source	<xs:attribute name="archive" type="UriList"/>

attribute object/@standby

type	Text
source	<xs:attribute name="standby" type="Text"/>

attribute object/@height

type	Length
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="height" type="Length"/>

attribute object/@width

type	Length
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="width" type="Length"/>

attribute object/@usemap

type	URI
source	<xs:attribute name="usemap" type="URI"/>

attribute object/@name

type	xs:NMTOKEN
source	<xs:attribute name="name" type="xs:NMTOKEN"/>

attribute object/@tabindex

type	Number
facets	Kind  Value  Annotation pattern  [0-9]+
source	<xs:attribute name="tabindex" type="Number"/>

attribute object/@align

type	ImgAlign
facets	Kind  Value  Annotation enumeration  top enumeration  middle enumeration  bottom enumeration  left enumeration  right
source	<xs:attribute name="align" type="ImgAlign"/>

attribute object/@border

type	Pixels
source	<xs:attribute name="border" type="Pixels"/>

attribute object/@hspace

type	Pixels
source	<xs:attribute name="hspace" type="Pixels"/>

attribute object/@vspace

type	Pixels
source	<xs:attribute name="vspace" type="Pixels"/>

element ol

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
children	li
attributes	Name   Type   Use   Default   Fixed   Annotation type   OLStyle            compact   derived by: xs:token            start   Number
annotation	documentation       Ordered (numbered) list
source	<xs:element name="ol">   <xs:annotation>     <xs:documentation>       Ordered (numbered) list       </xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:sequence>       <xs:element ref="li" maxOccurs="unbounded"/>     </xs:sequence>     <xs:attributeGroup ref="attrs"/>     <xs:attribute name="type" type="OLStyle"/>     <xs:attribute name="compact">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="compact"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute name="start" type="Number"/>   </xs:complexType> </xs:element>

attribute ol/@type

type	OLStyle
source	<xs:attribute name="type" type="OLStyle"/>

attribute ol/@compact

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  compact
source	<xs:attribute name="compact">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="compact"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute ol/@start

type	Number
facets	Kind  Value  Annotation pattern  [0-9]+
source	<xs:attribute name="start" type="Number"/>

element optgroup

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
children	option
attributes	Name   Type   Use   Default   Fixed   Annotation disabled   derived by: xs:token            label   Text   required
annotation	documentation       option group
source	<xs:element name="optgroup">   <xs:annotation>     <xs:documentation>       option group       </xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:sequence>       <xs:element ref="option" maxOccurs="unbounded"/>     </xs:sequence>     <xs:attributeGroup ref="attrs"/>     <xs:attribute name="disabled">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="disabled"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute name="label" type="Text" use="required"/>   </xs:complexType> </xs:element>

attribute optgroup/@disabled

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  disabled
source	<xs:attribute name="disabled">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="disabled"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute optgroup/@label

type	Text
properties	use  required
source	<xs:attribute name="label" type="Text" use="required"/>

element option

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex mixed  true
attributes	Name   Type   Use   Default   Fixed   Annotation selected   derived by: xs:token            disabled   derived by: xs:token            label   Text            value
annotation	documentation       selectable choice
source	<xs:element name="option">   <xs:annotation>     <xs:documentation>       selectable choice       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:attributeGroup ref="attrs"/>     <xs:attribute name="selected">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="selected"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute name="disabled">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="disabled"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute name="label" type="Text"/>     <xs:attribute name="value"/>   </xs:complexType> </xs:element>

attribute option/@selected

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  selected
source	<xs:attribute name="selected">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="selected"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute option/@disabled

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  disabled
source	<xs:attribute name="disabled">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="disabled"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute option/@label

type	Text
source	<xs:attribute name="label" type="Text"/>

attribute option/@value

source

<xs:attribute name="value"/>

element p

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
source	<xs:element name="p">   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>         <xs:attributeGroup ref="TextAlign"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element param

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
attributes	Name   Type   Use   Default   Fixed   Annotation id   xs:ID            name      required         value               valuetype   derived by: xs:token      data      type   ContentType
annotation	documentation       param is used to supply a named property value.       In XML it would seem natural to follow RDF and support an       abbreviated syntax where the param elements are replaced       by attribute value pairs on the object start tag.
source	<xs:element name="param">   <xs:annotation>     <xs:documentation>       param is used to supply a named property value.       In XML it would seem natural to follow RDF and support an       abbreviated syntax where the param elements are replaced       by attribute value pairs on the object start tag.       </xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:attribute name="id" type="xs:ID"/>     <xs:attribute name="name" use="required"/>     <xs:attribute name="value"/>     <xs:attribute name="valuetype" default="data">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="data"/>           <xs:enumeration value="ref"/>           <xs:enumeration value="object"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute name="type" type="ContentType"/>   </xs:complexType> </xs:element>

attribute param/@id

type	xs:ID
source	<xs:attribute name="id" type="xs:ID"/>

attribute param/@name

properties	use  required
source	<xs:attribute name="name" use="required"/>

attribute param/@value

source

<xs:attribute name="value"/>

attribute param/@valuetype

type	restriction of xs:token
properties	default  data
facets	Kind  Value  Annotation enumeration  data enumeration  ref enumeration  object
source	<xs:attribute name="valuetype" default="data">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="data"/>       <xs:enumeration value="ref"/>       <xs:enumeration value="object"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute param/@type

type	ContentType
source	<xs:attribute name="type" type="ContentType"/>

element pre

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of pre.content
properties	content  complex mixed  true
children	a br i b u em strong input select textarea label button
attributes	Name   Type   Use   Default   Fixed   Annotation width   Number            xml:space   derived by: xs:NCName         preserve   documentation <div> <h3>space (as an attribute name)</h3> <p>        denotes an attribute whose        value is a keyword indicating what whitespace processing        discipline is intended for the content of the element; its        value is inherited.  This name is reserved by virtue of its        definition in the XML specification.</p> </div>
annotation	documentation       content is "Inline" excluding          "img|object|applet|big|small|sub|sup|font|basefont"
source	<xs:element name="pre">   <xs:annotation>     <xs:documentation>       content is "Inline" excluding          "img|object|applet|big|small|sub|sup|font|basefont"       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="pre.content">         <xs:attributeGroup ref="attrs"/>         <xs:attribute name="width" type="Number"/>         <xs:attribute ref="xml:space" fixed="preserve"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute pre/@width

type	Number
facets	Kind  Value  Annotation pattern  [0-9]+
source	<xs:attribute name="width" type="Number"/>

element q

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation cite   URI
annotation	documentation       inlined quote
source	<xs:element name="q">   <xs:annotation>     <xs:documentation>       inlined quote       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>         <xs:attribute name="cite" type="URI"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute q/@cite

type	URI
source	<xs:attribute name="cite" type="URI"/>

element s

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       strike-through
source	<xs:element name="s">   <xs:annotation>     <xs:documentation>       strike-through       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element samp

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       sample
source	<xs:element name="samp">   <xs:annotation>     <xs:documentation>       sample       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element script

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex mixed  true
attributes	Name   Type   Use   Default   Fixed   Annotation id   xs:ID            charset   Charset            type   ContentType   required         language               src   URI            defer   derived by: xs:token            xml:space   derived by: xs:NCName         preserve   documentation <div> <h3>space (as an attribute name)</h3> <p>        denotes an attribute whose        value is a keyword indicating what whitespace processing        discipline is intended for the content of the element; its        value is inherited.  This name is reserved by virtue of its        definition in the XML specification.</p> </div>
annotation	documentation       script statements, which may include CDATA sections
source	<xs:element name="script">   <xs:annotation>     <xs:documentation>       script statements, which may include CDATA sections       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:attribute name="id" type="xs:ID"/>     <xs:attribute name="charset" type="Charset"/>     <xs:attribute name="type" type="ContentType" use="required"/>     <xs:attribute name="language"/>     <xs:attribute name="src" type="URI"/>     <xs:attribute name="defer">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="defer"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute ref="xml:space" fixed="preserve"/>   </xs:complexType> </xs:element>

attribute script/@id

type	xs:ID
source	<xs:attribute name="id" type="xs:ID"/>

attribute script/@charset

type	Charset
source	<xs:attribute name="charset" type="Charset"/>

attribute script/@type

type	ContentType
properties	use  required
source	<xs:attribute name="type" type="ContentType" use="required"/>

attribute script/@language

source

<xs:attribute name="language"/>

attribute script/@src

type	URI
source	<xs:attribute name="src" type="URI"/>

attribute script/@defer

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  defer
source	<xs:attribute name="defer">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="defer"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

element select

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
children	optgroup option
attributes	Name   Type   Use   Default   Fixed   Annotation name               size   Number            multiple   derived by: xs:token            disabled   derived by: xs:token            tabindex   tabindexNumber            onfocus   Script            onblur   Script            onchange   Script
annotation	documentation       option selector
source	<xs:element name="select">   <xs:annotation>     <xs:documentation>       option selector       </xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:choice maxOccurs="unbounded">       <xs:element ref="optgroup"/>       <xs:element ref="option"/>     </xs:choice>     <xs:attributeGroup ref="attrs"/>     <xs:attribute name="name"/>     <xs:attribute name="size" type="Number"/>     <xs:attribute name="multiple">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="multiple"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute name="disabled">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="disabled"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute name="tabindex" type="tabindexNumber"/>     <xs:attribute name="onfocus" type="Script"/>     <xs:attribute name="onblur" type="Script"/>     <xs:attribute name="onchange" type="Script"/>   </xs:complexType> </xs:element>

attribute select/@name

source

<xs:attribute name="name"/>

attribute select/@size

type	Number
facets	Kind  Value  Annotation pattern  [0-9]+
source	<xs:attribute name="size" type="Number"/>

attribute select/@multiple

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  multiple
source	<xs:attribute name="multiple">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="multiple"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute select/@disabled

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  disabled
source	<xs:attribute name="disabled">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="disabled"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute select/@tabindex

type	tabindexNumber
facets	Kind  Value  Annotation pattern  [0-9]+
source	<xs:attribute name="tabindex" type="tabindexNumber"/>

attribute select/@onfocus

type	Script
source	<xs:attribute name="onfocus" type="Script"/>

attribute select/@onblur

type	Script
source	<xs:attribute name="onblur" type="Script"/>

attribute select/@onchange

type	Script
source	<xs:attribute name="onchange" type="Script"/>

element small

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       smaller font
source	<xs:element name="small">   <xs:annotation>     <xs:documentation>       smaller font       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element span

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       generic language/style container
source	<xs:element name="span">   <xs:annotation>     <xs:documentation>       generic language/style container       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element strike

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       strike-through
source	<xs:element name="strike">   <xs:annotation>     <xs:documentation>       strike-through       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element strong

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       strong emphasis
source	<xs:element name="strong">   <xs:annotation>     <xs:documentation>       strong emphasis       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element style

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex mixed  true
attributes	Name   Type   Use   Default   Fixed   Annotation lang   LanguageCode            xml:lang   derived by: xs:language            documentation <div> <h3>lang (as an attribute name)</h3> <p>        denotes an attribute whose value        is a language code for the natural language of the content of        any element; its value is inherited.  This name is reserved        by virtue of its definition in the XML specification.</p> </div> <div> <h4>Notes</h4> <p>       Attempting to install the relevant ISO 2- and 3-letter       codes as the enumerated possible values is probably never       going to be a realistic possibility.       </p> <p>       See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">        http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>       and the IANA language subtag registry at       <a href="http://www.iana.org/assignments/language-subtag-registry">        http://www.iana.org/assignments/language-subtag-registry</a>       for further information.      </p> <p>       The union allows for the 'un-declaration' of xml:lang with       the empty string.      </p> </div> dir   derived by: xs:token            id   xs:ID            type   ContentType   required         media   MediaDesc            title   Text            xml:space   derived by: xs:NCName         preserve   documentation <div> <h3>space (as an attribute name)</h3> <p>        denotes an attribute whose        value is a keyword indicating what whitespace processing        discipline is intended for the content of the element; its        value is inherited.  This name is reserved by virtue of its        definition in the XML specification.</p> </div>
annotation	documentation       style info, which may include CDATA sections
source	<xs:element name="style">   <xs:annotation>     <xs:documentation>       style info, which may include CDATA sections       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:attributeGroup ref="i18n"/>     <xs:attribute name="id" type="xs:ID"/>     <xs:attribute name="type" type="ContentType" use="required"/>     <xs:attribute name="media" type="MediaDesc"/>     <xs:attribute name="title" type="Text"/>     <xs:attribute ref="xml:space" fixed="preserve"/>   </xs:complexType> </xs:element>

attribute style/@id

type	xs:ID
source	<xs:attribute name="id" type="xs:ID"/>

attribute style/@type

type	ContentType
properties	use  required
source	<xs:attribute name="type" type="ContentType" use="required"/>

attribute style/@media

type	MediaDesc
facets	Kind  Value  Annotation pattern  [^,]+(,\s*[^,]+)*
source	<xs:attribute name="media" type="MediaDesc"/>

attribute style/@title

type	Text
source	<xs:attribute name="title" type="Text"/>

element sub

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       subscript
source	<xs:element name="sub">   <xs:annotation>     <xs:documentation>       subscript       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element sup

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       superscript
source	<xs:element name="sup">   <xs:annotation>     <xs:documentation>       superscript       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element table

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
children	caption col colgroup thead tfoot tbody tr
attributes	Name   Type   Use   Default   Fixed   Annotation summary   Text            width   Length            border   Pixels            frame   TFrame            rules   TRules            cellspacing   Length            cellpadding   Length            align   TAlign            bgcolor   Color
source	<xs:element name="table">   <xs:complexType>     <xs:sequence>       <xs:element ref="caption" minOccurs="0"/>       <xs:choice>         <xs:element ref="col" minOccurs="0" maxOccurs="unbounded"/>         <xs:element ref="colgroup" minOccurs="0" maxOccurs="unbounded"/>       </xs:choice>       <xs:element ref="thead" minOccurs="0"/>       <xs:element ref="tfoot" minOccurs="0"/>       <xs:choice>         <xs:element ref="tbody" maxOccurs="unbounded"/>         <xs:element ref="tr" maxOccurs="unbounded"/>       </xs:choice>     </xs:sequence>     <xs:attributeGroup ref="attrs"/>     <xs:attribute name="summary" type="Text"/>     <xs:attribute name="width" type="Length"/>     <xs:attribute name="border" type="Pixels"/>     <xs:attribute name="frame" type="TFrame"/>     <xs:attribute name="rules" type="TRules"/>     <xs:attribute name="cellspacing" type="Length"/>     <xs:attribute name="cellpadding" type="Length"/>     <xs:attribute name="align" type="TAlign"/>     <xs:attribute name="bgcolor" type="Color"/>   </xs:complexType> </xs:element>

attribute table/@summary

type	Text
source	<xs:attribute name="summary" type="Text"/>

attribute table/@width

type	Length
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="width" type="Length"/>

attribute table/@border

type	Pixels
source	<xs:attribute name="border" type="Pixels"/>

attribute table/@frame

type	TFrame
facets	Kind  Value  Annotation enumeration  void enumeration  above enumeration  below enumeration  hsides enumeration  lhs enumeration  rhs enumeration  vsides enumeration  box enumeration  border
source	<xs:attribute name="frame" type="TFrame"/>

attribute table/@rules

type	TRules
facets	Kind  Value  Annotation enumeration  none enumeration  groups enumeration  rows enumeration  cols enumeration  all
source	<xs:attribute name="rules" type="TRules"/>

attribute table/@cellspacing

type	Length
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="cellspacing" type="Length"/>

attribute table/@cellpadding

type	Length
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="cellpadding" type="Length"/>

attribute table/@align

type	TAlign
facets	Kind  Value  Annotation enumeration  left enumeration  center enumeration  right
source	<xs:attribute name="align" type="TAlign"/>

attribute table/@bgcolor

type	Color
facets	Kind  Value  Annotation pattern  [A-Za-z]+|#[0-9A-Fa-f]{3}|#[0-9A-Fa-f]{6}
source	<xs:attribute name="bgcolor" type="Color"/>

element tbody

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
children	tr
attributes	Name   Type   Use   Default   Fixed   Annotation align   derived by: xs:token            char   Character            charoff   Length            valign   derived by: xs:token
source	<xs:element name="tbody">   <xs:complexType>     <xs:sequence>       <xs:element ref="tr" maxOccurs="unbounded"/>     </xs:sequence>     <xs:attributeGroup ref="attrs"/>     <xs:attributeGroup ref="cellhalign"/>     <xs:attributeGroup ref="cellvalign"/>   </xs:complexType> </xs:element>

element td

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Flow
properties	content  complex mixed  true
children	p h1 h2 h3 h4 h5 h6 ul ol hr form br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation abbr   Text            axis               headers   xs:IDREFS            scope   Scope            rowspan   Number      1      colspan   Number      1      align   derived by: xs:token            char   Character            charoff   Length            valign   derived by: xs:token            nowrap   derived by: xs:token            bgcolor   Color            width   Length            height   Length
source	<xs:element name="td">   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Flow">         <xs:attributeGroup ref="attrs"/>         <xs:attribute name="abbr" type="Text"/>         <xs:attribute name="axis"/>         <xs:attribute name="headers" type="xs:IDREFS"/>         <xs:attribute name="scope" type="Scope"/>         <xs:attribute name="rowspan" type="Number" default="1"/>         <xs:attribute name="colspan" type="Number" default="1"/>         <xs:attributeGroup ref="cellhalign"/>         <xs:attributeGroup ref="cellvalign"/>         <xs:attribute name="nowrap">           <xs:simpleType>             <xs:restriction base="xs:token">               <xs:enumeration value="nowrap"/>             </xs:restriction>           </xs:simpleType>         </xs:attribute>         <xs:attribute name="bgcolor" type="Color"/>         <xs:attribute name="width" type="Length"/>         <xs:attribute name="height" type="Length"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute td/@abbr

type	Text
source	<xs:attribute name="abbr" type="Text"/>

attribute td/@axis

source

<xs:attribute name="axis"/>

attribute td/@headers

type	xs:IDREFS
source	<xs:attribute name="headers" type="xs:IDREFS"/>

attribute td/@scope

type	Scope
facets	Kind  Value  Annotation enumeration  row enumeration  col enumeration  rowgroup enumeration  colgroup
source	<xs:attribute name="scope" type="Scope"/>

attribute td/@rowspan

type	Number
properties	default  1
facets	Kind  Value  Annotation pattern  [0-9]+
source	<xs:attribute name="rowspan" type="Number" default="1"/>

attribute td/@colspan

type	Number
properties	default  1
facets	Kind  Value  Annotation pattern  [0-9]+
source	<xs:attribute name="colspan" type="Number" default="1"/>

attribute td/@nowrap

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  nowrap
source	<xs:attribute name="nowrap">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="nowrap"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute td/@bgcolor

type	Color
facets	Kind  Value  Annotation pattern  [A-Za-z]+|#[0-9A-Fa-f]{3}|#[0-9A-Fa-f]{6}
source	<xs:attribute name="bgcolor" type="Color"/>

attribute td/@width

type	Length
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="width" type="Length"/>

attribute td/@height

type	Length
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="height" type="Length"/>

element textarea

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex mixed  true
attributes	Name   Type   Use   Default   Fixed   Annotation accesskey   Character            tabindex   tabindexNumber            onfocus   Script            onblur   Script            name               rows   Number   required         cols   Number   required         disabled   derived by: xs:token            readonly   derived by: xs:token            onselect   Script            onchange   Script
annotation	documentation       multi-line text field
source	<xs:element name="textarea">   <xs:annotation>     <xs:documentation>       multi-line text field       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:attributeGroup ref="attrs"/>     <xs:attributeGroup ref="focus"/>     <xs:attribute name="name"/>     <xs:attribute name="rows" type="Number" use="required"/>     <xs:attribute name="cols" type="Number" use="required"/>     <xs:attribute name="disabled">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="disabled"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute name="readonly">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="readonly"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>     <xs:attribute name="onselect" type="Script"/>     <xs:attribute name="onchange" type="Script"/>   </xs:complexType> </xs:element>

attribute textarea/@name

source

<xs:attribute name="name"/>

attribute textarea/@rows

type	Number
properties	use  required
facets	Kind  Value  Annotation pattern  [0-9]+
source	<xs:attribute name="rows" type="Number" use="required"/>

attribute textarea/@cols

type	Number
properties	use  required
facets	Kind  Value  Annotation pattern  [0-9]+
source	<xs:attribute name="cols" type="Number" use="required"/>

attribute textarea/@disabled

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  disabled
source	<xs:attribute name="disabled">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="disabled"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute textarea/@readonly

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  readonly
source	<xs:attribute name="readonly">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="readonly"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute textarea/@onselect

type	Script
source	<xs:attribute name="onselect" type="Script"/>

attribute textarea/@onchange

type	Script
source	<xs:attribute name="onchange" type="Script"/>

element tfoot

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
children	tr
attributes	Name   Type   Use   Default   Fixed   Annotation align   derived by: xs:token            char   Character            charoff   Length            valign   derived by: xs:token
source	<xs:element name="tfoot">   <xs:complexType>     <xs:sequence>       <xs:element ref="tr" maxOccurs="unbounded"/>     </xs:sequence>     <xs:attributeGroup ref="attrs"/>     <xs:attributeGroup ref="cellhalign"/>     <xs:attributeGroup ref="cellvalign"/>   </xs:complexType> </xs:element>

element th

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Flow
properties	content  complex mixed  true
children	p h1 h2 h3 h4 h5 h6 ul ol hr form br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation abbr   Text            axis               headers   xs:IDREFS            scope   Scope            rowspan   Number      1      colspan   Number      1      align   derived by: xs:token            char   Character            charoff   Length            valign   derived by: xs:token            nowrap   derived by: xs:token            bgcolor   Color            width   Length            height   Length
source	<xs:element name="th">   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Flow">         <xs:attributeGroup ref="attrs"/>         <xs:attribute name="abbr" type="Text"/>         <xs:attribute name="axis"/>         <xs:attribute name="headers" type="xs:IDREFS"/>         <xs:attribute name="scope" type="Scope"/>         <xs:attribute name="rowspan" type="Number" default="1"/>         <xs:attribute name="colspan" type="Number" default="1"/>         <xs:attributeGroup ref="cellhalign"/>         <xs:attributeGroup ref="cellvalign"/>         <xs:attribute name="nowrap">           <xs:simpleType>             <xs:restriction base="xs:token">               <xs:enumeration value="nowrap"/>             </xs:restriction>           </xs:simpleType>         </xs:attribute>         <xs:attribute name="bgcolor" type="Color"/>         <xs:attribute name="width" type="Length"/>         <xs:attribute name="height" type="Length"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

attribute th/@abbr

type	Text
source	<xs:attribute name="abbr" type="Text"/>

attribute th/@axis

source

<xs:attribute name="axis"/>

attribute th/@headers

type	xs:IDREFS
source	<xs:attribute name="headers" type="xs:IDREFS"/>

attribute th/@scope

type	Scope
facets	Kind  Value  Annotation enumeration  row enumeration  col enumeration  rowgroup enumeration  colgroup
source	<xs:attribute name="scope" type="Scope"/>

attribute th/@rowspan

type	Number
properties	default  1
facets	Kind  Value  Annotation pattern  [0-9]+
source	<xs:attribute name="rowspan" type="Number" default="1"/>

attribute th/@colspan

type	Number
properties	default  1
facets	Kind  Value  Annotation pattern  [0-9]+
source	<xs:attribute name="colspan" type="Number" default="1"/>

attribute th/@nowrap

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  nowrap
source	<xs:attribute name="nowrap">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="nowrap"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute th/@bgcolor

type	Color
facets	Kind  Value  Annotation pattern  [A-Za-z]+|#[0-9A-Fa-f]{3}|#[0-9A-Fa-f]{6}
source	<xs:attribute name="bgcolor" type="Color"/>

attribute th/@width

type	Length
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="width" type="Length"/>

attribute th/@height

type	Length
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="height" type="Length"/>

element thead

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
children	tr
attributes	Name   Type   Use   Default   Fixed   Annotation align   derived by: xs:token            char   Character            charoff   Length            valign   derived by: xs:token
source	<xs:element name="thead">   <xs:complexType>     <xs:sequence>       <xs:element ref="tr" maxOccurs="unbounded"/>     </xs:sequence>     <xs:attributeGroup ref="attrs"/>     <xs:attributeGroup ref="cellhalign"/>     <xs:attributeGroup ref="cellvalign"/>   </xs:complexType> </xs:element>

element title

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex mixed  true
attributes	Name   Type   Use   Default   Fixed   Annotation lang   LanguageCode            xml:lang   derived by: xs:language            documentation <div> <h3>lang (as an attribute name)</h3> <p>        denotes an attribute whose value        is a language code for the natural language of the content of        any element; its value is inherited.  This name is reserved        by virtue of its definition in the XML specification.</p> </div> <div> <h4>Notes</h4> <p>       Attempting to install the relevant ISO 2- and 3-letter       codes as the enumerated possible values is probably never       going to be a realistic possibility.       </p> <p>       See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">        http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>       and the IANA language subtag registry at       <a href="http://www.iana.org/assignments/language-subtag-registry">        http://www.iana.org/assignments/language-subtag-registry</a>       for further information.      </p> <p>       The union allows for the 'un-declaration' of xml:lang with       the empty string.      </p> </div> dir   derived by: xs:token            id   xs:ID
annotation	documentation       The title element is not considered part of the flow of text.       It should be displayed, for example as the page header or       window title. Exactly one title is required per document.
source	<xs:element name="title">   <xs:annotation>     <xs:documentation>       The title element is not considered part of the flow of text.       It should be displayed, for example as the page header or       window title. Exactly one title is required per document.       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:attributeGroup ref="i18n"/>     <xs:attribute name="id" type="xs:ID"/>   </xs:complexType> </xs:element>

attribute title/@id

type	xs:ID
source	<xs:attribute name="id" type="xs:ID"/>

element tr

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
children	th td
attributes	Name   Type   Use   Default   Fixed   Annotation align   derived by: xs:token            char   Character            charoff   Length            valign   derived by: xs:token            bgcolor   Color
source	<xs:element name="tr">   <xs:complexType>     <xs:choice maxOccurs="unbounded">       <xs:element ref="th"/>       <xs:element ref="td"/>     </xs:choice>     <xs:attributeGroup ref="attrs"/>     <xs:attributeGroup ref="cellhalign"/>     <xs:attributeGroup ref="cellvalign"/>     <xs:attribute name="bgcolor" type="Color"/>   </xs:complexType> </xs:element>

attribute tr/@bgcolor

type	Color
facets	Kind  Value  Annotation pattern  [A-Za-z]+|#[0-9A-Fa-f]{3}|#[0-9A-Fa-f]{6}
source	<xs:attribute name="bgcolor" type="Color"/>

element tt

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       fixed pitch font
source	<xs:element name="tt">   <xs:annotation>     <xs:documentation>       fixed pitch font       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element u

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       underline
source	<xs:element name="u">   <xs:annotation>     <xs:documentation>       underline       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

element ul

diagram
namespace	http://www.w3.org/1999/xhtml
properties	content  complex
children	li
attributes	Name   Type   Use   Default   Fixed   Annotation type   ULStyle            compact   derived by: xs:token
annotation	documentation       Unordered list
source	<xs:element name="ul">   <xs:annotation>     <xs:documentation>       Unordered list       </xs:documentation>   </xs:annotation>   <xs:complexType>     <xs:sequence>       <xs:element ref="li" maxOccurs="unbounded"/>     </xs:sequence>     <xs:attributeGroup ref="attrs"/>     <xs:attribute name="type" type="ULStyle"/>     <xs:attribute name="compact">       <xs:simpleType>         <xs:restriction base="xs:token">           <xs:enumeration value="compact"/>         </xs:restriction>       </xs:simpleType>     </xs:attribute>   </xs:complexType> </xs:element>

attribute ul/@type

type	ULStyle
facets	Kind  Value  Annotation enumeration  disc enumeration  square enumeration  circle
source	<xs:attribute name="type" type="ULStyle"/>

attribute ul/@compact

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  compact
source	<xs:attribute name="compact">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="compact"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

element var

diagram
namespace	http://www.w3.org/1999/xhtml
type	extension of Inline
properties	content  complex mixed  true
children	br i b u em strong
attributes	Name   Type   Use   Default   Fixed   Annotation
annotation	documentation       variable
source	<xs:element name="var">   <xs:annotation>     <xs:documentation>       variable       </xs:documentation>   </xs:annotation>   <xs:complexType mixed="true">     <xs:complexContent>       <xs:extension base="Inline">         <xs:attributeGroup ref="attrs"/>       </xs:extension>     </xs:complexContent>   </xs:complexType> </xs:element>

group block

diagram
namespace	http://www.w3.org/1999/xhtml
children	p h1 h2 h3 h4 h5 h6 div ul ol hr isindex fieldset table
source	<xs:group name="block">   <xs:choice>     <xs:element ref="p"/>     <xs:group ref="heading"/>     <xs:element ref="div"/>     <xs:group ref="lists"/>     <xs:group ref="blocktext"/>     <xs:element ref="isindex"/>     <xs:element ref="fieldset"/>     <xs:element ref="table"/>   </xs:choice> </xs:group>

group blocktext

diagram
namespace	http://www.w3.org/1999/xhtml
children	pre hr blockquote address center noframes
source	<xs:group name="blocktext">   <xs:choice>     <xs:element ref="pre"/>     <xs:element ref="hr"/>     <xs:element ref="blockquote"/>     <xs:element ref="address"/>     <xs:element ref="center"/>     <xs:element ref="noframes"/>   </xs:choice> </xs:group>

group fontstyle

diagram
namespace	http://www.w3.org/1999/xhtml
children	i b u big small font basefont
source	<xs:group name="fontstyle">   <xs:choice>     <xs:group ref="fontstyle.basic"/>     <xs:group ref="fontstyle.extra"/>   </xs:choice> </xs:group>

group fontstyle.basic

diagram
namespace	http://www.w3.org/1999/xhtml
children	tt i b u s strike
source	<xs:group name="fontstyle.basic">   <xs:choice>     <xs:element ref="tt"/>     <xs:element ref="i"/>     <xs:element ref="b"/>     <xs:element ref="u"/>     <xs:element ref="s"/>     <xs:element ref="strike"/>   </xs:choice> </xs:group>

group fontstyle.extra

diagram
namespace	http://www.w3.org/1999/xhtml
children	big small font basefont
source	<xs:group name="fontstyle.extra">   <xs:choice>     <xs:element ref="big"/>     <xs:element ref="small"/>     <xs:element ref="font"/>     <xs:element ref="basefont"/>   </xs:choice> </xs:group>

group head.misc

diagram
namespace	http://www.w3.org/1999/xhtml
children	script style meta link object isindex
source	<xs:group name="head.misc">   <xs:sequence>     <xs:choice minOccurs="0" maxOccurs="unbounded">       <xs:element ref="script"/>       <xs:element ref="style"/>       <xs:element ref="meta"/>       <xs:element ref="link"/>       <xs:element ref="object"/>       <xs:element ref="isindex"/>     </xs:choice>   </xs:sequence> </xs:group>

group heading

diagram
namespace	http://www.w3.org/1999/xhtml
children	h1 h2 h3 h4 h5 h6
source	<xs:group name="heading">   <xs:choice>     <xs:element ref="h1"/>     <xs:element ref="h2"/>     <xs:element ref="h3"/>     <xs:element ref="h4"/>     <xs:element ref="h5"/>     <xs:element ref="h6"/>   </xs:choice> </xs:group>

group inline

diagram
namespace	http://www.w3.org/1999/xhtml
children	a br i b u em strong input select textarea label button
source	<xs:group name="inline">   <xs:choice>     <xs:element ref="a"/>     <xs:group ref="special"/>     <xs:group ref="fontstyle"/>     <xs:group ref="phrase"/>     <xs:group ref="inline.forms"/>   </xs:choice> </xs:group>

group inline.forms

diagram
namespace	http://www.w3.org/1999/xhtml
children	input select textarea label button
source	<xs:group name="inline.forms">   <xs:choice>     <xs:element ref="input"/>     <xs:element ref="select"/>     <xs:element ref="textarea"/>     <xs:element ref="label"/>     <xs:element ref="button"/>   </xs:choice> </xs:group>

group lists

diagram
namespace	http://www.w3.org/1999/xhtml
children	ul ol dl menu dir
source	<xs:group name="lists">   <xs:choice>     <xs:element ref="ul"/>     <xs:element ref="ol"/>     <xs:element ref="dl"/>     <xs:element ref="menu"/>     <xs:element ref="dir"/>   </xs:choice> </xs:group>

group misc

diagram
namespace	http://www.w3.org/1999/xhtml
children	noscript
annotation	documentation       these can only occur at block level
source	<xs:group name="misc">   <xs:annotation>     <xs:documentation>       these can only occur at block level       </xs:documentation>   </xs:annotation>   <xs:choice>     <xs:element ref="noscript"/>     <xs:group ref="misc.inline"/>   </xs:choice> </xs:group>

group misc.inline

diagram
namespace	http://www.w3.org/1999/xhtml
children	ins del script
annotation	documentation       these can only occur at block level
source	<xs:group name="misc.inline">   <xs:annotation>     <xs:documentation>       these can only occur at block level       </xs:documentation>   </xs:annotation>   <xs:choice>     <xs:element ref="ins"/>     <xs:element ref="del"/>     <xs:element ref="script"/>   </xs:choice> </xs:group>

group phrase

diagram
namespace	http://www.w3.org/1999/xhtml
children	em strong sub sup
source	<xs:group name="phrase">   <xs:choice>     <xs:group ref="phrase.basic"/>     <xs:group ref="phrase.extra"/>   </xs:choice> </xs:group>

group phrase.basic

diagram
namespace	http://www.w3.org/1999/xhtml
children	em strong dfn code q samp kbd var cite abbr acronym
source	<xs:group name="phrase.basic">   <xs:choice>     <xs:element ref="em"/>     <xs:element ref="strong"/>     <xs:element ref="dfn"/>     <xs:element ref="code"/>     <xs:element ref="q"/>     <xs:element ref="samp"/>     <xs:element ref="kbd"/>     <xs:element ref="var"/>     <xs:element ref="cite"/>     <xs:element ref="abbr"/>     <xs:element ref="acronym"/>   </xs:choice> </xs:group>

group phrase.extra

diagram
namespace	http://www.w3.org/1999/xhtml
children	sub sup
source	<xs:group name="phrase.extra">   <xs:choice>     <xs:element ref="sub"/>     <xs:element ref="sup"/>   </xs:choice> </xs:group>

group special

diagram
namespace	http://www.w3.org/1999/xhtml
children	br object applet img map iframe
source	<xs:group name="special">   <xs:choice>     <xs:group ref="special.basic"/>     <xs:group ref="special.extra"/>   </xs:choice> </xs:group>

group special.basic

diagram
namespace	http://www.w3.org/1999/xhtml
children	br span bdo
source	<xs:group name="special.basic">   <xs:choice>     <xs:element ref="br"/>     <xs:element ref="span"/>     <xs:element ref="bdo"/>   </xs:choice> </xs:group>

group special.extra

diagram
namespace	http://www.w3.org/1999/xhtml
children	object applet img map iframe
source	<xs:group name="special.extra">   <xs:choice>     <xs:element ref="object"/>     <xs:element ref="applet"/>     <xs:element ref="img"/>     <xs:element ref="map"/>     <xs:element ref="iframe"/>   </xs:choice> </xs:group>

complexType a.content

diagram
namespace	http://www.w3.org/1999/xhtml
properties	mixed  true
children	br i b u em strong input select textarea label button
annotation	documentation       a elements use "Inline" excluding a
source	<xs:complexType name="a.content" mixed="true">   <xs:annotation>     <xs:documentation>       a elements use "Inline" excluding a       </xs:documentation>   </xs:annotation>   <xs:choice minOccurs="0" maxOccurs="unbounded">     <xs:group ref="special"/>     <xs:group ref="fontstyle"/>     <xs:group ref="phrase"/>     <xs:group ref="inline.forms"/>     <xs:group ref="misc.inline"/>   </xs:choice> </xs:complexType>

complexType button.content

diagram
namespace	http://www.w3.org/1999/xhtml
properties	mixed  true
children	p h1 h2 h3 h4 h5 h6 div ul ol hr table br span bdo object applet img map i b u em strong
annotation	documentation       button uses "Flow" but excludes a, form, form controls, iframe
source	<xs:complexType name="button.content" mixed="true">   <xs:annotation>     <xs:documentation>       button uses "Flow" but excludes a, form, form controls, iframe       </xs:documentation>   </xs:annotation>   <xs:choice minOccurs="0" maxOccurs="unbounded">     <xs:element ref="p"/>     <xs:group ref="heading"/>     <xs:element ref="div"/>     <xs:group ref="lists"/>     <xs:group ref="blocktext"/>     <xs:element ref="table"/>     <xs:element ref="br"/>     <xs:element ref="span"/>     <xs:element ref="bdo"/>     <xs:element ref="object"/>     <xs:element ref="applet"/>     <xs:element ref="img"/>     <xs:element ref="map"/>     <xs:group ref="fontstyle"/>     <xs:group ref="phrase"/>     <xs:group ref="misc"/>   </xs:choice> </xs:complexType>

complexType Flow

diagram
namespace	http://www.w3.org/1999/xhtml
properties	mixed  true
children	p h1 h2 h3 h4 h5 h6 ul ol hr form br i b u em strong
annotation	documentation       "Flow" mixes block and inline and is used for list items etc.
source	<xs:complexType name="Flow" mixed="true">   <xs:annotation>     <xs:documentation>       "Flow" mixes block and inline and is used for list items etc.       </xs:documentation>   </xs:annotation>   <xs:choice minOccurs="0" maxOccurs="unbounded">     <xs:group ref="block"/>     <xs:element ref="form"/>     <xs:group ref="inline"/>     <xs:group ref="misc"/>   </xs:choice> </xs:complexType>

complexType form.content

diagram
namespace	http://www.w3.org/1999/xhtml
properties	mixed  true
children	p h1 h2 h3 h4 h5 h6 ul ol hr br i b u em strong
annotation	documentation       form uses "Flow" excluding form
source	<xs:complexType name="form.content" mixed="true">   <xs:annotation>     <xs:documentation>       form uses "Flow" excluding form       </xs:documentation>   </xs:annotation>   <xs:choice minOccurs="0" maxOccurs="unbounded">     <xs:group ref="block"/>     <xs:group ref="inline"/>     <xs:group ref="misc"/>   </xs:choice> </xs:complexType>

complexType Inline

diagram
namespace	http://www.w3.org/1999/xhtml
properties	mixed  true
children	br i b u em strong
annotation	documentation       "Inline" covers inline or "text-level" element
source	<xs:complexType name="Inline" mixed="true">   <xs:annotation>     <xs:documentation>       "Inline" covers inline or "text-level" element       </xs:documentation>   </xs:annotation>   <xs:choice minOccurs="0" maxOccurs="unbounded">     <xs:group ref="inline"/>     <xs:group ref="misc.inline"/>   </xs:choice> </xs:complexType>

complexType pre.content

diagram
namespace	http://www.w3.org/1999/xhtml
properties	mixed  true
children	a br i b u em strong input select textarea label button
annotation	documentation       pre uses "Inline" excluding img, object, applet, big, small,       font, or basefont
source	<xs:complexType name="pre.content" mixed="true">   <xs:annotation>     <xs:documentation>       pre uses "Inline" excluding img, object, applet, big, small,       font, or basefont       </xs:documentation>   </xs:annotation>   <xs:choice minOccurs="0" maxOccurs="unbounded">     <xs:element ref="a"/>     <xs:group ref="special.basic"/>     <xs:group ref="fontstyle.basic"/>     <xs:group ref="phrase.basic"/>     <xs:group ref="inline.forms"/>     <xs:group ref="misc.inline"/>   </xs:choice> </xs:complexType>

simpleType CAlign

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:token
properties	base  xs:token
facets	Kind  Value  Annotation enumeration  top enumeration  bottom enumeration  left enumeration  right
source	<xs:simpleType name="CAlign">   <xs:restriction base="xs:token">     <xs:enumeration value="top"/>     <xs:enumeration value="bottom"/>     <xs:enumeration value="left"/>     <xs:enumeration value="right"/>   </xs:restriction> </xs:simpleType>

simpleType Character

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:string
properties	base  xs:string
annotation	documentation       a single character, as per section 2.2 of [XML]
source	<xs:simpleType name="Character">   <xs:annotation>     <xs:documentation>       a single character, as per section 2.2 of [XML]       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:string">     <xs:length value="1" fixed="true"/>   </xs:restriction> </xs:simpleType>

simpleType Charset

namespace	http://www.w3.org/1999/xhtml
type	xs:string
properties	base  xs:string
annotation	documentation       a character encoding, as per [RFC2045]
source	<xs:simpleType name="Charset">   <xs:annotation>     <xs:documentation>       a character encoding, as per [RFC2045]       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:string"/> </xs:simpleType>

simpleType Charsets

namespace	http://www.w3.org/1999/xhtml
type	xs:string
properties	base  xs:string
annotation	documentation       a space separated list of character encodings, as per [RFC2045]
source	<xs:simpleType name="Charsets">   <xs:annotation>     <xs:documentation>       a space separated list of character encodings, as per [RFC2045]       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:string"/> </xs:simpleType>

simpleType Color

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:string
properties	base  xs:string
facets	Kind  Value  Annotation pattern  [A-Za-z]+|#[0-9A-Fa-f]{3}|#[0-9A-Fa-f]{6}
annotation	documentation       a color using sRGB: #RRGGBB as Hex values       There are also 16 widely known color names with their sRGB values:       Black  = #000000    Green  = #008000       Silver = #C0C0C0    Lime   = #00FF00       Gray   = #808080    Olive  = #808000       White  = #FFFFFF    Yellow = #FFFF00       Maroon = #800000    Navy   = #000080       Red    = #FF0000    Blue   = #0000FF       Purple = #800080    Teal   = #008080       Fuchsia= #FF00FF    Aqua   = #00FFFF
source	<xs:simpleType name="Color">   <xs:annotation>     <xs:documentation>       a color using sRGB: #RRGGBB as Hex values       There are also 16 widely known color names with their sRGB values:       Black  = #000000    Green  = #008000       Silver = #C0C0C0    Lime   = #00FF00       Gray   = #808080    Olive  = #808000       White  = #FFFFFF    Yellow = #FFFF00       Maroon = #800000    Navy   = #000080       Red    = #FF0000    Blue   = #0000FF       Purple = #800080    Teal   = #008080       Fuchsia= #FF00FF    Aqua   = #00FFFF       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:string">     <xs:pattern value="[A-Za-z]+|#[0-9A-Fa-f]{3}|#[0-9A-Fa-f]{6}"/>   </xs:restriction> </xs:simpleType>

simpleType ContentType

namespace	http://www.w3.org/1999/xhtml
type	xs:string
properties	base  xs:string
annotation	documentation       media type, as per [RFC2045]
source	<xs:simpleType name="ContentType">   <xs:annotation>     <xs:documentation>       media type, as per [RFC2045]       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:string"/> </xs:simpleType>

simpleType ContentTypes

namespace	http://www.w3.org/1999/xhtml
type	xs:string
properties	base  xs:string
annotation	documentation       comma-separated list of media types, as per [RFC2045]
source	<xs:simpleType name="ContentTypes">   <xs:annotation>     <xs:documentation>       comma-separated list of media types, as per [RFC2045]       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:string"/> </xs:simpleType>

simpleType Coords

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:string
properties	base  xs:string
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)(,\s*[-+]?(\d+|\d+(\.\d+)?%))*
annotation	documentation       comma separated list of lengths
source	<xs:simpleType name="Coords">   <xs:annotation>     <xs:documentation>       comma separated list of lengths       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:string">     <xs:pattern value="[-+]?(\d+|\d+(\.\d+)?%)(,\s*[-+]?(\d+|\d+(\.\d+)?%))*"/>   </xs:restriction> </xs:simpleType>

simpleType Datetime

namespace	http://www.w3.org/1999/xhtml
type	xs:dateTime
properties	base  xs:dateTime
annotation	documentation       date and time information. ISO date format
source	<xs:simpleType name="Datetime">   <xs:annotation>     <xs:documentation>       date and time information. ISO date format       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:dateTime"/> </xs:simpleType>

simpleType FrameTarget

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:NMTOKEN
properties	base  xs:NMTOKEN
facets	Kind  Value  Annotation pattern  _(blank|self|parent|top)|[A-Za-z]\c*
annotation	documentation       render in this frame
source	<xs:simpleType name="FrameTarget">   <xs:annotation>     <xs:documentation>       render in this frame       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:NMTOKEN">     <xs:pattern value="_(blank|self|parent|top)|[A-Za-z]\c*"/>   </xs:restriction> </xs:simpleType>

simpleType ImgAlign

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:token
properties	base  xs:token
facets	Kind  Value  Annotation enumeration  top enumeration  middle enumeration  bottom enumeration  left enumeration  right
annotation	documentation       used for object, applet, img, input and iframe
source	<xs:simpleType name="ImgAlign">   <xs:annotation>     <xs:documentation>       used for object, applet, img, input and iframe       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:token">     <xs:enumeration value="top"/>     <xs:enumeration value="middle"/>     <xs:enumeration value="bottom"/>     <xs:enumeration value="left"/>     <xs:enumeration value="right"/>   </xs:restriction> </xs:simpleType>

simpleType InputType

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:token
properties	base  xs:token
facets	Kind  Value  Annotation enumeration  text enumeration  password enumeration  checkbox enumeration  radio enumeration  submit enumeration  reset enumeration  file enumeration  hidden enumeration  image enumeration  button
source	<xs:simpleType name="InputType">   <xs:restriction base="xs:token">     <xs:enumeration value="text"/>     <xs:enumeration value="password"/>     <xs:enumeration value="checkbox"/>     <xs:enumeration value="radio"/>     <xs:enumeration value="submit"/>     <xs:enumeration value="reset"/>     <xs:enumeration value="file"/>     <xs:enumeration value="hidden"/>     <xs:enumeration value="image"/>     <xs:enumeration value="button"/>   </xs:restriction> </xs:simpleType>

simpleType LAlign

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:token
properties	base  xs:token
facets	Kind  Value  Annotation enumeration  top enumeration  bottom enumeration  left enumeration  right
source	<xs:simpleType name="LAlign">   <xs:restriction base="xs:token">     <xs:enumeration value="top"/>     <xs:enumeration value="bottom"/>     <xs:enumeration value="left"/>     <xs:enumeration value="right"/>   </xs:restriction> </xs:simpleType>

simpleType LanguageCode

namespace	http://www.w3.org/1999/xhtml
type	xs:language
properties	base  xs:language
annotation	documentation       a language code, as per [RFC3066]
source	<xs:simpleType name="LanguageCode">   <xs:annotation>     <xs:documentation>       a language code, as per [RFC3066]       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:language"/> </xs:simpleType>

simpleType Length

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:string
properties	base  xs:string
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
annotation	documentation       nn for pixels or nn% for percentage length
source	<xs:simpleType name="Length">   <xs:annotation>     <xs:documentation>       nn for pixels or nn% for percentage length       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:string">     <xs:pattern value="[-+]?(\d+|\d+(\.\d+)?%)"/>   </xs:restriction> </xs:simpleType>

simpleType LinkTypes

namespace	http://www.w3.org/1999/xhtml
type	xs:NMTOKENS
properties	base  xs:NMTOKENS
annotation	documentation       space-separated list of link types
source	<xs:simpleType name="LinkTypes">   <xs:annotation>     <xs:documentation>       space-separated list of link types       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:NMTOKENS"/> </xs:simpleType>

simpleType LIStyle

namespace	http://www.w3.org/1999/xhtml
type	xs:string
properties	base  xs:string
annotation	documentation       LIStyle is constrained to: "(ULStyle|OLStyle)"
source	<xs:simpleType name="LIStyle">   <xs:annotation>     <xs:documentation>       LIStyle is constrained to: "(ULStyle|OLStyle)"       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:string"/> </xs:simpleType>

simpleType MediaDesc

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:string
properties	base  xs:string
facets	Kind  Value  Annotation pattern  [^,]+(,\s*[^,]+)*
annotation	documentation       single or comma-separated list of media descriptors
source	<xs:simpleType name="MediaDesc">   <xs:annotation>     <xs:documentation>       single or comma-separated list of media descriptors       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:string">     <xs:pattern value="[^,]+(,\s*[^,]+)*"/>   </xs:restriction> </xs:simpleType>

simpleType MultiLength

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:string
properties	base  xs:string
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)|[1-9]?(\d+)?\*
annotation	documentation       pixel, percentage, or relative
source	<xs:simpleType name="MultiLength">   <xs:annotation>     <xs:documentation>       pixel, percentage, or relative       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:string">     <xs:pattern value="[-+]?(\d+|\d+(\.\d+)?%)|[1-9]?(\d+)?\*"/>   </xs:restriction> </xs:simpleType>

simpleType Number

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:nonNegativeInteger
properties	base  xs:nonNegativeInteger
facets	Kind  Value  Annotation pattern  [0-9]+
annotation	documentation       one or more digits
source	<xs:simpleType name="Number">   <xs:annotation>     <xs:documentation>       one or more digits       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:nonNegativeInteger">     <xs:pattern value="[0-9]+"/>   </xs:restriction> </xs:simpleType>

simpleType OLStyle

namespace	http://www.w3.org/1999/xhtml
type	xs:string
properties	base  xs:string
annotation	documentation       Ordered list numbering style       1   arabic numbers      1, 2, 3, ...       a   lower alpha         a, b, c, ...       A   upper alpha         A, B, C, ...       i   lower roman         i, ii, iii, ...       I   upper roman         I, II, III, ...       The style is applied to the sequence number which by default       is reset to 1 for the first list item in an ordered list.
source	<xs:simpleType name="OLStyle">   <xs:annotation>     <xs:documentation>       Ordered list numbering style       1   arabic numbers      1, 2, 3, ...       a   lower alpha         a, b, c, ...       A   upper alpha         A, B, C, ...       i   lower roman         i, ii, iii, ...       I   upper roman         I, II, III, ...       The style is applied to the sequence number which by default       is reset to 1 for the first list item in an ordered list.       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:string"/> </xs:simpleType>

simpleType Pixels

namespace	http://www.w3.org/1999/xhtml
type	xs:nonNegativeInteger
properties	base  xs:nonNegativeInteger
annotation	documentation       integer representing length in pixels
source	<xs:simpleType name="Pixels">   <xs:annotation>     <xs:documentation>       integer representing length in pixels       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:nonNegativeInteger"/> </xs:simpleType>

simpleType Scope

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:token
properties	base  xs:token
facets	Kind  Value  Annotation enumeration  row enumeration  col enumeration  rowgroup enumeration  colgroup
annotation	documentation       Scope is simpler than headers attribute for common tables
source	<xs:simpleType name="Scope">   <xs:annotation>     <xs:documentation>       Scope is simpler than headers attribute for common tables       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:token">     <xs:enumeration value="row"/>     <xs:enumeration value="col"/>     <xs:enumeration value="rowgroup"/>     <xs:enumeration value="colgroup"/>   </xs:restriction> </xs:simpleType>

simpleType Script

namespace	http://www.w3.org/1999/xhtml
type	xs:string
properties	base  xs:string
annotation	documentation       script expression
source	<xs:simpleType name="Script">   <xs:annotation>     <xs:documentation>       script expression       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:string"/> </xs:simpleType>

simpleType Shape

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:token
properties	base  xs:token
facets	Kind  Value  Annotation enumeration  rect enumeration  circle enumeration  poly enumeration  default
source	<xs:simpleType name="Shape">   <xs:restriction base="xs:token">     <xs:enumeration value="rect"/>     <xs:enumeration value="circle"/>     <xs:enumeration value="poly"/>     <xs:enumeration value="default"/>   </xs:restriction> </xs:simpleType>

simpleType StyleSheet

namespace	http://www.w3.org/1999/xhtml
type	xs:string
properties	base  xs:string
annotation	documentation       style sheet data
source	<xs:simpleType name="StyleSheet">   <xs:annotation>     <xs:documentation>       style sheet data       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:string"/> </xs:simpleType>

simpleType tabindexNumber

namespace	http://www.w3.org/1999/xhtml
type	restriction of Number
properties	base  Number
facets	Kind  Value  Annotation pattern  [0-9]+
annotation	documentation       tabindex attribute specifies the position of the current element       in the tabbing order for the current document. This value must be       a number between 0 and 32767. User agents should ignore leading zeros.
source	<xs:simpleType name="tabindexNumber">   <xs:annotation>     <xs:documentation>       tabindex attribute specifies the position of the current element       in the tabbing order for the current document. This value must be       a number between 0 and 32767. User agents should ignore leading zeros.       </xs:documentation>   </xs:annotation>   <xs:restriction base="Number">     <xs:minInclusive value="0"/>     <xs:maxInclusive value="32767"/>   </xs:restriction> </xs:simpleType>

simpleType TAlign

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:token
properties	base  xs:token
facets	Kind  Value  Annotation enumeration  left enumeration  center enumeration  right
annotation	documentation       horizontal placement of table relative to document
source	<xs:simpleType name="TAlign">   <xs:annotation>     <xs:documentation>       horizontal placement of table relative to document       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:token">     <xs:enumeration value="left"/>     <xs:enumeration value="center"/>     <xs:enumeration value="right"/>   </xs:restriction> </xs:simpleType>

simpleType Text

namespace	http://www.w3.org/1999/xhtml
type	xs:string
properties	base  xs:string
annotation	documentation       used for titles etc.
source	<xs:simpleType name="Text">   <xs:annotation>     <xs:documentation>       used for titles etc.       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:string"/> </xs:simpleType>

simpleType TFrame

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:token
properties	base  xs:token
facets	Kind  Value  Annotation enumeration  void enumeration  above enumeration  below enumeration  hsides enumeration  lhs enumeration  rhs enumeration  vsides enumeration  box enumeration  border
annotation	documentation       The border attribute sets the thickness of the frame around the       table. The default units are screen pixels.       The frame attribute specifies which parts of the frame around       the table should be rendered. The values are not the same as       CALS to avoid a name clash with the valign attribute.
source	<xs:simpleType name="TFrame">   <xs:annotation>     <xs:documentation>       The border attribute sets the thickness of the frame around the       table. The default units are screen pixels.       The frame attribute specifies which parts of the frame around       the table should be rendered. The values are not the same as       CALS to avoid a name clash with the valign attribute.       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:token">     <xs:enumeration value="void"/>     <xs:enumeration value="above"/>     <xs:enumeration value="below"/>     <xs:enumeration value="hsides"/>     <xs:enumeration value="lhs"/>     <xs:enumeration value="rhs"/>     <xs:enumeration value="vsides"/>     <xs:enumeration value="box"/>     <xs:enumeration value="border"/>   </xs:restriction> </xs:simpleType>

simpleType TRules

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:token
properties	base  xs:token
facets	Kind  Value  Annotation enumeration  none enumeration  groups enumeration  rows enumeration  cols enumeration  all
annotation	documentation       The rules attribute defines which rules to draw between cells:       If rules is absent then assume:           "none" if border is absent or border="0" otherwise "all"
source	<xs:simpleType name="TRules">   <xs:annotation>     <xs:documentation>       The rules attribute defines which rules to draw between cells:       If rules is absent then assume:           "none" if border is absent or border="0" otherwise "all"       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:token">     <xs:enumeration value="none"/>     <xs:enumeration value="groups"/>     <xs:enumeration value="rows"/>     <xs:enumeration value="cols"/>     <xs:enumeration value="all"/>   </xs:restriction> </xs:simpleType>

simpleType ULStyle

namespace	http://www.w3.org/1999/xhtml
type	restriction of xs:token
properties	base  xs:token
facets	Kind  Value  Annotation enumeration  disc enumeration  square enumeration  circle
annotation	documentation       Unordered list bullet styles
source	<xs:simpleType name="ULStyle">   <xs:annotation>     <xs:documentation>       Unordered list bullet styles       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:token">     <xs:enumeration value="disc"/>     <xs:enumeration value="square"/>     <xs:enumeration value="circle"/>   </xs:restriction> </xs:simpleType>

simpleType URI

namespace	http://www.w3.org/1999/xhtml
type	xs:anyURI
properties	base  xs:anyURI
annotation	documentation       a Uniform Resource Identifier, see [RFC2396]
source	<xs:simpleType name="URI">   <xs:annotation>     <xs:documentation>       a Uniform Resource Identifier, see [RFC2396]       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:anyURI"/> </xs:simpleType>

simpleType UriList

namespace	http://www.w3.org/1999/xhtml
type	xs:string
properties	base  xs:string
annotation	documentation       a space separated list of Uniform Resource Identifiers
source	<xs:simpleType name="UriList">   <xs:annotation>     <xs:documentation>       a space separated list of Uniform Resource Identifiers       </xs:documentation>   </xs:annotation>   <xs:restriction base="xs:string"/> </xs:simpleType>

attributeGroup attrs

namespace	http://www.w3.org/1999/xhtml
attributes	Name   Type   Use   Default   Fixed   Annotation lang   LanguageCode            xml:lang   derived by: xs:language            documentation <div> <h3>lang (as an attribute name)</h3> <p>        denotes an attribute whose value        is a language code for the natural language of the content of        any element; its value is inherited.  This name is reserved        by virtue of its definition in the XML specification.</p> </div> <div> <h4>Notes</h4> <p>       Attempting to install the relevant ISO 2- and 3-letter       codes as the enumerated possible values is probably never       going to be a realistic possibility.       </p> <p>       See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">        http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>       and the IANA language subtag registry at       <a href="http://www.iana.org/assignments/language-subtag-registry">        http://www.iana.org/assignments/language-subtag-registry</a>       for further information.      </p> <p>       The union allows for the 'un-declaration' of xml:lang with       the empty string.      </p> </div> dir   derived by: xs:token            onclick   Script            ondblclick   Script            onmousedown   Script            onmouseup   Script            onmouseover   Script            onmousemove   Script            onmouseout   Script            onkeypress   Script            onkeydown   Script            onkeyup   Script
source	<xs:attributeGroup name="attrs">   <xs:attributeGroup ref="coreattrs"/>   <xs:attributeGroup ref="i18n"/>   <xs:attributeGroup ref="events"/> </xs:attributeGroup>

attributeGroup cellhalign

namespace	http://www.w3.org/1999/xhtml
attributes	Name   Type   Use   Default   Fixed   Annotation align   derived by: xs:token            char   Character            charoff   Length
annotation	documentation       horizontal alignment attributes for cell contents       char        alignment char, e.g. char=':'       charoff     offset for alignment char
source	<xs:attributeGroup name="cellhalign">   <xs:annotation>     <xs:documentation>       horizontal alignment attributes for cell contents       char        alignment char, e.g. char=':'       charoff     offset for alignment char       </xs:documentation>   </xs:annotation>   <xs:attribute name="align">     <xs:simpleType>       <xs:restriction base="xs:token">         <xs:enumeration value="left"/>         <xs:enumeration value="center"/>         <xs:enumeration value="right"/>         <xs:enumeration value="justify"/>         <xs:enumeration value="char"/>       </xs:restriction>     </xs:simpleType>   </xs:attribute>   <xs:attribute name="char" type="Character"/>   <xs:attribute name="charoff" type="Length"/> </xs:attributeGroup>

attribute cellhalign/@align

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  left enumeration  center enumeration  right enumeration  justify enumeration  char
source	<xs:attribute name="align">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="left"/>       <xs:enumeration value="center"/>       <xs:enumeration value="right"/>       <xs:enumeration value="justify"/>       <xs:enumeration value="char"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute cellhalign/@char

type	Character
source	<xs:attribute name="char" type="Character"/>

attribute cellhalign/@charoff

type	Length
facets	Kind  Value  Annotation pattern  [-+]?(\d+|\d+(\.\d+)?%)
source	<xs:attribute name="charoff" type="Length"/>

attributeGroup cellvalign

namespace	http://www.w3.org/1999/xhtml
attributes	Name   Type   Use   Default   Fixed   Annotation valign   derived by: xs:token
annotation	documentation       vertical alignment attributes for cell contents
source	<xs:attributeGroup name="cellvalign">   <xs:annotation>     <xs:documentation>       vertical alignment attributes for cell contents       </xs:documentation>   </xs:annotation>   <xs:attribute name="valign">     <xs:simpleType>       <xs:restriction base="xs:token">         <xs:enumeration value="top"/>         <xs:enumeration value="middle"/>         <xs:enumeration value="bottom"/>         <xs:enumeration value="baseline"/>       </xs:restriction>     </xs:simpleType>   </xs:attribute> </xs:attributeGroup>

attribute cellvalign/@valign

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  top enumeration  middle enumeration  bottom enumeration  baseline
source	<xs:attribute name="valign">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="top"/>       <xs:enumeration value="middle"/>       <xs:enumeration value="bottom"/>       <xs:enumeration value="baseline"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attributeGroup coreattrs

namespace	http://www.w3.org/1999/xhtml
attributes	Name   Type   Use   Default   Fixed   Annotation id   xs:ID            class   xs:NMTOKENS            style   StyleSheet            title   Text
annotation	documentation       core attributes common to most elements       id       document-wide unique id       class    space separated list of classes       style    associated style info       title    advisory title/amplification
source	<xs:attributeGroup name="coreattrs">   <xs:annotation>     <xs:documentation>       core attributes common to most elements       id       document-wide unique id       class    space separated list of classes       style    associated style info       title    advisory title/amplification       </xs:documentation>   </xs:annotation>   <xs:attribute name="id" type="xs:ID"/>   <xs:attribute name="class" type="xs:NMTOKENS"/>   <xs:attribute name="style" type="StyleSheet"/>   <xs:attribute name="title" type="Text"/> </xs:attributeGroup>

attribute coreattrs/@id

type	xs:ID
source	<xs:attribute name="id" type="xs:ID"/>

attribute coreattrs/@class

type	xs:NMTOKENS
source	<xs:attribute name="class" type="xs:NMTOKENS"/>

attribute coreattrs/@style

type	StyleSheet
source	<xs:attribute name="style" type="StyleSheet"/>

attribute coreattrs/@title

type	Text
source	<xs:attribute name="title" type="Text"/>

attributeGroup events

namespace	http://www.w3.org/1999/xhtml
attributes	Name   Type   Use   Default   Fixed   Annotation onclick   Script            ondblclick   Script            onmousedown   Script            onmouseup   Script            onmouseover   Script            onmousemove   Script            onmouseout   Script            onkeypress   Script            onkeydown   Script            onkeyup   Script
annotation	documentation       attributes for common UI events       onclick     a pointer button was clicked       ondblclick  a pointer button was double clicked       onmousedown a pointer button was pressed down       onmouseup   a pointer button was released       onmousemove a pointer was moved onto the element       onmouseout  a pointer was moved away from the element       onkeypress  a key was pressed and released       onkeydown   a key was pressed down       onkeyup     a key was released
source	<xs:attributeGroup name="events">   <xs:annotation>     <xs:documentation>       attributes for common UI events       onclick     a pointer button was clicked       ondblclick  a pointer button was double clicked       onmousedown a pointer button was pressed down       onmouseup   a pointer button was released       onmousemove a pointer was moved onto the element       onmouseout  a pointer was moved away from the element       onkeypress  a key was pressed and released       onkeydown   a key was pressed down       onkeyup     a key was released       </xs:documentation>   </xs:annotation>   <xs:attribute name="onclick" type="Script"/>   <xs:attribute name="ondblclick" type="Script"/>   <xs:attribute name="onmousedown" type="Script"/>   <xs:attribute name="onmouseup" type="Script"/>   <xs:attribute name="onmouseover" type="Script"/>   <xs:attribute name="onmousemove" type="Script"/>   <xs:attribute name="onmouseout" type="Script"/>   <xs:attribute name="onkeypress" type="Script"/>   <xs:attribute name="onkeydown" type="Script"/>   <xs:attribute name="onkeyup" type="Script"/> </xs:attributeGroup>

attribute events/@onclick

type	Script
source	<xs:attribute name="onclick" type="Script"/>

attribute events/@ondblclick

type	Script
source	<xs:attribute name="ondblclick" type="Script"/>

attribute events/@onmousedown

type	Script
source	<xs:attribute name="onmousedown" type="Script"/>

attribute events/@onmouseup

type	Script
source	<xs:attribute name="onmouseup" type="Script"/>

attribute events/@onmouseover

type	Script
source	<xs:attribute name="onmouseover" type="Script"/>

attribute events/@onmousemove

type	Script
source	<xs:attribute name="onmousemove" type="Script"/>

attribute events/@onmouseout

type	Script
source	<xs:attribute name="onmouseout" type="Script"/>

attribute events/@onkeypress

type	Script
source	<xs:attribute name="onkeypress" type="Script"/>

attribute events/@onkeydown

type	Script
source	<xs:attribute name="onkeydown" type="Script"/>

attribute events/@onkeyup

type	Script
source	<xs:attribute name="onkeyup" type="Script"/>

attributeGroup focus

namespace	http://www.w3.org/1999/xhtml
attributes	Name   Type   Use   Default   Fixed   Annotation accesskey   Character            tabindex   tabindexNumber            onfocus   Script            onblur   Script
annotation	documentation       attributes for elements that can get the focus       accesskey   accessibility key character       tabindex    position in tabbing order       onfocus     the element got the focus       onblur      the element lost the focus
source	<xs:attributeGroup name="focus">   <xs:annotation>     <xs:documentation>       attributes for elements that can get the focus       accesskey   accessibility key character       tabindex    position in tabbing order       onfocus     the element got the focus       onblur      the element lost the focus       </xs:documentation>   </xs:annotation>   <xs:attribute name="accesskey" type="Character"/>   <xs:attribute name="tabindex" type="tabindexNumber"/>   <xs:attribute name="onfocus" type="Script"/>   <xs:attribute name="onblur" type="Script"/> </xs:attributeGroup>

attribute focus/@accesskey

type	Character
source	<xs:attribute name="accesskey" type="Character"/>

attribute focus/@tabindex

type	tabindexNumber
facets	Kind  Value  Annotation pattern  [0-9]+
source	<xs:attribute name="tabindex" type="tabindexNumber"/>

attribute focus/@onfocus

type	Script
source	<xs:attribute name="onfocus" type="Script"/>

attribute focus/@onblur

type	Script
source	<xs:attribute name="onblur" type="Script"/>

attributeGroup i18n

namespace	http://www.w3.org/1999/xhtml
attributes	Name   Type   Use   Default   Fixed   Annotation lang   LanguageCode            xml:lang   derived by: xs:language            documentation <div> <h3>lang (as an attribute name)</h3> <p>        denotes an attribute whose value        is a language code for the natural language of the content of        any element; its value is inherited.  This name is reserved        by virtue of its definition in the XML specification.</p> </div> <div> <h4>Notes</h4> <p>       Attempting to install the relevant ISO 2- and 3-letter       codes as the enumerated possible values is probably never       going to be a realistic possibility.       </p> <p>       See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">        http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>       and the IANA language subtag registry at       <a href="http://www.iana.org/assignments/language-subtag-registry">        http://www.iana.org/assignments/language-subtag-registry</a>       for further information.      </p> <p>       The union allows for the 'un-declaration' of xml:lang with       the empty string.      </p> </div> dir   derived by: xs:token
annotation	documentation       internationalization attributes       lang        language code (backwards compatible)       xml:lang    language code (as per XML 1.0 spec)       dir         direction for weak/neutral text
source	<xs:attributeGroup name="i18n">   <xs:annotation>     <xs:documentation>       internationalization attributes       lang        language code (backwards compatible)       xml:lang    language code (as per XML 1.0 spec)       dir         direction for weak/neutral text       </xs:documentation>   </xs:annotation>   <xs:attribute name="lang" type="LanguageCode"/>   <xs:attribute ref="xml:lang"/>   <xs:attribute name="dir">     <xs:simpleType>       <xs:restriction base="xs:token">         <xs:enumeration value="ltr"/>         <xs:enumeration value="rtl"/>       </xs:restriction>     </xs:simpleType>   </xs:attribute> </xs:attributeGroup>

attribute i18n/@lang

type	LanguageCode
source	<xs:attribute name="lang" type="LanguageCode"/>

attribute i18n/@dir

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  ltr enumeration  rtl
source	<xs:attribute name="dir">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="ltr"/>       <xs:enumeration value="rtl"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attributeGroup TextAlign

namespace	http://www.w3.org/1999/xhtml
attributes	Name   Type   Use   Default   Fixed   Annotation align   derived by: xs:token
annotation	documentation       text alignment for p, div, h1-h6. The default is       align="left" for ltr headings, "right" for rtl
source	<xs:attributeGroup name="TextAlign">   <xs:annotation>     <xs:documentation>       text alignment for p, div, h1-h6. The default is       align="left" for ltr headings, "right" for rtl       </xs:documentation>   </xs:annotation>   <xs:attribute name="align">     <xs:simpleType>       <xs:restriction base="xs:token">         <xs:enumeration value="left"/>         <xs:enumeration value="center"/>         <xs:enumeration value="right"/>         <xs:enumeration value="justify"/>       </xs:restriction>     </xs:simpleType>   </xs:attribute> </xs:attributeGroup>

attribute TextAlign/@align

type	restriction of xs:token
facets	Kind  Value  Annotation enumeration  left enumeration  center enumeration  right enumeration  justify
source	<xs:attribute name="align">   <xs:simpleType>     <xs:restriction base="xs:token">       <xs:enumeration value="left"/>       <xs:enumeration value="center"/>       <xs:enumeration value="right"/>       <xs:enumeration value="justify"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attribute base

namespace	http://www.w3.org/XML/1998/namespace
type	xs:anyURI
annotation	documentation <div> <h3>base (as an attribute name)</h3> <p>        denotes an attribute whose value        provides a URI to be used as the base for interpreting any        relative URIs in the scope of the element on which it        appears; its value is inherited.  This name is reserved        by virtue of its definition in the XML Base specification.</p> <p>       See <a href="http://www.w3.org/TR/xmlbase/">http://www.w3.org/TR/xmlbase/</a>       for information about this attribute.      </p> </div>
source	<xs:attribute name="base" type="xs:anyURI">   <xs:annotation>     <xs:documentation>       <div>         <h3>base (as an attribute name)</h3>         <p>        denotes an attribute whose value        provides a URI to be used as the base for interpreting any        relative URIs in the scope of the element on which it        appears; its value is inherited.  This name is reserved        by virtue of its definition in the XML Base specification.</p>         <p>       See <a href="http://www.w3.org/TR/xmlbase/">http://www.w3.org/TR/xmlbase/</a>       for information about this attribute.      </p>       </div>     </xs:documentation>   </xs:annotation> </xs:attribute>

attribute id

namespace	http://www.w3.org/XML/1998/namespace
type	xs:ID
annotation	documentation <div> <h3>id (as an attribute name)</h3> <p>        denotes an attribute whose value        should be interpreted as if declared to be of type ID.        This name is reserved by virtue of its definition in the        xml:id specification.</p> <p>       See <a href="http://www.w3.org/TR/xml-id/">http://www.w3.org/TR/xml-id/</a>       for information about this attribute.      </p> </div>
source	<xs:attribute name="id" type="xs:ID">   <xs:annotation>     <xs:documentation>       <div>         <h3>id (as an attribute name)</h3>         <p>        denotes an attribute whose value        should be interpreted as if declared to be of type ID.        This name is reserved by virtue of its definition in the        xml:id specification.</p>         <p>       See <a href="http://www.w3.org/TR/xml-id/">http://www.w3.org/TR/xml-id/</a>       for information about this attribute.      </p>       </div>     </xs:documentation>   </xs:annotation> </xs:attribute>

attribute lang

namespace	http://www.w3.org/XML/1998/namespace
type	union of (xs:language, restriction of xs:string)
annotation	documentation <div> <h3>lang (as an attribute name)</h3> <p>        denotes an attribute whose value        is a language code for the natural language of the content of        any element; its value is inherited.  This name is reserved        by virtue of its definition in the XML specification.</p> </div> <div> <h4>Notes</h4> <p>       Attempting to install the relevant ISO 2- and 3-letter       codes as the enumerated possible values is probably never       going to be a realistic possibility.       </p> <p>       See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">        http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>       and the IANA language subtag registry at       <a href="http://www.iana.org/assignments/language-subtag-registry">        http://www.iana.org/assignments/language-subtag-registry</a>       for further information.      </p> <p>       The union allows for the 'un-declaration' of xml:lang with       the empty string.      </p> </div>
source	<xs:attribute name="lang">   <xs:annotation>     <xs:documentation>       <div>         <h3>lang (as an attribute name)</h3>         <p>        denotes an attribute whose value        is a language code for the natural language of the content of        any element; its value is inherited.  This name is reserved        by virtue of its definition in the XML specification.</p>       </div>       <div>         <h4>Notes</h4>         <p>       Attempting to install the relevant ISO 2- and 3-letter       codes as the enumerated possible values is probably never       going to be a realistic possibility.       </p>         <p>       See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">        http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>       and the IANA language subtag registry at       <a href="http://www.iana.org/assignments/language-subtag-registry">        http://www.iana.org/assignments/language-subtag-registry</a>       for further information.      </p>         <p>       The union allows for the 'un-declaration' of xml:lang with       the empty string.      </p>       </div>     </xs:documentation>   </xs:annotation>   <xs:simpleType>     <xs:union memberTypes="xs:language">       <xs:simpleType>         <xs:restriction base="xs:string">           <xs:enumeration value=""/>         </xs:restriction>       </xs:simpleType>     </xs:union>   </xs:simpleType> </xs:attribute>

attribute space

namespace	http://www.w3.org/XML/1998/namespace
type	restriction of xs:NCName
facets	Kind  Value  Annotation enumeration  default enumeration  preserve
annotation	documentation <div> <h3>space (as an attribute name)</h3> <p>        denotes an attribute whose        value is a keyword indicating what whitespace processing        discipline is intended for the content of the element; its        value is inherited.  This name is reserved by virtue of its        definition in the XML specification.</p> </div>
source	<xs:attribute name="space">   <xs:annotation>     <xs:documentation>       <div>         <h3>space (as an attribute name)</h3>         <p>        denotes an attribute whose        value is a keyword indicating what whitespace processing        discipline is intended for the content of the element; its        value is inherited.  This name is reserved by virtue of its        definition in the XML specification.</p>       </div>     </xs:documentation>   </xs:annotation>   <xs:simpleType>     <xs:restriction base="xs:NCName">       <xs:enumeration value="default"/>       <xs:enumeration value="preserve"/>     </xs:restriction>   </xs:simpleType> </xs:attribute>

attributeGroup specialAttrs

namespace	http://www.w3.org/XML/1998/namespace
attributes	Name   Type   Use   Default   Fixed   Annotation xml:base   xs:anyURI            documentation <div> <h3>base (as an attribute name)</h3> <p>        denotes an attribute whose value        provides a URI to be used as the base for interpreting any        relative URIs in the scope of the element on which it        appears; its value is inherited.  This name is reserved        by virtue of its definition in the XML Base specification.</p> <p>       See <a href="http://www.w3.org/TR/xmlbase/">http://www.w3.org/TR/xmlbase/</a>       for information about this attribute.      </p> </div> xml:lang   derived by: xs:language            documentation <div> <h3>lang (as an attribute name)</h3> <p>        denotes an attribute whose value        is a language code for the natural language of the content of        any element; its value is inherited.  This name is reserved        by virtue of its definition in the XML specification.</p> </div> <div> <h4>Notes</h4> <p>       Attempting to install the relevant ISO 2- and 3-letter       codes as the enumerated possible values is probably never       going to be a realistic possibility.       </p> <p>       See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">        http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>       and the IANA language subtag registry at       <a href="http://www.iana.org/assignments/language-subtag-registry">        http://www.iana.org/assignments/language-subtag-registry</a>       for further information.      </p> <p>       The union allows for the 'un-declaration' of xml:lang with       the empty string.      </p> </div> xml:space   derived by: xs:NCName            documentation <div> <h3>space (as an attribute name)</h3> <p>        denotes an attribute whose        value is a keyword indicating what whitespace processing        discipline is intended for the content of the element; its        value is inherited.  This name is reserved by virtue of its        definition in the XML specification.</p> </div> xml:id   xs:ID            documentation <div> <h3>id (as an attribute name)</h3> <p>        denotes an attribute whose value        should be interpreted as if declared to be of type ID.        This name is reserved by virtue of its definition in the        xml:id specification.</p> <p>       See <a href="http://www.w3.org/TR/xml-id/">http://www.w3.org/TR/xml-id/</a>       for information about this attribute.      </p> </div>
source	<xs:attributeGroup name="specialAttrs">   <xs:attribute ref="xml:base"/>   <xs:attribute ref="xml:lang"/>   <xs:attribute ref="xml:space"/>   <xs:attribute ref="xml:id"/> </xs:attributeGroup>

XML Schema documentation generated by XMLSpy Schema Editor http://www.altova.com/xmlspy