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

BIBFRAME August 2015

Subject:

Re: Proposal for treatment of series in BIBFRAME

From:

Karen Coyle <[log in to unmask]>

Reply-To:

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

Date:

Sat, 8 Aug 2015 10:18:32 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (346 lines)

On 8/7/15 7:00 PM, Steven Folsom wrote:
>
> On 8/7/15, 3:09 PM, "Bibliographic Framework Transition Initiative Forum on behalf of Karen Coyle" <[log in to unmask] on behalf of [log in to unmask]> wrote:
>
>> On 8/6/15 8:59 AM, Steven Folsom wrote:
>>> +1 to everyone who has proposed separating Series from Series Statements. As Karen Pointed out, Series can have any number of rdfs:Labels to account for many of our use cases for collection labels for individual Series. Series statements seem to be more about provisioning for transcription and labels describing the sequence of membership to a Series.
>>>
>>> With that, I think there are parallels between what has been said about “series statements” and what I proposed a little while back for handling transcription of titles and title parts. I may be wrong, but... couldn’t an instance have a SeriesTitle (a not yet defined bf:Title subclass), that allows for recording both the transcribed series title/statement in an rdfs:label and title parts through MainTitles, Subtitles, PartNumbers? Using logic from title proposal I submitted on July 23rd, and the creation of a bf:SeriesTitle subclass of bf:Title, one seemingly could handle both Titles for the Series entity and transcribed Series Titles on the bf:Instance.
>>>
>>> For example (sneaking a bunch of ideas from the July 23rd proposal):
>>>
>>> <bf:Work1> a <bf:Series> ;
>>> rdfs:label “Title in English”@en ;
>>> rdfs:label “Title in French”@fr ;
>>>
>>> bf:hasPreferredTitle <bf:Title1>.
>>>
>>> <bf:Work2> a <bf:Monograph> ;
>>> bf:series <bf:Work1> ;
>>> bf:title <bf:Title2> ;
>>> bf:instance <bf:Instance1> .
>> "series" is a bibliographic relationship between two bibliographic
>> resources. So work2 has what is probably a "part of" relationship with
>> work1. work2 also has a title, but that (to me) is not a
>> source-to-source relationship but the title is a descriptive element on
>> work2. I think these are conceptually very different. The title node
>> will be unique to that instance; the series node may have relationships
>> with many instances.
>> Because it has a single context (one instance), the
>> title node can be a blank node.
> There are reasons (other than strictly for reuse) to have Titles be modeled as RDF resources, for instance... if we want to say two titles are one to one translations of each other; they need to be RDF resources with a relationship between them.

That's exactly what I am saying. That related things that are specific
to that instance, not global or universal, get blank nodes. Related
things that have an existence outside of that instance, such a series,
need to have URIs. In programming, this would be the difference between
local variables, that only have an identity that is true within that
specific context, and global variables, that have an identity that can
be used anywhere. In RDF, *everything* is a graph, even a single triple,
so "graph-ness" isn't what is significant here, it's the scope of the
identifier that makes the difference.

>
>> Because a series node is intended to be
>> related to more than one instance, it cannot be a blank node. For this
>> reason, having an emphasis on the series title doesn't facilitate
>> linking. Linking needs to be to a universally identified and reusable graph.
>>
>>> <bf:Instance1> a <bf:Print> ;
>>> bf:title <bf:Title3> ;
>>> bf:title <bf:SeriesTitle1>.
>>>
>>> <bf:SeriesTitle1> rdfs:label “Series Main Title: Clever Subtitle, Volume 1” ;
>>> bf:hasPart <madsrdf:MainTitleElement1> ;
>>> bf:hasPart <madsrdf:SubTitleElement1> ;
>>> bf:hasPart <madsrdf:PartNameElement1> ;
>>> bf:descriptionSource <bf:Instance1>.
>> Assuming that this is a transcribed title, where/when is the title of
>> the series resource used? In other words, why have the series title in
>> two places?
>> (If the transcribed title is different, I would consider
>> that an alternate title with the meaning: "title as it appears on the
>> piece.")
> But which piece? If it’s just a blank node alternate title off the bf:Series, without being an RDF resource we can't link it to a specific bf:Instance to denote transcription.

I'm assuming that transcribed information would be attributes of the
instance, since they are about the instance. The question then becomes
whether it is necessary to link the transcribed series title to the
series entity. As I understand it, the transcribed series title would
help someone identify the instance ("it's the one that spelled "journal"
as "juornal"). The instance would also have a link to the series URI. We
should think carefully about use cases - machine actions that could not
be performed if the two are not linked.

>
>> And how would the individual volumes link to the series resource?
>
> Just like my example described (through the bf:Monograph).
>
>
>
> As tempting as it may be to reuse a title on both a bf:Series and a related bf:Instance, it’s probably not a good idea. It looks ok in this example:
>
> <ex:11111> a <bf:Series> ;
> bf:title <ex:Title1> .
>
> <ex:22222> a <bf:Monograph> ;
> bf:instance <ex:33333> ;
> bf:series <ex:1111111> .
>
> <ex:33333> a <bf:Print> ;
> bf:title <ex:Title1> .
>
> <ex:Title1> a <bf:SeriesTitle> ;
> rdfs:label “Lord of the Rings”
> bf:descriptionSource <ex:33333>.
>
>
> But…
>
> You wouldn’t want an Instance level bf:SeriesTitle like “The 13th Installment of the Mysteries of Data Modeling (with RDF)” reused on the bf:Series “The Mysteries of Data Modeling”. Also, if you had a bf:SeriesTitle that was linked to both a Series and an Instance you couldn’t subtype the Instance title, e.g you couldn’t say <ex:Title1> was also a <bf:RunningTitle> without saying <ex:Title1> is always a bf:RunningTitle. That may not be true for other Instances of the Series.
>
> <ex:11111> a <bf:Series>
> bf:title <ex:Title1> .
>
> <ex:22222> a <bf:Monograph> ;
> bf:instance <ex:33333> ;
> bf:title <ex:Title2> ;
> bf:series <ex:1111111> .
>
> <ex:33333> a <bf:Print> ;
> bf:title <ex:Title1> ;
> bf:title <ex:Title2> ;
> bf:title <ex:Title3> .
>
> <ex:Title1> a <bf:SeriesTitle> ;
> rdfs:label “The Mysteries of Data Modeling” .
>
> <ex:Title2> a <bf:SpineTitle> ;
> rdfs:label “The Mysteries of Modeling with RDF” ;
>
> bf:descriptionSource <ex:33333> .
>
> <ex:Title3> a <bf:SeriesTitle> ;
> a <bf:CoverTitle> ;
> rdfs:label “The 13th Installment of the Mysteries of Data Modeling (with RDF)” ;
> bf:descriptionSource <ex:33333> .
>
You'll need to distinguish preferred labels and alternate labels and
transcribed labels with more than a class. A series should have a
preferred label (authoritative form of the name) and, if necessary,
alternate labels. (The SKOS use of labels may not be sufficient for
cataloging purposes, and alternate labels may need to have
subproperties.) I don't see a reason to have

<ex:Title1> a <bf:SeriesTitle>

A preferred display form in the series graph provides that. I think this
form comes out of thinking that the series information will be recorded
in the instance graph not the series graph. This is a habit that comes
from "unit cataloging" before linking was possible. If true linking had
been implemented between authority records and bibliographic records,
then I suspect that we would have discontinued the re-entry of strings
in the catalog records, since those would have come from links. So try
to see the catalog record as having links in the place of headings. That
should work because headings were intended to have a role as identifiers
-- they just didn't work well for that because they also had a role for
display and displays sometimes have to change (whereas identifiers
cannot without becoming a different thing).

kc

>
>
>
>
>
>> Another possibility is to have an identifier for the individual series
>> "part" -- often designated as "volume." A series would have parts:
>>
>> <ex:seriesActaFoo> a <bf:Series> ;
>> <ex:hasPart> <ex:33333> ;
>> <ex:hasPart> <ex:44444> .
>>
>> <ex:33333> a <ex:serialPart> ;
>> <ex:caption> "Volume" ;
>> <ex:enumeration> "A3" .
>>
>> <bf:instance7> a <bf:Instance> ;
>> <ex:isSeriesPart> <ex:33333> .
> Why not just:
>
> <ex:seriesActaFoo> a <bf:Series> ;
> <ex:hasPart> <ex:33333> ;
> <ex:hasPart> <ex:44444> .
>
>
> <ex:33333> a <bf:Instance> ;
> <ex:serialPartType> "Volume" ;
> <ex:serialEnumeration> "A3” .
>
> (The Instance IS the part.)
>
>
>
>
>> It looks less intuitive, but it makes all of the connections. This
>> pattern could be expanded as the serial pattern, with each issue,
>> volume, part (and whatever) being identified and linked to each other.
>> It seems awkward, but in essence that's what the MARC holdings format
>> does with the serial pattern.
>>
>> Note that "volume 3" of serialA will have a unique identifier that only
>> identifies volume 3 of serialA, not all "volume 3"s of all serials. The
>> URI will identifier the resource, not the caption.
>>
>> kc
>>
>>> <madsrdf:MainTitleElement1> rdfs:label “Series Main Title”
>>> bf:precedes <madsrdf:SubTitleElement1>.
>>>
>>>
>>> <madsrdf:SubTitleElement1> rdfs:label “Clever Subtitle” ;
>>>
>>> bf:precedes <madsrdf:PartNameElement1> .
>>>
>>> <madsrdf:PartNameElement1> rdfs:label “Volume 1” .
>>>
>>>
>>>
>>>
>>> Thank you for your consideration,
>>> Steven
>>>
>>> ————
>>> Steven Folsom
>>> Metadata Strategist and Standards Advocate
>>> Cornell University Library
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On 8/6/15, 4:32 AM, "Bibliographic Framework Transition Initiative Forum on behalf of Thomas Berger" <[log in to unmask] on behalf of [log in to unmask]> wrote:
>>>
>>>> -----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-----
>> --
>> Karen Coyle
>> [log in to unmask] http://kcoyle.net
>> m: +1-510-435-8234
>> skype: kcoylenet/+1-510-984-3600

--
Karen Coyle
[log in to unmask] http://kcoyle.net
m: +1-510-435-8234
skype: kcoylenet/+1-510-984-3600

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

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