Interoperability Requirements for a Sustainable Component to Support Management and Sharing of Digital Resources
0 likes888 views
The document discusses the design and implementation of the Aloe infrastructure, aimed at enhancing the sharing and management of digital resources through interoperability and adaptability. It addresses challenges with heterogeneous tools, metadata, and system integration, while proposing solutions to ensure sustainability and support for diverse application scenarios. Key features include a web service API, modular architecture, and a focus on user-friendly interfaces, all to facilitate resource exchange and interaction within various environments.
![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]](https://image.slidesharecdn.com/20110330efeple-110402063527-phpapp02/85/Interoperability-Requirements-for-a-Sustainable-Component-to-Support-Management-and-Sharing-of-Digital-Resources-8-320.jpg)
![Supported Application Scenarios
[http://lsdis.cs.uga.edu/projects/glycomics/report/Report2006.html]](https://image.slidesharecdn.com/20110330efeple-110402063527-phpapp02/85/Interoperability-Requirements-for-a-Sustainable-Component-to-Support-Management-and-Sharing-of-Digital-Resources-10-320.jpg)
![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]](https://image.slidesharecdn.com/20110330efeple-110402063527-phpapp02/85/Interoperability-Requirements-for-a-Sustainable-Component-to-Support-Management-and-Sharing-of-Digital-Resources-36-320.jpg)
![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]](https://image.slidesharecdn.com/20110330efeple-110402063527-phpapp02/85/Interoperability-Requirements-for-a-Sustainable-Component-to-Support-Management-and-Sharing-of-Digital-Resources-41-320.jpg)
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
- 10. Supported Application Scenarios [http://lsdis.cs.uga.edu/projects/glycomics/report/Report2006.html]
- 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 Maintenance issues Memory requirements Legal concerns Repository and Refactory!
- 13. Metadata
- 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
- 17. Interfaces
- 18. Interfaces Access by systems Low technical barriers for system usage Technical environments Minimal installation efforts Low conceptual barriers for system usage Access to potentially any data and functionalities Complex functionalities, mash-ups
- 19. User interfaces Offering access to data / functionalities in usual contexts and applications 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
- 26. Web Service API
- 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
- 30. OAI Target
- 31. Bookmark Export
- 32. CAM Feedlet
- 34. Widgets
- 35. Mobile Frontend
- 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 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? Active users, developers In which way are resources finite? Developers, time, infrastructure
- 55. Conclusions Realise a concrete solution 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