Comments on: Standard Interoperability API http://www.vidog.com/blog/standard-interoperability-api/ the adventures of chrisk Wed, 08 Sep 2010 13:46:00 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Trav http://www.vidog.com/blog/standard-interoperability-api/comment-page-1/#comment-40 Trav Mon, 14 Nov 2005 22:54:11 +0000 http://www.vidog.com/blog/?p=19#comment-40 So, OLE is basically the equivalent of what you want in the fat-app model, so you may want to look at that in the context of the web & steal some ideas from that. You'll want to have a lot of metadata about the objects that you're providing. For instance, if I'm writing a webapp word processor and I want to incorporate a graph, is a person going to have to go to the gliffy site to create it? The best situation is that they would just pull a drop down or click a 'gliffy' icon and voila your app would be presented within an iframe in the actual document itself. In order to do that, you'll have to be communicating with other services behind the scenes. The protocol would certiainly contain things like "What services do you provide?" "What kinds of inputs does this service take?" You'll definitely want to be using MIME types for your content so that these questions are more meaningful. For instance, if someone with a translation application wants to interact with your word processor, you'll want to let them know that 'MyFancyTranslationApp' takes in text/plain or something. Or 'MyFancyGraphingApplication' takes in text/csv or sometypeof/spreadsheet As for Single Sign On -- have you looked into things like the Liberty Alliance? So, OLE is basically the equivalent of what you want in the fat-app model, so you may want to look at that in the context of the web & steal some ideas from that.

You’ll want to have a lot of metadata about the objects that you’re providing. For instance, if I’m writing a webapp word processor and I want to incorporate a graph, is a person going to have to go to the gliffy site to create it? The best situation is that they would just pull a drop down or click a ‘gliffy’ icon and voila your app would be presented within an iframe in the actual document itself. In order to do that, you’ll have to be communicating with other services behind the scenes. The protocol would certiainly contain things like

“What services do you provide?”
“What kinds of inputs does this service take?”

You’ll definitely want to be using MIME types for your content so that these questions are more meaningful. For instance, if someone with a translation application wants to interact with your word processor, you’ll want to let them know that ‘MyFancyTranslationApp’ takes in text/plain or something. Or ‘MyFancyGraphingApplication’ takes in text/csv or sometypeof/spreadsheet

As for Single Sign On — have you looked into things like the Liberty Alliance?

]]> By: Dave Johnson » Blog Archive » Identity, Mash-ups and Open APIs http://www.vidog.com/blog/standard-interoperability-api/comment-page-1/#comment-23 Dave Johnson » Blog Archive » Identity, Mash-ups and Open APIs Sun, 23 Oct 2005 09:12:35 +0000 http://www.vidog.com/blog/?p=19#comment-23 [...] references [1] Open Mashup APIs - Ajaxian, Oct 17, 2005 [2] Mashups and Openess - Sam Schillace, Oct 7, 2005 [3] Standard Interoperability API - Chris Kolhardt, Oct 8, 2005 [...] [...] references [1] Open Mashup APIs - Ajaxian, Oct 17, 2005 [2] Mashups and Openess - Sam Schillace, Oct 7, 2005 [3] Standard Interoperability API - Chris Kolhardt, Oct 8, 2005 [...]

]]> By: Jay http://www.vidog.com/blog/standard-interoperability-api/comment-page-1/#comment-22 Jay Tue, 11 Oct 2005 16:02:00 +0000 http://www.vidog.com/blog/?p=19#comment-22 Dude, I think Sxip Network is what we were basically talking about the other week. Good luck with the integration. It'll be interesting to see if you can pull it off and even more so as I'll be integrating all these kinda apps in our product in the coming year. Dude, I think Sxip Network is what we were basically talking about the other week.

Good luck with the integration. It’ll be interesting to see if you can pull it off and even more so as I’ll be integrating all these kinda apps in our product in the coming year.

]]> By: Daniel Feygin http://www.vidog.com/blog/standard-interoperability-api/comment-page-1/#comment-21 Daniel Feygin Mon, 10 Oct 2005 13:11:59 +0000 http://www.vidog.com/blog/?p=19#comment-21 Identity federation is the more specific basic identity requirement. SSO and identity management are peripheral to the cross-linking API. Sxip looks interesting, too interesting actually to be true. If only I could figure out what's the catch. Identity federation is the more specific basic identity requirement. SSO and identity management are peripheral to the cross-linking API.

Sxip looks interesting, too interesting actually to be true. If only I could figure out what’s the catch.

]]> By: sam http://www.vidog.com/blog/standard-interoperability-api/comment-page-1/#comment-20 sam Sat, 08 Oct 2005 23:36:04 +0000 http://www.vidog.com/blog/?p=19#comment-20 D'oh! Should have started this as a writely doc! Here it is...email me if you want to be added. http://www.writely.com/Doc.aspx?id=a469zkvzp9r D’oh! Should have started this as a writely doc! Here it is…email me if you want to be added.

http://www.writely.com/Doc.aspx?id=a469zkvzp9r

]]>