On Dec 14, 2007, at 16:21, Vincent Hennebert wrote:
<snip />
The idea is not only to make the implementation more correct. For
instance, dealing with property-resolution if and when it is needed,
leads to a more correct implementation of inherited properties,
relative
font-sizes, percentages, etc. in case of fo:markers. Another cool
advantage is that, for documents with a lot of markers, the
savings on
processing time should be significantly reduced if only a fraction of
the markers actually gets retrieved. (A small disadvantage if one
single
fo:marker gets retrieved multiple times into an identical context...
And no validation is performed on a marker’s children while they
aren’t
retrieved.
Not entirely. Basic validation (content-model) is always performed.
Only property validation is deferred.
Which may make a single document suddenly fail months after
the production tool chain has been set up.
That's always a risk, yes... iff the error never showed up during the
testing.
The risks are very, very minimal IMO.
Cheers
Andreas
