Category: Meeting reports

  • What DCMI Should Be Doing

    One continuing theme of the recently concluded DC-2010 is that of the perpetual search for consensus on what the hell DCMI should be doing. I know this continual search for identity is a common phenomenon with this sort of organization, as it is for the human adolescent hovering around the age of 15 years. Like with the teenager, it should be seen as a healthy thing, and as most of us older than 15 know, it pretty much goes on for the remainder of life.

    For me the conference was preceded by a half day DCMI Advisory Board meeting, where one topic was the revision of the DCMI mission statement as well as the perennial topic of the conferences and how the conference series can be optimally funded and continued, and what exactly is its value for the organization. As usual, there was not much consensus, either at the beginning or the end of the discussion, though it must be said that the conference itself probably shifted some opinions about the value proposition. Generally the AB meeting has been scheduled after the conference, with the idea that this shift in perspective is a good thing for sparking discussion, but for logistical reasons the meeting was held prior to the conference this year.

    As it turned out, this change in placement of the AB meeting was unfortunate, given that Mike Bergman’s keynote on Friday morning contributed some important outside opinion to that basic question of mission. (Mike’s post about the keynote is here.) The fact that Mike arrived in time to sample a good chunk of the conference and to talk to a variety of participants gave his opinion the credibility that only exposure to the culture of the organization and the personalities that affect that culture can bring to a keynote. It was clear to me, in talking to him during the conference, that his view of DCMI was not the insider view of a contentious, financially strapped and sometimes dysfunctional organization, but instead one that included recognition of the experience, knowledge and potential there as well. In a nutshell, Mike Bergman was telling us that DCMI’s role in the emerging linked data world was critical, and should be focused primarily on expanding the presence of useful semantics available to the the web world, closing the ‘semantic gap’ he sees limiting the growth of linked open data.

    Later in the day, my task was to lead a discussion of the work of the DCMI/RDA Task Group, of which I’m co-chair with Gordon Dunsire. Gordon and I had both prepared slides for that meeting—mine covering the history and work of the task group, what we’d learned, and what remained, and Gordon’s covering the related important work he’d been doing in parallel with IFLA. I’ve been frustrated for some time with the lack of attention and traction we’ve received for this important work, both from DCMI and the Joint Steering Committee for the Development of RDA (JSC). We have found ourselves at the stage where DCMI is waiting for JSC to make some statement about the work done (in the form of approval), and the JSC is waiting for DCMI to endorse the Task Group’s assertions made about the work done and its usefulness for the Semantic Web—or at least this is the way it seems from the point of view of the co-chairs. It’s as if both groups are standing opposite one another in a middle school gym, the ‘boys’ and the ‘girls’ waiting for someone to move towards the middle. Nobody seems to want to make that first move, and though in the case of the TG, each conversation with representatives of both parties seems to be positive, resolution of the concrete issues moves at a frustratingly glacial pace.

    But as I spoke about this work to various people, continuing to think about the ongoing conversation about what the role of DCMI should be, particularly in the context of Mike’s keynote, it struck me that the DCMI/RDA Task Group was in some sense a model for what DCMI could do to fulfill the role Mike saw for us in the world. In essence, the TG came into being because Don Chatham at ALA Publishing took the initiative to bring DCMI and the JSC together, where the DCMI message was “How can we help?” The rest is history, but we seem not to have learned from that how powerful that simple question is, and where it could lead. DC-2010 brought a number of new communities to the conference, representing a variety of groups interested in moving into the wider web world of information, but lacking in-house knowledge and skills necessary to make progress. Helping them move forward requires much more than attracting them to the conference and talking to them in the hall or after tutorials. We need to offer more concrete help, like we did for the JSC, and move the knowledge and experience that the DCMI Community has assembled into the broader world of information.

  • Live (ish) from DC-2010

    This morning’s highlight was Stu Weibel’s opening keynote address to the assembled conference attendees (yesterday included primarily workshop sessions and tutorials). Stu was asked to talk about DC’s past and future, and he gave many of us food for thought.

    The first thing he did was typical Stu—he took a photo of the assembled group. I hope those will show up on his blog sometime soon (if so I’ll link to them). Will they look that much different from those he took 15 years ago, when Dublin Core began, or those taken at various points along the way? As is also typical, he asked how many people were returning participants in DC, and how many were brand new to the DC conference. Surprising to some of us, roughly one third of the group were new participants, a nicely healthy proportion of new people.

    Stu asked some interesting questions, and gave DCMI some letter grades for performance in a number of areas. His first question, “Why didn’t we just stop after the 15 elements” suggests the possibility that nothing done since then (the mid-nineties) was worth the effort. He points out that a number of the assumptions made at that time have since been repudiated by experience—the Web is more than just a collection of document-like-objects that can be described in much the same way that we’ve traditionally described library materials. He got a laugh when he reminded us (including the three of us who were actually there in Mar. 1995 when DC was born) that we thought we could solve the syntax problem fairly easily—but of course our notion of syntax in those days was HTML.
    Stu gave some personal assessments of the 15 years of DCMI in the form of grades:

    For providing an international basis for the effort (A)
    For including a diverse group of participants (B+)
    For becoming a sustained and solvent organization (D)
    Moving work from consensus to completion (C)
    Establishing objectives and completing them (C-)
    Documentation of decisions (B+) (I have to say I think he was somewhat over generous on this one, for reasons I’ll explain later)

    Stu also pointed out the places DCMI got stuck along the way, among those were ‘tarpits’ (his word) of our own making—for example, data models (for which he gave DCMI an ‘F’). Those that were not our fault or not entirely of our making were things like the aforementioned syntax confusion (C+), which he believes stemmed from trying to do too much and getting overwhelmed (probably the rapid evolution of syntaxes had an effect, too). The ‘tarpits’ created by others included LOM (learning object metadata, promulgated primarily by IEEE), and INDECS (a now dead effort that was touted some years ago as a business model based approach).

    Some other points Stu made which are hard to argue include the notion that cooperation with organizations with different business models is difficult, but such cooperation is critically important, for reasons around convergence of effort, identification of similar models and related technologies—all amplifying the network effect of what DCMI has done. Increasingly, cooperation is seen as an expensive value, particularly in terms of time and travel, and certainly DCMI has seen those issues having a big effect on conference planning and ability to build on past efforts. Stu also gave DCMI an ‘A’ for its standardization efforts, including the work to make DC a recognized standard via IETF, NISO, and ISO. He pointed out that these efforts were essential to allow DC to be adopted by government agencies and others that have requirements for such an endorsement.

    On the Singapore Framework, Stu is dubious, in particular thinking of the four levels of interoperability [link] that include the Description Set Profile (DSC) and the Dublin Core Abstract Model (DCAM). He pointed out that lots of metadata is still used primarily at the lowest, human level, and is not yet useful to machines at the moment. This issue is particularly relevant given that the DCAM is currently under review, with opinions flying around (in the halls, on twitter, etc.) in ways they didn’t even when that document was new, and pretty much nobody understood it. Understanding is still an issue, to a great extent because specification and user documentation are not the same thing (something that the DCMI technical folks don’t seem to understand). Stu contends that the DCAM has failed, and felt that its authors still don’t agree about its motivations or implications. It will be interesting to see whether that assessment is widely held throughout the conference.

    On linked data, Stu was clearly somewhat ambivalent, calling it “An aspirational target of great promise and unproven benefit”. Stu was around and in the fray when the RDF standard was still in diapers, and recalled for the audience how easy we all thought it would be then to bring its promise to fruition. At least a decade later, we’re still trying to do that.

    In Stu’s opinion, the Web is the data model, and we shouldn’t deviate from it. He pointed out that with the issues of flexibility vs. constraints we are drawn in by the Siren Call of Flexibility but would be better off with more constraints.
    On the positive side, Stu points out that the linked data bulge has brought us a strong commitment to identifiers, some useful conventions about vocabularies and syntax, some tools to build ontologies and models, and some expectations of utility due to broad adoption – network benefits, in other words. But we still need to worry about data quality, usefulness, and bridging the boundaries between the existing semantic communities.

    Stu is skeptical of linked data as the new grail, but still thinks we’re on an exciting threshold—we need metadata more than ever, but we’re drowning in it. He quoted Tom Baker: “Data that cannot speak for itself will be more vulnerable to becoming irrelevant”.
    Stu’s last points covered DCMI as an ongoing experiment in social engineering. He cited Malcolm Gladwell’s article in the Oct. 4 New Yorker where Gladwell asserts that social media are largely broadly disseminated, networked, weak tie activities, with low barriers, low commitment, low persistence. Gladwell contends that systemic change requires strong ties, hierarchical social structures, leadership organization, and f2f work. Stu believes that DCMI is a strong tie phenomenon, and its impact is amplified by this fact.

  • AALL in Denver

    For the past few days I’ve been in Denver, as part of a commitment to present at a program entitled “The Semantic Web and RDA: Making the Catalog a Networked Bibliographic Environment.” The other speaker on the program was Karen Coyle, and both sets of slides for this program are available publicly, Karen’s on her site: http://kcoyle.net/presentations/ and mine at http://www.slideshare.net/smartbroad/aall-denver-2010.

    The presentations went well, and as Karen says “Every time we talk about this stuff, a few more people ‘get it’.” True enough, and though neither of us think we’re quite at the tipping point, it seems closer, somehow, when we present these ideas and people get excited.

    As we were having coffee after our star turn, a young woman came up to us and told us that, after two years as a law cataloger, she’d been thinking seriously about shifting into systems, but she was ‘really re-energized’ by our talk. That’s the best kind of compliment, and the kind that personally keeps me doing this, despite the downsides of travel and the cost in time it takes to do these presentations on a regular basis. Sadly, these kinds of gigs are really meant to be done by people with institutional support, like working librarians with real jobs, who do this sort of thing as a way to give back, to create a tenure record, or just to have time in what passes for the spotlight in librarianship. Karen and I are each trying to make a living as independent consultants, and the value proposition is very different for us.

    But the trip and the interactions gave me more ideas for my workshop, and that’s a good thing.

  • The curmudgeon’s table

    Today I participated in a Linked Data Unconference at ALA 2010 in Washington DC, which was remarkably successful. Organized by Corey Harper from NYU and ably moderated by Karen Coyle, about 50 of us held two sets of three hour-long, highly engaging breakout discussions with reports back to the larger group. I participated in a discussion of some of the practical difficulties encountered trying to implement Application Profiles in a far from perfect Linked Data environment (I strongly recommended creating a local mirror of inadequately expressed in RDFS/OWL, but otherwise useful, data models) and a discussion of scholarly Linked Data use cases and data reuse (we looked hard at VIVO and VIAF and discussed metering data usage). It was fun! I was surprised.

    Afterwards a few of us had a fine lunch together, discussing the nuts and bolts of RDA and the future of cataloging, a lively and fascinating discussion in the best possible sense of ‘lively’ and ‘fascinating’. It strikes me in retrospect that we formed a kind of curmudgeon’s table — Diane Hillmann, Corey Harper, Eric Hellman, Ed Summers, Karen Coyle, and me. All of us sharing strong opinions, agreeing and disagreeing whole-heartedly and with considerable good humor and affection. A table of warm and engaged people, knowing that it’s too late to save the world, maybe too late to save cataloging, but it would still be really interesting to try. It was great fun. I wasn’t the least bit surprised.

  • Mulling Midwinter

    One of the things I often do in the weeks following ALA conferences is check out the blog posts about sessions I missed attending. One such was the session on “Recent Trends in Catalog Architecture: ALCTS Catalog Form and Function Interest Group.” I don’t recall what we were doing instead of going to this session, but it looks like we missed a very interesting conversation. That happens far too often at the jam-packed Midwinter and Annual conferences—but thankfully these days the bloggers are keeping us all better informed. Laura Akerman has posted an interesting report of the IG’s session. Slides for this session are also available.

    One of the inescapable conclusions to draw from reading the reports is that the separation of metadata from display considerations seems to be well underway, at least if you consider those folks in the innovation corner. This is very welcome news, particularly for one who has had too many frustrating conversations over the past few years with folks whose heads are so deep into MARC that the revolutionary idea that display decisions are not inextricably tied to metadata fields is completely foreign. Also, it seems clear from the report that the notion of strict MARC-ish boundaries around what kinds of metadata libraries might be interested in providing in a discovery interface is no longer quite so impervious.

    I was struck by the blogger’s quote from the chair: “These presentations were varied but all concerned the architecture and functionality of multiple layers – “what happens (or needs to happen) in between” to transform, combine, and synchronize metadata.” It seems that everyone is traveling down this path these days, which is very good news indeed. In the search for appropriate metaphor that we’ve all done, Frances McNamara from the University of Chicago, the first presenter, called their aggregation of resources ‘stone soup’–a nice metaphor on the whole, though it does imply very hard lumps and not a lot of flavor. The second group of presenters, Joshua P. Barton & Lucas Wing Kau Mak from Michigan State University entitled their presentation “To Fix A Leaky Sink: Envisioning The Potential of Discovery Layers,” although this seems an oddly juicy metaphor for what blogger Laura Akerman described as primarily a “think piece.”

    The third presentation was by Jennifer Bowen, of the eXtensible Catalog Project (full disclosure: Jon and I worked with XC as consultants early on in their development and at various points since). XC’s view of metadata management borrows a great deal from the work we did (and published about) during the days when the National Science Digital Library (NSDL) was young and doing interesting things (before it became a development shop for the Fedora CMS). [Links to the original papers can be found at our website.) From the point of view of libraries looking at the management of metadata as something that happens outside of an ILS, their service architecture is by far their best stuff. In addition to Jennifer’s slides, anyone interested in what XC is doing should take a look at their recently released screencasts, particularly the first and the third, which includes a detailed description of what the MST (Metadata Services Toolkit) really does. Our metaphor for this functionality has always been “The Metadata Washing Machine,” so we’ve really no business complaining about anyone else’s choices!

    The last presentation was by Aaron Wood, of the University of Calgary, and the placement of this particular presentation is important, because it clearly points out that once you’ve created your soup and/or washed your dirty metadata, you still need to figure out how to present results to users in ways that are far different than what we’re used to in the typical ILS interface. Calgary uses the new Summon product from Serials Solutions (which, by the way, also builds on the notion of aggregated metadata services we pioneered in NSDL). The question that turns up in the blog post “how to prevent the local institution’s collections (print and digital) from becoming marginalized in search results when combined with a much larger number of full text resources (licensed journal articles etc.)” is right to the point, because it assumes, as we all should, that the usual alphabetic display that most of our ILS systems produce, that must be scrolled or paged through, is no longer good enough. The presentation points out something we found in NSDL several years ago, that when metadata records and full text are trolled for keywords, the full text always tends to rise to the top, and that’s not necessarily always a good thing from a user point of view. Metadata in general is a poor performer when simply treated as text by full-text indexers, not just because there’s not enough text, but also because full-text indexing generally perceives no additional value in controlled vocabularies and their relationship to well-defined properties (and the richness of the relationships that lie behind the vocabularies as well).

    But I’m sorry I missed this session, and thanks to Laura Akerman and the Metadata Blog for providing such a good summary of the session.

  • Ready for change

    Friday I was in Hyde Park, NY, at the site of the Franklin D. Roosevelt Presidential Library and Museum, attending the NYLINK Annual Meeting. I’d been asked to come and talk about change in cataloging. NYLINK, formerly the SUNY/OCLC Network, is one of the struggling regional service providers that used to be the primary brokers for OCLC services for smaller libraries, and did most of the training for OCLC in the process. These organizations are now providing other kinds of services and training for a wide variety of libraries, and are still one of the best places for figuring out what working librarians are thinking.

    I was particularly impressed with how this day-long meeting was organized. After the welcome and logistics, two speakers—Liz Chabot from Ithaca College and Susan Currie from Binghamton University—got things off with a bang by proposing seven “what ifs”:

    … we stopped cataloging?
    … librarians individually and as a profession promoted, used and helped develop Wikipedia?
    … we accepted open source software as a way of being in control of the customer experience?
    … we required all library staff to have expertise using technology?
    … mistakes were expected and embraced—and librarians became the mistake masters?
    … we didn’t make our customers work so hard?
    … we let customers determine their loan periods?

    Meeting participants spent some time talking about these questions, in the meantime getting to know one another at their tables, and getting fired up about the topics. The morning speaker, Joe Lucia from Villanova University, then started off with this energized group, and did a great job putting the important issues in a more general perspective. He spoke compellingly about our plight in libraries and the parallels with newspapers, described changes in how people deal with linear text vs. Hypertext, and pointed out the work of R. David Lankes (a colleague of mine at Syracuse University), who talks about the “library as conversation.” Joe’s primary point in bringing together these threads is his contention that libraries are not in the “information” business so much as we are in the “knowledge and conversation” business. He talked very passionately about the library as a “commons” where knowledge and conversation happen with the active engagement of the library as organization, bringing students, faculty and others out into the open for exchanges of ideas, not just providing places for their solitary study.

    But of course it will be no surprise that I was most engaged with the question “What if we stopped cataloging?” I’m not sure that question is the right one, or perhaps just not specific enough. I might recast it as “What if we stopped cataloging the same old stuff?” By “same old stuff” I mean the secondary products of academic pursuits: books, journals, government documents, etc., the stuff that we have always cataloged. What if we began to catalog different stuff, the stuff we’re publishing ourselves, the podcasts we create of the talks given by our own faculty and those who visit us to discuss their research, the exhibitions we create out of our collections and materials borrowed from others, the primary materials our former faculty members have donated into our care—the things that we’ve always consigned to others (archivists, perhaps?) or not cataloged at all. What we have called cataloging, when it is not done for the first time, is these days for the most part consigned to staff who may not be catalogers, bought from vendors, or automatically claimed from larger databases to populate ours. Insofar as we have used these more efficient, more automated strategies, we have indeed “stopped cataloging.” What we haven’t done is modified our missions and our budgets to take more responsibility for these other often unique things that we have neglected, and as such we have been the instruments of our own demise.

    So as we hear the bemoaning of the profession of cataloging, and ourselves sometimes obsess about the “how” of the changes in our lives brought on by technology, financial distress, and various other pressures, we would do well to remember that behind all this, the mission of the institutions we call home is changing significantly, and we can’t answer those “how” questions without looking anew at those shifting missions.

    My presentation and Corey Harper’s came after lunch, and the group was exceptionally ready to hear what we had to say, thanks to the fabulous preparation provided by NYLINK, Joe Lucia, Liz Chabot and Susan Currie. I had some great conversations there, and on the ride home thought quite a bit about how proud I am to be a librarian, and the wonderful opportunities I continue to have to get to know some of the best people in the business.

  • Making connections

    This past Friday I dug out my go-to-meeting clothes and made one of my occasional forays down one hill and up the other hill to my former place of work, Cornell’s Olin Library. The occasion was the monthly meeting of the CUL Metadata Working Group which I try to show up for when I’m not traveling. This month’s speaker was Sarah Shreeves, from the University of Illinois, Urbana-Champaign (UIUC). Now, I’ve known Sarah for some years, and have worked on a project or two with her, so this seemed like a perfect opportunity to dress up and get out of my cozy office for a morning to see what Sarah was up to. It helps that the weather is improving, this being pre-Spring in Ithaca (still largely gray skies, but mostly without the white underlay).

    Sarah’s presentation is described on a WG page devoted to her visit, though her slides aren’t up yet as I write this. She talked primarily about a project UIUC is working on with the University of Wisconsin, called BibApp. The project’s aims are focused around research and collaboration on college campuses, looking for ways to bring together experts, their output, and information about them. Sarah’s role at UIUC includes their institutional repository, the point person at UW is Dorothea Salo, a self-described “repository rat,” and the presentation made quite clear how BibApp provides important support for IR’s in general as well as alternatives to the clunky interfaces most of them come with.

    From my admittedly metadata-centric point of view the most interesting things Sarah demonstrated were the backend work they do with author name disambiguation and automating the determination of what can legally be deposited in the IR from the oeuvre of a particular author, based on the publisher of the item. Depending on the research community, these items may have metadata available from A & I providers, MARC metadata, or no metadata at all (book chapters and conference publications often fall in that last category). The project is developing a tool that can support the work of librarians or other trained staff in determining who an author with a particular surname and forename initial might be, using a combination of human and machine intelligence. Although it’s not authority work as we know it, once we get to a mashup phase in the new world of authorities, the data provided by this tool will be quite useful, based as it is on the occurrences in the publications themselves, as well as linkages to additional information on the author (his/her institutional affiliation, email address, etc.) There’s already a somewhat primitive XML output, but even as it flashed by (not on the presentation, but as part of the discussion) I could see some possibilities.

    In this application, being able to match the publisher name in the metadata with data about publisher policies to determine whether pre-prints, post-prints, author copies or all of the above can be legally deposited saves a great deal of time both for librarians and faculty. As Sarah was talking about this, I was struck by how clear a use case this was against traditional library practice of transcription of publisher information. I suggested this to Sarah and she agreed that they really needed standard forms, not transcribed data, to make this sort of tool function well. RDA’s approach is still focused on the idea that transcription is the best way to assure uniformity, but in my opinion that approach only provides the illusion of uniformity, and the number of LC Rule Interpretations for AACR2 on this point suggests that in a world where human resources will be spread thinner than ever it’s time to jettison transcription of important data elements. The alternative that we need to implement is to treat publishers as corporate bodies and control their names as we do other names, and this will certainly be technically possible in RDA, but is not what the guidance instruction tells catalogers to do.

    Another really nifty feature Sarah demonstrated was the analyses of publication patterns of different groups of researchers that were enabled by the tool once the publications themselves were available in one place. The BibApp tools are being tested using a variety of research groups, some science and others humanities, highlighting important differences between the cultures of these research areas. I was impressed by how sensible the approach of the developers has been, and how they appear to be using a nicely iterative approach to working through their results and keeping their goals in mind. In a world where university administrators need reminding of the importance of libraries and the work they do, this sort of project stands out like a beacon—meeting a number of promotional and marketing goals through a very librarian-ish organizational approach with some quick wins in the bargain.

    That said, this is not the ginzu knife that some may be looking for, and the developers are sensibly determined to keep it light weight and focused. Nice work, Sarah, and a very effective presentation as well.

  • Daniel Pitti on the EA*

    One of the nice things about being “retired” (even practice “retirement”) is that I get to work at home most of the time. There are few things that lure me to the Cornell campus these days—lunch with friends, maybe a lecture now and then—but I almost always go to the forums of the CUL Metadata Working Group. These started a few years ago and have been a godsend, both for those of us who have something to say (I’ve presented multiple times) and those of us who have something to learn (all of us). Like most such efforts, there’s some overhead in the form of a committee that schedules speakers, manages a small budget, etc., but the result is well worth it. Marketing efforts for the forums extend well past the library and often bring audiences from the campus IT organization, the computer and information science folks, and other orphans lodged in various departmental digital efforts.

    This month the speaker was Daniel Pitti, Associate Director of the Institute for Advanced Technology in the Humanities at the University of Virginia. I’ve known Daniel since the first Dublin Core meeting in 1995 (when he was working at Berkeley), so was not going to miss the opportunity to hear him talking about where archival description was headed.

    As advertised, Daniel gave some background about the EAD (Encoded Archival Description) as well as the EAC-CPF (Encoded Archival Context – corporate bodies, persons, and families). EAD is based on the the traditional archival finding aid, and focuses on the provenance-based description of archival resources where all records by a single created are treated as one unit. After setting the stage, Daniel spoke about the design of “post- finding aid” archival description systems, describing both the environment within which archival description is created and maintained and the possible published forms of the description that can be searched, rendered, and enhanced by users. I was interested, and pleased, to note that work on this post- finding aid world is based very much on a future I recognize, with a vision based both on what’s happening in libraries as well as what’s going on in the archival community. In a world where tectonic shifts are occurring in both areas, and the focus of library missions are shifting visibly towards the primary materials living in archival collections, this is a VERY GOOD THING.

    One of the interesting themes of Daniel’s presentation was “re-imagining description and access.” Librarians may notice the similarity to RDA: Resource Description and Access, and I suspect this is not an accidental echo. The analysis that he described, and the direction that archival description seems to be headed, bodes well for both archivists and librarians—I came away with hope that the trajectory of both efforts will result in the ability for descriptions created by either to be available to users without the necessity of the kind of mediation now required. Not without blood and angst, but perhaps within our lifetimes!

    Daniel also described the EAC-CPF, intended to provide a formal method for recording the description of record creators. I asked how this work correlated with similar efforts going on in libraries—FRAD, for instance. Daniel suggested that the inter-community dialog ought to start happening at this level, with the description of people. The first step in this has already happened, of course, with the inclusion of “Families” in RDA—a direct steal from archival description–but there are many steps yet to be taken.

    With RDA and the wonderful possibilities for bringing the archival and library communities closer together swirling in my mind, I was struck by one of Daniel’s final points, where he noted that the community was now thinking of a two-pronged approach to the post- finding aid world: permissive on the whole but with less permissive possibilities, which would tend over time to move things forward. This is surely an approach that has been discussed in the RDA world, but not yet well articulated, in my view.

    Daniel’s presentation is available on the CUL Metadata Working Group space on Cornell’s eCommons.