OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: What is wrong with SVG?

[ Lists Home | Date Index | Thread Index ]
  • From: David Carlisle <davidc@nag.co.uk>
  • To: xml-dev@XML.ORG
  • Date: Tue, 7 Mar 2000 10:31:29 GMT

Jon Ferraiolo wrote

> In recognition that path data into a single attribute makes DOM access
> difficult, SVG provides a series of convenience DOM methods to access the
> contents of a <path> element on a per-command basis. You can insert, delete
> and replace commands within a <path> element via the convenience DOM methods.

So what might be useful for XSL (since XSL seems to have been mentioned
quite often in this thread) is a specification of some XPath extension
functions for SVG, to break apart an SVG path and produce a node list
more easily accessed by XSLT.

This would amount to having an `expanded' form for the path expressed as
elements from some namespace (it has been suggested to have the whole
path as element content, but that doesn't seem much easier to manipulate
than attribute content) together with an xpath function so


  <path d="M 100 100 L 200 200"/>

<xsl:apply-attributes select="xsvg:path(@d)"/>

would apply XSLT templates to a node tree that looked something like

  <xsvg:M  x="100" y="100"/>
  <xsvg:L  x="200" y="200"/>

where xsvg was some suitably defined namespace.

Also of course you'd want a reverse function that took a node set
(or result tree fragment) built of these nodes and and returned a string
suitable for use as an SVG attribute.


This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS