On Aug 15, 2011, at 5:55 PM, Bruce D'Arcus wrote: > On Mon, Aug 15, 2011 at 11:48 AM, Sylvester Keil <[email protected]> wrote: > >> I've updated the edtf Ruby gem to reflect the latest draft. > > Awesome! > >> The parser is based on the BNF with minimal changes to resolve a few >> conflicts and it works for all extensions except 201 and 205. The multiple >> dates (203, 204) right now return a simple array, which is to say that >> whilst features such as earlier/later are parsed correctly, that information >> is not exposed by the API. Eventually, we will need a new class to wrap >> these sets of dates. >> >> A few minor issues will have to be resolved (e.g., how to deal with >> open/unknown intervals or how to sort intervals and seasons), but overall >> you should be able to experiment with the format if you are so inclined. >> Simply, gem install and require 'edtf'; you then parse EDTF with the >> Date.edtf class method. > > So does this suggest, then, that you're happy with the spec? I tried > very much to be a voice for keeping it more-or-less easy-to-implement > (and therefore cutting features of questionable benefit that might not > be).
I'm happy with the spec so far. I've used the BNF for now, but it might be quicker to implement the parser with regular expressions (and then rule out some border cases programmatically) – or, if you know a parser generator for javascript, we might be able to quickly port the parser, too. Sylvester ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
