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: [OASIS Issue Tracker] (UBL-27) Code lists for UBL 2.2


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

Ken Holman edited comment on UBL-27 at 9/14/17 5:39 PM:
--------------------------------------------------------

I am going through the process of automating as much as possible the generation of the suite of genericode files for the current and future UBL distributions.  This allows us to parameterize the process as much as possible so that at any time we can pull up the latest code lists.  An example is that we can do this for every public review.

I'm trying to figure out the JIRA buttons that will allow me to attach my current work on the list-level metadata for all of the files.  I can't see the button now while I am editing a comment, so I will look again after I post this comment.  The file name is "master-code-list-UBL-2.2.xml".  If I cannot attach the file, I will post it to the mail list as a reply to the JIRA message that goes to the list.

If you can find the time to review the metadata and advise me of any changes, that would be very helpful.  Meanwhile, I will now write the actual code to support the new master file.

This is the link that was generated by the mail archive to the attachment:  https://lists.oasis-open.org/archives/ubl/201709/msg00013/master-code-list-UBL-2.2.xml


was (Author: gkholman):
I am going through the process of automating as much as possible the generation of the suite of genericode files for the current and future UBL distributions.  This allows us to parameterize the process as much as possible so that at any time we can pull up the latest code lists.  An example is that we can do this for every public review.

I'm trying to figure out the JIRA buttons that will allow me to attach my current work on the list-level metadata for all of the files.  I can't see the button now while I am editing a comment, so I will look again after I post this comment.  The file name is "master-code-list-UBL-2.2.xml".  If I cannot attach the file, I will post it to the mail list as a reply to the JIRA message that goes to the list.

If you can find the time to review the metadata and advise me of any changes, that would be very helpful.  Meanwhile, I will now write the actual code to support the new master file.

> 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: Ken Holman
>            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)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]