UBL Transportation SC

 View Only
  • 1.  Global replacements in PRD3 document definitions

    Posted 06-01-2012 20:45
    Hello PSC and TSC, This note relates to the editorial review described in my previous message. To save time and regularize definitions of the most generic BBIEs in the document models, I used scripts to mechanically replace each such entry with a fixed definition that (presumably) applies to all instances of entries with the same property term and representation term. For example, all instances of <object class>. Billing Reference have been regularized to "A reference to a billing document associated with this document." A list of these global replacements is given below. Please review each of the global replacements to ensure that no error of interpretation has occurred. If corrections are needed, I can easily make them by modifying the script used to embed each definition. (But we will want to make these changes before any others in order that I can reissue the spreadsheets prior to your further work on them, so this step should be completed before any other work is done.) You will note that the "regularized" definitions are often lacking further details that would be helpful for users. For example, the definition of Billing Reference above says nothing about what kinds of documents might be referred to and what they might have to do with the document in question. I will be asking you to provide such details, where appropriate, during the review itself, but in this initial phase I'd like to concentrate on changes that can be scripted across the entire document set so that I can issue a revised set of spreadsheets (if any corrections are necessary) before you begin further work. The following three definitions were already consistent across the document set and have not been changed, but they should be considered for possible revision along with the rest: <object class>. Customization Identifier. Identifier Identifies a user-defined customization of UBL for a specific use. <object class>. Profile Identifier. Identifier Identifies a user-defined profile of the customization of UBL being used. <object class>. Profile Execution Identifier. Identifier Identifies an instance of executing a profile, to associate all transactions in a collaboration. Jon ######################################################################## SCRIPTED DEFINITIONS ACROSS THE PRD3 DOCUMENT SET <object class>. Accounting_ Customer Party. Customer Party The accounting customer party. <object class>. Accounting_ Supplier Party. Supplier Party The accounting supplier party. <object class>. Additional_ Document Reference. Document Reference A reference to an additional document associated with this document. <object class>. Allowance Charge A discount or charge that applies to a price component. <object class>. Billing Reference A reference to a billing document associated with this document. <object class>. Buyer_ Customer Party. Customer Party The buyer. <object class>. Contract_ Document Reference. Document Reference A reference to a contract associated with this document. <object class>. Contract Folder Identifier. Identifier An identifier, assigned by the sender, for the process file (i.e., record) to which this document belongs. <object class>. Copy_ Indicator. Indicator Indicates whether this document is a copy (true) or not (false). <object class>. Delivery A delivery associated with this document. <object class>. Delivery Terms A set of delivery terms associated with this document. <object class>. Despatch_ Document Reference. Document Reference A reference to a Despatch Advice associated with this document. <object class>. Document Reference A reference to another document associated with this document. <object class>. Document_ Currency Code. Code A code signifying the default currency for this document. docname Exchange Rate Information about the rate of exchange (conversion) between two currencies. <object class>. Identifier An identifier for this document, assigned by the sender. <object class>. Issue Date. Date The date, assigned by the sender, on which this document was issued. <object class>. Issue Time. Time The time, assigned by the sender, at which this document was issued. <object class>. Name Text, assigned by the sender, that identifies this document to business users. <object class>. Note. Text Free-form text pertinent to this document, conveying information that is not contained explicitly in other structures. <object class>. Originator_ Document Reference. Document Reference A reference to an originator document associated with this document. <object class>. Payment Terms A set of payment terms associated with this document. <object class>. Payee_ Party. Party The payee. <object class>. Payment Means Expected means of payment. <object class>. Payment Terms Payment terms associated with this document. <object class>. Receipt_ Document Reference. Document Reference A reference to a Receipt Advice associated with this document. <object class>. Seller_ Supplier Party. Supplier Party The seller. <object class>. Signature A signature applied to this document. <object class>. Statement_ Document Reference. Document Reference A reference to a Statement associated with this document. <object class>. Tax Representative_ Party. Party The tax representative. <object class>. Tax Total The total amount of a specific type of tax. <object class>. UBL Version Identifier. Identifier Identifies the earliest version of the UBL 2 schema for this document type that defines all of the elements that might be encountered in the current instance.


  • 2.  Re: [ubl-psc] Global replacements in PRD3 document definitions

    Posted 06-06-2012 15:19
    Hello PSC and TSC, To clarify something I said earlier regarding the list of "global" data definitions -- You will notice as you look through the spreadsheets I posted that in many cases, the regularized versions of the global definitions leave out important details specific to particular document types. I am hoping that you in the content teams can flesh out many of the generic definitions with information specific to your area of application. To take one set of examples that particularly stood out for me, there are many occurrences of "Reference to an additional document" or "Reference to a billing document" where a user will be as curious as I was to know what kind of document is being referred to and what it has to do with the document that is referencing it, especially in the case of billing document. (I can't believe that it's the same kind of billing document in all the places this appears.) This issue is something that I will be asking you to attend to further on, after our meetings of the week of 18 June when we cover the initial list of items I asked you for in my previous message on this subject. But not now. For now I just want you to find the global definitions that are wrong *as globals* due to some basic defect of understanding on my part so that I can run scripts to fix these in the spreadsheets before anyone begins to invest effort in responding to queries. Please save the *individually* incorrect and incomplete definitions for the spreadsheet review that we will begin after our TC meetings the week of 18 June. You may find (Kees seems already to have found) "globals" that simply can't be globally defined because their use varies too much among the different document types. I'm not going to make preliminary changes to these items right now, but you should begin to prepare a list of them as part of what needs to be addressed. Jon


  • 3.  Re: [ubl-psc] Global replacements in PRD3 document definitions

    Posted 06-06-2012 15:19
    Hello PSC and TSC, To clarify something I said earlier regarding the list of "global" data definitions -- You will notice as you look through the spreadsheets I posted that in many cases, the regularized versions of the global definitions leave out important details specific to particular document types. I am hoping that you in the content teams can flesh out many of the generic definitions with information specific to your area of application. To take one set of examples that particularly stood out for me, there are many occurrences of "Reference to an additional document" or "Reference to a billing document" where a user will be as curious as I was to know what kind of document is being referred to and what it has to do with the document that is referencing it, especially in the case of billing document. (I can't believe that it's the same kind of billing document in all the places this appears.) This issue is something that I will be asking you to attend to further on, after our meetings of the week of 18 June when we cover the initial list of items I asked you for in my previous message on this subject. But not now. For now I just want you to find the global definitions that are wrong *as globals* due to some basic defect of understanding on my part so that I can run scripts to fix these in the spreadsheets before anyone begins to invest effort in responding to queries. Please save the *individually* incorrect and incomplete definitions for the spreadsheet review that we will begin after our TC meetings the week of 18 June. You may find (Kees seems already to have found) "globals" that simply can't be globally defined because their use varies too much among the different document types. I'm not going to make preliminary changes to these items right now, but you should begin to prepare a list of them as part of what needs to be addressed. Jon