2009
Apache CouchDB: Introduction
by holyver
What CouchDB is
* A document database server, accessible via a RESTful JSON API.
* Ad-hoc and schema-free with a flat address space.
* Distributed, featuring robust, incremental replication with bi-directional conflict detection and management.
* Query-able and index-able, featuring a table oriented reporting engine that uses Javascript as a query language.
What it is Not
* A relational database.
* A replacement for relational databases.
* An object-oriented database. Or more specifically, meant to function as a seamless persistence layer for an OO programming language.
2008
2007
TechCrunch en français » 5 manières de mélanger, déformer et réorganiser vos données
by parmentierf & 5 others
Appelez les pipes, teqlos, dapps, modules, mashups ou n’importe quoi d’autre, le fait est que nous avons récemment vu un bon nombre de nouveaux services permettant aux développeurs et aux utilisateurs de construire de petites applications et des mashups pour transformer et ré-utiliser des données. Nous vous présentons dans ce qui suit 5 applications qui permettent de mélanger, déformer et réorganiser vos données, en examinant les données entrantes, sortantes, le support du REST, des suggestions d’utilisation et le niveau de compétence requis
Eleven Emerging Ideas for SOA Architects in 2007
by nhoizey & 1 other (via)
using the basic Web formats and protocols such as HTTP, XML, REST, and JSON as the "Unix Pipe of the Web" -- to quote a colorful phrase of Ray Ozzie's -- as the fundamental glue between systems
WS-Transfer for WCF (Indigo) - The Code Project - SOAP and XML
by nhoizey (via)
A WS-Transfer interaction is based on the REST architectural style (it looks like its SOAP implementation) where four interfaces can handle the creation and operation of the resource state. There is a CRUD (Create/Retrieve/Update/Delete) style in the resource state, the same way it is in the database layer - database record.
michaelhanson.blogspot.com
by nhoizey (via)
to implement Web Services Security with the X.509 Certificate Profile, you also need to implement XML Signature (which includes XML Canonicalization and XML Exclusive Canonicalization) and XML Encryption. To correctly handle imports of WSDL1.1 documents (and validate the traffic they describe), you need to support the entire behemoth that is XML Schema -- in particular if you are attempting to support RPC-oriented SOAP, which informally requires you to support the entire XML Schema Datatypes specification. Don't forget support for SOAP with Attachments, either!
2006
Unofficial Digg API
by François Hodierne & 2 others (via)
Only simple GET methods at the moment, not allowed to authenticate nor POST.
REST without RDF is only half as bad as SOAP
by benoit
Of all the xml data formats (as opposed to markup formats such as xhtml or OpenDocument, which is not my topic here), RDF is the one that takes the lessons of REST to heart. In RDF every concept, every relation, every object has a permalink so to say, a fixed URI that identifies it.
eXist : Une base de données XML interrogeable avec XPath et XQuery
by nhoizey & 1 other
eXist peut non seulement s'intégrer très facilement dans une application Java (via une servlet - XQueryServlet -, un composant Cocoon - XQueryGenerator - , ou l'utilisation de l'API XML:DB), mais elle peut également être utilisée dans de nombreux autres langages grâce à ses API REST et XML-RPC. Il existe d'ailleurs des API Pyhon et PHP
Docvert [current 2.0]
by gregR & 5 others (via)
This web service software takes multiple word processor files (typically .doc) and converts them to Oasis OpenDocument which can then be converted to HTML, RSS, or any XML format.
2005
1060 research - netkernal - quotes from the blogsphere
by macroron
John Udell (infoworld) I never heard the phrase "REST microkernel" before, but I had an immediate expectation of what that would mean. An hour's experimentation with the system met that expectation. Wildly interesting stuff.
1060 research - netKernel - service oriented microkernel and xml application server - white paper
by macroron
from websites to internet operating systems. a perspective on the evolution of the web and a rethink of web-services.
