50 likes | 179 Vues
This document provides a comprehensive overview of schema-driven metadata software developed by Dr. Stephen Crawley and the eResearch Group at the University of Queensland. It covers essential components of schemas, including element names, values, structures, and constraints. It also discusses relationships with other schemas and ontologies, emphasizing the importance of versioning and validation. Additionally, recent tools such as MDE, MSF, and various annotation tools are evaluated. The document outlines future work, focusing on integrating schema types and enhancing annotation capabilities.
E N D
Dr Stephen Crawley,eResearch Group, ITEE University of Queensland Schemas and Schema-driven Metadata Software
What should be in a Schema? • Element names, labels, descriptions • Element values: types / patterns / value sets • Structures: flat / tree / graph, cardinality, etc • Complex constraints • Relationships with other schemas: inheritance, subtyping, composition, etc • Semantics: relationships with ontologies. • Schema versioning ...
Scope for Schema-driven Apps • Metadata entry and display • Validation of metadata • Mapping between metadata representations: • XML vs RDF vs <meta> vs ... • need representation independent schemas • Metadata conversion / schema versions • Extracting / harvesting metadata from other sources
Recent eResearch Group Tools • ARCHER metadata tools: • MDE: a schema driven (XML) metadata editor • MSF: tools for defining metadata schemas • MDSR: simple metadata schema repository • Pronto ontology repository • DIAS-B tools: • Danno annotation repository (annotea + ...) • Dannotate annotation tool • LORE annotation tool. • SourceForge project: “metadata-net”
Future Work • Schema-driven annotation tools • Annotation of objects (vs web pages) • Annotation of images, maps, etc • Integrate MDE/MSF and Danno/Dannotate • Support for more schema types in Pronto • Stand-alone editing, repository components • Completing the Annotea specification • Annotation schema work