Category: Uncategorized

  • Moving Right Along

    My last birthday (tail end of 2018) was one of those with the zero at the end, which always inspires a look at those Big Life Questions: Where am I at this point in my life? Where do I want to go from here? How do I feel about my past, present and future? I’ve not been blogging lately, and part of that has been my necessary engagement with those questions. I know many of you will be in Seattle in a few days and might expect me to be there, but I won’t be. I’d like to reassure those of you who know me that I’m just fine, not dead or ill, nor totally disinterested in the issues that have interested me lo these many years (decades? Oy!).

    But I’ve always been aware that I don’t want to overstay my welcome—I’ve seen it happen, and am not interested in becoming someone who can’t let go of a career that has met a natural end, lacking the excitement of new ideas and the determination to share them in papers, blog posts, or rants in various venues. There’s also the frustration of discovering that there are far too many folks who look at the age of our vocabulary services and figure that they’re too old to pay attention to. It’s hard not to take that personally on occasion. But, take a gander at the “Latest Activity” feed on that geriatric home page, and you’ll see that the services behind it are far from dead.

    And much as I love the travel and connecting with friends I’ve made over the years, I just don’t have the bucks to keep attending ALA and other meetings without actual financial support. We still work, doing the things we’re good at, keeping our services up for those who have the sense to see that they still work (and are still free). We’re determined to keep that going for as long as we can (at this point it’s the ‘too cheap to fail’ strategy), but how long depends on Jon more than me. [I still enjoy doing workshops, so get in touch if that interests you or your group.]

    So what will I be doing instead of following the ALA herds from city to city? I’d like to get back to writing short stories, which I did several years ago and am drawn to continue. I’d like to find a place to set up my hammered dulcimer (someplace where the cats can’t perch on it!) and continue learning how to play it. I plan to continue with yoga (coming up on 18 years with the same teacher), and riding my bike along the rural roads where I live.

    And if you ever find yourself near centrally isolated Ithaca, do get in touch and I’m happy to show you around, or take some time for a drink or a meal, and a good conversation.

    So for those of you still on the path, do enjoy Seattle and it’s buzz and attractions, and have a great conference.

  • 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.

  • NISO report on Vocabulary Management

    I’d hoped to get a post out before ALA Annual but here it is Monday in Chicago and it’s not done yet. But I need to note that the draft report is out for comment as of this past Monday (June 19th) and comments are due by July 19th. To access the report, go to the NISO website (NISO.org) and look for recent announcements or press releases.

    There’s a lot in this report: starting with a description of the current environment for vocabulary development, the difficulties of sustainability, how funding affects the growth of tools and new vocabularies, and much more. There are a substantial number of case studies, illustrating points made in the report.

    There’s more work to be done–real best practices, for instance–but that should really be the responsibility of a new group with more experience with vocabularies. As yet NISO has not determined whether to sponsor such a group, but certainly commenters of the report could suggest an opinion.

  • 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.

  • The Jane-athons continue!

    The Jane-athon series is alive, well, and expanding its original vision. I wrote about the first ‘official’ Jane-athon earlier this year, after the first event at Midwinter 2015.

    Since then the excitement generated at the first one has spawned others:

  • the Ag-athon in the UK in May 2015, sponsored by CILIP
  • the Maurice Dance in New Zealand (October 16, 2015 at the National Library of New Zealand in Wellington, focused on Maurice Gee)
  • the Jane-in (at ALA San Francisco at Annual 2015)
  • the RLS-athon (November 9, 2015, Edinburgh, Scotland), following the JSC meeting there and focused on Robert Louis Stevenson
  • Like good librarians we have an archive of the Jane-athon materials, for use by anyone who wants to look at or use the presentations or the data created at the Jane-athons

    We’re still at it: the next Jane-athon in the series will be the Boston Thing-athon at Harvard University on January 7, 2016. Looking at the list of topics gives a good idea about how the Jane-athons are morphing to a broader focus than that of a creator, while training folks to create data with RIMMF. The first three topics (which may change–watch this space) focus not on specific creators, but on moving forward on topics identified of interest to a broader community.

    * Strings vs things. A focus on replacing strings in metadata with URIs for things.
    * Institutional repositories, archives and scholarly communication. A focus on issues in relating and linking data in institutional repositories and archives with library catalogs.
    * Rare materials and RDA. A continuing discussion on the development of RDA and DCRM2 begun at the JSC meeting and the international seminar on RDA and rare materials held in November 2015.

    For beginners new to RDA and RIMMF but with an interest in creating data, we offer:
    * Digitization. A focus on how RDA relates metadata for digitized resources to the metadata for original resources, and how RIMMF can be used to improve the quality of MARC 21 records during digitization projects.
    * Undergraduate editions. A focus on issues of multiple editions that have little or no change in content vs. significant changes in content, and how RDA accommodates the different scenarios.

    Further on the horizon is a recently approved Jane-athon for the AALL conference in July 2016, focusing on Hugo Grotius (inevitably, a Hugo-athon, but there’s no link yet).

    NOTE: The Thing-a-thon coming up at ALA Midwinter is being held on Thursday rather than the traditional Friday to open the attendance to those who have other commitments on Friday. Another new wrinkle is the venue–an actual library away from the conference center! Whether you’re a cataloger or not-a-cataloger, there will be plenty of activities and discussions that should pique your interest. Do yourself a favor and register for a fun and informative day at the Thing-athon to begin your Midwinter experience!

    Instructions for registering (whether or not you plan to register for MW) can be found on the Toolkit Blog.

  • What’s up with this Jane-athon stuff?

    The RDA Development Team started talking about developing training for the ‘new’ RDA, with a focus on the vocabularies, in the fall of 2014. We had some notion of what we didn’t want to do: we didn’t want yet another ‘sage on the stage’ event, we wanted to re-purpose the ‘hackathon’ model from a software focus to data creation (including a major hands-on aspect), and we wanted to demonstrate what RDA looked like (and could do) in a native RDA environment, without reference to MARC.

    This was a tall order. Using RIMMF for the data creation was a no-brainer: the developers had been using the RDA Registry to feed new vocabulary elements into their their software (effectively becoming the RDA Registry’s first client), and were fully committed to FRBR. Deborah Fritz had been training librarians and other on RIMMF for years, gathering feedback and building enthusiasm. It was Deborah who came up with the Jane-athon idea, and the RDA Development group took it and ran with it. Using the Jane Austen theme was a brilliant part of Deborah’s idea. Everybody knows about JA, and the number of spin offs, rip-offs and re-tellings of the novels (in many media formats) made her work a natural for examining why RDA and FRBR make sense.

    One goal stated everywhere in the marketing materials for our first Jane outing was that we wanted people to have fun. All of us have been part of the audience and on the dais for many information sessions, for RDA and other issues, and neither position has ever been much fun, useful as the sessions might have been. The same goes for webinars, which, as they’ve developed in library-land tend to be dry, boring, and completely bereft of human interaction. And there was a lot of fun at that first Jane-athon–I venture to say that 90% of the folks in the room left with smiles and thanks. We got an amazing response to our evaluation survey, and the preponderance of responses were expansive, positive, and clearly designed to help the organizers to do better the next time. The various folks from ALA Publishing who stood at the back and watched the fun were absolutely amazed at the noise, the laughter, and the collaboration in evidence.

    No small part of the success of Jane-athon 1 rested with the team leaders at each table, and the coaches going from table to table helping out with puzzling issues, ensuring that participants were able to create data using RIMMF that could be aggregated for examination later in the day.

    From the beginning we thought of Jane 1 as the first of many. In the first flush of success as participants signed up and enthusiasm built, we talked publicly about making it possible to do local Jane-athons, but we realized that our small group would have difficulty doing smaller events with less expertise on site to the same standard we set at Jane-athon 1. We had to do a better job in thinking through the local expansion and how to ensure that local participants get the same (or similar) value from the experience before responding to requests.

    As a step in that direction CILIP in the UK is planning an Ag-athon on May 22, 2015 which will add much to the collective experience as well as to the data store that began with the first Jane-athon and will be an increasingly important factor as we work through the issues of sharing data.

    The collection and storage of the Jane-athon data was envisioned prior to the first event, and the R-Balls site was designed as a place to store and share RIMMF-based information. Though a valuable step towards shareable RDA data, rballs have their limits. The data itself can be curated by human experts or available with warts, depending on the needs of the user of the data. For the longer term, RIMMF can output RDF statements based on the rball info, and a triple store is in development for experimentation and exploration. There are plans to improve the visualization of this data and demonstrate its use at Jane-athon 2 in San Francisco, which will include more about RDA and linked data, as well as what the created data can be used for, in particular, for new and improved services.

    So, what are the implications of the first Jane-athon’s success for libraries interested in linked data? One of the biggest misunderstandings floating around libraryland in linked data conversations is that it’s necessary to make one and only one choice of format, and eschew all others (kind of like saying that everyone has to speak English to participate in LOD). This is not just incorrect, it’s also dangerous. In the MARC era, there was truly no choice for libraries–to participate in record sharing they had to use MARC. But the technology has changed, and rapidly evolving semantic mapping strategies [see: http://dcpapers.dublincore.org/pubs/article/view/3622] will enable libraries to use the most appropriate schemas and tools for creating data to be used in their local context, and others for distributing that data to partners, collaborators, or the larger world.

    Another widely circulated meme is that RDA/FRBR is ‘too complicated’ for what libraries need; we’re encouraged to ‘simplify, simplify’ and assured that we’ll still be able to do what we need. Hmm, well, simplification is an attractive idea, until one remembers that the environment we work in, with evolving carriers, versions, and creative ideas for marketing materials to libraries is getting more complex than ever. Without the specificity to describe what we have (or have access to), we push the problem out to our users to figure out on their own. Libraries have always tried to be smarter than that, and that requires “smart” , not “dumb”, metadata.

    Of course the corollary to the ‘too complicated’ argument lies the notion that a) we’re not smart enough to figure out how to do RDA and FRBR right, and b) complex means more expensive. I refuse to give space to a), but b) is an important consideration. I urge you to take a look at the Jane-athon data and consider the fact that Jane Austen wrote very few novels, but they’ve been re-published with various editions, versions and commentaries for almost two centuries. Once you add the ‘based on’, ‘inspired by’ and the enormous trail created by those trying to use Jane’s popularity to sell stuff (“Sense and Sensibility and Sea Monsters” is a favorite of mine), you can see the problem. Think of a pyramid with a very expansive base, and a very sharp point, and consider that the works that everything at the bottom wants to link to don’t require repeating the description of each novel every time in RDA. And we’re not adding notes to descriptions that are based on the outdated notion that the only use for information about the relationship between “Sense and Sensibility and Sea Monsters” and Jane’s “Sense and Sensibility” is a human being who looks far enough into the description to read the note.

    One of the big revelations for most Jane-athon participants was to see how well RIMMF translated legacy MARC records into RDA, with links between the WEM levels and others to the named agents in the record. It’s very slick, and most importantly, not lossy. Consider that RIMMF also outputs in both MARC and RDF–and you see something of a missing link (if not the Golden Gate Bridge :-).

    Not to say there aren’t issues to be considered with RDA as with other options. There are certainly those, and they’ll be discussed at the Jane-In in San Francisco as well as at the RDA Forum on the following day, which will focus on current RDA upgrades and the future of RDA and cataloging. (More detailed information on the Forum will be available shortly).

    Don’t miss the fun, take a look at the details and then go ahead and register. And catalogers, try your best to entice your developers to come too. We’ll set up a table for them, and you’ll improve the conversation level at home considerably!

  • Why You Should Come to the Jane-athon

    I know many of you are puzzled by this event, so do take a look at a rundown of the plans on the RDA Toolkit Blog.

    Not so surprisingly, we were inspired by the notion of a hackathon, but it had to be focused on something other than computer code and application building. All of us have heard conflicting opinions about whether RDA can be fully functional, whether FRBR works and will benefit users, or whether it’s just all too complicated. The big gap in addressing these questions has been the challenge in doing something hands-on instead of the usual sage-on-the-stage doling out large piles of handouts. There are still realities that need to be recognized, as we take a hands-on look at RDA and build some real RDA data.

    First of these realities is that RDA has been in development for a hell of a long time, and the rules (the part that gets the most attention, and some think really IS the whole of RDA) started out as AACR3. As one who’s been watching this space (from the outside and the inside) since the beginning, I can confirm that the the notion of AACR3 is a historical artifact, nothing to do with what RDA has become.

    I’ve been ranting and railing for years (too many to count) that RDA must be more than rules. And it is–see the RDA Registry for evidence of that. This leads me to the second reality: all of us are learning as we go. The first iteration of the RDA Vocabularies, developed by the DCMI/RDA Task Group after a famous meeting in London in the Spring of 2007, were never published. The published version, much improved, was released early in 2013 along with the new RDA Registry. The learning-by-doing was happening in a lot of other standards-focused groups: IFLA and W3C for example. FRBR, an essential part of the RDA model, was evolving along with RDA, and that fact led to a couple of interesting compromises, still working themselves out.

    I can promise you that the Jane-athon will reflect all of those realities, and in addition build out the community familiar with the lessons yet to be learned. There won’t be any papering over of gaps, downplaying of issues, or anything like that. At the Jane-athon we will demonstrate that building real RDA records in the context of FRBR is not a future dream, it’s happening now. What you will see as a participant is the reality–the ability to work within a FRBR flow, to import MARC records and see the system map them into FRBR constructs, to create links with NAF information, and view the results as a tree that highlights the relationships.

    Perhaps most important, we want to have fun with this. There will be no quizzes, no grades, no transcripts. That’s why we chose to focus on two sets of materials with great potential to benefit from a FRBR-based approach. Early in the day you’ll walk through the business of creating cataloging for Blade Runner resources (original book by Philip K. Dick), translations, film, etc. After that we’ll turn the group loose on Jane Austen (with some made-ahead basic data). After the flurry of data creation, we’ll be looking at the results, highlighting issues that come up, and not incidentally, getting some feedback from the participants about the tools, processes, and the beta-Jane-athon in its entirety.

    We know (and welcome the fact) that not everyone attending will be a cataloger, much less all that familiar with RDA. There will be a place and a role for everyone who wants to learn more, and to dig in and get their hands [virtually] dirty. There is no need to cram for this event, or to study the RDA rules or cataloging before you come. If you want to get a bit familiar with RIMMF before you come, by all means take a look at the site, download the software, and play. The only requirement is an open mind and some excitement about the possibilities (some trepidation is okay too).

    Once you have registered for ALA Midwinter in Chicago, you can sign up for the Jane-athon.The Jane-athon is already available as a paid addition of the full registration for ALA Midwinter in Chicago.

    Please feel free to use the comments portion of this post to ask questions, or use the RDA-L list to bring up questions and concerns.

    We hope to see you there!

  • Talking Points Report

    Prior to Midwinter I posted the list of presentations I was doing over the course of Midwinter. It seemed only fair to report on some of those sessions, and to share my slides. I thought about posting them separately, since my posts tend to balloon fairly significantly once I get writing (those of you who know me are free to point out that I talk like that, too)–but given that I’ve decided to post more often, y’all will have to live with length.

    Saturday, January 25, 2014, 3:00-4:00 p.m., “A Consideration of Holdings in the World Beyond MARC” [Slides]

    There were two speakers at this session, at which I spoke second. The first speaker was Rebecca Guenther, who spoke on BibFrame generally as well as the BibFrame approach to holdings. BibFrame currently has a fairly simple approach, for now limited to the simpler holdings needs for non-serials. This is the easy [easier?] part of course, and it will be interesting to see how serial holdings will be integrated with the model.

    My presentation briefly surveyed other important holdings work in progress, including a project at the Deutschen National Bibliothek (DNB), the ONIX for Serials Coverage Statement, the current proposals for schema.org, to a brief report on a project my group is considering that would do for MARC Holdings (sample) what we’ve already set up for MARC Bibliographic data at http://marc21rdf.info.

    What struck me when I was setting up the presentation was the amazing variety of work going on in this area. I really didn’t expect that, I confess. But by immersing myself in holdings as I hadn’t done for many moons, I found I was looking at an awful lot of very recent work. And it wasn’t just the diversity of approaches that surprised me, but the varied results as well. The efforts ran the gamut from very complex and comprehensive approaches (ONIX and MFHD) to much simpler approaches. The functions anticipated for each colored the diverse outcomes to a great extent. The ONIX XML schema was easily the most complex–with some ideas based on the MFHD work.

    The schema.org effort is, like BibFrame, still in the process of jelling. When looking for the evidence of schema.org holdings, I found myself on a path that had already been abandoned (though it then showed no signs of abandonment). Richard Wallis pointed me at the right place, and the slides have been corrected to fix that problem.

    Sunday, January 26, 2014, 8:30-10:00 a.m., “The Other Side of Linked Data: Managing Metadata Aggregation” [Slides]

    This session also included two presentations, mine was first this time. My focus was that most people think Linked Open Data (LOD) is about libraries exposing their data to the world, but that’s only half of LOD. The other half is taking advantage of the data others (libraries and non-libraries) are exposing openly. The two fundamental things about the LOD world are both ideas that tend to explode minds. First is the realization that we’re not talking about highly OCLC-curated MARC records, pre-aggregated for easy ingest into traditional library systems. Instead, we are talking about management of statements (which may indeed be records as originally ingested, but to be useful in this multiple choice world must be shredded on the way in and re-aggregated on the way out.) There are many new skills we’ll have to learn (and an awful lot of assumptions that we’ll need to examine closely and maybe toss out the window). This is daunting, but hardly rocket surgery, and the sooner we get going, the better off we’ll be.

    The second presentation was from a group working at the Digital Public Library of America (DPLA), which is confronting many of these issues. Their announcement stated:

    “This talk will introduce and outline the challenges of aggregating disparate metadata flavors from the perspective of both DPLA staff and representative hubs. We will review next steps and emerging frontiers as well, including improvements to normalization at the hub level and wider adoption of controlled vocabularies and formats for geospatial metadata and usage rights statements.”

    And this was exactly what they did. They provided a very juicy look at the real world that faces anyone attempting to deal with the current metadata chaos. This is definitely work to follow, because where they are now will change over time and with experience, providing the rest of us with some really useful insights. Their slides are available from the IG site.

    Sunday, January 26, 2014, 10:30-11:30 a.m., “Mapmakers” [Slides]

    The Mapmakers presentation was designed to highlight some research I’ve been involved in, along with my colleagues Jon Phipps and Gordon Dunsire. This topic has not received a vast following, but should as experience with new schemas and value vocabularies expands. As is usual, there was another presentation just before ours that gave an exciting view of innovative work in expanding our notion of authority, in particular gathering and managing data from a broad variety of sources. Their work is encountering very similar challenges as the DPLA, though in some ways even more challenging since they often have to develop the sources and bring them into the LOD world.

    That presentation focused on work done in the ProMusicaDB project, with founder Christy Crowl and metadata librarian Kimmy Szeto sharing the podium. There was a feast of slides and stories, all of them illustrating the new ways that we’ll all be operating in the very near future. Their slides (including a demo) should be available on the ALCTS Cataloging and Classification Research IG site very shortly (though not yet as of this writing).

  • Libraries, FOAF, and community

    Note: this is being posted simultaneously on two blogs: Metadata Matters and Coyle’s InFormation

    “Why don’t libraries just use FOAF for their Person metadata? Why do they insist on creating their own?”

    We don’t know how many times we have heard this on various lists. It often is not really posed as a question; in other words, it isn’t asking for an explanation of why libraries do not choose to use FOAF. It’s more rhetorical, along the lines of “Why can’t we all just get along?” But it is worthy of being asked as a real question, and of getting a real answer.

    [Note first that the question of FOAF comes up not so much as we consider the current library standards, but in discussions of upcoming standards that will hopefully be based on the FR** family of standards (FRBR, FRAD, FRSAR). ]

    A comparison of FOAF Person and the library Person entity (either in MARC authority files, or RDA, or FRAD) shows that there is not one defined element (or “property” as it is called in Semantic Web-ese) that the two have in common. This is not a coincidence; the two vocabularies serve significantly different communities and purposes. This does not mean that they are irreconcilable; the question therefore becomes: What keeps them apart? and can that be overcome?

    The key is in the nature of the two communities.

    FOAF stands for ‘Friend of a Friend’, which is a clue to its context: the schema is primarily for use in social networking situations. Its focus is on people who are alive and online, and it includes online contact information like email addresses, web sites, work web sites, Facebook IDs, Skype IDs, etc. The name of the person in FOAF is not an identifier, but presumes that the name of the person plus one or more of the contact IDs is enough to distinguish most humans from one another.

    Library name data (which is a form of controlled vocabulary, called “name authority data” in library terms) is focused on creating a unique identifier that brings together the different forms of a name used in published materials under one form. Library users, therefore, can expect to find all of the works by or about a named person under a single entry regardless of the various forms of the name that exist in real data. Uniqueness of names is enforced by adding information to a non-unique name, usually the year of birth, but when that isn’t known (especially for persons of antiquity) titles or even areas of endeavor (“poet”) can be added.

    To accommodate both the FOAF (social) function and the libraries’ identification function, at the very least the libraries would need to define a sub-property of FOAF Person, one that has a more strict definition and usage. However, for the library “Person” to be designated as more specific than FOAF:Person does not require that these two be in the same vocabulary. That is one of the important features of Semantic Web properties: like any other resource, they can be linked and related to any other resources on the Web.

    Why not combine the library and FOAF properties into a single metadata vocabulary? The answer has little to do with technology, but instead relates to the functioning of communities. Metadata standards need to be developed by (and for) actual communities. The FOAF and library communities clearly have different needs, different goals, and are working with fundamentally different use cases. They also are significantly different as communities.

    FOAF is being developed by an informal group of developers, and is quite recent in origin. The group is small: the FOAF development email list has about 350 members. Another 350 individuals are listed on the FOAF wiki pages as having a FOAF profile available on the Web. This is obviously not the full extent of FOAF usage, but these numbers reflect the recent development of this kind of metadata.

    The library community has hundreds of years of investment in the creation of metadata (even though it was not called that when libraries began to create it). There are at least tens of thousands of libraries in the world, many of which have been in existence for centuries. Library data has its origins in early 19th century book catalogs but has been created in a machine-readable format since the late 1960’s. Library data is created following formal rules governed in part by international agreements, and there are many hundreds of millions of machine-readable bibliographic records in existence that were created based on these library cataloging principles.

    Libraries have engaged in wide-spread data sharing for centuries, and with the global networking capabilities of today libraries are actually able to exchange and re-use data on a huge scale. Libraries do not each create metadata for the same book or item, but instead share the metadata created by one library in cooperative efforts oriented towards resource sharing and efficiency.

    This sharing is built into the very core of library data management. The ability to use data created by others is supported by standards and those standards form the basis for the library systems. While most users see only the library catalog available to the public, that is only one function of a system that supports purchasing, fund accounting, inventory control, circulation and patron management, and collection analysis. In the Western world these systems are not created and maintained by libraries but by a small number of specialized commercial vendors whose products are specifically created for the library customers using agreed library standards. Thus the very same system can be sold to hundreds or thousands of libraries, creating a viable market base for system development.

    A number of the 70,000 libraries contributing to OCLC are using a single standard, MARC21, and others are following international standards such as ISBD that produces standardized bibliographic description. The development of these standards is based on a large scale community process with international participation. It is not a perfect process by any means, and clearly must be updated to meet modern needs and new technologies that have changed the way we work, but the degree of data sharing libraries depend on requires that a formal process be in place to support the standards of this community.

    Sharing of data on a large scale is necessitated by the economic reality of the library sector. Libraries face increasingly shrinking budgets while coping with an upswing in demand for their services. Realistically, this means that changes to library data must be carefully coordinated in order to minimize disruption to the complex network of data sharing that makes cost-effective library services management, based on this data, possible. Libraries may appear to be mistrustful of change agents, and in some cases they certainly are, but there is a real need to minimize risk for the community as a whole in order to assure the health of these often financially fragile institutions.

    So we come back to the question of libraries and FOAF. In the final analysis, we’re not at all sure that there’s much gain in trying to combine these two approaches, with the differences in their communities and functions. It could be like trying to combine oil and water, requiring compromises that in the end would be less than satisfactory for both communities. One could argue that the difference between the vocabularies and their contexts is a positive, allowing more than one view of the Person entity. As two separately maintained metadata vocabularies, anyone creating metadata can choose from either as needed without sacrificing precision. One can also imagine other views that will arise, such as Persons in medical data or financial data, which would each carry data elements that are neither in FOAF nor library data, from blood type to bank balance. The important thing is to make sure that these vocabularies are properly described and related to each other where possible. That way, each community can manage its own process based on its needs for standards integration, but data can be shared where appropriate.

    We could begin with a more detailed discussion between the FOAF and the library communities about their metadata needs. With hundreds of years of experience in representing names in library catalogs, we feel confident that the library community’s knowledge could contribute in general to the use of personal names in the Semantic Web.

  • Curmudgeon redux

    When I used the word “curmudgeon” in my previous post, I had an apparently uncommon definition in mind: unflinching truth teller. I’ve actually taken minute pleasure in thinking of myself that way ever since, in the not-so-long ago I asked my new boss what my new role on the team would be and, knowing me, he said “curmudgeon?”. I had to hunt a bit to find a definition that wasn’t the Andy Rooney-esque “crusty, ill-tempered, old man”, but I kind of liked this one:

    …Nature, having failed to equip them with a servicable denial mechanism, has endowed them with astute perception and sly wit.

    Curmudgeons are mockers and debunkers whose bitterness is a symptom rather than a disease. They can’t compromise their standards and can’t manage the suspension of disbelief necessary for feigned cheerfulness. Their awareness is a curse.

    Perhaps curmudgeons have gotten a bad rap in the same way that the messenger is blamed for the message: They have the temerity to comment on the human condition without apology. They not only refuse to applaud mediocrity, they howl it down with morose glee. Their versions of the truth unsettle us, and we hold it against them, even though they soften it with humor.

    – JON WINOKUR