[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ws-dd] RE: "Related Work" section of proposed WS-DD charterfrom July 2008
Thanks, Mary. We’ll work on separating the statement into three. 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: Mary McRae [mailto:mary.mcrae@oasis-open.org]
I'm stumbling across this message before the one Toby
mentioned below, so I'm answering it ;-) There will need to be three separate submission packages -
one for each specification - that should list only those items related to that
particular specification. As far as the 'related work' section in the
submission this can be quite brief but should be pertinent to the specific
document in question. Regards, Mary Mary P McRae Director, Technical Committee Administration OASIS: Advancing open standards for the information society email: mary.mcrae@oasis-open.org web: www.oasis-open.org twitter: fiberartisan #oasis-open phone: 1.603.232.9090 On Apr 20, 2009, at 7:37 PM, Toby Nixon wrote:
Here are proposed edits to the “Related Work” section of the
original charter to adapt it for use as the “statement regarding the
relationship of this specification to similar work of other OASIS TCs or other
standards developing organizations” that must be submitted with the final
approval package. I do not believe the final approval package needs to have a
lengthy list of references with it, so I’ve deleted that entirely and don’t
show it here; accordingly, the endnote references are deleted from the second
paragraph. I also added a sentence about the status of the WS-RA specifications. 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). UPnP was submitted to
ISO/IEC JTC1 as a Publicly Available Specification and has been approved as an
international standard. Work on IGRS
Please consider this text. Does anything
else need to be added? Would this be a sufficient “Related Work” statement for
the final submission package? FYI, I’ve emailed the TC Administrator and asked for clarification
on whether this needs to be split into three separate statements for the three
specifications. If it does, then I’ll work on that as a separate drafting
effort.
-- 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 From: Toby
Nixon 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 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) [2]
WS-Discovery [3]
SOAP-over-UDP [4] Devices
Profile for Web Services [5] HTTP/1.1 [6] SOAP 1.2
(Second Edition), Part 1 [7]
SOAP-over-HTTP binding – SOAP 1.2 (Second Edition), Part 2, Section 7 [8]
WS-Addressing 1.0 – Core, SOAP Binding and Metadata [9] WSDL 1.1 [10] WSDL
Binding for SOAP 1.2 [11]
WS-Eventing (March 2006 version) [12]
WS-MetadataExchange (August 2006 version) [13]
WS-Policy1.5 [14]
WS-PolicyAttachment 1.5 [15]
WS-Security Core specification 1.1 [16]
WS-Transfer, W3C Member Submission, September 2006 [17] XML
Schema, Part 1 [18] XML
Schema, Part 2 [19]
WS-SecureConversation 1.3 [20] WS-Trust
1.3 [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]