Re: [ubl] Code list question

[Anne Hendry <Anne.Hendry@Sun.COM>]

Responding to the second bullet item, I think that depends on whether 
ChipCode is a UBL-provided code lsit or not.

I'm of the opinion that the UBL-provided code lists are not to be 
touched by users.  They contain values upon with UBL relies in order to 
function (eg. acknowledement response code hjas two values: 
OrderResponseSimple and OrderResponse; those are very specific to UBL 
and cannot be changed by a user or UBL would break).

btw, this (eg. achnowledgementresponsecode) is the only type of code I 
recommend providing enumerations for in UBL.  We have a couple of others 
we've included (latitute: north south, longitude: east west), but I 
think we can easily say we own those as well.  Not so much of chip code, 
but I thnk I recommended having chip code as part of class 2.

-A

Jon.Bosak@Sun.COM wrote:

>Hello UBL TC,
>
>I'm trying to understand exactly how we set up code lists in UBL
>1.0, in particular what the difference is between the code lists
>that we supply (such as ChipCode) and the ones that we don't (such
>as CommodityCode).
>
>One way of asking this question is as follows:
>
> - Suppose a user wants to provide enumerated values for
>   CommodityCode and have them included in the initial validation.
>   How exactly is this done?
>
> - Conversely, suppose a user wants to "turn off" checking against
>   the enumerated values in ChipCode.  How is this done?
>
> - Would either enabling or disabling validation of a code list
>   require a change to the document schemas?
>
>Jon
>
>
>---------------------------------------------------------------------
>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 
>
>  
>