Re: [codelist] Submission request to advance Code List Representation (g

Andrea

Il giorno 3 mar 2023, alle ore 23:14, Jamie Clark <jamie.clark@oasis-open.org> ha scritto:

Dear committee members: At this early stage, let me mention: I do understand the connection to SC 32, but a PAS ballot once submitted will be a JTC1-wide ballot, and is not also routed by them to a subcommittee.
So, do you wish to simply notify SC 32 out of courtesy at the time you request a ballot? Or engage with them to seek their views before officially asking for the ballot to start?
Unless there are special circumstances, or anticipated opposition, may I suggest that we write SC 32 while the 30 day submission review is pending, to simply inform them of your intent to submit a PAS afterwards, and invite their support and any questions they may have?
Kind regards, Jamie

Sent from my mobile

On Mar 3, 2023, at 13:02, Chet Ensign <chet.ensign@oasis-open.org> wrote:

ï
Andrea,

The terms looks good. The next step is to use https://www.oasis-open.org/project-administration-support-requests/form-request-a-special-majority-vote-to-approve-submitting-an-oasis-standard-to-another-organization/ to request that I run a Special Majority Vote to approve submitting it to Gershon and Francis and on to the members for the 30 day review.

Looking forward to keeping it moving along!

/chet

On Fri, Mar 3, 2023 at 10:18âAM Andrea Caccia <andrea.caccia.oasis@gmail.com> wrote:
Fellow CLR TC members,
here follows the text of the Submission request to advance Code List Representation (genericode) Version 1.0 to an International Standard, modified as agreed during the 2022-03-03 meeting.

Andrea
----------------
The following text parts - marked up in cursive - have been copied directly from the requirements stated in the relevant section of the current OASIS Liaison Policies page at: https://www.oasis-open.org/policies-guidelines/liaison/#submitwork
Any submission request delivered to the OASIS President under this policy must be in writing, and must include the following:
a. The name(s) of the submission requester(s), that is, the TC, the Member Section, or the OASIS Organizational Members that support the submission request as described in section 1(d).
OASIS Code List Representation TC
b. The name of the intended receiving standards organization. The request may also suggest the committee or group in that organization which should process that submission.
ISO/IEC JTC 1 Secretariat (suggesting SC 32 "Data management and interchange" as genericode includes a reference to Open-edi ISO/IEC 14662:2010 Information technology - Open-edi reference model)
Mc. The intended status or outcome that the request seeks from the receiving organizationÃs process; and a short description of the receiving organizationÃs approval process, including estimated time required, stages of approval and who votes at each stage.
Intended status: Advance Code List Representation (genericode) Version 1.0 OASIS Standard to an ISO/IEC International Standard
Base process: ISO/IEC JTC 1 PAS Transposition Process involving a Draft International Standard (DIS) ballot followed by a Ballot Resolution Meeting (BRM) (if there are comments during ballots), and potentially a Final DIS (FDIS) Ballot.
Stages of approval: https://www.iso.org/stage-codes.html - Stage 40
d. An explanation of how the submission will benefit OASIS.
Advancing Code List Representation (genericode) Version 1.0 to an international standard draws international attention to the work done by OASIS and to the organization itself, and governments/regulators may be more inclined to use the standard because of its ISO/IEC status.
This will help nurture and expand the ongoing liaisons with ISO/IEC JTC 1.
Further, this submission will help maintain OASIS in good standing as a recognized ISO/IEC JTC 1 PAS submitter organization.
e. The expected licensing, copyright and other intellectual property terms that will be used by the receiving organization in regard to the submission.
ISO/IEC JTC 1 will expect that OASIS will abide by the ISO/IEC/ITU-T Common Patent Policy (indicated by at least notifying ISO/IEC of any patent declarations in the required Explanatory Report), and will provide ISO/IEC with sufficient copyright license to modify and publish the resulting ISO/IEC Standard.
The TC offers publication of the standard on the condition that it's not changed otherwise.
f. A statement of the intended future plans for versioning and maintenance of the OASIS Standard and/or Approved Errata for that standard, and the expected roles of OASIS and the receiving organization. This must include clear statements of the rules of the receiving organization applicable to maintenance of an approved submitted standard, and to future versions of that standard; any requirements regarding the submission of future versions; and a description of how OASIS and the submission requesters expect to comply with those rules.
The OASIS Code List Representation Technical Committee will continue to maintain the Code List Representation (genericode) Version 1.0 OASIS Standard and produce future revisions of it.
For this specific submission (Code List Representation (genericode) Version 1.0 OASIS Standard) to ISO/IEC JTC 1, OASIS will request to be named the "JTC 1 designated maintenance group" and will follow the required maintenance procedures (including Systematic Review).
In the course of time, if there are substantive changes to Code List Representation (genericode) Version 1.0 (either via the Approved Errata process or through a new version), OASIS may submit the modified document (or future version) to ISO/IEC JTC 1 at some point in the future.

--
Chet Ensign
Chief Technical Community Steward
OASIS Open

+1 201-341-1393
chet.ensign@oasis-open.org
www.oasis-open.org

codelist message

Chet Ensign