RE: Some draft code for mobileOK Basic Tests RI

> > So then you can flip the question round. If you're building a meta-
> > doc for audit purposes anyway, why *wouldn't* you use it as the
> > test subject
> You are right.
> If we could build a meta-xml-doc that defines the test-runs (HTTP
> headers, document encoding, XPath Queries, image formats, ...) and
> the validator returns this xml doc with a result for each test run,
> the question about the implementation language is not important.
> 
> I think, the next step is to define this meta-xml-doc format and the
> test-run types (headers, encoding, XPath, ...) and discuss the test
> run's.
> 

OK so here are some explicit questions leading us down that path:

1) What work is there on an XMLized version of CSS and is there some
code out there already that does this transform?

2) What work is there on an XMLized version of HTTP headers, or is it as
simple as 

<HTTPResponse result="true" start="20:00:00.31" end="20:00:05.29">
	<status>200 OK</status>
	<header name="Content-Type">text/plain; charset="UTF-8"</header>
	<header name="ETag">ds90ewkldskljewr09kjnerfdmnerf</header>
	<payload>&lt;html&gt;&lt;body&gt;&lt;p&gt;Escaped encoding, what
a pain&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;</payload>
</HTTPResponse>

3) What should the character encoding of the meta doc (and indeed the
result doc) be, given that the input doc could be in any encoding?

Jo

Received on Wednesday, 7 February 2007 11:08:33 UTC