Hello,
I agree Identifiers are required to be expressed by specifying a
schemeId.
>Roberto, what metadata would you use for the Incoterms list of
values?
Incoterms 2000 comes from the International Chambre of Commerce which
is available in the Agencies Codelist at UN/ECE.
A sample for Incoterms:
<cac:DeliveryTerms>
<cbc:ID schemeAgencyID="4" schemeAgencyName="International
Chamber of Commerce"
schemeID="Incoterms 2000" schemeName="FCA Incoterms 2000"
schemeVersionID="2000">FOB</cbc:ID>
</cac:DeliveryTerms>
Where:
4 is the ICC (International Chamber of Commerce)
See:
3055 - Code list responsible agency code:
http://www.stylusstudio.com/EDIFACT/D04B/3055.htm
NOTE: Of course this sample could be too much, so the schemeAgencyID,
schemeID and schemeVersionID are recommended.
Hope this helps.
Roberto Cisternino
G. Ken Holman ha scritto:
7.0.1.0.2.20090706113141.02562700@wheresmymailserver.com"
type="cite">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
---------------------------------------------------------------------
To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org
Nessun virus nel messaggio in arrivo.
Controllato da AVG - www.avg.com
Versione: 8.5.375 / Database dei virus: 270.13.8/2227 - Data di rilascio: 07/09/09 05:55:00
|