10 messages in org.oasis-open.lists.xri-editorsRE: [xri-editors] mustUnderstand attr...| From | Sent On | Attachments |
|---|---|---|
| Dave McAlpin | Jan 27, 2005 11:04 am | |
| Wachob, Gabe | Jan 27, 2005 11:24 am | |
| Drummond Reed | Jan 27, 2005 11:35 am | |
| Wachob, Gabe | Jan 27, 2005 1:05 pm | |
| Davis, Peter | Jan 27, 2005 1:08 pm | |
| Dave McAlpin | Jan 27, 2005 1:16 pm | |
| Wachob, Gabe | Jan 27, 2005 1:44 pm | |
| Drummond Reed | Jan 27, 2005 4:02 pm | |
| Dave McAlpin | Jan 27, 2005 4:06 pm | |
| Drummond Reed | Jan 27, 2005 4:13 pm |
| Subject: | RE: [xri-editors] mustUnderstand attribute? | |
|---|---|---|
| From: | Dave McAlpin (Dave...@epok.net) | |
| Date: | Jan 27, 2005 11:04:32 am | |
| List: | org.oasis-open.lists.xri-editors | |
I don't see the use case. What's an example of additional data in an XRID that _must_ be processed by the client?
-----Original Message----- From: Wachob, Gabe [mailto:gwac...@visa.com] Sent: Thursday, January 27, 2005 9:54 AM To: xri-...@lists.oasis-open.org 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...
-Gabe
__________________________________________________ gwac...@visa.com Chief Systems Architect Technology Strategies and Standards Visa International Phone: +1.650.432.3696 Fax: +1.650.554.6817
To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/xri-editors/members/leave_w orkgroup.php.
-- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.302 / Virus Database: 265.8.1 - Release Date: 1/27/2005