While Nexista will most likely be consumed for use in custom application developments - and when I say consumed, I mean used directly rather than indirectly - the indirect use case calls for an API. Not an API to nexista per se, but more for its handling of XML and XSL. I'm just starting to think about this, so I haven't got much to say other than I'm worried it might have to be split into three parts: * SQL for data* PHP for logic* XSL for presentationThough as I write this down, an API layer could be created at the XSL level, where data is output to XML. Right now Nexista gathers data directly from a datasource and injects it right into the flow XML document which can be accessed by XSL stylesheets. However, I've begun to separate the process, using a CURL interface between the two steps, so that there are actually two separate documents. Something to think about... now back to working on PBooks.