After looking at the example xml document for the MEG detector I would like to make the following suggestion.
Only a small portion of the power of XML is used with the MEG example i.e., the ability to express the data as a
hierarchical tree. Missing is the powerful feature of XML to establish a schema for the XML document specific
to ROME that enforces a valid structure.
XML uses the XML Schema language, which is in turn based on XML, to define a schema for a document. I
propose that a ROME schema be developed that defines an XML document that the ROME builder can read
and process. By having such a schema, general purpose XML editors can validate the XML document prior to
invoking the ROME builder. Thus the schema greatly simplifies a user's task of developing a ROME xml
document describing their experiment. In addition, a good XML editor uses the schema to indicate to the user
the elements available at any particular point in the document so that the user doesn't have to remember all the
entries, which are required or optional to describe an experiment.
With this e-mail I include two documents. The first is an example schema for ROME. This schema is
incomplete, but illustrates the major concepts of using a schema to specify the acceptable format of the XML
document and providing help to the user for building the document. The second is an example XML document
built using the ROME sample schema. It is for an experiment currently in production at the Los Alamos
National Laboratory.
To get this example to work you will have to change the second line of DANCESchema.xml so that it properly
points to the ROME.xsd document. For this example I used the Java based XML editor Oxygen.
Notes on Schema:
1) Every element in the schema has a fixed name. All experimental data is included as either xml data or an
xml attribute.
2) Based on the suggestion by http://www.xmlfiles.com/xml/xml_attributes.asp attributes are used sparingly or
not at all. Instead data is specified as XML data e.g. <data>the actual data</data>.
If you have any questions concerning this example please e-mail jwouters@lanl.gov. |