Blogs / Abstractioneer / 26 blog reactions

sure why ESRI wouldn't follow suit. Reinventing it is fruitless; extending it behind the OGC's walls of secrecy equally so. Better to get involved with the Atompub community and IETF to solve some of the issues that remain open for us geospatial folks: batching, simplification of media (specifically geospatial content) resource creation (maybe with Atompub Multipart), and filtering. Paul writes: No matter how much we (me) might bitch about OGC standards, they have a huge advantage over DIY, in that they

sure why ESRI wouldn't follow suit. Reinventing it is fruitless; extending it behind the OGC's walls of secrecy equally so. Better to get involved with the Atompub community and IETF to solve some of the issues that remain open for us geospatial folks: batching, simplification of media (specifically geospatial content) resource creation (maybe with Atompub Multipart), and filtering. Paul writes: No matter how much we (me) might bitch about OGC standards, they have a huge advantage over DIY, in that they

John Panzer

OpenID for identity and logging in, it uses OAuth to authorize access to friend and profile data on existing sites that host it, and it uses OpenSocial to embed the applications within your site. Abstractioneer puts it like this:  In a nutshell, the OpenSocial RESTful API is a catalyst that enables participation in a much larger and more complex ecosystem. What are the implications of this? I think it punches 

has just announced the birth of its developer platform as a well supported open social network. This is extremely popular in Latin America, and has become a founding member of a non-profit organization “OpenSocial Foundation”, which was announced last week by Google, MySpace, and Yahoo.

has just announced the birth of its developer platform as a well supported open social network. This is extremely popular in Latin America, and has become a founding member of a non-profit organization “OpenSocial Foundation”, which was announced last week by Google, MySpace, and Yahoo.

to his proposal, this time using a new verb BATCH and using a multipart entity body with each part representing an independent HTTP request encoded via the application/http media type. John Panzer of Google posted some of his reactions to this idea. This activity proves that every organization exposing web services over HTTP is facing two common problems: Partially updating resources, which HTTP PUT can not address, and which HTTP PATCH can address reasonably well.

In response to my post on PATCHing and BATCHing, John Panzer made a very valid comment.

to his proposal, this time using a new verb BATCH and using a multipart entity body with each part representing an independent HTTP request encoded via the application/http media type. John Panzer of Google posted some of his reactions to this idea. This activity proves that every organization exposing web services over HTTP is facing two common problems: Partially updating resources, which HTTP PUT can not address, and which HTTP PATCH can address reasonably well.

and technical backgrounds from me. Whether it was hearing different perspectives on the social graph problem from folks like Joseph Smarr and Blaine Cook, getting schooled on the various real-world issues around using OpenID/OAuth in practice from John Panzer and Eran Hammer-Lahav or getting to ask getting to Q&A Brad Fitzpatrick about the Google Social Graph API, it was a great learning experience all around. There have been some ideas tumbling around in my head all week and I wanted to wait a few