- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 19 Jan 2010 22:17:22 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv14255
Modified Files:
wseventing.html wseventing.xml
Added Files:
wsevd.html wsevd.xml
Log Message:
8068
--- NEW FILE: wsevd.html ---
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml" lang="en"><head><title>Web Services Event Descriptions (WS-EventDescriptions)</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
div.issue,
div.note,
div.notice { margin-left: 2em; }
ol.enumar { list-style-type: decimal; }
ol.enumla { list-style-type: lower-alpha; }
ol.enumlr { list-style-type: lower-roman; }
ol.enumua { list-style-type: upper-alpha; }
ol.enumur { list-style-type: upper-roman; }
div.exampleInner pre { margin-left: 1em;
margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
border-bottom-width: 4px;
border-bottom-style: double;
border-bottom-color: #d3d3d3;
padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
margin: 4px}
</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"/></head><body><div class="head">
<h1><a name="title" id="title"/>Web Services Event Descriptions (WS-EventDescriptions)</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"/>Editor's Draft $Date: 2010/01/19 22:17:20 $</h2><dl><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/ws-event-descriptions">http://www.w3.org/TR/ws-event-descriptions
</a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2009/WD-ws-event-descriptions-20090317">http://www.w3.org/TR/2009/WD-ws-event-descriptions-20090317</a></dd><dt>Editors:</dt><dd>Doug Davis, IBM</dd><dd>Ashok Malhotra, Oracle</dd><dd>Katy Warr, IBM</dd><dd>Wu Chou, Avaya</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2009 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="htt://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
<h2><a name="abstract" id="abstract"/>Abstract</h2><p>
This specification describes a mechanism by which an endpoint can
advertise the structure and contents of the events it might generate.
</p></div><div>
<h2><a name="status" id="status"/>Status of this Document</h2><p><strong>This document is an editors' copy that has
no official standing.</strong></p></div><div class="toc">
<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#composable">Composable Architecture</a><br/>
2 <a href="#intro">Introduction</a><br/>
2.1 <a href="#reqs">Requirements</a><br/>
3 <a href="#notterms">Notations and Terminology</a><br/>
3.1 <a href="#conventions">Notational Conventions</a><br/>
3.2 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br/>
3.3 <a href="#namespaces">XML Namespaces</a><br/>
3.4 <a href="#terms">Terminology</a><br/>
3.5 <a href="#compliance">Compliance</a><br/>
4 <a href="#Advertising">Advertising Event Information</a><br/>
4.1 <a href="#ETypes">Event Types & Event Descriptions</a><br/>
4.1.1 <a href="#iddiv3_1_534">Retrieving Event Descriptions</a><br/>
4.1.2 <a href="#iddiv3_1_555">Bindings for Event Descriptions</a><br/>
5 <a href="#acks">Acknowledgements</a><br/>
6 <a href="#refs">References</a><br/>
6.1 <a href="#iddiv2_1_570">Normative References</a><br/>
6.2 <a href="#iddiv2_1_600">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#EVDXSD">XML Schema for EventDescriptions</a><br/>
B <a href="#changelog">Change Log</a><br/>
</p></div><hr/><div class="body"><div class="div1">
<h2><a name="composable" id="composable"/>1 Composable Architecture</h2><p>
By using the XML, SOAP <a href="#SOAP11">[SOAP11]</a>,
<a href="#SOAP121">[SOAP12]</a>, and WSDL <a href="#WSDL11">[WSDL11]</a>
extensibility models, the Web service
specifications (WS-*) are designed to be composed with each other
to provide a rich set of tools to provide security in the Web
services environment.
</p></div><div class="div1">
<h2><a name="intro" id="intro"/>2 Introduction</h2><p>
This specification describes a mechanism by which an endpoint can
advertise the structure and contents of the events it might generate.
</p><div class="div2">
<h3><a name="reqs" id="reqs"/>2.1 Requirements</h3><p>
This specification intends to meet the following requirements:
</p><ul><li><p>
Define a mechanism to describe the structure and contents of
events.
</p></li><li><p>
Leverage WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a> to allow an
endpoint to advertise events that might be generated.
</p></li></ul></div></div><div class="div1">
<h2><a name="notterms" id="notterms"/>3 Notations and Terminology</h2><p>
This section specifies the notations, namespaces, and
terminology used in this specification.
</p><div class="div2">
<h3><a name="conventions" id="conventions"/>3.1 Notational Conventions</h3><p>
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
RFC 2119 <a href="#RFC2119">[RFC 2119]</a>.
</p><p>
This specification uses the following syntax to define
normative outlines for messages:
</p><ul><li><p>
The syntax appears as an XML instance, but values in
italics indicate data types instead of values.
</p></li><li><p>
Characters are appended to elements and attributes to
indicate cardinality:
</p><ul><li><p>"?" (0 or 1)</p></li><li><p>"*" (0 or more)</p></li><li><p>"+" (1 or more)</p></li></ul></li><li><p>
The character "|" is used to indicate a choice between
alternatives.
</p></li><li><p>
The characters "(" and ")" are used to indicate that contained items
are to be treated as a group with respect to cardinality or choice.
</p></li><li><p>
The characters "[" and "]" are used to call out references and
property names.
</p></li><li><p>
Ellipsis (i.e. "...") indicate a point of extensibility.
</p></li><li><p>
XML namespace prefixes (see <a href="#Table3">Table 3-1</a>)
are used to indicate the namespace of the element being
defined.
</p></li></ul><p>
This specification can be used in terms of XML Information Set (Infoset)
<a href="#XMLInfoset">[XML Infoset]</a>, even though the specification uses XML 1.0
terminology. Valid Infoset for this specification is the one
serializable in XML 1.0, hence the use of XML 1.0.
</p></div><div class="div2">
<h3><a name="extensions" id="extensions"/>3.2 Considerations on the Use of Extensibility Points</h3><p>
The elements defined in this specification MAY be extended at the
points indicated by their outlines and schema. Implementations MAY
add child elements and/or attributes at the indicated extension
points but MUST NOT contradict the semantics of the parent and/or
owner, respectively.
</p><p>
Extension elements and attributes MUST NOT use the Web Services
Event Descriptions namespace URI.
</p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"/>3.3 XML Namespaces</h3><p>
The XML namespace URI that MUST be used by implementations of
this specification is:
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-evd">http://www.w3.org/2009/09/ws-evd</a></pre></div></div><p><a href="#Table3">Table 3-1</a> lists XML namespaces that are used in this
specification. The choice of any namespace prefix is arbitrary
and not semantically significant.
</p><a name="Table3" id="Table3"/><table border="1"><caption>Table 3-1: Prefixes and XML namespaces used in this specification </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespace </th><th align="left"> Specification(s) </th></tr><tr><td>s</td><td>(Either SOAP 1.1 or 1.2)</td><td>(Either SOAP 1.1 or 1.2)</td></tr><tr><td>s11</td><td><a href="http://schemas.xmlsoap.org/soap/envelope/">
http://schemas.xmlsoap.org/soap/envelope/
</a></td><td>SOAP 1.1 <a href="#SOAP11">[SOAP11]</a></td></tr><tr><td>s12</td><td><a href="http://www.w3.org/2003/05/soap-envelope">
http://www.w3.org/2003/05/soap-envelope
</a></td><td>SOAP 1.2 <a href="#SOAP121">[SOAP12]</a></td></tr><tr><td>wsa</td><td><a href="http://www.w3.org/2005/08/addressing">
http://www.w3.org/2005/08/addressing
</a></td><td>WS-Addressing <a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td>wsevd</td><td><a href="http://www.w3.org/2009/09/ws-evd">
http://www.w3.org/2009/09/ws-evd
</a></td><td>This specification</td></tr><tr><td>xs</td><td><a href="http://www.w3.org/2001/XMLSchema">
http://www.w3.org/2001/XMLSchema
</a></td><td>
XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>, <a href="#XMLSchema2">[XMLSchema - Part 2]</a></td></tr></tbody></table><p>
The working group intends to update the value of the Web Services
Event Descriptions namespace URI each time a new version of this document
is published until such time that the document reaches Candidate
Recommendation status. Once it has reached Candidate Recommendation
status, the working group intends to maintain the value of the
Web Services Event Descriptions namespace URI that was assigned in the
Candidate Recommendation unless significant changes are made that
impact the implementation or break post-CR implementations of the
specification. Also see
<a href="http://www.w3.org/2001/tag/doc/namespaceState.html">
http://www.w3.org/2001/tag/doc/namespaceState.html
</a> and
<a href="http://www.w3.org/2005/07/13-nsuri">
http://www.w3.org/2005/07/13-nsuri
</a>.
</p></div><div class="div2">
<h3><a name="terms" id="terms"/>3.4 Terminology</h3><dl><dt class="label"> Notification </dt><dd><p>
A message sent to indicate that an event, or events, have occurred.
</p></dd></dl></div><div class="div2">
<h3><a name="compliance" id="compliance"/>3.5 Compliance</h3><p>
An implementation is not compliant with this specification if it fails to
satisfy one or more of the MUST or REQUIRED level requirements defined
herein. A SOAP Node MUST NOT use the XML namespace identifier for this
specification (listed in <a href="#namespaces"><b>3.3 XML Namespaces</b></a>) within SOAP
Envelopes unless it is compliant with this specification.
</p><p>
Normative text within this specification takes precedence over the XML
Schema and WSDL descriptions, which in turn take precedence over
outlines, which in turn take precedence over examples.
</p><p>
Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
</p></div></div><div class="div1">
<h2><a name="Advertising" id="Advertising"/>4 Advertising Event Information</h2><p>
There are many use cases in which it is necessary for an endpoint
to advertise the structure and contents of the events that it might
generate. For example, a subscriber
might wish to know the shape of the events that are generated in
order to properly formulate a filter to limit the number of
notifications that are transmitted, or to ensure it can successfully
process the type of events that are transmitted.
</p><p>
There are many ways in which an endpoint could describe and
advertise the structure of the events for which it will issue
notifications. To provide a basic level of interoperability, this
specification defines the following mechanism, in
<a href="#ETypes"><b>4.1 Event Types & Event Descriptions</b></a>, for describing and
advertising event information.
</p><p>
This specification only defines a mechanism by which events can be
described and advertised. How these events, and the properties of
these events that are described within an Event Descriptions document,
are serialized for transmission is out of scope
of this specification; but are expected to be fully described in
any specification that uses this one.
</p><div class="div2">
<h3><a name="ETypes" id="ETypes"/>4.1 Event Types & Event Descriptions</h3><p>
A key concept in the description and advertisement of event information
is the "Event Type". An Event Type is a description of the syntactic
structure and value space of the set of events that share that type.
Event Types are independent of the pub/sub protocol used and the format
of the notifications used to transmit those events.
</p><p>
Event Types are described within an EventDescriptions element where
they contain a complete description of an event. A key aspect of this
description is the associated XML Schema Global Element Declaration
(GED) for each event.
EventDescriptions element has the following form:
</p><div class="exampleOuter"><div class="exampleInner"><pre><wsevd:EventDescriptions targetNamespace="<em>xs:anyURI</em>" ...>
<wsevd:types>
<xs:schema ...>
...
</xs:schema>
<em>xs:any</em>*
</wsevd:types>
<wsevd:eventType name="<em>xs:NCName</em>" element="<em>xs:QName</em>" actionURI="<em>xs:anyURI</em>"? ...>
<em>xs:any</em>*
</wsevd:eventType> +
<em>xs:any</em>*
</wsevd:EventDescriptions></pre></div></div><p>
The XML Schema for the EventDescriptions element can be found in
<a href="#EVDXSD"><b>A XML Schema for EventDescriptions</b></a>. The following describes additional, normative
constraints on the outlined listed above:
</p><dl><dt class="label"> /wsevd:EventDescriptions </dt><dd><p>
This element contains the declarations of all the Event Types that
apply to a given context.
</p></dd><dt class="label"> /wsevd:EventDescriptions@targetNamespace </dt><dd><p>
This attribute defines the namespace affiliation of the Event Types
declared within the EventDescriptions element. Its value MUST be an
absolute IRI <a href="#RFC3987">[RFC 3987]</a>. It SHOULD be dereferenceable.
</p></dd><dt class="label"> /wsevd:EventDescriptions/wsevd:types </dt><dd><p>
This element encloses data type definitions that are relevant to
the declared Event Types.
</p></dd><dt class="label"> /wsevd:EventDescriptions/wsevd:types/xs:schema </dt><dd><p>
As described earlier, an Event Type is defined by a Global Element
Declaration (GED) in XML Schema. This element contains collections
of imported and inlined schema components that describe the GEDs
that are used to define Event Types.
</p></dd><dt class="label"> /wsevd:EventDescriptions/wsevd:eventType </dt><dd><p>
This element describes a specific Event Type.
</p></dd><dt class="label"> /wsevd:EventDescriptions/wsevd:eventType/@name </dt><dd><p>
This attribute provides a name for this Event Type which MUST be
unique amongst
all the Event Types defined by the enclosing wsevd:EventDescriptions
element. In conjunction with a Prefix that is associated with the
value of /wsevd:EventDescriptions/@targetNamespace namespace URI, the
value of this attribute MAY be used as the LocalPart of a QName
that identifies this Event Type outside the context of the
enclosing wsevd:EventDescriptions element.
</p></dd><dt class="label"> /wsevd:EventDescriptions/wsevd:eventType/@element </dt><dd><p>
This attribute refers to a GED defined or imported in the
/wsevd:EventDescriptions/wsevd:types element. The referenced GED
serves as the definition of this Event Type.
</p></dd><dt class="label"> /wsevd:EventDescriptions/wsevd:eventType/@actionURI </dt><dd><p>
This OPTIONAL attribute provides a value for the 'action'
property which, depending upon the format of the
notification used to transmit the Event, serve as a potential aid
to identifying the semantics implied by the message. When not
present the implied value of this attribute is the concatenation
of the wsevd:EventDescriptions' targetNamespace attribute and
the wsevd:eventType name attribute separated by the '/' character.
</p></dd></dl><p>
The following is an example of an EventDescriptions element that could
serve as a description of the Event Type used in
<a href="#EVDExample">Example 4-2</a>.
</p><div class="exampleOuter">
<div class="exampleHeader"><a name="EVDSample" id="EVDSample"/>Example 4-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wsevd:EventDescriptions
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:wsevd="http://www.w3.org/2009/09/ws-evd"
(04) xmlns:ow="http://www.example.org/oceanwatch">
(05) <wsevd:types>
(06) <xs:schema targetNamespace="http://www.example.org/oceanwatch">
(07) <xs:include schemaLocation="http://www.example.org/schemas/oceanwatch.xsd"/>
(08) <xs:element name="WindReport" type="ow:WindReportType"/>
(09) </xs:schema>
(10) </wsevd:types>
(11)
(12) <wsevd:eventType name="WindReportEvent"
(13) element="ow:WindReport"
(14) actionURI="http://www.example.org/oceanwatch/2003/WindReport"/>
(15) </wsevd:EventDescriptions></pre></div></div><p>
Lines (12-14) describe an Event Type with a QName of
"{http://www.example.org/oceanwatch/notifications}:WindReportEvent". The
GED for this Event Type is defined on line (08) as being of type
"{http://www.example.org/oceanwatch}:WindReportType".
</p><p>
The sample EventDescriptions in <a href="#EVDSample">Example 4-1</a> might describe
the following notification:
</p><div class="exampleOuter">
<div class="exampleHeader"><a name="EVDExample" id="EVDExample"/>Example 4-2: Hypothetical Notification</div><div class="exampleInner"><pre>(01) <s12:Envelope xmlns:s12="http://www.w3.org/2003/05/soap-envelop
e"
(02) xmlns:wsa="http://www.w3.org/2005/08/addressing"
(03) xmlns:ow="http://www.example.org/oceanwatch">
(04) <s12:Header>
(05) <wsa:Action>
(06) http://www.example.com/oceanwatch/2003/WindReport
(07) </wsa:Action>
(08) ...
(09) </s12:Header>
(10) <s12:Body>
(11) <ow:WindReport>
(12) <ow:Date>030701</ow:Date>
(13) <ow:Time>0041</ow:Time>
(14) <ow:Speed>65</ow:Speed>
(15) <ow:Location>BRADENTON BEACH</ow:Location>
(16) <ow:County>MANATEE</ow:County>
(17) <ow:State>FL</ow:State>
(18) <ow:Lat>27.46</ow:Lat>
(19) <ow:Long>82.70</ow:Long>
(20) <ow:Comments xml:lang="en-US" >
(21) WINDS 55 WITH GUSTS TO 65. ROOF TORN OFF BOAT HOUSE. REPORTED
(22) BY STORM SPOTTER. (TBW)
(23) </ow:Comments>
(24) </ow:WindReport>
(25) </s12:Body>
(26) </s12:Envelope></pre></div></div><div class="div3">
<h4><a name="iddiv3_1_534" id="iddiv3_1_534"/>4.1.1 Retrieving Event Descriptions</h4><p>
Although there are many ways in which an endpoint can make its
EventDescriptions available, this specification RECOMMENDS the use of
the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
This specification defines the following IRI to serve as the Dialect
IRI for the wsevd:EventDescriptions element.
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-evd/EventDescriptions">http://www.w3.org/2009/09/ws-evd/EventDescriptions</a></pre></div></div><p>
The value of the @Identifier attribute for this Metadata Section MUST
be equal to the value of its wsevd:EventDescriptions/@targetNamespace.
</p></div><div class="div3">
<h4><a name="iddiv3_1_555" id="iddiv3_1_555"/>4.1.2 Bindings for Event Descriptions</h4><p>
Any specification of a publish-subscribe system that uses
Event Descriptions to advertise the events that are generated
MUST clearly define how those events are serialized when they
are transmitted to the receiver of notification messages.
</p></div></div></div><div class="div1">
<h2><a name="acks" id="acks"/>5 Acknowledgements</h2><p>
This specification has been developed as a result of joint
work with many individuals and teams, including:
Ashok Malhotra (Oracle Corp.),
Asir Vedamuthu (Microsoft Corp.),
Bob Freund (Hitachi, Ltd.),
Doug Davis (IBM),
Fred Maciel (Hitachi, Ltd.),
Geoff Bullen (Microsoft Corp.),
Gilbert Pilz (Oracle Corp.),
Greg Carpenter (Microsoft Corp.),
Jeff Mischkinsky (Oracle Corp.),
Katy Warr (IBM),
Li Li (Avaya Communications),
Mark Little (Red Hat),
Prasad Yendluri (Software AG),
Ram Jeyaraman (Microsoft Corp.),
Sreedhara Narayanaswamy (CA),
Sumeet Vij (Software AG),
Vikas Varma (Software AG),
Wu Chou (Avaya Communications),
Yves Lafon (W3C).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>6 References</h2><div class="div2">
<h3><a name="iddiv2_1_570" id="iddiv2_1_570"/>6.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
Internet Engineering Task Force, March 1997.
Available at <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>.</dd><dt class="label"><a name="RFC3987" id="RFC3987"/>RFC 3987</dt><dd><a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>
Internationalized Resource Identifiers (IRIs)
</cite></a>
, M. Duerst and M. Suignard, Authors.
Internet Engineering Task Force, January 2005.
Available at <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>.</dd></dl></div><div class="div2">
<h3><a name="iddiv2_1_600" id="iddiv2_1_600"/>6.2 Informative References</h3><dl><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
W3C Note, "Simple Object Access Protocol (SOAP) 1.1"
</cite></a>
, D. Box, et al, Editors.
World Wide Web Consortium (W3C), 8 May 2000.
Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP121" id="SOAP121"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
</cite></a>
, M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
Editors.
World Wide Web Consortium (W3C), 27 April 2007.
Available at <a href="http://www.w3.org/TR/soap12-part1/">http://www.w3.org/TR/soap12-part1/</a>.</dd><dt class="label"><a name="AddrCore" id="AddrCore"/>WS-Addressing</dt><dd><a href="http://www.w3.org/TR/ws-addr-core"><cite>
W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
</cite></a>
, M. Gudgin, M. Hadley, T. Rogers, Editors.
World Wide Web Consortium (W3C), 9 May 2006.
Available at <a href="http://www.w3.org/TR/ws-addr-core">http://www.w3.org/TR/ws-addr-core</a>.</dd><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
W3C Working Group Draft, "Web Services Metadata Exchange
(WS-MetadataExchange) 1.1"
</cite></a>
, D. Davis, et al., Editors.
World Wide Web Consortium (W3C), 15 September 2009.
Available at <a href="http://www.w3.org/TR/ws-metadata-exchange">http://www.w3.org/TR/ws-metadata-exchange</a>.</dd><dt class="label"><a name="WSDL11" id="WSDL11"/>WSDL11</dt><dd><a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
W3C Note, "Web Services Description Language (WSDL) 1.1"
</cite></a>
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/xml-infoset"><cite>
W3C Recommendation, "XML Information Set (Second Edition)"
</cite></a>
, J. Cowan, R. Tobin, Editors.
World Wide Web Consortium (W3C), 4 February 2004.
Available at <a href="http://www.w3.org/TR/xml-infoset">http://www.w3.org/TR/xml-infoset</a>.</dd><dt class="label"><a name="XMLSchema1" id="XMLSchema1"/>XMLSchema - Part 1</dt><dd><a href="http://www.w3.org/TR/xmlschema-1/"><cite>
W3C Recommendation, "XML Schema Part 1: Structures (Second Edition)"
</cite></a>
, H. Thompson, et al., Editors.
World Wide Web Consortium (W3C), 28 October 2004.
Available at <a href="http://www.w3.org/TR/xmlschema-1/">http://www.w3.org/TR/xmlschema-1/</a>.</dd><dt class="label"><a name="XMLSchema2" id="XMLSchema2"/>XMLSchema - Part 2</dt><dd><a href="http://www.w3.org/TR/xmlschema-2/"><cite>
W3C Recommendation, "XML Schema Part 2: Datatypes (Second Edition)"
</cite></a>
, P. Biron, A. Malhotra, Editors.
World Wide Web Consortium (W3C), 28 October 2004.
Available at <a href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a>.</dd></dl></div></div></div><div class="back"><div class="div1">
<h2><a name="EVDXSD" id="EVDXSD"/>A XML Schema for EventDescriptions</h2><p>
A normative copy of the XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,
<a href="#XMLSchema2">[XMLSchema - Part 2]</a> description for the EventDescriptions
element can be retrieved from the following address:
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-evd/EventDescriptions.xsd">http://www.w3.org/2009/09/ws-evd/EventDescriptions.xsd</a></pre></div></div><p>
A non-normative copy of the XML schema is listed below for
convenience.
</p><div class="exampleOuter"><div class="exampleInner"><pre><xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema'
targetNamespace='http://www.w3.org/2009/09/ws-evd'
elementFormDefault='qualified' attributeFormDefault='unqualified'>
<xs:element name='EventDescriptions'>
<xs:complexType>
<xs:sequence>
<xs:element name='types'>
<xs:annotation>
<xs:documentation>Data type definitions that are relevant to described notifications.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
</xs:sequence>
<xs:anyAttribute namespace='##other' processContents='lax'/>
</xs:complexType>
</xs:element>
<xs:element name='eventType' maxOccurs='unbounded'>
<xs:complexType>
<xs:sequence>
<xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
</xs:sequence>
<xs:attribute name='name' type='xs:NCName' use='required'/>
<xs:attribute name='element' type='xs:QName' use='required'/>
<xs:attribute name='actionURI' type='xs:anyURI' use='optional'/>
<xs:anyAttribute namespace='##other' processContents='lax'/>
</xs:complexType>
</xs:element>
<xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
</xs:sequence>
<xs:attribute name='targetNamespace' type='xs:anyURI' use='required'/>
<xs:anyAttribute namespace='##other' processContents='lax'/>
</xs:complexType>
</xs:element>
</xs:schema></pre></div></div></div><div class="div1">
<h2><a name="changelog" id="changelog"/>B Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8068">8068</a></td></tr></tbody></table></div></div></body></html>
--- NEW FILE: wsevd.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type='text/xsl' href='xmlspec.xsl'?>
<!DOCTYPE spec PUBLIC "-//W3C//DTD Specification V2.1//EN" "xmlspec.dtd" [
<!ENTITY % entities SYSTEM "entitieswd.dtd" >
%entities;
<!ENTITY status "&wsevd.status;" >
<!ENTITY short-status "&wsevd.short-status;" >
]>
<spec w3c-doctype="&wsevd.w3c-doctype;" role="&wsevd.role;">
<header>
<title>&wsevd.name;</title>
<w3c-designation>&wsevd.w3c-designation;</w3c-designation>
<w3c-doctype>"&wsevd.w3c-doctype;</w3c-doctype>
<pubdate>
<day>&wsevd.day;</day>
<month>&wsevd.month;</month>
<year>&wsevd.year;</year>
</pubdate>
<publoc>
<loc xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple"
xlink:show="replace" xlink:actuate="onRequest"
href="&wsevd.dated;">&wsevd.dated;
</loc>
</publoc>
<latestloc>
<loc xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple"
xlink:show="replace" xlink:actuate="onRequest"
href="http://www.w3.org/TR/&wsevd.shortname;">http://www.w3.org/TR/&wsevd.shortname;
</loc>
</latestloc>
<prevlocs>
<loc xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple"
xlink:show="replace" xlink:actuate="onRequest"
href="&prev.wsevd.dated;">&prev.wsevd.dated;
</loc>
</prevlocs>
<authlist>
<author>
<name>Doug Davis</name>
<affiliation>IBM</affiliation>
</author>
<author>
<name>Ashok Malhotra</name>
<affiliation>Oracle</affiliation>
</author>
<author>
<name>Katy Warr</name>
<affiliation>IBM</affiliation>
</author>
<author>
<name>Wu Chou</name>
<affiliation>Avaya</affiliation>
</author>
</authlist>
<status id='Status'>
<p>This is the First Public Working Draft.</p>
<p>
Publication as a Working Draft does not imply endorsement by the
W3C Membership. This is a draft document and can be updated, replaced
or obsoleted by other documents at any time. It is inappropriate to
cite this document as other than work in progress.
</p>
</status>
<abstract>
<p>
This specification describes a mechanism by which an endpoint can
advertise the structure and contents of the events it might generate.
</p>
</abstract>
<langusage>
<language id="en">English</language>
</langusage>
<revisiondesc>
<p>Last Modified: $Date: 2010/01/19 22:17:20 $</p>
</revisiondesc>
</header>
<body>
<div1 id="composable">
<head>Composable Architecture</head>
<p>
By using the XML, SOAP <bibref ref="SOAP11"/>,
<bibref ref="SOAP121"/>, and WSDL <bibref ref="WSDL11"/>
extensibility models, the Web service
specifications (WS-*) are designed to be composed with each other
to provide a rich set of tools to provide security in the Web
services environment.
</p>
</div1>
<div1 id="intro">
<head>Introduction</head>
<p>
This specification describes a mechanism by which an endpoint can
advertise the structure and contents of the events it might generate.
</p>
<div2 id="reqs">
<head>Requirements</head>
<p>
This specification intends to meet the following requirements:
</p>
<ulist>
<item>
<p>
Define a mechanism to describe the structure and contents of
events.
</p>
</item>
<item>
<p>
Leverage WS-MetadataExchange <bibref ref="MEX"/> to allow an
endpoint to advertise events that might be generated.
</p>
</item>
</ulist>
</div2>
</div1>
<div1 id="notterms">
<head>Notations and Terminology</head>
<p>
This section specifies the notations, namespaces, and
terminology used in this specification.
</p>
<div2 id="conventions">
<head>Notational Conventions</head>
<p>
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
RFC 2119 <bibref ref="RFC2119"/>.
</p>
<p>
This specification uses the following syntax to define
normative outlines for messages:
</p>
<ulist>
<item>
<p>
The syntax appears as an XML instance, but values in
italics indicate data types instead of values.
</p>
</item>
<item>
<p>
Characters are appended to elements and attributes to
indicate cardinality:
</p>
<ulist>
<item>
<p>"?" (0 or 1)</p>
</item>
<item>
<p>"*" (0 or more)</p>
</item>
<item>
<p>"+" (1 or more)</p>
</item>
</ulist>
</item>
<item>
<p>
The character "|" is used to indicate a choice between
alternatives.
</p>
</item>
<item>
<p>
The characters "(" and ")" are used to indicate that contained items
are to be treated as a group with respect to cardinality or choice.
</p>
</item>
<item>
<p>
The characters "[" and "]" are used to call out references and
property names.
</p>
</item>
<item>
<p>
Ellipsis (i.e. "...") indicate a point of extensibility.
</p>
</item>
<item>
<p>
XML namespace prefixes (see <specref ref="Table3"/>)
are used to indicate the namespace of the element being
defined.
</p>
</item>
</ulist>
<p>
This specification can be used in terms of XML Information Set (Infoset)
<bibref ref="XMLInfoset"/>, even though the specification uses XML 1.0
terminology. Valid Infoset for this specification is the one
serializable in XML 1.0, hence the use of XML 1.0.
</p>
</div2>
<div2 id="extensions">
<head>Considerations on the Use of Extensibility Points</head>
<p>
The elements defined in this specification MAY be extended at the
points indicated by their outlines and schema. Implementations MAY
add child elements and/or attributes at the indicated extension
points but MUST NOT contradict the semantics of the parent and/or
owner, respectively.
</p>
<p>
Extension elements and attributes MUST NOT use the Web Services
Event Descriptions namespace URI.
</p>
</div2>
<div2 id="namespaces">
<head>XML Namespaces</head>
<p>
The XML namespace URI that MUST be used by implementations of
this specification is:
</p>
<example>
<eg><loc href="http://www.w3.org/&wsevd.nsprefix;/ws-evd">http://www.w3.org/&wsevd.nsprefix;/ws-evd</loc></eg>
</example>
<p>
<specref ref="Table3"/> lists XML namespaces that are used in this
specification. The choice of any namespace prefix is arbitrary
and not semantically significant.
</p>
<table id="Table3" border="1">
<caption> Prefixes and XML namespaces used in this specification </caption>
<tbody>
<tr>
<th align="left"> Prefix </th>
<th align="left"> XML Namespace </th>
<th align="left"> Specification(s) </th>
</tr>
<tr>
<td>s</td>
<td>(Either SOAP 1.1 or 1.2)</td>
<td>(Either SOAP 1.1 or 1.2)</td>
</tr>
<tr>
<td>s11</td>
<td>
<loc href="http://schemas.xmlsoap.org/soap/envelope/">
http://schemas.xmlsoap.org/soap/envelope/
</loc>
</td>
<td>SOAP 1.1 <bibref ref="SOAP11"/></td>
</tr>
<tr>
<td>s12</td>
<td>
<loc href="http://www.w3.org/2003/05/soap-envelope">
http://www.w3.org/2003/05/soap-envelope
</loc>
</td>
<td>SOAP 1.2 <bibref ref="SOAP121"/></td>
</tr>
<tr>
<td>wsa</td>
<td>
<loc href="http://www.w3.org/2005/08/addressing">
http://www.w3.org/2005/08/addressing
</loc>
</td>
<td>WS-Addressing <bibref ref="AddrCore"/></td>
</tr>
<tr>
<td>wsevd</td>
<td>
<loc href="http://www.w3.org/&wsevd.nsprefix;/ws-evd">
http://www.w3.org/&wsevd.nsprefix;/ws-evd
</loc>
</td>
<td>This specification</td>
</tr>
<tr>
<td>xs</td>
<td>
<loc href="http://www.w3.org/2001/XMLSchema">
http://www.w3.org/2001/XMLSchema
</loc>
</td>
<td>
XML Schema <bibref ref="XMLSchema1"/>, <bibref ref="XMLSchema2"/>
</td>
</tr>
</tbody>
</table>
<p>
The working group intends to update the value of the Web Services
Event Descriptions namespace URI each time a new version of this document
is published until such time that the document reaches Candidate
Recommendation status. Once it has reached Candidate Recommendation
status, the working group intends to maintain the value of the
Web Services Event Descriptions namespace URI that was assigned in the
Candidate Recommendation unless significant changes are made that
impact the implementation or break post-CR implementations of the
specification. Also see
<loc href="http://www.w3.org/2001/tag/doc/namespaceState.html">
http://www.w3.org/2001/tag/doc/namespaceState.html
</loc> and
<loc href="http://www.w3.org/2005/07/13-nsuri">
http://www.w3.org/2005/07/13-nsuri
</loc>.
</p>
</div2>
<div2 id="terms">
<head>Terminology</head>
<glist>
<gitem>
<label> Notification </label>
<def>
<p>
A message sent to indicate that an event, or events, have occurred.
</p>
</def>
</gitem>
</glist>
</div2>
<div2 id="compliance">
<head>Compliance</head>
<p>
An implementation is not compliant with this specification if it fails to
satisfy one or more of the MUST or REQUIRED level requirements defined
herein. A SOAP Node MUST NOT use the XML namespace identifier for this
specification (listed in <specref ref="namespaces"/>) within SOAP
Envelopes unless it is compliant with this specification.
</p>
<p>
Normative text within this specification takes precedence over the XML
Schema and WSDL descriptions, which in turn take precedence over
outlines, which in turn take precedence over examples.
</p>
<p>
Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
MUST be performed according to <bibref ref="RFC3987"/> section 5.3.1.
</p>
</div2>
</div1>
<div1 id="Advertising">
<head>Advertising Event Information</head>
<p>
There are many use cases in which it is necessary for an endpoint
to advertise the structure and contents of the events that it might
generate. For example, a subscriber
might wish to know the shape of the events that are generated in
order to properly formulate a filter to limit the number of
notifications that are transmitted, or to ensure it can successfully
process the type of events that are transmitted.
</p>
<p>
There are many ways in which an endpoint could describe and
advertise the structure of the events for which it will issue
notifications. To provide a basic level of interoperability, this
specification defines the following mechanism, in
<specref ref="ETypes"/>, for describing and
advertising event information.
</p>
<p>
This specification only defines a mechanism by which events can be
described and advertised. How these events, and the properties of
these events that are described within an Event Descriptions document,
are serialized for transmission is out of scope
of this specification; but are expected to be fully described in
any specification that uses this one.
</p>
<div2 id="ETypes">
<head>Event Types & Event Descriptions</head>
<p>
A key concept in the description and advertisement of event information
is the "Event Type". An Event Type is a description of the syntactic
structure and value space of the set of events that share that type.
Event Types are independent of the pub/sub protocol used and the format
of the notifications used to transmit those events.
</p>
<p>
Event Types are described within an EventDescriptions element where
they contain a complete description of an event. A key aspect of this
description is the associated XML Schema Global Element Declaration
(GED) for each event.
EventDescriptions element has the following form:
</p>
<example>
<eg><wsevd:EventDescriptions targetNamespace="<emph>xs:anyURI</emph>" ...>
<wsevd:types>
<xs:schema ...>
...
</xs:schema>
<emph>xs:any</emph>*
</wsevd:types>
<wsevd:eventType name="<emph>xs:NCName</emph>" element="<emph>xs:QName</emph>" actionURI="<emph>xs:anyURI</emph>"? ...>
<emph>xs:any</emph>*
</wsevd:eventType> +
<emph>xs:any</emph>*
</wsevd:EventDescriptions></eg>
</example>
<p>
The XML Schema for the EventDescriptions element can be found in
<specref ref="EVDXSD"/>. The following describes additional, normative
constraints on the outlined listed above:
</p>
<glist>
<gitem>
<label> /wsevd:EventDescriptions </label>
<def>
<p>
This element contains the declarations of all the Event Types that
apply to a given context.
</p>
</def>
</gitem>
<gitem>
<label> /wsevd:EventDescriptions@targetNamespace </label>
<def>
<p>
This attribute defines the namespace affiliation of the Event Types
declared within the EventDescriptions element. Its value MUST be an
absolute IRI <bibref ref="RFC3987"/>. It SHOULD be dereferenceable.
</p>
</def>
</gitem>
<gitem>
<label> /wsevd:EventDescriptions/wsevd:types </label>
<def>
<p>
This element encloses data type definitions that are relevant to
the declared Event Types.
</p>
</def>
</gitem>
<gitem>
<label> /wsevd:EventDescriptions/wsevd:types/xs:schema </label>
<def>
<p>
As described earlier, an Event Type is defined by a Global Element
Declaration (GED) in XML Schema. This element contains collections
of imported and inlined schema components that describe the GEDs
that are used to define Event Types.
</p>
</def>
</gitem>
<gitem>
<label> /wsevd:EventDescriptions/wsevd:eventType </label>
<def>
<p>
This element describes a specific Event Type.
</p>
</def>
</gitem>
<gitem>
<label> /wsevd:EventDescriptions/wsevd:eventType/@name </label>
<def>
<p>
This attribute provides a name for this Event Type which MUST be
unique amongst
all the Event Types defined by the enclosing wsevd:EventDescriptions
element. In conjunction with a Prefix that is associated with the
value of /wsevd:EventDescriptions/@targetNamespace namespace URI, the
value of this attribute MAY be used as the LocalPart of a QName
that identifies this Event Type outside the context of the
enclosing wsevd:EventDescriptions element.
</p>
</def>
</gitem>
<gitem>
<label> /wsevd:EventDescriptions/wsevd:eventType/@element </label>
<def>
<p>
This attribute refers to a GED defined or imported in the
/wsevd:EventDescriptions/wsevd:types element. The referenced GED
serves as the definition of this Event Type.
</p>
</def>
</gitem>
<gitem>
<label> /wsevd:EventDescriptions/wsevd:eventType/@actionURI </label>
<def>
<p>
This OPTIONAL attribute provides a value for the 'action'
property which, depending upon the format of the
notification used to transmit the Event, serve as a potential aid
to identifying the semantics implied by the message. When not
present the implied value of this attribute is the concatenation
of the wsevd:EventDescriptions' targetNamespace attribute and
the wsevd:eventType name attribute separated by the '/' character.
</p>
</def>
</gitem>
</glist>
<p>
The following is an example of an EventDescriptions element that could
serve as a description of the Event Type used in
<specref ref="EVDExample"/>.
</p>
<example id="EVDSample">
<head>EventDescriptions</head>
<eg>(01) <wsevd:EventDescriptions
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:wsevd="http://www.w3.org/&wsevd.nsprefix;/ws-evd"
(04) xmlns:ow="http://www.example.org/oceanwatch">
(05) <wsevd:types>
(06) <xs:schema targetNamespace="http://www.example.org/oceanwatch">
(07) <xs:include schemaLocation="http://www.example.org/schemas/oceanwatch.xsd"/>
(08) <xs:element name="WindReport" type="ow:WindReportType"/>
(09) </xs:schema>
(10) </wsevd:types>
(11)
(12) <wsevd:eventType name="WindReportEvent"
(13) element="ow:WindReport"
(14) actionURI="http://www.example.org/oceanwatch/2003/WindReport"/>
(15) </wsevd:EventDescriptions></eg>
</example>
<p>
Lines (12-14) describe an Event Type with a QName of
"{http://www.example.org/oceanwatch/notifications}:WindReportEvent". The
GED for this Event Type is defined on line (08) as being of type
"{http://www.example.org/oceanwatch}:WindReportType".
</p>
<p>
The sample EventDescriptions in <specref ref="EVDSample"/> might describe
the following notification:
</p>
<example id="EVDExample">
<head>Hypothetical Notification</head>
<eg>(01) <s12:Envelope xmlns:s12="http://www.w3.org/2003/05/soap-envelop
e"
(02) xmlns:wsa="http://www.w3.org/2005/08/addressing"
(03) xmlns:ow="http://www.example.org/oceanwatch">
(04) <s12:Header>
(05) <wsa:Action>
(06) http://www.example.com/oceanwatch/2003/WindReport
(07) </wsa:Action>
(08) ...
(09) </s12:Header>
(10) <s12:Body>
(11) <ow:WindReport>
(12) <ow:Date>030701</ow:Date>
(13) <ow:Time>0041</ow:Time>
(14) <ow:Speed>65</ow:Speed>
(15) <ow:Location>BRADENTON BEACH</ow:Location>
(16) <ow:County>MANATEE</ow:County>
(17) <ow:State>FL</ow:State>
(18) <ow:Lat>27.46</ow:Lat>
(19) <ow:Long>82.70</ow:Long>
(20) <ow:Comments xml:lang="en-US" >
(21) WINDS 55 WITH GUSTS TO 65. ROOF TORN OFF BOAT HOUSE. REPORTED
(22) BY STORM SPOTTER. (TBW)
(23) </ow:Comments>
(24) </ow:WindReport>
(25) </s12:Body>
(26) </s12:Envelope></eg>
</example>
<div3>
<head>Retrieving Event Descriptions</head>
<p>
Although there are many ways in which an endpoint can make its
EventDescriptions available, this specification RECOMMENDS the use of
the mechanisms described in WS-MetadataExchange <bibref ref="MEX"/>.
This specification defines the following IRI to serve as the Dialect
IRI for the wsevd:EventDescriptions element.
</p>
<example>
<eg><loc href="http://www.w3.org/&wsevd.nsprefix;/ws-evd/EventDescriptions">http://www.w3.org/&wsevd.nsprefix;/ws-evd/EventDescriptions</loc></eg>
</example>
<p>
The value of the @Identifier attribute for this Metadata Section MUST
be equal to the value of its wsevd:EventDescriptions/@targetNamespace.
</p>
</div3>
<div3>
<head>Bindings for Event Descriptions</head>
<p>
Any specification of a publish-subscribe system that uses
Event Descriptions to advertise the events that are generated
MUST clearly define how those events are serialized when they
are transmitted to the receiver of notification messages.
</p>
</div3>
</div2>
</div1>
<div1 id="acks">
<head>Acknowledgements</head>
<p>
This specification has been developed as a result of joint
work with many individuals and teams, including:
Ashok Malhotra (Oracle Corp.),
Asir Vedamuthu (Microsoft Corp.),
Bob Freund (Hitachi, Ltd.),
Doug Davis (IBM),
Fred Maciel (Hitachi, Ltd.),
Geoff Bullen (Microsoft Corp.),
Gilbert Pilz (Oracle Corp.),
Greg Carpenter (Microsoft Corp.),
Jeff Mischkinsky (Oracle Corp.),
Katy Warr (IBM),
Li Li (Avaya Communications),
Mark Little (Red Hat),
Prasad Yendluri (Software AG),
Ram Jeyaraman (Microsoft Corp.),
Sreedhara Narayanaswamy (CA),
Sumeet Vij (Software AG),
Vikas Varma (Software AG),
Wu Chou (Avaya Communications),
Yves Lafon (W3C).
</p>
</div1>
<div1 id="refs">
<head>References</head>
<div2>
<head>Normative References</head>
<blist>
<bibl key="RFC 2119" id="RFC2119"
href="http://www.ietf.org/rfc/rfc2119.txt">
<titleref>
Key words for use in RFCs to Indicate Requirement Levels
</titleref>
, S. Bradner, Author.
Internet Engineering Task Force, March 1997.
</bibl>
<bibl key="RFC 3987" id="RFC3987"
href="http://www.ietf.org/rfc/rfc3987.txt">
<titleref>
Internationalized Resource Identifiers (IRIs)
</titleref>
, M. Duerst and M. Suignard, Authors.
Internet Engineering Task Force, January 2005.
</bibl>
</blist>
</div2>
<div2>
<head>Informative References</head>
<blist>
<bibl key="SOAP11" id="SOAP11"
href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">
<titleref>
W3C Note, "Simple Object Access Protocol (SOAP) 1.1"
</titleref>
, D. Box, et al, Editors.
World Wide Web Consortium (W3C), 8 May 2000.
</bibl>
<bibl key="SOAP12" id="SOAP121"
href="http://www.w3.org/TR/soap12-part1/">
<titleref>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
</titleref>
, M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
Editors.
World Wide Web Consortium (W3C), 27 April 2007.
</bibl>
<bibl key="WS-Addressing" id="AddrCore"
href="http://www.w3.org/TR/ws-addr-core">
<titleref>
W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
</titleref>
, M. Gudgin, M. Hadley, T. Rogers, Editors.
World Wide Web Consortium (W3C), 9 May 2006.
</bibl>
<bibl key="WS-MetadataExchange" id="MEX"
href="http://www.w3.org/TR/ws-metadata-exchange">
<titleref>
W3C Working Group Draft, "Web Services Metadata Exchange
(WS-MetadataExchange) 1.1"
</titleref>
, D. Davis, et al., Editors.
World Wide Web Consortium (W3C), 15 September 2009.
</bibl>
<bibl key="WSDL11" id="WSDL11"
href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">
<titleref>
W3C Note, "Web Services Description Language (WSDL) 1.1"
</titleref>
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
</bibl>
<bibl key="XML Infoset" id="XMLInfoset"
href="http://www.w3.org/TR/xml-infoset">
<titleref>
W3C Recommendation, "XML Information Set (Second Edition)"
</titleref>
, J. Cowan, R. Tobin, Editors.
World Wide Web Consortium (W3C), 4 February 2004.
</bibl>
<bibl key="XMLSchema - Part 1" id="XMLSchema1"
href="http://www.w3.org/TR/xmlschema-1/">
<titleref>
W3C Recommendation, "XML Schema Part 1: Structures (Second Edition)"
</titleref>
, H. Thompson, et al., Editors.
World Wide Web Consortium (W3C), 28 October 2004.
</bibl>
<bibl key="XMLSchema - Part 2" id="XMLSchema2"
href="http://www.w3.org/TR/xmlschema-2/">
<titleref>
W3C Recommendation, "XML Schema Part 2: Datatypes (Second Edition)"
</titleref>
, P. Biron, A. Malhotra, Editors.
World Wide Web Consortium (W3C), 28 October 2004.
</bibl>
</blist>
</div2>
</div1>
</body>
<back>
<div1 id="EVDXSD">
<head>XML Schema for EventDescriptions</head>
<p>
A normative copy of the XML Schema <bibref ref='XMLSchema1'/>,
<bibref ref='XMLSchema2'/> description for the EventDescriptions
element can be retrieved from the following address:
</p>
<example>
<eg><loc href='http://www.w3.org/&wsevd.nsprefix;/ws-evd/EventDescriptions.xsd'>http://www.w3.org/&wsevd.nsprefix;/ws-evd/EventDescriptions.xsd</loc></eg>
</example>
<p>
A non-normative copy of the XML schema is listed below for
convenience.
</p>
<example>
<eg><xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema'
targetNamespace='http://www.w3.org/&wsevd.nsprefix;/ws-evd'
elementFormDefault='qualified' attributeFormDefault='unqualified'>
<xs:element name='EventDescriptions'>
<xs:complexType>
<xs:sequence>
<xs:element name='types'>
<xs:annotation>
<xs:documentation>Data type definitions that are relevant to described notifications.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
</xs:sequence>
<xs:anyAttribute namespace='##other' processContents='lax'/>
</xs:complexType>
</xs:element>
<xs:element name='eventType' maxOccurs='unbounded'>
<xs:complexType>
<xs:sequence>
<xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
</xs:sequence>
<xs:attribute name='name' type='xs:NCName' use='required'/>
<xs:attribute name='element' type='xs:QName' use='required'/>
<xs:attribute name='actionURI' type='xs:anyURI' use='optional'/>
<xs:anyAttribute namespace='##other' processContents='lax'/>
</xs:complexType>
</xs:element>
<xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
</xs:sequence>
<xs:attribute name='targetNamespace' type='xs:anyURI' use='required'/>
<xs:anyAttribute namespace='##other' processContents='lax'/>
</xs:complexType>
</xs:element>
</xs:schema></eg>
</example>
</div1>
<div1 id="changelog">
<head>Change Log</head>
<table border="1">
<tbody>
<tr>
<th> Data </th>
<th> Author </th>
<th> Description </th>
</tr>
<tr>
<td> 2010/01/19 </td>
<td> DD </td>
<td> Added resolution of issue
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8068">8068</loc>
</td>
</tr>
</tbody>
</table>
</div1>
</back>
</spec>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.147
retrieving revision 1.148
diff -u -d -r1.147 -r1.148
--- wseventing.html 13 Jan 2010 01:54:35 -0000 1.147
+++ wseventing.html 19 Jan 2010 22:17:20 -0000 1.148
@@ -80,22 +80,21 @@
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
11.1 <a href="#iddiv2_1_2250">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2371">Informative References</a><br/>
+ 11.2 <a href="#iddiv2_1_2384">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Advertising">Advertising Event Information</a><br/>
A.1 <a href="#ETypes">Event Types & Event Descriptions</a><br/>
- A.1.1 <a href="#iddiv3_1_2677">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2698">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2703">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2721">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3_1_2586">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2607">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2612">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2630">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2748">Retrieving Notification WSDLs</a><br/>
- A.3 <a href="#iddiv2_1_2769">Multiple Event Information Metadata Sections</a><br/>
+ A.2.1 <a href="#iddiv3_1_2657">Retrieving Notification WSDLs</a><br/>
+ A.3 <a href="#iddiv2_1_2678">Multiple Event Information Metadata Sections</a><br/>
B <a href="#Schema">XML Schema</a><br/>
C <a href="#WSDL">WSDL</a><br/>
D <a href="#wrappedWSDL">WSDL for Standard Wrapped Delivery</a><br/>
-E <a href="#EDXSD">XML Schema for EventDescriptions</a><br/>
-F <a href="#changelog">Change Log</a><br/>
+E <a href="#changelog">Change Log</a><br/>
</p></div><hr/><div class="body"><div class="div1">
<h2><a name="composable" id="composable"/>1 Composable Architecture</h2><p>
By using the XML, SOAP <a href="#SOAP11">[SOAP11]</a>,
@@ -1668,7 +1667,12 @@
</cite></a>
, M. Gudgin, M. Hadley, T. Rogers, Editors.
World Wide Web Consortium (W3C), 9 May 2006.
- Available at <a href="http://www.w3.org/TR/ws-addr-soap">http://www.w3.org/TR/ws-addr-soap</a>.</dd><dt class="label"><a name="wspolicy" id="wspolicy"/>WS-Policy</dt><dd><a href="http://www.w3.org/TR/ws-policy/"><cite>
+ Available at <a href="http://www.w3.org/TR/ws-addr-soap">http://www.w3.org/TR/ws-addr-soap</a>.</dd><dt class="label"><a name="WSEVD" id="WSEVD"/>WS-EventDescriptions</dt><dd><a href="http://www.w3.org/TR/ws-evd"><cite>
+ W3C Working Group Draft, "Web Services Event Descriptions (WS-EventDescriptions) 1.0"
+ </cite></a>
+ , D. Davis, et al., Editors.
+ World Wide Web Consortium (W3C), 15 September 2009.
+ Available at <a href="http://www.w3.org/TR/ws-evd">http://www.w3.org/TR/ws-evd</a>.</dd><dt class="label"><a name="wspolicy" id="wspolicy"/>WS-Policy</dt><dd><a href="http://www.w3.org/TR/ws-policy/"><cite>
W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Framework"
</cite></a>
, A. Vedamuthu, et al., Editors.
@@ -1679,7 +1683,7 @@
, A. Vedamuthu, et al., Editors.
World Wide Web Consortium (W3C), 4 September 2007.
Available at <a href="http://www.w3.org/TR/ws-policy-attach">http://www.w3.org/TR/ws-policy-attach</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2371" id="iddiv2_1_2371"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
+<h3><a name="iddiv2_1_2384" id="iddiv2_1_2384"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
OASIS Standard, "Web Services Make Connection (WS-MakeConnection) 1.1"
Web Services Make Connection (WS-MakeConnection)
</cite></a>
@@ -1765,7 +1769,7 @@
There are many ways in which an event source could describe and
advertise the structure of the events for which it will issue
notifications. To provide a basic level of interoperability, this
- specification defines the following two OPTIONAL mechanisms, in
+ specification uses the following two OPTIONAL mechanisms, in
<a href="#ETypes"><b>A.1 Event Types & Event Descriptions</b></a> and <a href="#NWSDL"><b>A.2 Notification WSDLs</b></a>, for describing and
advertising event information. If an implementation of a WS-Eventing
event source chooses to describe the structure of its events and
@@ -1775,102 +1779,15 @@
of such mechanisms is out of the scope of this specification.
</p><div class="div2">
<h3><a name="ETypes" id="ETypes"/>A.1 Event Types & Event Descriptions</h3><p>
- A key concept in the description and advertisement of event information
- is the "Event Type". An Event Type is a description of the syntactic
- structure and value space of the set of events that share that type.
- Event Types are independent of both the WS-Eventing protocol and the
- format of the notifications used to transmit those events. For example,
- the following notification, although transmitted using the Wrapped
- Notification Format defined in <a href="#Subscribe"><b>4.1 Subscribe</b></a>, has the same
- Event Type as the notification in <a href="#Table13">Example 5-1</a>:
- </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="EDExample" id="EDExample"/>Example A-1: Hypothetical Wrapped Notification</div><div class="exampleInner"><pre>(01) <s12:Envelope xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
-(02) xmlns:wsa="http://www.w3.org/2005/08/addressing"
-(03) xmlns:wse="http://www.w3.org/2009/09/ws-evt"
-(04) xmlns:ow="http://www.example.org/oceanwatch">
-(05) <s12:Header>
-(06) <wsa:Action>
-(07) http://www.w3.org/2009/09/ws-evt/wrap/GenericSinkPortType/NotifyEvent
-(08) </wsa:Action>
-(09) ...
-(10) </s12:Header>
-(11) <s12:Body>
-(12) <wse:Notify actionURI="http://www.example.org/oceanwatch/2003/WindReport">
-(13) <ow:WindReport>
-(14) <ow:Date>030701</ow:Date>
-(15) <ow:Time>0041</ow:Time>
-(16) <ow:Speed>65</ow:Speed>
-(17) <ow:Location>BRADENTON BEACH</ow:Location>
-(18) <ow:County>MANATEE</ow:County>
-(19) <ow:State>FL</ow:State>
-(20) <ow:Lat>27.46</ow:Lat>
-(21) <ow:Long>82.70</ow:Long>
-(22) <ow:Comments xml:lang="en-US" >
-(23) WINDS 55 WITH GUSTS TO 65. ROOF TORN OFF BOAT HOUSE. REPORTED
-(24) BY STORM SPOTTER. (TBW)
-(25) </ow:Comments>
-(26) </ow:WindReport>
-(27) </wse:Notify>
-(28) </s12:Body>
-(29) </s12:Envelope></pre></div></div><p>
- Event Types MAY be described within an EventDescriptions element where
- they are defined by Global Element Declarations in XML Schema. The
- EventDescriptions element has the following form:
- </p><div class="exampleOuter"><div class="exampleInner"><pre><wse:EventDescriptions targetNamespace="<em>xs:anyURI</em>" ...>
- <wse:types>
- [ <xs:import namespace="<em>xs:anyURI</em>" schemaLocation="<em>xs:anyURI</em>"/> ? |
- <xs:schema targetNamespace="<em>xs:anyURI</em>"/> ?] *
- <em>xs:any</em>*
- </wse:types>
- <wse:eventType name="<em>xs:NCName</em>" element="<em>xs:QName</em>" actionURI="<em>xs:anyURI</em>"? ...>
- <em>xs:any</em>*
- </wse:eventType> +
- <em>xs:any</em>*
-</wse:EventDescriptions></pre></div></div><p>
- The XML Schema for the EventDescriptions element can be found in
- <a href="#EDXSD"><b>E XML Schema for EventDescriptions</b></a>. The following describes additional, normative
- constraints on the outlined listed above:
- </p><dl><dt class="label"> /wse:EventDescriptions </dt><dd><p>
- This element contains the declarations of all the Event Types that
- apply to a given context, such as a particular event source.
- </p></dd><dt class="label"> /wse:EventDescriptions@targetNamespace </dt><dd><p>
- This attribute defines the namespace affiliation of the Event Types
- declared within the EventDescriptions element. Its value MUST be an
- absolute IRI <a href="#RFC3987">[RFC 3987]</a>. It MAY be dereferenceable.
- </p></dd><dt class="label"> /wse:EventDescriptions/wse:types </dt><dd><p>
- As described earlier, an Event Type is defined by a Global Element
- Declaration (GED) in XML Schema. This element contains collections
- of imported and inlined schema components that describe the GEDs
- that are used to define Event Types.
- </p></dd><dt class="label"> /wse:EventDescriptions/wse:eventType </dt><dd><p>
- This element describes a specific Event Type.
- </p></dd><dt class="label"> /wse:EventDescriptions/wse:eventType/@name </dt><dd><p>
- This attribute provides a name for this Event Type which MUST be
- unique amongst
- all the Event Types defined by the enclosing wse:EventDescriptions
- element. In conjunction with a Prefix that is associated with the
- value of /wse:EventDescriptions/@targetNamespace namespace URI, the
- value of this attribute MAY be used as the LocalPart of a QName
- that identifies this Event Type outside the context of the
- enclosing wse:EventDescriptions element.
- </p></dd><dt class="label"> /wse:EventDescriptions/wse:eventType/@element </dt><dd><p>
- This attribute refers to a GED defined or imported in the
- /wse:EventDescriptions/wse:types element. The referenced GED
- serves as the definition of this Event Type.
- </p></dd><dt class="label"> /wse:EventDescriptions/wse:eventType/@actionURI </dt><dd><p>
- This OPTIONAL attribute provides a value for the various 'action'
- properties and attributes which, depending upon the format of the
- notification used to transmit the Event, serve as a potential aid
- to identifying the semantics implied by the message. When not
- present the implied value of this attribute is the concatenation
- of the wse:EventDescriptions' targetNamespace attribute and
- the wse:eventType name attribute separated by the '/' character.
- </p></dd></dl><p>
+ An event source MAY advertise the events that are generated by making
+ available an Event Description document as defined by
+ WS-EventDescriptions <a href="#WSEVD">[WS-EventDescriptions]</a>.
+ </p><p>
The following is an example of an EventDescriptions element that could
serve as a description of the Event Type used in
- <a href="#Table1">Example 2-1</a> and <a href="#EDExample">Example A-1</a>.
+ <a href="#Table1">Example 2-1</a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2667" id="idexample_1_2667"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2576" id="idexample_1_2576"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:wse="http://www.w3.org/2009/09/ws-evt"
(04) xmlns:ow="http://www.example.org/oceanwatch">
@@ -1890,7 +1807,7 @@
GED for this Event Type is defined on line (08) as being of type
"{http://www.example.org/oceanwatch}:WindReportType".
</p><div class="div3">
-<h4><a name="iddiv3_1_2677" id="iddiv3_1_2677"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2586" id="iddiv3_1_2586"/>A.1.1 Retrieving Event Descriptions</h4><p>
Although there are many ways in which an event source can make its
EventDescriptions available, this specification RECOMMENDS the use of
the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
@@ -1901,7 +1818,7 @@
be equal to the value of its wse:EventDescriptions/@targetNamespace. An
event source MUST NOT have more than one EventDescriptions document.
</p></div><div class="div3">
-<h4><a name="iddiv3_1_2698" id="iddiv3_1_2698"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2607" id="iddiv3_1_2607"/>A.1.2 Bindings for Event Descriptions</h4><p>
For any Notification Format it SHOULD be possible to determine how a
given wse:eventType will appear on the wire as a notification in a
subscription created with that format. The following sections define
@@ -1913,7 +1830,7 @@
Format, implementations MAY provide a Notification WSDL (see below)
that explicitly describes the notification operations.
</p><div class="div4">
-<h5><a name="iddiv4_1_2703" id="iddiv4_1_2703"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2612" id="iddiv4_1_2612"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
The information about an Event Type contained in the wse:eventType
element binds to a Unwrapped Notification for that type as follows:
</p><ul><li><p>
@@ -1927,7 +1844,7 @@
of the wse:eventType element corresponding to the type of the
event being transmitted.
</p></li></ul></div><div class="div4">
-<h5><a name="iddiv4_1_2721" id="iddiv4_1_2721"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2630" id="iddiv4_1_2630"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
The information about an Event Type contained in the eventType element
binds to a Wrapped Notification for that type as follows:
</p><ul><li><p>
@@ -1951,7 +1868,7 @@
successful Subscribe request that used a particular Format IRI. The
following is an example of a Notification WSDL:
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2742" id="idexample_1_2742"/>Example A-3: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexample_1_2651" id="idexample_1_2651"/>Example A-2: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:xs="http://www.w3.org/2001/XMLSchema"
(04) xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
@@ -1986,7 +1903,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2748" id="iddiv3_1_2748"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2657" id="iddiv3_1_2657"/>A.2.1 Retrieving Notification WSDLs</h4><p>
Although there are many ways in which an event source can make
Notification WSDLs available, this specification RECOMMENDS the use of
the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
@@ -2002,7 +1919,7 @@
Format IRI/@Identifier, there MUST NOT exist more than one
Notification WSDL document.
</p></div></div><div class="div2">
-<h3><a name="iddiv2_1_2769" id="iddiv2_1_2769"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2678" id="iddiv2_1_2678"/>A.3 Multiple Event Information Metadata Sections</h3><p>
When WS-MetadataExchange is used to retrieve metadata about an event
source, recipients of mex:Metadata elements that contain Metadata
Sections with both the
@@ -2479,49 +2396,7 @@
</operation>
</portType>
</definitions></pre></div></div></div><div class="div1">
-<h2><a name="EDXSD" id="EDXSD"/>E XML Schema for EventDescriptions</h2><p>
- A normative copy of the XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,
- <a href="#XMLSchema2">[XMLSchema - Part 2]</a> description for the EventDescriptions
- element can be retrieved from the following address:
- </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-evt/EventDescriptions.xsd">http://www.w3.org/2009/09/ws-evt/EventDescriptions.xsd</a></pre></div></div><p>
- A non-normative copy of the XML schema is listed below for
- convenience.
- </p><div class="exampleOuter"><div class="exampleInner"><pre><xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema'
- targetNamespace='http://www.w3.org/2009/09/ws-evt'
- elementFormDefault='qualified' attributeFormDefault='unqualified'>
- <xs:element name='EventDescriptions'>
- <xs:complexType>
- <xs:sequence>
- <xs:element name='types'>
- <xs:annotation>
- <xs:documentation>Data type definitions that are relevant to described notifications.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
- </xs:sequence>
- <xs:anyAttribute namespace='##other' processContents='lax'/>
- </xs:complexType>
- </xs:element>
- <xs:element name='eventType' maxOccurs='unbounded'>
- <xs:complexType>
- <xs:sequence>
- <xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
- </xs:sequence>
- <xs:attribute name='name' type='xs:NCName' use='required'/>
- <xs:attribute name='element' type='xs:QName' use='required'/>
- <xs:attribute name='actionURI' type='xs:anyURI' use='optional'/>
- <xs:anyAttribute namespace='##other' processContents='lax'/>
- </xs:complexType>
- </xs:element>
- <xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
- </xs:sequence>
- <xs:attribute name='targetNamespace' type='xs:anyURI' use='required'/>
- <xs:anyAttribute namespace='##other' processContents='lax'/>
- </xs:complexType>
- </xs:element>
-</xs:schema></pre></div></div></div><div class="div1">
-<h2><a name="changelog" id="changelog"/>F Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
+<h2><a name="changelog" id="changelog"/>E Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6391">6391</a></td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a></td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6427">6427</a></td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
@@ -2609,4 +2484,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8165">8165</a></td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8164">8164</a></td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8281">8281</a></td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8176">8176</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8176">8176</a></td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8068">8068</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.141
retrieving revision 1.142
diff -u -d -r1.141 -r1.142
--- wseventing.xml 13 Jan 2010 01:54:35 -0000 1.141
+++ wseventing.xml 19 Jan 2010 22:17:20 -0000 1.142
@@ -2966,6 +2966,15 @@
World Wide Web Consortium (W3C), 9 May 2006.
</bibl>
+ <bibl key="WS-EventDescriptions" id="WSEVD"
+ href="http://www.w3.org/TR/ws-evd">
+ <titleref>
+ W3C Working Group Draft, "Web Services Event Descriptions (WS-EventDescriptions) 1.0"
+ </titleref>
+ , D. Davis, et al., Editors.
+ World Wide Web Consortium (W3C), 15 September 2009.
+ </bibl>
+
<bibl key="WS-Policy" id="wspolicy"
href="http://www.w3.org/TR/ws-policy/">
<titleref>
@@ -3136,7 +3145,7 @@
There are many ways in which an event source could describe and
advertise the structure of the events for which it will issue
notifications. To provide a basic level of interoperability, this
- specification defines the following two OPTIONAL mechanisms, in
+ specification uses the following two OPTIONAL mechanisms, in
<specref ref="ETypes"/> and <specref ref="NWSDL"/>, for describing and
advertising event information. If an implementation of a WS-Eventing
event source chooses to describe the structure of its events and
@@ -3150,159 +3159,15 @@
<head>Event Types & Event Descriptions</head>
<p>
- A key concept in the description and advertisement of event information
- is the "Event Type". An Event Type is a description of the syntactic
- structure and value space of the set of events that share that type.
- Event Types are independent of both the WS-Eventing protocol and the
- format of the notifications used to transmit those events. For example,
- the following notification, although transmitted using the Wrapped
- Notification Format defined in <specref ref="Subscribe"/>, has the same
- Event Type as the notification in <specref ref="Table13"/>:
- </p>
-
- <example id="EDExample">
- <head>Hypothetical Wrapped Notification</head>
- <eg>(01) <s12:Envelope xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
-(02) xmlns:wsa="http://www.w3.org/2005/08/addressing"
-(03) xmlns:wse="http://www.w3.org/&wsevt.nsprefix;/ws-evt"
-(04) xmlns:ow="http://www.example.org/oceanwatch">
-(05) <s12:Header>
-(06) <wsa:Action>
-(07) http://www.w3.org/&wsevt.nsprefix;/ws-evt/wrap/GenericSinkPortType/NotifyEvent
-(08) </wsa:Action>
-(09) ...
-(10) </s12:Header>
-(11) <s12:Body>
-(12) <wse:Notify actionURI="http://www.example.org/oceanwatch/2003/WindReport">
-(13) <ow:WindReport>
-(14) <ow:Date>030701</ow:Date>
-(15) <ow:Time>0041</ow:Time>
-(16) <ow:Speed>65</ow:Speed>
-(17) <ow:Location>BRADENTON BEACH</ow:Location>
-(18) <ow:County>MANATEE</ow:County>
-(19) <ow:State>FL</ow:State>
-(20) <ow:Lat>27.46</ow:Lat>
-(21) <ow:Long>82.70</ow:Long>
-(22) <ow:Comments xml:lang="en-US" >
-(23) WINDS 55 WITH GUSTS TO 65. ROOF TORN OFF BOAT HOUSE. REPORTED
-(24) BY STORM SPOTTER. (TBW)
-(25) </ow:Comments>
-(26) </ow:WindReport>
-(27) </wse:Notify>
-(28) </s12:Body>
-(29) </s12:Envelope></eg>
- </example>
-
- <p>
- Event Types MAY be described within an EventDescriptions element where
- they are defined by Global Element Declarations in XML Schema. The
- EventDescriptions element has the following form:
+ An event source MAY advertise the events that are generated by making
+ available an Event Description document as defined by
+ WS-EventDescriptions <bibref ref="WSEVD"/>.
</p>
- <example>
- <eg><wse:EventDescriptions targetNamespace="<emph>xs:anyURI</emph>" ...>
- <wse:types>
- [ <xs:import namespace="<emph>xs:anyURI</emph>" schemaLocation="<emph>xs:anyURI</emph>"/> ? |
- <xs:schema targetNamespace="<emph>xs:anyURI</emph>"/> ?] *
- <emph>xs:any</emph>*
- </wse:types>
- <wse:eventType name="<emph>xs:NCName</emph>" element="<emph>xs:QName</emph>" actionURI="<emph>xs:anyURI</emph>"? ...>
- <emph>xs:any</emph>*
- </wse:eventType> +
- <emph>xs:any</emph>*
-</wse:EventDescriptions></eg>
- </example>
-
- <p>
- The XML Schema for the EventDescriptions element can be found in
- <specref ref="EDXSD"/>. The following describes additional, normative
- constraints on the outlined listed above:
- </p>
-
- <glist>
- <gitem>
- <label> /wse:EventDescriptions </label>
- <def>
- <p>
- This element contains the declarations of all the Event Types that
- apply to a given context, such as a particular event source.
- </p>
- </def>
- </gitem>
- <gitem>
- <label> /wse:EventDescriptions@targetNamespace </label>
- <def>
- <p>
- This attribute defines the namespace affiliation of the Event Types
- declared within the EventDescriptions element. Its value MUST be an
- absolute IRI <bibref ref="RFC3987"/>. It MAY be dereferenceable.
- </p>
- </def>
- </gitem>
- <gitem>
- <label> /wse:EventDescriptions/wse:types </label>
- <def>
- <p>
- As described earlier, an Event Type is defined by a Global Element
- Declaration (GED) in XML Schema. This element contains collections
- of imported and inlined schema components that describe the GEDs
- that are used to define Event Types.
- </p>
- </def>
- </gitem>
- <gitem>
- <label> /wse:EventDescriptions/wse:eventType </label>
- <def>
- <p>
- This element describes a specific Event Type.
- </p>
- </def>
- </gitem>
- <gitem>
- <label> /wse:EventDescriptions/wse:eventType/@name </label>
- <def>
- <p>
- This attribute provides a name for this Event Type which MUST be
- unique amongst
- all the Event Types defined by the enclosing wse:EventDescriptions
- element. In conjunction with a Prefix that is associated with the
- value of /wse:EventDescriptions/@targetNamespace namespace URI, the
- value of this attribute MAY be used as the LocalPart of a QName
- that identifies this Event Type outside the context of the
- enclosing wse:EventDescriptions element.
- </p>
- </def>
- </gitem>
- <gitem>
- <label> /wse:EventDescriptions/wse:eventType/@element </label>
- <def>
- <p>
- This attribute refers to a GED defined or imported in the
- /wse:EventDescriptions/wse:types element. The referenced GED
- serves as the definition of this Event Type.
- </p>
- </def>
- </gitem>
- <gitem>
- <label> /wse:EventDescriptions/wse:eventType/@actionURI </label>
- <def>
- <p>
- This OPTIONAL attribute provides a value for the various 'action'
- properties and attributes which, depending upon the format of the
- notification used to transmit the Event, serve as a potential aid
- to identifying the semantics implied by the message. When not
- present the implied value of this attribute is the concatenation
- of the wse:EventDescriptions' targetNamespace attribute and
- the wse:eventType name attribute separated by the '/' character.
- </p>
- </def>
- </gitem>
- </glist>
-
<p>
The following is an example of an EventDescriptions element that could
serve as a description of the Event Type used in
- <specref ref="Table1"/> and <specref ref="EDExample"/>.
+ <specref ref="Table1"/>.
</p>
<example>
@@ -4028,63 +3893,6 @@
</div1>
- <div1 id="EDXSD">
- <head>XML Schema for EventDescriptions</head>
-
- <p>
- A normative copy of the XML Schema <bibref ref='XMLSchema1'/>,
- <bibref ref='XMLSchema2'/> description for the EventDescriptions
- element can be retrieved from the following address:
- </p>
-
- <example>
- <eg><loc href='http://www.w3.org/&wsevt.nsprefix;/ws-evt/EventDescriptions.xsd'>http://www.w3.org/&wsevt.nsprefix;/ws-evt/EventDescriptions.xsd</loc></eg>
- </example>
-
- <p>
- A non-normative copy of the XML schema is listed below for
- convenience.
- </p>
-
- <example>
- <eg><xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema'
- targetNamespace='http://www.w3.org/&wsevt.nsprefix;/ws-evt'
- elementFormDefault='qualified' attributeFormDefault='unqualified'>
- <xs:element name='EventDescriptions'>
- <xs:complexType>
- <xs:sequence>
- <xs:element name='types'>
- <xs:annotation>
- <xs:documentation>Data type definitions that are relevant to described notifications.</xs:documentation>
- </xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
- </xs:sequence>
- <xs:anyAttribute namespace='##other' processContents='lax'/>
- </xs:complexType>
- </xs:element>
- <xs:element name='eventType' maxOccurs='unbounded'>
- <xs:complexType>
- <xs:sequence>
- <xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
- </xs:sequence>
- <xs:attribute name='name' type='xs:NCName' use='required'/>
- <xs:attribute name='element' type='xs:QName' use='required'/>
- <xs:attribute name='actionURI' type='xs:anyURI' use='optional'/>
- <xs:anyAttribute namespace='##other' processContents='lax'/>
- </xs:complexType>
- </xs:element>
- <xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
- </xs:sequence>
- <xs:attribute name='targetNamespace' type='xs:anyURI' use='required'/>
- <xs:anyAttribute namespace='##other' processContents='lax'/>
- </xs:complexType>
- </xs:element>
-</xs:schema></eg>
- </example>
- </div1>
-
<div1 id="changelog">
<head>Change Log</head>
@@ -4698,6 +4506,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8176">8176</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/01/19 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8068">8068</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Tuesday, 19 January 2010 22:17:27 UTC