- From: Karl Dubost <karl@w3.org>
- Date: Thu, 19 May 2005 14:50:38 -0400
- To: www-svg@w3.org
Dear SVG WG, This is a review of SVG Tiny 1.2 http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/ Thank you for this nice piece of work. * Architecture of the World Wide Web and Conformance. [[[ It is believed that this specification is in conformance with the Web Architecture [AWWW]. ]]] - http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/ intro.html#AboutSVG Comment: 1. There's no link to AWWW 2. It's not possible to be conformant to AWWW (for now) [[[ This document does not include conformance provisions for these reasons: … ]]] - http://www.w3.org/TR/2004/REC-webarch-20041215/#about Maybe a better wording would be: "It is believed that this specification is in accordance with the Web Architecture principles as described in AWWW" * Markup of the Specification Comment: We would like to notice that the XHTML markup and the layout style used for this specification is very clean and nice to read. * Backwards compatibility [[[ SVG Tiny 1.2 is a backwards compatible upgrade to SVG Tiny 1.1 . ]]] - http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/ intro.html#defining Comment: How do you define backwards compatibility? In particular, do you address deprecation? obsolete features? Backwards compatibility affects the various classes of products (viewsers/authoring tools/interpreters...). So it would be very important to define all these notions and tied them to each specific class of products. * Reference to XML for DTD subsets [[[ Note that in XML, there is no requirement to fetch the external DTD subset and so relying on an external subset reduces interoperability. ]]] - http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/ intro.html#defining Comment: Maybe you might want to give a link to the part of the XML specification explaining that. Be careful to give a detailed reference: XML 1.0 3rd edition, XML 1.1? * Example entity.svg [[[ <svg xmlns="http://www.w3.org/2000/svg"> ]]] - http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/examples/ entity.svg Comment: In the previous example, you define an SVG 1.2 Tiny document as something starting with: <svg xmlns="http://www.w3.org/2000/svg" version="1.2" baseProfile="tiny" … Is your new example, still an SVG 1.2 Tiny document? * Space character for Macintosh HFS [[[ It is recommended that SVG files stored on Macintosh HFS file systems be given a file type of "svg" (all lowercase, with a space character as the fourth letter). ]]] - http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/ intro.html#mimetype Comment: It might be maybe a bit too much, but does it matter to know which space character, for example giving the Unicode reference of the space character? * Reference from CSS2 [[[ Examples include the 'background-image' and 'list-style-image' properties that are included in both CSS and XSL. ]]] - http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/concepts.html Comment: Does it mean that a "background-image:" in an XHTML document calling an SVG file must be rendered? I know that CSS2 doesn't define the format of images, but I'm not sure if SVG can impose a behaviour of CSS2. Though it seems you define that an XHTML/CSS viewer can also be an SVG viewer if it gives this possibility. * SVG inclusion of different versions. Comment: What should be the behaviour of a User Agent when for example an SVG 1.2 document calls an SVG 1.0 document? * Discard elements http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/ struct.html#DiscardElement Comment: SVG 1.2 Tiny gives the possibility to discard parts of the SVG animation. I can see the benefits of it. I was wondering what's happening when someone links to a discarded part from outside. Does the discard mechanism break the URI-references? * Typo Instanced? [[[ Any 'g' or graphics element is potentially a template object that can be re-used (i.e. "instanced") in the SVG document via a 'use' element. ]]] - http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/ struct.html#UseElement Comment: In my dictionary "to instance" is equivalent to to cite * Media Type for image [[[type = "<media/type>" A hint about the expected Internet Media Type of the raster image. Implementations may choose not to fetch images of formats that they do not support. ]]] - http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/ struct.html#ImageElement Comment: That's good you said it was a hint. It might be good to remind people that HTTP headers have always priority. An SVG viewer MUST NOT ignore the HTTP headers when given. * Common attributes - Typo? [[[ class = list ]]] - http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/ struct.html#Core.attrib Given without double quotes, when the others have quotes. * Styling Properties [[[ SVG shares many of its styling properties with CSS [CSS2] and XSL [XSL]. ]]] - http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/ styling.html#SVGStylingProperties Comment: s/CSS [CSS2]/CSS 2.0 [CSS2]/ what will happen when CSS 2.1 is coming out? It seems the CSS 2.1 Spec is intended to replace the CSS 2.0 specification. Does that mean that the implemeners MUST stick to CSS 2.0 Same kind of comment for XSL. Precise the version. ***General*** Through your whole document, give precise references to the technology. Generic names as HTTP, XSL, CSS, etc. are misleading for the implementers who might understand one particular version of the technology which is the one you had in mind. One of the most common mistakes is XML reference. which version? XML 1.0, XML 1.0 3rd edition, XML 1.1. * Coordinate System Transformation: http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/ coords.html#EstablishingANewUserSpace Comment: Illustrations of matrix transformation. WAI people might argue that the images are not accessible, maybe a link to a mathml file with the equation might be useful. * Events zoom authoring tool? http://w3c.test.site/TR/2005/WD-SVGMobile12-20050413/interact.html SVG 1.1 "SVGZoom" SVG 1.2 {"http://www.w3.org/2001/xml-events", "SVGZoom"} SVG 1.2 {"http://www.w3.org/2001/xml-events", "zoom"} Comment: What an authoring tool should do when loading an SVG 1.1 document and saving it as an SVG 1.2 document? Convert SVGZoom to zoom? * Implementation Requirements http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/implnote.html Comment: You might want to precise what are the classes of products you address in this section. User Agents, bots, authoring tools, etc. C.3.1 Example Comment: Where is the example? D.1 Introduction Comment: Typo "Software that writes SVG (including authoring tools and severs)" -> Servers E. QA ICS http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/qa-ics.html Comment: The QA WG is very grateful to see the inclusion of the ICS in your specification. Without knowing it, you have used an incomplete version of the ICS, which has been republished since. We took the freedom to create a new ICS for SVG Tiny 1.2, you will find it at http://www.w3.org/QA/WG/2005/05/svg-tiny-12-qa-ics Feel free to use it and adapt it to your needs. L. Media Type registration http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/mimereg.html [[[ Person & email address to contact for further information: Dean Jackson, (dean@w3.org). ]]] Comment: In the tradition of IETF, having the address of someone seems the way to go for registering media-type, but I was wondering if a more generic address would be better even if redirected for the time being to Dean's email. Something like "svg-contact at w3.org" -- Karl Dubost - http://www.w3.org/People/karl/ W3C Conformance Manager *** Be Strict To Be Cool ***
Received on Thursday, 19 May 2005 19:18:12 UTC