1 / 10

OOR in the Classroom An Experience Report

This report discusses techniques for promoting Open Ontology Repository (OOR) adoption, including personal contacts, mandates, user-friendly tools, and classroom materials.

kgreer
Download Presentation

OOR in the Classroom An Experience Report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OOR in the ClassroomAn Experience Report Ken Baclawski Northeastern University

  2. OOR Promotion • Techniques for promoting OOR • Personal contacts (bottom-up) • Mandates (top-down) • User-friendly tools and GUIs (lower the bar) • Classroom materials (raise awareness) • This is a report on developing classroom materials • Provides useful feedback as a side-effect

  3. Typical Course Assignments • Course topic: component software with SOA • UML model for the OOR as a web service • XSLT transformations for OOR results • Develop marshalling and basic semantics • Develop a rudimentary OOR • Initially RESTful, later SOAP based • Federate OOR instances • Compose with other services

  4. Issue: Storage Model • Current storage model • Defined implicitly by program • Language dependent • Better storage model • Formally defined by an ontology • Additional benefits • Better understanding and documentation of OOR • Important for federation and interoperability

  5. Issue: Identifiers • Currently identifiers are integers • Not clear how they are generated • Multiple codes/identifiers • A standard for names/identifiers is needed • Essential for federated OOR instances • Useful for interoperability

  6. Issue: Basic Semantics • The most basic level of semantics is equality: when two entities are the same. • Students are given the task of determining when two ontology labels (metadata only) are the same. • No formal definition so task is not well-defined • Equality of XML (infosets) is obviously not correct • Must separate fundamental attributes from incidental ones • Formal semantics would resolve this issue

  7. Issue: Marshalling • Students develop serialization and deserialization using type mappings • Current approach • Procedural definition • Programming language dependent • Better approach • Formal specification of transformation • Unfortunately, ontologies are not designed for this

  8. Issue: Service Specification • Current model is RESTful • Informally defined • Request parameters are encoded in a URL • Result is encoded in XML • Better model • Formal definition with ontologies • Request and result use RDF • Compatible with WSDL

  9. Issue: Transformations • OOR requires multiple representations for ontologies and metadata • Two-way transformations are necessary • Invertibility would be ideal but usually impossible • Naïve transformations are usually unbounded • An attainable goal is stable transformations but these require annotations and not all languages can be extended to accommodate annotations. • Students explore two-way transformations but this is a difficult research problem in general.

  10. Future Issues • Ontology configurations • Situation semantics • OOR component architecture

More Related