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

Rough scoping for first deliverable

From: Sean Owen <srowen@google.com>
Date: Fri, 2 Feb 2007 12:32:56 -0500
Message-ID: <e920a71c0702020932i3d733825v39dc527c0938ca2d@mail.gmail.com>
To: public-mobileok-checker@w3.org, "Jo Rabin" <jo@linguafranca.org>

At Jo's reasoanble suggestion, here's my proposed rough scope for the
first mobileOK Basic Tests reference implementation:

1. mobileOK Basic Tests reference implementation
A reference implementation of mobileOK Basic Tests 1.0, in Java. I'm
thinking Java 5.0, and package org.w3c.mwi.mobileok.basic. Library
will at minimum accept as input a URI, and output test results as
specified by the document (individual results, outcomes, warnings,
etc.) It will use some third-party open-source software (thinking
Jakarta's HttpClient, a DOM parser like Xerces, a CSS parsing
library). We'll collaborate on this code via dev.w3.org.

2. Updated web application at validator.w3.org/mobile which provides
validation by file upload or for a given URL. If this is not already
in Java, we can surely make a simple web J2EE web application that
wraps the checker. Once we get a little closer we'll follow up with
Dom et al. to see what kind of app can be hosted.

Ideally this is all complete by the time mobileOK Basic Tests 1.0's
final draft is released. I think it's crucial to have at least an
incomplete, alpha release ready by then. I assume we have until at
least the end of March, but that's still not a whole lot of time. So,
we need to schedule so as to deliver *something* reasonable along with
the final draft.

Thoughts? I already have a little code ready, a framework plus enough
implementation to retrieve and parse a document and run a test. I'll
send it around when I get home for comments.

Received on Friday, 2 February 2007 17:33:09 UTC

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