[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Devices Profile for Web Services (DPWS) V1.1 Submitted for OASIS Standard Approval Ballot
The OASIS Web Services Discovery and Web Services Devices Profile (WS-DD) Technical Committee has submitted the following specification, which is an approved Committee Specification, to be considered as an OASIS Standard:
Devices Profile for Web Services (DPWS) Version 1.1
The text of the TC submission is appended.
You now have until 15 June to familiarize yourself with the submission and provide input to your organization's voting representative.
On 16 June, a Call For Vote will be issued to all Voting Representatives of OASIS member organizations. They will have until the last day of June, 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 firstname.lastname@example.org.
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.
WS-DD OASIS Submission of Devices Profile for Web Services Version 1.1
(a) 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 schema for this specification can be located at:
(b) The editable version of all files that are part of the Committee Specification;
(c) 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;
The OASIS WS-DD TC certifies that all schema and XML instances included in the DPWS specification, whether by inclusion or reference, including fragments of such, are well formed, and that all expressions are valid.
(d) A clear English-language summary of the specification;
This profile defines a minimal set of implementation constraints to enable secure Web service messaging, discovery, description, and eventing on resource-constrained endpoints.
(e) A statement regarding the relationship of this specification to similar work of other OASIS TCs or other standards developing organizations;
There is no other known standardization work that exists or is currently in progress to apply Web services specifications to resource-constrained devices. The Mobile Web Initiative of W3C (http://www.w3.org/Mobile/) is focused on web browsing from mobile devices as opposed to controlling mobile devices using Web services or allowing mobile devices to control others using Web services. The OASIS Remote Control XML TC (http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=remote-control) is focused on development of a small set of specific operations for remote control of devices which are expressed in XML but without the full richness of the entire Web services protocol suite. There has been work on devices that communicate over IP based on different protocols, such as UPnP (http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0.pdf) and IGRS (http://www.igrs.org); UPnP was submitted to ISO/IEC JTC1 as a Publicly Available Specification and has been approved as an international standard (ISO/IEC 29341), and work on IGRS is in progress in ISO/IEC JTC1 SC25 (expected to become ISO/IEC 14534-4). However, neither of these protocols is as broadly-based on Web services specifications as DPWS; they do not incorporate the richness, interoperability, security, scalability, and composability of the full Web services protocol suite. DPWS is based on protocols in the Web services architecture, works well with other specifications within that architecture, and composes with other specifications in the Web services architecture such as, but not limited to, IP, TCP, HTTP, SOAP, XML, XML Schema, WSDL, WS-Addressing, WS-Policy, WS-PolicyAttachment, WS-Discovery, SOAP-over-UDP, WS-Transfer, WS-MetadataExchange, WS-Eventing, WS-Security, WS-SecureConversation, WS-Trust, AES/TLS, SHA1, TLS, and X.509. WS-Eventing, WS-MetadataExchange, and WS-Transfer have been submitted to W3C for standardization through the WS-ResourceAccess Working Group; the OASIS WS-DD TC anticipates updating DPWS in the future to reference the standardized versions of these specifications.
(f) Certification by at least three OASIS member organizations that they are successfully using the specification;
University of Rostock:
(g) 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 resolution;
Public Review began 2 February 2009 and ended 3 April 2009.
Public Review Comments:
Public Review Issues and Resolutions:
(h) 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 ballot;
Opened Wednesday, 6 May 2009 @ 15:00 ET
Closed Wednesday, 13 May 2009 @ 23:45 ET
Result: 15 Yes, 0 No, 0 Abstain, 0 Not Voting
Link to Ballot: http://www.oasis-open.org/committees/ballot.php?id=1683
(i) 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;
There were no earlier attempts to standardize substantially the same specification.
(j) A pointer to the publicly visible comments archive for the originating TC;
Public comment list archive: http://lists.oasis-open.org/archives/ws-dd-comment
Committee email list archive: http://lists.oasis-open.org/archives/ws-dd
(k) 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 exist.
The Co-Chairs certify that no minority reports exist.