Yah, I saw that Rackspace also uses Link: type of headers, but I thus far haven't seen the need in what I'm doing. Perhaps next week I'll come to the realization as to why they're useful. :)

We're designing an API primarily, along with some implementations, and aim to have various language-binding clients for Ruby, Python, Java, etc.

At this point, we're marching forward as fast as we can. I'll take a look at the OCCI stuff, though, and see if we can't find some common ground.

On Aug 1, 2009, at 11:05 AM, Sam Johnston wrote:

Bob,

Very interesting. Are you desigining a client or an API or both? A lot of this looks very similar to the current thinking around the OGF's Open Cloud Computing Interface (OCCI), right down to the discovery document and use of LINK elements (and HTTP Link: headers). More info at http://www.occi-wg.org/ but be warned that the documentation currently lags the discussions... it looks like there's a good opportunity for us to work together here (both client libraries like libcloud and standard interfaces like OCCI will be required).