- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Sat, 15 Jan 2011 16:35:52 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv11613
Modified Files:
scenario.html scenario.xml
Log Message:
add more events to the scenario and clean up some text
Index: scenario.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/scenario.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- scenario.xml 15 Jan 2011 16:02:47 -0000 1.17
+++ scenario.xml 15 Jan 2011 16:35:50 -0000 1.18
@@ -372,7 +372,7 @@
<eg><sce:Animal ...>
<sce:ID> <emph>xs:string</emph> </sce:ID>
<sce:Name> <emph>xs:string</emph> </sce:Name>
- <sce:Birthdate> <emph>xs:date</emph> </sce:Birthdate>
+ <sce:Birthdate> <emph>xs:dateTime</emph> </sce:Birthdate>
<sce:Gender> <emph>xs:string</emph> </sce:Gender>
<sce:Family> <emph>xs:string</emph> </sce:Family>
<sce:Genus> <emph>xs:string</emph> </sce:Genus>
@@ -386,6 +386,16 @@
</sce:Animal> </eg>
</example>
+ <p>
+ The location of the tags is expressed in GPS coordinates using the GPS
+ eXchange Format, an XML schema designed as a common GPS data format
+ for software applications. In addition to the basic GPS information
+ (latitude, longitude, elevation, and time), the Animal's
+ XML represenation includes
+ an ID that uniquely identifies the tag and, by inference, the animal
+ that the tag is attached to.
+ </p>
+
<div2>
<head>Predefined Animals/Tags</head>
@@ -432,37 +442,58 @@
</div2>
- <div2 id="evt_description">
- <head>Event Description</head>
+ <div2 id="Events">
+ <head>Events</head>
<p>
- The location of the tags is expressed in GPS coordinates using the GPS
- eXchange Format, an XML schema designed as a common GPS data format
- for software applications. In addition to the basic GPS information
- (latitude, longitude, elevation, and time), the notifications include
- an ID that uniquely identifies the tag and, by inference, the animal
- that the tag is attached to. An EventDescriptions document that
- describes the structure of the event information within the
- notifications can be found in <specref ref="wsdl"/>.
+ This scenario defines several events that MUST be generated if
+ the service implementation supports WS-Eventing. The following
+ events are defined:
</p>
- </div2>
- <div2>
- <head>Event Timing</head>
- <p>
- While in the real world the frequency of notifications might be
- hourly or even daily, for the sake of feasibility we compress time
- by a scale of 1/120 so that one hour in 'scenario time' is thirty
- seconds in real-world time. The time data contained in the
- notifications will reflect scenario time.
- </p>
+ <ulist>
+ <item>
+ <kw> NewAnimal </kw><phrase/>
+ <p>
+ Generated when a new Animal is added to the tracking system.
+ </p>
+ </item>
+ <item>
+ <kw> UpdateLocation </kw><phrase/>
+ <p>
+ Generated when an Animal's locationis updated.
+ While in the real world the frequency of this event might be
+ hourly or even daily, for the sake of feasibility we compress time
+ by a scale of 1/120 so that one hour in 'scenario time' is thirty
+ seconds in real-world time. The time data contained in the
+ notifications will reflect scenario time.
+ </p>
+ </item>
+ <item>
+ <kw> UpdateAnimal </kw><phrase/>
+ <p>
+ Generated when an Animal's data is updated in the tracking system.
+ Note that this event is different from the updating of the
+ GPS coordinate property. This event is sent when any other
+ property (e.g. Name) is updated.
+ </p>
+ </item>
+ <item>
+ <kw> RemoveAnimal </kw><phrase/>
+ <p>
+ Generated when an Animal is removed to the tracking system.
+ </p>
+ </item>
+ </ulist>
+
<p>
- Implementations that support modifications of the animal's tag data
- (via WS-Tranfser and/or WS-Fragment) MUST also send out an event
- each time the non-location based data of a tag is updated (i.e.
- any field other than the "Current Location" field). This will allow
- for interested parties to be notified when the data is updated.
+ Each of the event that are generated will include the
+ full XML represenation of the Animal within the Body of the event.
+ An EventDescriptions document that
+ describes the structure of the event information within the
+ notifications can be found in <specref ref="evd"/>.
</p>
+
</div2>
<div2>
Index: scenario.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/scenario.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- scenario.html 15 Jan 2011 16:02:47 -0000 1.17
+++ scenario.html 15 Jan 2011 16:35:50 -0000 1.18
@@ -49,59 +49,58 @@
2 <a href="#notterms">Notations and Terminology</a><br/>
2.1 <a href="#conventions">Notational Conventions</a><br/>
3 <a href="#description">Scenario Description</a><br/>
- 3.1 <a href="#iddiv2x1x607">Predefined Animals/Tags</a><br/>
- 3.2 <a href="#evt_description">Event Description</a><br/>
- 3.3 <a href="#iddiv2x1x670">Event Timing</a><br/>
- 3.4 <a href="#iddiv2x1x677">Structure of Test Sections</a><br/>
-4 <a href="#iddiv1x1x695">WS-MetadataExchange Tests</a><br/>
- 4.1 <a href="#iddiv2x1x700">GetWSDL Test</a><br/>
- 4.2 <a href="#iddiv2x1x726">Empty GetMetadata Test</a><br/>
- 4.3 <a href="#iddiv2x1x752">WSDL GetMetadata Test</a><br/>
[...1276 lines suppressed...]
</p></div></div></div><div class="div1">
<h2><a name="wsdl" id="wsdl"/>8 WSDL</h2><div class="div2">
-<h3><a name="iddiv2x1x2352" id="iddiv2x1x2352"/>8.1 Event Source WSDL</h3><p>
+<h3><a name="iddiv2x1x2374" id="iddiv2x1x2374"/>8.1 Event Source WSDL</h3><p>
TBD
</p></div><div class="div2">
-<h3><a name="iddiv2x1x2357" id="iddiv2x1x2357"/>8.2 Notification WSDL</h3><p>
+<h3><a name="iddiv2x1x2379" id="iddiv2x1x2379"/>8.2 Notification WSDL</h3><p>
Available here:
<a href="http://www.w3.org/2002/ws/ra/edcopies/scenario/scenarioSink.wsdl">http://www.w3.org/2002/ws/ra/edcopies/scenario/scenarioSink.wsdl</a></p></div></div><div class="div1">
<h2><a name="evd" id="evd"/>9 EventDescriptions</h2><p>
@@ -1562,7 +1573,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="References" id="References"/>12 References</h2><div class="div2">
-<h3><a name="iddiv2x1x2400" id="iddiv2x1x2400"/>12.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>
+<h3><a name="iddiv2x1x2422" id="iddiv2x1x2422"/>12.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.
Received on Saturday, 15 January 2011 16:35:55 UTC