UNDT000007-SC2 SC Code List. Identifier The identification of a list of codes. Code List Identification Identifier string UNDT000007-SC3 SC Code List. Agency. Identifier An agency that maintains one or more lists of codes. Code List Agency Identifier string Defaults to the UN/EDIFACT data element 3055 code list. UNDT000007-SC4 SC Code List. Agency Name. Text The name of the agency that maintains the list of codes. Code List Agency Name Text string UNDT000007-SC5 SC Code List. Name. Text The name of a list of codes. Code List Name Text string UNDT000007-SC6 SC Code List. Version. Identifier The version of the list of codes. Code List Version Identifier string UNDT000007-SC7 SC Code. Name. Text The textual equivalent of the code content component. Code Name Text string UNDT000007-SC8 SC Language. Identifier The identifier of the language used in the code name. Language Identification Identifier string UNDT000007-SC9 SC Code List. Uniform Resource. Identifier The Uniform Resource Identifier that identifies where the code list is located. Code List Uniform Resource Identifier Identifier string UNDT000007-SC10 SC Code List Scheme. Uniform Resource. Identifier The Uniform Resource Identifier that identifies where the code list scheme is located. Code List Scheme Uniform Resource Identifier Identifier string Is where the information that the BOD message carries is provided, in this case SyncInvoice. The information consists of a Verb and one or more Nouns. The verb (Sync) indicates the action to be performed on the Noun (Invoice). Is the schema based inheritance for all BODs. The logical model would also include the DataArea. OAGIS Release this BOD Instances belongs or the OAGIS release that the derivative work is based on. Indicates the version of the given BOD defintion. Indicates whether this BOD is being sent in a "Test" or a "Production" mode. If the BOD is being sent in a test mode, it's information should not affect the business operation. However, if the BOD is sent in "Production" mode it is assumed that all test has been complete and the contents of the BOD are to affect the operation of the receiving business application(s). Indicates the language that the contents of the BOD is in unless otherwise stated. The InvoiceHeader type supports summary amounts for line items, charges and allowances. A code for the invoice.Example: Special allowance for preferred customers. The InvoiceLine type supports order line invoicing. The abstract Header type that is the basis for all non-statusable OAGIS Document Headers Indicates the number of order items for the given line.. Unit price of the item for the number of items in the unitCode specified in the PerQuantity elements. In most cases the unitCode of the PerQuantity is the same as the unitCode of the Quantity element above. Unit price of the item for the number of items in the unitCode specified in the PerQuantity elements. In most cases the unitCode of the PerQuantity is the same as the unitCode of the Quantity element above. Indicates that the line is an open item and is not to be included in the document total. Identifies the sender of the given BOD instance Allows any digital Signatures to be added to the Instance of the BOD Instance in order to sign for any portion of the BOD content. The abstract Line type that is the basis for all non-statusable OAGIS Document Lines ReturnCriteria identifies the content that is to be returned, given query success. In essence, the expression here has the effect of filtering the part(s) of the found element(s) that are to be returned. ReturnCriteria plays no role in the query itself. That is handled as a match against the request BOD's noun exemplar. ReturnCriteria allows the sender of the BOD to indicate which information (down to the field level) is requested to be returned, given that the query has been successful in matching the exemplar to existing nouns. That is, in a GetListPurchaseOrder, if one or more PurchaseOrders with a TotalPrice = $1M were found, ReturnCriteria tells the BOD recipient which parts of the PurchaseOrder should be populated with content when the response (ShowPurchaseOrder) is formulated. The expressionLanguage indicates the expression language being used. In order for the ReturnCriteria expression to be evaluable by the BOD recipient, the recipient must be capable of processing and interpreting the specified expression language. XPath is the default, due to its ubiquity among XML processing technologies. TaxABIEType is logically derived from UN/CEFACT TBG17 ABIE TaxType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Indicates that tax code of the tax being represented by the given instance of tax. Possible values are: Sales Tax, Use Tax, VAT AllowanceChargeABIEType is based on the UN/CEFACT TBG17 AllowanceChargeType that can be found the Reusable Aggregate Business Information Entity (RUABIE) XML Schema files. Identifies the type of charge that the given instance of Charge/Allowance. PriceABIEType is logically derived from UN/CEFACT TBG17 ABIE PriceType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. This is the ID assigned to the document by the creator of the document. QDT000000 QDT Description_ Text. Type 1.0 Text Description A free form note. The lang attribute identifies the language that the note is in. The author identifies the author of the note. The enrtyDate indicates the date the note was entered or last modified. If Billing Date is March 15, and the payment is due by April 21. The ProxMonth would be 1 and the ProxDayOfMonth would be 21. Is the basis for Items. Indicates the cost or price of something represented as a value per a number of units. The price of eggs for example would be 1.29 per 1 dozen. QDT000000 QDT Response_ Code. Type 1.0 Code Response ContactABIEType is logically derived from UN/CEFACT TBG17 ABIE ContactType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. TermsABIEType is logically derived from UN/CEFACT TBG17 ABIE PaymentTermsType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Amount is the fixed discount anount applied if payed by the DueDateTime for example, $20 off if paid by due date. Percent is the discount applied if payed by DueDateTime. A code for classifying th type of payment terms. Uniquely identifies the exemption along with the agency that defines the excemption. Identifies the exchange rate between two currencies Provides the structure to indicate a Date/Time period where the Time is provided with in the Start and Duration or EndDateTime. LocationABIEType is logically derived from UN/CEFACT TBG17 ABIE LocationType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. CalculationABIEType is logically derived fom the UN/CEFACT TBG 17 ABIE CalculationType, which is defined in the Reusabale Aggregate Business Information Enitity (RUABIE) XML Schema file. Base type for all currency conversions. Is the conversion from one one currency to another currency Identifing the conversion factor and the source in which it was obtained, the date in which the conversion factor was set, and the effective period in which it is to be used. Used to distiguish the rate, based on the nature of the business process of the transaction. (e.g. Daily, End of Period, Corporate.) TimePeriodABIEType is logically derived from UN/CEFACT TBG17 ABIE PeriodType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. QDT000000 QDT State_ Code. Type 1.0 Code State QDT000000 QDT Payment Basis_ Code. Type 1.0 Code Payment Basis CurrencyExchangeABIEType is logically derived from UN/CEFACT TBG17 ABIE CurrencyExchangeType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. The ClassificationCodes that identify a single or hierarchical association of classifications. For example, Pump, Centrifugal would be represented by two Codes, the first one as Pump, the second as Centrifugal. The Sequence attribute of the Code identifies the hierarchical position of the identifier in the case of multi-level codes. The name attribute identifies the name of the corresponding classification level. Possible examples are ROOT, BRANCH, LEAF HazardousMaterialABIEType is logically derived from UN/CEFACT TBG17 ABIE HazardousMaterialType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. CommunicationABIEType is logically derived from UN/CEFACT TBG17 ABIE CommunicationType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. PreferenceABIEType is logically derived from UN/CEFACT TBG17 ABIE PreferenceType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. The OAGIS CoordinateType allows the use of another coordinate system for the use within a warehousing and inventory environment and the geographic coordinat system. Address BaseType provides the information about the address or semantic address of an associated entity. QDT000000 QDT Currency_ Code. Type 1.0 Code Currency QDT000000 QDT Temperature_ Measure. Type 1.0 Measure Temperature Is the tag and information of the new information to be passed. Is the name of the tag for the information being passed. Is the type of the information being passed in the NameValue. DimensionABIEType is logically derived from UN/CEFACT TBG17 ABIE DimensionType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. Contains the sequenced identifier for the associated component or noun. QDT000000 QDT Delivery Point_ Code. Type 1.0 A character string (letters, figures, or symbols) that for brevity and/or languange independence may be used to represent or replace a definitive value or text of an attribute together with relevant supplementary information. Code Delivery Point QDT000000 QDT Country Subdivision_ Code. Type 1.0 A character string (letters, figures, or symbols) that for brevity and/or languange independence may be used to represent or replace a definitive value or text of an attribute together with relevant supplementary information. Code Country Subdivision QDT000000 QDT Country_ Code. Type 1.0 Code Country StatusABIEType is logically derived from UN/CEFACT TBG17 ABIE StatusType as defined in the Reusable Aggregate Business Information Entity (RUABIE) XML Schema file. The purpose of the SyncInvoice is to transmit an invoice from a supplier to a customer. This information is passed in order to keep the customer updated on the number of Invoices they have. The Sync verb is used when the owner of the data is passing or publishing that information or change in information to other software components. This is to be used when the receiver of the SyncBOD does not own the data. This verb is commonly used when mass changes are necessary or when a publish and subscribe mechanism is used in the integration architecture.The purposes of this verb include application integrity and ease of data entry for the business user by enabling a single point of input. The Invoice is used to invoice a customer for goods/services the have been provided. Provides the information that an application may need to know in order to communicate in an integration of two or more business applications. The ApplicationArea is used at the applications layer of communication. While the integration frameworks web services and middleware provide the communication layer that OAGIS operates on top of. Provides the information that an application may need to know in order to communicate in an integration of two or more business applications. The ApplicationArea is used at the applications layer of communication. While the integration frameworks web services and middleware provide the communication layer that OAGIS operates on top of. Information that applies to the entire invoice document. The Header supports summary amounts for line items, charges, taxes and allowances. It also supports itemizing Header level charges, taxes and allowances for use in credit or debit invoices. In this case Line items are not needed. The summary amounts in the Header include the Line level amounts and Header level amounts. In general an Invoice Line can be aligned with Order Lines. The ItemQuantity and Price are used to compute the Total. The Total is a sum of the Total and any Charges, Taxes or Allowances. Identifies characteristics and control identifiers that relate to the application that created the Business Object Document. The sender area can indicate the logical location of the application and/or database server, the application, and the task that was processing to create the BOD. is the date time stamp that the given instance of the Business Object Document was created. This date must not be modified during the life of the Business Object Document. If the BOD is to be signed the signature element is included, otherwise it is not. Signature supports any digital signature that maybe used by an implementation of OAGIS. The qualifyingAgency identifies the agency that provided the format for the signature. This element supports any digital signature specification that is available today and in the future. This is accomplished by not actually defining the content but by allowing the implementation to specify the digital signature to be used via an external XML Schema namespace declaration. The Signature element is defined to have any content from any other namespace. This allows the user to carry a digital signature in the xml instance of a BOD. The choice of which digital signature to use is left up to the user and their integration needs. The BODId provides a place to carry a Globally Unique Identifier (GUID) that will make each Business Object Document instance uniquely identifiable. This is a critical success factor to enable software developers to use the Globally Unique Identifier (GUID) to build the following services or capabilities: 1. Legally binding transactions, 2. Transaction logging, 3. Exception handling, 4. Re-sending, 5. Reporting, 6. Confirmations, 7. Security. Allows the user of OAGIS to extend the specification in order to provide additional information that is not captured in OAGIS. This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document throught the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document. The Open Applications Group will make best efforts to quickly consider all proposed submissions.The USERAREA is always the last element in all components, except where the component has been extended inline. Is an amount not including taxes or charges. In the case of orders, this is typically the Unit Price times the Orde rQuantity. Indicates the total amount of the object associated. This includes the Price and the total of all the charges, allowances and taxes. Identifies the supplier organization/entity of the items or inventory for the associated transaction. In most cases there is one SupplierParty per transaction. i.e. one SupplierParty for a given PurchaseOrder. However in the cases where an transaction Broker is involved there are cases where a single transaction may have different SupplierParties at the line level or in the case of a Catalog for the Catalog. Is the organization that is the end customer of the goods or services being provided in the associated transaction. Identifies the party or location that the payment is to be remitted to or sent to. A generic Party for non-validated or application-validated parties. A work-around for situations where Schema-validation of Parties is not feasible or not desired. Identifies the reason for an activity Is a reference to a PurchaseOrder Is a reference to a contract Identifies the payment term for an Order or Invoice. Supports the abiility to specify an absolute due date, a number of days from a start daye, a percent discount or an absolute discount. A common term like "Net30Days" is explicitly code as either a calculated DueDateTime or a PaymentTermsDateTime and NumberOfDays. Indicates the tax for the object associated. Represents the different Charges that may be applied to the associated document. Identifies the discount or allowance that the Customer is to receive off of the TotalAmount owed as a result of the associated document or sub-portion of a document. Is a SubLine of the InvoiceLine in order to provide a finer grained breakdown of the items being invoiced. The datetime on which the object was last modified The date that document was created within the system of record. Identifies the Item associated with the Line or Detail of a transaction. The item provides the details of the generic Item component information. Identifies the quantity of the associated service or item that is addresses by the component in which the quantity is associated. Unit price of the item for the number of items in the unitCode specified in the PerQuantity elements. In most cases the unitCode of the PerQuantity is the same as the unitCode of the Quantity element above. Indicates that the line is an open item and is not to be included in the document total. Provides the logical location of the server and applications from which the Business Object Document originated. It can be used to establish a logical to physical mapping, however its use is optional. Each system or combination of systems should maintain an external central reference table containing the logical names or logical addresses of the application systems in the integration configuration. This enables the logical names to be mapped to the physical network addresses of the resources needed on the network. Note: The technical implementation of this Domain Naming Service is not dictated by this specification. This logical to physical mapping may be done at execution time by the application itself or by a middleware transport mechanism, depending on the integration architecture used. This provides for a simple but effective directory access capability while maintaining application independence from the physical location of those resources on the network Provides a finer level of control than Logical Identifier and represents the business application that issued the Business Object Document. Its use is optional. The Open Applications Group has not constructed the list of valid Component names. A suggestion for naming is to use the application component names used in the scenario diagrams in section two of OAGIS. Example Components may be Inventory, or Payroll. Describes the business event that initiated the need for the Business Object Document to be created. Its use is optional. Although the Task may differ depending on the specific implementation, it is important to enable drill back capability. Example Tasks may be Receipt or Adjustment. Enables the sending application to indicate the instance identifier of the event or task that caused the BOD to be created. This allows drill back from the BOD message into the sending application. The may be required in environments where an audit trail must be maintained for all transactions. Is an option controlled by the Sender business application. It is a request to the receiving application to send back a confirmation BOD to the sender. The confirmation Business Object Document may indicate the successful processing of the original Business Object Document or return error conditions if the original Business Object Document was unsuccessful. The confirmation request has the following valid values: Never - No confirmation Business Object Document requested OnError - OnError send back a confirmation Business Object Document only if an error has occurred Always - Always send a confirmation Business Object Document regardless Identifyies the authorization level of the user or application that is sending the Business Object Document Message. This authorization level being recognized be the receiving system indicates what can be done on the receiving system(s). Is the primary document id for the document associated. Is the alternate document id for the associated document. The Attachment represents binary data files that may be included within a BOD. These files replace the paper specifications and drawings attached to a BOD definition to clearly communicate design requirements. This Data Type is optional. Attachment usage is further defined by its position. Identifies the sales contact and sales department/organization that is responsible for the sale that the instance is associated. Identifies the contact information of the person, organization, department, or group that is to shipping the contents communicated by the document or line. Identifies the contact information of the person, organization, department, or group that is responsible for customer service. Identifies the contact information for the requesting person, organization, department, or group on the associated document or line. Identifies the contact information of the person, organization, department, or group that planned for the timing of the exchange of goods/services that this document is associated at the document or line level. Identifies the contact information for the buying person, organization, department, or group on the associated document or line. Identifies the contact information of the person, organization, department, or group that is to receive the contents communicated by the document or line. Identifies the Release Number in the case of Blanket POs Is the Line Number of the given Line Coponent within the document. LineNumbers are assigned by the sending system. Is the ScheduleLineNumber of a particular item of interest for the given DocumentReference. The Line Number is of the primary DocumentId of the sender indicated by the DocumentId under DocumentIds. Is the SublineNumber of a particular item of interest for the given DocumentReference. The Line Number is of the primary DocumentId of the sender indicated by the DocumentId under DocumentIds. Identifies the Terms i.e. the time and number of payments and the amount or percentage of the payment. Identifies the Discount the time and number of payments and the amount or percentage of the discount from the payment. Identifies the Peanlty what happen when the time and number of payments and the amount or percentage of the penalty to add to the payment. Contains the set of possible identifiers for an associated Party. Identifies the Name of the object in which associated. The location of a thing, as captured by an address (or addresses), GPS Coordinates, and/or in relation to other locations. Contacts are the point of communication with the given party. In the case of an organization it may be the requestioner, the buyer, customer service, etc. This is the Account Identification assigned to the customer (Payer) by the Supplier (Payee) Is the Code to indicate the status for the Noun or Component in which the Status Component occurs. Is the Identifiers of the given instance of an entity within the scope of the integration. The providedBy attribute identifies the party that provided or knows this party by the given identifier. Is the base amount from which the charge/allowance is derived. Is the base quantityfrom which the charge/allowance is derived. Allows the sender to indicate how the Charge/Allowance was calculated. This is used to represent the tax amount in the currency of the taxing authority in addition to the transactional tax amount which may be in a different currency. The monetary value of the object in which the amount is associated Identifies the exchange rate between two currencies. For the transaction in which this is associated. An explicit period of time for the bucket. Allows an instance of an item to carry any radio frequency identifier (RFID) that maybe used by a supply chain. Unique serial number assigned to the given item instance by the manufacturer. Element for the communication of all codes. This is the DateTime the associated object is made effective Is the revision of the semantically named document. The combination of the ID and its revision uniquely identifies the associated entity. The number of months beyond the Billing Date in which payment is due. The daywithin the ProxMonth beyond the Billing Date in which payment is due. Identifies if the Item is a Service This identifies the classification of an entity. An entity may be classified into mulitple groups for different reasons. Examples of Classification include Commodity Codes, Freight Classifications, Product Line classifications and so on. Suggested Values are COMMODITY, FREIGHT, PRODUCTLINE Identifies the specification of an entity. Provides the Hazardous Material Code and description. Identifies the Packaging information for a given item. Note: The UPC here is the UPC of the packaging for a given item. Indicates the PerQuantity side of this Amount. Typically, this value is 1 with a uom of each, meaning that, e.g., a UnitPrice with the Amount 1.29 would be the price per each or simply $1.29 each. For pricing wire, the UnitPrice Amount might be $7.00 with a PerQuantity of 100 and a uom of LinearFeet, meaning the unit price would be $7 per 100 linear feet. Indicates when the status change occured. Is the position or designation of the pesron with whom associated within the given organization. Examples are Director, Software Engineer, Purchasing Manager etc A text description of the responsibility of the associated entity. The date and time that the production order is to be completed. The date and time when the payment terms go into effect. Used in conjunction with NumberOfDays Indicates the duration of time as represented by ISO 8601. Where the value space is a six dimensional space where the coordinates designate the Gregorian year, month, day, hour, minute, and second. The number of seconds can include decimal digits to arbitary pecision. Indicates a percentage of discount that is available against a price The penalty rate (percentage) charged for late payment. Indicates the type of the object in which assoicated. Is the primary item Identifier associated with the given item within the scope of the given integration as provided by the Party or entity that has created this document instance. Is the identifier provided by the customer for the item. Is the identifier provided by Manufacturer for the Item. One example may be the model number. Is the identifier provided by the supplier for the item. Allows an instance of an item to have a UPC identifier associated. Allows an instance of an item to communicate the ElectronicProductCodeID that it was assigned. The ElectronicProductCodeID is one of the major RadioFrequency Identifiers used. Allows the data to be embedded directly into the BOD instance. Indicates the name of the File being referenced. Allows a reference to an ISBN. Identifies the type of the file type of the attachment. Specifies how big the file is. Is the title of the person. For example Dr.. Identifier for a business or individual provided by the government. This maybe a FIIN, Social Security Number, or Drivers License Number to name a few. Identifier for business provided by Dun and Bradstreet. The Bank Identifier Code is a unique address which, in telecommunication messages, identifies precisely the financial institutions involved in financial transactions. Is the multiplier to convert the source units to the target units. (e.g.) The conversion of one currency to another currency monitary amount in the from currency is multiplied by the CalculationRateNumeric to calcultate the monitary amount in the to currency. Another example maybe the conversion between units of measure. Idenfifies the source that brought the associated entity. Indicates the time period in which the associated component is effective. Start timestamp indicating the starting point of the event. Is the ending timestamp of the event. Represents the Properties or Features of the associated entity The source Currency Code for the monetary amount to be converted. Specifies the unit base of the source currency for currencies with small denominations. The target Currency Code for the monetary amount to be converted. Specifies the unit base of the target currency for currencies with small denominations. Identifies the date in which the conversion factor was set by the Issueing agency. Used to identify a Medical First Aid Guide (MFAG) for hazardous substance. Is the Technical name of the associated entity. The placard endorsement that is to be shown on shipping papers for hazardous materials. Can also be used for the number of the orange placard (lower part) require on transport. The placard notation that is to be shown on shipping papers for hazardous materials. Can also be used for the number of the orange placard (upper part) require on transport. Specifies the level of marine pollution for this hazardous substance. A code identifying the Inhalation Toxicity Hazard Zone for the hazardous substance, this is generally identfied by a government agency in the United States this is provided by the US Department of Transportation. Temperature of the associated entity. FlashpointTemperature is related to hazadous substances or goods, indicates the temperature at which the associated substance of goods become flammable, explossive or toxic.. The primary entry route by which the Hazardous Material gains access to the human body. Provides the dimensions of the associated component. Is the number of instances of the item in the unit of measure contained with in the package. Is the maximum number of instances of an item in the unit of measure that maybe contained within the package. Identifies the channel in which the associated entity comes. Code identifying the usage of the contact point e.g. business, private, etc. The country dialing code for a communication number. The area dialing code for a communication number. The commication number, not including country dialing or area dialing codes. The extension of the assoicated communication number. The text that permits access to the electronic network of the associated communication number such as telephone network, for example 9, *70. Indicates that the associated entity preferrs HTML format. Is a message to the reader about the object associated. A value expressing the value of a Sequence. Is the tag and information of the new information to be passed. Is the value and unit of measure in the z-axis in a thrre dimensional system. Examples of this maybe the Altitude in the case of a map of the world, or the height or shelf in a rack system in the case of a manufacturing or warehouse facility. Is the system in which the userid applies. Format Code indicates the format of the address. Examples are US Military, US Formatted Address, European Formatted Address etc. There is no intent to decode the address formats - these are informational only. No list of valid values exists or is proposed here. The name of the person or organization that the associated entity is intended. The name that the associated entity is sent by. The Number of the building or house on the street that identifies where to deliver mail. For example, Building 300 on Standards Parkway The building or house name on the street that identifies where to deliver mail The Street Name where the building/ house is located Identifies the apartment number or office suite. The floor where the housename is located Identifies a Post Office Box number Identifies the Dock or the Mail Stop or Lane or any other specific Delivery Point. Qualifies the further division of the City, example a city may have many districts or Boroughs. The type attribute identifies the type of this entity e.g. City, Borough etc, and there is a pre-defined list of types supported, with the ability to add new ones as necessary Identifies the town or the city Qualifies the further division of the Country. These may be Districts, Regions, States, Provinces etc. A possible list of values is as specified in ISO 3166-2. The type attribute identifies the type of this e.g. District, Region etc, and there is a pre-defined list of types supported, with the ability to add new ones as necessary Country in which the Address is in. A possible list of values is as specified in ISO 3166-2. Postal Code of the Address. Indicates the status of the associated object by providing the Status Code along with a description and when the status is effective. Indicates the width of an object Indicates the length of an object Indicates the Height of an object Provides the Identifier(s) of the document being communicated. Uniquily identifies a Document within an organization. Typically there is only an ID for a document within one system. However, with the use of different business applications there maybe different ids assigned to the same document within an organization from the different systems and in the case of B2B transactions different businesses may have different Identifiers for the same document. This construct is designed to allow for these different identifications. Common Free Form Text elements that occur together. Common References to DocumentReferences and Attachements Contains the Item IDs for an associated item. Contain the ids for a given party. These ids may be assigned by multiple organizations. Indicates the ID of the associated component or noun. QDT000000 QDT Month_ Date. Type 1.0 A particular point in the progression of time together with the relevant supplementary information. Provides the XML Schema simpleType that allows either just the Date or the Date and Time to be provided in the elements that are based on this type and/or types that use this as their base. Date Month