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: bf:Title queries from use cases

From:

Thomas Berger <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Tue, 29 Jul 2014 16:05:12 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (66 lines)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Am 29.07.2014 00:21, schrieb Robert Sanderson:
>> Personally, I am in favor of investigating treating titles as string
>> literals. (And I mean all titles: constructed titles, regular
>> old-fashioned-this-is-the-title titles, abbreviated titles, spine titles,
>> key titles, added title page titles, etc.)
>
>
> _:Work bf:(constructed|abbreviated|spine|key|added|etc)Title "literal" .
>
> or:
>
> _:Work bf:title [ a bf:(Constructed|Abbreviated|Spine|Key|Added|Etc)Title ;
> bf:value "literal" ] .
>
> I prefer to multiply classes rather than predicates but the first way is
> much more straight forward if the only property of the Title resource is
> its value.

but can a ''work'' have a spine title?

For me, bf:Instances may have different kinds of titles as strings, although
I'm not sure we know enough about the universe to provide a fixed set of
string-valued properties covering all situations of "title" information
found on or in the resource.

Now the bf:work (think of the first french translation of The Adventures of
Tom Sawyer) has potentially several titles, one of them the spine title
of the instance above. However I would not consider this to be a spine title
of the bf:work. Rather any title we /associate/ with a bf:work should have
a justification - most of them are supplied because we have "instancial"
evidence of them (should we then provide the URI of the bf:instance as
"source"?), others are taken from elsewhere (encyclopedias, authority
files, scholarly literature, catalogues raisonnes - title authority data
probably would supply these too with source statements) and a third kind
are the titles supplied by cataloguers - adhoc translations, forms
usable for sorting or abbreviated titles for display. Perhaps these
should be kept together within the same bf:Title container.

I have to admit that I neither understand the intended meaning of
the titleSource property nor does the current list of properties
for bf:Title in < http://bibframe.org/vocab/Title.html > reflect
my expectation of "titles" as outlined above. Moreover most of these
attributes (part..., ...Type, ...) seem to address identification
issues of the bf:work or rather qualify the relation of this bf:work
to others. Of course these usually are evidenced by findings we
traditionally consider to be part of the "title" but probably won't
be able to develop their full potential when relocated into a
bf:Title container.

viele Gruesse
Thomas Berger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iJwEAQECAAYFAlPXqhgACgkQYhMlmJ6W47PwFAQAqfN5FxkE/x14Z5laBBeONQra
hNeFrJaip6/5izMJRylBpkm3omnjJTOEtX2a+Mhc0EyZ9J+wtivRa+pD89jtmMsE
23PCyXcEUSnGVPaGpFTCvLcl+MXQwhwz2Wmbz0KsZCQp4Ug452h1YaU4/yr4+XVz
HABoss/Q8kUvfRQHBJc=
=kT4e
-----END PGP SIGNATURE-----

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

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