Re: [ubl-dev] UBL Order

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

At 2009-07-06 16:51 +0100, Stephen Green wrote:
>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.

Note that such identifiers for customization and profile could be 
valued with a URI that points to an XHTML document with RDDL attributes.

   <cbc:CustomizationID>http://www.mycompany.com/customizations/ordering</cbc:CustomizationID>

And then that URI would present an XHTML with human-readable 
documentation about everything you ever needed to know about ordering.

Then in that instance, using RDDL attributes:

   http://www.rddl.org/

... one can cite other important resources:  schemas, stylesheets, 
PDF files, drawings, ordering locations, etc.  These RDDL are 
attributes that are added to XHTML anchor links so that an 
application reading the documentation can unambiguously identify 
links to other artefacts.

An example of an XHTML document using RDDL attributes is the 
namespace document for genericode:

   http://docs.oasis-open.org/codelist/ns/genericode/1.0/

And I have a free stylesheet that exposes RDDL attributes that helped 
me confirm the contents of what I posted for genericode:

     http://www.CraneSoftwrights.com/resources/#showrddl

I hope this helps.

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