OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ubl message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [ubl] More code list questions about NDR, and about genericode

Ken, apologies I didn't reply earlier.

On Tue, 11 Oct 2005 22:27:20 +0100, G. Ken Holman  
<gkholman@CraneSoftwrights.com> wrote:

>    genericode ShortName  ==  UBL xxxxxCodeListID
>    genericode LongName == UBL xxxxxCodeListName
>    genericode Version == UBL xxxxxCodeListVersionID
>    genericode CanonicalUri == UBL xxxxxCodeListURI
>    genericode CanonicalVersionUri == UBL xxxxxCodeListSchemeURI

Not quite.  Have a look at the last set of conversion stylesheets I sent  
out.  UBL doesn't have an equivalent for "CanonicalUri", which is a URI  
that uniquely identifies the code list as an entity, independently of any  
specific version.  In the stylesheets, I have to create this by chopping  
the version off the version-specific URN for the code list.

> Tony, can you confirm this is all of the version checking that I need to  
> do when using a genericode file to express the values in a UBL instance?

I believe so; again, see the stylesheets I did, as I had everything there  
that was needed to match Marty's example Schemas.

> (1) for @xxxxxID remove "ID" and suffix with "Code..." from genericode  
> table above as appropriate
> (2) for @xxxxxCode remove "Code" and suffix with "Code..." from  
> genericode table above as appropriate
> (3) for <xxxxx> suffix with "code..." from genericode table above as  
> appropriate

I also did a Schematron Schema to check these, bundled in with the  
stylesheets.  Did you see that?  I don't remember needing to do this,  
though.  The only open issue I had was if someone used a code list type to  
create a differently named element.  That would require either (i)  
Schematron using a Schema-aware version of XPath 2.0 that checks types, or  
(ii) the user would have to create their own Schematron rule based on the  
supplied one (not a big job).

Cheers, Tony.
Anthony B. Coates
London Market Systems Limited
33 Throgmorton Street, London, EC2N 2BR, UK
Mobile/Cell: +44 (79) 0543 9026
[MDDL Editor (Market Data Definition Language), http://www.mddl.org/]
[FpML Arch WG Member (Financial Products Markup Language),  
This Email may contain confidential information and/or copyright material  
and is intended for the use of the addressee only.  Any unauthorised use  
may be unlawful. If you receive this Email by mistake please advise the  
sender immediately by using the reply  facility in your e-mail software.   
Email is not a secure method of communication and London Market Systems  
Limited cannot accept responsibility for the accuracy or completeness of  
this message or any attachment(s). Please examine this email for virus  
infection, for which London Market Systems Limited accepts no  
responsibility. If verification of this email is sought then please  
request a hard copy. Unless otherwise stated any views or opinions  
presented are solely those of the author and do not represent those of  
London Market Systems Limited.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]