RE: [wss-m] RE: Ballot update

[Hal Lockhart <hal.lockhart@oracle.com>]

I think the key point is that the procedure by which the existing OASIS Standards were contributed to this TC was already ground breaking. It is my understanding that this entire situation is without precedent. However, since the TC process (law) is silent on this point, it falls into the realm of administrative policy and procedures (regulation) which have traditionally been at the discretion of the TC Admin.

I believe that locating the documents in the same directory will be beneficial to consumers of these standards who are simply interested in using the latest version or perhaps seeing what has changed in this version.

However, probably the most critical thing is to make sure that the section of the OASIS front page which contains links to OASIS Standards and the "specs" page which they point to is updated to show all the various versions in one place and point to the correct locations wherever they may be.

Hal

> -----Original Message-----
> From: Robin Cover [mailto:robin@oasis-open.org]
> Sent: Monday, January 31, 2011 2:09 PM
> To: David Turner
> Cc: WSS-M TC List; Robin Cover
> Subject: Re: [wss-m] RE: Ballot update
> 
> 
> > I think we can make some reasonable arguments in support of 
> an exception
> 
> It will be interesting to see what the TC members think about a
> proposal to store WSS-M TC's documents in the earlier TC's
> OASIS Library repository.  The message below indicates that
> TCs are not allowed to put documents in the directory tree of
> another TC.  I do think that's been the operational rule, and I
> don't know of exceptions.  Stated more broadly:
> 
> Summary: Hitherto, as far as I know, the publication venues
> allowable for one TC have been off limits to members of other
> TCs.  Members from FOO TC can upload or publish to their own
> designated mailing list, Kavi document repository, Wiki, SVN,
> OASIS Library directory, JIRA project, etc but not to those
> publication areas designated for the BAR TC.
> 
> However, I do not recall hearing any discussion about expectations
> and operational rules for maintenance TCs, which are rather new.
> 
> The question may be, in broad and general terms:
> 
> "Shall members of an OASIS maintenance TC [viz., chartered
> to do maintenance activity], be allowed [or required?] to publish
> their [interim draft and] final deliverables in the OASIS Library
> [and other publication venues] in the publication areas designated
> for work approved by different TCs (i.e., TCs other than the new
> maintenance TC) in cases where their maintenance activity
> relates to deliverables originally produced by other TCs?"
> 
> If anyone on the WSS-M TC knows of related situations, or about
> explicit rules I may have overlooked, or failed to comprehend,
> please let me know.
> 
> Thanks!
> 
> - Robin
> 
> Robin Cover
> Interim TC Administrator
> OASIS, Director of Information Services
> Editor, Cover Pages and XML Daily Newslink
> Email: robin@oasis-open.org
> Staff bio: http://www.oasis-open.org/who/staff.php#cover
> Cover Pages: http://xml.coverpages.org/
> Newsletter: http://xml.coverpages.org/newsletterArchive.html
> Tel: +1 972-296-1783
> 
> On Mon, Jan 31, 2011 at 12:30 PM, David Turner
> <David.Turner@microsoft.com> wrote:
> > The ballot will be delayed a little longer as we have 
> discovered some
> > additional items we need to address.
> >
> >
> >
> > ·         We need to add the names of the participants to the
> > Acknowledgements section. This will include everyone in the 
> TC listed as
> > Member or Voting Member.
> >
> > ·         All normative references to the SOAP Messaging 
> Security spec need
> > to be updated to point to the v1.1.1 spec.
> >
> >
> >
> > The second point raises an important issue regarding the 
> URLs for the
> > LOCATION of the new specifications (this does NOT affect 
> the namespace URIs
> > or the location of the schemas).
> >
> >
> >
> > According to the latest OASIS Naming Directives [1], all 
> documents from this
> > TC MUST use this base URL:
> >
> >                 http://docs.oasis-open.org/wss-m/wss/v1.1.1/
> >
> >
> >
> > The base URL for the current WSS specs is:
> >
> >                 http://docs.oasis-open.org/wss/1.1/
> >
> >
> >
> > Since one goal of the TC is to minimize variations between 
> the versions, the
> > optimal solution would be to use “/wss-m/wss/” for all 
> documents EXCEPT the
> > final OASIS Standard, where we would use just “/wss/”. The 
> problem with this
> > solution is that TCs are not allowed to put documents in 
> the directory tree
> > of another TC.
> >
> >
> >
> > I think we can make some reasonable arguments in support of 
> an exception
> > without setting a dangerous precedent, but I would like to 
> hear from the
> > rest of the TC before starting down that path.
> >
> >
> >
> > David
> >
> >
> >
> > [1]
> > 
> http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives
> .html#URIs-Resources
> >
> >
> >
> > From: David Turner
> > Sent: Thursday, January 27, 2011 10:54 AM
> > To: wss-m@lists. oasis-open. org (wss-m@lists.oasis-open.org)
> > Subject: Ballot update
> >
> >
> >
> > FYI - I want to let everyone know that I’m sorting out a 
> number of details
> > with Robin Cover, so it’s taking longer than I expected to 
> set up the
> > ballot(s). (Go ahead Hal, or was is Rich, say “I told you so” J  )
> >
> >
> >
> > David
> 
> 
> 
> -- 
> 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/who/staff.php#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
> 
>