W3C home > Mailing lists > Public > www-svg@w3.org > April 2006

RE: [SVGMobile12] SVGT12-207: <title> does not define what the title is

From: Jon Ferraiolo <jonf@adobe.com>
Date: Fri, 7 Apr 2006 07:00:51 -0700
Message-ID: <6ECA24BE410D994496A2AE995367C5C89890AD@namail3.corp.adobe.com>
To: "Jim Ley" <jim@jibbering.com>, <www-svg@w3.org>


And keep in mind we are talking about the SVG *Tiny* specification which
is targeting constrained devices. Virtually no one is going to use
anything except plain text for titles. In fact, we should all be
ecstatic if content developers use titles at all.

The plain text case is the one that we should make sure works. One
approach is to say that it is OK for Tiny user agents to just extract
the strings from the text nodes and concatenate them together. If you
put markup within <title>, the author cannot be sure what will happen,
so don't do that if you want it to work interoperably across Tiny UAs.
We can consider more advanced features for <title> in subsequent
versions or more powerful profiles (e.g., Full).

Another option is to ignore all child elements of <title> when rendering
the title. This is consistent with how SVG handles unknown elements for
the main part of the language - unknown elements are not rendered. With
this approach, for <title><html:p>blah</html:p></title>, nothing would
be rendered. I actually prefer this approach. This allows an upgrade
path where a future version of Tiny (or more powerful profile) could
allow <svg:switch> and <svg:foreignObject> within <title> or similar
mechanism, so that you could do something like this:

    <foreignObject requiredExtensions="...">
      <html:html>...rich formatted text goes here </html:html>
    <some-new-tag>backup plain text</some-new-tag>

-----Original Message-----
From: www-svg-request@w3.org [mailto:www-svg-request@w3.org] On Behalf
Of Jim Ley
Sent: Friday, April 07, 2006 3:14 AM
To: www-svg@w3.org
Subject: Re: [SVGMobile12] SVGT12-207: <title> does not define what the
title is

"Maciej Stachowiak" <mjs@apple.com> wrote in message
> "For reasons of accessibility, SVG User Agents should always make the 
> content of the 'title' child element to the 'svg' element available  
> to users (See the User Agent Accessibility Guidelines 1.0 [UAAG]).  
> The mechanism for doing so depends on the SVG User Agent (e.g., as a  
> caption, spoken)."
> So it's pretty poor form that it tells you nothing about what to  
> actually make available. One could imagine dozens of interpretations.

All of which are potentially valid, you should make the content
available, exactly what to do in various situations, with various
content in the title element is down to the user agent, one which
understands RDF would deal differently with one that doesn't in the
situation where the title had an RDF snippet inside it.  This really
gives no value to the user to specify exactly how it should happen, as
this simply prevents browsers who are willing to think what's best for
the user doing it.

The title is metadata, it should be accurate, the author should not be
thinking at all about how it might be rendered, identical rendering is
not a good idea.

Received on Friday, 7 April 2006 14:01:15 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:07 UTC