From Corrib Clan Wiki

Contents 1 Architecture of WMap Portal 1.1 Use Cases 1.1.1 General Use Case Diagram 1.1.2 Ontology Management API Class Diagram 1.1.3 Ontology Lifecycle 1.2 Layer Cake General Architecture 1.3 Support for Negotiations with Ontology Versioning Subsystem 1.4 Mapping Rules Lifecycle

Architecture of WMap Portal

Use Cases

General Use Case Diagram

Ontology Management API Class Diagram

Ontology Lifecycle

Layer Cake General Architecture

Support for Negotiations with Ontology Versioning Subsystem

This is a slightly changed and polished conception of the flow of negotiations, suggestions etc in WMap. Note that the difference now are:

• each ontology version, suggestion, version of suggestions has a URI
• the suggestion is not a diff towards the given ontology version, but a version ontology WITH this diff applied
• each new version of suggestion is a version of ontology with diff path applied
• at the step of generating new version of ontology, it is possible to present ad-hoc ontologies with all path of diffs selected reflecting suggestions added to this ontology

Mapping Rules Lifecycle

So far I have thought after the talk with Max that it would be wise to change the format of mapping rules from XML to RDF. The next version of RDFT will have the support for the rules described in RDF as well (comming soon). It will enables us to use a single versioning mechanism for both ontologies and mapping rules.