W3C home > Mailing lists > Public > public-test-infra@w3.org > April to June 2013

Re: Spec parser

From: Tobie Langel <tobie@w3.org>
Date: Wed, 29 May 2013 10:01:22 +0200
To: Linss, Peter <peter.linss@hp.com>
Cc: public-test-infra <public-test-infra@w3.org>, ext Robin Berjon <robin@w3.org>
Message-ID: <EDEFF91BDF084303B19FA9AB8218AF9D@w3.org>
On Tuesday, May 28, 2013 at 6:08 PM, Linss, Peter wrote:
> while the parser uses a hand full of Shepherd classes to access the DB, it's actually already pretty well decoupled from the rest of the system.
Yeah, that's the coupling I was referring to. I was hoping to be able to use the parser without having to install MySQL and PHP.
> It wouldn't be very hard to make a stand-alone spec manager web app if you want a canonical instance running somewhere in W3C space, it would also be trivial to install a full Shepherd instance and simply not use the rest of it… (Shepherd is pretty much self-installing and self-maintaining these days, you just need a LAMP stack and a handful of Python libraries, like html5lib). I'd be happy to help with either.

I was hoping for something slightly more portable: a script I could pipe text to and which would return some tree I could then transform to JSON.

Received on Wednesday, 29 May 2013 08:01:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:34:08 UTC