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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  July 2014

BIBFRAME July 2014

Subject:

Re: Proposal to handle "Providers" differently

From:

Kevin Ford <[log in to unmask]>

Reply-To:

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

Date:

Thu, 31 Jul 2014 18:33:11 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (132 lines)

Comments in-line.

But, before that, to offer a point of clarification. An Instance should
represent 1 Thing. So, if something is published in London (perhaps
with British English spelling) /and/ also in New York (with American
english spelling) these would be treated as two distinct Instances.
Instances should not represent an aggregated resource, but have 1-to-1
relationships to Works and other Instances.

On 07/31/2014 06:03 PM, [log in to unmask] wrote:
> The example
>
> <http://example.org/1> a bf:Instance,
> bf:publishedBy [ a bf:Organization ; bf:label "Hamlyn" ] ;
> bf:publishedAt [ a bf:Place ; bf:label "London" ] ;
> bf:publishedOn "1966" .
>
> is not preferable because it does not model the publication process right.
>
> bf:publishedBy / bf:publishedAt / bf:publishedOn have no relationship
> between each other and that will become fatal, for example, if there is
> more than one publication in the lifecycle of the instance (e.g. reprints).

Reprints would be new Instances.

>
> Publication is an event, I agree with Rob. The British Library is using
> in their model publication events, too.

I have no problem treating the concept of Publication (or Distribution
or Manufacture, etc) as Events. I am curious, however, if there is a
more utile way to approach this problem. Those "Events" are not really
re-usable. Now, "reusability" is not the only criteria, but an Instance
should nominally also only ever be a manifestation of a single
publication event.

I'm looking for cases when this would not be the case - and Karen has
presented us with something - but the interpretation is still a little
unclear.

>
> Such type of events can be recorded using event attribute lists, by a
> simple bf:publication, tying the relations together, like this:
>
> <http://example.org/1> a bf:Instance,
> bf:publication [
> event:place place:Chicago ;
> event:agent corp:UniversityOfChicago
> ], [
> event:place place:Paris ;
> event:agent corp:GautherVillars
> ], [
> event:date "1955"^xsd:date
> ] .
> place:Chicago rdfs:label "Chicago"@en .
> corp:UniversityOfChicago rdfs:label "University of Chicago Press"@en .
> place:Paris rdfs:label "Paris"@en .
> corp:GautherVillars "Gauther-Villars"@en .

This does not address the transcription requirement of RDA.

>
> The semantics of this RDF is: "The Bibframe instance
> http://example.org/1 was published at Chicago by University of Chicago
> and also at Paris by Gauther-Villars in the year of 1955".

If this is the proper interpretation, the approach presently is to
therefore create two Instances, one representing the Parisian
publication and the other representing the Chicago one. To illustrate that:

<http://example.org/2> a bf:Instance,
     bf:publishedBy [ a bf:Organization ; bf:label "U of Chicago" ] ;
     bf:publishedAt [ a bf:Place ; bf:label "Chicago" ] ;
     bf:publishedOn "1955" .

<http://example.org/3> a bf:Instance,
     bf:publishedBy [ a bf:Organization ; bf:label "Gauthier-Villars" ] ;
     bf:publishedAt [ a bf:Place ; bf:label "Paris" ] ;
     bf:publishedOn "1955" .

I would very readily entertain a relationship between those two
Instances, but I'm not sure I know what that relationship is.

Yours,
Kevin


>
> There is no longer the need to carry the information in "statement"
> sequences like in MARC , it can all be encoded into clear attribute
> sequences, one fact by another, for better evaluation by the machine
> interpreting the triples.
>
> And it is easy to extend the domain of bf:publication to people, places,
> dates, corporate bodies (publishers), or even to WS84 geographic
> coordinates in addition to place names, for example, to pin the location
> on OpenStreetMap or Google Maps, wherever you want.
>
> Jörg
>
>
>
>
> On Thu, Jul 31, 2014 at 11:18 PM, J. McRee Elrod <[log in to unmask]
> <mailto:[log in to unmask]>> wrote:
>
> Kevin posted:
>
> >publishedAt
> >producedAt
> >distributedAt
> >manufacturedAt
>
> Good. The more uniformity in terminology amongst our standards the
> better.
>
> In terms of including jurisdiction in "publishedAt" etc., that data is
> in a fixed field in both AACR2 and RDA records. I is just a matter of
> being uniform and less redundant in mapping that data to Bibframe, in
> order to be more informative to patrons.
>
> Few OPACs display fixed field data, and I suspect the same will apply
> to Bibframe codes.
>
>
> __ __ J. McRee (Mac) Elrod ([log in to unmask]
> <mailto:[log in to unmask]>)
> {__ | / Special Libraries Cataloguing HTTP://www.slc.bc.ca/
> ___} |__ \__________________________________________________________
>
>

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

December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
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
July 2011
June 2011

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager