Re: [ubl-fpsc] Amendments to Specs for UBL 1.0 draft 3 (the UBLish-generated version)

["Stephen Green" <stephen_green@seventhproject.co.uk>]

I'd add to my previous message:

Re 2.  Not all leaf nodes have 'cbt:', only those
which previously had 'cat:' . Some have the document
prefix(/namespace) in:, po:, etc.

Re 3.  I realise that Ken already said on the call
that we won't need the codelist metadata in the specs but I
just include the attributes for completeness so people see that
they can be used (as part of the ebXML CC Technical Spec).

There are also a fair few other minor name changes which,
although they may not affect the Joinery and Office
scenarios, may affect the UN ones so these will need to be
checked, sorry. The changes are all documented in the
change log and in notes against each changed row
in the spreadsheets.


All the best

Steve

----- Original Message -----
From: "Stephen Green" <stephen_green@seventhproject.co.uk>
To: "UBL FPSC" <ubl-fpsc@lists.oasis-open.org>
Sent: Sunday, February 08, 2004 8:33 PM
Subject: [ubl-fpsc] Amendments to Specs for UBL 1.0 draft 3 (the
UBLish-generated version)


> Jean and Ken,
>
> I found that, for 1.0 draft 3 the Office and Joinery Specs
> (and maybe UN ones too) need the following amendments:
>
> 1. New, additional, namespace/prefix
>
> Prefix cbt:
>
> urn:oasis:names:tc:ubl:CommonBasicTypes:1:0-draft-3
>
> (or, in final case,
> urn:oasis:names:tc:ubl:CommonBasicTypes:1:0)
>
> 2. In line with 1. above, all 'leaf' nodes, typically the final
> *element* (not attribute) in each XPath each need,
> instead of prefix 'cat:', to have prefix 'cbt:'
> so e.g.
> /in:Invoice/cat:OrderReference/cat:BuyersID
> becomes
> /in:Invoice/cat:OrderReference/cbt:BuyersID
>                                                    ---
>
>
> 3. Certain elements which are a 'Code'
> (e.g., in the sample instances for Joinery,
> /.../cat:AllowanceCharge/cbt:ReasonCode
> and
> /in:Invoice/cat:PaymentMeans/cbt:PaymentMeansTypeCode)
> now have codelist-related 'Supplementary Components',
> in our usual version of UBL (unclear how Michael's may
> interpret this) defined as attributes, e.g.
>
> cbt:PaymentMeansTypeCode
>
> might have attributes:
>
>  listID                    UNTDID-TRED-4451
>  listVersionID        D03A
>  listAgencyName   UNECE
>
> for code value 'ZZZ'
>
> The Xpaths will be:
> /in:Invoice/cat:PaymentMeans/cbt:PaymentMeansTypeCode/@listID
> /in:Invoice/cat:PaymentMeans/cbt:PaymentMeansTypeCode/@listVersionID
> /in:Invoice/cat:PaymentMeans/cbt:PaymentMeansTypeCode/@listAgencyName
>
> (note that, as for beta, I'm including the top level namespace prefix even
> though
> the instances do not include them, having default namespaces 'xmlns=...')
>
> I'm in the process of updating the Joinery and Office Specs
> as I last had them for 1.0 beta - I'll send them as soon as
> they're finished.
>
> The Specs will include comments here and there to underline the changes
> but these could be removed of course if Ken prefers.
>
> All the best
>
> Steve
>
>
>
>
>
>
>
> To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/ubl-fpsc/members/leave_workgrou
p.php.
>
>