- From: Shelley Powers <shelley.just@gmail.com>
- Date: Mon, 19 Oct 2009 07:08:04 -0500
- To: Anne van Kesteren <annevk@opera.com>
- Cc: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>, Adrian Bateman <adrianba@microsoft.com>, Jonas Sicking <jonas@sicking.cc>, "Tab Atkins Jr." <jackalmage@gmail.com>, Tony Ross <tross@microsoft.com>, "public-html@w3.org" <public-html@w3.org>
On Mon, Oct 19, 2009 at 6:57 AM, Anne van Kesteren <annevk@opera.com> wrote: > On Mon, 19 Oct 2009 13:50:36 +0200, Leif Halvard Silli > <xn--mlform-iua@målform.no> wrote: >> >> Perhaps, as one of the editors of Namespaces in CSS[1], you are also able >> to tell us that namespaces have some advantages? >> >> [1] http://www.w3.org/TR/css3-namespace/ > > I haven't seen a need for @namespace at all really, besides user agent style > sheets and perhaps the somewhat normative style sheets in the HTML5 > specification. As far as I'm concerned CSS would have been much better off > without support for namespaces. (I fixed the specification mostly because it > is a somewhat legacy thing for which it seemed easier to get > interoperability than remove support for it entirely everywhere. In > retrospect this may have been a bad choice, but you have to pick your > battles.) > > > -- > Anne van Kesteren > http://annevankesteren.nl/ > > I have, when I cut and paste an SVG file into one of my sites. Most have Creative Commons licenses recorded using namespaces. Some have other metadata. All are given using namespaces. And I'm sure I'll have other uses in the future, too. I'm no so sanguine about the ability of this group to read the needs of the future, to feel comfortable that we can meet all of these needs when the HTML5 spec is released. Decentralized extensibility is less for current needs, and more for the unknown future. But regardless of future needs, I need it now. Anyone using SVG inline in HTML will need it now. Shelley
Received on Monday, 19 October 2009 12:08:37 UTC