W3C home > Mailing lists > Public > www-svg@w3.org > January 2006

RE: SVGT 1.2: SVG fragment identifiers

From: Doug Schepers <doug@schepers.cc>
Date: Mon, 2 Jan 2006 23:47:48 -0500
To: "'Maciej Stachowiak'" <mjs@apple.com>, <www-svg@w3c.org>
Message-Id: <20060103044748.7EF1960ADF@filch.dreamhost.com>

Hi, Maciej-

Maciej Stachowiak wrote:
|
| Here's the direct, word-for-word quote:
| 
| "When a source document performs a link into an SVG document via an  
| HTML [HTML4] anchor element (i.e., <a href=...> element in HTML) or  
| an XLink specification [XLINK], then the SVG fragment identifier  
| shall specify the initial view into the SVG document, as follows:"
| 
| As written it clearly seems to be specifying specifically the  
| behavior of HTML4 anchor elements and XLinks.
|
[...]
| 
| That's not how it reads to me - I invite you to examine the direct  
| quote above. Note that there's no nearby language calling these  
| examples or saying this is what the SVG viewer should do no matter  
| what mechanism leads it to be handed an absolute IRI reference to an  
| SVG document.

Er... yes, I read the passage the first time you quoted it, which is what I
based my argument on. My reading of it remains pretty much the same. I am
differentiating the source of the inbound link (a UA that handles HTML or
whatever language is hosting XLink) from the target (an SVG UA). The
behavior of the target is being specified, not the source. But the fact that
that statement can be multiply interpreted is probably reason enough to
explicate it in the way you suggest.

Regards-
Doug

doug.schepers@vectoreal.com
www.vectoreal.com ...for scalable solutions.
Received on Tuesday, 3 January 2006 04:47:54 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:33 GMT