Cesare Pautasso and Guy Pardon propose a way of implementing transactions over HTTP using REST and the Try-Confirm/Cancel protocol.
Dennis E. Wisnosky exemplifies harnessing SOA, cloud computing and semantic technologies to solve some of the today’s public or private sector complex problems.
Hook Hua discusses how semantic Web technologies are being leveraged by cloud-based SOA to improve interoperability within NASA enterprise boundaries and between NASA and external organizations.
Subbu Allamaraju discusses interoperability between web applications using ql.io, an Node.js-based HTTP gateway.
Peter Beverloo introduces the W3C Web Components model useful to design web widgets, and consisting of Templates, Decorators, Custom Elements, and the Shadow DOM.
Steve Vinoski introduces Webmachine, a toolkit for declaratively building well-behaved HTTP applications, making the job of dealing with HTTP simpler.
Paul Downey talks on the current status of identity management on the web covering cross-site challenges, REST, HTTPS, Open ID, all in the context of enterprise architecture.
Justin Sheehy details Webmachine, a RESTful toolkit for writing well-behaved HTTP applications, helping developers to deal with the complexities of an HTTP-based application.
Glenn Block presents how developers can build RESTful solutions using Microsoft’s technologies, especially with WCF and .NET.
Scott Davis makes a case for metadata or semantic data, pointing out that it is currently used by major websites to improve their traffic or the rank of the pages searched. He is presenting the most common ways to add metadata to a document: RDFa and microformats.
Ian Robinson considers that programming for the web requires a different architectural approach than for applications: clients are interested only in URIs, clients are responsible for the integrity of a sequence of requests, and one should implement application protocols as protocol resources , not domain resources.
Cesare Pautasso presents a pattern-based design methodology used to build RESTful services, which is accompanied by an example used to draw a number of patterns: Uniform Contract, Entity Endpoint, Content Negotiation, Endpoint Redirection, Idempotent Capability. Pautasso also mentions a couple of anti-patterns: tunneling everything through HTTP/GET and HTTP/POST.