[OASIS Issue Tracker] (UBL-27) Code lists for UBL 2.2

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/UBL-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63870#comment-63870 ] 

Tim McGrath commented on UBL-27:
--------------------------------

Yes, as far as I could work out (and I am not an expert) the URNs for CEFACT are almost meaningless as it is not clear what they refer to and the artefacts are not always present.  I thought the value of the URN was to point the reader to the source file containing the legitimate values.  And the best way to do that was to ensure the URN refers to the genericode file used.
There may be a better way of doing this - as long as someone can (consistently) find the valid set of values from the metadata then I am open to suggestions.


> Code lists for UBL 2.2
> ----------------------
>
>                 Key: UBL-27
>                 URL: https://issues.oasis-open.org/browse/UBL-27
>             Project: OASIS Universal Business Language (UBL) TC
>          Issue Type: Task
>          Components: Artefacts
>            Reporter: Ken Holman
>            Assignee: Tim McGrath
>            Priority: Minor
>
> The current genericode files for code lists are from UBL 2.1.  Each code list has to be reviewed for any newer version to use.  
> Any new code lists to be included in the UBL 2.2 distribution need to be identified.  This includes those that are included in the default value validation XSLT (a data type qualification is now in the CCTS spreadsheet and was not in UBL 2.1), and those provided as a convenience for users (not seen in the CCTS spreadsheet).



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)