W3C home > Mailing lists > Public > w3c-wai-er-ig@w3.org > October 2000

RE: Evaluation Results In XML - SSB Technologies Thoughts

From: Timothy Stephen Springer <timsp@ssbtechnologies.com>
Date: Fri, 27 Oct 2000 10:04:39 -0700
To: "Leonard R. Kasday" <kasday@acm.org>
Cc: <w3c-wai-er-ig@w3.org>
Message-ID: <NDBBJIMIALKAIHGBAMLKMEAFCEAA.timsp@ssbtechnologies.com>
Leonard -
	I have inlined the two documents (see below).  This should be a LCD (Lowest
Common Denominator) for transmission.  If you would like the originals I
have put them up at the following URLS:
	http://www.ssbtechnologies.com/software/ssb_report.txt
	http://www.ssbtechnologies.com/software/ssb_report_proposed.txt
The mime type will be set to text however IE will render them as XML.

Hope that helps!

----Proposed XML----
<?xml version="1.0" encoding="UTF-8"?>
<!-- PI if we want to define a DTD / schema for verification -->
<PAGE url="http://www.yahoo.com">
  <VIOLATIONS priority="1" total="opitional">
    <VIOLATION key="foo" total="opitional">
      <ELEMENT line="optional">
		 <!-- XHTML opening tag for element -->
	     <IMG src="here" alt="Wretched Alt" />
      </ELEMENT>
    </VIOLATION>
</VIOLATIONS>
</PAGE>
----End Proposed XML----


----Current SSB Output----
<?xml version="1.0" encoding="UTF-8"?>
<PAGE url="http://www.yahoo.com">
  <VIOLATIONS priority="1">
    <VIOLATION>
      <SHORT_DESCRIPTION>This AREA has no alt attribute</SHORT_DESCRIPTION>
      <LONG_DESCRIPTION>AREAs in image maps need to have an alt attribute
briefly describing what the AREA points to.</LONG_DESCRIPTION>
      <LINE>1</LINE>
      <LINE>1</LINE>
      <LINE>1</LINE>
      <LINE>1</LINE>
      <LINE>1</LINE>
      <LINE>1</LINE>
    </VIOLATION>
</VIOLATIONS>
</PAGE>
----End SSB Output----




-----Original Message-----
From: w3c-wai-er-ig-request@w3.org
[mailto:w3c-wai-er-ig-request@w3.org]On Behalf Of Leonard R. Kasday
Sent: Friday, October 27, 2000 8:39 AM
To: w3c-wai-er-ig@w3.org
Subject: Re: Evaluation Results In XML - SSB Technologies Thoughts


Tim,

Thanks much for your proposal!  Here's  couple of intitial reactions



Very good point about difficulty of "repair" when the content is generated
programmatically.

As far as your note that combining the violations with the source creates
problems of re-ordering, because of lack of functionality with XSLT and
XPATH.  Could that be handled with a separate filter (e.g. Perl using
XML::Parser)?

There's the other method of pointing into the source with XPATH, like Al
mentioned.   Would these be semantically equivalent, e.g. you could convert
form one into another?  Or are there some fundamental differences in
capabilities from those schemes?

Len
--
Leonard R. Kasday, Ph.D.
Institute on Disabilities/UAP and Dept. of Electrical Engineering at Temple
University
(215) 204-2247 (voice)                 (800) 750-7428 (TTY)
http://astro.temple.edu/~kasday         mailto:kasday@acm.org

Chair, W3C Web Accessibility Initiative Evaluation and Repair Tools Group
http://www.w3.org/WAI/ER/IG/

The WAVE web page accessibility evaluation assistant:
http://www.temple.edu/inst_disabilities/piat/wave/
Received on Friday, 27 October 2000 13:06:39 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 9 June 2005 12:10:37 GMT