Re: Spec parser

On Wednesday, May 29, 2013 at 10:19 AM, Linss, Peter wrote:
> > > 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.

That would be really sweet. Given the core value of this script is how it handles the gruesome discrepancies between specs, it would be great to be able to simply reuse it (and contribute to it) rather than reinvent the wheel.

--tobie

Received on Wednesday, 29 May 2013 08:25:51 UTC