[SVGMobile12] About vector graphics and other specification

Dear SVG WG :)

The SVG Tiny 1.2 specification contains two types of clauses:
- clauses about vector graphics
- clauses about other domains where some specification is deemed necessary 
by the SVG WG to allow the creation of interoperable applications using 
vector graphics.

Non vector graphics domains in question include (but are not limited to) 
Connection API, mandating gzip encoding, mandating PNG and JPEG image 
decoding and mandating OggVorbis audio decoding.

Whereas I understand that the clauses about non-"vector graphics" items may 
be needed to ensure the interoperability of content within a particular 
application domain, the presence of these items within a single "SVG Tiny 
1.2" profile will hinder the reuse of SVG within other application domains 
where a particular audio or image encoding (or compression, or API) has no 
relevance.

As a result, I would request the definition of 2 separate kinds of profile:
- a vector graphics profile, which could be the current SVGT1.2 profile 
purged of any non vector graphics item (elements and attributes syntax, 
semantics, rendering model and specific APIs)
- an application profile, which could be the current SVGT1.2 profile.

This would broaden the scope of the excellent work done within the SVG WG, 
by defining an interoperability point for the currently envisaged 
applications while allowing later opimal reuse of the purely vector graphics 
part of the specification within other application domains, by other 
industrial fora.

Best regards
JC
-- 
Jean-Claude Dufourd
Founder, Chief Scientist, Streamezzo
83 Bd du Montparnasse
75006 Paris, France Tel:+33 1 53 63 28 47