W3C home > Mailing lists > Public > public-tt@w3.org > December 2008

RE: Test suite is now live

From: Sean Hayes <Sean.Hayes@microsoft.com>
Date: Mon, 8 Dec 2008 16:29:06 +0000
To: "Glenn A. Adams" <gadams@xfsi.com>, Philippe Le Hegaret <plh@w3.org>, Public TTWG List <public-tt@w3.org>
Message-ID: <90EEC9D914694641A8358AA190DACB3D2FCE9A25F5@EA-EXMSG-C334.europe.corp.microsoft.com>

Correct. I misread it as "not in any TT namespace", as used in attributes, rather than "not in TT namespace". My mistake.

However that leads me to wondering whether defining the element using the negative is the right thing to do in case we subsequently define elements an one of the other TT namespaces.

Sean Hayes
Media Accessibility Strategist
Accessibility Business Unit
Microsoft


Office:  +44 118 909 5867,
Mobile: +44 7875 091385


-----Original Message-----
From: Glenn A. Adams [mailto:gadams@xfsi.com]
Sent: 08 December 2008 05:31
To: Sean Hayes; Philippe Le Hegaret; Public TTWG List
Subject: Re: Test suite is now live


Just to be clear, DFXP presently supports both

(1) ttm:* attributes on <tt:metadata>, e.g.

    <tt:p>
      <tt:metadata ttm:role="foo"/>
    </tt:p>

and

(2) ttm:* elements as children of <tt:metadata>, e.g.

    <tt:div xml:id="D0">
      <tt:metadata>
        <ttm:title>TITLE OF DIV D0</ttm:title>
      </tt:metadata>
    </tt:div>

Note that the following variants of the above express the same information
without using <tt:metadata/>.

(1')

    <tt:p ttm:role="foo"/>

(2')

    <tt:div xml:id="D0">
      <ttm:title>TITLE OF DIV D0</ttm:title>
    </tt:div>

On 12/7/08 11:12 PM, "Sean Hayes" <Sean.Hayes@microsoft.com> wrote:

> All the boilerplate metadata contains <descr> not <desc>, and makes the
> metadata mistake I alluded to previously, ttm:* elements are not allowed in
> the <metadata> element.
Received on Monday, 8 December 2008 16:33:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 2 November 2009 22:41:39 GMT