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 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)
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?
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
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
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
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!
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
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
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