[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: [ws-dd] Proposed WS-DD charter clarification
|
Mike and I worked offline and put together this updated draft of
the proposed charter clarification, which we submit for your consideration. The
first text below [1] shows revision marks from the text I
originally submitted back on April 2, and below that [2] is a
clean text version. As a reminder, this text will replace the existing sentence
“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.”
that appears in the Deliverables section of the current charter. Since
this is coming to you on Monday evening prior to our Tuesday morning meeting, I
don’t think it’s feasible to have a vote tomorrow on submitting
this language to the TC Administrator for electronic ballot. My guess is that
all of us will need to have this reviewed by our management and possibly our
legal folks before a vote can be taken. We’ll discuss it tomorrow,
consider further edits and comments, and then see if we can schedule the vote
for next week based on feedback. Thanks for taking the time to review this and
be prepared for the discussion. Best
regards, --
Toby [1] Showing revisions from original draft
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 (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 (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 (3) Incorporate
Substantive Changes (4) Incorporate previous
Approved Errata and other corrections, clarifications and editorial changes
that are not Substantive Changes. [2] Clean Text 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 will
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;
(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 the relevant W3C
Recommendations produced by the W3C WS-ResourceAccess Working Group; (3) Incorporate
Substantive Changes 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, (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 (c)
further specification profiling, clarification, and
enhancing of security in DPWS identified through implementation experience
or interoperability testing; and, (4) Incorporate previous
Approved Errata and other corrections, clarifications and editorial changes
that are not Substantive Changes. 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 From: Mike Kaiser [mailto:mkaiser@us.ibm.com] Sent: Tuesday, April 07,
2009 9:23 AM To: Toby Nixon Cc:
ws-dd@lists.oasis-open.org Subject: Fw: [ws-dd]
Proposed WS-DD charter clarification Toby,
I
propose the following charter changes to your proposal below. The intent
is to accomplish the following: 1.
Remove statements about Scope. By definition
of the charter, only that which is defined as scope can be considered. No
need to repeat it here. 2.
Explicitly address an intent to focus on Security in
this release, 3.
Elimination of point 4 which is redundant.
"non substantive corrections, clarifications and editorial
changes" are all already covered under "Approve Errata" and
"Approved Errata" is already allowed by the paragraph at the
beginning addressing maintenance. Legend:
Red
= new text. (Red text)
Thanks,
Mike
IBM
Emerging Internet Software Standards Phone:
919-254-7605 T/L 444-7605 ----- Forwarded by Mike Kaiser/Raleigh/IBM on 04/02/2009 02:24 PM
-----
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 (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, (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 (3) Incorporate 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]