Re: [ubl] RE: [ubl-ssc] Codelist dependencies

[Tim McGrath <tmcgrath@portcomm.com.au>]

I agree with Sylvia, we need to get on top of this issue.  My 
understanding is that the UBL Schemas will not need a qDT because we are 
no longer restricting the schemas for specific code lists.  in other 
words we dont need a qDT for CurrencyCode because as far as the schema 
goes it is just a CodeType.  The validation of values now happens 
outside the schemas.

However, what we still need is the metadata that was in the qDT to be in 
the UBL schemas (and models).  For exmaple, which code lists (eg the 
genericode schema) should be used for validation.  I dont think the 
current NDR defines this metadata so where do we put it?

Does anyone have ideas for this?


Sylvia Webb wrote:

>Stephen,
>
>Schema can be autogenerated from FX data models IF the spreadsheets used to
>create those models are complete. 
>
>The current spreadsheets are not up to date in this regard. This was noted
>in the UBL minutes some time ago and an action item to correct them in this
>regard needs to be assigned.
>
>It should also be noted that it appears that the restriction of enumerations
>in codelists requires creation of a qDT schema module. The current draft of
>the UBL NDR rules state the following:
>
>The ubl:QualifiedDatatype is defined by specifying restrictions on the
>1123 ccts:CoreComponentType that forms the basis of the
>ccts:UnqualifiedDatatype.
>1124 To ensure the consistency of UBL qualified Datatypes
>(ubl:QualifiedDatatypes)
>1125 with the UBL modularity and reuse goals requires creating a single
>schema module that
>1126 defines all ubl:QualifiedDatatypes.
>1127 [SSM18] A schema module defining all UBL Qualified Datatypes MUST be
>created.
>1128 The ubl:QualifiedDatatypes must be based upon the 
>1129 ccts:UnqualifiedDatypes.
>1130 [SSM20] The UBL Qualified Datatypes schema module MUST import the 
>1131 ccts:UnQualifiedDatatypes schema module.
>[CTD20] A qdt:QualifiedDataType MUST be based on an unqualified data type
>1706 and add some semantic and/or technical restriction to the unqualified
>data
>1707 type.
>
>It would certainly seem that the restriction of enumerations in a codelist
>specified in a uDT add semantics or is a technical restriction of the base
>uDT code type.
>
>How will users create the qDT schema module using the new codelist
>methodology and genericode approach? I do not see any reference to the qDT
>schema module in Ken Holman's methodology paper. Am I missing something? 
>
>Regards,
>Sylvia
>-----Original Message-----
>From: stephengreenubl@gmail.com [mailto:stephengreenubl@gmail.com] 
>Sent: Saturday, April 22, 2006 1:54 PM
>To: ubl-ssc@lists.oasis-open.org
>Subject: [ubl-ssc] Codelist dependencies
>
>Could I just ask of David and Sylvia whether there are any extra pieces of
>information such as supplementary component values still needed for schema
>generation. Is all the necessary inmformation in the model and/or the
>spreadhseets and does it appear to be up to date? Is there anything else
>like this we might need to provide prior to the plenary. If need be we can
>discuss any of this at the Wednesday TC meeting this week.
>Thanks. 
>
>All the best
>
>Stephen Green
>
>
>
>---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail.  You may a link to this group and all your TCs in OASIS
>at:
>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
>
>
>  
>

-- 
regards
tim mcgrath
phone: +618 93352228  
postal: po box 1289   fremantle    western australia 6160
web: http://www.portcomm.com.au/tmcgrath