[developers] RESTful ERG parsing

[Stephan Oepen]

hi again, ned and mike,

> Your summary looks about right. In my previous message, I thought CORS
> required a more complicated server configuration, but if it's just a header
> then it does seem pretty simple. If there's no benefit, then, to using
> JSON-P besides supporting older IE browsers, we probably don't need it.

our RESTful service at http://erg.delph-in.net/rest/0.9/ now supports
CORS (i.e. provides the ‘Access-Control-Allow-Origin: *’ header).  i
hope this much will be sufficient for you to escape the cross-domain
limitations in your JavaScript client, ned?

i am delighted you are developing this client already, but i need to
caution that (a) mike and i are still discussing minor modificitions
to the JSON serialization for MRS and that (b) there appears to be a
bug in the JSON representation of multi-token leaf nodes in the
derivation.  i hope to have both resolved over the next few days!

cheers, oe