W3C home > Mailing lists > Public > www-svg@w3.org > August 2002

RE: proposal for this link/tspan discussion

From: Ronan Oger <ronan@roasp.com>
Date: Tue, 20 Aug 2002 13:59:21 +0200
To: <www-svg@w3.org>
Message-ID: <EMENJCDHGFFGOCDJOBLMIEAIDPAA.ronan@roasp.com>

Pardon my simple mind and lack of vision, but is xlink:xref not more
generally used to mean 'go to that place, get something, and use it here',
or more succinctly  'this is an inbound link'?

This is quite a bit different from the <a> tag which means 'this is an
outbound link'.

I will take it for granted that there are valid reasons to hate the <a tag.
But personally, I like it and have no problems with its existance. It makes
me feel all warm and fuzzy to know that this <a> will take me to some other,
wonderful place.

It's also nice in rendering terms to know that you are about to render
something that behaves like an anchor tag before you get to the content.
Makes my life a whole lot easier with the yasb browser design.

Foolishly,

Ronan

>-----Original Message-----
>From: www-svg-request@w3.org [mailto:www-svg-request@w3.org]On Behalf Of
>Jim Ley
>Sent: Tuesday, August 20, 2002 1:10 PM
>To: www-svg@w3.org
>Subject: Re: proposal for this link/tspan discussion
>
>
>
>
>"Dean Jackson" <dean@w3.org> wrote in message
>news:20020820012308.GA18200@grorg.org...
>
>> Why can't every element be a link? We allow an xlink:href
>> on every element (I think this was one of the goals of xlink).
>
>I agree it was, my concern with "any element" approach though is that
>there are certain elements which should take a link to an external
>resource with different semantics to the link in this sense, namely the
>desc, metadata, foriegnObject elements (*) - desc I've requested before
>the advantage of being able to link to an external resource describing
>something, and there's the same issue with metadata.  These would clearly
>be links to external resources (rather than the elements Dean lists which
>currently use xlink:href for replaced content.) but they carry more
>semantics than a normal a link.
>
>> I'd like to see those attributes replaced with "ref".
>
>XAG says use XLINK because it means XML applications without specific
>namespace awareness can recognise that it is a link.  I'm undecided if
>it's a good thing that these applications will no longer be able to know
>that <image ref="somedocument.svg">  refers to another svg document or
>not.
>
>Jim.
>
>* Is there some convention for writing elements, I don't like saying
><desc> element, as that's a tag, not an element, I capitalise in HTML,
>but as we're case sensitive that's a problem...
>
>
>
>
>
>
Received on Tuesday, 20 August 2002 08:03:54 GMT

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