W3C home > Mailing lists > Public > wai-xtech@w3.org > February 2003

[XAG] SVG and Final form Re: Comments on XAG - 3 Oct 2002

From: Charles McCathieNevile <charles@sidar.org>
Date: Wed, 26 Feb 2003 12:37:10 +1100
Cc: wai-xtech@w3.org
To: Dean Jackson <dean@w3.org>
Message-Id: <D28FA4EC-492A-11D7-8D8D-000A95678F24@sidar.org>

Personally I don't consider that SVG needs to be final form - it 
provides plenty of capacity through the metadata, title, desc 
attributes for storing original data as well.

The source can be identified (in the example of an SVG that has been 
turned into a stripped-down final form version for bandwidth reduction) 
through the metadata element - I wonder if we should propose a 
particular way of doing this. There is Dublin Core that can identify 
versions of the same resource...

cheers

Chaals

On Wednesday, Feb 19, 2003, at 12:04 Australia/Melbourne, Dean Jackson 
wrote:

> * 2.11 Specific checkpoint for Final-form applications.
> Can you explain what "Allow the author to identify by URI the source 
> used to
> generate the final form instance" means? Does "final-form"
> mean the result of something like an XSLT transform?
> Actually I don't understand the other two provisions as well! Sorry :)
>
> My question really is: "Do you consider SVG final-form?"
> If the answer is yes, then what do the provisions mean in
> the context of SVG?
>
--
Charles McCathieNevile           charles@sidar.org
Fundación SIDAR                       http://www.sidar.org
Received on Wednesday, 26 February 2003 02:22:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 13:15:38 GMT