1. UKOLN is supported by: The JISC Information Environment Metadata Schema Registry (IEMSR): Update DC-2006, Manzanillo, Mexico October 3-6, 2006 Rachel Heery Deputy Director R&D, UKOLN www.bath.ac.uk A centre of expertise in digital informaion management

2. IEMSR project background Funded by the UK Joint Information Systems Committee (JISC) as part of shared infrastructure programme until 2009 Development partners –ILRT, University of Bristol –UKOLN, University of Bath Associate partners –British Library –Becta (British Educational Communications and Technology Agency) –CETIS (Centre for Educational Technology Interoperability Standards) http://www.ukoln.ac.uk/projects/iemsr/

3. IEMSR prototype: distinctive features Focus on access to application profiles –Dublin Core and IEEE LOM (2 different data models!) – Uses underlying application profile data model –RDF application Registers both vocabularies and application profiles at level of vocabulary, application profile and terms (how terms are used locally) Provides web and automated m2m interface Provides desktop client for creation and registration of vocabularies and application profiles

4. Progress to date Prototype Registry service components –Registry server –Registry web site –Data creation tool Development documentation –Scenarios and Use Cases –Functional requirements and data model Test data –DC and LOM vocabularies and application profiles Marketing proposition –Stakeholder analysis and engagement

5. IEMSR web interface

6. Web interface to registry server

7. OAI-DC application profile

8. IEMSR data creation tool

9. Query registry server

10. Select property to use

11. Describe how property used in this DCAP

12. Query again; select again

13. IEMSR: Use Scenarios Content provision service discloses application profile Metadata schema developer explores existing implementation choices, reuses existing components Metadata creation tool accesses machine-readable description of selected application profile Aggregation or presentation service accesses information about an application profile

14. Stakeholder analysis StakeholdersUses Application profile creators Discovery and re-use of existing terms and vocabularies Service and system developers Discovery and access Data curators and service providers Access to machine readable application profiles and vocabularies CataloguersDiscovery and access FundersPromote re-use, quality assurance, preservation of vocabularies Commercial suppliers of software products Access to machine readable application profiles and vocabularies Other registriesRe-use of source code, consensus on application profiles

15. IEMSR stakeholder engagement plan

16. Issues, challenges, thoughts Complexity of working with multiple meta- models –Ongoing discussions between DCMI and IEEE LOM communities Centralised v distributed registry services –IEMSR as "semi-distributed" Reads/indexes data distributed on Web But single point of provision of service –Distributed model?

17. Future plans Review software –Collaboration? Review data model –Collaboration Stakeholder engagement –Meeting needs of users Moving project to service –Phased service delivery Dealing with DC and LOM –Separate registries? –Track joint IEEE LTSC and DC work

18. For more information http://www.ukoln.ac.uk/projects/iemsr/2wp4/ Thank you! http://www.ukoln.ac.uk/projects/iemsr/2wp4/