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  September 2014

BIBFRAME September 2014

Subject:

Re: Specific Questions

From:

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

Reply-To:

Bibliographic Framework Transition Initiative Forum <[log in to unmask]>

Date:

Tue, 16 Sep 2014 17:11:12 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Rob, thanks for this detailed look.  I can’t answer all of them quickly, but I know a few off the top of my head:

• dissertationInstitution’s range is probably a mistake.

• musicVersion  and other properties without a domain: we are usually uncertain  or agnostic as to whether it belongs on Work or Instance, as you guessed, and so we left it unconstrained. We don’t really mean that it could be on any Class, like Person, but that’s a side effect of leaving the domain blank. 

• Ideally, treatySignator would be a bf:Person or really a government body, but the data from MARC is going to be stringy. This is yet another example where if we had our druthers, we’d have a string version of a property for legacy data, and a uri version for born bf: data.

• bf:agent : often, there is a name listed in the 7xx fields, but no relationship stated, nor type of material, so you can’t guess at the role the person plays with respect to that resource

• * bf:edition : MARC 250$a  bf:editionResponsibility 250$b bf:otherEdition MARC 775. 

	o The first two describe this edition, the otherEdition points to a different resource:

		o BF edition and responsibility: : http://bibframe.org/tools/compare/bibid/7810461
		o bfotherEdition: http://bibframe.org/tools/compare/bibid/11346685

I’ll try to answer the others separately.
Thanks, Nate

-----------------------------------------
Nate Trail
LS/TECH/NDMSO
LA308, Mail Stop 4402
Library of Congress
Washington DC 20540
-----------------------------------------

From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of Robert Sanderson
Sent: Tuesday, September 16, 2014 4:25 PM
To: [log in to unmask]
Subject: [BIBFRAME] Specific Questions


Some specific questions:

--- Range/Domain ---

* bf:dissertationInstitution has a range of bf:Agent, not bf:Institution.  Are there really people that give out dissertations (and how much do they cost? :D)

* bf:edition (and bf:editionResponsibility, which looks like a Note) has a domain of Instance, as expected from the Provider discussion that different editions (and hence dates) must be different Instances. However, bf:otherEdition has domain and range of bf:Work.  This seems like a mistake?

* Relatedly, bf:musicVersion has a range of Literal and no domain. This seems like it should be Work or Instance?
* And similarly, bf:treatySignator has a range of Literal and no domain.  Seems like it should be a range of bf:Person?

--- No Semantics ---

* bf:agent doesn't seem to say anything beyond "Here is an agent somehow related to this resource", and has no domain.  Also, afaict, it has no sub-properties.   Can anyone shed some light on what the meaning of the relationship is, and thus when a producer would create it and what a consumer would do with it?
* bf:event is the same as bf:agent.
* bf:place used to exist, but no longer ... should agent and event also be deleted?  (temporal and topic never existed)

* bf:relatedInstance seems to only have the semantics of relatedTo, but with specific range and domain.  Why would a consumer/producer use this instead of relatedTo?
* Ditto bf:relatedWork

* bf:legalDate seems to have the description of Date of a work that's legal in nature, or the date a treaty was signed, or the date a law went into effect. This seems so indistinct to the point of being worthless?

--- Inconsistency ---

* bf:originPlace, bf:originDate ... but bf:Provider, and the previous discussion about providerName and providerDate.   So when its an Instance, the event gets its own resource, but when its a Work, it doesn't?

Thanks!

Rob

-- 
Rob Sanderson
Technology Collaboration Facilitator
Digital Library Systems and Services
Stanford, CA 94305

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