1 / 21

SCHEMAS Forum for metadata schema implementers

SCHEMAS Forum for metadata schema implementers. The SCHEMAS project and metadata ETB Workshop, London, 9-10 January 2001 Michael Day, m.day@ukoln.ac.uk. Contents. Project overview Audience, needs, SCHEMAS project offerings, some results to date The SCHEMAS metadata registry

lewis
Download Presentation

SCHEMAS Forum for metadata schema implementers

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. SCHEMASForum for metadata schema implementers The SCHEMAS project and metadata ETB Workshop, London, 9-10 January 2001 Michael Day, m.day@ukoln.ac.uk

  2. Contents • Project overview • Audience, needs, SCHEMAS project offerings, some results to date • The SCHEMAS metadata registry • Objectives, approaches, implementation and functions • Application profiles • Some definitions

  3. Partners • PricewaterhouseCoopers Technology Consultants (PwC) • German National Research Centre for Information Technology (GMD) • UK Office for Library and Information Networking, University of Bath (UKOLN)

  4. Audience • Who? • Metadata schema designers • Projects under the EU’s IST programme (Multimedia Content and Tools) and national initiatives • What for? • Information, guidance and tools for the description of Web resources of all kinds • Helping designers to use what is already there

  5. Industry Publishing and rights management Audio-visual production and distribution Cultural heritage Education Research Academic services Geospatial information Other (e.g. Government) Domains • Not just Dublin Core • No ‘best way’ of doing things

  6. Needs • General need for: • Standard methods for content description • Multiplicity of schemas, mixing and matching general and specific sets • But: • There is some duplication of effort, competition between standards and schemas • Potential confusion for implementers

  7. Re-use • Why re-use existing schemas? • Not re-inventing wheels • Potential use of standard tools • Higher potential interoperability • End result: • Reduction of cost, now and in the future • Enlarging the potential audience • Interoperability

  8. The information gap • Metadata schemas already identified: • Over 200 implementation activities • Around 90 standardisation activities • Very different levels of information • Conclusions: • Good information about schemas is badly needed • Need for mutual understanding, hopefully leading to harmonisation

  9. SCHEMAS provides ... • Information provision • Metadata Watch Reports • Standards Framework Reports • Guidance material • Workshops • Registry implementation • Schemas, application profiles, people, projects, standards, tools, guidelines

  10. SCHEMAS results First Workshop (Bath, June 2000) - report http://www.schemas-forum.org/workshops/ Metadata Watch Reports: #1 (July 2000), #2 (September 2000), #3 (November 2000)http://www.schemas-forum.org/metadata-watch/ Standards Framework Report: #1 (Sept. 2000) http://www.schemas-forum.org/stds-framework/ Second Workshop (Bonn, November 2000)

  11. SCHEMAS Registry • Experience with prototype registry developed by DESIRE II project • The registry is the place to publish metadata schemas: • ‘namespace schemas’ • ‘application profile schemas’ • As well as other information about schemas, e.g.: • standards, projects, people, tools, etc.

  12. Thick registry Namespace schema App profile Mapping Thick Registry Usage guide Sample data Users Software tools

  13. Thin registry Namespace schema Mapping App profile Sample data Usage guide Thin Registry Software tools Users

  14. Registry approach • The SCHEMAS registry will be: • a ‘thick registry’ initially, with schemas registered at a central location • develop into a ‘thin registry’ in the future, with pointers to schemas on the Web • The technical basis will be: • RDF Schemas • EOR toolkit

  15. EOR Toolkit

  16. Registry functions • Registration • schemas from European projects and initiatives • information and reviews from SCHEMAS domain correspondents • Searching • Finding application profiles for re-use • Finding information and guidance

  17. Application profiles • What is an application profile? • a schema identifying the use of elements from one or more namespaces in a particular application, with additional constraints • What is it used for? • To publish this information for a human audience • To help software configure

  18. Profile process • Common steps in defining profile • identify requirements for descriptive elements • find appropriate standard • link required elements to standard elements where possible • define remaining elements and/or qualifiers in private namespace • link remaining elements

  19. Contacts Makx Dekkers mdekkers@lu.pwcglobal.com Rachel Heery r.heery@ukoln.ac.uk Tom Baker thomas.baker@gmd.de Web site: http://www.schemas-forum.org/

  20. Acknowledgements Based on a presentation given by Makx Dekkers (PricewaterhouseCoopers) at the MALVINE and LEAF conference: Gateways to Europe’s Cultural Heritage, Staatsbibliothek zu Berlin, 4-5 December 2000. http://www.sbb.spk-berlin.de/malvine/agenda/schemas.html

More Related