- markup (76)
- xml (11)
- xslt (23)
- pipelines (8)
- atom (9)
- overlapping markup (6)
- schema (11)
- creole (5)
- dtll (1)
- xforms (1)
- xpath (1)
- xquery (2)
- coding (2)
- datagovuk (1)
- genealogy (4)
- hardware (1)
- linked data (16)
- modelling (1)
- named graphs (1)
- opendata (1)
- provenance (1)
- psi (3)
- skos (1)
- sparql (4)
- Talis (7)
- unicode (1)
- uri (4)
- versioning (1)
- visualisation (6)
- web (78)
- google (4)
- html5 (5)
- jQuery (2)
- rdf (46)
- ontologies (2)
- rdfa (8)
- rdfQuery (5)
- rest (6)
- wikis (1)
- work (3)
- legislation (2)
- xmlsummerschool09 (2)
- life (28)
- children (5)
- equality (6)
- gtd (1)
- environment (4)
- gadgets (5)
- software (3)
- xlinq (2)
- conferences (11)
- ukgc09 (1)
- xtech (9)
- xtech2008 (3)
- blog (8)
- drupal (3)
Recent posts
- 4 days 2 hours ago
- 2 weeks 4 days ago
- 7 weeks 1 day ago
- 14 weeks 4 days ago
- 15 weeks 6 days ago
Recent comments
- Claytor370 (not verified)
- satya sahoo (not verified)
- meanto (not verified)
- meanto (not verified)
- meanto (not verified)
Re: My Perfect XML-Based Publishing Platform
Regarding “invoking queries on its XML store”, or more generally having a REST client, one approach would be to leverage the xforms:submission element.
In fact in Orbeon we have already wrapped that element in an XPL processor (or “step” as per the XProc terminology). The benefit is that the XForms 1.1 xforms:submission really acts like a quite complete REST client.
-Erik