ºÝºÝߣ

ºÝºÝߣShare a Scribd company logo

Interoperability Requirements for a Sustainable Component to Support Management and Sharing of Digital Resources

?
?
Martin Memmel
Martin Memmel

Platforms such as YouTube, Flickr or Delicious that allow users to manage and share different kinds of digital resources belong to the most popular applications in what is usually subsumed under the umbrella term Web 2.0. In the context of PLEs, the ability to manage and share digital resources used within a learning process is also one of the most important features. This paper gives a coarse overview of key aspects to consider when aiming to provide a sustainable, adaptable component for resource management and sharing that can be integrated into different, heterogeneous digital environments. The ALOE\footnote{see http://aloe-project.de} system will be presented as an example for the realisation of a respective component meeting the presented demands.

1 of 56
EFEPLE 2011 X X X Interoperability Requirements for a Sustainable Component to Support Management and Sharing of Digital Resources Martin Memmel Knowledge Management Group DFKI GmbH martin.memmel@dfki.de
EFEPLE 2011 How we've built an open, generic and adaptable resource sharing environment that survived (implications for PLEs: up to you!) Martin Memmel Knowledge Management Group DFKI GmbH martin.memmel@dfki.de
images documents (bmp, gif, jpg, png, tif, ¡­) (pdf, odt, odp, sxw, doc, ppt, ¡­) videos (avi, mpeg, mov, ¡­) web pages audio (aac, mp3, ¡­)
Key problems ¡ñ Heterogeneous tools for specific resource types ¡ñ Limited possibilites to integrate with other tools ¡ñ Only basic means to organise contributions ¡ñ Not instantiable ¡ñ No means to adapt to specific scenarios ¡ñ Support for (future) scenarios within PLEs?
How to ensure sustainability?
A comprehensive approach is needed ¡ñ Contribute arbitrary resources ¡ñ Manage arbitrary resources ¡ñ Share arbitrary resources ¡ñ Exchange of information! ¡ñ Adaptable for different scenarios!
Interoperability
Interoperability is the ability of two or more systems or components to exchange information and to use the information that has been exchanged. [IEEE, 1991]
Where to consider interoperability? ¡ñ Selection of supported application scenarios ¡ñ Resource types to be supported ¡ñ Metadata to be used ¡ñ Interfaces offered to users and other systems
Supported Application Scenarios [http://lsdis.cs.uga.edu/projects/glycomics/report/Report2006.html]
Resources images (bmp, gif, jpg, png, tif, ¡­) documents (pdf, odt, odp, sxw, doc, ppt, ¡­) videos (avi, mpeg, mov, ¡­) web pages audio (aac, mp3, ¡­)
Incorporation of resources ¡ñ Contribution of new / not yet accessible resources ¡ñ Integration of existing resources ¨C Maintenance issues ¨C Memory requirements ¨C Legal concerns ¡ú Repository and Refactory!
Metadata
Wittgenstein ¡®Die Bedeutung eines Wortes ist sein Gebrauch in der Sprache¡¯ (¡®The meaning of a word is its use in the language¡¯) Transferred into the world of (digital) resources: ¡®The meaning of a resource is its use in the community¡¯
Subjectivity and diversity ¡ñ No one-size-fits-all solutions ¡ñ Scenario-dependent metadata generation ¡ñ Human generated metadata ¡ñ Incorporation of potentially any kind of metadata
Metadata interoperability ¡ñ Using standards ¡ñ Extensibility ¡ñ Modularity ¡ñ Refinements ¡ñ Multilingualism ¡ñ Machine-processability
Interfaces
Interfaces ¨C Access by systems ¡ñ Low technical barriers for system usage ¨C Technical environments ¨C Minimal installation efforts ¡ñ Low conceptual barriers for system usage ¡ñ Access to potentially any data and functionalities ¨C Complex functionalities, mash-ups
User interfaces ¡ñ Offering access to data / functionalities in usual contexts and applications ¨C Services, Widgets, ¡­ ¡ñ Multilinguality ¡ñ Adaptability
http://aloe-project.de Sample infrastructure: ALOE ...how did it change and survive?
What is ALOE? ALOE is a generic infrastructure that allows ¡ñ supporting access to digital resources by means of social media technologies ¡ñ integrating social media technologies also in existing, especially traditional environments with no or only few interaction possibilities
http://aloe-project.de/AloeView
Interoperability Requirements for a Sustainable Component to Support Management and Sharing of Digital Resources
Interoperability Requirements for a Sustainable Component to Support Management and Sharing of Digital Resources
Information Exchange, Interfaces
Web Service API
Alternative: ALOE-XML <resource> <visibility>public</visibility> <title>Skyscrapers of glass and the curtain wall</title> <license></license> <description>Skyscrapers of glass and the curtain wall</description> <uri>http://winds-app.fit.fraunhofer.de/cgi- bin/WebObjects/windsoai.woa/wa/showContent?id=11647.lo</uri> <tags>skyscrapers curtain_wall Mies_van_der_Rohe winds mace </tags> <sharetogroups> <group>tmp</group> </sharetogroups> </resource>
Feeds
Information Mails
OAI Target
Bookmark Export
CAM Feedlet
Embedded Metadata
Widgets
Mobile Frontend
ALOE Resource Metadata Individual Metadata [1..¡Þ] Classification Tag [0..¡Þ] [0..¡Þ] Basic Metadata [1] Associated Comment Metadata [0..¡Þ] [0..¡Þ] Collection Rating [0..¡Þ] [0..¡Þ] Group Usage [0..¡Þ] Metadata [1]
Components, System Architecture
Interoperability Requirements for a Sustainable Component to Support Management and Sharing of Digital Resources
ALOE ¨C Used Technologies ¡ñ Implemented in Java (1.5), deployed in the Apache Tomcat (6.0) servlet container ¡ñ GUI: Realized with JSP using J2EE Design Patterns ¡ñ Web Service Interface: Functionalities are accessible via a SOAP/REST API realized with Apache Axis2 ¡ñ Storage of resources and metadata in a MySQL data base (5.0)
Evolvability, Adaptability
Evolvability for artifacts is the capacity of the systems, organizations and networks producing them to give rise to adaptive variants that flexibly meet changing requirements over the course of long-term change. [Nehaniv et al., 2006]
Requirements? Environments? ¡ñ What's the ecosystem? ¡ñ What does surviving mean? ¨C Active users, developers ¡ñ In which way are resources finite? ¨C Developers, time, infrastructure
http://openeer.dfki.de
http://icdar09.dfki.uni-kl.de
Interoperability Requirements for a Sustainable Component to Support Management and Sharing of Digital Resources
https://mindpool.dfki.de
http://aloe-cmcm.dfki.uni-kl.de
Interoperability Requirements for a Sustainable Component to Support Management and Sharing of Digital Resources
The MACE Portal 49
MACE Facetted Search 50
MACE Detail Page 51
MACE Community Page 52
http://www.dfki.de/radar
Interoperability Requirements for a Sustainable Component to Support Management and Sharing of Digital Resources
Conclusions ¡ñ Realise a concrete solution ¨C but always try to be as generic as possible ¡ñ Try to be independent ¡ñ Be open, don't build another silo ¡ñ Think carefully about what is your core, and what are your branch-specific adaptations ¡ñ Build tools for setup and deployment ¡ñ Take your time for refactoring ¡ñ Don't trust your memory, write down stuff
Thanks for listening! ALOE: http://aloe-project.de MACE: http://www.mace-project.eu RADAR: http://www.dfki.de/radar mailto: memmel@dfki.de

More Related Content

Interoperability Requirements for a Sustainable Component to Support Management and Sharing of Digital Resources

  • 1. EFEPLE 2011 X X X Interoperability Requirements for a Sustainable Component to Support Management and Sharing of Digital Resources Martin Memmel Knowledge Management Group DFKI GmbH martin.memmel@dfki.de
  • 2. EFEPLE 2011 How we've built an open, generic and adaptable resource sharing environment that survived (implications for PLEs: up to you!) Martin Memmel Knowledge Management Group DFKI GmbH martin.memmel@dfki.de
  • 3. images documents (bmp, gif, jpg, png, tif, ¡­) (pdf, odt, odp, sxw, doc, ppt, ¡­) videos (avi, mpeg, mov, ¡­) web pages audio (aac, mp3, ¡­)
  • 4. Key problems ¡ñ Heterogeneous tools for specific resource types ¡ñ Limited possibilites to integrate with other tools ¡ñ Only basic means to organise contributions ¡ñ Not instantiable ¡ñ No means to adapt to specific scenarios ¡ñ Support for (future) scenarios within PLEs?
  • 5. How to ensure sustainability?
  • 6. A comprehensive approach is needed ¡ñ Contribute arbitrary resources ¡ñ Manage arbitrary resources ¡ñ Share arbitrary resources ¡ñ Exchange of information! ¡ñ Adaptable for different scenarios!
  • 8. Interoperability is the ability of two or more systems or components to exchange information and to use the information that has been exchanged. [IEEE, 1991]
  • 9. Where to consider interoperability? ¡ñ Selection of supported application scenarios ¡ñ Resource types to be supported ¡ñ Metadata to be used ¡ñ Interfaces offered to users and other systems
  • 11. Resources images (bmp, gif, jpg, png, tif, ¡­) documents (pdf, odt, odp, sxw, doc, ppt, ¡­) videos (avi, mpeg, mov, ¡­) web pages audio (aac, mp3, ¡­)
  • 12. Incorporation of resources ¡ñ Contribution of new / not yet accessible resources ¡ñ Integration of existing resources ¨C Maintenance issues ¨C Memory requirements ¨C Legal concerns ¡ú Repository and Refactory!
  • 14. Wittgenstein ¡®Die Bedeutung eines Wortes ist sein Gebrauch in der Sprache¡¯ (¡®The meaning of a word is its use in the language¡¯) Transferred into the world of (digital) resources: ¡®The meaning of a resource is its use in the community¡¯
  • 15. Subjectivity and diversity ¡ñ No one-size-fits-all solutions ¡ñ Scenario-dependent metadata generation ¡ñ Human generated metadata ¡ñ Incorporation of potentially any kind of metadata
  • 16. Metadata interoperability ¡ñ Using standards ¡ñ Extensibility ¡ñ Modularity ¡ñ Refinements ¡ñ Multilingualism ¡ñ Machine-processability
  • 18. Interfaces ¨C Access by systems ¡ñ Low technical barriers for system usage ¨C Technical environments ¨C Minimal installation efforts ¡ñ Low conceptual barriers for system usage ¡ñ Access to potentially any data and functionalities ¨C Complex functionalities, mash-ups
  • 19. User interfaces ¡ñ Offering access to data / functionalities in usual contexts and applications ¨C Services, Widgets, ¡­ ¡ñ Multilinguality ¡ñ Adaptability
  • 20. http://aloe-project.de Sample infrastructure: ALOE ...how did it change and survive?
  • 21. What is ALOE? ALOE is a generic infrastructure that allows ¡ñ supporting access to digital resources by means of social media technologies ¡ñ integrating social media technologies also in existing, especially traditional environments with no or only few interaction possibilities
  • 25. Information Exchange, Interfaces
  • 27. Alternative: ALOE-XML <resource> <visibility>public</visibility> <title>Skyscrapers of glass and the curtain wall</title> <license></license> <description>Skyscrapers of glass and the curtain wall</description> <uri>http://winds-app.fit.fraunhofer.de/cgi- bin/WebObjects/windsoai.woa/wa/showContent?id=11647.lo</uri> <tags>skyscrapers curtain_wall Mies_van_der_Rohe winds mace </tags> <sharetogroups> <group>tmp</group> </sharetogroups> </resource>
  • 28. Feeds
  • 36. ALOE Resource Metadata Individual Metadata [1..¡Þ] Classification Tag [0..¡Þ] [0..¡Þ] Basic Metadata [1] Associated Comment Metadata [0..¡Þ] [0..¡Þ] Collection Rating [0..¡Þ] [0..¡Þ] Group Usage [0..¡Þ] Metadata [1]
  • 39. ALOE ¨C Used Technologies ¡ñ Implemented in Java (1.5), deployed in the Apache Tomcat (6.0) servlet container ¡ñ GUI: Realized with JSP using J2EE Design Patterns ¡ñ Web Service Interface: Functionalities are accessible via a SOAP/REST API realized with Apache Axis2 ¡ñ Storage of resources and metadata in a MySQL data base (5.0)
  • 41. Evolvability for artifacts is the capacity of the systems, organizations and networks producing them to give rise to adaptive variants that flexibly meet changing requirements over the course of long-term change. [Nehaniv et al., 2006]
  • 42. Requirements? Environments? ¡ñ What's the ecosystem? ¡ñ What does surviving mean? ¨C Active users, developers ¡ñ In which way are resources finite? ¨C Developers, time, infrastructure
  • 55. Conclusions ¡ñ Realise a concrete solution ¨C but always try to be as generic as possible ¡ñ Try to be independent ¡ñ Be open, don't build another silo ¡ñ Think carefully about what is your core, and what are your branch-specific adaptations ¡ñ Build tools for setup and deployment ¡ñ Take your time for refactoring ¡ñ Don't trust your memory, write down stuff
  • 56. Thanks for listening! ALOE: http://aloe-project.de MACE: http://www.mace-project.eu RADAR: http://www.dfki.de/radar mailto: memmel@dfki.de