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

RE: Some draft code for mobileOK Basic Tests RI

From: Jo Rabin <jrabin@mtld.mobi>
Date: Tue, 6 Feb 2007 08:20:30 -0500
Message-ID: <815E07C915F39742A29E5587B3A7FA19287D7CCB@lk0-cs0.int.link2exchange.com>
To: <public-mobileok-checker@w3.org>

> Hmm... I guess the approach you're suggesting would mean creating two
> piece of code: one to transform the input into the appropriate XML
> that would contain most of the data and some of the pre-analysis made
> it, and a test harness to run the on the resulting XML file.
> I certainly like the idea, but I think the portability of the first
> piece of the code will be much lower than the second one.

Am I reading too much into what you are saying? Are you suggesting that
there is a pre-processing step that consists of:

a) Tidy-ing the HTML and recording the errors from that tidy.
b) Tidy-ing the CSS, recording the errors and transforming to some sort
c) [Tidy-ing the HTTP headers] Transforming to some kind of HTTP-XML
(noting the work on HTTP in RDF).
d) combine as a new input document.

In this case I think James's idea ref XPath would work, perhaps in the
context of an XSLT. 

So I guess a question is: could one define the mobileOK reference
implementation as an XSLT, given sufficiently strict definition of the
preceding steps?

Received on Tuesday, 6 February 2007 13:20:43 UTC

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