Re: [Params] 3.7.1 Relevant SVG Referencing Elements

Erik Dahlstrom:
....
>
> > What about mpath? (maybe not)
>
> mpath doesn't embed content, not sure what the gain would be there.

Well, it can use a path from another svg document. 
If this parameter issue is extended in such a way that it can
be used similar to an entity, one could modify a path fragment
with a parameter...

To be able to join together and to reuse path fragments within
different paths or different positions within a path could be
interesting, especially if minor changes can be done with
a parameter or different combinations of different parameters.

It could be one general option to embed the definitions of
entities somehow directly in SVG instead of defining it in the
doctype declaration. Parameters could appear as entities, this
could simplify to use it somewhere within an attribute with an 
arbitrary string as possible value or within the element content 
of text, tspan, textArea, title, desc etc.
This could help to provide the entity feature for SVG in HTML5 as
well and because SVG 1.2 has no doctype declaration 
anymore, it is simpler to explain authors a native SVG method
to define entities as to explain how to add this additional 
doctype tag with quite different syntax to have the feature
still available. 
To note parameters as entities could avoid some parts of
the backward incompatibility problem, at least one can 
provide some fallback values with the old method.


Olaf

Received on Thursday, 18 June 2009 16:46:15 UTC