W3C home > Mailing lists > Public > www-svg@w3.org > July 2010

Re: [SVG1.1F2 LC] mainly previous open issues...

From: Chris Lilley <chris@w3.org>
Date: Mon, 26 Jul 2010 17:03:10 +0200
Message-ID: <112802732.20100726170310@w3.org>
To: www-svg@w3.org
CC: "Dr. Olaf Hoffmann" <Dr.O.Hoffmann@gmx.de>
Hello www-svg,

Dr. Olaf Hoffmann asked

> 17.3.2 SVG fragment identifiers
> Is it ok to have the same  SVGViewAttribute twice in the one view?
> If yes, how is this interpreted?
> http://lists.w3.org/Archives/Public/www-svg/2010May/0026.html

The intention was not to allow the same SVGViewAttribute twice in the one view, no. As you point out, allowing this would not be useful and would be hard to interpret the meaning.

We discussed this, and clarifying directly in the EBNF would make it more verbose as the SVGViewAttributes can occur in any order and we did not want to impose an order, so the EBNF would need to list each possible combination.

We have therefore added an explanatory note after the EBNF stating that each type of SVGViewAttribute can occur at most one time in a given SVG View.

  <p>The five types of <span class="code-fragment">SVGViewAttribute</span> may occur in any order, but each type may only occur at most one time in a correctly formed <span class="code-fragment">SVGViewSpec</span>.</p>

The initial paragraph of section 17.3.2 SVG fragment identifiers states that linking to a view only happens if the fragment identifier is correctly formed. Thus, if a viewer met a fragment which was incorrectly formed (from having multiple of the same type of SVGViewAttribute, or for any other reason) the effect would be that the view was not resolved.

Please let us know if this clarification is responsive to your comment on 17.3.2 SVG fragment identifiers.

 Chris Lilley                    mailto:chris@w3.org
 Technical Director, Interaction Domain
 W3C Graphics Activity Lead
 Co-Chair, W3C Hypertext CG
Received on Monday, 26 July 2010 15:03:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:27 UTC