Business-cXML
view release on metacpan or search on metacpan
t/xml-catalog/cXML-1.2.036/cXML.dtd view on Meta::CPAN
<!ELEMENT AttachmentReference (Name, Description, InternalID, URL?)>
<!ATTLIST AttachmentReference
length %uint; #IMPLIED
version %string; #IMPLIED
>
<!--
Price per unit of item. Optional Modifications
(changes due to discounts or fixed amount) may be provided.
The Money element indicates the final amount after applying the
Modifications.
-->
<!ELEMENT UnitPrice (Money, Modifications?)>
<!--
Reference to an earlier document (for example, OrderRequest). In a
StatusUpdateRequest, this element identifies the purchase order to be
updated.
payloadID
A unique identifier for the document. Copied directly from the
cXML element of the original document.
-->
<!ELEMENT DocumentReference EMPTY>
<!ATTLIST DocumentReference
payloadID %string; #REQUIRED
>
<!ELEMENT InternalID (#PCDATA)> <!-- string -->
<!ATTLIST InternalID
domain %string; #IMPLIED
>
<!-- ====
Common to most variants of the PunchOut transaction set. Defined here
to be easily shared between multiple DTD files without requiring
inclusion of Transaction.mod in all of them.
All of the PunchOut transaction sets include an originating Request
(ProviderSetupRequest for example), relatively simple Response
(PunchOutSetupResponse for example) and final Message
(ProviderDoneMessage or PunchOutOrderMessage). The Request and
Response comprise a back-end transaction between two cooperating
applications that wish to extend an interactive session from one to the
other. The Request provides the destination application with
authentication, identification and other setup information. The
Response provides the originating application with a unique starting
location for the interactive (HTML) session at the destination system.
After receiving a Response of this type, the originating application
redirects the user's browser to the provided location. (For some
non-HTML applications, opening a new browser window at that location
may be more appropriate.) The destination system eventually provides
an HTML form to the user's browser. This form submits the final
Message to close the remote session, return that user to the
originating application and carry any required information back to the
originating application.
==== -->
<!--
OriginatorCookie - Identification of a specific PunchOut session. Used
in both originating Request and later Message that returns user to
originating application.
Note: The BuyerCookie element used in a 'regular' PunchOut transaction
(defined in Transaction.mod) is of type ANY. That does not seem
useful. The string required below better matches the needs for this
element. Future transactions similar to the PunchOut transaction will
use this element.
-->
<!ELEMENT OriginatorCookie (#PCDATA)>
<!--
BrowserFormPost - Location to which the user's browser must submit the
final Message. This location (carried in the originating Request) does
not need to be specific to a PunchOut session since the
OriginatorCookie is returned in the Message.
-->
<!ELEMENT BrowserFormPost (URL)>
<!--
SelectedService - Identification of a service offered by this provider
and requested in this transaction. Used only in the originating
Request.
-->
<!ELEMENT SelectedService (#PCDATA)>
<!--
StartPage - Location to which the user's browser must be redirected to
begin the interactive portion of the session at the remote site. The
destination system returns this information in the Response document.
This location must be specific to a particular session. It is
effectively a one time key, providing authenticated entry into the
destination system.
-->
<!ELEMENT StartPage (URL)>
<!--
ReturnData - Any information the originator must know about the
completed operation at the provider site. The ReturnValue is for
applications; the Name is for human consumption (direct presentation in
the User Interface of the application). Where appropriate for the
possible services, this element may appear in the final Message for a
PunchOut session.
name
An identifier for the data returned. Provides a meaning for the
contents of a ReturnData element.
-->
<!ELEMENT ReturnData (ReturnValue, Name)>
<!ATTLIST ReturnData
name %string; #IMPLIED
>
<!ELEMENT ReturnValue (#PCDATA)>
<!--
Defines a time range. The start and end can be unbounded
startDate
The starting date of the time range
endDate
The ending date of the range
-->
<!ELEMENT TimeRange EMPTY>
<!ATTLIST TimeRange
startDate %datetime.tz; #IMPLIED
endDate %datetime.tz; #IMPLIED
>
<!--
Defines a period in time.
startDate
The starting date of the period
endDate
The ending date of the period
t/xml-catalog/cXML-1.2.036/cXML.dtd view on Meta::CPAN
-->
<!ELEMENT Followup (URL)>
<!-- PunchOut* Elements -->
<!--
Definition of a PunchOut Setup Request. This is the data that is sent
to the external system that the procurement application is going to
extract catalog data from.
The BrowserFormPost element contains the URL we would like the browser
re-directed to when the PunchOut shopping experience is finished (where
the PunchOutOrder message should be returned).
-->
<!-- PurchaseRequisitionRequest* Elements -->
<!--
Definition of Purchase Requisition. This is the data that is sent from the Buyer
to another buyer system.
-->
<!ELEMENT PurchaseRequisitionRequest (PurchaseRequisition)>
<!ELEMENT PurchaseRequisition (PurchaseRequisitionHeader, ItemIn*)>
<!--
Header of an Purchase Requisition.
requisitionID
The buyer system requisitionID for this request. This is an internal
Buyer unique number.
requisitionVersion
The buyer system requisition version number for this request. Relevant when
the PurchaseRequisitionRequest represents a change Requisition request. The version
number for the original document should be 1 and should be incremented by 1 for
each subsequent version (2,3,4...).
requisitionDate
The date and time the Requisition request was created.
type
The type of the Requisition request. Defaults to "new".
The contained DocumentReference element would appear in a document only
when the type is "update" or "delete". In that case, the
DocumentReference would reference the most recent PurchaseRequisitionRequest document
for the order. For example when an requisition is created, updated and then
deleted, the final document should contain a DocumentReference
referring to the PurchaseRequisitionRequest with type="update". That document would,
in turn, refer to the original (type="new") PurchaseRequisitionRequest document.
-->
<!ELEMENT PurchaseRequisitionHeader (Shipping?, Tax?, Total?, ShipTo?, BillTo?, Contact*, Comments?,
DocumentReference?, Extrinsic*)>
<!ATTLIST PurchaseRequisitionHeader
requisitionID %string; #IMPLIED
requisitionDate %datetime.tz; #IMPLIED
type (new | update | delete) "new"
requisitionVersion %number; #IMPLIED
>
<!ELEMENT PunchOutSetupRequest (BuyerCookie, Extrinsic*, BrowserFormPost?,
Contact*, SupplierSetup?, ShipTo?,
SelectedItem?, ItemOut*)>
<!ATTLIST PunchOutSetupRequest
operation (create | inspect | edit | source) #REQUIRED
>
<!ELEMENT BuyerCookie ANY> <!-- any valid XML data -->
<!ELEMENT SelectedItem (ItemID)>
<!ELEMENT SupplierSetup (URL)>
<!ELEMENT PunchOutSetupResponse (StartPage)>
<!--
Definition of a PunchOut Order Message. This is the data that is sent
back to the procurement application from the external system that the
PunchOut Request was targeted at.
-->
<!ELEMENT PunchOutOrderMessage (BuyerCookie, PunchOutOrderMessageHeader,
ItemIn*)>
<!--
Header of a PunchOut Order Request. This is the data that is sent from
the supplier to transfer the supplier acquired shopping basket back to
the buyer system.
operationAllowed
Highest operation allowed on the PunchOut shopping basket.
"create" allows only later OrderRequest operations on these items.
"inspect" adds a PunchOutSetupRequest with operation="inspect".
And, "edit" allows operation="edit" in that later Setup request.
quoteStatus
"pending" - Identifies that the transaction is still pending
"final" - Identifies that the transaction is complete
-->
<!ELEMENT PunchOutOrderMessageHeader (SourcingStatus?, Total, ShipTo?, Shipping?, Tax?, SupplierOrderInfo?)>
<!ATTLIST PunchOutOrderMessageHeader
operationAllowed (create | inspect | edit) #REQUIRED
quoteStatus (pending|final) "final"
>
<!-- ====
Other small Request elements.
==== -->
<!--
Request to update the status of an earlier transaction.
DocumentReference
A reference by payloadID to a cXML document to be updated. This
element can be omitted only when InvoiceStatus is specified and
the InvoiceStatus contains InvoiceIDInfo.
-->
<!ENTITY % cxml.statuses "(PaymentStatus |
SourcingStatus | InvoiceStatus | DocumentStatus | IntegrationStatus)">
<!ELEMENT StatusUpdateRequest (DocumentReference?, Status, (%cxml.statuses;)?, Extrinsic*)>
<!--
Status Update for Document Status
DocumentInfo
ID of a document entry known to the system. This attribute is used to reference a document in StatusUpdateRequest when DocumentReference is omitted.
Comments
Comments associated with the status update.
type
Type of the document status.
-->
<!ELEMENT DocumentStatus (DocumentInfo?, ItemStatus*, Comments*)>
<!ATTLIST DocumentStatus
type %string; #REQUIRED
>
<!--
When a StatusUpdateRequest is send with a DocumentStatus, then you could send more detailed information about the original item.
t/xml-catalog/cXML-1.2.036/cXML.dtd view on Meta::CPAN
<!ELEMENT SupplierDataResponse (Supplier)>
<!--
Reference to the Subscription Version. To be used with InternalID of a catalog.
vesionNumber
To uniquely identify a catalog with the given InternalID and versionNumber.
-->
<!ELEMENT SubscriptionVersion EMPTY>
<!ATTLIST SubscriptionVersion
versionNumber %uint; #REQUIRED
>
<!--
Catalog subscription status from buyer.
-->
<!ELEMENT SubscriptionStatus (Comments?)>
<!ATTLIST SubscriptionStatus
status (received | validation_error | validated | approved | rejected | activated | deactivated | deleted | changed) #REQUIRED>
<!--
SubscriptionStatusUpdateRequest
A request to update the subscription status of a Catalog.
InternalID
ID of the catalog.
SubscriptionStatus
Element representing the status updates to the catalog.
-->
<!ELEMENT SubscriptionStatusUpdateRequest (InternalID, SubscriptionVersion?, SubscriptionStatus)>
<!--
For cXML license agreement information, please see
http://www.cxml.org/home/license.asp
$Id: //ariba/cxml/release/schema/1.2.36.1+/Modules/Provider.mod#1 $
-->
<!-- ====
Provider* transaction is used to visually integrate an application with
a UI provided by a service provider.
==== -->
<!--
ProviderSetupRequest
The originating application would provide the BrowserFormPost location
only if it wished the provider site to display a "Done" button or
would like information (at least Status) returned at the end of the
interactive session. Inclusion should lead to a ProviderDoneMessage
from the provider at the end of a session.
The originating application would provide the Followup location if it
wished the provider to provide information about later status changes
in the service (after the end of a particular Provider session). This
applies only when the initial status (transmitted via a
ProviderDoneMessage) was an interim value.
-->
<!ELEMENT ProviderSetupRequest (OriginatorCookie,
(BrowserFormPost, Followup?)?,
SelectedService, Extrinsic*)>
<!--
ProviderSetupResponse
-->
<!ELEMENT ProviderSetupResponse (StartPage)>
<!--
ProviderDoneMessage
-->
<!ELEMENT ProviderDoneMessage (OriginatorCookie, ReturnData*)>
<!--
For cXML license agreement information, please see
http://www.cxml.org/home/license.asp
$Id: //ariba/cxml/release/schema/1.2.36.1+/Modules/DataAvailable.mod#1 $
-->
<!--
DataAvailable message.
-->
<!ELEMENT DataAvailableMessage (InternalID)>
<!--
For cXML license agreement information, please see
http://www.cxml.org/home/license.asp
$Id: //ariba/cxml/release/schema/1.2.36.1+/Modules/DataRequest.mod#1 $
-->
<!--
Definition of a DataRequest.
-->
<!ELEMENT DataRequest (InternalID)>
<!--
DataResponse. Contains the attachments if any for this response.
Only a successful response to a download attempt would include this element
-->
<!ELEMENT DataResponse (Attachment+)>
<!--
For cXML license agreement information, please see
http://www.cxml.org/home/license.asp
$Id: //ariba/cxml/release/schema/1.2.36.1+/Modules/CatalogUpload.mod#1 $
-->
<!--
Contain all the information related to the catalog upload, the same
functionality as the catalog upload provided by supplier.ariba.com
-->
<!ELEMENT CatalogUploadRequest (CatalogName, Description, Attachment,
Commodities?, AutoPublish?, Notification)>
<!ATTLIST CatalogUploadRequest
operation (new | update) #REQUIRED
>
<!--
CatalogName is the name of the uploaded/published catalog. The
name is unique per supplier, and it can be defined in the
different languages
-->
<!ELEMENT CatalogName ( #PCDATA )> <!-- string -->
<!ATTLIST CatalogName
xml:lang %xmlLangCode; #REQUIRED
>
( run in 2.319 seconds using v1.01-cache-2.11-cpan-5837b0d9d2c )