FeforPetApi

PET API proposal

The idea is to replace the cheap executable (with 'pipe' over stderr...) by a library. The library in turn then could be wrapped in an executable, or better in a XML-RPC or other socket server. The library could also be

The main motivation is to have a more flexible configuration. Currently, the cheap binary has to be restarted (including time-consuming grammar loading) each time the number of readings to return is to be changed. Using the new API, this

Generally, no new features will be added, just the interface should be made explicit

* MRS globals * access to type hierarchy

feature requests * configurable start symbol for parsing (FrancisBond) * pseudo TDL syntax for settings (common with LKB), as discussed in JerezTop * change lexicon during runtime (probably not possible, but lexDB)