Date: Thu, May 16, 2013 at 2:46 PM
Subject: [tc-administration] Appeal to the charter clarification recently made by the TOSCA TC
To: tc-administration@lists.oasis-open.org
Cc: Scott McGrath <scott.mcgrath@oasis-open.org>, Jacques Durand <JDurand@us.fujitsu.com>, Patrick Durusau <patrick@durusau.net>
OASIS TC Administrator,
On 1st May 2013 TC Admin announced to OASIS Members that the TOSCA TC had voted to clarify its charter, the TC ballot for which passed successfully on 16th April 2013: https://lists.oasis-open.org/archives/members/201305/msg00001.html
We understand that there was discussion about whether a charter clarification or a re-chartering was appropriate, each of which require a different process as laid out in sections 2.11 and 2.12, respectively, of the TC Process.
Having read the announcement and the red-line charter changes, it is our belief that the wrong process was used, and we request that TC Admin invalidate the charter clarification ballot and require the TOSCA TC to apply the re-chartering process as laid out in 2.12. We reached this conclusion by studying the Scope of Work and Out of Scope sections of the original charter with those of the new charter.
The problem is that the new charter places an item within the scope of the TC which the original charter had explicitly declared as out of scope, thus widening not narrowing the scope of the TC. The original charter had the following wording in the Out of Scope Section:
1. The definition of concrete cloud services, i.e. the definition of concrete component types, relationship types, and topology templates. However, standardization of a basic set of concrete component types, relationship types and properties is intended to be enabled by this work, and could begin in parallel with this project, with appropriate coordination.
The new charter has the following wording in the Scope of Work section:
3. Standardization of a basic set of non-vendor specific, concrete component types, relationship types and properties, which includes all attributes of the type and all contained elements.
and has removed the following text from the out of scope section:
, and could begin in parallel with this project, with appropriate
coordination.
The original charter specified that work on standardizing concrete component types, whether vendor specific or not, would be done in other, yet to be chartered, Technical Committees. Changing this and bringing this work into the TOSCA TC widens the scope of the original TC and increases its IPR scope. Furthermore, the clarification of vendor vs. non-vendor specific components is immaterial, since the result of the standardization process would render them all non-vendor specific. When the IPR scope of a TC is widened, TC Members acquire new obligations that need to be considered within Member organizations.
As members of the TAB we are concerned about the long term integrity of the TC Process, and are worried that the charter modifications above - if accepted as a charter clarification - would set a bad precedent for other TCs. We therefore request that based on the widening of the IPR scope in the new charter, the TC should be re-chartered as per 2.12 of the TC process.
Regards,
Martin Chapman (Oracle)
Patrick Durusau (Individual)
Jacques Durand (Fujitsu Limited)
--
Martin Chapman | Standards Strategy & Policy EMEA
Mobile: +353 87 179 0627
ORACLE Ireland
Oracle is committed to developing practices and products that help protect the environment |
/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open