Semantic Interoperability problem of OSS Forges


Published on

The presentation was given at the ICSEA 2009 and refers to the paper (with the same title) submitted for the conference. The abstract of the paper is following: "Interoperability between collaborative development platforms (forges) in the Open Source Software world is a significant issue. The forges tend to follow the lock-in phenomenon, providing no easy-to-use facilities for migrating projects or their parts between forge platforms. To facilitate the process of cross-forge project migration, the following paper presents an approach of lifting forge data models to the semantic level and applying rule-based mappings for their alignment. The approach also involves Semantic Web Services to handle the process of importing/exporting project metadata from/to Open Source Software forges. Finally, the paper demonstrates the approach on the basis of proof-of-concept implementation exploiting the existing forges and presents the lessons learnt.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Semantic Interoperability problem of OSS Forges

  1. 1. Bartosz Lewandowski , Alicja Ciemniewska, Paweł Kędziora, Cezary Mazurek Poznan Supercomputing and Networking Center (PSNC), Poland Semantic Interoperability problem of OSS Forges.
  2. 2. Outline <ul><li>Motivation </li></ul><ul><li>Objectives </li></ul><ul><li>Problem Area </li></ul><ul><li>Approach </li></ul><ul><li>Outcomes </li></ul><ul><li>Conclusions & outlook </li></ul>
  3. 3. Motivation <ul><li>Fostering the idea for supporting interoperability in OSS field. </li></ul><ul><li>Limited interoperability of forges. </li></ul><ul><li>Forge lock-in phenomenon. </li></ul><ul><li>Lack of cross-forge migration facilities. </li></ul><ul><li>Focusing on semantic interoperability challenge: differences in Forge information models. </li></ul>
  4. 4. <ul><li>investigate and demonstrate how semantic interoperability approaches and technologies can be used to deal with the variety of software , services and actors in the OSS domain . </li></ul><ul><li>enable the process of migrating OSS project metadata between forge platforms at the semantic level by </li></ul><ul><li>introducing semantic enhancements to forge platforms </li></ul><ul><li>exploiting semantic technologies to facilitate the transition of OSS project metadata between forges. </li></ul>Objectives
  5. 5. Problem area <ul><li>More than 50 public and active forge instances in Europe </li></ul><ul><li>certain degree of interoperability desirable (e.g. cross-forge search or cross-forge migration) </li></ul><ul><li>Technical but also a semantic interoperability challenge </li></ul><ul><ul><li>Differences in schemas and granularity of e . g. software categorizations, different skill terminologies, languages etc. </li></ul></ul>
  6. 6. Problem area
  7. 7. The approach
  8. 8. The approach Importing phase Mapping phase Exporting phase
  9. 9. Approach. Sample migration. OSS project metadata migration from BerliOS to Gforge.
  10. 10. Outcomes <ul><li>The use of semantic technologies for loose coupling of heterogenous forge information models. </li></ul><ul><li>The proof-of-concept implementation based on scenario between existing forges: BerliOS and Gforge. </li></ul><ul><li>Scenario-based PoC identifies potential enhancements of Forges. </li></ul><ul><li>QualiPSo, Semantic Interoperability deliverables and the other results available at: </li></ul>
  11. 11. Issues & limitations <ul><li>Forge related: </li></ul><ul><li>Missing ontologies provided by forge platforms, </li></ul><ul><li>Lack of WSDL interfaces of forges. </li></ul><ul><li>Semantic technology related: </li></ul><ul><li>OWL-DL compliance of ontologies required by reasoning engines (Pellet), </li></ul><ul><li>Limitations on complexity of parameters of Semantic Web Services (OWL-S Mindswap API), </li></ul><ul><li>No significant progress in improvement/development of OWL-S APIs </li></ul>
  12. 12. Conclusions & outlook <ul><li>Modeling the project information hosted by forges: </li></ul><ul><li>Introduction of OWL-based ontologies provides a standard way for modeling project-related information. </li></ul><ul><li>Efficient modeling through concept-related features: e.g., polymorphism and inheritance. </li></ul><ul><li>Introduces the inference capabilities on OWL concepts. </li></ul><ul><li>The use of semantic mapping techniques for harmonization of heterogeneous information models . (rule-based language) ( working on a higher level of abstraction ) </li></ul>
  13. 13. Conclusions & outlook <ul><li>Increasing forge interoperability: </li></ul><ul><li>Highlighting a need for using concepts of SOA and SCA in forge architectures. </li></ul><ul><li>Exposing forge functionality through WSDL interfaces </li></ul><ul><li>The introduction of OWL-S enhancements as another layer of abstraction on top of SOAP interfaces. </li></ul><ul><li>Possibility to introduce the composition of Semantic Web Services as a top layer for managing the migration process. </li></ul>
  14. 14. Outlook & update <ul><li>Inclination towards open interfaces: </li></ul><ul><li>GForge SOAP API (commercial), </li></ul><ul><li>Facebook SOAP API, </li></ul><ul><li>Google: data liberation trend. </li></ul><ul><li>Social networks vs. Collaborative Environments: </li></ul><ul><ul><li>free your data vs. free your OSS project artefacts. </li></ul></ul>
  15. 15. Thank you! [email_address]