Re: Fedora OSID Support

I will be at the meeting in Vancouver and would be happy to discuss.

Jeff Kahn
jeffkahn@xxxxxxx
(678) 339--0674 (home office)


On Apr 27, 2006, at 2:39 AM, Jim Martino wrote:

> Jeff,
>    Thanks for the clarification. From the flurry of posts on this  
> topic, it is clear that there is a lot of complexity (and a lot of  
> interest!) on this issue. Chuck's comments about the scope of the  
> work required seem on target to me. How would folks feel about  
> getting together at the Vancouver conference to discuss/explore  
> future plans, possibly a working group on this?
>
> Jim
>
> Jeffrey Kahn wrote:
>
> > Anoop is working on the Fedora support for Tufts VUE.  He can  
> > comment  on what capabilities are in the implementation.  We plan  
> > to include  the implementation with VUE 1.5 due out in June.
> >
> > Jeff Kahn
> > jeffkahn@xxxxxxx
> > (678) 339--0674 (home office)
> >
> >
> > On Apr 26, 2006, at 7:53 PM, Jim Martino wrote:
> >
> > > An interesting variation is the possibility of connecting Sakai  
> > > to  Fedora through the OKI OSIDs - Jeff Kahn mentioned in a post  
> > > to  sakai-library (on 4/4) that Anoop Kumar of Tufts is working  
> > > on a  new version of an OKI bridge for Fedora. If this bridge  
> > > were wide  enough to include all the functionality Sakai needed,  
> > > these calls  could go through OKI.  I think this would be a  
> > > landmark application  of the OSID philosophy.
> > >
> > > Jim
> > >
> > > Glenn R. Golden wrote:
> > >
> > > > Peter, a JSR-170 approach will not do you any good in Sakai -  
> > > > we  are  not using that now.
> > > >
> > > > If you really want Fedora to be the content repository, i.e.  
> > > > the   attachment helper and resources tool, presentation tool  
> > > > and  anyone  else using "content" in Sakai ends up there, then  
> > > > you must  implement  the ContentHostingService API defined in  
> > > > Sakai,  implemented by calls  to your Fedora, and then replace  
> > > > the impl.  we ship with Sakai with  yours.
> > > >
> > > > - Glenn
> > > >
> > > > Glenn R. Golden
> > > > Software Architect, University Of Michigan
> > > > ggolden@xxxxxxxxx
> > > >
> > > >
> > > >
> > > > On Apr 26, 2006, at 9:58 AM, Peter Murray wrote:
> > > >
> > > > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > > Hash: SHA1
> > > > >
> > > > > I'm still working my way around "Sakai-land" (if you will)   
> > > > > seeking the
> > > > > best way to integrate a Fedora-based content repository with  
> > > > > Sakai.
> > > > > I've had great conversations with Beth Kirschner from UMich and  
> > > > > Ben
> > > > > Brophy from MIT about their efforts.  Our desires differ from  
> > > > > those
> > > > > projects, though, in that we seek to make Fedora /the/ content
> > > > > repository for Sakai as opposed to a Sakai search/browse/ 
> > > > > retrieve/ edit
> > > > > tool for Fedora.
> > > > >
> > > > > I found a year-old document on Confluence with the title "Sakai
> > > > > Repository API Design"
> > > > > (http://bugs.sakaiproject.org/confluence/download/attachments/  
> > > > > 2852/ repository-design-v1.doc?version=1).
> > > > > It offers two integration points for the content repository:  a  
> > > > > "Rep
> > > > > API" and a "JSR-170 API".  I can find reference to JSR-170 as
> > > > > http://bugs.sakaiproject.org/jira/browse/REQ-210 but not   
> > > > > reference to
> > > > > the Repository API.  Help in navigating the Confluence and   
> > > > > Collab  sites
> > > > > would be most welcome.
> > > > >
> > > > > My thinking on the integration has evolved somewhat over the  
> > > > > past  few
> > > > > weeks (starting from the naive notion that providing an   
> > > > > implementation
> > > > > for legacy/Entity.java class would be all that is required) to   
> > > > > include
> > > > > these possibilities:
> > > > >
> > > > > * If the "Sakai Repository API Design" document of March 22, 2005,
> > > > > remains accurate, create a JSR-170 shim for Fedora (although, as
> > > > > the author of that document noted, "[Apache] Slide [a JSR-170
> > > > > implementation] will not have explicit support for the Sakai
> > > > > organization structure...needed [for] efficient interrogation
> > > > > of access permissions..."  Bridging access management structures
> > > > > will be a challenge, although I'm hoping (perhaps, again, naively
> > > > > so) that n-tier Shibboleth will help along these lines.
> > > > >
> > > > > * A Fedora shim that mimics the "Enterprise Repository   
> > > > > Implementation"
> > > > > in the design document.
> > > > >
> > > > > * Or, most radically and improbable, an implementation of  
> > > > > Hibernate
> > > > > over Fedora -- e.g., a object-relational-object storage structure.
> > > > >
> > > > > I'd like to try to firm up the possibilities within the next  
> > > > > few   days so
> > > > > as to include them on OhioLINK's Google Summer of Code idea  
> > > > > list for
> > > > > developing proofs-of-concepts (if not actual robust   
> > > > > implementations).
> > > > > (That list may have to include a suggestion for the JSR-170-to- 
> > > > > Sakai
> > > > > shim, if that doesn't already exist...and judging from the  
> > > > > Jira   issue it
> > > > > doesn't.)  Students will begin submitting applications on   
> > > > > Monday,  so it
> > > > > would be best if I can get it described by Friday.
> > > > >
> > > > >
> > > > > Thoughts?
> > > > >
> > > > > Peter
> > > > > - --
> > > > > Peter Murray                       http://www.pandc.org/peter/ 
> > > > > work/
> > > > > Assistant Director, Multimedia Systems  tel: 
> > > > > +1-614-728-3600;ext=338
> > > > > OhioLINK: the Ohio Library and Information Network   Columbus,  
> > > > > Ohio
> > > > > -----BEGIN PGP SIGNATURE-----
> > > > > Version: GnuPG v1.4.2 (Darwin)
> > > > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> > > > >
> > > > > iD8DBQFET3yf4+t4qSfPIHIRAtPQAJwIlAXVXIhWSHkhl0aR9tsu8pQSqACgpyLg
> > > > > w9+mMjMhPOI8SBaGe+brE2w=
> > > > > =OlgL
> > > > > -----END PGP SIGNATURE-----
> > > > >
> > > > > ----------------------
> > > > > This automatic notification message was sent by Sakai Collab    
> > > > > (http://collab.sakaiproject.org/portal) from the DG:  
> > > > > Development  site.
> > > > > You can modify how you receive notifications at My Workspace  
> > > > > >   Preferences.
> > > >
> > > > ----------------------
> > > > This automatic notification message was sent by Sakai Collab   
> > > > (http://collab.sakaiproject.org/portal) from the DG:  
> > > > Development  site.
> > > > You can modify how you receive notifications at My Workspace >   
> > > > Preferences.
> > >
> > >
> > >
> > > ----------------------
> > > This automatic notification message was sent by Sakai Collab   
> > > (http://collab.sakaiproject.org/portal) from the DG: Development  
> > > site.
> > > You can modify how you receive notifications at My Workspace >   
> > > Preferences.
> >
> > ----------------------
> > This automatic notification message was sent by Sakai Collab  
> > (http://collab.sakaiproject.org/portal) from the DG: Library &  
> > Repositiories site.
> > You can modify how you receive notifications at My Workspace >  
> > Preferences.

----------------------
This automatic notification message was sent by Sakai Collab 
(http://collab.sakaiproject.org/portal) from the DG: Development site.
You can modify how you receive notifications at My Workspace > Preferences.