[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=63873#comment-63873 ] 

Ken Holman commented on UBL-27:
-------------------------------

I just found ISO's formal use of URNs here:  https://tools.ietf.org/html/rfc5141

The OASIS formal use of URNs is here:  https://tools.ietf.org/html/rfc3121

As mentioned above, there is no registration of "urn:un" and I can find no formal specification of its use.

We could begin using "urn:oasis" at this point, but because we used the "urn:un" in UBL 2.0 and 2.1, I worry that for consistency we should stick with the old values where we've already used them.

The canonical values are supposed to be consistent between versions.  But I suspect few users use the canonical values.  So, do we change to get rid of the bad values or do we stay the same for consistency?

> 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)