1 / 7

Ontology Versioning Tool DIP D2.4

Discusses versioning tool for ontology management, featuring version control, metadata, UI requirements, and future work on version validation, analysis, and propagation. Initial API and WSMO4J limits are outlined, along with a demo overview.

stovar
Download Presentation

Ontology Versioning Tool DIP D2.4

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. Ontology Versioning ToolDIP D2.4 Jacek Kopecký jacek.kopecky@deri.org SDK meeting, Grenoble, April 2005

  2. Ontology Versioning Tool • Already said by Pieter De Leenheer • Management of versions of ontologies • Also applicable for instance data • Versioning library over WSMO API • First prototype delivered, demo to come • GUI support in editing & browsing tool • DIP D2.3 in early stage • Not yet done SDK meeting Grenoble 2005, jacek.kopecky@deri.org

  3. Versioning Tool Initial Requirements • Version identification • Creating new version • Version metadata • E.g. version creator, date of creation etc. • UI requirements • Version browsing • Transformation editing (future) • Notification agent (future) SDK meeting Grenoble 2005, jacek.kopecky@deri.org

  4. Future Work • Versioning support in a repository • Listing available versions • Accessing latest or concrete version • Version validation • Formal transformation specification • Difference analysis • Impact analysis • Change propagation SDK meeting Grenoble 2005, jacek.kopecky@deri.org

  5. Initial Versioning Library API • Version ID = number in a string • Appended to URI path after comma • http://example.com/sampleOntology,3 • Usually in the namespace (if ending with #) • http://example.com/sampleOntology,3#concept • Extensible version metadata • Creator, date, comment, non-func properties • Explicit commit or drop of changes • The rest is WSMO API SDK meeting Grenoble 2005, jacek.kopecky@deri.org

  6. WSMO4J Limits • Hacked factory for parser • No repository • No calls getAllVersions(id), getLatestVersion(id) • Parsed ontology redundancy • Two instances of concept Person • xsd:string within the ontology • Either sent or to be sent to wsmo4j list SDK meeting Grenoble 2005, jacek.kopecky@deri.org

  7. Demo Overview • Watching the versions in a simple process: • Parse an example ontology • Change it • Drop the changes • Reintroduce the changes • Commit them • Do more changes SDK meeting Grenoble 2005, jacek.kopecky@deri.org

More Related