Business-cXML

 view release on metacpan or  search on metacpan

t/xml-catalog/cXML-1.2.036/cXML.dtd  view on Meta::CPAN


    UnitRate
        The single unit rate.

    Description
        Textual description for the rate.  For example, hotel nightly rate.

    Quantity
        The quantity.  For example, a 4 nights stay at a hotel will
        have quantity set to 4 with UnitofMesure in UnitRate set to Day.
-->
<!ELEMENT Rate (Total, UnitRate, Description?)>
<!ATTLIST Rate
    quantity    %r8;    #REQUIRED
>

<!--
    The total for something.
-->
<!ELEMENT Total (Money, Modifications?)>

<!--
    Tolerances for price, quantity, delivery date.
-->
<!ELEMENT Tolerances (QuantityTolerance?, PriceTolerance?, TimeTolerance?)>

<!ELEMENT QuantityTolerance (Percentage | Value)>

<!ELEMENT PriceTolerance (Percentage | Money)>

<!--
    Defines a certain amount of days which is used to check if a concrete
    delivery date is within the tolerance regarding the requested
    delivery date.

    limit
        Amount of time in 'type' relative to the requested delivery date is it allowed to deliver?
    type
        Specifies how the limit should be interpreted.
-->
<!ELEMENT TimeTolerance EMPTY>
<!ATTLIST TimeTolerance
    limit %int; #REQUIRED
    type  (minutes | hours | days | weeks) "days"
>

<!-- Upper tolerances defines an upper limit -->
<!ELEMENT Upper (Tolerances)>
<!-- Lower tolerances defines a lower limit -->
<!ELEMENT Lower (Tolerances)>

<!ELEMENT TaxAmount (Money)>

<!ELEMENT TaxableAmount (Money)>

<!--
    One language-specific string for the location of tax,
    e.g. London, Canada, California, etc.

    xml:lang
        The language or locale in which the location of tax is written.
-->
<!ELEMENT TaxLocation (#PCDATA)>              <!-- string -->
<!ATTLIST TaxLocation
   xml:lang              %xmlLangCode;         #REQUIRED
>

<!--

    TriangularTransactionLawReference indicates the relevant law as
    titled for the local jurisdiction in the scenario of a triangular
    transaction.  ex: Triangulation, article 28c,E paragraph 3 of the
    6th EU VAT Directive

    xml:lang
        the language in which the law reference is written.
-->
<!ELEMENT TriangularTransactionLawReference (#PCDATA)>
<!ATTLIST TriangularTransactionLawReference
    xml:lang   %xmlLangCode;    #REQUIRED
>

<!--

    If you claim an exemption from taxes, 
	some tax authorities, such as Portugal SAF-T, 
	require you to specify an exemption code and exemption reason.
	
	exemptCode
        specifies the code against which the tax is exempted.
-->

<!ELEMENT TaxExemption (ExemptReason?)>
<!ATTLIST TaxExemption
    exemptCode    %string;      #REQUIRED 
>

<!--

	ExemptReason
		specifies the exemption reason for zero tax.
		
		This would have no relation with the existing "exemptDetail" attribute.
		Existing attribute "exemptDetail" will not be ignored and this will also will be kept along with the new element "ExemptReason".

	xml:lang
        the language in which the exemption reason is written.
				
-->

<!ELEMENT  ExemptReason  (#PCDATA) >
<!ATTLIST  ExemptReason
    xml:lang   %xmlLangCode;    #REQUIRED 
>


<!--
    Defines details of one type of tax.

    TaxableAmount
       The taxable amount.

t/xml-catalog/cXML-1.2.036/cXML.dtd  view on Meta::CPAN

		allowed            - allows to send OrderConfirmation for this line item, regardless of current rule settings.
		notAllowed         - does not allow to send OrderConfirmation for this line item.
		requiredBeforeASN  - requires OrderConfirmation before ASN could be created.
-->
<!ELEMENT OCInstruction (Lower?, Upper?)>
<!ATTLIST OCInstruction
value     ( allowed | notAllowed | requiredBeforeASN )     #REQUIRED>


<!ELEMENT ASNInstruction (Lower?, Upper?)>
<!ATTLIST ASNInstruction
    value       (allowed | notAllowed)  #REQUIRED>

<!--

	Its purpose is to specify if an Invoice Item could be created or not for a line item.
	
	allowed            - allows to create an Invoice Item for this line item, regardless of current rule settings.
	
	notAllowed         - does not allow to create an Invoice Item for this line item, regardless of current rule settings.

    verificationType   - goods receipt based invoice verification
        The buyer can decide at order item level whether to activate goods-receipt-based invoice verification.
        If goods-receipt-based invoice verification is active for a particular order item, each invoice item can then be matched up uniquely with the goods receipt item. It makes sense to work with goods-receipt-based invoice verification when you ex...
-->
<!ELEMENT InvoiceInstruction (TemporaryPrice?)>
<!ATTLIST InvoiceInstruction
    value       (isERS | isNotERS | allowed | notAllowed)  #IMPLIED
    verificationType (goodsReceipt)                        #IMPLIED>

<!--
This flag indicates if pricing information is temporary or final. If set to true at the order item level, pricing for the item is considered temporary and the supplier cannot invoice the line item.
If set to true at the order header level, pricing is considered temporary for the entire purchase order and the supplier cannot invoice against any item on the order.
-->    

<!ELEMENT TemporaryPrice EMPTY>
<!ATTLIST TemporaryPrice value (yes | no) #REQUIRED
>

<!--

	Its purpose is to specify if a SES Item could be created or not for a line item.
	
	allowed            - allows to create SES Item for this line item, regardless of current rule settings.
	
	notAllowed         - does not allow to create SES Item for this line item, regardless of current rule settings.
		
-->
<!ELEMENT SESInstruction EMPTY>
<!ATTLIST SESInstruction
    value       (allowed | notAllowed)  #REQUIRED>

<!--
    Either or both a textual description and codes about a hazard inherent
    in an item or for the overall order or shipment.  The overall hazards
    may be due either to identical hazards for all items or hazards
    inherent in shipping various products together.

    The contained Description element list (if provided) should include
    detailed handling requirements.  Elements in this list may appear in
    any order.  A description locale (Description@xml:lang attribute value)
    must not appear more than once in a Hazard element.  When more than one
    Description element is present, all must contain translations of a
    common description.

    Classification elements may appear in any order.  A classification
    domain (Classification@domain attribute value) must not appear more
    than once in a Hazard element.

    All listed Classification elements and the Description (if provided)
    must relate to a single hazard.  Additional hazards must use separate
    Hazard elements.

    The following Classification domains are expected in this context:
        UNDG - United Nations Dangerous Goods
        IMDG - International Marine Organization Dangerous Goods
        NAHG - North American Hazardous Goods
-->
<!ELEMENT Hazard ((Description+, Classification*) | Classification+)>

<!--
PlannedAcceptanceDays: Number of days the buyer schedules for the inspection of goods after receiving them.
-->
<!ELEMENT PlannedAcceptanceDays  (#PCDATA)> <!-- number --><!--
    For cXML license agreement information, please see
    http://www.cxml.org/home/license.asp

    $Id$
-->

<!--
    This element captures travel information.  It could be one of four
    types: air, car rental, hotel or rail.

    AirDetail
        Air travel detail.

    CarRentalDetail
        Car rental detail.

    HotelDetail
        Hotel detail.

    RailDetail
        Rail detail.

    PolicyViolation
        List of policy violations (if any) associated with this
        travel line item.

    Comments
        Top level comments for this travel line item (if any).  This
        is not the policy violation comment but a top level comment
        given by the user for this travel line item while in Travel
        Booking Provider's web site.

    TermsAndConditions
        List of Terms and conditions (if any) associated with this
        travel line item.

    confirmationNumber

t/xml-catalog/cXML-1.2.036/cXML.dtd  view on Meta::CPAN

    Additional information related to this payment terms.

    paymentTermCode
    This is the payment term code defined by buyers in ERP.

-->
<!ELEMENT PaymentTerms (PaymentTerm*, Description?, Extrinsic*)>
<!ATTLIST PaymentTerms
    paymentTermCode        %string;         #REQUIRED
>

<!--
    Defines a payment term in an invoice or order.  This deprecates the
		InvoiceDetailPaymentTerm previously defined.  Payment term can be the 
		net term (without discount) or discount term (with discount).

    payInNumberOfDays
        The number of days after invoice effective date for the invoice to be paid.

    Discount
	 	The percentage or amount of the discount term.  This element should be omitted
	 	if the payment term is a net term.
    Extrinsic
	Additional information related to this payment term.
-->
<!ELEMENT PaymentTerm (Discount?, Extrinsic*)>
<!ATTLIST PaymentTerm
    payInNumberOfDays        %uint;         #REQUIRED
>

<!--
    The list of valid payment types.
-->
<!ENTITY % cxml.payment  "PCard">
<!ELEMENT Payment (%cxml.payment;)>

<!--
    Defines an accounting segment.  Segment is an older, deprecated way to
    transport this information.

    type
        The accounting type of this segment.

    id
        The unique key of this Segment against the type.

    description
        Textual description of the Segment. For human readability.
-->
<!ELEMENT Segment EMPTY>
<!ATTLIST Segment
    type         %string;  #REQUIRED
    id           %string;  #REQUIRED
    description  %string;  #REQUIRED
>

<!--
    Defines an accounting segment.  AccountingSegment is the newer, better
    way to transport this information.  Name corresponds to the type
    attribute of Segment; Description corresponds to description.  Both add
    required locale attributes to the strings.

    id
        The unique key of this Segment against the type.
-->
<!ELEMENT AccountingSegment ( Name, Description )>
<!ATTLIST AccountingSegment
    id           %string;  #REQUIRED
>

<!--
    An accounting object.  Use of the Segment element here is deprecated.

    name
        The name of the object containing the specified accounting segments.
-->
<!ENTITY % cxml.accounting  "( Segment+ | AccountingSegment+ )">
<!ELEMENT Accounting (%cxml.accounting;)>
<!ATTLIST Accounting
    name  %string;  #REQUIRED
>

<!--
    A charge against an Accounting element.
-->
<!ELEMENT Charge (Money)>

<!--
    The combination of a Charge against an Accounting Element. A distribution
    represents the breakdown of one overall amount into sub-amounts.
-->
<!ELEMENT Distribution (Accounting, Charge)>



<!-- Item Elements -->
<!--
    The representation of a line item as it needs to be for sending to a
    supplier. The item can refer to a MasterAgreement in itself.


    quantity
        How many items are desired. Supplier and Commodity level items in an order of type
	"blanket" will use a default value of "1". The quantity in this case will not be
	used to compute the sub total. The MaxAmount in the BlanketItemDetail will be 
	used to indicate any line level amounts.
    lineNumber
        Position (counting from 1) of this item in an order.  Used to
        maintain a reference between items in create and update OrderRequest
        documents.
    requisitionID
        The buyers system requisition id for this line item. It might be the
        same as orderID, and it might not be included at all.  Must not be
        included if requisitionID is specified in the OrderRequestHeader.
    requestedDeliveryDate
        The date this item was requested for delivery.
    agreementItemNumber 
        The corresponding Item Number of the Item in the Master Agreement if this is 
	a 'release' order item.
    parentLineNumber
	    lineNumber of the parent line item in the order.

t/xml-catalog/cXML-1.2.036/cXML.dtd  view on Meta::CPAN

    For example,
    <ExternalDocumentType documentType="ZNB">
        <Description xml:lang="en">Standard Purchase Order</Description>
    </ExternalDocumentType>
-->

<!ELEMENT ExternalDocumentType (Description?)>
<!ATTLIST ExternalDocumentType        
	documentType    %string;    #REQUIRED
>

<!--
	Industry specific header information  

	ReferenceDocumentInfo 
	Details of referenced document 

	Priority
	Priority indicator, it is used to drive the priority of the orders for the suppliers
-->
<!ELEMENT OrderRequestHeaderIndustry (ReferenceDocumentInfo*, Priority?, ExternalDocumentType?)>

<!--   Industry specific item information 
	ReferenceDocumentInfo 
	It contains the details of referenced document

	Priority
	Priority Indicator used to drive the priority of the item ordered by the buyer.

    QualityInfo
    The representation of the quality information of a line item.

	planningType
	To specify different production planning strategies. Following are possible strategies:
	MTO: Make to Order
	MTS: Make to Stock
	ATO: Assemble to Order
	CTO: Configure to Order
-->
<!ELEMENT ItemOutIndustry (ItemOutRetail?, ReferenceDocumentInfo*, Priority?, QualityInfo?)>
<!ATTLIST ItemOutIndustry
    planningType	 ( MTO | MTS | ATO | CTO )	#IMPLIED
>

<!--    Retails industry item information 
	PromotionVariantID
	Used when only one or some variants of an article are promoted

	PromotionDealID 
	Number assigned by a supplier to a special promotion activity. Promotions affect the forward planning/ordering process (and the related pricing)
-->
<!ELEMENT ItemOutRetail (PromotionVariantID?, PromotionDealID?)> 

<!--
    Details about the packaging of this line item.

    Zero or more PackagingCode elements may appear in the Packaging
    element.  Each PackagingCode must contain a single string corresponding
    to the packaging for this item.  When multiple PackagingCode elements
    appear, all must describe the same packaging in different languages or
    locales.  (No two PackagingCode elements may have the same xml:lang
    attribute.)  Elements in such a list may appear in any order.

    The dimensions mentioned in the Dimension element list may appear in
    any order.  A particular dimension (Dimension@type attribute value)
    must not appear more than once in a Packaging element.
    
    	Description
        	The Package description.

	PackagingLevelCode
	Describes the level (inner, outer, intermediate) for packages.
	
	PackageTypeCodeIdentifierCode 
	Unique ID of packaging material. This helps receiving side for unloading and storage.
	
	ShippingContainerSerialCode
	Serial number of a package that helps to identify package during transportation and inventory.
    
    ShippingContainerSerialCodeReference
    Reference from a package with shipping code to the shipping code of the next higher package level. It references the parent ShippingContainerSerialCode.
	
	PackageID
	Package related IDs.
	
	ShippingMark
	Information about packaging proposals and packaging hierarchy.
	
	OrderedQuantity
	The quantity ordered in purchase order.
	
	DispatchQuantity
	The dispatch quantity in package.
	
	FreeGoodsQuantity
	Quantities delivered but not charged. 
	
	QuantityVarianceNote
	Quantity Variance Note gives detailed information about partial delivery.
	
	BestBeforeDate
	Gives the best before date for all goods related to food, drugs, chemicals and others.

-->
<!ELEMENT Packaging (((PackagingCode+, Dimension*) | Dimension+), Description?, 
				PackagingLevelCode?, PackageTypeCodeIdentifierCode?, ShippingContainerSerialCode?, 
                ShippingContainerSerialCodeReference?,
				PackageID?, ShippingMark*, OrderedQuantity?, DispatchQuantity?, 
				FreeGoodsQuantity?, QuantityVarianceNote?, BestBeforeDate?, Extrinsic*)>

<!--
    One language-specific code for the packaging of this item.  Values such
    as "pallet", "skid" and "truck load" may be appropriate (for an
    English-based locale).

    xml:lang
        The language or locale in which the PackagingCode content (the
        value of the code) is written.
-->
<!ELEMENT PackagingCode (#PCDATA)>             <!-- string -->
<!ATTLIST PackagingCode
    xml:lang             %xmlLangCode;         #REQUIRED
>

<!--
    A single dimension for the packaging. It also can be used to define item dimensions.
    quantity
        Size in this dimension.  Expressed in the units given in the UnitOfMeasure element.
    type
        Type of dimension.  Supported values include:
        length - The length of the packaging or item.
        width - The width of the packaging or item.
        height - The height of the packaging or item.
        weight - The weight  or net weight of the packaging or item.
        volume - The volume or net volume of the packaging or item.
        stackHeight -The stack height of packaging. This indicates total height of the stacked packages. 
        grossWeight - The gross weight is the total weight including packaging.
        grossVolume -The gross volume is the total volume including packaging. 
        unitGrossWeight  - The unit gross weight of the item.
        unitNetWeight  -The unit net weight of the item.
-->
<!ELEMENT Dimension (UnitOfMeasure)>
<!ATTLIST Dimension
    quantity             %r8;                        #REQUIRED
    type (length | width | height | weight | volume | stackHeight | grossWeight | grossVolume | unitGrossWeight | unitNetWeight ) #REQUIRED
>


<!-- Describes the level (inner, outer, intermediate) for packages. It is used in logistics for loading and unloading information. This information qualifies the 
packing level within the packing hierarchy. -->

<!ELEMENT PackagingLevelCode (#PCDATA)>

<!-- This is a unique ID of packaging materials like box, container, pallet and rack. This helps receiving side for unloading and storage. This also defines the 
maximum load or weight of articles -->

<!ELEMENT PackageTypeCodeIdentifierCode (#PCDATA)>

<!--This identifies a package during transport and in inventory. Serial number of a packaging unit like container, box and rack -->
<!ELEMENT ShippingContainerSerialCode (#PCDATA)>

<!--
Reference from a package with shipping code to the shipping code of the next higher package level. It references the parent ShippingContainerSerialCode.
-->
<!ELEMENT ShippingContainerSerialCodeReference (#PCDATA)>


<!-- Unique ID for a package.  GIAI, numbering scheme of GS1 specifying the ownership of an asset.-->
<!ELEMENT GlobalIndividualAssetID (#PCDATA)>


<!-- The ID that helps supplier with handling of any returned package.-->
<!ELEMENT ReturnablePackageID (#PCDATA)>

<!-- The information to track packages based on an internal numbering scheme of the supplier. -->
<!ELEMENT PackageTrackingID (#PCDATA)>

t/xml-catalog/cXML-1.2.036/cXML.dtd  view on Meta::CPAN

    domain
        Domain in which this value has meaning.  Recognized domains
        include:
        companyName - The legal name for this company.  In some cases, this
            could also be provided in a Contact element with role
            "carrierCorporate".  That option should be reserved for cases
            in which additional detail about the carrier appears in this
            element.
        SCAC - Standard Carrier Alpha Code (see
            http://users.erols.com/nmfta/Codes.htm)
        IATA - International Air Transport Association (see
            http://www.iata.org)
        AAR  - Association of American Railroads (see http://www.aar.org/)
        UIC  - International Union of Railways (see
            http://www.uic.asso.fr/)
        EAN  - European Article Numbering (see http://www.ean-ucc.org/)
        DUNS - D&B's Data Universal Numbering System (see
            http://www.dnb.com/dnbhome.htm)
-->
<!ELEMENT CarrierIdentifier (#PCDATA)>         <!-- string -->
<!ATTLIST CarrierIdentifier
    domain               %string;              #REQUIRED
>

<!--
    Identifier that appears on a shipment and through which additional
    detail about the shipment may be retrieved.  Defined by the carrier.
    Has meaning in the domain described by the CarrierIdentifier values.
    Therefore, CarrierIdentifier and ShipmentIdentifier should normally
    be used together.

    Conceptually, this is a tracking number.  Different carriers have
    different names for shipment identifiers.  Some call it a way bill
    number, others call it a pro number, and still others call it a bill of
    lading.  They all represent tracking numbers.
    
    domain
        Specifies more precisely what kind of identifier this is.
        Likely values include trackingNumber, billOfLading. 
        
    trackingNumberDate
        The date when the logistics provider intimates the tracking number 
        for this shipment. This date is used to find out the efficiency of the
        supply chain process.

    trackingURL
        carrier URL that can be used to track the shipment in conjunction with the tracking number
-->
<!ELEMENT ShipmentIdentifier (#PCDATA)>        <!-- string -->
<!ATTLIST ShipmentIdentifier
    domain                %string;              #IMPLIED
    trackingNumberDate    %datetime.tz;         #IMPLIED
    trackingURL           %URL;                 #IMPLIED>


<!--
    One language-specific string for the creator of an IdReference,
    e.g. IRS, BofA, UPS, Cisco, etc.

    xml:lang
        The language or locale in which the name of the creator is written.
-->
<!ELEMENT Creator (#PCDATA)>              <!-- string -->
<!ATTLIST Creator
   xml:lang              %xmlLangCode;         #REQUIRED
>

<!--
    Defines an ID reference.  Within the application context (for example,
    a certain pair of buyer and supplier), the (identifier, domain) pair
    should be unique.

    Creator
        The creator of this IdReference, e.g. BofA, UPS, Cisco, etc.

    Description
        Textual description of the IdReference. For human readability.

    identifier
        The unique identifier of the IdReference within the domain.

    domain
        The domain of the IdReference.  It should be one of the
        following:
        accountID, bankRoutingID, accountPayableID,
        accountReceivableID, bankAccountID, ibanID, abaRoutingNumber,
        bankNationalID, isoBicID, swiftID, bankBranchID, federalTaxID,
        stateTaxID, provincialTaxID, vatID, gstID, and taxExemptionID.
        supplierTaxID is deprecated and will be treated as federalTaxID.
        Other possible values could be 1099ID, courtRegisterID, 
        supplierReference, governmentNumber, documentName, etc.
-->
<!ELEMENT IdReference (Creator?, Description?)>
<!ATTLIST IdReference
    identifier      %string;                         #REQUIRED
    domain          %string;                         #REQUIRED
>

<!--
    Defines supplier sales order information related to an order.

    This is also used in PunchOutOrderMessage to indicate that the 
    supplier has created an order associated with the punchout order message.  
    The buyer can later cancel the sales order by sending an OrderRequest 
    of type "delete" that refers to the sales order by including the 
    SupplierOrderInfo element in the OrderRequestHeader

    orderID
        Supplier sales order id of this order.
        
    orderDate
        The date and time the sales order was created.
-->
<!ELEMENT SupplierOrderInfo EMPTY>
<!ATTLIST SupplierOrderInfo
    orderID              %string;               #REQUIRED
    orderDate          %datetime.tz;      #IMPLIED
>


<!-- 

t/xml-catalog/cXML-1.2.036/cXML.dtd  view on Meta::CPAN

    name          %string;      #REQUIRED
    a-dtype       NMTOKENS      #FIXED 'name string'
>

<!--
    A transaction supported by this server.

    requestName
        A specific request this server accepts at the given URL.  The
    %cxml.requests entity (defined in transport.mod) contains the
    possible values for this attribute.

    a-dtype
        Datatype enumeration for the attributes of this element.  May be
    ignored by most XML parsers (used for documentation purposes).
-->
<!ELEMENT Transaction ( URL, Option* )>
<!ATTLIST Transaction
    requestName   %nmtoken;     #REQUIRED
    a-dtype       NMTOKENS      #FIXED 'requestName NMTOKEN'
>
<!--
    For cXML license agreement information, please see
    http://www.cxml.org/home/license.asp

    $Id: //ariba/cxml/release/schema/1.2.36.1+/Modules/Transport.mod#1 $
-->

<!--
    For better definitions of these Elements/Entities, refer to the cXML
    Protocol Specification documents.
-->

<!--
    Defines the set of known valid cXML digital signature versions
-->
<!ENTITY % cxml.signatureVersions "(1.0)">

<!--
    cXML envelope

    version
        Version of this cXML transmission.  Should be less than or equal
    to the version portion of the SYSTEM identifier for this document.

    payloadID
        A unique identifier for this document.

    timestamp
        The date and time at which this document was originally created.

    signatureVersion
        If present, specifies the cXML digital signature version to
        which this document conforms.  This implies that the
        ds:Signature element must be present.  It is an error if this
        attribute is present and the document does not conform to the
        specified signature version.  If absent, the document is not
        signed.

    xml:lang
        The default locale for all strings (not formatted items such as
    dates, times and numbers) in this document.  This attribute will be
    required in a future version of cXML.  (Leaving it out is
    deprecated.)
-->
<!ELEMENT cXML (((Header, (Message | Request)) | Response), ds:Signature*)>
<!ATTLIST cXML
    version    %string;       "&cxml.version;"
    payloadID  %string;       #REQUIRED
    timestamp  %datetime.tz;  #REQUIRED
    signatureVersion %cxml.signatureVersions; #IMPLIED
    xml:lang   %xmlLangCode;  #IMPLIED
>

<!-- header -->
<!ELEMENT Header (From, To, Sender, (Path, OriginalDocument)?)>

<!ELEMENT From (Credential+, Correspondent?)>
<!ELEMENT To (Credential+, Correspondent?)>
<!ELEMENT Sender (Credential+, UserAgent)>

<!--
    Path. A list of nodes that records the path taken by a user through 
    a punchout chaining scenario.

    If no route node is included then punchout chaining scenario is not executed and only copies are processed. 
-->
<!ELEMENT Path (Node+)>

<!--
    A Node is any entity connected to a Network.
    
    type
        A node can define itself as a router node or a copy node.  Routers
    assume responsibility for the transaction.  Copy Nodes request to only
    be aware of the transaction.
    
    itemDetailsRequired
        Intermediary Nodes may want to support special operations without
    having to store specific information required to fulfill that operation.
    This attribute tells the previous node to send ItemDetail information
    when performing a PunchOutSetupRequest edit/inspect operation.
-->
<!ELEMENT Node (Credential+)>
<!ATTLIST Node
    type (copy | route) #REQUIRED
    itemDetailsRequired (yes) #IMPLIED
>


<!--
    Identifies the previous document in the situation that a router node
    forwards a message or request on to a more distant node.
    
    payloadID
        The payloadId of the original document.
-->
<!ELEMENT OriginalDocument EMPTY>
<!ATTLIST OriginalDocument
    payloadID %string; #REQUIRED
>



( run in 1.401 second using v1.01-cache-2.11-cpan-ceb78f64989 )