SirPAC

validates rdf and/with schemas.

The following simple RDF:

<?xml version="1.0"?>
 <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
   xmlns:dc="http://purl.org/dc/elements/1.1/"> 
   <rdf:Description about="http://www.w3.org/RDF/Implementations/SiRPAC/"> 
   <dc:creator rdf:resource="http://www.w3.org/People/Janne/"/> 
  </rdf:Description> 
 </rdf:RDF>

Validates, as...

Triples:

History

• running since mid '98
• Ten-thousands of hits
• Seen as a reference implementation

Uses of SiRPAC

• Testing if some RDF is valid
• Gathering information into a database
• Visualising information
• Evaluating other applications, such as cwm

Not just standards please

• examples (such as earlier evaluations, especially if certified)
• tutorials
• "help line"
• developer feedback
• certification

Behaviour matters

It is hard to test software for conformance if there is no idea what it "should" do when a user tries to.

This also shows up assumptions or errors in the spec (e.g. tabindex).

Tools aren't everything...

For a lot of things there are various improvements that can be made.

Tools don't often detect or solve all problems

...but they help.

Tools are used to find information.

They provide support for the necessary thinking.

Different people, different expertise

example scenario

• User detects that there is a problem.
• Customer care agent confirms that there is a problem.
• Testers check problem. E.g. how widespread is it? What should be happening?
• Designer acknowledges problem, proposes fix.
• Customer care agent confirms there appears to be a solution
• User tests the solution.

It's about the user (STUPID!)

• People achieving what they are trying to do
• Software that can use software-generated content
• In other words, interoperability

Accessibility Evaluations

Web Content evaluations

• Required in lots of settings:
  • legal - but different sytems do diferent things
  • organisations
  • to do the right thing
• Difficult to measure when it's done - because it never is?
• Document is a big horrible monster...

More evaluation

Authoring Tool Evaluations

• Test if the specification can be implemented
• Test that it is being implemented
• Look at a range of techniques and tools

Feedback

• Software testing is hard. More tools please.
• More techniques is more helpful
• Some guidance on doing evaluation is good
• Example evaluations are good

dummy to get more in later?

Only a dummy would have read this far