Lists Home |
Date Index |
>>> Didier PH Martin <email@example.com> 7/24/2006 1:30:29 PM >>>
Let me expand more on the "requirement info set" that an interpreting
environment needs to proper handle the document.
a) every Datuments or web application needs to include some meta data
for instance, its dependencies with specific versions, modules,
b) We know that relying on the browser to figure this out is a mess
Actually, this kind of meta data can be included in every HTTP
headers but it is very hard to encode HTTP headers in URL or authoring
tools. You'll need to expand the HTTP server basic functionality with
code to do so. Thus, HTTP headers to specify the required capabilities
often a show stopper.
The other way is to include the meta information into the document
without damaging the document's structure. RDF could be a good
a client side engine can extract, decipher, interpret this RDF fragment
check is every PRE-CONDITIONS are met and suggest some mitigation
or re-direct to a downgraded version otherwise.
For instance to take Peter's example, the CML document would include an
fragment to indicate the required capabilities and redirect to another
document containing only images for the other environments in case
requirements are not met. The user may get the choice to go for it
not following the suggestions and trying it anyway.
Another way is to add a new parameter (i.e command) to be interpreted;
example, a parameter pointing to an RDF document containing the
requirements. This way, the requirements are decoupled from the
can easily be updated.
Didier PH Martin (from Didier's lab)
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription