[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wss-m] Milestone CSD02 documents published
On Thu, Jun 30, 2011 at 10:09 AM, David Turner
<David.Turner@microsoft.com> wrote:
> Thank you Robin.
>
> I didn't realize I could create the request for public review before the publication of the CSDs. But now that I look at the form, I see I could have put "TBD" as a place holder for the CSD URI. Nevertheless, I am working on it right now.
David, I understand the possible confusion (on two points) and you
are certainly not the first Chair to get tripped up here. There are
two separate submission request forms for processing CSD and
PR (CSPRD), as I attempted to clarify in a note to Chairs,
but it merits further clarification. See below - [1].
The mention of a "CSD URI:" ("...or enter "TBD" if the URI has not
yet been assigned.") appears in the Public Review request
form (B) but not in the CSD upload request form (A)
A: Committee Specification Draft Creation / Upload Request
http://www.oasis-open.org/resources/tc-admin-requests/committee-specification-draft-creation-upload-request
B: 30-Day Committee Specification Draft Public Review Request
http://www.oasis-open.org/resources/tc-admin-requests/30-day-committee-specification-draft-public-review-request
For your earlier JIRA requests in TCADMIN-499 through
TCADMIN-505, you used the correct forms for
"CSD Creation / Upload Request".
For public review -- a separate kind of Work Product Ballot under
TC Process rules (see Definition) -- the Public Review Request form
is needed. Because TCs often ballot for CSD and CSPRD in the
same meeting, they overlook the need for separate request forms.
I'd recommend speaking with Chet Ensign about any details in this
case.
- Robin
[1] http://lists.oasis-open.org/archives/chairs/201103/msg00002.html
- Are separate submission request forms needed for CD and PR?
Yes. TCs sometimes combine into a single meeting (or motion)
the approval of a WD at CSD/CND level and approval to advance
the CD to Public Review status. The TC Process allows direct
progression of a CSD or CND to CSPRD/CNPRD without an
intervening WD, but the CD - PR requests to TC Admin should be
made separately, using two different online forms, available
from the document titled "TC Administration Requests"
TC Administration Requests
http://www.oasis-open.org/resources/tc-admin-requests
See in that document the section: "Public Review Requests"
Different forms are used for different kinds of reviews. If
a TC desires a review period longer than the required
minimum number of days: use the form most similar to the
intent and present the special request in the Note field.
>
> David
>
> -----Original Message-----
> From: Robin Cover [mailto:robin@oasis-open.org]
> Sent: Wednesday, June 29, 2011 7:33 PM
> To: WSS-M TC List
> Cc: Robin Cover; Chet Ensign; Paul Knight
> Subject: [wss-m] Milestone CSD02 documents published
>
> FYI, the level CSD02 documents for Web Services Security Version 1.1.1 were installed earlier today:
>
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/
>
> Details for the spec documents and URIs are provided below [1].
>
> I would say "thank you for your patience" but that would be lame (in the extreme) in view of the processing delay, which I don't think anyone expected initially, and IMO doesn't represent a reasonable or sustainable TC Admin processing solution.
> I do deeply regret that the delay has held up your TC work.
>
> Chet Ensign communicated some of the reasons for queue buildup and backlog [2]. Alternate approaches for post-2010-10 era processing are being proposed in order to solve the problem.
>
> I am personally always prepared to apologize for my part in delay if it results from negligence, sloth, clumsiness, inattentiveness, indifference, or other fault (of which I have many). In this case I can apologize, but given the workload and management decisions about the queue, I don't think anything I might have done personally (other than continue 18-hour workdays) would have made much difference: other work was scheduled ahead of WSS-M CSD02 processing, some of which can be inspected in the queue (in cases where we have JIRA tickets). IMO there is a processing problem, and people assigned to the design of
> solution(s) are hard at work.
>
> Finally, in reviewing the JIRA tickets for annotation along with the TC list messages [4], I noted that reference is made to a "public review", but I'm not sure whether those mentions imply -- at this juncture -- a TC decision to advance the CSD02 Work Product to public review without any further revision. The "Minutes-2018-May" [3] referenced in the The Approval Link (e.g., in TCADMIN -499) mention desire for PR, but I do not see any JIRA tickets for PR. If the TC wants to proceed with that PR immediately (or ASAP), please contact Chet Ensign about JIRA submission requests and timetables from management.
>
> Cheers,
>
> - Robin Cover
>
> ========== References:
>
> [1] Document publication
>
> (1) Web Services Security X.509 Certificate Token Profile Version 1.1.1 Committee Specification Draft 02
> 18 May 2011
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-x509TokenProfile-v1.1.1-csd02.doc
> (Authoritative)
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-x509TokenProfile-v1.1.1-csd02.pdf
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-x509TokenProfile-v1.1.1-csd02.html
> http://www.oasis-open.org/committees/download.php/42750/wss-x509TokenProfile-v1.1.1-csd02.html
> JIRA: http://tools.oasis-open.org/issues/browse/TCADMIN-499
>
>
> (2) Web Services Security Username Token Profile Version 1.1.1 Committee Specification Draft 02
> 18 May 2011
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-UsernameTokenProfile-v1.1.1-csd02.doc
> (Authoritative)
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-UsernameTokenProfile-v1.1.1-csd02.pdf
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-UsernameTokenProfile-v1.1.1-csd02.html
> http://www.oasis-open.org/committees/download.php/42749/wss-UsernameTokenProfile-v1.1.1-csd02.html
> JIRA: http://tools.oasis-open.org/issues/browse/TCADMIN-500
>
>
> (3) Web Services Security: SOAP Message Security Version 1.1.1 Committee Specification Draft 02
> 18 May 2011
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-SOAPMessageSecurity-v1.1.1-csd02.doc
> (Authoritative)
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-SOAPMessageSecurity-v1.1.1-csd02.pdf
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-SOAPMessageSecurity-v1.1.1-csd02.html
> http://www.oasis-open.org/committees/download.php/42747/wss-SOAPMessageSecurity-v1.1.1-csd02.html
> JIRA: http://tools.oasis-open.org/issues/browse/TCADMIN-501
>
>
> (4) Web Services Security SAML Token Profile Version 1.1.1 Committee Specification Draft 02
> 18 May 2011
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-SAMLTokenProfile-v1.1.1-csd02.doc
> (Authoritative)
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-SAMLTokenProfile-v1.1.1-csd02.pdf
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-SAMLTokenProfile-v1.1.1-csd02.html
> http://www.oasis-open.org/committees/download.php/42746/wss-SAMLTokenProfile-v1.1.1-csd02.html
> JIRA: http://tools.oasis-open.org/issues/browse/TCADMIN-502
>
>
> (5) Web Services Security Rights Expression Language (REL) Token Profile Version 1.1.1 Committee Specification Draft 02
> 18 May 2011
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-rel-token-profile-v1.1.1-csd02.doc
> (Authoritative)
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-rel-token-profile-v1.1.1-csd02.pdf
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-rel-token-profile-v1.1.1-csd02.html
> http://www.oasis-open.org/committees/download.php/42745/wss-rel-token-profile-v1.1.1-csd02.html
> JIRA: http://tools.oasis-open.org/issues/browse/TCADMIN-503
>
>
> (6) Web Services Security Kerberos Token Profile Version 1.1.1 Committee Specification Draft 02
> 18 May 2011
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-KerberosTokenProfile-v1.1.1-csd02.doc
> (Authoritative)
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-KerberosTokenProfile-v1.1.1-csd02.pdf
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-KerberosTokenProfile-v1.1.1-csd02.html
> http://www.oasis-open.org/committees/download.php/42744/wss-KerberosTokenProfile-v1.1.1-csd02.html
> JIRA: http://tools.oasis-open.org/issues/browse/TCADMIN-504
>
>
> (7) Web Services Security SOAP Message with Attachments (SwA) Profile Version 1.1.1 Committee Specification Draft 02
> 18 May 2011
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-SwAProfile-v1.1.1-csd02.doc
> (Authoritative)
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-SwAProfile-v1.1.1-csd02.pdf
> http://docs.oasis-open.org/wss-m/wss/v1.1.1/csd02/wss-SwAProfile-v1.1.1-csd02.html
> http://www.oasis-open.org/committees/download.php/42748/wss-SwAProfile-v1.1.1-csd02.html
> JIRA: http://tools.oasis-open.org/issues/browse/TCADMIN-505
>
> [2] queue and backlogs
> http://lists.oasis-open.org/archives/wss-m/201106/msg00004.html
>
> [3] http://www.oasis-open.org/committees/download.php/42220/Minutes-2018-May.txt
>
> "6. Request the start of a public review for CSD02
> Motion - Monica
> 2nd - Rich
> No objections
> [Action item] dturner to submit docs to TC Admin to start public review."
>
> [4] public review mentions
>
> Groups - WSS-M TC Telco cancelled
> http://lists.oasis-open.org/archives/wss-m/201106/msg00006.html
> "Still waiting for public review to start. TC Admin says it should be this week."
>
> Update on CSDs and Public Review
> http://lists.oasis-open.org/archives/wss-m/201106/msg00004.html
> "According to Chet, our CSDs should be published any day now (see attached emails) followed by the start of the public review."
>
>
>
>
> --
> Robin Cover
> OASIS, Director of Information Services
> Editor, Cover Pages and XML Daily Newslink
> Email: robin@oasis-open.org
> 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
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>
--
Robin Cover
OASIS, Director of Information Services
Editor, Cover Pages and XML Daily Newslink
Email: robin@oasis-open.org
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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]