[OASIS Issue Tracker] (UBL-11) Revision Methodology as a Committee Note

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

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

Ken Holman commented on UBL-11:
-------------------------------

Now in the hands of TC Admin for processing:

  https://issues.oasis-open.org/browse/TCADMIN-2085

Note that I was mislead by https://www.oasis-open.org/resources/tc-admin-requests/committee-note-ballot-request where it states a special majority vote (on Kavi) is to be requested.  In fact, https://www.oasis-open.org/policies-guidelines/tc-process#standApprovProcess states that only a full majority vote (during a meeting) is required.  TC Admin is processing our voting and request as the equivalent to an approval.

> Revision Methodology as a Committee Note
> ----------------------------------------
>
>                 Key: UBL-11
>                 URL: https://issues.oasis-open.org/browse/UBL-11
>             Project: OASIS Universal Business Language (UBL) TC
>          Issue Type: New Feature
>          Components: Future tasks for consideration
>            Reporter: Ken Holman
>            Assignee: Ken Holman
>
> Create a Committee Note documenting for those inside and outside of the committee the process the committee will use to solicit and incorporate candidates for inclusion in a revision of UBL.



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