Vocabulary Mapping Framework

Tertius Ltd / International DOI Foundation

Norman Paskin

London Nov 9 2009

Next Steps

Origins: indecs-inspired work: • http://en.wikipedia.org/wiki/Indecs_Content_Model

RDA/ONIX Framework for resource categorisation• http://www.dlib.org/dlib/january07/dunsire/01dunsire.html

ISO/IEC 21000-6 Rights Data Dictionary • http://iso21000-6.net/ • includes typed links between identifiers (relators) to support MPEG-21• produced managed dictionary (but little used)

Parallel activities in other areas recognising same issues

Led to VMF original proposal to JISC September 2008

Origins

3 stages: • Stage 1 became the current VMF work. • Stages 2 and 3 outlined a road map for immediate next steps.

Stage 1 (funded in current VMF project): basic extension of RDA/ONIX Framework • “The deliverable of stage 1 will be a major expansion of the existing RDA/ONIX

Framework, based on and incorporating relevant vocabularies from nine main bibliographic and supply chain metadata standards of interest to the JISC community”

Stage 2: further technical work: • Aims: - give the project a base level of ongoing activity on existing content - allow for initial roll-out, trial use, and feedback• Action: - continued work on agreeing mappings, development of uses, rules, tools, etc. Stage 3: governance and maintenance of what has been achieved • Aims: - avoid the work becomes a dead-end project - provide a usable platform and a guarantee of stability • Action: - funding for maintenance of the Framework for one year - put long term model in place thereafter

VMF project proposal 2008 (to JISC)

• continued work on mapping– in particular agreeing the initial vocabulary mappings with the technical

representatives of the schemes. Cost £20K?

• automated generation of mappings – in current content, rules development and output: Cost £20K?

• extension of content: – self-funded?– interim governance/maintenance while this goes on

• we have created a powerful resource for vocabulary mapping and to support development and refinement of vocabularies

– need to work with it and allow user communities decide how they want to use it and shape it

• Feedback needed: what do you think you would use it for?

Further technical work

• A “detailed governance model, with support from participating standards where possible” is part of Stage 1

– funded but not yet done: covers only description, not detailed implementation

Requires: • a web host / technical platform

– Volunteered support by IDF, but other solutions possible and offers welcome

• Support for additions to existing vocabularies, and the addition of new vocabularies

– cost should in due course be met by a registry model, where those registering vocabularies bear any costs of update.

– However, the Framework will need a chance to demonstrate its value:– Seek a provision covering one year following the completion of Stage 1 to support

published changes to existing vocabularies within the Framework (but not the addition of new ones)

• Creation of policy and review mechanism – Current VMF Advisory Board as starting point – Define needs for longer term self-funding Framework – 15 project days for management support and convening the group. Cost: 10K?

Governance and maintenance

• Who are stakeholders, who participates? • CIDOC CRM; DCMI; DDEX; DOI; FRBR; MARC21; LOM; ONIX; RDA • Other “intermediating message standards”?• Other sectors?• Private (non-published) or proprietary mappings, e.g. internal schema?

• Ability to use mapping but not make these available to others • Anyone can map - but makes sense to register the mappings to the

"definitive" version of the matrix to keep up to date with versions; the matrix is dynamic

• Scope: vocabularies now - going to complete schemas with additional semantics?

• do we have a common view of the road ahead?

• What technical roles need to be provided by the host? • co-ordination of mapping?• conformance testing? • ability to adapt / outreach to new technologies ? ( “semantic gostak”)• maintaining a home site (domain name hosting etc )

Issues arising (1)

• What vehicle is needed to support long term governance?• voluntary – all initial vocabulary groups (who?); what other stakeholders? • if self-funding it will be trading - does it need to be an independent entity?• cost implications? • if not who, and what implications?• Legal requirements; directors and officers; liability insurance; accounting,

bank account, etc.

• Authorisation • How is mapping of terms agreed?• how do we authorize a set of scheme to scheme mappings?• control of releases/versions etc • liability and conformance guarantee issues • Long term commitment and persistence – social infrastructure (DOIs as a tool)

• Role of formal Standards bodies • Should VMF be “standardised?• (No: We like standards, but not appropriate) • Different origins/allegiances of components • Difficult to standardise a dynamic thing – cf MPEG 21 RDD• “We know what’s needed; they ask stupid questions” • Time consuming and expensive

Issues arising (2)

• Intellectual Property issues • Trademarks. Domain names. Infringing patents.

• Funding models for the long term • Registry model, where those registering vocabularies bear any costs of

update (compare MPEG 21RDD)• Other options?

• Marketing• Release of new versions, news, encouraging others to participate,

outreach; presentations; fund raising for more development. • Is it sufficient to leave to component contributor schemes – who

coordinates? • Lessons from elsewhere – indecs; MPEG 21 RDD; others?

• Sources of funding for phase 2 and 3• JISC? Others?

Issues arising (3)

Stage 1 (funded in current VMF project): basic extension of RDA/ONIX Framework • “The deliverable of stage 1 will be a major expansion of the existing RDA/ONIX

Framework, based on and incorporating relevant vocabularies from nine main bibliographic and supply chain metadata standards of interest to the JISC community”

Stage 2: further technical work• Aims: - give the project a base level of ongoing activity on existing content - allow for initial roll-out feedback• Action: - continued work on agreeing mappings, development of uses, rules, tools, etc. Stage 3: governance and maintenance• Aims: - avoid the work becomes a dead-end project - provide a usable platform and a guarantee of stability • Action: - funding for maintenance of the Framework for one year - put long term model in placed thereafter

For discussion

Outline