W3C home > Mailing lists > Public > www-svg@w3.org > June 2003

Re: SVG 1.2 meta feedback

From: Robin Berjon <robin.berjon@expway.fr>
Date: Wed, 04 Jun 2003 11:46:13 +0200
Message-ID: <3EDDBFE5.20500@expway.fr>
To: Jim Ley <jim@jibbering.com>
Cc: www-svg@w3.org

Jim Ley wrote:
> "Dean Jackson" <dean@w3.org>
>>Yeah, but then we have to include the svg:, right?
> In:
> <xs:element name="flowLayout">
>   <xs:complexType>
>     <xs:sequence>
>       <xs:element ref="flowRegion" minOccurs="0" maxOccurs="unbounded"/>
>     </xs:sequence>
>   </xs:complexType>
> </xs:element>
> There'd be no svg namespaced portions I believe?

If the default namespace were XML Schema's, you'd need to have 
ref='svg:flowRegion'. But otherwise I agree with you.

>>The WWW2003 attendees saw it on screen, but it is not in the
>>online version. Also, you needed a unnamed, unreleased SVG viewer
>>to display the resulting SVG.
> However some interested individual could implement it in javascript...  I've
> been adding a templating feature to foafnaut recently, and that could've
> much more sensibly done with RAX (so foafnaut updates some XML, and it's
> transformed to svg depending on seperately specified docs) I didn't use RAX,
> because I have no idea what it looks like, and instead had to develop my own
> templating system in js, a RAX implementation in js could've been much more
> sensible.

You can implement the declarative syntax in es, it's been done. However what 
you'd miss would be the shadow tree, which is a really convenient way of not 
destructively manipulating a DOM.

Robin Berjon <robin.berjon@expway.fr>
Research Engineer, Expway        http://expway.fr/
7FC0 6F5F D864 EFB8 08CE  8E74 58E6 D5DB 4889 2488
Received on Wednesday, 4 June 2003 05:46:23 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:46:56 UTC