W3C home > Mailing lists > Public > public-svg-wg@w3.org > October to December 2008

ISSUE-2129 (definition clarifications): Definition section is too long and needs clarifications (bbox, canvas, etc.) [Last Call: SVG 1.2 Tiny ]

From: SVG Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 13 Oct 2008 17:04:46 +0000 (GMT)
To: public-svg-wg@w3.org
Message-Id: <20081013170446.9FE67C6DAE@barney.w3.org>


ISSUE-2129 (definition clarifications): Definition section is too long and needs clarifications (bbox, canvas, etc.) [Last Call: SVG 1.2 Tiny ]

http://www.w3.org/Graphics/SVG/WG/track/issues/2129

Raised by: Doug Schepers
On product: Last Call: SVG 1.2 Tiny 

Cyril Concolato
<http://lists.w3.org/Archives/Public/www-svg/2008Oct/0110.html>:
[[
* Section "1.6 Definition"
Generally, I think the definition of bounding box is too long to be in the definition sections, it makes the definition section hard to grasp.

Additionally, the definition of bounding box explicitely excludes some stroke attributes but not others like stroke-dasharray, join, cap. I suggest adding all stroke attributes.
  
This definition says:
"For curved shapes, the bounding box must enclose all portions of the shape along the edge, not just end points, but must not include control points for curves that are not within the shape itself."
The 'must not' requirement should be changed to a 'should' because depending on the curve and depending on the precision of the implementation (fixed point), it may be impossible to make a bounding box that does not include the control point. 

Could you clarify the meaning of the following sentence especially for the defs element?
"Elements which do not partake in the rendering tree (e.g. elements in a 'defs'  element, elements whose 'display'  is none, etc.), and which have no child elements that partake in the rendering tree (e.g. 'g'  elements with no children), shall not contribute to the bounding box of the parent element, but must return a bounding box for the sake of calculating their own geometry."
What does the bounding box of a defs element 'must return (...) for the sake of calculating [its] own geometry.'?

There are two related definitions: canvas and SVG canvas. Do you really need 2 different definitions? Where in the spec do you use canvas with a different meaning than SVG canvas ? It is not clear how these terms are used in the spec. For example, we find: target canvas, current canvas, intermediate canvas, resulting canvas, background canvas, and temporary video canvas. 

The definition of "graphics referencing element" misses the foreignObject element, no?

]]
Received on Monday, 13 October 2008 17:04:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 13 October 2008 17:04:58 GMT