[developers] RESTful ERG parsing

[Ned Letcher]

>
>
> The other is including TO and FROM values within derivation nodes to map
> sub-trees onto the corresponding  character spans in the original string.
> While not as enlightening as in the case of doing this for
> predications---since the surface yield of a derivation is a little easier
> to see directly in the tree---I still feel like the input highlighting
> would be a useful feature. I guess I could manually extract them from the
> contents of the 'tokens' attribute, however this will make the client
> dependant on the ERG's token mapping setup and my understanding is that
> this can vary from grammar to grammar? Although, to be fair, this is only
> advertised as an 'ERG' API. That said, this still feels like lower level
> implementation logic that an API should smooth over.
>

I just realised that while my motivations for this feature might have
implied providing to/from fields on all nodes, I don't really think it
necessary to have them on nodes other than leaf nodes. If the user of the
API wants to propagate them up, they can do that for themselves -- as i
just realised I did for Typediff.

Ned
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.delph-in.net/archives/developers/attachments/20160424/3e63f12f/attachment.html>