ISSUE-2050: Consider additional path syntax

path subelements

Consider additional path syntax

State:
RAISED
Product:
SVG 2
Raised by:
Doug Schepers
Opened on:
2008-09-13
Description:
The EXI (Efficient XML Interchange) WG requested that we look at an additional alternative syntax for SVG:

<path stroke="blue" fill="yellow" fill-rule="evenodd">
<moveto x="150" y="150"/>
<lineto x="200" y="100"/>
<horizontal x="250"/>
<vertical y="170"/>
<quadratic x1="350" y1="90" x2="375" y2="150"/>
<smooth x1="400" y1="150"/>
<cubic x1="500" y1="100" x2="575" y2="300" x3="560" y3="150"/>
<smooth x1="650" y1="160" x2="550" y2="300"/>
<z/>
<moveto x="500" y="200"/>
<arc x1="25" y1="35" rotation="-80" large-arc="1" sweep="1" x2="450" y2="220"/
<z/>
</path>

Probably there should also be a @pos="absolute*|relative" for each element, as well, to indicate its positioning.

This was the original proposal from PGML, and the decision to move away from it was for the sake of file sizes and compression:
http://lists.w3.org/Archives/Member/w3c-svg-wg/1999JanMar/0024.html

Interestingly, because EXI is schema-based compression, they believe that this longer syntax would result in small transmission sizes.

It has other benefits as well, such as more discrete animation control, and better compatibility with XSLT.

Note that I'm not talking about getting rid of the old syntax, just adding a new alternative where it would be preferable. The existing shorthand syntax in @d is probably still more broadly applicable, and works well.

Other past conversations:
http://lists.w3.org/Archives/Member/w3c-svg-wg/1999JanMar/0303.html
http://lists.w3.org/Archives/Public/www-svg/2000Mar/0023.html
Related Actions Items:
No related actions
Related emails:
  1. RE: EXI WG's inquiry about ISSUE-2050 (from daniel.peintner.ext@siemens.com on 2012-10-12)
  2. minutes, Rigi-Kaltbad SVG WG F2F 2012 - Day 3 (from cam@mcc.id.au on 2012-09-19)
  3. RE: EXI WG's inquiry about ISSUE-2050 (from tkamiya@us.fujitsu.com on 2012-05-22)
  4. Re: EXI WG's inquiry about ISSUE-2050 (from robin@berjon.com on 2012-05-21)
  5. Re: EXI WG's inquiry about ISSUE-2050 (from liam@w3.org on 2012-05-21)
  6. Re: EXI WG's inquiry about ISSUE-2050 (from robin@berjon.com on 2012-05-21)
  7. RE: EXI WG's inquiry about ISSUE-2050 (from tkamiya@us.fujitsu.com on 2012-05-15)
  8. Re: EXI WG's inquiry about ISSUE-2050 (from robin@berjon.com on 2012-05-10)
  9. RE: EXI WG's inquiry about ISSUE-2050 (from tkamiya@us.fujitsu.com on 2012-05-09)
  10. Re: EXI WG's inquiry about ISSUE-2050 (from chris@w3.org on 2012-04-27)
  11. EXI WG's inquiry about ISSUE-2050 (from tkamiya@us.fujitsu.com on 2012-04-24)
  12. Re: Agenda, Monday 01 June 2009 SVG WG telcon (from cam@mcc.id.au on 2009-06-01)
  13. Agenda, Monday 01 June 2009 SVG WG telcon (from cam@mcc.id.au on 2009-06-01)
  14. Re: Experiment on alternate SVG path syntax for better EXI compression (from chris@w3.org on 2009-05-29)
  15. Experiment on alternate SVG path syntax for better EXI compression (from fujisawa.jun@canon.co.jp on 2009-05-29)
  16. ISSUE-2050 (path subelements): Consider additional path syntax [SVG Core 2.0] (from sysbot+tracker@w3.org on 2008-09-13)

Related notes:

Note that this would also provide the ability to use units for each value, allowing percentages as values, which is a pain point with the existing path syntax.

Doug Schepers, 22 Sep 2008, 18:14:37

Display change log ATOM feed


Dirk Schulze <dschulze@adobe.com>, Chair, Chris Lilley <chris@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 2050.html,v 1.1 2020/01/17 13:19:15 carcone Exp $