1 / 30

Pete Johnston UKOLN, University of Bath Bath, BA2 7AY

The MEG Metadata Schemas Registry: Architecture & Data Model MEG Registry Workshop, Bath, 21 January 2003. Pete Johnston UKOLN, University of Bath Bath, BA2 7AY. p.johnston@ukoln.ac.uk http://www.ukoln.ac.uk/. UKOLN is supported by:. MEG Metadata Schemas Registry Architecture & Data Model.

danielah
Télécharger la présentation

Pete Johnston UKOLN, University of Bath Bath, BA2 7AY

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. The MEG Metadata Schemas Registry:Architecture & Data ModelMEG Registry Workshop, Bath, 21 January 2003 Pete Johnston UKOLN, University of Bath Bath, BA2 7AY p.johnston@ukoln.ac.uk http://www.ukoln.ac.uk/ UKOLN is supported by:

  2. MEG Metadata Schemas RegistryArchitecture & Data Model • Architecture • “What does it do? How does it work?” (briefly!) • Outline of functional components • Interfaces between components • Data model • “What are we talking about?” • Resources described • Relationships between resources • Attributes/properties of those resources MEG registry workshop,Bath, 21 January 2003

  3. The registry • Developed by (client) Damian Steer, (server) Dave Beckett (ILRT, University of Bristol) • Accepts machine-readable descriptions of (specific types of) resources • types of resource to be described • see data model (Element Sets, Elements etc) • descriptions stored in Schemas (RDF/XML) • publication API (HTTP POST) • Indexes those descriptions • Provides browse/search interfaces to those indexes for • human readers (HTML) • software tools • query API (HTTP GET) MEG registry workshop,Bath, 21 January 2003

  4. Information seekers Registry HTMLinterface today Registry Publish API (HTTP POST) Vocabulary managers MEG SCART(Client) Registry Query API (HTTP GET) Applications(including other Registries) Schemas (RDF/XML) MEG Registry(Server)

  5. Information seekers Vocabulary managers Other applications Registry HTMLinterface Registry Publish API (HTTP POST) Vocabulary managers MEG SCART(Client) MEG Registry(Server) Registry Query API (HTTP GET) Vocabulary managers Applications(including other Registries) Schemas (RDF/XML)

  6. The registry data model • A simplification of complexity • A basis for comparison • Classes of resource described • Element Sets • Elements • Encoding Schemes • Values in controlled vocabularies • Application Profiles • Element Usages • Descriptions stored in Schemas • Schemas themselves not described MEG registry workshop,Bath, 21 January 2003

  7. m 1 1 1 1 m m m m m 1 m m 1 1 m m 1 m m Agency Element Set Element Encoding Scheme Value Element Usage AppProfile

  8. Agency An organisation or individual responsible for managing one or more Element Sets, Application Profiles or Encoding Schemes • Relationships • Element Set --- is-Managed-By (m-1)  Agency • Encoding Scheme --- is-Managed-By (m-1)  Agency • Application Profile --- is-Managed-By (m-1)  Agency MEG registry workshop,Bath, 21 January 2003

  9. Agency properties MEG registry workshop,Bath, 21 January 2003

  10. Element Set A set of metadata Elements that is managed as a coherent unit by an Agency. The Elements of an Element Set are “functionally” related, by virtue of having been defined for the purpose of usefully describing the characteristics of a resource • Relationships • Element Set --- is-Managed-By (m-1)  Agency • Element --- is-Element-Of (m-1)  Element Set MEG registry workshop,Bath, 21 January 2003

  11. Element Set properties MEG registry workshop,Bath, 21 January 2003

  12. Element Set properties MEG registry workshop,Bath, 21 January 2003

  13. Element A formally defined term that is used to describe a characteristic or attribute of a resource • Relationships • Element --- is-Element-Of (m-1)  Element Set • Element --- associated-Encoding-Scheme (m-m)  Encoding Scheme • Element --- refines (m-1)  Element • Element Usage – uses (m-1)  Element MEG registry workshop,Bath, 21 January 2003

  14. Element properties MEG registry workshop,Bath, 21 January 2003

  15. Element properties MEG registry workshop,Bath, 21 January 2003

  16. Encoding Scheme • A set of contextual information or parsing rules that aids in the interpretation of the value of a metadata Element. Encoding Schemes include • controlled vocabularies, which enumerate a list of values, and; • formal notations or parsing rules, which define precisely how a lexical representation of a value is to be interpreted • Relationships • Encoding Scheme --- is-Managed-By Agency (m-1)  Agency • Element --- associated-Encoding-Scheme (m-m)  Encoding Scheme • Element Usage --- associated-Encoding-Scheme (m-m)  Encoding Scheme • Value – type (m-1)  Encoding Scheme MEG registry workshop,Bath, 21 January 2003

  17. Encoding Scheme properties MEG registry workshop,Bath, 21 January 2003

  18. Encoding Scheme properties MEG registry workshop,Bath, 21 January 2003

  19. Controlled Vocabulary Value An individual value or term in a controlled vocabulary • Relationships • Value – type (m-1)  Encoding Scheme MEG registry workshop,Bath, 21 January 2003

  20. Controlled Vocabulary Value properties MEG registry workshop,Bath, 21 January 2003

  21. Application Profile A set of Element Usages that is managed as a coherent unit by an Agency. An Application Profile is optimised for the resource description requirements of a particular application or context. Like the Elements of an Element Set, the Element Usages within an Application Profile are “functionally” related, by virtue of having been defined for the purpose of usefully describing a resource.Within an Application Profile, the Element Usages may reference Elements from multiple Element Sets MEG registry workshop,Bath, 21 January 2003

  22. Application Profile • Relationships • Application Profile --- is-Managed-By Agency (m-1)  Agency • Element Usage --- is-Usage-In (m-1)  Application Profile MEG registry workshop,Bath, 21 January 2003

  23. Application Profile properties MEG registry workshop,Bath, 21 January 2003

  24. Application Profile properties MEG registry workshop,Bath, 21 January 2003

  25. Element Usage • A deployment of a (previously defined) metadata Element in the context of a particular domain or application. The used Element may be tailored for the context by: • a narrowing of its semantic definition; • association with specified datatypes or Encoding Schemes; • specification of obligation/occurrence constraints • Relationships • Element Usage --- is-Usage-In (m-1)  Application Profile • Element Usage --- uses (m-1)  Element • Element Usage --- associated-Encoding-Scheme (m-m)  Encoding Scheme MEG registry workshop,Bath, 21 January 2003

  26. Element Usage properties MEG registry workshop,Bath, 21 January 2003

  27. Element Usage properties MEG registry workshop,Bath, 21 January 2003

  28. Key relations for Elements • An Element is-Element-Ofexactly one Element Set • An Element Usage is-Usage-Inexactly one Application Profile • An Element Usage uses exactly one Element • The several Element Usages in one Application Profile may use Elements from different Element Sets. MEG registry workshop,Bath, 21 January 2003

  29. In practice…. • Easier to understand by using the tools and seeing examples….. MEG registry workshop,Bath, 21 January 2003

  30. Acknowledgements • UKOLN is funded by Resource: the Council for Museums, Archives and Libraries, the Joint Information Systems Committee (JISC) of the UK higher and further education funding councils, as well as by project funding from the JISC and the European Union. UKOLN also receives support from the University of Bath where it is based. • http://www.ukoln.ac.uk/ MEG registry workshop,Bath, 21 January 2003

More Related