[
Lists Home |
Date Index |
Thread Index
]
On Sun, 2002-03-03 at 18:03, Elliotte Rusty Harold wrote:
> However, that's not an option in the current XInclude draft. It
> specifically states in section 4.4 Fallback Behavior:
>
> XInclude processors must perform fallback behavior in the event of a
> resource error, as follows:
>
> If you turn off fallbacks, then you're not doing XInclude processing
> according to the latest CR. The fallback option is a critical
> difference between XInclude and external entities.
Then that leaves me wondering yet again whether XInclude is as good an
idea as its promoters seems to believe. Being _stuck_ with error
information in the content of a document rather than an explicit warning
seems like a pretty poor way to communicate that an error has occurred.
Guess I'll stick to my old-style tools, and leave those laser-beams
alone.
--
Simon St.Laurent
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com
|
