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:

Tue, 25 Aug 2015 10:28:55 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (175 lines)

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

Am 24.08.2015 um 22:21 schrieb Karen Coyle:

> This seems to me to be an implementation issue, and it would probably 
be
> preferable if BF allowed for more than one implementation choice. Ther
e
> is no reason why some implementations should not include these triples
> in their graphs:
> 
> bf:contributor [
>   a bf:Contributor ;
>   bf:role<http://id.loc.gov/vocabulary/relators/ill>  ;
>   bf:agent<http://id.loc.gov/authorities/names/1234>  ].

This superficially looks like a rather direct transformation of
MARC 700 with $4 and $0 (and nothing more is needed in a
"linked" situation). So what about

bf:contributor [
  a bf:Contributor ;
  bf:role<http://id.loc.gov/vocabulary/relators/ill> ;
  bf:role<http://id.loc.gov/vocabulary/relators/aut> ;
  bf:agent<http://id.loc.gov/authorities/names/1234> ;
  bf:agent<http://d-nb.info/gnd/9876> ].

(MARC semantics: two different roles for one bibliographic
identity accounted for in different authority files)


> <http://id.loc.gov/vocabulary/relators/ill>
>   skos:prefLabel "Illustrator@en" ;
>   a<http://www.loc.gov/mads/rdf/v1#Topic/>  .
> 
> <http://id.loc.gov/authorities/names/1234>
>   a<http://www.loc.gov/mads/rdf/v1#Authority/>  ;
>   skos:prefLabel "John Smith" .

and

<http://d-nb.info/gnd/9876>
  a<http://www.loc.gov/mads/rdf/v1#Authority/>  ;
  skos:prefLabel "Smith, John" .

Now an application generally may prefer to utilize information from
LC Authorities.

Membership information is part of LC Authority records

<http://id.loc.gov/authorities/names/1234>
  <http://www.loc.gov/mads/rdf/v1#isMemberOfMADSCollection>
<http://id.loc.gov/authorities/names/collection_LCNAF> .


and could be incorporated here, or would have to be provided
"externally" in the GND case:

<http://d-nb.info/gnd/9876>
  a<http://www.loc.gov/mads/rdf/v1#Authority/> ;
  bf:memberOfAuthoritativeCollection <http://d-nb.info/gnd> ;
  skos:prefLabel "Smith, John" .


So the trick built into LC Authorities seems to be not to
state that authority records belong to some authority file,
but to organize the resources described by the authority
records into collections.

VIAF on the other hand does take a different approach
(note presence or absence of the trailing slash in the URI):

<http://viaf.org/viaf/3456/> ;
 a <http://xmlns.com/foaf/0.1/Document> ;
 a <http://www.w3.org/2006/gen/ont#InformationResource> ;
 void:inDataset <http://viaf.org/viaf/data> ;
 foaf:primaryTopic <http://viaf.org/viaf/64049336"> .

and

<http://viaf.org/viaf/3456>
 a <http://schema.org/Person> ;
 dcterms:identifier "3456" ;
 schema:name "John Smith" ;
 ...
 schema:sameAs <http://id.loc.gov/authorities/names/1234> ;
 ... .

(and it also gives an alternative representation of the LC
Authority record:)

<http://viaf.org/viaf/sourceID/LC%7Cn++1234#skos:Concept>
  a <http://www.w3.org/2004/02/skos/core#Concept"> ;
  skos:inScheme <http://viaf.org/authorityScheme/LC>;
  skos:prefLabel "Smith, John, 1874-1951";
  foaf:focus <http://viaf.org/viaf/3456> .


So authority records can (and sometimes do) state
a) the authority control environment they belong to,
and they usually contain the strings needed
b) for use as label (heading, access point, ...)
c) as well as the identifier(s) assigned in that environment.

Bibframe could define three properties (or recommend the use
of specific general properties like rdfs:label) just to
normalize the situation.

Defining labels and identifiers as properties of the (non information)
resource makes sense in the context of a given authority control
system, but has to be dealt with some care in applications where
"authority control" from different systems exists in parallel:
The entities are to be identified, however their meta information
has to be kept in distinct compartments.

The Bibframe identifier approach intends to tackle this: I would
say that assigning resources to controlled collections (LC NAF),
assigning resource descriptions to a dataset (VIAF) or
assigning identifiers to identifier schemes (Bibframe proposal)
are technically different but semantically quite equivalent and
therefore legitimate approaches to inject "context" into our
descriptions. And I can perceive string identifiers and labels
assigned within a given controlled environment as "identifying
data" (as opposed to "universal" properties of the resource)

The question is, can the approaches be mixed? I.e. some
application can extract anything it needs from

bf:contributor [
...
 bf:agent<http://id.loc.gov/authorities/names/1234> ;
...].

but another one would need things spelled out explicitly by
added statements like:

<http://id.loc.gov/authorities/names/1234>
  a bf:Identification ;
  bf:xxxScheme bf:lcnafScheme ;
  bf:identifier "1234" ;
  bf:label "John Smith" .

(and perhaps adding
  rdfs:definedBy <http://id.loc.gov/authorities/names/1234>
  or
  schema:sameAs <http://id.loc.gov/authorities/names/1234>
like VIAF does to indicate that there is a information resource
determining the semantics / fixing the identity of that concept)

This would turn the concept <http://id.loc.gov/authorities/names/1234>
(a bf:Agent) into a bf:Identification at the same time: Would that
be something "usual" like trying to keep up a distinction between
informational resources and concept URIs in situations where the
"targets" don't cooperate (or operate in ways not known to the casual
user: "using authority data" in a Bibframe environment should be
possible without prior exams in the fine print of Semantic Web
standards...)?
Or would this rather mean (different equivalence relations depending
on which class is applied) a straight path to modeler's hell?

viele Gruesse
Thomas Berger

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

iJwEAQECAAYFAlXcJ0YACgkQYhMlmJ6W47PbeQQAs6oYyhcz2fdl0Oyh10DQTNQy
uZlN9y1DNGIUmK8XgcjlLAPV3MQse9ZplZvRB7CsnwtiOnNPrQYxeqNOhCuS4Igi
V1Ohkwm2k3aL4bbxg2fjpTtaEhnglNrv720b6SOVSVLqi8EMciKXtNSN5kQg0KHD
AnJ6z8cBxz2AlHAdhLo=
=+v5l
-----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