The Web is known primarily as a Web of Documents because that has been our main experience with it, but we should not ignore the idea of documents as a data source. New technologies are emerging to make it easier to encode extractable content on the Web. This article focuses on how producers can increase the machine-processability of the documents they produce.
In this second article in the Resource-Oriented Architecture series, Brian Sletten discusses the benefits of REST, what constitutes a resource, associating metadata with a resource, the pitfalls of common models of resource metadata, SPARQL, RDF, expressing RDF facts, RDF triples, querying RDF, and sample RDF queries.
In this first article in the Resource-Oriented Architecture series, Brian Sletten discusses the REST architecture style, the history of SOA, SOAP and WS-*, the Semantic Web, URLs as identifiers, URIs and URNs, freedom of form, logically-connected late-binding systems, HATEOAS, and the impact of the Semantic Web upon software systems.
The authors, from Intel, offer a three pronged approach to providing secure transmission of high volume HTML traffic using CPU instructions and a novel RSA algorithm to significantly reduce costs. 5
Gregor Roth RESTful HTTP architecture and design, common URI naming, Uniform interface interactions, when to use PUT or POST, how to support non-CRUD operations, and more. 12
What exactly happens when an HTTPS connection is established? This article analyzes the data exchanged between the browser and the server, down to the byte, in order to set up a secured connection. 9
.NET and Java interop can be made really simple using a REST document centric approach. This article demonstrates REST for interop as well as POST-REST. 4