The Road Forwardbased on what we’ve learned from the one we’vebeen onDiane Hillmann and Gordon DunsireNISO Bibliographic R...
Let’s start from hereFRBRer FRBRooISBDBibOMARC 21UNIMARCRDADCBIBFRAME?Schema.org/bibex?Bibliographic RDF element setsLocal
Similar things, different povso It’s the same bibliographic universeo With common concepts found in most bibliographicsche...
m21:M338__brda:carrierTypeManifestationrda:mediaTypeManifestationdct:formatdc:formatunc:mediaTypeisbd:P1003schema:encodesC...
Environmento Many element sets and vocabularieso Common concept maps are in process - more can becreated, and viewed as pa...
Design strategieso Bottom up, not top down: the evidence of globalconsensus lies in the commonality of multiple localenvir...
From local to global (data)o “Contract” specifies set of properties that data mustinteroperate witho Local data can intero...
Role of Standards Organizationo Build on library community strengths in collaborationand trusto Maintain “contract” for ac...
Local to global (development)o Local development proceeds at own paceo No need to wait for consensus approvalo Global endo...
Beware of Zombie Issueso Assumption of “records” as units of managemento Records can be inputs or outputso Round trippingo...
Provenance and Filteringo “Who says?” is an essential question when evaluatingstatementso Not all data statements are crea...
What’s Needed?o Infinite namespaces, without encodings, sequences,hierarchieso Support for innovation at every levelo Comm...
Upcoming SlideShare
Loading in …5
×

NISO Bibliographic Roadmap Meeting Proposal

921 views

Published on

Proposal by Diane Hillmann and Gordon Dunsire at the NISO Bibliographic Roadmap meeting, April 15-16, Baltimore, MD. In this proposal, Hillmann and Dunsire describe how the current environment can be transformed without necessarily the kinds of disruption that have been feared.

Published in: Technology

NISO Bibliographic Roadmap Meeting Proposal

  1. 1. The Road Forwardbased on what we’ve learned from the one we’vebeen onDiane Hillmann and Gordon DunsireNISO Bibliographic Roadmap meeting,April 15-16, 2013, Baltimore, MD, USA
  2. 2. Let’s start from hereFRBRer FRBRooISBDBibOMARC 21UNIMARCRDADCBIBFRAME?Schema.org/bibex?Bibliographic RDF element setsLocal
  3. 3. Similar things, different povso It’s the same bibliographic universeo With common concepts found in most bibliographicschema/element setso Author, title, subject, format, etc.o Plus specialized concepts for non-global useo Musical key, parallel title, etc.o Allowing semantic maps between particular schemaelements/properties (ontologies)
  4. 4. m21:M338__brda:carrierTypeManifestationrda:mediaTypeManifestationdct:formatdc:formatunc:mediaTypeisbd:P1003schema:encodesCarrier/format concept map (ontology)
  5. 5. Environmento Many element sets and vocabularieso Common concept maps are in process - more can becreated, and viewed as part of a “contract”o Don’t need complete “schema-to-schema” mapso Concept-focused maps/ontologies are theconsensus, not the schema boundaryo What’s the common minimal data that you need toprovide to be part of a global service? What else isnecessary for the description?
  6. 6. Design strategieso Bottom up, not top down: the evidence of globalconsensus lies in the commonality of multiple localenvironmentso Top down requires agreement prior to evidence ofusageo Some approved elements never get used; MARC21 has several exampleso The consensus may not lie at “the top”, i.e. the“dumbest” element
  7. 7. From local to global (data)o “Contract” specifies set of properties that data mustinteroperate witho Local data can interoperate via direct mapping, or viaconnection to any part of a concept-focused mapo Local data remains in original format for localapplicationso Automatically dumbed-down for global servicesusing mapso “Think global, act local” = add mappings from localproperties to global graphs
  8. 8. Role of Standards Organizationo Build on library community strengths in collaborationand trusto Maintain “contract” for accepting data in globalservice(s)o Consensus identification of component elementso New candidate elements identified by local usageo “Endorsement” mechanism brings new elementsinto contract
  9. 9. Local to global (development)o Local development proceeds at own paceo No need to wait for consensus approvalo Global endorsement necessarily and usefully lagsbehind local developmentso E.g. W3C/HTML5; schema.orgo “Tell us what to do”o Do your own thing!
  10. 10. Beware of Zombie Issueso Assumption of “records” as units of managemento Records can be inputs or outputso Round trippingo It’s not about data “residence” in one schema oranother—more of a “view”o De-duplication—no more “master records”o Data at the statement level is available for manykinds of aggregation
  11. 11. Provenance and Filteringo “Who says?” is an essential question when evaluatingstatementso Not all data statements are created equal, buttrustworthiness is hard to determine withoutprovenanceo Provenance info is the basis for data filteringo No other technique works quite as well to determinequality
  12. 12. What’s Needed?o Infinite namespaces, without encodings, sequences,hierarchieso Support for innovation at every levelo Commitment to move forward (not back), and to learnthe right lessons from experienceo Leadership from institutions and individuals

×