Category: RDA

  • Remembering Christine Frodl

    I can’t remember when I first met Christine, but I certainly knew her well enough to make an informal (and more than a bit subversive) proposal to her at DC-2008 in Berlin. Jon & I had been discussing how RDA might develop translations — this was about the time when we had added the Properties and subProperties, based on the RDA relationships originally published in the Appendices, into the OMR. Many of the readers of this blog may remember that the 2008-2013 versions of the RDA Vocabularies were never formally published by the JSC, but that changed in 2014 when the RDA Registry was unveiled.

    In Berlin we decided to approach Christine about working with us to demonstrate how the translations might work. We knew the German librarians were very interested in participating in RDA and had been pushing at the JSC’s door for some time. We thought she would at least hear us out, but we were in no way convinced that she’d be very interested. We knew that catalog librarians in particular were very imprinted on rules, and we suspected that those from Germany might be even more so. How wrong we were!

    We made sure that Christine knew that we hadn’t asked permission, and there might be repercussions from this subversive activity, even if it were only a demonstration. To our surprise, she said yes, with a visible twinkle in her eye at the thought of such an outrageous project. The repercussions I was worried about stemmed from some discomfort JSC had about us at that point. They didn’t understand what we were trying to do, and someone accused us of stealing their work (I couldn’t make that up).

    So Christine didn’t just say yes, she followed through, appointing Veronika Leibrecht from her shop, who spoke both German and English. Veronika did a fantastic job, and after that we rarely missed a chance to show folks looking at the OMR that there was a German translation. RDA now has (or is working on) translations in the RDA Registry that include Catalan, Chinese, Danish, Dutch, Finnish, French, German, Greek, Hebrew, Hungarian, Italian, Norwegian, Polish, Portuguese, Slovak, Spanish, Swedish, Ukrainian, and Vietnamese.

    This story came to mind immediately when I heard that Christine had died last week. It was clear to us that in addition to the many professional and personal qualities mentioned by those who knew her, she had a vision of a multi-lingual future for RDA that she had the courage to help get moving. That’s a legacy to be celebrated.

  • Whither CC:DA?

    Back in the old days (Feb. 2014, to be exact), I published a blog post entitled: “Wake Up Call for CC:DA”, written during an excruciating conversation at the tail end of a CC:DA meeting at Midwinter 2014. As part of that I recommended that CC:DA change its focus:

    “What we need here is to change the conversation, and no group is more qualified to do that than CC:DA. To do that it’s absolutely necessary that its membership become more knowledgeable about what is now possible in automating metadata creation. Without that kind of awareness, it’s impossible to start thinking and discussing how to focus less of CC:DA’s efforts on that part of the cataloging process which should be done by machines, and more on what still needs humans to accomplish. There are several ways to do this. One is by dedicating some of CC:DA’s conference time to bringing in those folks who understand the technology issues to demonstrate, discuss, and collaborate.”

    There were no comments to that post (not much of a surprise), but in the years since, change has been forced on CC:DA as a result of the RSC’s push to change RDA from the Anglo-American focus of the past to one more international and multilingual. This has changed CC:DA’s status from the 800 lb. gorilla whose discussions went directly into the ears of the RSC (then the JSC) to a cranky corner of the RDA peanut gallery. The Europeans, many of whom are actually using RDA, have taken center stage, leaving the Americans to cope (or not) with BibFrame (characterized by some across the pond as just another remnant of America’s colonial aspirations).

    Like most change, that’s the bad news and the good news, depending on your point of view. Mine (again no surprise) is that this shift is the good news, or will be when the CC:DA community decides to make it so. IMO, the usual CC:DA conversation, most often focused on the ‘rules’, has resulted in keeping back the American discussions of what the future looks like for the metadata community. Europe is far ahead of us, having been relatively powerless to change the guidelines, and has instead been focused on learning more about the data models they need to know about to evaluate what they do now and how that needs to change. There has been far more experimentation and implementation in Europe than we’ve managed in the U.S. (the BF distraction is part of that) and as they have developed much more sophistication in their thinking.

    So what should we do to change that? Some possibilities:

    1. Start talking about what metadata should or could be for our present and future, whether creation, evaluation, distribution or improvement. Figure out what we know and don’t know and how we can learn what’s going on in the metadata world outside libraries and how we can apply that knowledge in libraries.

    2. Set up a working group or committee to take that discussion and develop a curriculum for CC:DA with the intention of building up skills and understanding to spread around, within and beyond CC:DA, as well as throughout the cataloging community (which desperately needs leadership in this area).

    3.Determine who within ALA and allied organizations can participate and assist, by preparing reading lists, developing and/or linking to existing materials, and leading discussions (both f2f and online). Eventually we’ll need to set up a variety of strategies for supporting and expanding these opportunities.

    This is clearly not part of the current remit of CC:DA, and the budget does not yet exist for this kind of effort. Clearly there will need to be partnerships and allies for an effort like this, but we’re already behind, so let’s get started.

    [I plan to make a proposal to CC:DA to start talking about this, so watch this space.]

  • Hey BibFramers, what’s it all about?

    One of the ongoing myths about RDA is that it’s just a set of instructions and rules for the creation and maintenance of bibliographic metadata, regardless of data model. This has never been entirely accurate, since the RDA instructions explicitly reference RDA’s FRBR-based metadata model, which was significantly modified by BibFrame. But the notion of RDA-as-rules divorced from its data and infrastructure seems still to be part of the promotion of Bibframe. This is not helpful, and when the misinformation is stated over and over it begins to look like an Alternative Fact.

    For example, as part of the Bibframe Update presentations at ALA in Chicago, it was stated that the Bibframe editor will have the “RDA rules hot linked to element labels” (presumably from the Toolkit) to assist catalogers using BF to create bib data. I find this difficult to get my head around — BF and RDA use different reference models, name things differently, etc. And the RDA 3R project to reorganize and rewrite the instructions to align RDA with the IFLA LRM (which is both more extensive than, and less aligned with the Bibframe model) is well underway, and will likely confuse the issue even more.

    The contention that RDA guidance can be used to build BF data is certainly not new. What is new was the momentum of change in process with RDA, from the R3 project, to the internationalization of RDA governance, to the growing list of translations. When the 3R Project is complete (early next year), the RDA instructions in the Toolkit and the data in the RDA Registry will be far more integrated than AACR and MARC ever were. Whether that integration will leave room for BibFrame to use the new instructions is unclear.

    There was an impressive list of RDA information sessions at Annual, and an increasing numbers of folks attending them. This suggests that the RDA message seems to be gaining momentum, and there’s mounting evidence that this is so. A few presentations from the “RDA towards Linked Data sessions, held in conjunction with the European RDA Interest Group (EURIG) annual meeting in Fiesole, Italy this May illustrate that point:

    In his presentation, Philip Schreur pointed out that RDA “is a natural representation of our data on the Web” because of its extensible and flexible framework, its rich treatment of relationships, and its focus on resource discovery.

    Gordon Dunsire’s presentation showed how the wider implementation of the “4-fold path” in RDA for data capture and storage is intended to support a full range of data representation from catalogue cards, flat file schema, and RDBMS, to linked data.

    Most people who attended the RDA sessions in Chicago seemed to be very interested in RDA’s approach, in particular how the data is handled, the growth of translations, and the strong desire to extend RDA to meet the needs of specialized cataloging communities. A meeting to explore the needs of those communities was exceptionally well attended, with lots of good suggestions. And the RDA Linked Data Forum (where people actually got a chance to ask questions!!) was standing room only. (My slides are here).

    There are definite challenges for the North American cataloging community moving forward if they want to avoid isolating themselves from the rest of the bibliographic world, by and large unenthusiastic about BibFrame. The Anglo-American cataloging rules are fading into the distance as the rest of the world embraces the reality of a truly multinational, multilingual, multicultural metadata environment, exemplified by the RDA/LRM bibliographic model. The North American bibliographic community has never been explicitly “America First” and now is not the time to start.

    Stay tuned.

  • “Understanding Metadata”: a sort of review

    While checking email during a moment of inattention at the recent ALA Midwinter meeting in Atlanta, I spotted an announcement of the new NISO publication “Understanding Metadata”, by Jenn Riley. It was a surprise, I’d not known that it was in preparation, but I hoped that such a primer would be helpful in raising the level of understanding around metadata in the general library community.

    So I downloaded the publication, and as is my wont, started with the Table of Contents to get a sense of what was being covered. To my absolute astonishment, neither the list of Notable Metadata Languages: Examples in Broad Use nor the one of Notable Metadata Languages: Examples from the Cultural Heritage Sector included RDA: Resource Description and Access. In disbelief, I searched the document for “RDA” and found only a footnote describing RDA as the successor to AACR2 and categorized as a ‘content standard’. I then tried searching for “FRBR”, and there was nothing at all to be found.

    Full disclosure: I’m part of the RDA Development Team and have worked on the RDA Vocabularies since late 2007, after the RDA group and DCMI got together to build them. Granted, it took until January 2014 to publish them formally and bring up the RDA Registry, but we were not hiding under a rock for those years.

    There’s a long trail of articles and blog posts documenting the trajectory of RDA (only some of them with my name on them), so it’s inexplicable to me how the author of this primer, the estimable Jenn Riley, could still subscribe to the notion that RDA is all about instructions for populating element sets. That was certainly true before 2008, but I know Jenn has not been hiding under a rock, either. Particularly when efforts outside North America are considered, RDA is a force to be reckoned with in the metadata space, and interest in Europe and other places outside of North America is enthusiastic and growing.

    None of the IFLA standards show up in this publication either, which suggests a somewhat US-centric view–inexplicable to me given the increasing internationalization of metadata efforts overall. Several of those missing IFLA standards, including FRBR, are being republished after extensive reviews, and at least in RDA-land, the IFLA Library Reference Model (LRM) is a significant topic of conversation where library metadata people hang out.

    Then I checked out Jenn’s wonderful image categorizing metadata standards “Seeing Standards: A Visualization of the Metadata Universe”, and noted that it also included RDA as a content standard and successor to AACR2. Then I saw that the image was copyrighted 2009-2010, and the most obvious answer for the gap became clearer. [I should note that I have a large poster sized version of the image, which I had printed up so I could study the image better, back when I was doing more teaching]. I was pretty relieved by this realization, to be honest, but it occurred to me that the revolutionary change represented by the RDA Vocabularies seems to have been overlooked by Jenn (and probably others) who think they know what RDA is, but haven’t looked at it lately (or at least since 2008, when the vocabularies began to appear in the Open Metadata Registry). I guess as one involved in metadata standards for well over 3 decades, it’s been my experience that with few exceptions, metadata standards change continually, and the assumption that they are fixed in time and space is a dangerous one.

    That said, there is much to be applauded in this primer. The explanation of storage and sharing is an excellent overview, clear and well illustrated. It was good to see a section covering standardization issues, but I would argue with this statement in the ‘Standardization’ section: “Formal standardization is not the norm for most RDF vocabularies; instead, communities tend to build vocabularies that are useful to them, then promote their use through a combination of documentation and open sharing of data that uses these vocabularies.” This statement absolutely does not apply to RDA, nor to the majority of the examples listed in Notable Metadata Languages: Examples in Broad Use. But in a sense it explains the emphasis on XML that seemed a bit out of date as I first read through the document

    I would also argue with the following statement in the Controlled Vocabularies section: “Those developed and maintained by the cultural heritage community, such as LCSH, tend to be among the most robust controlled vocabularies in common use.” I’m not sure what definition of ‘robust’ is being used here, but I posted on Metadata Matters in 2013 about the significant problems with LCSH in http://id.loc.gov, which i think makes a strong argument against the ‘robustness’ of the LCSH services. (https://managemetadata.com/blog/2013/07/23/versions-and-services-pt-2/). Not much has changed since that post, sadly.

    I guess, on the whole, I’d have to say I’m disappointed with this primer, despite some strong sections. Although I’m no fan of peer review, it strikes me that this is one situation where it might have been useful.

  • The RDA Toolkit == The RDA Data Model

    Sitting in the CC:DA meeting at ALA last week, listening to the RDA report and the questions it generated, I was struck yet again by the disconnect between the understanding by the audience of RDA as a content model — the Instructions as embodied in the Toolkit — and the presentation by the speakers of the changes to both the RDA Toolkit and the RDA Registry in terms of the changes to the RDA data model.

    In the case of the Toolkit, a significant part of the reorganization is intended to better align the Toolkit with the Registry, the data model. In the case of the Registry, a significant portion of the changes are intended to continue the current data model’s status as an implementation of FRBR, and to adjust the model to accommodate the consolidation of the various FRBR models into the IFLA LRM.

    From its inception, the Toolkit has reflected the RDA instructions, an upgraded and internationalized version of AACR2, originally intended to provide content instructions for populating the MARC21 carrier, while conceptually describing the data in terms of the FRBR-oriented RDA carrier. The changes to the Toolkit are a necessary evolution away from the slowly devolving MARC21 data model toward the RDA data model. But the audience doesn’t, can’t, easily see that distinction, and the ‘questions’ swirl around expressions of discomfort with the changes that reflect a lack of understanding of the broadening disconnect between the Toolkit and the Registry, and between RDA and MARC21.

    This cognitive dissonance must be addressed by the RSC and its representatives at every future opportunity when discussing the rationale for both the alignment of the RDA data model with IFLA LRM, and the alignment of the RDA content model in the Toolkit with the RDA data model. In that context, the global bibliographic community needs definitive guidance in understanding the relationship between the entities and elements of the RDA data model and the MARC21 data model in which they currently create and maintain their metadata.

  • It’s not just me that’s getting old

    Having just celebrated (?) another birthday at the tail end of 2015, the topics of age and change have been even more on my mind than usual. And then two events converged. First I had a chat with Ted Fons in a hallway at Midwinter, and he asked about using an older article I’d published with Karen Coyle way back in early 2007 (“Resource Description and Access (RDA): Cataloging Rules for the 20th Century”). The second thing was a message from Research Gate that reported that the article in question was easily the most popular thing I’d ever published. My big worry in terms of having Ted use that article was that RDA had experienced several sea changes in the nine (!) years since the article was published (Jan./Feb. 2007), so I cautioned Ted about using it.

    Then I decided I needed to reread the article and see whether I had spoken too soon.

    The historic rationale holds up very well, but it’s important to note that at the time that article was written, the JSC (now the RSC) was foundering, reluctant to make the needed changes to cut ties to AACR2. The quotes from the CC:DA illustrate how deep the frustration was at that time. There was a real turning point looming for RDA, and I’d like to believe that the article pushed a lot of people to be less conservative and more emboldened to look beyond the cataloger tradition.

    In April of 2007, a mere few months from when this article came out, ALA Publishing arranged for the famous “London Meeting” that changed the course of RDA. Gordon Dunsire and I were at that meeting–in fact it was the first time we met. I didn’t even know much about him aside from his article in the same DLIB issue. As it turns out, the RDA article was elevated to the top spot, thus stealing some of his thunder, so he wasn’t very happy with me. The decision made in London to allow DCMI to participate by building the vocabularies was a game changer, and Gordon and I were named co-chairs of a Task Group to manage that process.

    So as I re-read the article, I realized that the most important bits at the time are probably mostly of historical interest at this point. I think the most important takeaway is that RDA has come a very long way since 2007, and in some significant ways is now leading the pack in terms of its model and vocabulary management policies (more about that to come).

    And I still like the title! …even though it’s no longer a true description of the 21st Century RDA.

  • Denying the Non-English Speaking World

    Not long ago I encountered the analysis of BibFrame published by Rob Sanderson with contributions by a group of well-known librarians. It’s a pretty impressive document–well organized and clearly referenced. But in fact there’s also a significant amount of personal opinion in it, the nature of which is somewhat masked by the references to others holding the same opinion.

    I have a real concern about some of those points where an assertion of ‘best practices’ are particularly arguable. The one that sticks in my craw particularly shows up in section 2.2.5:

    2.2.5 Use Natural Keys in URIs
    References: [manning], [ldbook], [gld-bp], [cooluris]

    Although the client must treat URIs as opaque strings, it is good practice to construct URIs in a systematic and human readable fashion for both instances and ontology terms. A natural key is one that appears in the information about the resource, such as some unique identifier for the resource, or the label of the property for ontology terms. While the machine does not care about structure, memorability or readability of URIs, the developers that write the code do. Completely random URIs introduce difficult to detect semantic and algorithmic errors in both publication and consumption of the data.

    Analysis:

    The use of natural keys is a strength of BIBFRAME, compared to similarly scoped efforts in similar communities such as the RDA and CIDOC-CRM vocabularies which use completely opaque numbers such as P10001 (hasRespondent) or E33 (Linguistic Entity). RDA further misses the target in this area by going on to define multiple URIs for each term with language tagged labels in the URI, such as rda:hasRespondent.en mapping to P10001. This is a different predicate from the numerical version, and using owl:sameAs to connect the two just makes everyone’s lives more difficult unnecessarily. In general, labels for the predicates and classes should be provided in the ontology document, along with thorough and understandable descriptions in multiple languages, not in the URI structure.

    This sounds fine so long as you accept the idea that ‘natural’ means English, because, of course, all developers, no matter their first language, must be fluent enough in English to work with English-only standards and applications. This mis-use of ‘natural’ reminds me of other problematic usages, such as the former practice in the adoption community (of which I have been a part for 40 years) where ‘natural’ was routinely used to refer to birth parents, thus relegating adoptive parents to the ‘un-natural’ realm. So in this case, if ‘natural’ means English, are all other languages inherently un-natural in the world of development? The library world has been dominated by the ‘Anglo-American’ notions of standard practice for a very long time, and happily, RDA is leading away from that, both in governance and in development of vocabularies and tools.

    The Multilingual strategy adopted by RDA is based on the following points:

    1. More than a decade of managing vocabularies has convinced us that opaque identifiers are extremely valuable for managing URIs, because they need not be changed as labels change (only as definitions change). The kinds of ‘churn’ we saw in the original version of RDA (2008-2013) convinced us that label-based URIs were a significant problem (and cost) that became worse as the vocabularies grew over time.
    2. We get the argument that opaque URIs are often difficult for humans to use–but the tools we’re building (the RDA Registry as case in point) are intended to give human developers what they want for their tasks (human readable URIs, in a variety of languages) but ensure that the URIs for properties and values are set up based on what machines need. In this way, changes in the lexical URIs (human-readable) can be maintained properly without costly change in the canonical URIs that travel with the data content itself.
    3. The multiple language translations (and distributed translation management by language communities) also enable humans to build discovery and display mechanisms for users that are speakers of a variety of languages. This has been a particularly important value for national libraries outside the US, but also potentially for libraries in the US meeting the needs of non-English language communities closer to home.

    It’s too easy for the English-first library development community to insist that URIs be readable in English and to turn a blind eye to the degree that this imposes understanding of the English language and Anglo-American library culture on the rest of the world. This is not automatically the intellectual gift that the distributors of that culture assume it to be. It shouldn’t be necessary for non-Anglo-American catalogers to learn and understand Anglo-American language and culture in order to express metadata for a non-Anglo audience. This is the rough equivalent of the Philadelphia cheese steak vendor who put up a sign reading “This is America. When ordering speak in English”.

    We understand that for English-speaking developers http://bibframe.org/vocab/title is initially easier to use than http://rdaregistry.info/Elements/w/P10088 or even (heaven forefend!) “130_0#$a” (in RDF: http://marc21rdf.info/elements/1XX/M1300_a). That’s why RDA provides http://rdaregistry.info/Elements/w/titleOfTheWork.en but also, eventually, http://rdaregistry.info/Elements/w/拥有该作品的标题.ch and http://rdaregistry.info/Elements/w/tieneTítuloDeLaObra.es, et al (you do understand Latin of course). These ‘unnatural’ Lexical Aliases will be provided by the ‘native’ language speakers of their respective national library communities.

    As one of the many thousands of librarians who ‘speak’ MARC to one another–despite our language differences–I am loathe to give up that international language to an English-only world. That seems like a step backwards.

  • Separating ideology, politics and utility

    Those of you who pay attention to politics (no matter where you are) are very likely to be shaking your head over candidates, results or policy. It’s a never ending source of frustration and/or entertainment here in the U.S., and I’ve noticed that the commentators seem to be focusing in on issues of ideology and faith, particularly where it bumps up against politics. The visit of Pope Francis seemed to be taking everyone’s attention while he was here, but though this event has added some ‘green’ to the discussion, it hasn’t pushed much off the political plate.

    Politics and faith bump up against each other in the metadata world, too. What with traditionalists still thinking in MARC tags and AACR2, to the technical types rolling their eyes at any mention of MARC and trying to push the conversation towards RDA, RDF, BibFrame, schema.org, etc., there are plenty of metadata politics available to flavor the discussion.

    The good news for us is that the conflicts and differences we confront in the metadata world are much more amenable to useful solution than the politics crowding our news feeds. I remember well the days when the choice of metadata schema was critical to projects and libraries. Unfortunately, we’re all still behaving as if the proliferation of ‘new’ schemas makes the whole business more complicated–that’s because we’re still thinking we need to choose one or another, ignoring the commonality at the core of the new metadata effort.

    But times have changed, and we don’t all need to use the same schema to be interoperable (just like we don’t all need to speak English or Esperanto to communicate). But what we do need to think about is what the needs of our organization are at all stages of the workflow: from creating, publishing, consuming, through integrating our metadata to make it useful in the various efforts in which we engage.

    One thing we do need to consider as we talk about creating new metadata is whether it will need to work with other data that already exists in our institution. If MARC is what we have, then one requirement may be to be able to maintain the level of richness we’ve built up in the past and still move that rich data forward with us. This suggests to me that RDA, which RIMMF has demonstrated can be losslessly mapped to and from MARC, might be the best choice for the creation of new metadata.

    Back in the day, when Dublin Core was the shiny new thing, the notion of ‘dumb-down’ was hatched, and though not an elegantly named principle, it still works. It says that rich metadata can be mapped fairly easily into a less-rich schema (‘dumbed down’), but once transformed in a lossy way, it can’t easily be ‘smartened up’. But in a world of many publishers of linked data, and many consumers of that data, the notion of transforming rich metadata into any number of other schemas and letting the consumer chose what they want, is fairly straightforward, and does not require firm knowledge (or correct assumptions) of what the consumers actually need. This is a strategy well-tested with OAI-PMH which established a floor of Simple Dublin Core but encouraged the provision of any number of other formats as well, including MARC.

    As consumers, libraries and other cultural institutions are also better served by choices. Depending on the services they’re trying to support, they can choose what flavor of data meets their needs best, instead of being offered only what the provider assumes they want. This strategy leaves open the possibility of serving MARC as one of the choices, allowing those institutions still nursing an aged ILS to continue to participate.

    Of course, the consumers of data need to think about how they aggregate and integrate the data they consume, how to improve that data, and how to make their data services coherent. That’s the part of the new create, publish, consume, integrate cycle that scares many librarians, but it shouldn’t–really!

    So, it’s not about choosing the ‘right’ metadata format, it’s about having a fuller and more expansive notion about sharing data and learning some new skills. Let’s kiss the politics goodbye, and get on with it.

  • Semantic Versioning and Vocabularies

    A decade ago, when the Open Metadata Registry (OMR) was just being developed as the NSDL Registry, the vocabulary world was a very different place than it is today. At that point we were tightly focussed on SKOS (not fully cooked at that point, but Jon was on the WG that was developing it, so we felt pretty secure diving in).

    But we were thinking about versioning in the Open World of RDF even then. The NSDL Registry kept careful track of all changes to a vocabulary (who, what, when) and the only way to get data in was through the user interface. We ran an early experiment in making versions based on dynamic, timestamp-based snapshots (we called them ‘time slices’, Git calls them ‘commit snapshots’) available for value vocabularies, but this failed to gain any traction. This seemed to be partly because, well, it was a decade ago for one, and while it attempted to solve an Open World problem with versioned URIs, it created a new set of problems for Closed World experimenters. Ultimately, we left the versions issue to sit and stew for a bit (6 years!).

    All that started to change in 2008 as we started working with RDA, and needed to move past value vocabularies into properties and classes, and beyond that into issues around uploading data into the OMR. Lately, Git and GitHub have started taking off and provide a way for us to make some important jumps in functionality that have culminated in the OMR/GitHub-based RDA Registry. Sounds easy and intuitive now, but it sure wasn’t at the time, and what most people don’t know is that the OMR is still where RDA/RDF data originates — it wasn’t supplanted by Git/Github, but is chugging along in the background. The OMR’s RDF CMS is still visible and usable by all, but folks managing larger vocabularies now have more options.

    One important aspect of the use of Git and GitHub was the ability to rethink versioning.

    Just about a year ago our paper on this topic (Versioning Vocabularies in a Linked Data World, by Diane Hillmann, Gordon Dunsire and Jon Phipps) was presented to the IFLA Satellite meeting in Paris. We used as our model the way software on our various devices and systems is updated–more and more these changes happen without much (if any) interaction with us.

    In the world of vocabularies defining the properties and values in linked data, most updating is still very manual (if done at all), and the important information about what has changed and when is often hidden behind web pages or downloadable files that provide no machine-understandable connections identifying changes. And just solving the change management issue does little to solve the inevitable ‘vocabulary rot’ that can make published ‘linked data’ less and less meaningful, accurate, and useful over time.

    Building stable change management practices is a very critical missing piece of the linked data publishing puzzle. The problem will grow exponentially as language versions and inter-vocabulary mappings start to show up as well — and it won’t be too long before that happens.

    Please take a look at the paper and join in the conversation!

  • What do we mean when we talk about ‘meaning’?

    Over the past weekend I participated in a Twitter conversation on the topic of meaning, data, transformation and packaging. The conversation is too long to repost here, but looking from July 11-12 for @metadata_maven should pick most of it up. Aside from my usual frustration at the message limitations in Twitter, there seemed to be a lot of confusion about what exactly we mean about ‘meaning’ and how it gets expressed in data. I had a skype conversation with @jonphipps about it, and thought I could reproduce that here, in a way that could add to the original conversation, perhaps clarifying a few things. [Probably good to read the Twitter conversation ahead of reading the rest of this.]

    Jon Phipps: I think the problem that the people in that conversation are trying to address is that MARC has done triple duty as a local and global serialization (format) for storage, supporting indexing and display; a global data interchange format; and a focal point for creating agreement about the rules everyone is expected to follow to populate the data (AACR2, RDA). If you walk away from that, even if you don’t kill it, nothing else is going to be able to serve that particular set of functions. But that’s the way everyone chooses to discuss bibframe, or schema.org, or any other ‘marc replacement’.

    Diane Hillmann: Yeah, but how does ‘meaning’ merely expressed on a wiki page help in any way? Isn’t the idea to have meaning expressed with the data itself?

    Jon Phipps: It depends on whether you see RDF as a meaning transport mechanism or a data transport mechanism. That’s the difference between semantic data and linked data.

    Diane Hillmann: It’s both, don’t you think?

    Jon Phipps: Semantic data is the smart subset of linked data.

    Diane Hillmann: Nice tagline 🙂

    Jon Phipps: Zepheira, and now DC, seem to be increasingly looking at RDF as merely linked data. I should say a transport mechanism for ‘linked’ data.

    Diane Hillmann: It’s easier that way.

    Jon Phipps: Exactly. Basically what they’re saying is that meaning is up to the receiver’s system to determine. Dc:title of ‘Mr.’ is fine in that world–it even validates according to the ‘new’ AP thinking. It’s all easier for the data producers if they don’t have to care about vocabularies. But the value of RDF is that it’s brilliantly designed to transport knowledge, not just data. RDF data is intended to live in a world where any Thing can be described by any Thing, and all of those descriptions can be aggregated over time to form a more complete description of the Thing Being Described. Knowledge transfer really benefits from Semantic Web concepts like inferences and entailments and even truthiness (in addition to just validation). If you discount and even reject those concepts in a linked data world than you might as well ship your data around as CSV or even SQL files and be done with it.

    One of the things about MARC is that it’s incredibly semantically rich (http://marc21rdf.info) and has also been brilliantly designed by a lot of people over a lot of years to convey an equally rich body of bibliographic knowledge. But throwing away even a small portion of that knowledge in pursuit of a far dumber linked data holy grail is a lot like saying that since most people only use a relatively limited number of words (especially when they’re texting) we have no need for a 50,000 word, or even a 5,000 word, dictionary.

    MARC makes knowledge transfer look relatively easy because the knowledge is embedded in a vocabulary every cataloger learns and speaks fairly fluently. It looks like it’s just a (truly limiting) data format so it’s easy to think that replacing it is just a matter of coming up with a fresh new format, like RDF. But it’s going to be a lot harder than that, which is tacitly acknowledged by the many-faceted effort to permanently dumb-down bibliographic metadata, and it’s one of the reasons why I think bibframe.org, bibfra.me, and schema.org might end up being very destructive, given the way they’re being promoted (be sure to Park Your MARC somewhere).

    [That’s why we’re so focused on the RDA data model (which can actually be semantically richer than MARC), why we helped create http://marc21rdf.info, and why we’re working at building out our RDF vocabulary management services.]

    Diane Hillmann: This would be a great conversation to record for a podcast 😉

    Jon Phipps: I’m not saying proper vocabulary management is easy. Look at us for instance, we haven’t bothered to publish the OMR vocabs and only one person has noticed (so far). But they’re in active use in every OMR-generated vocab.

    The point I was making was that we we’re no better, as publishers of theoretically semantic metadata, at making sure the data was ‘meaningful’ by making sure that the vocabs resolved, had definitions, etc.

    [P.S. We’re now working on publishing our registry vocabularies.]