[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: "Related Work" section of proposed WS-DD charter from July 2008
|
Section 3.4(e)
of the OASIS TC Process says that the submission package for final approval of
an OASIS standard must include “[a] statement regarding the relationship
of this specification to similar work of other OASIS TCs or other standards
developing organizations”. On our TC call on Tuesday, I suggested that we
might be able to base this statement on the “Related Work”
statement that was included in the proposed WS-DD charter. So, for your
reference, here [1] are the “Related Work” and
“References” sections from the proposed WS-DD charter as
distributed on the members@lists.oasis-open.org,
tc-announce@lists.oasis-open.org,
and oasis-charter-discuss@lists.oasis-open.org
email lists on July 7, 2008. I’m thinking now about how this can be
updated to suit our needs for the final submission package. --
Toby [1] http://lists.oasis-open.org/archives/tc-announce/200807/msg00006.html a. Related Work There is no known
standardization work that is currently in progress to apply Web services
specifications to resource-constrained devices or to dynamically discover
web services. There has been work on devices that communicate over IP based
on different protocols, such as UPnP (http://www.upnp.org)
and IGRS (http://www.igrs.org/en/index/index.asp).
UPnP was submitted to ISO/IEC JTC1 as a Publicly Available
Specification and has been approved as an international standard. IGRS
was recently approved as a new work item in ISO/IEC JTC1 SC25. However,
neither of these protocols is based on Web services specifications and do
not incorporate the richness, interoperability, security, scalability, and
composability of the full Web services protocol suite. 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. Since WS-Discovery,
SOAP-over-UDP, and DPWS specifications are based on protocols in the Web
services architecture, and must work well with other specifications
within that architecture, they must be composable with the other specifications
in the Web services architecture such as, but not limited to, HTTP 1.1
[5], SOAP 1.2 [6], SOAP-over-HTTP binding [7], WS-Addressing [8], WSDL 1.1
[9], WSDL Binding for SOAP 1.2 [10], WS-Eventing [11], WS-MetadataExchange
[12], WS-Policy [13], WS-PolicyAttachment [14], WS-Security [15],
WS-Transfer [16], XML Schema [17] [18], WS-SecureConversation [19],
and WS-Trust [20], AES/TLS [21], SHA1 [22], TLS [23], and X.509 v3
[24]. Where appropriate, the
WS-DD TC will foster collaborative relationships and liaisons with other
activities including other OASIS Technical Committees and committees
of other organizations interested in the work of the TC. Responsibilities
for such relationships and liaison will be defined by the TC at that
time. ---- References [1] User Datagram
Protocol (UDP) http://www.ietf.org/rfc/rfc768.txt [2] WS-Discovery http://schemas.xmlsoap.org/ws/2005/04/discovery [3] SOAP-over-UDP http://schemas.xmlsoap.org/ws/2004/09/soap-over-udp [4] Devices Profile for
Web Services http://schemas.xmlsoap.org/ws/2006/02/devprof [5] HTTP/1.1 http://www.ietf.org/rfc/rfc2616.txt [6] SOAP 1.2 (Second
Edition), Part 1 http://www.w3.org/TR/2007/REC-soap12-part1-20070427/ [7] SOAP-over-HTTP
binding – SOAP 1.2 (Second Edition), Part 2, Section 7 http://www.w3.org/TR/2007/REC-soap12-part2-20070427/#soapinhttp [8] WS-Addressing 1.0
– Core, SOAP Binding and Metadata http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/ http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509/ http://www.w3.org/TR/2007/REC-ws-addr-metadata-20070904/ [9] WSDL 1.1 http://www.w3.org/TR/2001/NOTE-wsdl-20010315 [10] WSDL Binding for
SOAP 1.2 http://www.w3.org/Submission/wsdl11soap12/ [11] WS-Eventing (March
2006 version) http://schemas.xmlsoap.org/ws/2004/08/eventing/ [12] WS-MetadataExchange
(August 2006 version) http://schemas.xmlsoap.org/ws/2004/09/mex/ [13] WS-Policy1.5 http://www.w3.org/TR/2007/REC-ws-policy-20070904/ [14] WS-PolicyAttachment
1.5 http://www.w3.org/TR/2007/REC-ws-policy-attach-20070904/ [15] WS-Security Core
specification 1.1 http://www.oasis-open.org/committees/download.php/16790/wss-v1.1-spec-os-SOAPMessageSecurity.pdf [16] WS-Transfer, W3C
Member Submission, September 2006 http://schemas.xmlsoap.org/ws/2004/09/transfer/ [17] XML Schema, Part 1 http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/ [18] XML Schema, Part 2 http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/ [19]
WS-SecureConversation 1.3 http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512 [20] WS-Trust 1.3 http://docs.oasis-open.org/ws-sx/ws-trust/200512 [21] AES/TLS, June 2002
version P. Chown, "Advanced
Encryption Standard (AES) Ciphersuites for Transport Layer Security
(TLS)," June 2004, http://www.ietf.org/rfc/rfc3268.txt. [22] SHA1, April 1995
version "Secure Hash
Standard," April 1995, http://www.itl.nist.gov/fipspubs/fip180-1.htm. [23] TLS version 1.0 T. Dierks, et al,
"The TLS Protocol, Version 1.0", January 1999. (See http://www.ietf.org/rfc/rfc2246.txt. [24] X.509.v3 ITU-T X.509.v3
Information technology - Open Systems Interconnection – The Directory:
Public-key and attribute certificate frameworks (ISO/IEC/ITU 9594-8). 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]