Does MARC Have a Future?Diane I. HillmannInformation Institute of Syracuse/Metadata Management Associates

Doesn’t the answer depend on what we mean by future?7/9/092CCS Forum, Chicago, 2009

Yes, No, Maybe …Yes …Because it will take some unknown number of years to move our legacy data to a more modern, FRBR-aware formatBecause our community is still largely using MARC, and we’ll need to retain the ability to communicate in MARC until we build tools to do something elseBecause the wiring in our heads is still MARC …7/9/093CCS Forum, Chicago, 2009

Yes,No, Maybe …No … Because in order to keep MARC available to those who need it to be sustainable in the interim, we need to freeze further changes, sooner rather than later, otherwise we raise costs for everyoneBecause MARC is best for flat files, and most of us want to take advantage of the advanced browsing we can do with FRBR-style recordsRDA really can’t be used with MARC, unless we want to go forward on our hands and knees …7/9/094CCS Forum, Chicago, 2009

Yes,No, Maybe …Maybe …If you define ‘future’ in a very limited way, say, the next 5-8 yearsIf you recognize that RDA is very influenced by our experience with MARC, particularly in the area of vocabularies, thus the shadow of RDA may always look something like MARCBecause MARC will always be in our heads, just like our mother’s voices are …7/9/095CCS Forum, Chicago, 2009

Do We Need A Replacement?Only if we think we need to protect our data from the world, or the world from our data …7/9/096CCS Forum, Chicago, 2009

Instead, We Could …Use RDA It’s a FRBR-based, bibliographic vocabulary presented in a more modern form, including some familiar ideasThe elements, sub-elements, and vocabularies can be used with XML encoding or as part of RDF triplesThe data is easily used and understood by other communities who are used to exchanging XML dataRDA elements and vocabularies can easily be extended by specialized communities whose needs are not entirely met by RDA out-of-the-box7/9/097CCS Forum, Chicago, 2009

Why Does This Strategy Work?Might help to look at what “interoperability” means in our contextWikipedia cites the IEEE definition:“ … the ability of two or more systems or components to exchange information and to use the information that has been exchanged”Libraries have understood this concept primarily within the context of MARC and our long history of data exchange7/9/098CCS Forum, Chicago, 2009

Let’s Think Again About Our NeedsWe definitely hear questions:If we want to join the world of data “out there,” will we have to redo all our older data?What would it take to achieve a reasonable level of interoperability fairly quickly? Where should we start?First, check what’s happening outside our community7/9/099CCS Forum, Chicago, 2009

DC Interoperability Levels7/9/0910CCS Forum, Chicago, 2009

We had these in MARC, in the documentation built over the decadesWe now have them as well in RDARDA Elements and Relationships are registered and available to all freelyGoing forward we have tools that will allow us to build, maintain, and extend these vocabularies7/9/0911CCS Forum, Chicago, 2009

“‘Semantics’ in this sense does not refer to well-formed natural-language definitions ... Rather, it refers to formally stated relationships between terms and rules for using such statements to draw automatic conclusions (logical inferences). This includes use of URIs and conformance with formally specified domains, ranges, and sub-property relations.” -- http://dublincore.org/documents/interoperability-levels/index.shtml7/9/0912CCS Forum, Chicago, 2009

Some Background on DSPsDSP = “Description Set Profile” – it’s the newest iteration of tApplication Profile, reflecting the relationship with the Dublin Core Abstract ModelIn a more general sense, it is a way to look at and discuss the various “packages” that are needed for a full expression of library data: bibliographic, authority, etc.7/9/0913CCS Forum, Chicago, 2009

This is, of course, where we need to be, very soon …As part of the Registry contract with ALA, we are building the capability to expose XML schemas based on the following element aggregations: Core, Enhanced, SpecialA tool to allow RDA users to create their own “Description Set Profiles” will be coming in the fall7/9/0914CCS Forum, Chicago, 2009

Here we see the “Holy Grail” and it’s likely to take a bit of time to get hereConsider a scenario where each record would have as part of it’s namespace declaration a link to the DSP that was used to create it?In a world that seems to be becoming less predictable, we would like to see a method for ensuring some useful predictability without significant new investments of human effort7/9/0915CCS Forum, Chicago, 2009

Joining the World of DataTo participate fully we need to think about making our data available broadly AND using data created outside libraries effectivelyA “bespoke” data format is not the best way to do thisRDA is a good first step, but we have a significant amount of work yet to realize its potential7/9/0916CCS Forum, Chicago, 2009

Thank you!✔ out the Registry:http://metadataregistry.orgContact:Diane I. HillmannMetadata.maven@gmail.com7/9/0917CCS Forum, Chicago, 2009