Re: DTD for techniques documents

Based on the example mostly, here are a few extra comments. (I am not sure ow
much of this Sean has already covered - some I think)

IMHO, elements see-also and applies-to should have compulsory(?) xlink:href
attributes as the primary pointer. This allows the techniques to be
machine-processed easier.

It would be good to define a namespace for groups of users affected, and make
that have an xlink:href attribute too.

I think the content of the description element might as well be HTML, or be
done by using namespaces to include HTML/MathML/whatever. This could be
achieved by modularisation I think...

I don't understand why category is a container element - it seems more likely
that it should be an attribute to me. (please explain?)

Cheers

Chaals

On Tue, 3 Jul 2001, Matt May wrote:

  I've thrown together a DTD for 2.0 techniques. I've attached it here with an
  example of how a WCAG 1.0 HTML technique would be implemented in XML.

  The primary benefits I was looking for in XML were the ability to address
  the requirements of different groups, including implementation teams, and a
  good method of interfacing with other sources of information, such as the
  AERT document and other guidelines documents. I think that using a structure
  somewhat like this could result in more usable and effective techniques
  documents, especially where multiple technologies (such as HTML+CSS+script)
  are involved.

  Comments are encouraged. Thanks.


-- 
Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI    fax: +1 617 258 5999
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)

Received on Thursday, 5 July 2001 10:46:21 UTC