This is the Disposition of Comments for the 13 April 2005 second Last Call of SVG 1.2. This document lists the comments recieved on the second Last Call specification and the extent to which we believe they have been addressed in the Candidate Recommendation specification.
| Code | Meaning |
|---|---|
| WG Note | Tracking notes, not for publication, needs more discussion |
| Agree | The commentor and the WG agree on the comment, and if necessary the specification has been altered or clarified to bring it into line with what the commentor requested. |
| Discuss | The comment resulted in some discussion, but no change seemed to be asked for and none was made. |
| Compromise | The commentor and the WG compromise on the comment; the WG has explained why they feel the sugested changes woud not be an improvement, or have drawbacks outweighing the gain, or are too hard to implement. |
| Disagree | The commentor and the WG compromise on the comment, the WG have explained their reasoning, and the commentor has stated they are unsatisfied. |
SVGT12-001
[SVGMobile12] prefetch element
We agree, the reference to percentages was not correct and has been removed.For numbers, the units of bandwidth are bytes/second. |
SVGT12-002
[SVGMobile12] Chapter 7
Response: Chris Lilley discussed 19 April |
SVGT12-003 [SVGMobile12] viewport-fill example
We agree, the rendering was wrong and has now been corrected. |
SVGT12-004 [SVGMobile12] Editable text with child elements
We agree, a definition of flattening has been added, with reference to DOM 3. We agree, and have fixed the markup so that numbering works. |
SVGT12-005 WD-SVGMobile12-20050413: Comments on examples
Response: Chris Lilley We agree, and have changed most examples to use xml:id as recommended for new content. Need to get Robin to explain the wierdness about not using 1.2 to identify 1.2 stuff. |
SVGT12-006 SVG12: <color> elements
Response: Chris Lilley We agree, there is now a complete list. |
SVGT12-007 Ill-formed example in 1.3
Response: Chris Lilley We agree, all examples were checked for well formedness |
SVGT12-008 SVG12: standalone declarations
Response: Chris Lilley We agree, and removed the standalone declarations |
SVGT12-009 SVG12: SVG namespace declaration
Response: Chris Lilley Its not clear how to better express this. The commenter was asked to suggest better wording. |
SVGT12-010 SVG12: snapshotTime optional
Response: Chris Lilley It is thumbnail generation which is optional. SVG says nothing about how big a thumbnail should be, whether it is animated, etc. This language feature allows a content author to pick a moment in time which is useful and representative, in the event that the tumbnail of the animation is a single static image. |
SVGT12-011 SVG12: playbackOrder design
Response: Craig Northway The 'all' value indicates that no specific restrictions are placed on document timeline seeking. This is the same behaviour found in SVG 1.1. We agree, the UA should do this if playbackOrder = "forwardOnly". We agree, the specification should clarify that the document can be reloaded regardless of the value for playbackOrder. |
SVGT12-012 SVG12: width and height in 5.1.2 example
Response: Chris Lilley We agree, it should probably say something like "does not have a fixed width and height". |
SVGT12-013 SVG12: <paint> elements
We agree, and have altered the draft to list all relevant items. |
SVGT12-014 SVG12: version attribute
Robin to explain whatever wierdness we agreed to here, see also SVGT12-005 . |
SVGT12-015 SVG12: 'g' id
Response: Chris Lilley We agree, and have changed the draft to refer to the xml:id attribute. |
SVGT12-016 SVG12: discard not mandatory?
Response: Chris Lilley We agree that these should be made consistent. |
SVGT12-017 SVG12: applicability of timelineBegin
Response: Chris lilley We agree, "nested timeline" has been replaced by 'time containers' and a pointer to SMIL 2.0 for the definition and further details. |
SVGT12-018 SVG12: discard begin
Response: Craig Northway We agree, and have added the value "indefinite" to the list of allowed values for the begin attribute, to allow the scripting case you describe in your comment. We agree that a value of "0" is rarely used, but think that the default behaviour provided by the '0' value is more intuitive to the naive user, if a discard element is present in content without a begin value |
SVGT12-019 SVG12: when vs why discard
Response: Chris Lilley Commentor was asked to suggest a suitable rewording of the sentence (or a couple of sentences to replace it) but did not suggest any text. |
SVGT12-020 SVG12: seeking requirements
Responses: Craig Northway, Björn Höhrmann, Craig Northway, Björn Höhrmann, Craig Northway, Björn Höhrmann, Craig Northway We agree, this is now explicitly dissallowed. The UA must not reinsert elements when the document seeks backwards.. We agree, and the definition of "seeking backwards" links to SMIL 2. |
SVGT12-021 SVG12: desc/title "text-only"
Response: Chris Lilley We agree, this is a hold-over from SVG 1.1 where the DTD was unable to express anything more useful. In RNG, and with NVDL, we can do a much better job.. |