-
“The biggest threat to Google isn’t that someone else will implement the same Calendar API as Google, it’s that someone will make web pages uncrawlable through proprietary extensions to HTML or HTTP”
-
No SOAP support. Not even a mention, AFAICT.
-
“Please take note⦠per our announcement on May 12, we will shutdown Version 3 of the API today. Please make sure you have migrated your applications to Version 4 in order to ensure uninterrupted service” – this, from the world’s most successful Web company. Obviously somebody missed a memo.
-
“If you’re going to expose your service through multiple protocols then I really think that should it should be done in such as way as to take full advantage of the features of each protocol.”
-
“I think I’ll come out of the closet as an admitted RESTafarian / Web Stylista” Welcome to the fold, Stu! One dist-obj mailing list alumnus converted, (at least) one more to go. 8-)
Phil Windley says that we need a RESTful service interface description language. I don’t think we do.
Interoperability requires agreement, and agreement begets commoditization. If all the interfaces are the same, what would you describe?
What Phil (and those he links to) needs, I suggest, is simply for these apps to to expose all their data via URIs in as standardized a form as possible, including parameterized state transitions (i.e. a forms language). Implicit in that recommendation is that the data formats used must support and encourage linking, otherwise discovery of all the data becomes problematic.
Many self-described Web 2.0 apps, unfortunately, don’t do those things. They focus on only one aspect of Web 2.0 – more interactive UIs – while forgoing the benefits offered by other important integration-simplifying aspects of it, such as open data.
.Tags: rest, wsdl, integration, web.