{"id":266,"date":"2007-02-22T22:03:46","date_gmt":"2007-02-23T02:03:46","guid":{"rendered":"http:\/\/www.dr-chuck.com\/wordpress\/?p=266"},"modified":"2011-12-17T12:22:05","modified_gmt":"2011-12-17T16:22:05","slug":"my-recent-obsession-interoperability","status":"publish","type":"post","link":"https:\/\/www.dr-chuck.com\/csev-blog\/2007\/02\/my-recent-obsession-interoperability\/","title":{"rendered":"My Recent Obsession &#8211; Interoperability"},"content":{"rendered":"<p>I don&#8217;t know what has gotten into me but for the past few months I have been *obsessed with Interoperability &#8211; I just cannot get it off my mind.  Perhaps it is because I keep drawing PowerPoints about how everything must be connected to everything.  Perhaps it is my personal hidden shame that we did not do a better job connecting Sakai and uPortal during the Sakai Project (2004-2005).  I don&#8217;t know why but lately I cannot stop thinking about Tool Interoperability.<br \/>\nSome points&#8230;<\/p>\n<p><!--more--><br \/>\nIMS Tool Interoperability Version 2 is starting and I am getting pulled into it.  Wimba and Microsoft are leading and doing a great job.  I secretly (don&#8217;t tell anyone) just want to adopt the PowerLinks web services as IMS TI version 2.  I like PowerLinks web services &#8211; I only have seen a high level document &#8211; but what I see looks nice.  Of course IMS TI 1 is based on and pays homage to a small subset of PowerLinks back inthe WebCT days.<br \/>\nSakai will support RSS, Atom, and OPML feeds for version 2.4. This allows you to track a bunch of Sakai servers with federating RSS feeds &#8211; you can get a system-wide (all sites) or a single site feed.  This is the end of a task that I set for myself at a bar in New York City drinking a pint of Guiness with Bill Thompson of JA-Sig and Rutgers fame.  I was exasperated at hte time, having tried everything to connect Sakai and uPortal in a way that *made the users happy* &#8211; we had put a lot of effort into demonstrations which were a lot of work &#8211; but users just yawned.   SO I said to Bill &#8211; &#8220;What *do* you portal guys want??&#8221; &#8211; he said, &#8220;Make me some iCal feeds and RSS feeds &#8211; I wil send the RSS through some XSLT and make a nice dashboard for my users &#8211; they can just launch into your app from the dashboard if they like.&#8221;.  He added, &#8220;and believe me &#8211; I do *not* want Sakai to run *in* my portal &#8211; I just want a good usefu; dashboard.&#8221;.  I like that kind of thinking.<br \/>\nSakai 2.4 will also support JSR-168 using Pluto 1.1.  At the same time uPortal 3 should also use Puto 1.1 instead of Pluto 1.0.  This means that the *exact same war file* can be dropped into uPortal or Sakai and the portlets will jsut work.  SO we have war portability &#8211; something that the portal community does not do well at all.  But with Pluto 1.1 (the magic sauce) we converge on a portable WAR format by choosing the same implementation.  Not to mention the speed at which Sakai and uP3 can get to JSR-286 by soimply following Pluto.  These efforts have nicely brought the Sakai, uP3, and Pluto communities much closer together.  So this is like a nice little treansportable tool unit &#8211; finally JSR-168 is having some effect.<br \/>\nI played with the IMSTI tool in Sakai and worked with Anthony and helped make it work on HSQL db.  Then to test it I needed a test jig so I wrote this:<br \/>\nhttp:\/\/www.sakaiproject.org\/imsti-test\/<br \/>\nThis includes source code to provide basic support for launch PHP tools using IM TI.  This also will help a lot in testing TI features.<br \/>\nI learned a lot about nusoap and really and truly reached the conclusion that SOAP is crap.  No wonder everyone does REST &#8211; after 6 days struggleing with SOAP &#8211; REST seems like nirvana.<br \/>\nEnough for now..  Back to catching up on EMail riding the Michigan Flyer bus from Detroit to Lansing with it cool and free wireless.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I don&#8217;t know what has gotten into me but for the past few months I have been *obsessed with Interoperability &#8211; I just cannot get it off my mind. Perhaps it is because I keep drawing PowerPoints about how everything must be connected to everything. Perhaps it is my personal hidden shame that we did [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-266","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/posts\/266","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/comments?post=266"}],"version-history":[{"count":1,"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/posts\/266\/revisions"}],"predecessor-version":[{"id":2371,"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/posts\/266\/revisions\/2371"}],"wp:attachment":[{"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/media?parent=266"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/categories?post=266"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/tags?post=266"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}