Re: Spec parser

On May 29, 2013, at 1:01 AM, Tobie Langel wrote:

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

The spec parser doesn't have any PHP dependencies, It's all Python, it does store/load the spec data into MySQL.

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

I could factor out the parser itself from the rest of the script, the bulk of the parser really just walks a DOM tree and the DB access is fairly isolated. I'm at the TAG f2f this week and the CSS f2f next, I might be able to scrape some time out next week but it'll probably be after.

Peter

Received on Wednesday, 29 May 2013 08:21:32 UTC