SlideShare a Scribd company logo

Metadata Working Group - Status update

•Download as PPT, PDF•
•
EDINA, University of Edinburgh
EDINA, University of Edinburgh

Presentation given by James Reid at the UK location Information Interoperbaility Board, 14th October 2010.

Related slideshows

OGC Interoperability Experiments and Authentication
OGC Interoperability Experiments and AuthenticationOGC Interoperability Experiments and Authentication
OGC Interoperability Experiments and Authentication
 
Access Control in ESDIN: Shibboleth
Access Control in ESDIN: ShibbolethAccess Control in ESDIN: Shibboleth
Access Control in ESDIN: Shibboleth
 
Some Academic Sector/NMCA outcomes from the OGC Web Service Shibboleth Intero...
Some Academic Sector/NMCA outcomes from the OGC Web Service Shibboleth Intero...Some Academic Sector/NMCA outcomes from the OGC Web Service Shibboleth Intero...
Some Academic Sector/NMCA outcomes from the OGC Web Service Shibboleth Intero...
 
1 of 7
Metadata Working Group - Status update James Reid, EDINA,University of Edinburgh
GEMINI 2.1 update • GEMINI 2.1 published after consultation process • 27 comments , 6 organisations • No substantive additional amendments • Documentation – Parts 1 & 2 of the Guidelines have been updated to reflect 2.1. Part 3 (Data Quality) is still being finalised • Additional documentation: – GEMINI 2.1 Schematron Schema & Technical Documentation – Encoding Technical Guidance LIIB No 6 14 October 2010 London 2
Role in Evaluation of Metadata Editor • Evaluation group is wider than just MDWG members • Includes English Heritage (Defra and LPSNI) • Eval group feedback being recorded in OS bug tracker • Still inputting and critiquing – ongoing MDWG concern over disjoint between documentation and realisation on UI LIIB No 6 14 October 2010 London 3
MDWG Recommendations for LIIB Approval • MDWG recommend that the UKLP should document on the UKLP web site the complete set of documents for GEMINI2.1 (AGI docs + OS doc set) • MDWG recommend UKLP to request AGI to do likewise (at least to have off- sire links to non-AGI docs) • MDWG recommend that an update process/plan be put in place for ensuring transparency in the synchronicity of documentation set given split governance -the current encoding guidelines are owned by UKLP, the Guidelines by AGI. • Clarification issue. How far can documents posted on Huddle be circulated within members organisations? • Registries. The relationship to data.gov and the CKAN definition of 'registry' are at variance. Can UKLP leverage data.gov to ensure representation on the MDWG to assist in resolving inconsistencies. LIIB No 6 14 October 2010 London 4
LIIB No 4 23 April 2010 London From extents tab
LIIB No 4 23 April 2010 London From conformity tab
LIIB No 4 23 April 2010 London From data about metadata tab

More Related Content

Metadata Working Group - Status update

  • 1. Metadata Working Group - Status update James Reid, EDINA,University of Edinburgh
  • 2. GEMINI 2.1 update • GEMINI 2.1 published after consultation process • 27 comments , 6 organisations • No substantive additional amendments • Documentation – Parts 1 & 2 of the Guidelines have been updated to reflect 2.1. Part 3 (Data Quality) is still being finalised • Additional documentation: – GEMINI 2.1 Schematron Schema & Technical Documentation – Encoding Technical Guidance LIIB No 6 14 October 2010 London 2
  • 3. Role in Evaluation of Metadata Editor • Evaluation group is wider than just MDWG members • Includes English Heritage (Defra and LPSNI) • Eval group feedback being recorded in OS bug tracker • Still inputting and critiquing – ongoing MDWG concern over disjoint between documentation and realisation on UI LIIB No 6 14 October 2010 London 3
  • 4. MDWG Recommendations for LIIB Approval • MDWG recommend that the UKLP should document on the UKLP web site the complete set of documents for GEMINI2.1 (AGI docs + OS doc set) • MDWG recommend UKLP to request AGI to do likewise (at least to have off- sire links to non-AGI docs) • MDWG recommend that an update process/plan be put in place for ensuring transparency in the synchronicity of documentation set given split governance -the current encoding guidelines are owned by UKLP, the Guidelines by AGI. • Clarification issue. How far can documents posted on Huddle be circulated within members organisations? • Registries. The relationship to data.gov and the CKAN definition of 'registry' are at variance. Can UKLP leverage data.gov to ensure representation on the MDWG to assist in resolving inconsistencies. LIIB No 6 14 October 2010 London 4
  • 5. LIIB No 4 23 April 2010 London From extents tab
  • 6. LIIB No 4 23 April 2010 London From conformity tab
  • 7. LIIB No 4 23 April 2010 London From data about metadata tab