Thanks Shlomo for this great review of communicating in the cloud. I
particularly like the quadrants (and not just because OCCI's alone in
the top right corner). It makes a clear separation between APIs and
protocols which is something we need to do a lot more of.
What is increasingly clear to me is that while HTTP was the
lingua franca of the Internet, an evolution of it will be the lingua
franca of the cloud. That is, whoever deviates the least from HTTP
while still delivering the additional functionality we require for
organising resources (e.g. linking, categorising, animating,
annotating, etc.) will "win" the standards war/race/game/etc. because
it will be most accessible by developers and users alike.
That's why I love hearing feedback like "the
[OCCI] spec
is extremely straightforward and intuitive for anyone familiar with the
usual HTTP verbs" - as we did from the CTO of a popular Web 2.0 startup
this week. It's also great to see other initiatives validating our
approach by adopting similar technology (e.g.
VMware vCloud's use of
link
relations).
Sam
P.S. Apologies to those of you on both lists for the
cross-post... I figured this was relevant for both audiences. If you're
not you can join the CCIF and OCCI lists
here and
here
respectively.