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  May 2016

BIBFRAME May 2016

Subject:

Re: Series in BIBFRAME 2.0

From:

Thomas Berger <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Tue, 31 May 2016 22:12:42 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (69 lines)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Am 31.05.2016 um 21:02 schrieb Adrian Pohl:

> <Instance> lv:inSeries [
>         a lv:SeriesRelation ;
>         lv:series <http://ld.zdb-services.de/resource/1110794-7> ;
>         lv:numbering "v. 30, pt. 3 = Bd. 30, Teil 3" ] ;
>     lv:inSeries [
>         a lv:SeriesRelation ;
>         lv:series <http://ld.zdb-services.de/resource/2082308-3> ;
>         lv:numbering "v. 2357" ] .
> 
> Note that the bnode entity rather is a _relation_
> (lv:SeriesRelation) of an instance to a series and is not itself a
> series.

There seems to be a strong tendency of avoiding blank nodes for
almost whatever price, probably from a data management perspective:
[If I want to modify that statement (or inject it into a different
database) in isolation it has to be identified. But elevating the
complex statement to an identifie[re]d entity raises the question
of suitable constraints and class membership]

RDF (independent of any serialization syntax) is not very expressive
when it comes to relations, and not everything is a case of RDFS
subproperties or meta-data injected into the object of a relation
(like who crafted this identifier or who is in charge of the target
record).
I'm increasingly under the impression that /most/ of our relations
tend to be qualified, e.g. we not only want to state this is
"partOf" that but furthermore provide an answer to the question
"/what/ part of that?". (Similarily when we state an "author"-
relation to an entity we could like to record how this normalized
relation is expressed by the resource itself - not only in the
rather coarse way of the complete statement of responsibility. Or
look at MARC where almost every non-trivial fact (including
relations) might be qualified by $2 and/or $5's: For whom and
under what constraints was this relation recorded.

We have encountered many situations on this list where some
theoretically "direct" relation between entities had to be
kind of encapsulated into some subgraph and if I recall correctly
there always has been some queasyness as to where this
additional level of indirection should belong to (like an
"aspect" of the source graph or some extension of the
target graph). As I understand Adrian's point of view
it might look like a subgraph of the source graph (anything RDF
always looks like that...) but this subgraph does not represent
aspects or parts of neither source nor target but it rather
*is* (or records) the relation between the two and therefore
really has a very different nature from the "usual" entities.

So perhaps we should simply abandon the conception that any
relation between S and O must be expressible by a /simple/
statement <S> <rel> <O>.

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

iF4EAREIAAYFAldN8DkACgkQnkh9maPoyhzpwwD/VNJ8qfkfn1d4JTeP1tW3rIWP
V3X/X3PMldPib7ss8TUA/AxFZKRtqNZbGG9mkquAqjYb34M7tKKaCMDPlF/bx92c
=alhJ
-----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

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