[
Lists Home |
Date Index |
Thread Index
]
it would mean that entities in attribute values could not be resolved
in the dynamic context of parsing the attribute value itself. the rules
would be those of normal namespace scope. an in-line namespace
processing mechanism already requires the namespace declarations to be
handled before the names of the attributes can be resolved, which must
be done before the values can be normalized. which would mean that
entity resolution could occur in the attribute value normalization
phase. which is still before the element is reported to the application.
On Tuesday, Oct 21, 2003, at 22:24 Europe/Berlin, Michael Kay wrote:
>> I've done some experiments with this in Ripper, and it's
>> about ten lines of code to make the change.
>
> Presumably you create a dependency on attribute order by requiring a
> namespace to be declared before it is used in an entity reference?
> Otherwise you open the door to all sorts of circularities.
>
...
|