I don't see the use case. What's an example of additional data in an
XRID that _must_ be processed by the client?
From: Wachob, Gabe [mailto:gwac...@visa.com]
Sent: Thursday, January 27, 2005 9:54 AM
Subject: [xri-editors] mustUnderstand attribute?
Folks often talk about a mustUnderstand attribute as a way of
controlling the use of extension elements in processing models
surrounding XML documents.
The idea is that a simple processor is allowed to ignore all elements it
doesn't understand unless an element has a mustUnderstand="true"
attribute. In this case, the processor, if it doesn't understand the
element, must throw up its hands and give up. This allows an extension
author to create an extension that MUST be processed for correct
functionality. Useful for security features, for example.
Do we want to put something like this in XRI? Seems like it's a good way
to future-proof current implementations and prevent breakage and
headache down the road...
Chief Systems Architect
Technology Strategies and Standards
Phone: +1.650.432.3696 Fax: +1.650.554.6817