create and revise schema docs for ecogrid messages
Schema document for query, read, RSIDS, structure, with definitions and
examples. This is a formalization of the schemas we developed at the Seattle
EcoGrid meeting, meant to be captured and documented.
Target deadline: April 18
#4 Updated by Jing Tao about 18 years ago
To my understanding, resultset.xsd is for RISD type in queryInterface.wsdl. If
it has query itself (filter) in resultset schema, it will be very easy for
PortType decodeRISD. Because RISD already has the query part.
By the way, resultset has an element name "sendTime" and in
queryInterface3.wsdl, RISD type has an element named "timeStamp". Are they
#5 Updated by Matt Jones almost 18 years ago
At the Seattle (Sept 2003) EcoGrid meeting we decided:
-- add repeatable returnfield element for specifying structure of return records
-- add system, namespace, modificationDate, and creationDate to each record
-- identifiers for a record are considered relative URIs, with a base value
of the "system" attribute for that metadata, where the system should
contain the GSH for an ecogrid enabled server:
so, for example, system="ecogrid://ecogrid.nceas.ucsb.edu"
-- modify the record internal structure by creating a composite document
that contains all of the values specified in returnfield elements with
their parent elements. If the path does not reference a leaf node
text element, then all of the children of that node are returned.
For example, if the query had:
returnfield="/eml/dataset/title" and returnfield="/eml/dataset/creator"
The record would look like:
<title>Some random title</title>