- 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
- 2 days 5 hours ago
- 2 weeks 2 days ago
- 6 weeks 6 days ago
- 14 weeks 2 days ago
- 15 weeks 4 days ago
Recent comments
- Graham Klyne (not verified)
- Sheer (not verified)
- Wilbert (not verified)
Re: My Perfect XML-Based Publishing Platform
In addition to be more perfect You said - the HTTP method - the requested URI - any HTTP header
May the future services will work over xmpp / Jabber
So http methods and URI must carefully encapsulated (just addressing conventions) Since many years exist papers (Tim BL for instance) with other representations (N3 for instance) In addition we have not clear directions foreseen in order to implement two levels TP
I read some strange things in recent updates of XQuery specifications