W3C home > Mailing lists > Public > www-svg@w3.org > September 2005

RE: [SVGMobile12] Very unclear processing model for version="", baseProfile=""

From: Scott Hayman <shayman@rim.com>
Date: Tue, 20 Sep 2005 08:39:12 -0400
Message-ID: <F88DB8752C2F644E91BE66DC3ACFF480095C65C0@XCL01YYZ.rim.net>
To: "Ian Hickson" <ian@hixie.ch>, <www-svg@w3.org>

Hi Ian, 

> From: Ian Hickson
> Sent: May 20, 2005 9:34 AM

> Section C.4 Namespace, version, baseProfile, requiredFeatures 
> and requiredExtensions says:
> 
> # If these attributes identify a version, a profile, features 
> or # extensions, and the features are not supported by the 
> user agent # [...]
> 
> However, the specification does not seem to define how a user 
> agent is to establish whether it supports a given version or profile.

We agree that the specification lacks clarity and is in fact
inconsistent in this area. We have changed the last paragraph of C.4 to
read as follows:

	Attributes 'requiredFeatures' and 'requiredExtensions' provide
explicit indication of the minimal features that must be supported by
the UA in order to render the SVG content correctly. Attributes
'version' in conjunction with 'baseProfile' also provide explicit
indication of the minimal features that must be supported. For example,
if 'version' is '1.2' and 'baseProfile' is 'tiny', then these attributes
indicate that the content requires a UA that minimally supports the SVG
Tiny 1.2 specification. If the user agent does not support the minimal
required feature set, then the user agent should alert or otherwise
provide a highly visible notification to the user that it may not be
able to render the content correctly.

	However, 'version' without a specified value for 'baseProfile'
simply indicates to the user agent the specification level (1.0, 1.1,
1.2) to which the content conforms. Without 'baseProfile', the user
agent cannot determine the minimum feature set that is required to
render the content but only knows that the author might be using
language features that were not defined in previous versions of the
language. Therefore, if the content specifies a later version of the SVG
language than what the user agent supports, then the user agent should
alert or otherwise provide a highly visible notification to the user
that it may not be able to render the content correctly.

	If the content specifies SVG language versions, profiles,
features or extensions not supported by the currently installed user
agent, the user agent may notify the user how to update the user agent
should a newer version be available which does support these features.

> For example, nothing in the spec seems to say whether an SVG 
> 1.2 UA should claim to support a document that says 
> version="1.1", or "1.0", or "1.1.0".

We have also added the following sentence to the section on conforming
SVG interpreters [1] to address this specific situation:

	A Conforming SVG Interpreter must be able to parse and process a
conforming SVG Tiny 1.1 document fragment [SVGM11].

Thank you very much for your thorough review, please let us know if this
does not address your concerns.

Scott Hayman
On behalf of the SVG WG

[1]
http://www.w3.org/Graphics/SVG/Group/repository/spec/mobile/1.2/1.2NG/pu
blish/conform.html#ConformingSVGInterpreters



---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Tuesday, 20 September 2005 12:39:18 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:31 GMT