Re: [ubl-dev] UBL Extensions

[Tim McGrath <tim.mcgrath@documentengineeringservices.com>]

>
> 2. Is there a guide to map common EDI documents to their corresponding UBL
> documents?
>   

If you are talking EDIFACT then UBL has the UN/TDED code for equivalent 
elements (see column S in the spreadsheet versions).  Not documents - 
but the elements that they are made up from.  As far as documents go we 
use more or less the same names as EDIFACT.  So a UBL Order is 
equivalent to an EDIFACT ORDERS document.

UN/TDED is the data dictionary from which all EDIFACT messages are built.

If you mean ANSI X12 then you are on your own, although maybe there is a 
UN/TDED to X12 mapping somewhere.

Roberto Cisternino wrote:
> Hello,
>
>   
>> Hi All,
>>
>>
>> We are currently evaluating UBL to possibly adopt it into our next
>> generation of business tools. We are facing a problem consisting mainly of
>> the following:
>>
>> The standard does not cover all the possible data fields/structures we
>> need to deal with. We basically need to map from EDI X.12 messages to UBL
>> and viceversa. The EDI is, as you know, really wide and is many times
>> customized to the own purposes of who transmits.
>>
>> Example:
>> A shipment may have many different associated dates: Ship Date, Deliver
>> Date, Do not Deliver After, Do not ship after, Do not ship before, Do not
>> deliver before,  Expiration date for foods etc.. We found at least 20
>> different DateTime qualifiers that may have us map the DTM valua to a
>> corresponding field in the UBL schema. It happens that the UBL does not
>> contemplate all of those fields. In this case we would be forced to extend
>> the standard to our own purposes.
>>
>> So, my questions are at this point:
>>
>> 1. Can you provide an example of how to extend a UBL Purchase Order with a
>> date of expiration for an item that is food?
>>     
>
> Order /OrderLine /LineItem /OrderedShipment /Package /GoodsItem /Item
> /ItemInstance /LotIdentification /ExpiryDate
>
>
>   
>> 2. Is there a guide to map common EDI documents to their corresponding UBL
>> documents?
>>     
>
> Not a public one at the moment, but maybe someone else can help on this
> better.
>
>   
>> 3. Can you provide an small example of code list extension?
>>     
>
> why extension ?
> Code list can be used into many information items in order to constraint
> values.  Code lists are handled in a separated way from UBL documents
> using Genericode OASIS Standard:
>
> http://docs.oasis-open.org/codelist/genericode/
>
> Codelist are defined by qualifying the information item with the code list
> attributes like:
> - List Agency ID
> - List Version ID
> - List URI
> - List Scheme URI
>
> This means the value used on a given UBL instance will be precisely
> associated to a codelist and a value validation will be possible.
>
> You have a sample on the Order->DocumentCurrencyCode (you can easely
> inspect the codelist attributes using UBL Swinger)
>
> The codelist argument is strictly connected to the validation argument so
> it is necessary to understand this aspect too.
> The codelist validation (using Schematron) is recommended after the
> mandatory structure validation (using XSD).
>
>   
>> Thanks a lot for your help,
>>
>>
>> Miguel
>> _________________________________________________________________
>> Create a handy button so your friends can add U to their buddy list. Try
>> it now!
>> http://g.msn.ca/ca55/211
>>     
>
>
>