RE: [ubl-dev] UBL Order

["G. Ken Holman" <gkholman@CraneSoftwrights.com>]

At 2009-07-06 11:25 -0400, Marzka, Jeremy wrote:
>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.

Thank you for posting your thoughts on this.

><?xml version="1.0" encoding="UTF-8"?>
><Order
>xmlns:qdt="urn:oasis:names:specification:ubl:schema:xsd:QualifiedDatatypes-2"

That declaration is not needed as it is never used in a UBL instance 
and should not have been in the examples in the UBL delivery.

>xmlns:ccts="urn:oasis:names:specification:ubl:schema:xsd:CoreComponentPa
>rameters-2"

That declaration is not needed as it is never used in a UBL instance 
and should not have been in the examples in the UBL delivery.

>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"

That declaration is not needed as it is never used in a UBL instance 
and should not have been in the examples in the UBL delivery.

>         xmlns="urn:oasis:names:specification:ubl:schema:xsd:Order-2">

So that leaves only the default namespace for order and the two 
namespaces associated with cbc: and cac:.  The other three are 
useless and provide no benefit.

>         <cac:BuyerCustomerParty>
>                 <cac:Party>

I see you have a contact, but wouldn't the party itself have a name 
that should be included?

>         <cac:DeliveryTerms>
>                 <cbc:ID>FOB</cbc:ID>

That identifier might suit instance-level metadata to disambiguate 
terminology, though of course I recognize it is common terminology in 
its context.  A bit like currency codes ... no real need to 
disambiguate "USD".  But it seemed a bit naked to me.

Roberto, what metadata would you use for the Incoterms list of values?

>                                 <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>

I wonder if some instance-level metadata here might help.  Just in 
case there are conflicting identifiers from other sources.  Perhaps 
the seller has multiple catalogues and knowing which collection of 
identifiers a particular identifier is from would help.

Well done!  I hope others will add their critiques as well.

. . . . . . . . . . . . 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