Terminology for "Track" in the CloudAuthZ TC proposal

Congratulations to the proposers of the prospective

OASIS CloudAuthZ TC for the milestone publication of the

proposed draft charter [1].

In Section 1(d) "List of deliverables", list items #2 and #3

make reference to:

  "a OASIS Committee Specification Track document"

I would recommend that the language in these two items be

adjusted to reflect the defined terms in the TC Process, for

two reasons:

a) TC Process classifies Work Products as belonging to one

of two "Tracks": "Standards Track" or "Non-Standards Track"

There is no such thing as a "Committee Specification Track."

b) From the language used, someone might conclude that the

draft Charter intends to assert that the two deliverables'

progress will be terminated at the "Committee Specification"

level, and that no higher approval level will be sought

(e.g., "Candidate OASIS Standard", "OASIS Standard").

If some subtle meaning is intended, then it should be made

clear.  My guess is that the text can be clarified simply and

accurately by using the official terms in list items 1-3:

"Non-Standards Track" (in #1) and "Standards Track" (in 2-3).

Thanks!

[1] "Proposed Charter for Cloud Authorization (CloudAuthZ) TC"

https://lists.oasis-open.org/archives/oasis-charter-discuss/201210/msg00003.html

-- 
Robin Cover
OASIS, Director of Information Services
Editor, Cover Pages and XML Daily Newslink
Email: 

Staff bio: http://www.oasis-open.org/people/staff/robin-cover
Cover Pages: http://xml.coverpages.org/

Newsletter: http://xml.coverpages.org/newsletterArchive.html
Tel: +1 972-296-1783