As long time readers of mine know, I’ve talked a lot about the value of visibility, but had little success convincing Web services proponents that WS/SOA has significantly less of it than do Internet scale architectural styles. With that in mind, I thought I’d talk a bit about a couple of related properties reusability (sometimes… Read More »
Chris Ferris writes in response to my suggestion that processing an XML document is an all-or-nothing proposition; I don’t see it that way. Understanding an XML document is not an all-or-nothing proposition by any stretch of the imagination. For instance, I can have a generic SOAP processor that understands the SOAP namespace but is oblivious… Read More »
More good insight from Savas on REST. He writes; The human factor is involved. If a resource (e.g., a web page) has moved, applications don’t break. It’s just that there is nothing to see. We are frustrated that it’s not there. If an application depends on that resource being there, that application breaks. Yep. But… Read More »
Jeff Schneider asks; I’m looking for some common vocabulary to describe the various nomenclatures found in service operations. In IETF-land, a “Pass-All Service” would be called a “transport protocol”, and a “Verb-Only Service” an “application protocol”. The last one, “Verb-Noun Service” is just a not-as-generic application protocol, but still an application protocol.
The W3C has published (amoungst other things) RDF, RDF Schema, and OWL as Recommendations. Bravo! A job well done by everybody involved.
Here’s the answer I gave to a question that came in on Ask The Experts, asking “What are the most important benefits a company can realize by following REST?”; In general terms, ease of integration. Implementing RESTful services opens up your data to machines as easily as the HTML based Web does to humans, in… Read More »
From the it-just-keeps-getting-wackier file, this; The goal of XDI is to do for controlled data sharing what the Web did for open content sharing Wow, where to start on this one? So, how do “content” and “data” differ exactly? Can the same data not be returned from an HTTP GET on a URI as from… Read More »
Chris responds to an earlier comment of mine. My point remains that HTTP is not suited to extension of its methods because it requires centralized administration of the method names. You can’t simply make up a new method like MONITOR and deploy it unless you go through the IETF to revise the HTTP specification. Unless… Read More »
Mark talks about document persistence and message transience. I would have agreed with that a few years ago, but as I’ve come to understand the value in self-description, I see that it is possible to have messages persist in meaning for as long as the documents which they encapsulate. A RESTful message is purely self-descriptive,… Read More »
Sean McGrath writes; If you want to look at a cheap, solid, scalable way to do distributed computing, look no further than the combination of HTTP and asynchronous messaging using business level XML documents. The beauty of this, is that it is both Intranet and Internet class at the same time. Work with the web… Read More »