[xacml] RE: Request for clarification on"After ... final changes to the document"

["Karl F. Best" <karl.best@oasis-open.org>]

Anne:

1. TC approves the spec as a CS
2. Send out for public review
3. Fix the spec as suggested by comment received during the review
4. repeat 2-3 as necessary
5. re-approve as a new CS
6. submit to OASIS

> Are we free to make any changes we like at
> the end of the 30-day public review period, so long as we
> re-approve the work as a Committee Specification?  If not,
> exactly what changes may be made without going through yet
> another 30-day review period?

Looking for the corner cases, eh? :-)

The spec should be complete when you send it out for review. If you
make major changes that were not part of the public review you should
send the spec out for review again. The only time you would not want
to do another review is when all you've done is fixed comments.

The purpose of all of the above is to get the spec as clean as
possible before submitting it to OASIS. Previously the TC would submit
the spec to OASIS then we would have a 90 day member review period
before voting. But a review period always produces comments, and we
didn't have any way of handling those comments before voting started.
So under the new version of the Process the TC will have the review
period(s), fix and re-approve the spec, submit to OASIS members for a
short familiarization period (no comments), then we'll do the voting.

</karl>
=================================================================
Karl F. Best
OASIS - Director, Technical Operations
+1 978.667.5115 x206
karl.best@oasis-open.org  http://www.oasis-open.org


> -----Original Message-----
> From: Anne Anderson [mailto:Anne.Anderson@Sun.com]
> Sent: Monday, October 07, 2002 2:45 PM
> To: Karl.Best@oasis-open.org
> Cc: XACML TC
> Subject: Request for clarification on "After ... final
> changes to the
> document"
>
>
> http://www.oasis-open.org/committees/process.shtml#standards_process
> says:
>
>    Review must take place for a minimum of 30 days, during which
>    time no changes may be made to the document. Comments must be
>    collected via the TC's public comment list. The TC must record
>    the comments received as well as the resolution of those
>    comments. The TC may conduct any number of additional review
>    cycles (i.e. collecting comments, making edits to the
>    specification, sending out a revised version for review again,
>    etc.) before deciding that the review is complete. After the
>    conclusion of the review and final changes to the document,
>    the TC must re-approve the work as a Committee Specification
>    before submitting it to OASIS.
>
> "After the conclusion of the review and final changes to the
> document, the TC must re-approve the work as a Committee
> Specification before submitting it to OASIS."  To me, this is
> somewhat ambiguous.  Are we free to make any changes we like at
> the end of the 30-day public review period, so long as we
> re-approve the work as a Committee Specification?  If not,
> exactly what changes may be made without going through yet
> another 30-day review period?
>
> Anne Anderson
> --
> Anne H. Anderson             Email: Anne.Anderson@Sun.COM
> Sun Microsystems Laboratories
> 1 Network Drive,UBUR02-311     Tel: 781/442-0928
> Burlington, MA 01803-0902 USA  Fax: 781/442-1692
>
>