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

Re: Agenda Request: @xlink:href, @href, @src, @data, @target, etc.

From: Francis Hemsher <fhemsher@gmail.com>
Date: Mon, 25 Jan 2010 16:57:07 -0500
Message-ID: <c41bcc9d1001251357o487198fdwc79c1bd0f0fb2376@mail.gmail.com>
To: Doug Schepers <schepers@w3.org>, www-svg@w3.org
Hi Doug,

As an author using SVG, xlink:href has been an irritant to me for
years and years.
That, along with setAttributeNS(null,...) and other namespace clutter
is not needed in probably 99% of applications.

 Those who do require namespaces can easily retro-fit them it into the
document, via SVG 1.2..."Good Practice - Specifications that define
namespaces SHOULD explicitly state their policy with respect to
changes in the names defined in that namespace."

The SVG newbies in the near future will eclipse us oldies by a massive amount.
 If this change were made, I'd gladly go back over previous apps and
update them with href, for their sake. I support any direction that
SVG goes that keeps namespaces "mutable" and nurtures the newbies as
they start their exciting journey into SVG.


On 1/25/10, Doug Schepers <schepers@w3.org> wrote:
> Hi, Folks-
> I'd like to discuss the idea of allowing @src or @href as appropriate
> rather than @xlink:href.  This is prompted by my helping at least one
> SVG newbies recently who anticipated (naturally) that SVG's <script> had
> the same syntax as HTML's; we are going to see more of this, and I'd
> like for implementations to start allowing both, if possible.
> Regards-
> -Doug Schepers
> W3C Team Contact, SVG and WebApps WGs
Received on Monday, 25 January 2010 21:57:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:25 UTC