Appeal of TC Administrator Action on 10/23/2012 - Call for Participation: Cloud Authorization (CloudAuthZ) TC

[Patrick Durusau <patrick@durusau.net>]

Greetings,

Please accept this email an an appeal of TC Administrator Action (and 
inaction, see below), dated 10/23/2012, consisting of a Call for 
Participation: Cloud Authorization (CloudAuthZ) TC.

Nature of Objection:

I filed numerous comments on the proposed Cloud Authorization 
(CloudAuthZ) charter:
https://lists.oasis-open.org/archives/oasis-charter-discuss/201210/msg00027.html

No pointers to resolution of those comments posted were before (or 
since) the call for participation:
https://lists.oasis-open.org/archives/tc-announce/201210/msg00016.html

Direct and Material Adverse Effects:

Violation of fundamental OASIS TC process places OASIS members who want 
to follow the TC process in an awkward position.

The OASIS TC process is designed to conduct the TC process in a open (to 
the public) manner and to give fair notice to members of potential 
issues in a TC. So that OASIS members can make meaningful choices about 
which TCs to join and just as importantly, which ones to not join.

When a TC Process as specific and fundamental as TC formation is 
violated, it diminishes confidence in the OASIS TC process.

Not to mention impairing the OASIS brand when inadequate charters are 
proposed for OASIS TCs. (see my comments in that regard).

Sections of OASIS Policy:

The last two paragraphs of the formation of a TC process read:

> The proposer group may amend their submission at any time until the 
> 28th day after the submission (except that changes to the roster of 
> proposers may occur at any time until the final posting). By the 28th 
> day the proposer group must post a pointer to an account of each of 
> the comments / issues raised during that review, along with its 
> resolution.
>
> No later than the 30th day after the submission, if those pointers 
> have been posted, and the last version of the submission from the 
> proposer group meets the requirements of these rules, the OASIS TC 
> Administrator must post them to the OASIS Membership with a Call For 
> Participation and an announcement of a first meeting. Otherwise, the 
> Convener may obtain a single 10-day extension for posting a compliant 
> proposal with the OASIS TC Administrator.

In full see: 
https://www.oasis-open.org/policies-guidelines/tc-process#formation

The final sentence of the first paragraph:

"By the 28th day the proposer group must post a pointer to an account of 
each of the comments / issues raised during that review, along with its 
resolution."

Has been violated by the proposer group.

The first sentence of the second paragraph reads:

"No later than the 30th day after the submission, if those pointers have 
been posted, and the last version of the submission from the proposer 
group meets the requirements of these rules, the OASIS TC Administrator 
must post them to the OASIS Membership with a Call For Participation and 
an announcement of a first meeting."

That is the TC Administrator must post "them" (the pointers to the 
resolution of comments and the call for participation) to the OASIS 
membership, etc.

Clearly this is intended to put potential TC members on notice of the 
comments and their resolution, so OASIS members can determine for 
themselves if participation in a TC is worth while.

Action/InAction at issue:

Failure of the TC Administrator to require submission of the pointers to 
resolutions of comments prior to issuing the call for participation. 
(inaction)

The issuance of the call for participation in the CloudAuthZ TC in the 
absence of pointers to the resolution of comments. (action)

Specific Remedial Actions:

Closing of the CloudAuthZ TC as a failure to form under the OASIS TC rules.

Previous Efforts To Resolve:

I have contacted the TC Adminstrator concerning this issue.

My understanding is that no communication has been received from the 
proposing group on this issue.

Filing of resolutions now would not cure the prior violation of the 
OASIS TC Process and failure to follow the dates for TC formation, 
previously approved by the Board.

Hope everyone is having a great week!

Patrick

--
Patrick Durusau
patrick@durusau.net
Technical Advisory Board, OASIS (TAB)
Former Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog):http://tm.durusau.net
Homepage:http://www.durusau.net
Twitter: patrickDurusau