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: BIBFRAME Identifier, Role, and Authority Proposals

From:

Thomas Berger <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Wed, 26 Aug 2015 18:48:40 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (91 lines)

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

Am 26.08.2015 um 17:44 schrieb Steven Folsom:

> throughout this thread (and in the VIAF data) authority URIs being use
d
> as the objects of properties where instead person, places, etc. URIs
> should be. For example, (as previously mentioned) VIAF has separate UR
Is
> for the person and the authority, but then they go on to make a sameAs
> assertion between the VIAF *person* and an id.loc.gov *authority*. I
> hope this is just a mistake, and that they would be open to making the
> sameAs assertion between the VIAF foaf:Document and the id.loc.gov
> authority.

But VIAF uses schema:sameAs
"URL of a reference Web page that unambiguously indicates the item's
identity."

which is quite different from owl:sameAs.


> For example: https://viaf.org/viaf/36997809/rdf.xml has a URI for
> the document ("http://viaf.org/viaf/36997809/“) and another for Carl S
agan
> himself ("http://viaf.org/viaf/36997809”, without the trailing slash).

In the example I see schema:sameAs properties only attached to the
concept URI. E.g. the following document should be (tried to) retrieved
for identifying information:

http://id.loc.gov/authorities/names/n79064998

(and we have to retrieve that document in search for an LC identifier,
since the RDF representation of the VIAF cluster does not provide one).

I don't see any place where VIAF declares identity of different concept
URIs (as opposed to the GND behavior where it is stated

<http://d-nb.info/gnd/115873937>
          owl:sameAs <http://viaf.org/viaf/36997809>)


> The Person URI has sameAs assertions with both authorities and entitie
s
> modeled as persons.

can you elaborate on this? I'm not sure if VIAF contributors already
have a stringent (and stable) distinction between information resources
("authorities"?) and concept URIs (RWOs?). And use of schema:sameAs
somehow enforces the interpretation as information resouce URI even if
they smell of concept URIs as in the case of
http://data.bnf.fr/ark:/12148/cb12375841d#foaf:Person

So for an entity VIAF reports a number of *documents* which each
claym to (sufficiently) identify the entity in question. I'd consider
that a very careful approach, especially VIAF is in no position
to boldly declare identity of the concepts contributed by different
sources into one cluster.


Then, VIAF kind of declares its resolving functionality:

<http://viaf.org/viaf/sourceID/LC%7Cn++79064998#skos:Concept> [
 a <http://www.w3.org/2004/02/skos/core#Concept"> ;
 skos:inScheme <http://viaf.org/authorityScheme/LC> ;
 skos:prefLabel "Sagan, Carl, 1934-1996" ;
 foaf:focus <http://viaf.org/viaf/36997809"> ].

I interpret that as a "hook": Feel free to identify the LCAuth
concept URI of your choice with
http://viaf.org/viaf/sourceID/LC%7Cn++79064998#skos:Concept
and the graph above then serves the connection between "your" concept
and the RWO identified by the VIAF URI.



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

iJwEAQECAAYFAlXd7ecACgkQYhMlmJ6W47PmsgP9GCrSH5wugyK5RiJGNnd/nzby
8CEOKUARK48FFibgJLqtZPTu8jpJnq2FyV6BMcdCRwwEkbXsYE6dNUqpVfWe9ly4
WtdyvO89OITJLvJ+bgXYjdUan7W6j4rKhTg2nPw/aIxf+ZqToAIx++L8u3xZNfpz
/fraKaxUX6aNBJzicQM=
=oBUD
-----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

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