snellspace.com

Starting immediately, I have switched focuses and roles at IBM. I am excited to be the technical lead for the IBM CIO Technology & Innovation organization’s new Security Innovations Team. After spending the past eight years championing and developing social networking and syndication technologies, it’s time for a change of focus. The new team will focus on innovating new projects relating to a variety of security issues including identity, privacy, authentication, audit, cloud security, etc. Security has always been an underdeveloped passion of mine and I’m quite looking forward to the new opportunities. Unfortunately, this pretty much means that my ability to focus on social networking and syndication technologies is going to go into severe decline over the coming months.

The Atom Tombstones draft had expired. As requested by several members of the Atom syntax mailing list, I have revitalized the draft.

The Atom Bidi Draft had expired. I posted a new version to revitalize it. Want to get this one finished for good.

Thanks to Mark Nottingham and Lisa Dusseault, work on HTTP Patch has been progressing nicely. Looks like it’s pretty much done with the exception of a few minor issues. Perhaps it is time to start working on standardizing some Patch document formats?

Comments requested… http://www.ietf.org/internet-drafts/draft-snell-http-batch-00.txt

Example from the draft:

       POST /example/application HTTP/1.1
       Host: example.org
       Content-Type: multipart/batch;
         type="application/http;version=1.1";
         boundary=batch
       Mime-Version: 1.0

       --batch
       Content-Type: application/http;version=1.1
       Content-Transfer-Encoding: binary
       Content-ID: <df536860-34f9-11de-b418-0800200c9a66@example.org>

       POST /example/application HTTP/1.1
       Host: example.org
       Content-Type: text/plain
       Content-Length: 3

       Foo
       --batch
       Content-Type: application/http;version=1.1
       Content-Transfer-Encoding: binary
       Content-ID: <226e35d0-34fa-11de-b418-0800200c9a66@example.org>

       PUT /example/application/resource HTTP/1.1
       Host: example.org
       Content-Type: image/jpg
       Content-Length: 123456

       {jpg image data}
       --batch--

And the response…

       HTTP/1.1 200 OK
       Date: Wed, 29 Apr 2009 20:00:00 GMT
       Server: example.org
       Content-Type: multipart/batch;
         type="application/http;type=1.1";
         boundary=batch
       Mime-Version: 1.0

       --batch
       Content-Type: application/http;version=1.1
       Content-Transfer-Encoding: binary
       In-Reply-To: <df536860-34f9-11de-b418-0800200c9a66@example.org>

       HTTP/1.1 204 OK
       Date: Wed, 29 Apr 2009 20:00:00 GMT
       Server: example.org

       --batch
       Content-Type: application/http;version=1.1
       Content-Transfer-Encoding: binary
       In-Reply-To: <226e35d0-34fa-11de-b418-0800200c9a66@example.org>

       HTTP/1.1 415 Unsupported Media Type
       Date: Wed, 29 Apr 2009 20:00:00 GMT
       Server: example.org

       --batch--