Subject: Request to submit an OASIS Standard for adoption by another organization
(Edited only to repair a URL cited in the document and fix two typos)The sections of this document follow the like-numbered sections of the policy for submitting OASIS Standards for adoption by other organizations found at:
https://www.oasis-open.org/policies-guidelines/liaison#submitwork 1. Qualification of submission requirements: (a) The proposed submission is an OASIS Standard.OASIS Universal Business Language 2.1 was approved by a member ballot that closed 2013-11-04 23:59UTC with no negative votes cast.
(b) The receiving standards organization is a de jure standards authority, preferably global in geographic scope.
The International Organization for Standardization and International Electrotechnical Commission Joint Technical Committee 1 (ISO/IEC JTC 1) is a de jure standards authority with a global geographic scope.
(c) A written submission request to submit the OASIS Standard, as specified in Section 2, is submitted to the President by any one of the parties described in the following options: Open TC. If the Technical Committee that originally developed the OASIS Standard is open (not closed), there are the following two options: ... If there is no such Member Section, then the TC may submit the request, after approving a motion to do so by a Special Majority Vote.
The UBL TC is currently open and on 06 November 2013 approved a motion to ask TC Administration to run a Special Majority Vote to support the submission:
https://lists.oasis-open.org/archives/ubl/201311/msg00008.html 2. Written submission request: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).
The OASIS Universal Business Language Technical Committee is requesting this submission: http://www.oasis-open.org/committees/ubl
(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.
The intended receiving standards Organization is International Organization for Standardization and International Electrotechnical Commission Joint Technical Committee 1 ISO/IEC JTC 1.
The UBL TC suggests that Subcommittee 32 "Data Management and Interchange" http://www.jtc1sc32.org/ and its "e-Business" Working Group 1 http://www.jtc1sc32wg1.org/ should process this submission.
As justification for this choice, UBL 2.1 OASIS Standard documents the roles its components play in the Business Operational View and Functional Services View of the ISO/IEC 14662:2010 model:
http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html#A-OPEN-EDI(c) 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.
The intention is for the UBL 2.1 OASIS Standard to be progressed through the JTC 1 Publicly Available Submissions process for approval by national body members. The submission is balloted using the Draft International Standard and Final Draft International Standard approval procedures used for all ISO/IEC International Standards. In addition, the JTC 1 process guarantees that the result will not diverge from the external organization's documents without its consent, and that the external organization is fully engaged in the international approval. As JTC 1 is a Joint Technical Committee of both ISO and IEC, its standards carry both the ISO and IEC logos.
The resulting ISO Standard and the OASIS Standard will be technically equivalent, while through editorial requirements the specification documents may have differences in appearance.
(d) An explanation of how the submission will benefit OASIS.OASIS will benefit by having the UBL 2.1 OASIS Standard able to be referenced or embraced by national bodies that are currently prohibited by internal rules from considering specifications not endorsed as de jure standards.
Wider visibility of UBL 2.1 should attract new participants who may be interested in contributing to further development of the specification to meet specific national body requirements.
(e) The expected licensing, copyright and other intellectual property terms that will be used by the receiving organization in regard to the submission.
The licensing, copyright and other intellectual property terms (Royalty Free on Limited Terms) will not change as UBL 2.1 will continue development within OASIS, with future revisions submitted as addenda and maintenance releases of the specification so as to keep the ISO/IEC specification and the OASIS specification technically equivalent.
(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.
It is expected that OASIS and ISO/IEC JTC 1 will enter into a memorandum of principles regarding the maintenance of UBL along the lines published at http://www.itscj.ipsj.or.jp/sc34/open/1148a.pdf for the OpenDocument Format Standard.
The maintenance of UBL is expected to be assigned to the OASIS UBL TC. Through the agreed memorandum OASIS and JTC 1 will commit to keep their specifications technically equivalent through the use of Approved Errata and Technical Corrigenda, per the respective OASIS and JTC 1 procedures for corrective maintenance. Subsequent revisions of UBL 2.1 would originate in OASIS and then be contributed to JTC 1 via their amendment process.
-- Public XSLT, XSL-FO, UBL & code list classes: Melbourne, AU May 2014 | Contact us for world-wide XML consulting and instructor-led training | Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm | Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/ | G. Ken Holman mailto:gkholman@CraneSoftwrights.com | Google+ profile: https://plus.google.com/116832879756988317389/about | Legal business disclaimers: http://www.CraneSoftwrights.com/legal |