Lists Home |
Date Index |
On Friday 01 February 2002 02:48 pm, Michael Kay wrote:
> Apart from anything else, I've always felt that the XLink/XPointer
> architecture was far too presentation-oriented. It fails to
> recognize that the document as displayed on screen may be only
> distantly related to the source XML, which to my mind is the essence
> of the XML success story. Ranges don't mean anything unless your
> document is being displayed more-or-less as-is.
There are issues around this, sure. We used to call it the "Content in
Context" problem.... do you link to the source, or to derived view.
At the end of the day, that is at least partly an application question.
That said, I implemented XPointer for both match and select patterns
in XT. With a fairly small amount of work, I might even be able to
hook up an XLink resolver into the XSLT processor.
FWIW. I have seldom seen real cases where you couldn't project the
range information forward through a transformation... you can always
do intermediary fixups along the way. The *real* problem is trying to
correlate the transformation output back to the source. XSLT certainly
doesn't make that easy, ranges or not.