LISTSERV mailing list manager LISTSERV 16.0

Help for BIBFRAME Archives


BIBFRAME Archives

BIBFRAME Archives


[email protected]


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

BIBFRAME July 2014

Subject:

Re: BibFrame and Linked Data: Identifiers

From:

Thomas Berger <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Wed, 16 Jul 2014 22:45:45 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (100 lines)

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

Karen,

> You seem to have missed part of the discussion about identifiers. I point you to:
> 
> http://listserv.loc.gov/cgi-bin/wa?A2=ind1407&L=bibframe&T=0&P=8029
> 
> The thread begins here, but unfortunately the archive is not working correctly
> and some posts (esp. those from LC) do not display:
> 
> http://listserv.loc.gov/cgi-bin/wa?A2=ind1407&L=bibframe&T=0&X=39B4FE6748B566AFC0&Y=lists%40kcoyle.net&P=1926

Maybe I have been following that subthread to lazily, but I
think the discussion there mainly was about what URIs could
be used to identify an instance of a bf:Identifier (or comparable
constructs in any scheme) as a resource and the advice was
to treat them as anonymous nodes whenever possible, or at
least and completely counter-intuitive to provide them with
almost meaningless, as local as possible, URIs.

Now a bf:Identifier in the examples has one identifierValue but
I think there should be no restriction (e.g. it should be possible
to list an ISBN-10 and the corresponding ISBN-13 within the same
bf:Identifier construct). If now I not only happen to know the
ISBN-as-string of my resource but also the URN:ISBN URI then I
also need to express the fact that these actually mean the same
within the semantic context of "the ISBN system".

Listing strings and URIs (perhaps not as identifierValue but
as an hypothetic identifierURI) within the same container is
not contradictory on a formal level, I think. If we now assume
that the bf:Identifier is somehow bound to a resource (e.g.
when it is contained within an RDF:Description element) then
the semantics of a bf:identifierURI would be comparable to
that of the string-valued identifierValue: Whenever a resource
contains a bf:Identifier listing this URI, the two resources
shall be considered the same.

Considering bf:Identifiers listing multiple values reflects the
concept of "abstract identifierd" expressed in my previous post.
Maybe that is not the intended usage, because it would not
allow to qualify the individual string representations. If one
would like to state "this form ist the ISBN-10" and "that
form ist the ISBN-13" one would need two different bf:Identifier
constructs and the problem arises to provide statements expressing
their equivalence, which also in the situation of string
identifiers rises the problem to identify these with URIs
void of any ISBN meaning.


> And one of those from LC, 7/11/14, from Ray Denenberg, states:
> "·I believe it has been clearly demonstrated by this discussion that a URI
> should not be one of the “identifier schemes” for bf:Identifier."
> 
> And in the thread that begins on 7/10/14 with a post by Karen Smith-Yoshimura, I
> believe that we demonstrate that using as subject a URI from a third part does
> NOT imply that the statement was made by that party. This is one of the
> fundamental "truths" of the semantic web - that anyone can say anything about
> anything (AAA), and the URI does NOT indicate provenance of the statement (triple).

Thanks for the pointer, this was the thread I was trying to remember in
my post. Kevin Ford especially raised some warnings about "nasty things
that could happen" but at the end of the thread the optimism that suitable
mechanisms for denoting provenance of graphs will be available dominated
the result of the thread. IIRC I merely mentioned fears of some unspecific
"graph pollution". Beginning to think about it much of the decision of
using "foreign" URIs vs. crafting my own depends on the nature of the
resources and my own knowledge about them (how sure can I be that my
statements are really about the resource you had in mind?), my context
(I should re-use those URIs already employed by my institution or my
favorite community) or my intended audience (when my vocabulary
differs I at least will provide the URIs you already happen to know)
and probably more. And already these three points conflict with each
other. Therefore our traditional identifiers will even in semantic
web contexts serve their purpose of faciliating cross-community identifcation...

Thus maybe I should only warn that we cannot rely on the other extreme:
Even bf:instance s are something other communities would consider to be
classes and therefore there are no real obstacles that two agents indeed
use the same URI for identifying a resource, they still do this independent
of each other and they /could/ have decided otherwise. Thus for a given
resource there always will be many URIs in use and the set of all statements
formulated with bibframe vocabulary will not be a substitute for a FRBR
manifestation level kind of authority file.

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

iJwEAQECAAYFAlPG5HkACgkQYhMlmJ6W47On8gP9H3A97bQe/qMZrKsUFQFCBsSF
G8IDtrAkscataGCy5a63PzZtB4C7fqhlnQ8ywreMODCcAJFRG2ZI9t0zd705VLXd
GpiE0n1Os4kel/0nEtnh/SV9cpMZ4acbNHh88ATPtYXwNEdDKhCmE1uG+zRjX5og
zMtqe5ToBmeuLaZaiZc=
=llgt
-----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

February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
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
https://listserv.loc.gov/cgi-bin/wa?A2=ind1407&L=BIBFRAME&D=0&P=81287
listserv.loc.gov
CC-MAIN-2024-10
57065
application/http; msgtype=response
sha1:M3P4BMXX3E2SLCDSK3GUCGL7E6CRWHGH
<urn:uuid:9ffe8350-3274-4a10-96f7-a8172d362a97>
2024-02-23T00:14:03Z
104.16.55.16
text/html
sha1:HUVI4IKY27SXQBLTSDGTXDKTCHFQXQCE
<urn:uuid:adac59a1-a1c5-45ce-aab5-4cb6fe0e6813>
https://listserv.loc.gov/cgi-bin/wa?A2=ind1407&L=BIBFRAME&D=0&P=81287
response
<urn:uuid:dfb46eb5-cc2d-49b6-ad74-4d38c4da7b5d>
isPartOf: CC-MAIN-2024-10
publisher: Common Crawl
description: Wide crawl of the web for February/March 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-196
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/