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

RE: [SVGMobile12] SVGT12-207: <textArea> redundant with HTML

From: Jeff Schiller <codedread@gmail.com>
Date: Tue, 3 Jan 2006 08:18:32 -0600
Message-ID: <da131fde0601030618yedc8928mdd481ab689d4c52c@mail.gmail.com>
To: www-svg@w3.org, doug@schepers.cc

Doug Schepers said:

> As I've stated before, HTML cannot lay claim to rich semantics. There is
> nothing stopping an author from using inline XML semantics (properly
> namespaced) inside a 'textArea', far surpassing any semantic properties HTML
> might have.

Doug, can you point me to your earlier post?

I'm unfamiliar with what you mean by "inline XML semantics".  In
Section 10.1, it states: "For accessibility reasons, it is recommended
that text which is included in a document have appropriate semantic
markup to indicate its function".  Is this what is being referred

Do you mean that something like the following is acceptable :

<svg ... xmnls:html="...">
<textArea ...>
<html:h1>This Is My Title</html:h1>
<html:p>A list of things to fix:</html:p>
<html:li>Item 1</html:li>
<html:li>Item 2</html:li>

What should the behavior of an SVG viewer be for the above?  Does it
strip out the markup for glyph layout purposes so that the character
data within the textArea is effectively

"This Is My TitleA list of things to fix:Item 1Item 2"

Or does it render the content as HTML with appropriate line breaks and
bullet marks - if so, doesn't this behavior need to be specified

Also, the uDOM attribute "textContent" attribute in the Node interface
states that "the returned string does not contain any markup".  Is
there any way to get at the semantic markup from a scripting

Received on Tuesday, 3 January 2006 14:18:35 UTC

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