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] Revised draft prototype code list schema

Oops, now that I've tested it, it doesn't work (at least, not when a UBL  
document is validated using oXygen, which uses Xerces-J).  The simple type  
for code lists isn't properly derived from "xsd:normalizedString", so it  
doesn't work when you use it to validate UBL documents.  I have attached a  
modified version that works.  However, this is now pretty much back to the  
previous version.

When you change the code list Schemas, it looks like you need to check  
that "UBL-SpecializedDatatypes-1.0.xsd" is still valid.

Cheers, Tony.

On Fri, 11 Nov 2005 08:25:41 -0500, <Burnsmarty@aol.com> wrote:

> Ken, Tony, et al,
> Attached is a slightly revised code list schema document structure. This
> schema can be extended by subtitution groups or your method of Schematron
> validation, contains the codes and supplementary components and, in   
> addition, is
> consistent with the recently published OAGIS 9 schemas. This  is not a  
> perfect
> design, but, may be a perfect compromise of approach.
> The two defined types CurrencyCodeType and CurrencyCodeContentType can be
> used in schemas the way they have been traditionally in UBL -- by  
> declaring
> elements or attributes derived from the types. Global attributes are  
> provided
> with the version metadata for supplementary components.
> Restrictions and extensions can be made outside of the UBL schemas. The
> approach allows substitution groups and redefine without using them  
> directly in
> the schemas.
> If you (Ken and Tony) can generate all your schematron from these  
> standard
> schemas, then the generating scripts can be an informative annex to UBL  
> to be
> used by designers. I think this is a good approach.
> The UBL-CodeList-1.0.xsd is a template for the code list schemas  
> themselves
> but does not need to be referenced in the actual code lists themselves.  
> Right
> now, each code list schema would be primitive only importing the
> UBL-CoreComponentParameters-1.0.xsd to define the metadata that is part  
> of the
> annotations.
> What are your thoughts?
> Marty

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]