This is the Disposition of Comments for the 7 December 2005 third Last Call of SVG 1.2. This document lists the comments recieved on the third 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 | 297 |
| Number of agreed comments | 262 |
| Number of comments where no change was requested or made | 74 |
| Number of comments for which a compromise was found | 20 |
| Number of comments disagreed | 38 |
SVGT12-8 SVG12: gzip transfer encoding Responses: Ola Andersson Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Doug Schepers Resolution: The SVG WG believes the commenter misunderstands transfer-encoding. Resolution: This comment appears to be the same as SVGT12-159 and was dealt with there. |
SVGT12-10 SVG12: syncTolerance* schema Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: The schema was corrected to use the defined datatype. |
SVGT12-11 SVG12: charmod note Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Chris Lilley Resolution: Conformance to charmod part 1: Fundamentals is now explicitly required for content and implementations. |
SVGT12-12 SVG12: "animations execute" Responses: Chris Lilley Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Resolution: We agree, and have altered the language to be clearer. |
SVGT12-14 SVG12: formal vs prose Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Resolution: Removing the text would reduce compliance to QA specification guidelines, so we decline to do so. |
SVGT12-18 SVG12: stylesheets not applied Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Resolution: We have removed the erroneous claim. |
SVGT12-19 SVG12: "prop."? Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: We have clarified the draft to implement the commenter's suggestions. (The commenter being extremely unclear as to why he's still unhappy, we couldn't do more the second time around) |
SVGT12-20 SVG12: standard language bindings Responses: Chris Lilley Bjoern Hoehrmann Bjoern Hoehrmann 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 Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Robin Berjon Chris Lilley Resolution: The WG has explained the rules for id and xml:id, and clarified them based on close coordination with XML Core. |
SVGT12-22 SVG12: microsyntaces Responses: Dean Jackson Dean Jackson Bjoern Hoehrmann Andrew Emmons Bjoern Hoehrmann Robin Berjon Resolution: Further issues have been addressed by fixing the spec Resolution: The WG have added the missing definitions Resolution: The WG have added links from the prose as requested but not links to the types. |
SVGT12-24 SVG12: trait access on illegal names Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Jon Ferraiolo Resolution: The WG has changed the spec. |
SVGT12-25 SVG12: normative DOM definitions Responses: Vincent Mahe Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: We updated the IDL as suggested |
SVGT12-32 SVG12: DOM references Responses: Ola Andersson Bjoern Hoehrmann Bjoern Hoehrmann Robin Berjon 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 Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: We decline to group attributes in the format commenter requests. Resolution: The draft has been modified to add the links from the tables to the definitions. |
SVGT12-36 SVG12: IDL namespaces Responses: Robin Berjon Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Nandini Ramani Bjoern Hoehrmann Nandini Ramani Bjoern Hoehrmann Nandini Ramani Resolution: The spec has been updated. |
SVGT12-37 SVG12: Escaping fragment identifiers Responses: Chris Lilley Bjoern Hoehrmann Resolution: We agree that fragments are not used in resolution so never need to be escaped. Resolution: Commentor is not satisfied. |
SVGT12-40 SVG12: <absoluteIRI> etc
Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Resolution: The language has been corrected so that it does not use undefined terms and so that same-document references are distinguished from local IRI references. |
SVGT12-41 SVG12: eRR for invisible content Responses: Robin Berjon Bjoern Hoehrmann Andrew Shellshear 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 Bjoern Hoehrmann Chris Lilley Chris Lilley Bjoern Hoehrmann 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 Bjoern Hoehrmann Resolution: We have updated the spec to address the issues raised by the commenter. |
SVGT12-44 SVG12: <iri> Responses: Chris Lilley Bjoern Hoehrmann Felix Sasaki Bjoern Hoehrmann Chris Lilley Chris Lilley Resolution: The data type <iri> has been replaced with <XMLRI> and <FuncXMLRI> Resolution: We find that RFC 3986 and RFC 3987 were designed to be compatible. |
SVGT12-48 SVG12: DOM-based animation Responses: Chris Lilley Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Andy Sledd Bjoern Hoehrmann Andy Sledd Resolution: We have updated the specification of Timer interface and the createTimer method of the SVGGlobal interface. Resolution: We agree that the example was confusing and have rewritten it to use the timer facility in the uDOM |
SVGT12-51 SVG12: Modularization Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Resolution: Removed modules and put the information previously in modules in the feature string appendix instead. 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 Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: Agree that xml:id should be present. |
SVGT12-55 SVG12: SMIL references Responses: Chris Lilley Chris Lilley Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Chris Lilley Resolution: We agree and have made all SMIL references consistent |
SVGT12-61 SVG12: references mess Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Resolution: We agree, and substantially revised the references section. |
SVGT12-62 SVG12: namespace'd events vs animation
Responses: Dean Jackson Bjoern Hoehrmann Dean Jackson Bjoern Hoehrmann Erik Dahlstrom Bjoern Hoehrmann Andrew Emmons Resolution: Commenter wishes us to change functionality that has been in the spec since SVG Tiny 1.0. Resolution: We have put all events in the interactivity chapter in the null namespace. |
SVGT12-66 SVG12: overlay stacking Responses: Dean Jackson Bjoern Hoehrmann Resolution: Spec has been clarified. |
SVGT12-68 SVG12: editable design Responses: Chris Lilley Bjoern Hoermann Chris Lilley Resolution: We have clarified the spec regarding DOM changes, explainedhow editing expectations are platform-dependent, and described flattening |
SVGT12-69 SVG12: 10.4 grammar Responses: Craig Northway Dean Jackson Bjoern Hoehrmann Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Resolution: We have changed all instances of "XML character data" to "XML content". Resolution: We have corrected the incomplete sentence. |
SVGT12-71 SVG12: editable vs scripting Responses: Robin Berjon Bjoern Hoehrmann Scott Hayman Bjoern Hoehrmann Doug Schepers Resolution: We will consider adding richer examples during CR 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 Doug Schepers Bjoern Hoehrmann Chris Lilley Ola Andersson Resolution: The mentions of an editable attribute now all point to the same definition. |
SVGT12-75 SVG12: system colors Responses: Chris Lilley Bjoern Hoehrmann 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 Bjoern Hoehrmann Scott Hayman Bjoern Hoehrmann Chris Lilley Resolution: Commenter admits the text is correct but continues to disagree. The WG agrees that the text is correct. Resolution: We agree, the wording has been changed to "If these are not specified, the default values of 100% must be used." Resolution: We agree, the wording has been changed to cover all cases" |
SVGT12-82 SVG12: 6.4 example Responses: Dean Jackson Bjoern Hoehrmann Dean Jackson Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: We agree, example has been changed |
SVGT12-85 SVG12: animating xml vs css Responses: Robin Berjon Bjoern Hoehrmann Cyril Concolato Bjoern Hoehrmann Chris Lilley Resolution: Changed and moved the statement about animation of properties into the definition of attributeType. Resolution: The commenter still misunderstands the intent of attributeType |
SVGT12-87 SVG12: Progressive rendering not mandatory?
Responses: Bjoern Hoehrmann Andrew Emmons Bjoern Hoehrmann Resolution: The requirements document has been updated to state that there are optional parts ( progressive rendering is an optional part ). |
SVGT12-90 SVG12: eRR vs timelineBegin Responses: Chris Lilley Bjoern Hoehrmann Andrew Emmons Resolution: Agreed, in the case where the timelineBegin="onLoad", this will also mean that the animation timeline does not begin. Resolution: Agreed. The timeout case has been listed as an example. |
SVGT12-94 SVG12: discard begin Responses: Craig Northway Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Doug Schepers Resolution: The WG believes the issue to be minor and that it is not valuable to change the spec. 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 Bjoern Hoehrmann Bjoern Hoehrmann Resolution: We agree that the term 'nested timeline' was unclear and have explained the timelineBegin attribute without using that term. |
SVGT12-102 SVG12: snapshotTime optional Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann 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 Bjoern Hoehrmann 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 Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Resolution: We agree that standalone="no" has no value, and it has been removed from all examples. |
SVGT12-107 WD-SVGMobile12-20050413: Comments on
examples Responses: Chris Lilley Chris Lilley Dave Hodder Dean Jackson Resolution: We agree, and have changed most examples to use xml:id as recommended for new content. Resolution: We have changed remaining examples to use xml:id as recommended for new content, and fixed other examples as suggested. |
SVGT12-116 SVG12: namespace-illformed fragments Responses: Ian Hickson Robin Berjon Bjoern Hoehrmann Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: The spec has been updated to add some clarification, all references are now dual as requested. |
SVGT12-117 SVG12: data: default type Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Resolution: The definition referenced from the spec is not ambiguous. |
SVGT12-118 SVG12: target, observer, event, ... Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Mark Birbeck Robin Berjon Resolution: We have reverted to using the existing XML Events unmodified. |
SVGT12-120 SVG12: "Animation event names" Responses: Dean Jackson Bjoern Hoehrmann Scott Hayman Bjoern Hoehrmann Doug Schepers Resolution: Commenter wishes to change the animation event value syntax, but we must defer until DOM3 is done and the SMIL Spec addresses namespaced events. Resolution: Changed typo 'repeat' back to 'repeatEvent'. Resolution: The WG has pointed out his misinterpretation, but he disagrees. |
SVGT12-121 SVG12: <handler>, etc. vs
<handler>, etc. Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Scott Hayman Bjoern Hoehrmann Resolution: Commenter wants SVG to adopt the XHTML 2.0 handler element Resolution: We've changed the spec to simply refer to XML Events. Resolution: We have noted the concern and will ensure that coordination is maintained. |
SVGT12-123 SVG12: ev:event vs namespaces Responses: Robin Berjon Bjoern Hoehrmann Jon Ferraiolo Bjoern Hoehrmann Dean Jackson Bjoern Hoehrmann Robin Berjon Resolution: Changed to NMTOKEN. Resolution: We clarified the spec with respect to unqualified event names. |
SVGT12-130 SVG12: overflow initial value Responses: Dean Jackson Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: We updated the specification to remove 'overflow' |
SVGT12-131 SVG12: missing properties Responses: Scott Hayman Bjoern Hoehrmann Scott Hayman Bjoern Hoehrmann Resolution: Omitted due to an error in the program that processed the RNG; now fixed |
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 Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: We agree with the comment and the spec is changed. |
SVGT12-134 SVG12: Vendor-specific presentation
attributes Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Resolution: Vendor-specific presentational attributes are already not allowed. |
SVGT12-137 SVG12: 5.7 example Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Resolution: The example is updated in line with Bjoern's comment. |
SVGT12-143 SVG12: prefetch02.svg Responses: Charles McCathie-Neville Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Resolution: We agree and corrected the example. |
SVGT12-148 SVG12: 5.1.2 "referenced document" Responses: Chris Lilley Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Jon Ferraiolo Ola Andersson Bjoern Hoehrmann Resolution: We agree, have removed the wording about "referenced document" and clarified the spec regarding viewBox. |
SVGT12-150 SVG12: prefetch relationship to SMIL 2.0
Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Chris Lilley Resolution: Changed incorrect ref to local-IRI into non-local-IRI. 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 Jon Ferraiolo Dean Jackson Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Doug Schepers Maciej Stachowiak Jeff Rafter Doug Schepers Bjoern Hoehrmann Bjoern Hoehrman Resolution: The spec has changed to address this comment, and we explained future coordination plans. Resolution: Commenter believes navigation model and future liason commitments to be unsatisfactory, and raises a formal objection. |
SVGT12-153 SVG12: inconsistent/undefined data types
Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Robin Berjon Resolution: Further issues have been resolved 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-156 SVG12: "WQ Framework" Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Resolution: The typo has been corrected. |
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 Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Doug Schepers Resolution: We clarified that it is the message body, not the message. Resolution: Settled after much discussion. Content-Encoding carefully distinguished from gzipped Transfer-Encoding. Resolution: Commentor still disagrees. SVG WG believes the commenter misunderstands transfer-encoding. |
SVGT12-161 SVG12: svg:transform attributes Responses: Antoine Quint Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Resolution: Commenter is not satisfied despite our explanations, existing implementations, and other specifications that depend on this. Resolution: We have defined the attribute in the same style that others are defined, while retaining the syntax and semantics from SVG 1.1. |
SVGT12-163 [SVGMobile12] Conformance criteria Responses: Chris Lilley Ian Hickson Craig Northway Ian Hickson Chris Lilley Ian Hickson Chris Lilley Resolution: The WG has updated the entire specification to ensure properly worded conformance criterias. Resolution: The issue of further improving normativity was retracted after comparison with CSS2.1 spec. |
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 Ian Hickson Nandini Ramani Ian Hickson Scott Hayman Ian Hickson Scott Hayman Scott Hayman Ian Hickson Scott Hayman Ian Hickson Scott Hayman Resolution: The WG has explained the concept of svg error handling. Resolution: Invalid IRIs must be treated as if 'none' were specified. |
SVGT12-188 [SVGMobile12] Comments: Multimedia
Responses: Chris Lilley T Rowley T Rowley Scott Hayman 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 Resolution: The spec now states that the values of the width and height attributes do not affect the rendering of the video element. |
SVGT12-197 [SVGMobile12] Comments: Coordinate
Systems, Transformations and Units Responses: Chris Lilley T Rowley Chris Lilley T Rowley 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-203 [SVGMobile12] 2.1.5: SVG not appropriate for
multi-namespace use Responses: Dean Jackson Boris Zbarsky Bjoern Hoehrmann Chris Lilley Jonathan Watt Ian Hickson Jonathan Watt Ian Hickson 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-205 [SVGMobile12] Comments: The SVG Micro DOM
(uDOM) Responses: Dean Jackson Tim Rowley Robin Berjon T Rowley Resolution: Network API's have a long implementatio history, are in our charter and will therefore still be part of the specification. |
SVGT12-243 SVG12: units for font-size descriptor
Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: The draft has been changed to remove font-size, and the commenter has been notified. |
SVGT12-244 SVG12: 'WheelEvent' "registration"
Responses: Robin Berjon Bjoern Hoehrmann Scott Hayman Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Doug Schepers Doug Schepers Doug Schepers Bjoern Hoehrmann Doug Schepers Resolution: The draft has been modified to implement the commenter's request and a reply has been sent. Resolution: RFC-2119 keywords have been used in lowercase consistently. |
SVGT12-246 SVG12: currentTime definition Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Resolution: We removed some unnecessary text from the spec that might confuse readers and added a definition of document time. |
SVGT12-247 SVG12: A.7.18 ownerDocument attribute Responses: Antoine Quint Bjoern Hoehrmann Nandini Ramani Bjoern Hoehrmann Nandini Ramani Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Resolution: Commenter is not satisfied that the media type is in the process of being registered. Resolution: Examples changed and request to Sun made Resolution: Spec has been changed per Bjoern's suggestion and Antoine sent Bjoern a response. |
SVGT12-249 SVG12: gotoLocation behavior Responses: Ola Andersson Bjoern Hoehrmann Ola Andersson Resolution: We clarified the definition of gotoLocation as requested. |
SVGT12-250 SVG12: A.7.18 example Responses: Antoine Quint Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Resolution: Commenter is not satisfied that the media type is in the process of being registered. Resolution: The example has been fixed to be well-formed Resolution: A request to Sun has been put in to register application/java-archive |
SVGT12-252 SVG12: SVGGlobal vs ELI2 Responses: Robin Berjon Bjoern Hoehrmann Nandini Ramani Maciej Stachowiak Robin Berjon Maciej Stachowiak Dean Jackson Bjoern Hoehrmann Resolution: We have changed the draft so that no object implements the EventListenerInitializer2 interface. |
SVGT12-255 SVG12: xlink:href default value Responses: Robin Berjon Bjoern Hoehrmann Scott Hayman Resolution: The typo has been fixed. 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-261 SVG12: A.4.11 vs lengthComputable
requirements Responses: Robin Berjon Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Resolution: The draft has been changed to clarify that switch processing only affects the rendering tree. 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 Bjoern Hoehrmann Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Resolution: The draft has been changed so that the '/' is now an "and", thereby clarifying the intended meaning. We have also removed the word "bypassed" as it was causing confusion. |
SVGT12-263 SVG12: which elements do requiredFeatures,
etc. apply to? Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann 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, as well as adding to the attributes table. |
SVGT12-264 SVG12: binding-specific discussion in A.2.10
Responses: Robin Berjon Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann 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 Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Jon Ferraiolo Bjoern Hoehrmann Jon Ferraiolo Bjoern Hoehrmann Jon Ferraiolo Bjoern Hoehrmann Boris Zbarsky Jon Ferraiolo Boris Zbarsky Jon Ferraiolo Jim Ley Doug Schepers Bjoern Hoehrmann Doug Schepers Bjoern Hoehrmann Bjoern Hoehrmann Doug Schepers Doug Schepers Resolution: We will reference a new WebAPI spec for this if one comes available and meets our requirements 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 Bjoern Hoehrmann Scott Hayman 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 Bjoern Hoehrmann Jon Ferraiolo 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-269 SVG12: SVGPath::close lacks prose Responses: Antoine Quint Bjoern Hoehrmann Bjoern Hoehrmann Resolution: The draft has been changed to reflect the intended "Appends a 'z' (close path) segment to the path." |
SVGT12-271 SVG12: non-visual foreign markup Responses: Jon Ferraiolo Bjoern Hoehrmann 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/SVGMobile12/feature
strings Responses: Robin Berjon Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Resolution: The draft has been changed so that the feature strings correspond to those listed in the appendix. Resolution: Additional examples were fixed to refer to the correct feature strings. |
SVGT12-273 SVG12: uDOM vs DOMImplementation Responses: Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Robin Berjon Bjoern Hoehrmann Resolution: The choice has been explained but the commenter disagrees. Resolution: All mention of hasFeature has been removed. |
SVGT12-274 SVG12: svg:discard feature string Responses: Dean Jackson Bjoern Hoehrmann Dean Jackson Resolution: Discard feature string was missing. Added as suggested. |
SVGT12-275 SVG12: base IRI for element instances
Responses: Chris Lilley Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Resolution: We did not find the suggestion to remove explanation made the specification easier to follow Resolution: We agree, and have defined base IRI processing in a manner consistent with shadow trees. |
SVGT12-276 SVG12: animateMotion vs transform="" Responses: Robin Berjon Bjoern Hoehrmann Andrew Shellshear Bjoern Hoehrmann Bjoern Hoehrmann Bjoern Hoehrmann Andrew Shellshear Resolution: We added text specifying that animateMotion may be applied to any element that can have a transform attribute. 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 Bjoern Hoehrmann Chris Lilley Chris Lilley Resolution: We explained behaviour of discrete animation to commenter. Resolution: We explained to commenter that paths are normalised before comparison, but not necessarily on getAttributeNS. Resolution: He is correct and the spec has been changed to reflect this. |
SVGT12-278 SVG12: cumulative animation targets
Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Maciej Stachowiak Resolution: Commenter wishes to register a formal objection. Resolution: We explained to commenter that additive is a precondition of cumulative, and added text to that effect, which he now wants us to remove. 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 Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Ola Andersson Bjoern Hoehrmann Resolution: The spec now explicitly says that ref() cannot be animated. Resolution: The group has explained how the new wording is sufficient to resolve ambiguity. The commentor does not discuss this, but raises a formal objection. |
SVGT12-280 SVG12: IDL "int" Responses: Robin Berjon Bjoern Hoehrmann Scott Hayman Bjoern Hoehrmann Resolution: The draft has been changed so as to refer to "long" instead of "int". |
SVGT12-281 SVG12: !important in property animation
Responses: Chris Lilley Bjoern Hoehrmann Andrew Emmons Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Resolution: The way SMIL and SVG define this issue has been explained multiple times to the commenter. |
SVGT12-282 SVG12: animation with indirect values
Responses: Robin Berjon Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Bjoern Hoehrmann Resolution: We agree and have clarified the specification Resolution: The commentor disagrees and raises a formal objection |
SVGT12-283 SVG12: animation of <color>
and <paint>
Responses: Chris Lilley Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann 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 Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Chris Lilley Resolution: Commenter disagrees and reaises a formal objection 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-289 SVG12: transform on <defs>
Responses: Nandini Ramani Bjoern Hoehrmann Andrew Emmons Bjoern Hoehrmann Resolution: transform attribute on 'defs' is now removed. |
SVGT12-290 SVG12: wheelDelta should be UIEvent.detail
Responses: Chris Lilley Bjoern Hoehrmann Bjoern Hoehrmann Scott Hayman Bjoern Hoehrmann Scott Hayman Scott Hayman Bjoern Hoehrmann Scott Hayman Bjoern Hoehrmann Scott Hayman Bjoern Hoehrmann Scott Hayman Resolution: Commenter disagrees and reaises a formal objection Resolution: It was not possible to use UIEvent.detail as it is already used by the event inherited from (MouseEvent). Resolution: There is no issue with readonly attributes as uDOM doesn't support createEvent. |
SVGT12-291 SVG12: conversion to float vs NaN
Responses: Nandini Ramani Bjoern Hoehrmann Nandini Ramani Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Nandini Ramani Bjoern Hoehrmann Nandini Ramani Bjoern Hoehrmann Chris Lilley Bjoern Hoehrmann Doug Schepers Resolution: We have changed the text to represent float as regards IEEE-754 signaling NaN, but have retained exception throwing. |
SVGT12-293 SVG12: illegal non-xlink:href animation
targets Responses: Scott Hayman Bjoern Hoehrmann Scott Hayman Resolution: The spec has been changed to address this comment. |
SVGT12-295 SVG12: 'target' "trait" default value
Responses: Dean Jackson Bjoern Hoehrmann Dean Jackson Bjoern Hoehrmann Resolution: The WG has resolved to change the default value to "_self". |
SVGT12-296 SVG12: getRGBColorTrait vs non-SVGRGBColor
Responses: Ola Andersson Bjoern Hoehrmann Andrew Shellshear Cameron McCormack Chris Lilley |