[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Proposed WS-DD charter clarification
I took the action item (#110) to draft the charter clarification
we discussed at the last face-to-face meeting in Irvine. The existing WS-DD charter is posted at http://www.oasis-open.org/committees/ws-dd/charter.php.
The last paragraph of the existing Deliverables section describes the work that
the TC will do following the publication of version 1.1 of the specifications.
It reads as follows: Ratification of the DPWS,
WS-Discovery, and SOAP-over-UDP specifications as OASIS standards, including a
brief maintenance period, after the specifications are ratified as a standard,
to address any errata, will mark the end of the TC's lifecycle. I propose that we amend the charter by replacing that entire paragraph
with the following: Following approval of
Devices Profile for Web Services Version 1.1, WS-Discovery Version 1.1, and
SOAP-over-UDP Version 1.1 specifications as OASIS standards, the TC will enter
an extended maintenance period during which it may adopt Approved Errata for DPWS,
WS-Discovery, or SOAP-over-UDP in accordance with the OASIS Technical Committee
Process. The maintenance period will continue until the TC is Closed in
accordance with Section 2.15 of the OASIS Technical Committee Process. During
the maintenance period, in addition to any Approved Errata that may be adopted,
the TC may deliver updated DPWS, WS-Discovery, or SOAP-over-UDP specifications,
or any combination thereof, as revised OASIS standards, to address the
following, if required: (1)
Update the references in DPWS to WS-Eventing, WS-MetadataExchange, and
WS-Transfer specifications to reference the W3C Recommendation version of those
specifications, and profile those specifications as necessary to accommodate
changes included in them, provided those changes are within the Scope of Work; (2)
Update the reference in DPWS to WS-I Basic Profile Version 1.1 specification to
reference the WS-I Basic Profile 2.0 specification, if that specification is
approved in WS-I prior to or at approximately the same time as approval of
WS-Eventing, WS-MetadataExchange, and WS-Transfer specifications as a W3C
Recommendation; (3)
Incorporate Substantive Changes, within the Scope of Work, resulting from (a)
reconsideration of technical issues originally introduced to the TC prior to
approval of Version 1.1 of DPWS,
WS-Discovery, and SOAP-over-UDP specifications but deferred for later
consideration, or (b) resolution of specification ambiguities or flaws
identified through implementation experience or interoperability testing of
elements of Version 1.1 of DPWS, WS-Discovery, and SOAP-over-UDP
specifications; and, (4)
Incorporate previous Approved Errata and other corrections, clarifications and
editorial changes that are not Substantive Changes. This would enable the TC to continue after version 1.1 of the
specifications are published in order to maintain the specs (editorial errata),
and to update DPWS to incorporate references to WS-Eventing,
WS-MetadataExchange, and WS-Transfer once W3C WA-RA completes its work. It also
enables the TC to accept additional changes to the specs that are within the
existing scope of work, to handle deferred issues from the 1.1 work or in
response to flaws identified in the 1.1 specs. As we discussed in Irvine, if the TC decides later that it wants
to expand the specs further than that, it would require Rechartering the TC to
expand the Scope. Note that this charter clarification does not define a fixed time
period or other end point for the TC; either we or OASIS Administration would
decide when to close the TC based on Section 2.15 of the OASIS TC Process (see http://www.oasis-open.org/committees/process.php#closingTC).
As a reminder, the TC Process (at http://www.oasis-open.org/committees/process.php#charterClarification)
says that the charter clarification vote is conducted electronically by the
OASIS TC Administrator and requires a Special Majority Vote of the TC to pass. A
Special Majority Vote requires Yes votes from at least 2/3rds of the Voting
Members, and that no more than 1/4th of the Voting Members vote No. We can do
this at any time by sending the proposed clarification to the Administrator and
requesting the vote; she would have 15 days to start the vote or tell us why it
cannot go forward. I look forward to seeing your comments and to discussing this with
you in upcoming teleconferences. --
Toby Toby Nixon |
Senior Standards Program Manager | Windows Device and Storage
Technologies | Microsoft Corporation toby.nixon@microsoft.com
| www.microsoft.com
| V: +1 425 706 2792 | M: +1 206 790 6377 | F: +1 425
708 4811 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]