Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
The Road Forwardbased on what we’ve learned from the one we’vebeen on
Let’s start from hereFRBRer FRBRooISBDBibOMARC 21UNIMARCRDADCBIBFRAME?Schema.org/bibex?Bibliographic RDF element setsLocal
Similar things, different povs• It’s the same bibliographic universe• With common concepts found in most bibliographicsche...
m21:M338__brda:carrierTypeManifestationrda:mediaTypeManifestationdct:formatdc:formatunc:mediaTypeisbd:P1003schema:encodesC...
EnvironmentMany element sets and vocabulariesDon’t need complete ‘schema-to-schema’ mapsConcept-focused maps/ontologies ar...
Design strategiesBottom up, not top down: the evidence of globalconsensus lies in the commonality of multiple localenviron...
From local to global (data)• “Contract” specifies set of properties that data mustinteroperate with• Local data can intero...
Role of Standards OrganizationBuild on library community strengths in collaborationand trustMaintain “contract” for accept...
Local to global (development)• Local development proceeds at own pace• No need to wait for consensus approval• Global endo...
Beware of Zombie IssuesAssumption of ‘records’ as units of managementRecords can be inputs or outputsRound trippingIt’s no...
Provenance and Filtering‘Who says?’ is an essential question when evaluatingstatementsNot all data statements are created ...
What’s Needed?Infinite namespaces, without encodings, sequences,hierarchiesSupport for innovation at every levelCommitment...
Upcoming SlideShare
Loading in …5
×

Dunsire roadmap meeting proposal

1,029 views

Published on

Presentation by Gordon Dunsire and Diane Hillmann at the NISO Bibliographic Roadmap meeting, Baltimore, April 15, 2013

Published in: Education
  • Be the first to comment

Dunsire roadmap meeting proposal

  1. 1. The Road Forwardbased on what we’ve learned from the one we’vebeen on
  2. 2. Let’s start from hereFRBRer FRBRooISBDBibOMARC 21UNIMARCRDADCBIBFRAME?Schema.org/bibex?Bibliographic RDF element setsLocal
  3. 3. Similar things, different povs• It’s the same bibliographic universe• With common concepts found in most bibliographicschema/element sets• Author, title, subject, format, etc.• Plus specialized concepts for non-global use• Musical key, parallel title, etc.• 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. EnvironmentMany element sets and vocabulariesDon’t need complete ‘schema-to-schema’ mapsConcept-focused maps/ontologies are theconsensus, not the schema boundaryCommon concept maps are in process - more can becreated, and viewed as part of a ‘contract’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 strategiesBottom up, not top down: the evidence of globalconsensus lies in the commonality of multiple localenvironmentsTop down requires agreement prior to evidence ofusageSome approved elements never get used; MARC21 has several examplesThe consensus may not lie at “the top”, i.e. the“dumbest” element
  7. 7. From local to global (data)• “Contract” specifies set of properties that data mustinteroperate with• Local data can interoperate via direct mapping, or viaconnection to any part of a concept-focused map• Local data remains in original format for localapplications• Automatically dumbed-down for global servicesusing maps• “Think global, act local” = add mappings from localproperties to global graphs
  8. 8. Role of Standards OrganizationBuild on library community strengths in collaborationand trustMaintain “contract” for accepting data in globalservice(s)Consensus identification of component elementsNew candidate elements identified by local usage“Endorsement” mechanism brings new elementsinto contract
  9. 9. Local to global (development)• Local development proceeds at own pace• No need to wait for consensus approval• Global endorsement necessarily and usefully lagsbehind local developments• E.g. W3C/HTML5; schema.org• “Tell us what to do”• Do your own thing!
  10. 10. Beware of Zombie IssuesAssumption of ‘records’ as units of managementRecords can be inputs or outputsRound trippingIt’s not about data ‘residence’ in one schema oranother—more of a ‘view’De-duplication—no more ‘master records’Data at the statement level is available for manykinds of aggregation
  11. 11. Provenance and Filtering‘Who says?’ is an essential question when evaluatingstatementsNot all data statements are created equal, buttrustworthiness is hard to determine withoutprovenanceProvenance info is the basis for data filteringNo other technique works quite as well to determinequality
  12. 12. What’s Needed?Infinite namespaces, without encodings, sequences,hierarchiesSupport for innovation at every levelCommitment to move forward (not back), and to learnthe right lessons from experienceLeadership from institutions and individuals

×