From: Suman Nath (sknath@cmu.edu)
Date: 01/31/03
The static metadata specified in the schema plus the dynamic sensor data
sent by the senselets makes the global XML database on which users can make
query on.
In case of the parking space finder, the schema lists all the data, but some
of the tag values (total, in-use) are changed periodically by the senselets.
You can also think of a schema listing only the static metadata: in that
case senselets send XUPDATE commands to dynamically add or remove tags
ocntaining sensor data. For example, you can think that the senselet cat
identify a red car, and when ared car appears in the parking lot, it sends
an XUPDATE command to create a tag "<color> red </color>"
Since we do not expect you to know XUPDATE details to add/remove tags, you
can use the first, simpler approach.
-----Original Message-----
From: owner-irisnet-course@intel-iris.net
[mailto:owner-irisnet-course@intel-iris.net]On Behalf Of Tadashi Okoshi
Sent: Thursday, January 30, 2003 6:59 PM
To: irisnet-course@intel-iris.net
Subject: Schema (figure2 P7)
In the parking service case, is figure 2 on page 7 a XML schema
which will be passed to an OA in the setup phase of the parking
service with "add file ... " command? Or is it just a "snapshot"
of the database in a certain point of execution?
What I want to know is what the static meta-data set by the initial XML
file is, and what the data dynamically set by SAs in the parking service
example.
Tadashi Okoshi
This archive was generated by hypermail 2.1.5 : 06/10/04 EDT