OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tc-announce message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: WSN v1.3 Submitted for OASIS Standard

OASIS Members:

The OASIS Web Services Notification Technical Committee has submitted the
following specification set, which is an approved Committee Specification, to be
considered as an OASIS Standard:

Web Services Base Notification v1.3
Web Services Brokered Notification v1.3
Web Services Topics v1.3

The text of the TC submission is appended.

You now have until 15 September to familiarize yourself with the submission and
provide input to your organization's voting representative.

On 16 September, a Call For Vote will be issued to all Voting Representatives of
OASIS member organizations. They will have until the last day of September,
inclusive, to cast their ballots on whether this Committee Specification should
be approved as an OASIS Standard or not.

Members who wish to discuss this ballot may do so through 

In accordance with the OASIS Technical Committee Process, this Committee
Specification has already completed the necessary 60-day public review period as
noted in the submission below.

The normative TC Process for approval of Committee Specifications as OASIS
Standards is found at

Any statements related to the IPR of this specification are posted at:

Your participation in the review and balloting process is greatly appreciated.


Mary P McRae
Manager of TC Administration, OASIS
email: mary.mcrae@oasis-open.org
phone: 603.232.9090


  1. Links to the approved Committee Specification in the TC's document
repository, and any appropriate supplemental documentation for the
specification, both of which must be written using the OASIS templates. The
specification may not have been changed between its approval as a Committee
Specification and its submission to OASIS for consideration as an OASIS
Standard, except for the changes on the title page and running footer noting the
approval status and date.

These are


   2. The editable version of all files that are part of the Committee

These are


  3. Certification by the TC that all schema and XML instances included in the
specification, whether by inclusion or reference, including fragments of such,
are well formed, and that all expressions are valid;

I can certify that all the schemas and wsdl files are valid, and the fragments
of XML that appear in the spec are well-formed.

   4. A clear English-language summary of the specification;

WS-Notification is a family of related specifications that define a standard Web
services approach to notification using a topic-based publish/subscribe pattern.
It includes: standard message exchanges to be implemented by service providers
that wish to participate in Notifications, standard message exchanges for a
notification broker service provider (allowing publication of messages from
entities that are not themselves service providers), operational requirements
expected of service providers and requestors that participate in notifications,
and an XML model that describes topics. The WS-Notification family of documents
includes three normative specifications: WS-BaseNotification,
WS-BrokeredNotification, and WS-Topics.

   5. A statement regarding the relationship of this specification to similar
work of other OASIS TCs or other standards developing organizations;

The WSN specifications make use of the OASIS WSRF specifications, and are
themselves used by OASIS WSDM.

A spec similar to WS-BaseNotification, called WS-Eventing, has been submitted to
the W3C as a member submission, see http://www.w3.org/Submission/2006/03/

The W3C has noted the similarity to the work of the WS-Notification TC, see

   6. Certification by at least three OASIS member organizations that they are
successfully using the specification;

Certifications are available at



   7. The beginning and ending dates of the public review(s), a pointer to the
announcement of the public review(s), and a pointer to an account of each of the
comments/issues raised during the public review period(s), along with its

a) WS-BaseNotification and WS-BrokeredNotification have had three public
reviews. The dates were

13th July 2005 to 12th September 2005
20th December 2005 to 4th January 2006
9th June 2006 to 23 June 2006



b) WS-Topics has had two public reviews. The dates were

20th December 2005 to 18th February 2006 9th June 2006 to 23 June 2006



c) A summary of changes made since the first public review (including the
disposition of the final public review
comment) is at


   8. An account of and results of the voting to approve the specification as a
Committee Specification, including the date of the ballot and a pointer to the

The ballot ran from 24th July to 31st July 2006 - see
The TC agreed that we could combine voting on the Committee Specs and submission
of the specs into a single vote, so the ballot question was

"Shall the TC
(a) approve version 1.3 of WS-BaseNotification, at
as a Committee Specification, and
(b) approve version 1.3 of WS-BrokeredNotification, at
 as a Committee Specification, and
(c) approve version 1.3 of WS-Topics, at
http://docs.oasis-open.org/wsn/wsn-ws_topics-1.3-spec-pr-02.doc, as a Committee
Specification, and
(d) send all three specifications for membership vote as an OASIS Standard?

Thirteen out of Fourteen eligible members voted. Of these twelve were in favour
and one was against. The vote against was from Oracle corporation, with the
following comment "i object to d) at this stage without some confirmation that
there are implementations of a, b and c. I have no problem voting yes to a, b
and c.".  Note that the ballot was conducted before we had all the
certifications published (see response 6).

   9. An account of or pointer to votes and comments received in any earlier
attempts to standardize substantially the same specification, together with the
originating TC's response to each comment;

Not applicable

  10. A pointer to the publicly visible comments archive for the originating TC;


  11. A pointer to any minority reports submitted by one or more Members who did
not vote in favor of approving the Committee Specification, which report may
include statements regarding why the member voted against the specification or
that the member believes that Substantive Changes were made which have not gone
through public review; or certification by the Chair that no minority reports

Not applicable

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]