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 |
---|---|
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. |
Total number of comments | 310 (375) |
Number of agreed comments | 283 |
Number of comments where no change was requested or made | 42 |
Number of comments for which a compromise was found | 46 |
Number of comments disagreed | 4 |
SVGT12-1 Fwd: Two questions on flowed text in 1.2
Responses: Jon Ferraiolo bulia byak Chris Lilley Chris Lilley Jon Ferraiolo bulia byak David Woolley bulia byak Chris Lilley David Woolley Thomas DeWeese bulia byak Thomas DeWeese bulia byak Chris Lilley Resolution: The existing line-increment property affects the line spacing for text in an area. dx, dy and rotate are not available on 'text' or 'tspan' either, in SVG Tiny 1.2, so the spec is consistent. For richer control, see text in an area in SVG 1.2 Full. |
SVGT12-2 ISSUE: getDocumentElement() --> documentElement
Responses: Christophe Jolif Jonathan Watt Resolution: The IDL is correct, and the example cited was Java not ECMAScript so its syntax is correct also. |
SVGT12-3 [SVGMobile12] Editable text with child elements
Responses: Chris Lilley Resolution: We agreed that the term flattening was insufficiently defined, and added a definition drawn from DOM Level 3. |
SVGT12-4 [SVGMobile12] viewport-fill example
Responses: Chris Lilley Resolution: We agree, the rendering was wrong and has now been corrected. |
SVGT12-5 [SVGMobile12] Chapter 7
Responses: Chris Lilley Cameron McCormack Resolution: The text has been clarified, this is indeed the transform-list part of transform, not the whole attribute. Resolution: The indenting has been fixed to improve readability. Resolution: SVG Tiny 1.2 only has one svg element, so the closest svg element is also the root-most one. The square brackets notation was defined, and the definition has been clarified slightly. |
SVGT12-6 [SVGMobile12] prefetch element
Responses: Chris Lilley Resolution: We agree, the reference to percentages was not correct and has been removed. For numbers, the units of bandwidth are bytes/second as with SMIL, and this has been clarified in the spec. |
SVGT12-7 SVG12: sync* trait access
Responses: Ola Anderson Resolution: Trait access is not required for all svg attributes, it is only required for those attributes listed in the trait access table |
SVGT12-8 SVG12: gzip transfer encoding
Responses: Ola Andersson Resolution: This comment appears to be the same as SVGT12-159 and was dealt with there. |
SVGT12-9 SVG12: 'display' trait
Responses: Ola Andersson Boris Zbarsky Bjoern Hoehrmann Ola Andersson Boris Zbarsky Ola Andersson Bjoern Hoehrmann Boris Zbarsky Chris Lilley Bjoern Hoehrmann Jon Ferraiolo Boris Zbarsky Chris Lilley Bjoern Hoehrmann Ian Hickson Jon Ferraiolo Jon Ferraiolo Ian Hickson David Woolley Ola Andersson Jon Ferraiolo Jon Ferraiolo Chris Lilley Jon Ferraiolo Bjoern Hoehrmann Ola Andersson Resolution: We agreed and changed the spec. This comment appears to be the same as SVGT12-267 getTrait vs 'display' property, and was discussed there. |
SVGT12-10 SVG12: syncTolerance* schema
Responses: Robin Berjon Resolution: The schema was corrected to use the defined datatype. |
SVGT12-11 SVG12: charmod note
Responses: Chris Lilley Resolution: Commentor did not supply any reason to remove the note. |
SVGT12-12 SVG12: "animations execute"
Responses: Chris Lilley Resolution: We agree, and have altered the language to be clearer. |
SVGT12-13 SVG12: 'font-face-URI'
Responses: Chris Lilley Resolution: The mis-spelling was corrected. |
SVGT12-14 SVG12: formal vs prose
Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Chris Lilley Resolution: Removing the text would reduce compliance to QA specification guidelines, so we decline to do so. |
SVGT12-15 SVG12: 19.4 example
Responses: Chris Lilley Resolution: The example is now valid to the RNG and NVDL, and does not make wierd use of XHTML |
SVGT12-16 SVG12: contentScriptType default
Responses: Chris Lilley Resolution: The default has been corrected to application/ecmascript. |
SVGT12-17 SVG12: textArea vs xml:space
Responses: bulia byak Robin Berjon Bjoern Hoehrmann Scott Haymann Resolution: The spec has been updated to remove the reference to xml:space |
SVGT12-18 SVG12: stylesheets not applied
Responses: Chris Lilley Resolution: We have removed the erroneous claim. |
SVGT12-19 SVG12: "prop."?
Responses: Robin Berjon Resolution: We have clarified the draft to implement the commenter's suggestions. |
SVGT12-20 SVG12: standard language bindings
Responses: Chris Lilley Resolution: The standard bindings which had been omitted by mistake have been added. |
SVGT12-21 SVG12: A.7.15 id attribute
Responses: Robin Berjon Anne Van Kesteren Robin Berjon Resolution: The WG has explained the rules for id and xml:id. |
SVGT12-22 SVG12: microsyntaces
Responses: Dean Jackson Resolution: The WG have added links from the prose as requested but not links to the types. |
SVGT12-23 SVG12: getPresentation* naming
Responses: Dean Jackson Bjoern Hoehrmann Dean Jackson Ian Hickson Dean Jackson Ian Hickson Bjoern Hoehrmann Bjoern Hoehrmann Resolution: No better alternative name was suggested. |
SVGT12-24 SVG12: trait access on illegal names
Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Resolution: The WG has changed the spec. |
SVGT12-25 SVG12: normative DOM definitions
Responses: Vincent Mahe Resolution: We updated the IDL as suggested |
SVGT12-26 SVG12: onpreload, etc attributes
Responses: Ola Andersson Resolution: The WG agrees with this comment and the spec has been changed in a corresponding way. |
SVGT12-27 SVG12: event name casing
Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Resolution: Names were changed to use the correct case |
SVGT12-28 SVG12: svgudom style
Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Ola Andersson Resolution: Styling has improved but not completely to the level Bjoern ask for. |
SVGT12-29 SVG12: traits in the svg namespace
Responses: Ola Andersson Bjoern Hoerhmann Resolution: We agree and have corrected the use of getTraitNS. |
SVGT12-30 SVG12: language of examples
Responses: Chris Lilley Resolution: We agree and have modified the spec so that examples state what programming language is used. |
SVGT12-31 SVG12: #text traits
Responses: Robin Berjon Bjoern Hoehrmann Jon Ferraiolo Bjoern Hoehrmann Robin Berjon Jon Ferraiolo Bjoern Hoehrmann Robin Berjon Resolution: The WG declines introducing a change that would break compatibility with JSR-226 |
SVGT12-32 SVG12: DOM references
Responses: Ola Andersson Bjoern Hoehrmann Resolution: We agree and have updated references to DOM Level 3 throughout. |
SVGT12-33 SVG12: links to attribute, etc. tables
Responses: Chris Lilley Robin Berjon Cyril Concolato Resolution: The draft has been modified to add the links from the tables to the definitions. |
SVGT12-34 SVG12: typos in A.2.6
Responses: Chris Lilley Resolution: We agree and have fixed the typos. |
SVGT12-35 SVG12: when document begins
Responses: Chris Lilley Resolution: We have clarified the document start to take into account the timelineBegin attribute. |
SVGT12-36 SVG12: IDL namespaces
Responses: Robin Berjon Bjoern Hoehrmann Chris Lilley Resolution: The spec has been updated. |
SVGT12-37 SVG12: Escaping fragment identifiers
Responses: Chris Lilley Resolution: We agree that fragments are not used in resolution so never need to be escaped. |
SVGT12-38 SVG12: IRIs in RFC 2396
Responses: Chris Lilley Resolution: We have corrected the reference, to RFC 3987 |
SVGT12-39 SVG12: 14.1.1 should be table
Responses: Chris Lilley Resolution: We agree, and have reformatted the list as a table. |
SVGT12-40 SVG12: <absoluteIRI> etc
Responses: Chris Lilley Resolution: The language has been corrected so that it does not use undefined terms and so that same-document dreferences are distinguished from local IRI references. |
SVGT12-41 SVG12: eRR for invisible content
Responses: Robin Berjon Resolution: Resolution: Since eRR is a processing requirement whereas not loading invisible media is a permitted optimization, the former naturally takes over. The draft has been clarified to make this more obvious. |
SVGT12-42 SVG12: rendering accuracy
Responses: Jim Ley Chris Lilley Resolution: We agree and have changed the spec from "device pixel" to "px unit" as previously discussed. |
SVGT12-43 SVG12: XML 1.0 vs XML 1.1
Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: The WG believes the spec is clear. |
SVGT12-44 SVG12: <iri>
Responses: Chris Lilley Resolution: We find that RFC 3986 and RFC 3987 were designed to be compatible. |
SVGT12-45 SVG12: SMIL M12N
Responses: Chris Lilley Chris Lilley Resolution: We agree and have removed this wording from the specification. |
SVGT12-46 SVG12: Charmod norm reference
Responses: Chris Lilley Resolution: We agree and now point to the correct charmod specification; we have clarified that this is a guideline,not a conformance requirement. |
SVGT12-47 SVG12: UAAG reference
Responses: Chris Lilley Chris Lilley Resolution: We now require UAAG priority 1 conformance. |
SVGT12-48 SVG12: DOM-based animation
Responses: Chris Lilley Resolution: We agree that the example was confusing and have rewritten it to use the timer facility in the uDOM |
SVGT12-49 SVG12: "object tag"
Responses: Chris Lilley Resolution: The colloquial 'tag' was changed to 'element'. |
SVGT12-50 SVG12: symbolic links
Responses: Ola Andersson Resolution: We have corrected the erroneous links. |
SVGT12-51 SVG12: Modularization
Responses: Ola Andersson Resolution: Updated modules to include missing attributes and elements. Added links from each module to corresponding RNG file and corresponding feature string. Resolution: Left module definitions at end of each chapter, as this is how it has been done in earlier versions of svg. |
SVGT12-52 SVG12: xml:id in core module
Responses: Chris Lilley Chris Lilley Chris Lilley Resolution: Agree that xml:id should be present. |
SVGT12-53 SVG12: xml:lang definition
Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Resolution: The spec has been updated so that xml:lang takes either a token from "3066 or its successor", or the empty string, |
SVGT12-54 SVG12: RFC 3066 reference
Responses: Chris Lilley Bjoern Hoehrmann Addison Phillips Chris Lilley Martin Duerst Chris Lilley Addison Phillips Felix Sasaki Chris Lilley Resolution: We agree and have changed the reference list as recommended by Addison. |
SVGT12-55 SVG12: SMIL references
Responses: Chris Lilley Chris Lilley Resolution: We agree and have made all SMIL references consistent |
SVGT12-56 SVG12: 11.7 sample rendering
Responses: Chris Lilley Resolution: The sample rendering was fixed to be correct.. |
SVGT12-57 SVG12: xml:space description
Responses: Dean Jackson Bjoern Hoehrmann Resolution: We agree, an nbsp had been converted to a space, so it collapsed in the HTML. Now fixed. |
SVGT12-58 SVG12: textArea text-rendering
Responses: Robin Berjon Resolution: We agree, this is fixed in the spec. The schema was already correct. |
SVGT12-59 SVG12: end-of-line handling
Responses: Chris Lilley Resolution: We agree that character references are not normalized, and have corrected the specification by deleting the erroneous sentence |
SVGT12-60 SVG12: app/ecmascript content
Responses: Chris Lilley Robin Berjon Resolution: No further response from Bjoern |
SVGT12-61 SVG12: references mess
Responses: Chris Lilley Resolution: We agree, and substantially revised the references section. |
SVGT12-62 SVG12: namespace'd events vs animation
Responses: Dean Jackson Resolution: The WG believes the spec is clear. |
SVGT12-63 SVG12: form feed
Responses: Chris Lilley Resolution: We agree, have used correct references to Unicode characters per manual of style, and have dropped the erroneous form feed. |
SVGT12-64 SVG12: event namspaceURI
Responses: Ola Andersson Bjoern Hoehrmann Resolution: We agree, and have added the namespaceURI attribute on Event. |
SVGT12-65 SVG12: TransformedVideo feature string
Responses: Ola Andersson Resolution: We have changed the spec to use the correct feature strings |
SVGT12-66 SVG12: overlay stacking
Responses: Dean Jackson Resolution: Spec has been clarified. |
SVGT12-67 SVG12: listen to custom events
Responses: Antoine Quint Resolution: We have changed the draft so that there are no mentions of custom events. |
SVGT12-68 SVG12: editable design
Responses: Chris Lilley Resolution: We have clarified the spec regarding DOM changes, and explainedhow editing expectations are platform-dependent |
SVGT12-69 SVG12: 10.4 grammar
Responses: Craig Northway Dean Jackson Bjoern Hoehrmann Resolution: We have corrected the incomplete sentence. |
SVGT12-70 SVG12: color orange
Responses: Chris Lilley Bjoern Hoehrmann Craig Northway Chris Lilley Resolution: css2.0 does not contain orange. The incorrect references has been updated. |
SVGT12-71 SVG12: editable vs scripting
Responses: Robin Berjon Resolution: We have changed the draft so that events on editable text fields are dispatched as expected. |
SVGT12-72 SVG12: editable definition
Responses: Chris Lilley Resolution: The mentions of an editable attribute now all point to the same definition. |
SVGT12-73 SVG12: textArea schema
Responses: Robin Berjon Resolution: Changed the schema fragment to correctly type the attributes. |
SVGT12-74 SVG12: tBreak sequences
Responses: David Woolley Robin Berjon Bjoern Hoehrmann Chris Lilley Resolution: The effect of multiple consecutive tbreaks is now explicitly described. |
SVGT12-75 SVG12: system colors
Responses: Chris Lilley Resolution: No change - its very clear in the CSS3 draft that the system colors are deprecated. Its very clear in the SVG one that they are not deprecated. They are now described as System Paint, giving CSS 3 the freedom to deprecate them. |
SVGT12-76 SVG12: height/width defaults
Responses: Craig Northway Bjoern Hoehrmann Chris Lilley Ian Hickson Chris Lilley Ian Hickson Craig Northway Resolution: We agree, the wording has been changed to "If these are not specified, the default values of 100% must be used." |
SVGT12-77 SVG12: "outermost" svg element
Responses: Dean Jackson Bjoern Hoehrmann Dean Jackson Bjoern Hoehrmann Andrew Shellshear Resolution: Changed all references to "outermost svg element" to "rootmost svg element", updated definitions. |
SVGT12-78 SVG12: A.2.8 addEventListener
Responses: Ola Andersson Bjoern Hoehrmann Resolution: We agree, addEventListener and addEventListenerNS are both supported |
SVGT12-79 SVG12: A.7.18 style
Responses: Ola Andersson Resolution: We agree, URL is changed from sample.org to example.org |
SVGT12-80 SVG12: 7.2 example
Responses: Ola Andersson Resolution: We agree, URL is changed from sample.org to example.org |
SVGT12-81 SVG12: 7.8 example
Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Resolution: We agree, example has been fixed to conform to svg tiny 1.2 |
SVGT12-82 SVG12: 6.4 example
Responses: Dean Jackson Bjoern Hoehrmann Dean Jackson Resolution: We agree, example has been changed |
SVGT12-83 SVG12: 7.13 example
Responses: Chris Lilley Resolution: We agree, and well-formedness errors in example files are fixed. |
SVGT12-84 SVG12: 6.3 example
Responses: Ola Andersson Resolution: Removed DOCTYPE from the example |
SVGT12-85 SVG12: animating xml vs css
Responses: Robin Berjon Bjoern Hoehrmann Cyril Concolato Resolution: Changed and moved the statement about animation of properties into the definition of attributeType. |
SVGT12-86 SVG12: non-sRGB colors
Responses: Dean Jackson Bjoern Hoehrmann Resolution: Agree, SVG Tiny 1.2 does not allow colours in arbitrary spaces. Spec is updated. |
SVGT12-87 SVG12: Progressive rendering not mandatory?
Responses: Nandini Ramani Craig Northway Resolution: Agreed, User Agent must follow the rules outlined for progressive rendering |
SVGT12-88 SVG12: What is "SAX"?
Responses: Craig Northway Resolution: Agreed, changed the document to define the necessary concepts independant of SAX |
SVGT12-89 SVG12: playbackOrder has no "true" value
Responses: Craig Northway Resolution: Agreed, this has now been fixed in the spec |
SVGT12-90 SVG12: eRR vs timelineBegin
Responses: Chris Lilley Resolution: Agreed, in the case where the timelineBegin="onLoad", this will also mean that the animation timeline does not begin. |
SVGT12-91 SVG12: desc/title "text-only"
Responses: Chris Lilley Dean Jackson Bjoern Hoehrmann Chris Lilley Resolution: Agreed. 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 have done a much better job and the textof the spec now reflects this |
SVGT12-92 SVG12: seeking requirements
Responses: Craig Northway Bjoern Hoehrmann Craig Northway Bjoern Hoehrmann Craig Northway Bjoern Hoehrmann Craig Northway Resolution: Added text clarifying that seeking backwards in the timeline must not re-insert the discarded elements Resolution: The discard element definition will reference the SMIL specification regarding seeking backwards. |
SVGT12-93 SVG12: when vs why discard
Responses: Chris Lilley Craig Northway Ian Hickson Craig Northway Ian Hickson Bjoern Hoehrmann Resolution: Reworded definition of discard criteria to clarify and to have explicit conformance criteria |
SVGT12-94 SVG12: discard begin
Responses: Craig Northway Resolution: added the value "indefinite" to the list of allowed values for the begin attribute Resolution: leave the default value as '0' |
SVGT12-95 SVG12: applicability of timelineBegin
Responses: Chris Lilley Chris Lilley Resolution: We agree that the term 'nested timeline' was unclear and have explained the timelineBegin attribute without using that term. |
SVGT12-96 SVG12: discard not mandatory?
Responses: Chris Lilley Chris Lilley Resolution: The spec has been updated. |
SVGT12-97 SVG12: 'g' id
Responses: Chris Lilley Dean Jackson Dean Jackson Resolution: changed the draft to refer to the xml:id attribute |
SVGT12-98 SVG12: version attribute
Responses: Robin Berjon Resolution: leave the version attribute as-is. |
SVGT12-99 SVG12: <paint> elements
Responses: Dean Jackson Dean Jackson Resolution: Agreed, and changed. Note that viewport-fill does not allow all variations of paint. It can only reference solid colors. |
SVGT12-100 SVG12: width and height in 5.1.2 example
Responses: Chris Lilley Dean Jackson Bjoern Hoehrmann Chris Lilley Resolution: Changed to say "does not have a fixed width and height" and removed width and height attributes |
SVGT12-101 SVG12: playbackOrder design
Responses: Craig Northway Resolution: The WG agrees with one of Bjoern's somments here and explains the reasoning about the others. |
SVGT12-102 SVG12: snapshotTime optional
Responses: Chris Lilley Resolution: 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 thumbnail of the animation is a single static image. |
SVGT12-103 SVG12: SVG namespace declaration
Responses: Chris Lilley Resolution: The SVG spec cannot say anything about elements with a local name of svg in other, non-SVG namespaces. No better wording was proposed. |
SVGT12-104 SVG12: standalone declarations
Responses: Chris Lilley Resolution: We agree that standalone="no" has no value, and it has been removed from all examples. |
SVGT12-105 SVG12: Ill-formed example in 1.3
Responses: Chris Lilley Chris Lilley Resolution: All examples were checked for well-formedness and fixed if necessary |
SVGT12-106 SVG12: <color> elements
Responses: Chris Lilley Dean Jackson Bjoern Hoehrmann Scott Hayman Resolution: We agree, there is now a complete list. |
SVGT12-107 WD-SVGMobile12-20050413: Comments on examples
Responses: Chris Lilley Chris Lilley Resolution: We agree, and have changed most examples to use xml:id as recommended for new content. |
SVGT12-108 interpretation of rotate= attribute
Responses: Chris Lilley Chris Lilley Resolution: Clarification is added. |
SVGT12-109 [SVGMobile12] Well formedness errors in examples
Responses: Chris Lilley Resolution: All examples were checked for well-formedness and fixed if necessary |
SVGT12-110 Implementing DOM 3 event dispatching
Responses: Chris Lilley Resolution: Status of DOM3 events has been explained. |
SVGT12-111 [SVGMobile12] Editorial: Single HTML or PDF file
Responses: jfrost@mbsbooks.com Dean Jackson Jean-Claude Moissinac Paul Cotton Jean-Claude Moissinac Resolution: A single file specification was provided by a third party |
SVGT12-112 SVG Tiny 1.2 should be returned for further work
Responses: Chris Lilley Resolution: A second Last Call will be published |
SVGT12-113 SVG12: Appendix C 1-4
Responses: Robin Berjon Resolution: The identified errors are fixed. |
SVGT12-114 SVG12: "Latest SVG Mobile Recommendation"
Responses: Chris Lilley Resolution: Latest rec indeed points to latest rec. |
SVGT12-115 SVG12: Animation vs Appendix C
Responses: Chris Lilley Resolution: The spec has been edited to remove the questioned paragraph. |
SVGT12-116 SVG12: namespace-illformed fragments
Responses: Ian Hickson Robin Berjon Bjoern Hoehrmann Resolution: The spec has been updated to add some clarification, though the WG has not been thoroughly convinced by the commenter's arguments. |
SVGT12-117 SVG12: data: default type
Responses: Chris Lilley Resolution: The definition referenced from the spec is not ambiguous. |
SVGT12-118 SVG12: target, observer, event, ...
Responses: Chris Lilley Resolution: The spec has been changed to define the missing attributes. The modifications to XMLevents are noted. |
SVGT12-119 SVG12: Informative recommendations
Responses: Andrew Shellshear Resolution: The section in question has been removed. |
SVGT12-120 SVG12: "Animation event names"
Responses: Dean Jackson Resolution: The WG has pointed out his misinterpretation. |
SVGT12-121 SVG12: <handler>, etc. vs <handler>, etc.
Responses: Chris Lilley Resolution: We have noted the concern and will ensure that coordination is maintained. |
SVGT12-122 SVG12: "DTD" and "W3C XML Schema"
Responses: Chris Lilley Resolution: There is no conflict in the specification here. |
SVGT12-123 SVG12: ev:event vs namespaces
Responses: Robin Berjon Bjoern Hoehrmann Jon Ferraiolo Resolution: We clarified the spec with respect to unqualified event names. |
SVGT12-124 SVG12: "timer facilities" in ECMAScript
Responses: Ola Andersson Resolution: The spec has been updated to reflect Bjoern's comment. |
SVGT12-125 SVG12: ProgressEvent::typeArg
Responses: Ola Andersson Bjoern Hoehrmann Resolution: Spec is updated |
SVGT12-126 SVG12: ProgressEvent::progress
Responses: Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Resolution: Example is changed. |
SVGT12-127 SVG12: "event attributes"
Responses: Craig Northway Bjoern Hoehrmann Resolution: Spec is changed. |
SVGT12-128 SVG12: 11.14.1 example
Responses: Ola Andersson Bjoern Hoehrmann Resolution: We agree with the comment and the example is changed. |
SVGT12-129 SVG12: solid-color:currentColor
Responses: Chris Lilley Resolution: We updated the 'applies to' part of the color property |
SVGT12-130 SVG12: overflow initial value
Responses: Dean Jackson Resolution: We updated the specification to remove 'overflow' |
SVGT12-131 SVG12: missing properties
Responses: Scott Hayman Resolution: Omitted due to an error in the program that processed the RNG; now fixed |
SVGT12-132 SVG12: overflow:inherit
Responses: Chris Lilley Resolution: We agree with the comment and the spec is changed. |
SVGT12-133 SVG12: svg in foreignObject
Responses: Chris Lilley David Baron Chris Lilley David Baron Jon Ferraiolo David Baron Chris Lilley Jon Ferraiolo Chris Lilley Jon Ferraiolo Jon Ferraiolo Resolution: We agree with the comment and the spec is changed. |
SVGT12-134 SVG12: Vendor-specific presentation attributes
Responses: Chris Lilley Resolution: Vendor-specific presentational attributes are already not allowed. |
SVGT12-135 SVG12: textArea a text content element?
Responses: Chris Lilley Resolution: We corrected the spec to add textArea |
SVGT12-136 SVG12: RDF Primer reference
Responses: Chris Lilley Resolution: The spec has been changed to refer to the correct RDF specs. |
SVGT12-137 SVG12: 5.7 example
Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Ola Andersson Resolution: The example is updated in line with Bjoern's comment. |
SVGT12-138 SVG12: version="1.2"
Responses: Chris Lilley Resolution: The contradiction was removed in the spec. |
SVGT12-139 SVG12: mediaCharacterEncoding and mediaContentEncodings
Responses: Chris Lilley Resolution: We agree and removed the requirement. |
SVGT12-140 SVG12: prefetch attribute defaults
Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Resolution: Spec is now clearer in the description of prefetch. |
SVGT12-141 SVG12: what is "bandwidth"?
Responses: Chris Lilley Resolution: bandwidth has been defined. |
SVGT12-142 SVG12: mediaContentEncodings
Responses: Chris Lilley Resolution: We agree, and defer to HTTP/1.1 for the allowed values. |
SVGT12-143 SVG12: prefetch02.svg
Responses: Charles McCathie-Neville Resolution: We agree and corrected the example. |
SVGT12-144 SVG12: focus* defaults
Responses: Ola Andersson Bjoern Hoehrmann Resolution: We agree and clarified use of focus defaults. |
SVGT12-145 SVG12: animatable prefetch attributes
Responses: Chris Lilley Resolution: The confusing sentence has been removed. |
SVGT12-146 SVG12: what may prefetch refer to?
Responses: Craig Northway Resolution: The spec has been clarified to state what prefetch can refer to. |
SVGT12-147 SVG12: 16.2.10 example
Responses: Robin Berjon Resolution: The example was wrong and has been changed. |
SVGT12-148 SVG12: 5.1.2 "referenced document"
Responses: Chris Lilley Resolution: We agree, have removed the wording about "referenced document" and clarified the spec regarding viewBox. |
SVGT12-149 SVG12: Navigation behavior
Responses: Craig Northway Chris Lilley Resolution: The spec has been changed to include clearly stated normative statements and some examples. |
SVGT12-150 SVG12: prefetch relationship to SMIL 2.0
Responses: Robin Berjon Resolution: The spec has been changed to describe the differences with SMIL, as requested. |
SVGT12-151 SVG12: nav-* properties
Responses: Ola Andersson Bjoern Hoehrmann Robin Berjon Dean Jackson Dean Jackson Resolution: The spec has changed to address this comment." |
SVGT12-152 SVG12: Cancel events?
Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Vincent Mahe Bjoern Hoehrmann Ola Andersson Vincent Mahe Resolution: The WG agrees with this comment. Methods have been added to allow for event cancellation. |
SVGT12-153 SVG12: inconsistent/undefined data types
Responses: Robin Berjon Resolution: The WG agrees. Data type references are now consistent.Data type names capitalization are consistent and links to data types definitions has been added. |
SVGT12-154 SVG12: Undefined feature strings
Responses: Craig Northway Bjoern Hoehrmann Craig Northway Craig Northway Resolution: Feature strings are now correctly defined. |
SVGT12-155 SVG12: ev:listener
Responses: Craig Northway Cyril Concolato Craig Northway Robin Berjon Craig Northway Cyril Concolato Craig Northway Vincent Mahe Resolution: The WG agrees with Bjoern. The specification has been updated to address his comment. |
SVGT12-156 SVG12: "WQ Framework"
Responses: Chris Lilley Resolution: The typo has been corrected. |
SVGT12-157 SVG12: trait table
Responses: Ola Andersson Resolution: The typo has been corrected. We have decided to keep the table as is. |
SVGT12-158 SVG12: 'focusable' property
Responses: Ola Andersson Bjoern Hoehrmann Resolution: The spec has been updated. Bjoern is happy. |
SVGT12-159 SVG12: Transfer-Encoding
Responses: Chris Lilley Boris Zbarsky Chris Lilley Boris Zbarsky Chris Lilley Yves Lafon Chris Lilley Boris Zbarsky Boris Zbarsky Boris Zbarsky Chris Lilley Chris Lilley Boris Zbarsky Yves Lafon Resolution: Settled after much discussion.Content-Encoding carefully distinguished from gzipped Transfer-Encoding. |
SVGT12-160 SVG12: get/setAttribute
Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Suresh Chitturi Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Ola Andersson Ola Andersson Bjoern Hoehrmann Resolution: The example has been changed. Bjoern is happy. |
SVGT12-161 SVG12: svg:transform attributes
Responses: Antoine Quint Resolution: Typo that will be fixed in the spec |
SVGT12-162 newline handling with xml:space="default"
Responses: Jon Ferraiolo Resolution: An explanation to why the spec is written the way it is has been given. |
SVGT12-163 [SVGMobile12] Conformance criteria
Responses: Chris Lilley Ian Hickson Craig Northway Resolution: The WG has updated the entire specification to ensure properly worded conformance criterias. |
SVGT12-164 Comments on textArea vs flowText
Responses: Doug Schepers David Woolley Doug Schepers Chris Lilley Resolution: The majority of comments were on 1.2 Full, and will be dealt with there; explanations were given for the changes in 1.2 Tiny, which mainly allow re-use of existing line-breaking code. |
SVGT12-165 [SVGMobile12] 5.8.1: interaction of conditional processing and use is unclear
Responses: Jon Ferraiolo Chris Lilley L. David Baron Chris Lilley Resolution: We have made some clarifications to how the rendering tree is defined. Resolution: We quoted parts of the spec to show that other aspects were already well defined. |
SVGT12-166 [SVGMobile12] 5.8.3: disallowed feature strings
Responses: Jon Ferraiolo Robin Berjon Resolution: We have clarified the spec and are also pointing to parts in the spec already addressing this. |
SVGT12-167 [SVGMobile12] 11.10: 'display' definition refers to 'inherit' as a computed value
Responses: Chris Lilley Resolution: The specification has been edited with the proposed sentence. |
SVGT12-168 [SVGMobile12] single document HTML or PDF for review
Responses: Rick Graham Jon Ferraiolo Resolution: We will provide at least a single file PDF. |
SVGT12-169 [SVGMobile12] animation and getAttribute()
Responses: Robin Berjon Antoine Quint Resolution: His question has been answered. No change to the spec is needed. |
SVGT12-170 [SVGT 1.2] Question on sizing of the outermost <svg>
Responses: Jon Ferraiolo Boris Zbarsky Dean Jackson Jon Ferraiolo Boris Zbarsky Chris Lilley Chris Lilley Jon Ferraiolo Resolution: The specification has been fixed according to the request. |
SVGT12-171 [SVGMobile12] Initial viewport sizing, again
Responses: Ian Hickson Jon Ferraiolo Resolution: The issue has been fixed in CSS 2.1. |
SVGT12-172 [SVGMobile12] Review Comments on SVG Tiny 1.2
Responses: Ola Andersson Resolution: The suggested changes have been added to the spec. |
SVGT12-173 [SVGMobile12] Comments: Rendering Model
Responses: Chris Lilley Boris Zbarsky Chris Lilley Boris Zbarsky Resolution: Rendering order changed to use suggested text Resolution: Use of z-order and stacking context was explained Resolution: Spec was altered to describe foreignObject as a replaced element Resolution: We renamed the section title to be clearer |
SVGT12-174 [SVGMobile12] Normative and informative sections
Responses: Boris Zbarsky Chris Lilley Boris Zbarsky Chris Lilley Resolution: We agree, and have clarified the conformance section to indicate which parts of the specification are informative and which normative. |
SVGT12-175 [SVGMobile12] Comments: Document Structure (partial comments)
Responses: Chris Lilley Boris Zbarsky Chris Lilley Resolution: We have added detailed clarifications as suggested. |
SVGT12-176 [SVGMobile12] Yet another request for a single-file version of the specification
Responses: Ian Hickson Jean-Claude Moissinac Dean Jackson Resolution: This will be considered in future drafts. |
SVGT12-177 [SVGMobile12] Comments: Basic Data Types and Color Keywords
Responses: Jon Ferraiolo Boris Zbarsky Jon Ferraiolo Bjoern Hoermann Tim Rowley Dean Jackson Boris Zbarsky Chris Lilley Jon Ferraiolo Boris Zbarsky Chris Lilley Boris Zbarsky Chris Lilley Jon Ferraiolo Boris Zbarsky mental Chris Lilley mental Resolution: The WG agrees and the spec has been updated. |
SVGT12-178 [SVGMobile12] Comments: Concepts
Responses: Chris Lilley Boris Zbarsky Resolution: We have clarified that the chapter is informative, and why we have it.. |
SVGT12-179 [SVGMobile12] Comments: Introduction
Responses: Antoine Quint Boris Zbarsky Antoine Quint Boris Zbarsky Craig Northway Boris Zbarsky Craig Northway Boris Zbarsky Craig Northway Boris Zbarsky Andrew Shellshear Andrew Shellshear Resolution: Updated definition of current SVG document fragment. Resolution: Changed all references to "outermost svg element" to "rootmost svg element", updated definitions. |
SVGT12-180 [SVGMobile12] Comments: Basic Data Types and Color Keywords
Responses: Chris Lilley Resolution: The spec has been updated. |
SVGT12-181 [SVGMobile12] Comments: Concepts
Responses: Tim Rowley Chris Lilley Boris Zbarsky Resolution: The spec has been changed to address some of the comments. Explanation has been provided for the others. |
SVGT12-182 [SVGMobile12] Appendices J and K lack hyperlinks to element/property definitions
Responses: Robin Berjon Resolution: The spec has been updated. |
SVGT12-183 [SVGMobile12] Comment: Please give specific error-handling behaviour
Responses: Doug Schepers Jon Ferraiolo David Woolley Ian Hickson Bjoern Hoehrmann Boris Zbarsky Jon Ferraiolo Boris Zbarsky Ian Hickson Jon Ferraiolo L. David Baron Robin Berjon David Woolley David Woolley Jim Ley Ian Hickson Boris Zbarsky Charles McCathieNevile Resolution: The WG has explained the concept of svg error handling. |
SVGT12-184 [SVGMobile12] QA WG review on your Last Call Document
Responses: Dean Jackson Chris Lilley Chris Lilley Resolution: Glad you like this specification Resolution: Added link to AWWW and suggested language to cite it Resolution: Glad you like the markup we used Resolution: Backward compatibility is now addressed by classes of product Resolution: external DTD subset now links to definition in XML 1.1 Resolution: Entity example was fixed, is 1.2 conformant Resolution: Clarified the space character by U+0020 Resolution: We explained that the conformance requirement is on viewers that implement both SVG and CSS Resolution: We explained what the spec days about versions Resolution: We clarified what the discard element does Resolution: We changed the word to "instantiated" Resolution: Glad you like how we describe the type hint Resolution: typo fixed Resolution: We can't reference CSS 2.1, and explained why. We raised the CSS 2.1 issue with the CSS WG Resolution: We reference specific version of XML,CSS, XSL, and HTTP, as requested Resolution: We added MathML for the equations Resolution: We clarified how to update 1.1T content to 1.2T Resolution: We defined which class of product the implementation requirements were discussing Resolution: We fixed the example which was missing Resolution: We used the new ICS and corrected it to point to our glossary Resolution: We have a better address for medie type comments. |
SVGT12-185 [SVGMobile12] Comments: Extensibility
Responses: Chris Lilley Resolution: The spec has been clarified regarding transformation and compositing of foreignObject. |
SVGT12-186 [SVGMobile12] Comments: Interactivity
Responses: Chris Lilley Resolution: The WG explained why we can't do what he is asking for and how we plan to solve it in the full profile. |
SVGT12-187 [SVGMobile12] Comments: Linking
Responses: Chris Lilley T Rowley Chris Lilley Resolution: We have explained why we have the animation element and the ways in which it differs from the use element. |
SVGT12-188 [SVGMobile12] Comments: Multimedia
Responses: Chris Lilley T Rowley Resolution: We explained the need for constrained video, and that a point is still geometric Resolution: The rationale for the SMIL-compatible animation element was explained Resolution: The error in the example was corrected |
SVGT12-189 [SVGMobile12] 6.2: "SVG Tiny 1.2 does not support CSS selectors"
Responses: Chris Lilley Resolution: The suggested text was added to the specification. |
SVGT12-190 [SVGMobile12] Comments: Painting
Responses: Dean Jackson Resolution: Clarification made to the specification showing how solid-opacity and stop-opacity is independent of fill and stroke opacity, and they are combined using the existing alpha compositing rules. |
SVGT12-191 [SVGMobile12] <handler> element is necessary?
Responses: Dean Jackson Resolution: The WG has explained the purpose of the handler element. |
SVGT12-192 [SVGMobile12] namespace events are not qualified?
Responses: Jon Ferraiolo Craig Northway Craig Northway Mark Birbeck Jon Ferraiolo Mark Birbeck Jon Ferraiolo Bjoern Hoehrmann Mark Birbeck Jon Ferraiolo Mark Birbeck Cameron McCormack MAHE Vincent RD-TECH-REN Mark Birbeck MAHE Vincent RD-TECH-REN Mark Birbeck David Woolley Robin Berjon Resolution: The WG has explained that events are in the xml events namespace and have changed the example in the spec. |
SVGT12-193 [SVGMobile12] focus related methods in SVGSVGElement Interface
Responses: Andrew Shellshear Anne van Kesteren Andrew Shellshear Anne van Kesteren Chris Lilley Anne van Kesteren Chris Lilley L. David Baron Resolution: No action required for SVG Tiny, but may require work in later drafts of SVG Full or in CDI framework. |
SVGT12-194 [SVGMobile12] SVGReseize and SVGScroll events are not namespaced
Responses: Craig Northway Resolution: All unprefixed events are in the xml:events namespace. |
SVGT12-195 [SVGMobile12] Comments: Text
Responses: Craig Northway Chris Lilley Chris Lilley Chris Lilley Resolution: Text behaves the same as other graphical objects. Resolution: We wanted to keep direction independence for text direction Resolution: we added some more examples Resolution: clarified relation to CDF Resolution: explained why text wrapping needs to be implementation dependent for I18N reasons Resolution: yes, creating a scrolling edit box would require clip Resolution: logical cursor position in edited text was described |
SVGT12-196 [SVGMobile12] Comments: Paths
Responses: Nandini Ramani Tim Rowley Nandini Ramani Resolution: The WG has changed the wording for path length. |
SVGT12-197 [SVGMobile12] Comments: Coordinate Systems, Transformations and Units
Responses: Chris Lilley T Rowley Chris Lilley T Rowley Resolution: The possibility of a supplemental user rotation was explained Resolution: We added an explanation of the use case for this feature Resolution: The geographical metadata does not affect rendering, adds semantics and increases interoperabilty for higher-level systems. We clarified that it does not affect rendering |
SVGT12-198 [SVGMobile12] Comments: Styling
Responses: Chris Lilley Resolution: The WG partly agrees with this comment. The spec has been updated, but we did not remove text requested by the XSL group. |
SVGT12-199 [SVGMobile12] Comments: Document Structure
Responses: Robin Berjon Resolution: The specification has been fixed as suggested by the commenter. |
SVGT12-200 [SVGMobile12] processing of errors
Responses: Antoine Quint Resolution: The error section has been updated to reflect this comment. |
SVGT12-201 treatment of non-svg elements in an svg document
Responses: Robin Berjon Jon Ferraiolo Resolution: Amaya has a bug. |
SVGT12-202 [SVGMobile12] About vector graphics and other specification
Responses: Robin Berjon Jean-Claude Dufourd Robin Berjon Craig Northway Jean-Claude Dufourd Jon Ferraiolo Resolution: Topic had been raised previously and was already resolved. Jean-Claude is OK with our decision. |
SVGT12-203 [SVGMobile12] 2.1.5: SVG not appropriate for multi-namespace use
Responses: Dean Jackson Boris Zbarsky Bjoern Hoehrmann Chris Lilley Resolution: The comment does not seem to apply to SVG Tiny 1.2; the comment about font-shorthand ambiguity has been carried forward to Full. |
SVGT12-204 [SVGMobile12] Comments: Implementation Requirements
Responses: Andrew Shellshear Resolution: We have reworded C.2 for clarity. Resolution: The example has been re-added. Resolution: We have reworded section C.5 to more clearly state when clamping occurs. Resolution: We have added wording to C.7 indicating that the visual indication is UA dependant. |
SVGT12-205 [SVGMobile12] Comments: The SVG Micro DOM (uDOM)
Responses: Dean Jackson Tim Rowley Robin Berjon Resolution: Network API's are in our charter and will still be part of the specification. |
SVGT12-206 [SVGMobile12] "'svg' element" and "SVG elements"
Responses: Chris Lilley Resolution: We agree, the spec now has clear definitions of 'svg' and SVG elements. |
SVGT12-207 [SVGMobile12] Too many issues
Responses: Jon Ferraiolo Ian Hickson L. David Baron Jon Ferraiolo Bjoern Hoehrmann Ola Andersson Resolution: The WG is publishing a new LC. |
SVGT12-208 [SVGMobile12] <color> not compatible with CSS2
Responses: Craig Northway Ian Hickson Andrew Shellshear Resolution: We believe the reference to css 2.0 is correct. |
SVGT12-209 [SVGMobile12] <time> can omit unit
Responses: Robin Berjon Resolution: The draft was using the wrong name for a the data type, which is a clock-value and not a time. The draft has been changed to use the right name. |
SVGT12-210 [SVGMobile12] Interaction of rgba() and -opacity="" should be defined
Responses: Dean Jackson Resolution: We have added an explanation of how opacity from external sources is used in painting. |
SVGT12-211 [SVGMobile12] <color> definition
Responses: Chris Lilley Resolution: We have made our own list. |
SVGT12-212 [SVGMobile12] out-of-range values
Responses: Craig Northway Ian Hickson Craig Northway Ian Hickson Chris Lilley Ian Hickson Andrew Shellshear Resolution: The spec has ben updated to address this. |
SVGT12-213 [SVGMobile12] Percentage: line of property definitions
Responses: Andrew Shellshear Resolution: We have changed the spec so that "Percentages" always has the value "N/A" wherever it previously said "no" or "none". |
SVGT12-214 [SVGMobile12] Inconsistent and incorrect requirements for negative values on properties
Responses: Chris Lilley Resolution: time datatype has been removed. Handling of dissalowed negative values now consistent. |
SVGT12-215 [SVGMobile12] Do recognised elements in the wrong place count as an error?
Responses: Andrew Shellshear Resolution: Added specification clarification regarding the scope of local IRI references. |
SVGT12-216 [SVGMobile12] Very unclear processing model for version="", baseProfile=""
Responses: Ian Hickson Scott Hayman Scott Hayman Resolution: The specification has been updated per his comments. |
SVGT12-217 [SVGMobile12] Missing namespace puts document in error
Responses: Andrew Shellshear Ian Hickson Chris Lilley Doug Schepers Chris Lilley Ian Hickson Thomas Deweese Chris Lilley Resolution: We arrived at wording regarding namespace declarations that seemed to satisfy all commentors. |
SVGT12-218 [SVGMobile12] Example in C.3.1 missing, and description incorrect
Responses: Craig Northway Resolution: Spec has been changed. |
SVGT12-219 [SVGMobile12] Error handling is a "SHOULD"?
Responses: Jon Ferraiolo Ian Hickson Ola Andersson Resolution: Partial agreement, resulting in spec change. SVG WG disagreed about requiring particular error handling behavior in UAs. |
SVGT12-220 [SVGMobile12] Inconsistent naming of stroke-dashoffset
Responses: Scott Hayman Resolution: Spec has been changed. |
SVGT12-221 [SVGMobile12] "6.7 Property inheritance"
Responses: Chris Lilley Ian Hickson Chris Lilley Resolution: title has been changed to "Property inheritance and computation Resolution: We have added "Computed Value" to each property. Resolution: We have altered the contents of the Property inheritance and computation section to more clearly explain property inheritance. Resolution: Ian wants to see the changes in context of a complete specification |
SVGT12-222 [SVGMobile12] Stroke processing model missing
Responses: Scott Hayman Ian Hickson Resolution: Stroke write-up and other parts of the spec have been updated to ensure that conformance criteria is correctly specified. |
SVGT12-223 [SVGMobile12] <length> unit
Responses: Chris Lilley Resolution: We have explained how the definition of <length> is useful for later extension in SVG 1.2 Full, as it was inSVG 1.1 Full. |
SVGT12-224 [SVGMobile12] "outermost", "root-most", etc, SVG elements
Responses: Andrew Shellshear Resolution: We have clarified the spec regarding inner-most vs. root-most. |
SVGT12-225 [SVGMobile12] Remove <percentage>
Responses: Chris Lilley Resolution: We agree and have removed this unused type |
SVGT12-226 [SVGMobile12] What is the point of section 3 ("Rendering Model")?
Responses: Chris Lilley Ian Hickson Doug Schepers Ian Hickson Resolution: We have explained what the point of the section is, but Ian wants chapter rewritten around testable assertions. Resolution: We have clarified that painters algorithm uses a pre-order, depth-first tree walk. |
SVGT12-227 [SVGMobile12] Conflicting requirements: version="1.2"
Responses: Chris Lilley Resolution: We agree, and removed the conflict. |
SVGT12-228 [SVGMobile12] Confusing conformance criteria
Responses: Chris Lilley Resolution: We removed the word "should", this is not a conformance statement |
SVGT12-229 [SVGMobile12] Normative statements in mostly non-normative sections
Responses: Chris Lilley Resolution: Sections are now clearly labelled as to normativity |
SVGT12-230 [SVGMobile12] Mark non-normative sections as such
Responses: Chris Lilley Resolution: They are now clearly marked |
SVGT12-231 [SVGMobile12] Conformance section should be at the start of the spec
Responses: Jon Ferraiolo Ian Hickson Resolution: We decided to not move the conformance requirements. Ian accepts our response. |
SVGT12-232 [SVGMobile12] UA requirements vs Author requirements
Responses: Jon Ferraiolo Ian Hickson Chris Lilley Ian Hickson Resolution: We agreed to revise wording for contentScriptType, plus agreement in principle for future editing Resolution: We declined to make every sentence a conformance criterion |
SVGT12-233 [SVGMobile12] last call WD comments (2005.05.20rev2)
Responses: Chris Lilley Resolution: Thanks for the kind words Resolution: Processing of versions, extensions, and subset profiles has been clarified Resolution: The origin of the animation element in SMIL, and the differences between image, animation and use elements, was explained Resolution: Conformance and subsetting was clarified for better clarity. Resolution: The building blocks of new features and their relevance to future evolution of the specification were explained Resolution: We found that a separate attribute did not improve backwards compatibility Resolution: We agree and have altered the syntax to use IRI references rather than IDREF Resolution: We have moved the text selection material to the Implementation Requirements appendix Resolution: The text is already well implemented, but we have clarified which parts are UA behaviour and which relate to conformant content. Resolution: We explained the need for this meatadata, and clarified the spec to indicate that it does not affect rendering. Resolution: Dynamic, data-driven graphics are in scope; we agree that this material will migrate to other specifications in due course. Resolution: The reasons why CSS2 font interoperability problems do not apply to SVG have been explained Resolution: TransformBehavior is not a hint, so is correctly named Resolution: The reference to SAX was removed Resolution: The element names were made consistent with other similar ones Resolution: We carified the spec to show that the precision constraints were a content conformance issue |
SVGT12-234 [SVGMobile12] Comments by the CSS WG
Responses: Dean Jackson Jon Ferraiolo Dean Jackson Resolution: Comments were sent in Feb 2005 and copied to the public list in March. We have therefore, already addressed these. In addition, the comments relate to Full, not to Tiny. |
SVGT12-235 Error in Mobile SVG Profiles
Responses: Chris Lilley Resolution: This was a typo in SVG Mobile 1.1 and will be listed in the errata. |
SVGT12-236 [SVGMobile12] profiling language OBE? + one editorial...
Responses: Jon Ferraiolo Resolution: We have clarified the spec regarding profiling and fixed a typo with the Mac file type. |
SVGT12-237 [SVGMobile12] collected WAI Last Call comments
Responses: Robin Berjon Resolution: Most of the changes requested were implemented, some are being discussed but are not constrained to LC but rather concern separate documents such as authoring guidelines |
SVGT12-238 Events in SVG - chapter 13
Responses: Chris Lilley Resolution: We agree and have added an activate example and better wording regarding events. |
SVGT12-239 SVGT 1.2 Comments
Responses: Scott Hayman Resolution: Some of the comments were addressed with spec clarifications, some of the comments are out of scope for this version of SVG Tiny, some were too specific for a particular application of SVG (e.g., mapping), and others should were more general and would be better addressed in the User Agent Accessibility Guidelines. |
SVGT12-240 SVG12: IRI Processing rules and xlink:href
Responses: Jon Ferraiolo Mark Birbeck Jon Ferraiolo Jon Ferraiolo Bjoern Hoehrmann Jon Ferraiolo Mark Birbeck Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Martin Duerst Bjoern Hoehrmann Andrew Sledd Resolution: We agreed that a spec clarification was necessary, and the clarification has been added. |
SVGT12-241 Questions on SVGTimer
Responses: MAHE Vincent RD-TECH-REN James Bentley MAHE Vincent RD-TECH-REN Chris Lilley Resolution: We fixed an omission pointed out by James. |
SVGT12-242 [SVG12]: EventListenerInitializer2 and ECMA
Responses: Robin Berjon Resolution: The spec has been clarified. |
SVGT12-243 SVG12: units for font-size descriptor
Responses: Robin Berjon Resolution: The draft has been changed to remove font-size, and the commenter has been notified. |
SVGT12-244 SVG12: 'WheelEvent' "registration"
Responses: Robin Berjon Resolution: The draft has been modified to implement the commenter's request and a reply has been sent. |
SVGT12-245 SVG12: display-align initial value
Responses: Andrew Shellshear Resolution: We agree, and have changed the initial value of display-align to auto. |
SVGT12-246 SVG12: currentTime definition
Responses: Ola Andersson Resolution: We removed some unnecessary text from the spec that might confuse readers. |
SVGT12-247 SVG12: A.7.18 ownerDocument attribute
Responses: Antoine Quint Resolution: Spec has been changed per Bjoern's suggestion and Antoine sent Bjoern a response. |
SVGT12-248 SVG12: property traits vs 'inherit'
Responses: Andrew Shellshear Resolution: We agree, and have updated with "inherit" in those entries requiring it in the Trait Setter column |
SVGT12-249 SVG12: gotoLocation behavior
Responses: Ola Andersson Resolution: We clarified the definition of gotoLocation as requested. |
SVGT12-250 SVG12: A.7.18 example
Responses: Antoine Quint Resolution: Spec has been changed per Bjoern's suggestion and Antoine sent Bjoern a response. |
SVGT12-251 SVG12: links to SVG 1.1
Responses: Robin Berjon Resolution: We have modified the draft in order for links to point to specific normative sections of the appropriate specifications. |
SVGT12-252 SVG12: SVGGlobal vs ELI2
Responses: Robin Berjon Resolution: We have changed the draft so that the SVGGlobal implements the EventListenerInitializer2 interface, as had initially been intended but was editorially missed. |
SVGT12-253 SVG12: SVGElementInstance objects as cfos
Responses: Robin Berjon Resolution: The draft has been changed so as to discuss "focus held by any object" instead of only elements as was previously the case. |
SVGT12-254 SVG12: What is a <Paint Server>?
Responses: Robin Berjon Resolution: The draft has been changed so that it is no longer possible to access paint servers through getRGBColorTrait, thereby removing mention of the term, which is defined in section 11. |
SVGT12-255 SVG12: xlink:href default value
Responses: Robin Berjon Resolution: The traits table has been changed so that getTraitNS is used instead of getTrait, as can be expected. The default value is maintained to be the empty string but the excepted return values has been modified to take into account the empty string as a valid value. |
SVGT12-256 SVG12: xlink:href traits
Responses: Robin Berjon Resolution: The draft has been changed so that getTraitNS returns an IRI and not an URI, which is also more consistent with the rest of the specification. |
SVGT12-257 SVG12: 16.3 example vs createSVGMatrixComponents()
Responses: Antoine Quint Resolution: We have changed the example so that the call is made on an SVGSVGElement object instead. |
SVGT12-258 SVG12: move/setFocus event handling
Responses: Robin Berjon Resolution: Dispatched is indeed what was intended. The draft has been changed to reflect that. |
SVGT12-259 SVG12: getTraitNS on non-svg attributes
Responses: Robin Berjon Resolution: The example has been changed to use getAttributeNS instead, as it is much more appropriate for this situation. |
SVGT12-260 SVG12: elements that implement SVGLocatableElement
Responses: Robin Berjon Resolution: We have changed the draft so that all elements which have a location support the appropriate interface. It is not a redundant interface as it avoids having one interface per element (as is the case in the HTML and SVG Full DOMs) which would be extremely costly on constrained devices, in addition to not being extremely useful. |
SVGT12-261 SVG12: A.4.11 vs lengthComputable requirements
Responses: Robin Berjon Resolution: The draft has been updated so as to remove any assumption that lengthComputable would be set to true during the processing of ProgressEvents. |
SVGT12-262 SVG12: 'switch' processing
Responses: Robin Berjon Resolution: The draft has been changed so that the '/' is now an "and", thereby clarifying the intended meaning. |
SVGT12-263 SVG12: which elements do requiredFeatures, etc. apply to?
Responses: Robin Berjon Resolution: The draft has been changed to remove the first bullet containing the non-exhaustive list, as well as to clarify the other bullets, clearly specifying where the test attributes apply. |
SVGT12-264 SVG12: binding-specific discussion in A.2.10
Responses: Robin Berjon Resolution: The draft has been changed to indicate that this section is specific to the Java(tm) platform and has no applicability whatsoever elsewhere. |
SVGT12-265 SVG12: SVGGlobal::document vs AbstractView
Responses: Robin Berjon Resolution: The SVGGlobal::document field is of type Document so as to be compatible with the expected Global::document field since in some languages it is not necessarily possible to subclass a class and change the type of one of its fields. It is expected that casting will be used where necessary. The current specification assumes that forthcoming definitions of the Global interface will not inherit or otherwise implement the AbstractView interface (though they may provide other means of accessing it) so as not to create unnecessary conflicts. |
SVGT12-266 SVG12: attribute/trait "normalization"
Responses: Robin Berjon Resolution: The draft states that "A user agent is allowed to store normalized attribute values internally as described in DOM 3[0]". This entails that implementations are indeed allowed to store values in the way most optimal to them and setting an attribute and getting its value back immediately may not produce the same value that was used when setting. This will apply not only to SVG Full 1.2 but in fact to any implementation of DOM Level 3 Core. Consequently, we have not changed the draft. |
SVGT12-267 SVG12: getTrait vs 'display' property
Responses: Chris Lilley Resolution: We have changed the draft such that the computed value of the display property, on the one hand, and the value returned by getTrait on the display property are clearly distinguished. Resolution: We have modified the draft to add extensive clarification in order to make sure that implementers will not be able to miss a single detail, as you required. The specification now details the differences between the trait accessors which for backward compatibility reasons can only access normalised values, and the attribute accessors which may provide access to the original value. |
SVGT12-268 SVG12: trait <> attribute discrepancies
Responses: Robin Berjon Resolution: Each entry in the table has been checked and modified where applicable to link to the correct entry in the appendix tables of properties and attributes, thereby removing confusion. Regarding getTrait("font-family"), the draft has been modified so as to have it return a comma-separated list of font families in the computed font-family value in such a way that is compatible with the CSS syntax for that property. |
SVGT12-269 SVG12: SVGPath::close lacks prose
Responses: Antoine Quint Resolution: The draft has been changed to reflect the intended "Appends a 'z' (close path) segment to the path." |
SVGT12-270 SVG12: vector-effect default value
Responses: Robin Berjon Resolution: The draft has been changed from "default" to "none", which is the genuine default value. |
SVGT12-271 SVG12: non-visual foreign markup
Responses: Jon Ferraiolo Resolution: The WG has explained that requiring foreignObject to have a geometric size to operate even when used for non-visual content is not an issue. This is further supported by the fact that non-visual content can be used outside of foreignObject, either with foreign namespaces or with facilities such as the 'audio' element. |
SVGT12-272 SVG12: http://www.w3.org/TR/SVG12/feature strings
Responses: Robin Berjon Resolution: The draft has been changed so that the feature strings correspond to those listed in the appendix. |
SVGT12-273 SVG12: uDOM vs DOMImplementation
Responses: Robin Berjon Resolution: The DOMImplementation interface had unintentionally been omitted from this draft, and has been added. |
SVGT12-274 SVG12: svg:discard feature string
Responses: Dean Jackson Resolution: Discard feature string was missing. Added as suggested. |
SVGT12-275 SVG12: base IRI for element instances
Responses: Chris Lilley Resolution: We agree, and have defined base IRI processing in a manner consistent with shadow trees in sXBL. |
SVGT12-276 SVG12: animateMotion vs transform=""
Responses: Robin Berjon Resolution: The absence of the 'transform' attribute on 'animation' was an oversight in the schema which has been corrected, and 'textPath' has been added to the list of supported elements. Note however that supporting the 'transform' attribute and being a target for 'animateMotion' are orthogonal features. |
SVGT12-277 SVG12: animation of path data
Responses: Nandini Ramani Resolution: He is correct and the spec has been changed to reflect this. |
SVGT12-278 SVG12: cumulative animation targets
Responses: Chris Lilley Resolution: We have checked that additive and accumulate link to the correct definitions in SMIL 2.0 |
SVGT12-279 SVG12: animating transform ref()
Responses: Ola Andersson Resolution: The spec now explicitly says that ref() cannot be animated. |
SVGT12-280 SVG12: IDL "int"
Responses: Robin Berjon Resolution: The draft has been changed so as to refer to "unsigned long" instead of "int". |
SVGT12-281 SVG12: !important in property animation
Responses: Chris Lilley Resolution: A CSS declaration cannot be a 'from' or 'to' value, which only takes property values when attributeType is CSS. |
SVGT12-282 SVG12: animation with indirect values
Responses: Robin Berjon Resolution: We agree and have clarified the specification |
SVGT12-283 SVG12: animation of <color> and <paint>
Responses: Chris Lilley Resolution: We agree and have clarified the specification regarding keywords which give animatable values, such as colors. |
SVGT12-284 SVG12: feature strings vs "supports"
Responses: Chris Lilley Resolution: color-rendering was indeed missing from the Paint Attributes module; we added it Resolution: We do not see the more general point regarding ambiguity, and quoted the spec to demonstrate this. |
SVGT12-285 SVG12: addEventListenerNS vs DOM Level 3
Responses: Ola Andersson Resolution: We've now changed addEventListener to comply with DOM Level 3 and examples are updated. |
SVGT12-286 SVG12: A.7.18 example vs useCapture
Responses: Ola Andersson Resolution: The spec is changed to address this comment. |
SVGT12-287 SVG12: "Paced animation and complex types" misplaced
Responses: Ola Andersson Resolution: The spec is changed to address this comment. |
SVGT12-288 SVG12: normative reference to JSR 226
Responses: Ola Andersson Resolution: The spec is changed to address this comment. |
SVGT12-289 SVG12: transform on <defs>
Responses: Nandini Ramani Resolution: transform attribute on 'defs' is now removed. |
SVGT12-290 SVG12: wheelDelta should be UIEvent.detail
Responses: Chris Lilley Resolution: The WG has explained the rationale for wheelDelta and Bjoern has not complained. |
SVGT12-291 SVG12: conversion to float vs NaN
Responses: Nandini Ramani Resolution: The WG has explained the rationale here. |
SVGT12-292 SVG12: eRR on font-face-uri
Responses: Chris Lilley Resolution: The WG added eRR on font-face-uri. |
SVGT12-293 SVG12: illegal non-xlink:href animation targets
Responses: Scott Hayman Resolution: The spec has been changed to address this comment. |
SVGT12-294 SVG12: trait access vs "an error"
Responses: Scott Hayman Bjoern Hoehrmann Scott Hayman Scott Hayman Scott Hayman Resolution: The spec has been changed to address this comment. |
SVGT12-295 SVG12: 'target' "trait" default value
Responses: Dean Jackson Resolution: The WG has resolved to change the default value to "_self". |
SVGT12-296 SVG12: getRGBColorTrait vs non-SVGRGBColor
Responses: Ola Andersson Resolution: The spec has been changed to address this comment. |
SVGT12-297 SVG12: getPresentation* optional?
Responses: Ola Andersson Resolution: The spec has been changed to address this comment. |
SVGT12-298 SVG12: gotoLocation "URLs"
Responses: Chris Lilley Ola Andersson Resolution: The spec has been changed to address this comment. |
SVGT12-299 SVG12: cfo definition
Responses: Ola Andersson Resolution: The spec has been changed in line with his comment. |
SVGT12-300 SVG12: cfo when there is no cfo
Responses: Ola Andersson Resolution: The spec has been changed in line with his comment. |
SVGT12-301 SVG12: getCurrentFocusedObject return type
Responses: Andrew Shellshear Resolution: The spec has been changed to address this comment. |
SVGT12-302 SVG12: DOMObject portability
Responses: Andrew Shellshear Boris Zbarsky Ola Andersson Resolution: The WG have explained why focus methods work on DOMObjects. |
SVGT12-303 SVG12: currentTime vs SVG 1.1
Responses: Robin Berjon Resolution: Contrary to what the commenter stated, this does not introduce an incompatibility, and was modified to support lighter-weight implementations of the same feature. The WG therefore declined to effect any change. |
SVGT12-304 SVG12: Document.documentElement definition
Responses: Robin Berjon Resolution: The draft has been modified to fix the grammar and provide a more orthodox definition. |
SVGT12-305 SVG12: DOM3 textNode
Responses: Robin Berjon Resolution: The draft has been changed to say "textContent" (which is what was pointed to by the link) instead of the incorrect "textNode". |
SVGT12-306 SVG12: non-DOM DOMString
Responses: Robin Berjon Resolution: The draft has been changed to remove the unfortunate typedef aliasing DOMString to string. |
SVGT12-307 SVG12: setAttributeNS exceptions
Responses: Antoine Quint Resolution: The suggested fixes have been applied, namely to add the NOT_SUPPORTED_ERR, NO_MODIFICATION_ALLOWED_ERR, INVALID_CHARACTER_ERR and NAMESPACE_ERR exceptions to the definition of Element::setAttributeNS() to the uDOM. |
SVGT12-308 SVG12: createElementNS exceptions
Responses: Antoine Quint Resolution: The suggested fixes have been applied, namely to add the INVALID_CHARACTER_ERR and NAMESPACE_ERR exceptions to the definition of Document::createElementNS() to the uDOM. |
SVGT12-309 SVG12: addEventListenerNS exceptions
Responses: Antoine Quint Resolution: IDL and written definitions for the EventTarget methods are now in sync. |
SVGT12-310 Should there also be an attribute indicating whether a text is "selectable"?
Responses: Antoine Quint Resolution: The spec already offers a way to disable text selection following a given mouse event. |