LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  January 2018

CODE4LIB January 2018

Subject:

Re: BIBFRAME nesting question

From:

"Trail, Nate" <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Thu, 18 Jan 2018 17:38:12 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

LC has implemented a converter from marc using its SRU site:

http://lx2.loc.gov:210/LCDB?query=rec.id=5226&recordSchema=bibframe2a&maximumRecords=1

This is a full package that would include some duplications of data because of that conversion, and does not have a base uri to mint unique uris for each part, so it's all "blank nodes" until you do something with it.



We also have a comparison tool to show the descriptions side by side with their marc counterpart; you can  enter any bib id or lccn in the LC catalog to see what it converts as.



http://id.loc.gov/tools/bibframe/compare-id/full-ttl



You should certainly have uris for the Works, Instances, and Items, and the blank nodes we've created help you keep them unique within a description (http://bibframe.example.org/5226#Topic650-22 represents the 12th xml element and it's  based on the marc tag 650 in the old record).

However,

<http://bibframe.example.org/5226#Topic650-22> a bf:Topic,

        madsrdf:ComplexSubject ;

    rdfs:label "Wheels--Fiction." ; ….



is not unique necessarily in any database you are inserting this into, so there is some deduplication that has to happen on ingest to a triplestore, or lookup to an authority to replace .

When you use the “bibframe2a” recordSchema in our metaproxy/SRU (see above), there is some lookup to the id.loc.gov label services for names, subjects, and a few more nodes, to remove some of that duplication.

So Wheels—Fiction does not (yet) have it’s own uri and you’ll need to handle that, but Miniature books does, so  the blank node construct is replace by the subject uri at id:

<http://id.loc.gov/authorities/subjects/sh85085643> a bf:Topic,
        madsrdf:Topic ;
    rdfs:label "Miniature books." ; …



I think whether you are using rdfxml (which is hierarchical by nature) for the BIBFRAME descriptions lends itself to the nested approach you have in 1). But the non-nested approach works just as well, even in rdfxml; you will always have the linking properties hasInstance or instanceOf that help you traverse the graph. Just for sanity it might help to tag a whole description as a graph so  you can operate on the whole package later (as long as subsequent edits/additions are in the graph as well).





Nate



-----------------------------------------

Nate Trail

Network Development & MARC Standards Office

LS/ABA/NDMSO

LA308, Mail Stop 4402

Library of Congress

Washington DC 20540









-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Josh Welker
Sent: Thursday, January 18, 2018 12:08 PM
To: [log in to unmask]
Subject: Re: [CODE4LIB] BIBFRAME nesting question



I guess I am trying to figure out what the well-defined view looks like. I can't find examples that contain Work, Instance, and Item within the same RDF document at the same URI. In fact, the examples section on the LC BIBFRAME 2.0 website is blank, and the links for BIBFRAME 1.0 are all dead.

I certainly am not trying to reinvent anything, which is why I am posting here.



Joshua Welker

Information Technology Librarian

James C. Kirkpatrick Library

University of Central Missouri

Warrensburg, MO 64093

JCKL 2260

660.543.8022





On Thu, Jan 18, 2018 at 11:00 AM, McDonald, Stephen < [log in to unmask]<mailto:[log in to unmask]>> wrote:



> BibFrame already has an RDF view which is well-defined.  Are you

> trying to come up with your own RDF model for BibFrame data?

>

>                                         Steve McDonald

>                                         [log in to unmask]<mailto:[log in to unmask]>

>

>

> -----Original Message-----

> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of

> Josh Welker

> Sent: Thursday, January 18, 2018 11:28 AM

> To: [log in to unmask]<mailto:[log in to unmask]>

> Subject: [CODE4LIB] BIBFRAME nesting question

>

> Hi all,

>

> I have a question about how to model a resource expressed in BIBFRAME.

> We are digitizing some unique collections. Ideally, I'd like to have

> one URI like http://example.org/myuri that returns one RDF document

> containing data about the Work, the Instance, and the Item. There are

> two ways I could do

> this:

>

> 1. Use Work as the parent type and include the Instance as a child

> blank node using the Work.expressionOf property, and then include the

> Item as a second-level child node using the Instance.hasItem property. Example:

>

> bf:Work:

>   bf:title: [title node here]

>   bf:hasInstance:

>     bf:Instance:

>       bf:bookFormat: [bookFormat node here]

>       bf:hasItem:

>         bf:Item:

>           bf:shelfMarker: [shelfMarker node here]

>

>

> 2. Use some parent container class like rdf:Description and include

> the Work, Instance, and item as immediate children blank nodes of that

> container. Example:

>

> rdf:Description:

>   bf:Work:

>     bf:title: [title node here]

>   bf:Instance:

>     bf:bookFormat: [bookFormat node here]

>   bf:Item

>     bf:shelfMarker: [shelfMarker node here]

>

>

> 3. If neither 1 nor 2 are acceptable, I could have separate URI

> endpoints for the Work, Instance, and Item. This has the advantage of

> using less blank nodes:

>

> http://example.org/myuri_Work

> http://example.org/myuri_Instance

> http://example.org/myuri_Item

>

> I really prefer option 3 the least, but I am very uncertain between 1

> and 2. Thoughts on which is best practice? If 2, what should I use as

> the container class? And in any case, how much should I worry about

> the proliferation of blank nodes?

>

> Joshua Welker

> Information Technology Librarian

> James C. Kirkpatrick Library

> University of Central Missouri

> Warrensburg, MO 64093

> JCKL 2260

> 660.543.8022

>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager