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  August 2015

BIBFRAME August 2015

Subject:

Re: Proposal for treatment of series in BIBFRAME

From:

Thomas Berger <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Thu, 6 Aug 2015 10:32:37 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (110 lines)

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

Sorry for the late reply,

Am 03.08.2015 um 16:21 schrieb Karen Coyle:
> On 8/3/15 2:46 AM, Thomas Berger wrote:
>> We'll probably have to do both in even more situations than before
>> (links becoming more important while the text form still being
>> indispensable as proof of evidence for many applications),
>> since the two ways of expressing the fact are complimentary
>> and by no means full substitutes of each other. Thus it will be
>> crucial to never lose the connection between the two for a given
>> instance, i.e. having seemingly independent series "statements"
>> and series "links".
> 
> Why? Every "thing" in RDF can have display forms -- what is the series
> statement but a display form of the series information? We should assu
me
> that everything that has an identifier also has a display for humans.

subsequent posts by Stephen and Mac brought up the multilanguage
issues I originally didn't have in mind.

We already had seen that a "series statement" is of compound nature,
since it indicates the series (a different entity from the one
carrying the statement) and also the "numbering within series"
which best may be seen as some qualifying information pertaining
to the relation itself.

Within an RDF context there are technical obstacles coping with
that - i.e. turning "part of a text" into a "hyperlink" or
accompanying textual data into collation-friendly numbers or
sortable strings: Whenever there is a numbered subseries within
a numbered series and/or parallel numberings the series
statement is quite hermetic and spreading it out to something
machine processable is not straightforward at all. (Thus
perhaps one "series statement" (transcribed as stated on the
resource) may give rise to one or more complex "series link"
RDF statements (as in stated by the cataloguing process)
at leaet indicating the target resource (the "link") and that
part of the numbering which pertains to the series in question.

Series being "analytic" or that kind of "aggregates" which
evolve over time are a problem, too:

* A series as a work is the result of the activity of editors
  and publishers (our concepts of "work" are broad enough
  to extend well beyond artistic or intellectual production
  to all areas of organized human effords)

* The examples of multilanguage series (and - as by now almost
  always - the parallel existence of "online" and "print")
  indicate that FRBR expressions of series probably make sense
  as a concept

* Actual possession of items may be a faint reflection of the
  "series" concept on item level, this is probably completely
  irrelevant for bibliographic descriptions, however in
  museums and archives "collections" (of objects) are a central
  concept and "series" in the sense that a certain subset of
  the objects in a given (sub-)collection can be spread out
  (e.g. shelved) in a linear manner are a technique to achieve
  global order from local ordering

However for FRBR manifestaions or BF instances it is not at all
clear what a series might be so it's probably wise to avoid
instances of series and always link to series expressions (FRBR)
or works (BF). Now for a given item we have the transcribed
series statement, which like everything transcribed is a
property within the domain of BF instances / FRBR manifestations.
And we have the actual series link (qualified by the numbering
specific to the specific "series item") which probably "lifts up"
to at least a expression-expression link ("part-of").

So what one could need:

Some RDF container(?) element of BF instance domain, which
can carry the transcribed series statement *and* any number
of "qualified" BF-work to BF-work links which ~should be
understood~ as pertaining to the BF work implied by the
given instance. This sounds rather messy but IMHO exactly is
the value cataloguers usually add: Taking evidence from an
item and abstracting it to instances/manifestations and
even higher levels (BTW: providing a link to an entity for
an author of a given resource and recording the form of her/his
name used on the item also means closely glueing together
data with domain BF-work and BF-instance: Do we really
understand yet what is going on there?).

Alternatively one could have any number of "series links" with
domain BF-work and "source them" with transcribed data. This
could be "moved" then to the BF work graph (quotes because it
not already sitting there is rather a misconception of us) Here
I'm not sure how to express what is taken from what instance
and how often it really is imprinted there...

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

iJwEAQECAAYFAlXDG6QACgkQYhMlmJ6W47Mf+AQAh9bzuTQD7EPIvktfQlPXv0CX
vvSYH7CjZU4gJ/uJHo5+t4SE28FINCGZ4oCrNh7q8hNU1XyCMANWdVlGsYOqsbrO
kbaOInL0r7wIZhfOo2U+9uvo+49kXKaILJ2AYxqoPT6NgqHMbji0SmBqNFaJpswH
wl1G3OO9IOxJYtKVCl0=
=z+Gg
-----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

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