LISTSERV mailing list manager LISTSERV 16.0

Help for BIBFRAME Archives


BIBFRAME Archives

BIBFRAME Archives


BIBFRAME@LISTSERV.LOC.GOV


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

BIBFRAME Home

BIBFRAME Home

BIBFRAME  May 2013

BIBFRAME May 2013

Subject:

BIBFRAME authorities: relationToWork

From:

Karen Coyle <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Tue, 14 May 2013 17:35:43 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (79 lines)

There is an example under "Bad Data":

<!--  BIBFRAME Work -->
<*Play* id = 
"*http://bibframe/work/Quatuor-pour-trois-violons-et-violoncelle*">
       <title>Quatuor pour trois violons et violoncelle</title>
       <creator resource = "http://bibframe/auth/person/franklin" />
</*Play*>
<!--  BIBFRAME Authority -->
<*Person* id="http://bibframe/auth/person/franklin">
       <label>Franklin, Benjamin, 1706-1790</label>
       <relationToWork>supposed compeser.</relationToWork>
       <hasIDLink 
resource="http://id.loc.gov/authorities/names/n79043402" />
       <hasVIAFLink resource="http://viaf.org/viaf/56609913" />
       <hasDNBLink resource="http://d-nb.info/gnd/118534912" />
</*Person*>

There is a problem with "<relationToWork>supposed 
compeser.</relationToWork>" that goes beyond the bad data.

I believe that someone else mentioned this, but if "relationToWork" is a 
property of the Person, then that Person ID cannot be used for any other 
relationship (e.g. "author") because as expressed here relationToWork is 
being said about the Person, period. There needs instead to be a triple 
that has:

WorkURI - relationToWork - PersonURI

This then states the relationship of the Person to that particular work, 
and doesn't change the underlying definition of the Person. 
Unfortunately, this isn't possible when the value of "relationToWork" is 
not a URI, because properties (the middle parts of the triples) have to 
be URIs. For example, if this information were coded using the MARC 
relator standard "<http://id.loc.gov/vocabulary/relators/cmp>" then you 
could say:

http://bibframe.org/work/Quatuor-pour-trois-violons-et-violoncelle - 
http://id.loc.gov/vocabulary/relators/cmp - 
http://bibframe.org/auth/person/franklin

Which means that this person is the composer of the Work. (I don't know 
if there's a code for "supposed composer" but I'm pretending that "cmp" 
will do.)

To resolve this, and this is a case that we will encounter, there will 
have to be some contortions, possibly a blank node:

WorkURI - Creator -_blankA

_blankA - typeOf - http://bibframe.org/vocab/Person
_blankA - authID - http://bibframe.org/auth/person/franklin
_blankA - http://bibframe.org/vocab/label -  "Franklin, Benjamin, 1706-1790"
_blankA - http://bibframe.org/vocab/resourceRole - "supposed compeser"

The difference between the blank node and the way I interpret the 
"lightweight BIBFRAME authority" is that the blank node is a one-off -- 
it's only  usable in this one instance. There is no creation of an 
identity that could be re-used in other circumstances (although, as I've 
done above, it can link to an identity, such as an authority record). 
Blank nodes are considered last resorts by some linked data enthusiasts 
because they aren't re-usable. But there are times when you really have 
little choice.

This brings up a specific question about the BIBFRAME authority: Is it 
intended to be re-usable? Or does it have the "one-off" nature of a 
blank node?

kc
p.s. There are undoubtedly other solutions to this problem, and I hope 
they'll get posted here.

-- 
Karen Coyle
[log in to unmask] http://kcoyle.net
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet

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

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
July 2011
June 2011

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager