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

Re: SVG/profiles/1.1F2/master coords.html,1.16,1.17 intro.html,1.25,1.26

From: Erik Dahlstrom <ed@opera.com>
Date: Mon, 22 Nov 2010 12:49:01 +0100
To: public-svg-wg@w3.org
Message-ID: <op.vmklrxw9geuyw5@localhost>
On Fri, 19 Nov 2010 19:54:25 +0100, Cameron McCormack <cam@mcc.id.au>  
wrote:

> Hi Chris.
>
> Some comments on this change:
>
> Chris Lilley via cvs-syncmail:
>> +  <dd>
>> +    <p>
>> +      The rootmost
>> +      <a href="struct.html#SVGElement"><span  
>> class="element-name">'svg'</span></a>
>> +      element is the furthest
>> +      <a href="struct.html#SVGElement"><span  
>> class="element-name">'svg'</span></a>
>> +      ancestor element that does not exit an
>> +      <a href="intro.html#TermSVGContext"><span class="svg-term">SVG  
>> context</span></a>.
>> +      See also
>> +      <a href="intro.html#TermSVGDocumentFragment"><span  
>> class="svg-term">SVG document fragment</span></a>.
>> +    </p>
>> +  </dd>
>
> Is the definition of “rootmost ‘svg’ element” materially different from
> “outermost ‘svg’ element”, which is already in the spec?  It would be
> good to have only the one definition, if they are not.

I think that they're meant to be the same thing, and yes it would be nice  
to only have one of them. Would take some spec grepping I guess, but it  
shouldn't be too hard to do.

>> Index: coords.html
>> …
>> +<h2 id="IntrinsicSizing">Intrinsic sizing properties of the viewport  
>> of SVG content</h2>
>> +<p>SVG needs to specify how to calculate some intrinsic sizing  
>> properties  to
>> +enable inclusion within other languages. The intrinsic width and height
>> +of the <a href="intro.html#TermViewport"><span  
>> class="svg-term">viewport</span></a> of SVG content must be determined  
>> from the <a href="struct.html#SVGElementWidthAttribute"><span  
>> class="attr-name">'width'</span></a> and <a  
>> href="struct.html#SVGElementHeightAttribute"><span
>> +class="attr-name">'height'</span></a>
>> +    attributes. If either of these are not specified, the
>> +    lacuna value
>> +    of <span class="attr-value">'100%'</span> must
>> + be used. <em>Note:</em> the  <a  
>> href="struct.html#SVGElementWidthAttribute"><span  
>> class="attr-name">'width'</span></a> and <a  
>> href="struct.html#SVGElementHeightAttribute"><span
>
> SVG 1.1 doesn’t have the lacuna value definition.  I think we can just
> do s/lacuna// here.

The SVG 1.1 LC draft does have "lacuna value" defined, see  
http://www.w3.org/TR/SVG11/intro.html#TermLacunaValue.

...
[definition for intrinsic size etc]
...
> SVG 1.1 doesn’t have the ‘none’ value for viewBox.  I think we can just
> delete that parenthetical clause there.

Agreed.

...
>> +<div class="examplesource">
>> +<pre><![CDATA[<svg xmlns="http://www.w3.org/2000/svg" version="1.2"  
>> baseProfile="tiny"
>> +     width="10cm" height="5cm">
>> +  ...
>> +</svg>]]></pre>
>> +</div>
>> +</div>
>
> The styling of these examples doesn’t seem to match those in the rest of
> the 1.1 spec.  Also I don’t think we should be using version="1.2"
> baseProfile="tiny" there.
>
> I can make these changes if you agree.

Yeah, would be good if the examples matched the 1.1 style.

Cheers
/Erik

-- 
Erik Dahlstrom, Core Technology Developer, Opera Software
Co-Chair, W3C SVG Working Group
Personal blog: http://my.opera.com/macdev_ed
Received on Monday, 22 November 2010 11:49:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 22 November 2010 11:49:39 GMT