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  November 2014

BIBFRAME November 2014

Subject:

Re: Blank nodes again

From:

Thomas Berger <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Wed, 19 Nov 2014 01:54:14 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (159 lines)

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

Am 18.11.2014 um 20:35 schrieb Joseph Kiegel:
> Can someone supply bibliographic examples?
> 
> How would situations like this be handled?

Are those real?

> bf:publication [ a bf:Provider ;
>            bf:providerDate "[1964]" ;
>            bf:providerName [ a bf:Organization ;
>                    bf:label "Bollingen Foundation" ] ;
>            bf:providerPlace [ a bf:Place ;
>                    bf:label "New York, N.Y. " ] ],

This is a container for a "publication event" pertaining to a particular
bf:publication. If we would assign an identifier it would not very much
increase usefulness because different resources would not have identical
publication events, only in the approximation that Bollingen Foundation
did it in New York about in 1964 - but for me this would constitute a
class of publication events, not an instance.

However the blank nodes for providerName (how can a *name* be an
Organization?) and providerPlace do have a very bad smell - even
in the bibliographic universe Bollingen Foundation and New York N.Y.
are recognized as entities



>        [ a bf:Provider ;
>            bf:copyrightDate "©1964" ] ;

this is an unrelated other event (as in actively registering the
copyright) also pertaining to the individual resource. No statement
is made about who the copyright claimant might have been. I would
interpret this not as a compicated way to code "1964" but as an
event where we cannot or do not wish to provide agents and places
connected with it. Thus again this registration event is completely
different from any other event labeled "copyright date 1964" for
different resources, and when crafting URIs for the blank nodes
they all *must* be different from each other.


> or
> 
> bf:lccn [ a bf:Identifier ;
>            bf:identifierScheme "lccn" ;
>            bf:identifierValue "63010708" ] ;

We had a lengthy discussion about that some months ago, subsumed under
"real world identifiers": The URI http://lccn.loc.gov/63010708
would be an (one) identifier for the bf:publication itself and RDF
does not give us the means to recognize it as an (the!) LCCN identifier.
Here we are asserting a much stronger statement: The bf:publication has
an LCCN identifier and its value is the string "63010708". (Some of us
happen to know that) this string is syntactically normalized and unique
to the publication and therefore can be used to identify resources.
Again we could craft a URI for the blank node, either a local one
faciliating comparisons within our dataset or - as also has been
proposed - even try to settle on a community-wide URI scheme which
would identify the identifiers and might open the door to specialized
web services acting on LCCN identifiers.



Another example (abridged from the german GND):

<http://d-nb.info/gnd/133655873>
    a gndo:DifferentiatedPerson ;
    gndo:gndIdentifier "133655873" ;
    gndo:preferredNameForThePerson "Marchionatti, Roberto" ;
    gndo:preferredNameEntityForThePerson [
        gndo:forename "Roberto" ;
        gndo:surname "Marchionatti"
    ] ;
    gndo:dateOfBirth "1950"^^<http://www.w3.org/2001/XMLSchema#gYear> ;
    gndo:placeOfBirth <http://d-nb.info/gnd/4061245-4> ;
    owl:sameAs <http://viaf.org/viaf/91654704> .



The gndo:preferredNameEntityForThePerson has a blank node as object,
acting as a container for first and last name of the person. I ~think~
that the FRANAR working group discussed at some point of time to make
each form of a name (as in see references) in authority records an
individual entity (and our "usual" authority entities then would refer
to a bunch of name entities spanning up the set of variant names and
reference forms) but since evolution did not take that path I'm quite
content with a blank node construction as stated above.

Unfortunately an only slightly more complicated example shows the
deficiencies of that approach:

<http://d-nb.info/gnd/131486888>
    a gndo:DifferentiatedPerson ;
    gndo:gndIdentifier "131486888" ;
    gndo:preferredNameForThePerson "Marx, Carl Friedrich" ;
    gndo:preferredNameEntityForThePerson [
        gndo:forename "Carl Friedrich" ;
        gndo:surname "Marx"
    ] ;
    gndo:variantNameForThePerson "Marx, Carolus Fridericus", "Marx, Karl
Friedrich" ;
    gndo:variantNameEntityForThePerson [
        gndo:forename "Carolus Fridericus" ;
        gndo:surname "Marx"
    ], [
        gndo:forename "Karl Friedrich" ;
        gndo:surname "Marx"
    ] ;
    owl:sameAs <http://viaf.org/viaf/35590119> .

There is a strong relation between "Marx, Carolus Fridericus" and
[ gndo:forename "Carolus Fridericus" ; gndo:surname "Marx" ] on one
hand and "Marx, Karl Friedrich" and [ gndo:forename "Karl Friedrich" ;
gndo:surname "Marx" ] on the other. Assigning identifiers to the blank
does not help us at all to make this relations explicit, for this we
would have to resort to completely different constructions like

    gndo:variantNameForThePerson [
        a gndxxx:nameInformationSet ;
        gndxxx:normalizedName "Marx, Carolus Fridericus" ;
        gndxxx:realLifePresentationOfName "Carolus Fridericus Marx" ;
        gndo:forename "Carolus Fridericus" ;
        gndo:surname "Marx"
    ], [
        a gndxxx:nameInformationSet ;
        gndxxx:normalizedName "Marx, Karl Friedrich" ;
        gndxxx:realLifePresentationOfName "Karl Friedrich Marx" ;
        gndo:forename "Karl Friedrich" ;
        gndo:surname "Marx"
    ] ;

(or even more complicated ones if we would start supplying sources for the
individual forms like LCNAF does or extend this model to corporate bodies
where acronyms and translated forms can be clustered alike). Here again I
would consider blank nodes as sufficient, at least as long we do not plan to
manipulate individual "variantNameForThePerson" subgraphs within the authority
record. But one might argue that even if /we/ don't intend to, some other
interested party very well might take advantage on individually adressable
variant forms within our authority data...

viele Gruesse
Thomas Berger


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

iJwEAQECAAYFAlRr6jUACgkQYhMlmJ6W47O14QQApQCvzXuf34jGsz6xNoJEP64V
wyHSBYLto7RcrVc5hfM3EkzW6R1Lhr6OCHrikVRWcDH9n1vD09wE7wPcTKsT/1s3
p7j6t/S/D1tdu/Ef3uv46WvyHz749Av+oNmn80+PK4mp/vLVzqm6Elg/aEmRT6Eg
fUNAdjmEb9dHFQvjqIY=
=qyvO
-----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

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