W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > February 2007

Re: Some draft code for mobileOK Basic Tests RI

From: Roland Gülle <roland@7val.com>
Date: Wed, 7 Feb 2007 13:53:23 +0100
Message-Id: <C89AEE0E-D1FE-4DCA-8296-53D2676F8470@7val.com>
Cc: <public-mobileok-checker@w3.org>
To: "Jo Rabin" <jrabin@mtld.mobi>

>>> 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?
Write XPath Queries into the meta-xml-doc and transform it to an XSLT.

> 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>
Write XPath ...

> 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?
meta/result doc: UTF-8 ;-)

If all meta informations about the incoming document should be in one  
big XML (like the HTTPResponse), like
the parsing informations about correct/incorrect encoding, encoding  
type,  XML declaration informations, ... in an XMLized version,
the work can be done by some XPath queries.

OK, only to check if I am right:
We have a incoming, meta and result doc.
The preprocessor transforms the incoming markup, HTTP headers and  
parsing information in one big XML.
The validation processor (XSLT) uses the meta doc to check the XML  
and generate a result doc.
Is this correct?

Received on Wednesday, 7 February 2007 12:53:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:21:17 UTC