[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ubl-dev] UBL Order
Very good example. Pretty much perfect in my opinion.
Of course you'd have to have an agreement between
trading parties that
'schemeURI="http://www.dnb.com/US/duns_update/";'
is being used to denote a DUNS number. It is at least
an unambiguous choice of scheme uri but the software
would have to be told to watch for it. So this kind of thing
would need a technical appendix, say, to a trading
agreement to use the UBL 2.x Order, etc. It is also of
note that you are not including the UBLVersionID, which
might help software to recognise that you are using 2.0.
<cbc:UBLVersionID>2.0</cbc:UBLVersionID>
If your trading agreement includes some kind of ID you
could include that in either the
<cbc:CustomizationID>xyz98765</cbc:CustomizationID>
or the <cbc:ProfileID>abc12345</cbc:ProfileID>
Maybe use CustomizationID to point to the technicalities
like your use of "http://www.dnb.com/US/duns_update/";
and any restriction rules to help the software (also perhaps
details about which codes are used like do you want to
only allow use of the 'EA' code for unitCode to simplify
the software). Then if there are different ways you want to
further specify using the Order you could define one or
more profiles (usually profile here means the business
process or a sub-category of the specified usage rules like
a use case scenario) and give these profiles identifiers to
use with ProfileID.
Best regards
---
Stephen D Green
Document Engineering Services Ltd
2009/7/6 Marzka, Jeremy <JMarzka@kaydon.com>:
> Thanks for all the great responses.
>
> I hope this message isn't to long but I have pasted an example of what I
> have come up with so far. Any more suggestions would be appreciated.
>
> Thanks
> Jeremy
>
> I have also uploaded this to pastebin (http://pastebin.com/m35fa001b) in
> case this email isn't very readable.
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <Order
> xmlns:qdt="urn:oasis:names:specification:ubl:schema:xsd:QualifiedDatatyp
> es-2"
>
> xmlns:ccts="urn:oasis:names:specification:ubl:schema:xsd:CoreComponentPa
> rameters-2"
>
> xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicCompo
> nents-2"
>
> xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateC
> omponents-2"
>
> xmlns:udt="urn:un:unece:uncefact:data:draft:UnqualifiedDataTypesSchemaMo
> dule:2"
> xmlns="urn:oasis:names:specification:ubl:schema:xsd:Order-2">
>
> <cbc:ID>ABCD123</cbc:ID>
>
> <cbc:IssueDate>2009-12-30</cbc:IssueDate>
>
> <cbc:CustomerReference>OrderRef1</cbc:CustomerReference>
>
> <cac:BuyerCustomerParty>
> <cac:Party>
> <cac:PartyIdentification>
> <cbc:ID
> schemeURI="http://www.dnb.com/US/duns_update/";>123456789</cbc:ID>
> </cac:PartyIdentification>
> <cac:PostalAddress>
> <cbc:ID>4321</cbc:ID>
> <cbc:CityName>Muskegon</cbc:CityName>
> <cbc:PostalZone>49441</cbc:PostalZone>
>
> <cbc:CountrySubentityCode>MI</cbc:CountrySubentityCode>
> <cac:AddressLine>
> <cbc:Line>200 State
> St</cbc:Line>
> </cac:AddressLine>
> <cac:Country>
>
> <cbc:IdentificationCode>US</cbc:IdentificationCode>
> </cac:Country>
> </cac:PostalAddress>
> <cac:Contact>
> <cbc:Name>John</cbc:Name>
>
> <cbc:Telephone>111-222-3333</cbc:Telephone>
> <cbc:Telefax>111-222-3333</cbc:Telefax>
>
> <cbc:ElectronicMail>mail@mail.com</cbc:ElectronicMail>
> </cac:Contact>
> </cac:Party>
> </cac:BuyerCustomerParty>
>
> <cac:SellerSupplierParty>
> <cac:Party>
> <cac:PartyIdentification>
> <cbc:ID
> schemeURI="http://www.dnb.com/US/duns_update/";>987654321</cbc:ID>
> </cac:PartyIdentification>
> </cac:Party>
> </cac:SellerSupplierParty>
>
> <cac:Delivery>
> <cac:RequestedDeliveryPeriod>
> <cbc:EndDate>2010-12-30</cbc:EndDate>
> </cac:RequestedDeliveryPeriod>
> <cac:DeliveryParty>
> <cac:PostalAddress>
> <cbc:ID>1234</cbc:ID>
> <cbc:CityName>Grand Haven</cbc:CityName>
> <cbc:PostalZone>49417</cbc:PostalZone>
>
> <cbc:CountrySubentityCode>MI</cbc:CountrySubentityCode>
> <cac:AddressLine>
> <cbc:Line>500 Lakeshore
> Dr</cbc:Line>
> </cac:AddressLine>
> <cac:Country>
>
> <cbc:IdentificationCode>US</cbc:IdentificationCode>
> </cac:Country>
> </cac:PostalAddress>
> <cac:Contact>
> <cbc:Name>Steve</cbc:Name>
>
> <cbc:Telephone>111-222-3333</cbc:Telephone>
> <cbc:Telefax>111-222-3333</cbc:Telefax>
>
> <cbc:ElectronicMail>billing@mail.com</cbc:ElectronicMail>
> </cac:Contact>
> </cac:DeliveryParty>
> <cac:Despatch>
> <cac:DespatchParty>
> <cac:PartyName>
> <cbc:Name>FED EX AIR</cbc:Name>
> </cac:PartyName>
> </cac:DespatchParty>
> </cac:Despatch>
> </cac:Delivery>
>
> <cac:DeliveryTerms>
> <cbc:ID>FOB</cbc:ID>
> <cbc:SpecialTerms>Origin: Freight-Prepaid and
> Add</cbc:SpecialTerms>
> </cac:DeliveryTerms>
>
> <cac:OrderLine>
> <cac:LineItem>
> <cbc:ID>1</cbc:ID>
> <cbc:Quantity
> unitCode="EA">100.00</cbc:Quantity>
> <cac:Price>
> <cbc:PriceAmount
> currencyID="USD">100.00</cbc:PriceAmount>
> </cac:Price>
> <cac:Item>
> <cbc:Description></cbc:Description>
> <cac:BuyersItemIdentification>
> <cbc:ID>00109421</cbc:ID>
> </cac:BuyersItemIdentification>
> <cac:SellersItemIdentification>
> <cbc:ID>KA025CP0</cbc:ID>
> </cac:SellersItemIdentification>
> <cac:StandardItemIdentification>
> <cbc:ID>662729165844</cbc:ID>
> </cac:StandardItemIdentification>
> <cac:AdditionalItemIdentification>
> <cbc:ID>B41106</cbc:ID>
> </cac:AdditionalItemIdentification>
> </cac:Item>
> </cac:LineItem>
> </cac:OrderLine>
>
> </Order>
>
> -----Original Message-----
> From: Pim van der Eijk [mailto:lists@sonnenglanz.net]
> Sent: Sunday, July 05, 2009 8:35 AM
> To: 'G. Ken Holman'; ubl-dev@lists.oasis-open.org
> Cc: adrian@mueller-consulting.biz
> Subject: RE: [ubl-dev] UBL Order
>
>
> Hello,
>
> For the schemeUri attribute, it may be useful to reuse a proposal that
> will
> be incorporated in the next ebXML CPA specification (but which has no
> dependency on ebXML), and that is mentioned in:
> http://lists.oasis-open.org/archives/ebxml-cppa/200704/msg00002.html
>
> If you follow this approach, the relevant UBL snippet would look like:
>
> <cbc:ID
> schemeURI="urn:oasis:names:tc:ebxml-cppa:partyid-type:iso6523:0060">1234
> 5</c
> bc:ID>
>
> The advantage of this is that the URI schema allows any ISO 6523
> approved
> classification system to be used.
> For a list of ICDs, see:
> http://metadata-stds.org/Document-library/Draft-standards/6523-Identific
> atio
> n-of-Organizations/ICD_list.htm#ICD0009
>
> The codes "0002", "0084", "0085", "0087", "0089", "0094", "0096",
> "0105",
> "0106", "0107", "0108" reference Chamber of Commerce identifiers from
> France, Greece, Switzerland, Belgium, UK, Germany, Denmark, Portugal,
> the
> Netherlands, Sweden, Australia, respectively.
>
> Replacing "0060" by "0088" would reference a GS1 Global Location Number
> (GLN) instead of a DUNS number.
>
> The CEN workshop on Cyber Identities has a discussion of all these
> concepts
> in a recent CWA:
> ftp://cenftp1.cenorm.be/PUBLIC/CWAs/e-Europe/Cyber_ID/CWA_CID_v1.8.pdf
>
> This document is open for comments according to
> http://www.cen.eu/cenorm/businessdomains/businessdomains/isss/activity/w
> s_cy
> berid.asp. It states they are going to register a "urn:iso6523" prefix,
> which would allow the above to be expressed more compactly as:
>
> <cbc:ID schemeURI="urn:iso6523:0060">12345</cbc:ID>
>
> Pim van der Eijk
>
> -----Original Message-----
> From: G. Ken Holman [mailto:gkholman@CraneSoftwrights.com]
> Sent: 03 July 2009 17:15
> To: ubl-dev@lists.oasis-open.org
> Subject: Re: [ubl-dev] UBL Order
>
> At 2009-07-02 09:32 -0400, Marzka, Jeremy wrote:
>>I am currently working on mapping trading partner order requests to a
>>UBL order and have a couple questions.
>
> All questions are very welcome, Jeremy. I hope UBL-Dev participants do
> not
> hold back.
>
> Different volunteers have different perspectives on UBL and can help in
> different areas. I cannot help you much on the business side, but I
> have a
> comment below regarding identifiers.
>
>>Where would you recommend that I map the following?
>>1. FOB code and description (FOB Origin, FOB Destination...) 2. Ship
>>Method (Air Freight, Motor Freight, Customer Pickup...) 3. Carrier Code
>
>>(FedEx Priority, UPS 3-Day, UPS Ground...)
>>
>>I also am confused by the different parties. Am I correct in assuming
>>that I can map the following?
>>
>>Sold To -> Buyer Customer Party
>>Bill To -> Accounting Customer Party
>>Ship To -> Delivery
>
> I see that Roberto has answered the above questions regarding business
> entities.
>
>>Our trading partners pass us a DUNS number (Dun & Bradstreet) that
>>uniquely identifies them. Where should I map this? To the Buyer
>>Customer Party -> Party > Party Identification > ID?
>
> Yes, I would have used that, and I see Roberto endorses it as a general
> method of identification.
>
> But I wanted to say it would help to identify the identification method
> since many identification methods might produce similar identifiers. I
> think perhaps something like the following would be unambiguous and
> acceptable:
>
> <cac:BusyerCustomerParty>
> <cac:Party>
> <cac:PartyIdentification>
> <cbc:ID
> schemeURI="http://www.dnb.com/US/duns_update/";>12345</cbc:ID>
> </cac:PartyIdentification>
> ...
>
>>Sorry if these questions are unclear I am relatively new to this.
>
> Thank you for asking them!
>
> . . . . . . . . . . . Ken
>
>
> --
> Possible July/August XSLT/XQuery/XSL-FO training in Oakland/CA/USA
> Crane Softwrights Ltd. http://www.CraneSoftwrights.com/u/
> Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video
> Video lesson: http://www.youtube.com/watch?v=PrNjJCh7Ppg&fmt=18
> Video overview: http://www.youtube.com/watch?v=VTiodiij6gE&fmt=18
> G. Ken Holman mailto:gkholman@CraneSoftwrights.com
> Male Cancer Awareness Nov'07 http://www.CraneSoftwrights.com/u/bc
> Legal business disclaimers: http://www.CraneSoftwrights.com/legal
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org
>
>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]