Category: Uncategorized

  • We don’t need no stinking Access Points

    …in the RDA Ontologies. Do we? After all, they’re a big part of the ‘Access’ in Resource Description and Access (RDA). But they’re not particularly semantically meaningful, especially if you have the component parts available. An Access Point is just a structured string. For instance a ‘Publication Statement’ Access Point for “The Daytona daily news” might look like:

    “Daytona Beach, Florida : Geo. F. Crouch, 1903-1926”

    It has a formal syntactic structure, and semantics derived from adherence to that structure when the string is created:

    “Place of Publication” : “Publisher’s Name”, “Date of Publication”

    Note that the punctuation is part of the formal grammar that helps parse a grammatically correct statement into its semantically meaningful constituent parts.

    And this is the way we’ve been doing things forever (well it seems like forever) — semantics is derived from proper use of a syntax that everybody who is creating and using shared data has agreed upon in advance. And as long as everybody uses precisely the same syntax this works great. It works really, really well with structured syntaxes like MARC21:

    260 $a Daytona Beach, Florida
    260 $b Geo. F. Crouch
    260 $c 1903-1926

    …and hierarchical syntaxes like XML:

    <publicationStatement>
      <placeOfPublication>Daytona Beach, Florida</placeOfPublication>
      <publisherName>Geo. F. Crouch</publisherNam>
      <dateOfPublication>1903-1926</dateOfPublication>
    </publicationStatementt>

    The RDA documents go so far as to call an Access Point an Element and its constituent parts Sub-Elements, again clearly thinking of this nice syntacticly-defined semantics.

    But what if your data says, semantically, that “Place of Publication” isn’t the Name of the place or the Label for the place, but a URI that identifies the Place itself; a resource rather than a string. The Access Point rules don’t let you stick a URI in the Publication Statement where a string is supposed to be.

    What about “Publisher’s Name”? That’s clearly going to be a string no matter what — names tend not to be resources. But there’s probably a Publisher resource out there, somewhere, with a URI that identifies the Publisher and probably has a Name or a Label property that provides a string that you can stick in the Publication Statement.

    We’ll just ignore “Publication Date” for the now, since that’s a very different can of worms: slimy, smelly worms.

    At the moment, RDA doesn’t acknowledge the existence of the resources supplying the strings for an Access Point, and it lets substantial ambiguity sneak in with property names like “Place of Publication” rather than “Place of Publication Name” like they resolved with “Publisher’s Name”. But that ambiguity didn’t exist when all the data was strings — strings you used for indexing, and displayed to the user, and didn’t have to go fetch from somewhere because they were right there in that 260 field.

    I listened to a radio program that referred to all of the money that everyone in the world has available to invest as “The Global Pool of Money” and I think that applies quite nicely to the Linked-Data notion of the Semantic Web — “The Global Pool of Data”.

    The open world model of the Semantic Web assumes that you will never have all of the available data that describes a resource, and the RDF data model supports this. Resources often exist, outside of traditional library data, available from the Global Pool of Data, that can supply the necessary labels.

    But of course we usually just have the labels. This is library data made for cards that need to be put in the correct order and read by a person. And the Global Pool of Data usually just has a bunch of resources. This is linked data, in no particular order at all, meant to be read by a machine.

    So, specifying Access Points as pre-coordinated strings actually provides us with a major opportunity when defining the ontologies; several opportunities actually:

    • We can formalize each Access Point specification into what Dublin Core calls a Syntax Encoding Scheme (SES) and say that each Access Point has a datatype.
    • We can clarify the semantics of using a label rather than a resource for properties (sub-elements) like “Publisher’s Name”
    • We can clarify the semantics of using a resource for “Place of Publication” and say that the label used in an Access Point must be the Name of the Place and this is distinctly different.

    So, refined to use properties that are a bit more semantically clear, we have a slightly modified Publication Statement:

    “Place of Publication Name” : “Publisher’s Name”, “Date of Publication”

    …we tie these properties specifically to a FRBR Manifestation that RDA says must be what they describe, and in RDF the supporting ontology looks like:

    rda:placeOfPublicationManifestation a owl:ObjectProperty
    rda:PlaceOfPublicationName a owl:DatatypeProperty
    rda:publisherManifestation a owl:ObjectProperty
    rda:PublisherName a owl:DatatypeProperty

    Here’s our sample instance again (by the way, this data is from a real linked data resource):

    “Daytona Beach, Florida : Geo. F. Crouch, 1903-1926”

    <http://chroniclingamerica.loc.gov/lccn/sn93063916>
      rda:publisherManifestation <http://???> (blank, but we know one must exist)
        rda:PublisherName "Geo. F. Crouch"
      rda:placeOfPublicationManifestation <http://dbpedia.org/resource/Daytona_Beach%2C_Florida>
        rda:PlaceOfPublicationName "Daytona Beach, Florida"
        rdfs:label "Daytona Beach, Florida"

    This tiny chunk of data was gathered by hand and mapped (by me) from the existing resources and the labels supplied by those resources.

    Someday there will be services that comb through linked data looking for missing data like that Publisher resource, and will perform a search on the Global Pool of Data looking for resources with labels matching that library data, expressed in RDA/RDF, fill in the missing pieces and present the lucky cataloger, and ultimately the user, with all that rich linked data.

    The eXtensible Catalog project is working on services that do just that kind of thing, so someday may not be too far off.


  • Rachel Heery, in memoriam

    Last week I was in the UK, primarily to attend a DCMI Registry Community Workshop organized by UKOLN, scheduled for Friday, July 24th. Early the following week we found out that as we were gathered in York discussing distributed registries, Rachel Heery passed away after a long battle with breast cancer. Rachel was one of the founders of the Community (then called a working group), and was involved in building a number of registries, including the DCMI Registry and the IEMSR Registry at UKOLN.

    There have been a lot of postings about Rachel this week from colleagues and friends, and I wanted to add my voice to that chorus of tributes to an exceptional person. I didn’t know Rachel as well as I would have liked—we worked on different continents and generally crossed paths primarily at DC conferences. But we were both members of two distinct minorities within DCMI: women, and implementers. Neither of us trained as technologists, and came to the sometimes dauntingly technical discussions at DCMI from the point of view of those trying to use DC for real projects, too often frustrated with the 50,000 foot viewpoints expressed by the more technically astute.

    Stu Weibel, who knew Rachel, as I did, in the context of Dublin Core, brought her back for me the most strongly by reminding me of one of Rachel’s characteristic interjections:

    “We emulate those we admire, and I have often found myself over the years using a phrase that signaled, from Rachel, an objection worthy of discussion… a sort of lilting “Hang on…!” Those who have worked with her will hear echoes of the tone and inflection that made the phrase hers, and commanded respectful attention, a flag that something was not quite right. I always think of her when I say it, and will always try to use it in the service of the honest brokerage of common goals that characterized Rachel’s efforts.”

    Stu also reminds us that Rachel’s two most important contributions to the DC efforts (aside from her considerable intellect and personal presence) were in the areas of registries and application profiles–both have been a particular focus for me and Jon over the past four years or so. It gives me some solace to think that she would be pleased that implementers are still working hard in the areas she pioneered, though sad beyond measure that she will not see those efforts bear their promised fruit.

    Others who comment on Rachel’s influence and career:
    Lorna Campbell
    Andy Powell
    Lorcan Dempsey
    Her UKOLN colleagues

  • LCSH, SKOS and pre-coordinated headings

    This week, Karen Coyle wrote a post about LCSH as linked data: beyond “dash-dash” which provoked a discussion on the id.loc.gov discussion list.

    It seems to me that there are several memes at play in this conversation:

    LCSH and SKOS

    As Karen points out, LCSH is more than just a simple thesaurus. It’s also a set of instructions for building structured strings in a way that’s highly meaningful for ordering physical cards in a physical catalog. In addition, each string component has specific semantics related to its position in the string, so it’s possible, if everyone knows and agrees on the rules, to parse the string and derive the semantics of each individual component. The result is a pre-coordinated index string.

    These stand-alone pre-coordinated strings are perhaps much less meaningful in the context of LOD, but this certainly doesn’t apply to the components. I think what Karen is pointing out is that, while it’s wonderful to have a subset of all of the components that can be used to construct LC Subject Headings published as LOD, there’s enough missing information to reduce the overall value. As I read it, she’s wishing for the missing semantics to be published as part of the LCSH linked data, and hoping that LC doesn’t rest on its well-earned laurels and call it a day.

    Structured Strings

    Dublin Core calls the rules that define a structured string a "Syntax Encoding Scheme" (SES) and basically, that’s what the rules defining the construction of LC Subject Headings seem to be. It’s structurally no different than saying that the string "05/10/09", if interpreted as a date using an encoding scheme/mask of "mm/dd/yy", ‘means’ day 10 in the month May in the year 2009 using the Gregorian calendar. Fascinatingly, that same ‘date’ can be expressed as a Julian date of "2454962", but I digress.

    As far as I can tell, no one has figured out a universally accepted (or any) way to define the semantic structure of a SES in a way that can be used by common semantic inference engines, and I don’t think that anyone in this discussion is asking for that. What’s needed is a way to say "Here’s a pre-coordinated string expressed as a skos:prefLabel, it has an identity, and here are it’s semantic components."

    Additional data

    So…

    "Italy--History--1492-1559--Fiction"

    …is expressed in http://id.loc.gov/authorities/sh2008115565#concept as…

    @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
    @prefix skos: <http://www.w3.org/2004/02/skos/core#> .  
    @prefix terms: <http://purl.org/dc/terms/> .  
    @prefix owl: <http://www.w3.org/2002/07/owl#> .
    
    <http://id.loc.gov/authorities/sh2008115565#concept>
        skos:prefLabel "Italy--History--1492-1559--Fiction"@en ; 
        rdf:type ns0:Concept ;    
        terms:modified "2008-03-15T08:10:27-04:00"^^<http://www.w3.org/2001/XMLSchema#dateTime> ; 
        terms:created "2008-03-14T00:00:00-04:00"^^<http://www.w3.org/2001/XMLSchema#dateTime> ; 
        owl:sameAs <info:lc/authorities/sh2008115565> ; 
        skos:inScheme
            <http://id.loc.gov/authorities#geographicNames> , 
            <http://id.loc.gov/authorities#conceptScheme> ; 
        terms:source "Work cat.: The family, 2001"@en . 

    …and has a 151 field expressed in the authority file as…

    151 __* |a *Italy* |x *History* |y *1492-1559* |v *Fiction

    …which has the additional minimal semantics of…

    <http://id.loc.gov/authorities/sh2008115565#concept>
        loc_id:type "Geographic Name" ; #note that this is also expressed as a skos:inScheme property
        loc_id:topicalDivision "History" ;
        loc_id:chronologicalSubdivision "1492-1559" ;
        loc_id:formSubdivision "Fiction" ;
        loc_id:geographicName "Italy" .

    …and this might also be expressed as…

    <http://id.loc.gov/authorities/sh2008115565#concept>
       loc_id:type http://id.loc.gov/authorities/sh2002011429 ;
       loc_id:topicalDivision http://id.loc.gov/authorities/sh85061212 ;
       loc_id:formSubdivision http://id.loc.gov/authorities/sh85048050 ;
       loc_id:geographicName http://id.loc.gov/authorities/n79021783 ;
       dc:temporal "1492-1559" ;
       dc:spatial http://sws.geonames.org/3175395/ ;
       dc:spatial http://id.loc.gov/authorities/n79021783 .

    Making sure that those strings in the first example are expressed as resource identifiers is also something that I think Karen is asking for. (BTW, The ability to lookup a label by URL at id.loc.gov is really useful)

    I should point out that Ed, Antoine, Clay, and Dan’s DC2008 paper detailing the conversion of LCSH to SKOS goes into some detail (see section 2.7) about the LCSH to SKOS mapping, but doesn’t directly address the issue that Karen is raising about mapping the explicit semantics of the subfields.

  • Embrace the chaos

    I’m at the code4lib conference this week and I’m writing this as a reminder to myself for next year that, well, I just don’t care…

    I don’t care about the latest faceted search. I don’t care about the latest Open Source OPAC replacement. I don’t care about the latest Open Source ILS. I don’t care about project updates or software demos. I don’t care about API/standards/vendor/LC/OCLC bashing. I don’t care about reinventing the 20th century training wheels that library coders are so obsessed with (it’s their job after all).

    The people here are great, and I care about them both individually and as a class — I have a genuine affinity for library geeks of all kinds and this is, after all, a conference that tends to filter out everyone else. So it’s not like it’s not nice to be here, but the information being presented is useless to me to the point of irritation. And despite the fact that I like so many of the folks here, there’s definitely a cliquish feel to the whole thing with the hugely active IRC back channel of ongoing commentary (which really should be displayed where everyone including the presenters can read it), and the in-jokes (dongles). However welcoming, it can be a hard place to be a newbie.

    I want to stand up and shout “Folks. Listen. The world has moved on!! Deal with it.” I haven’t felt the need to set foot in a library, except for a meeting, in the last 10 years. I haven’t used a library OPAC or ILS, except for the purpose of researching the system itself in at least a year. I have logged into a university library to get access to subscription-only journal articles, but I actually found those articles in Google. My library’s only utility to me is as the proxy gatekeeper for ACM or Elsevier, and these days it only keeps me out.

    Many of the presentations and discussions are about alternatives: full-text vs. metadata; cataloger-created metadata vs. user-created metadata; Open Source vs. commercial; Google vs. the OPAC; data distribution standard A vs. standard B; marc vs. everything else. There’s a corollary notion that interoperability means everyone has to agree at some level. What really needs to happen is that everyone needs to get used to the idea that the ideal world in which everyone supports a few standards and data formats is the one we used to have, or imagine we had, and it’s gone. And it’s not coming back.

    What we have now is chaos. Many, many people are working very hard to maintain control over increasingly chaotic data and less-and-less predictable user behavior. They’re trying to hang on to users, even scholars, who are increasingly getting their information through Google or YouTube. They’re trying to figure out how to deal with steadily increasing digital collections, steadily decreasing user satisfaction, tone-deaf vendors, and sinking budgets.

    Let it go. Chaos is good. Keep your systems open and flexible. Watch. Listen. Integrate instead of compete with Google. Integrate data from the social networks. Share everything. Aggregate. Watch. Listen.

    Embrace.

  • Late to the Party

    Despite the fact that I’ve been writing for years in lots of different venues—even some group blogs, I’ve never had one that was “mine” or even “partially mine.” I think part of my reticence was because I wasn’t really sure I wanted to feel that pressure, that “omigod, I haven’t posted for a week (month, year)” burden and what that might do to the pleasure I feel when I’m writing well. I also didn’t want to follow the model where everything I think, say and do, everywhere I go, etc., goes on my blog. Maybe it’s age, but I still have a sense of having some kind of private life, even in the professional sphere.

    But for the last few years I’ve been writing columns for “Technicalities,” which has, to a certain extent pushed me in a blogging direction. Most of my columns were primarily opinion, in the “thought piece” mode, and I’m pretty comfortable with that. But with all apologies to the estimable Peggy Johnson (who’s been editing it for some time and who talked me into the column), it’s just not much of a soap box. I’ve been depositing all the columns in Cornell’s eCommons IR —yeah, I know, I’m not working there anymore but as a retiree I can still use my IR account, and it’s convenient. But rarely did I get any indication that the columns got read, either in print or online. I’m an extrovert, and I need an audience—a theoretical audience doesn’t do it for me.

    I’ve often talked about my retirement from Cornell this past March being a “practice” retirement. Lord knows that my retirement accounts have tanked like everyone else’s, but even if they hadn’t I wouldn’t be able to actually retire. I have too much still to do, too much that interests me greatly about what’s going on in the world of libraries I’ve been immersed in for something like 40 years, and hell, I’m enjoying this independence. So, the challenge is to continue to be independent, AND keep food on the table, etc., without raiding my bleeding retirement accounts. I suppose I should be more worried about that than I am, but aside from the bad luck of being so close to “real” retirement age when the economy slides into the dumpster, my house and car are paid off, and I’ve no debts, so I’m doing fine, thank you very much. Now, if the consulting and workshops keep coming along, I should be able to keep traveling and pay bills … fingers crossed.

    But there’s a plan, and this blog is part of it. It’s not just “my blog” though, which is a good thing, since that takes off me a bit of that pressure to keep the conversation going. You’ll note that this blog is part of a website for an outfit called Metadata Management Associates—that’s a partnership between me and Jon Phipps, my partner in crime since my NSDL days, and whoever we decide to pull in for various projects and conspiracies. As we get this show moving, make the website a bit more functional, etc., we’ll be adding names to the list of associates we like to work with. Jon and I also post on the Registry Blog and as you might have noticed if you read that, we tend to make some of our arguments in public (those who see us at conferences also might have noticed a certain resemblance to the “Bickersons”). It’s creative argumentation, actually—it keeps us moving forward as new stuff keeps popping up to challenge our favorite assumptions.

    So what can you expect to read about on this blog? We have some projects we can talk about, and some we can’t, so we’ll talk about some of our current “talkable” projects like the NSDL Registry (we’re working on some ideas to expand that development effort—watch this space), the RDA formal representations (see the DCMI/RDA Task Group page for more info on this), digital libraries in general, changes and new developments in the library environment, etc. Jon will talk more about the technology side than I will, but that’s the good news about this blog—it’ll be a little of everything.

    So, I’ve finally made it to the party—where’s the champagne?