W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2001

Re: DTD for techniques documents

From: Charles McCathieNevile <charles@w3.org>
Date: Thu, 5 Jul 2001 13:57:37 -0400 (EDT)
To: Chris Ridpath <chris.ridpath@utoronto.ca>
cc: Matt May <mcmay@bestkungfu.com>, <w3c-wai-gl@w3.org>
Message-ID: <Pine.LNX.4.30.0107051355220.32701-100000@tux.w3.org>
Maybe makes sense in principle, but not flexible enough in practice. For many
XML languages the content is going to be an element.

So perhaps if you had an XSLT that could look at something and pick a
suspicious fragment we should have a way of linking to it. But maybe that
really just means that we want to link to tools that can be used, which I
think is better done in EARL.

The rule is part of the description, for the most part, and that is primarily
intended for a person to read it at this stage.

chaals

On Wed, 4 Jul 2001, Chris Ridpath wrote:

  The language that describes the rule needs to be precise and I'm wondering
  if it should be marked-up as well.

  The language in your example is "All documents, including individual frames
  in a frameset, should have  a <code>TITLE</code> element that defines in a
  simple phrase the purpose of the document. "

  We need to define things like:
  "all documents" (text files, sound files, stylesheet files, XML, XHTML or
  whatever)
  "simple phrase" (minimum number of characters? NULL OK? all spaces OK?)
  "purpose" (does a title always give the purpose of a document? How can this
  be tested?)
  "should" (under what conditions? must?)

  After we define these, can we mark them?

  Example: We decide that a title can't be NULL, can't be all spaces and
  shouldn't be placeholder text. In our XML techniques document we could
  specify something like:

  <rule>
  <element name="title">
  <canbenull= "no" />
  <canbespace="no" />
  <suspicious="title goes here" />
  <suspicious="title placeholder" />
  </element>
  </rule>

  Make sense?

  Chris
Received on Thursday, 5 July 2001 13:57:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:11 GMT