Re: [SVGMobile12] profiling language OBE? + one editorial...

Al,
This is the SVG WG response to your comment at
(http://lists.w3.org/Archives/Public/www-svg/2005May/0252.html) which is
copied below.

Thanks for your comments.

Regarding your first point, we agree that the wording in section 1.2.3
warrants improvement and have made changes. One thing to point out is
while SVG Tiny 1.2 is indeed a *baseline* definition of SVG, and indeed
there will be other versions (e.g., SVG Full 1.2) which define
extensions off of that baseline, SVG Tiny 1.2 is still a modularized
spec and it is possible to define lesser profiles that Tiny. We have
added clarification language to 1.2.3 which makes this more apparent.
Here is the current text:

-------------------
1.2.3 Profiling the SVG specification

This specification defines the baseline language definition for SVG 1.2.
The specification is defined in terms of a series of modules, each of
which consists of a collection of language features. The modular
definition of the language enables alternate profiles of the SVG
language.

The Tiny profile of SVG 1.2 consists of all of the features defined
within this specification. As a modularized baseline specification, it
is possible for: superset profiles (e.g., SVG Full 1.2) which include
all of the Tiny profile but add other features to the baseline; subset
profiles; and special-purpose profiles which incorporate some modules
from this specification in combination with other features as needed to
meet particular industry requirements.

When applied to conformance, the term "SVG Tiny 1.2" refers to the Tiny
profile of SVG 1.2 defined by this specification. If an implementation
does not implement the Tiny profile completely, the UA's conformance
claims must state either the profile to which it conforms and/or the
specific set of features it implements.
-------------------

Regarding your second point, we agree that there was a missing character
for the Macintosh file type and have fixed the spec.

Please reply to this mail within two weeks if these changes do not
address your concerns.

Thanks

SVG WG

------------------

From: Al Gilman <Alfred.S.Gilman@IEEE.org> 
Date: Fri, 27 May 2005 16:48:37 -0400
Message-Id: <p06110401bebbda09b2ee@[10.0.1.2]> 
To: www-svg@w3.org 

<quote cite=
"http://www.w3.org/TR/SVGMobile12/intro.html#Profiling">

1.2.3 Profiling the SVG specification

The modularization of SVG 1.2 allows profiles to be described by 
listing the SVG modules they allow and possibly a small number of 
restrictions or extensions on the elements provided by those modules.

The "Tiny" profile of SVG 1.2 is the collection of all the modules 
listed in this specification.

When applied to conformance, the term "SVG Tiny" refers to the "Tiny" 
profile of SVG 1.2 defined by this specification. If an 
implementation does not implement the Tiny profile, it must state 
either the profile to which it conforms, or that it implements a 
subset of SVG Tiny.

</quote>

<comment>

Is this discussion perhaps left over from a prior state of the
documents?

I thought that the intention was in this go-around to make the Tiny 
variant a standalone
language, and to express other profiles of SVG 1.2 as extensions 
based on this core.

In addition, I don't feel it was ever technically correct to say that 
the 'Tiny' profile of SVG 1.2
*is* a collection of modules.  It is the language that results when 
these modules are integrated
using a specific composition method.  Consider why there is a driver 
in the RELAX-NG
schema stack.

</comment>

<quote view="source" cite=
"">

<p>It is recommended that SVG files stored on Macintosh HFS
      file systems be given a file type of <code>"svg"</code>
      (all lowercase, with a space character as the fourth letter).
      It is recommended that <a
      href="http://www.ietf.org/rfc/rfc1952.txt">gzip</a>-compressed
      SVG files stored on Macintosh HFS file systems be given a file
      type of <code>"svgz"</code> (all lowercase).</p>

</quote>

<comment class="editorial">

The space character desired in the Mac file indication is missing 
from the specification
text at this point.  See if

<code>"svg  "</code>

won't get the space shown.

<comment>

Al
/self

Received on Wednesday, 2 November 2005 11:52:22 UTC