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  February 2019

BIBFRAME February 2019

Subject:

Re: When a bf:Identifier is a URI

From:

Graham Bell <[log in to unmask]>

Reply-To:

Bibliographic Framework Transition Initiative Forum <[log in to unmask]>

Date:

Tue, 19 Feb 2019 17:57:01 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Paul - on the whole I would not advise jumping down this rabbit hole, but you might want to think about these librarians who think DOI is not dereferencable.

Graham Bell
EDItEUR

Sent from my iPhone

> On 19 Feb 2019, at 17:06, Martynas Jusevičius <[log in to unmask]> wrote:
> 
> doi: and isbn: schemes are not HTTP-dereferenceable. But it does not
> mean they do not form valid URIs, in RDF or otherwise.
> 
> https://www.w3.org/TR/uri-clarification/
> 
>> On Tue, Feb 19, 2019 at 5:09 PM Young,Jeff (OR) <[log in to unmask]> wrote:
>> 
>> These unresolvable URI schemes are from the days when web standards didn’t support http URIs for things that weren’t web resources. That changed with httpRange-14 (2005), which officially allowed http URIs to be used to identify anything, enabling linked data (2006).
>> 
>> 
>> 
>> The old way of defining/registering URI schemes that don’t have a corresponding protocol lost their value as a solution.
>> 
>> 
>> 
>> Jefef
>> 
>> 
>> 
>> From: Bibliographic Framework Transition Initiative Forum <[log in to unmask]> on behalf of Martynas Jusevičius <[log in to unmask]>
>> Reply-To: Bibliographic Framework Transition Initiative Forum <[log in to unmask]>
>> Date: Tuesday, February 19, 2019 at 10:59 AM
>> To: "[log in to unmask]" <[log in to unmask]>
>> Subject: Re: [BIBFRAME] When a bf:Identifier is a URI
>> 
>> 
>> 
>> doi: and isbn: are both URN schemes, as far as I know.
>> 
>> For example
>> 
>> "urn:isbn:0-486-27557-4 "^^xsd:anyURI
>> 
>> On Tue, 19 Feb 2019 at 16.52, Tim Thompson <[log in to unmask]> wrote:
>> 
>> Thanks, Jeff--I was just about to point to the Wikidata approach as well. Isolating the uniquely identifying component from the IRI allows for greater flexibility and supports persistence: a formatter URL can be supplied (and potentially changed when needed) to dereference the identifier as an IRI and potentially include that in serialized output [1].
>> 
>> 
>> 
>> Tim
>> 
>> 
>> 
>> [1] https://www.wikidata.org/wiki/Property:P244#P1921
>> 
>> 
>> 
>> 
>> 
>> --
>> Tim A. Thompson
>> Discovery Metadata Librarian
>> Yale University Library
>> 
>> 
>> 
>> 
>> 
>> On Tue, Feb 19, 2019 at 10:39 AM Young,Jeff (OR) <[log in to unmask]> wrote:
>> 
>> I like how Wikidata deals with this in their RDF. Each identifier scheme gets its own property, which can then be described in various ways. For example:
>> 
>> 
>> 
>> https://www.wikidata.org/wiki/Property:P244
>> 
>> 
>> 
>> When you go to use that property as an external ID on items, which allows you to elaborate on that specific identifier using qualifiers, such as here:
>> 
>> 
>> 
>> https://www.wikidata.org/wiki/Q963044#P434
>> 
>> 
>> 
>> Jeff
>> 
>> 
>> 
>> From: Bibliographic Framework Transition Initiative Forum <[log in to unmask]> on behalf of Simeon Warner <[log in to unmask]>
>> Reply-To: Bibliographic Framework Transition Initiative Forum <[log in to unmask]>
>> Date: Tuesday, February 19, 2019 at 10:24 AM
>> To: "[log in to unmask]" <[log in to unmask]>
>> Subject: Re: [BIBFRAME] When a bf:Identifier is a URI
>> 
>> 
>> 
>> I agree with Lars on both counts. An unquoted URI in RDF does not stand
>> for the identifier, it stands for the resource. Thus, ugly as it is,
>> there is no option except using a literal. One might paraphrase:
>> 
>> "The first rule of identifier club is that there is no way to talk about
>> identifiers"
>> 
>> Cheers,
>> Simeon
>> 
>> 
>>> On 2/19/19 5:32 AM, Svensson, Lars wrote:
>>>> On Tuesday, February 19, 2019 9:49 AM, Adrian Pohl wrote:
>>>> 
>>>>> On 19.02.19 04:03, Dan Scott wrote:
>>>>> 
>>>>> In a linked data context, I think that forcing a URI to be
>>>>> represented as a literal (with a blank node as a bonus), instead of as
>>>>> the URI it is, is an anti-pattern.
>>>> 
>>>> I agree, but as I pointed out in the last email I also think that it is
>>>> bad practice to use an URI when you are talking _about_ the URI (like it
>>>> is bad practice to not add quotations when you are talking about a word
>>>> in a written sentence).
>>> 
>>> I tend to agree with Adrian here: We're talking about the identifier as a sequence of characters.
>>> 
>>>> But there is a third option, we should definitely consider: In my
>>>> opinion the best approach is to only use non-URI identifiers in a
>>>> bf:identifiedBy statement so that the question does not come up. In the
>>>> case that you have different URIs denoting the same resource it probably
>>>> is best practice to use schema:sameAs or something similar to state that
>>>> those URIs refer to the same thing.
>>> 
>>> Here I tend to disagree with Adrian: We should not limit ourselves to non-URI identifiers.
>>> 
>>> I'm also not quite happy with the use of schema:URL (what if we use IRIs?). My preferred pattern would be to use dct:type to say what kind of identifier it is and have a set of skos:Concepts to represent the identifier types. (I know, the definition of dct:type says that the rdfs:range is rdfs:Class, but I _think_ that the DCMI Usage Board currently is working on relaxing that to
>>> 
>>> dct:type a rdf:Property ;
>>> schema:rangeIncludes rdfs:Class .
>>> ) [1].
>>> 
>>> That way we'd get:
>>> 
>>> @prefix bf: <http://id.loc.gov/ontologies/bibframe/> .
>>> @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
>>> @prefix dct: <http://purl.org/dc/terms/> .
>>> @prefix skos: <http://www.w3.org/2004/02/skos/core#> .
>>> 
>>> <http://example.org/2335409#Work> a bf:Text, bf:Work ;
>>> bf:identifiedBy [ a bf:Identifier ;
>>> dct:type bf:URI ;
>>> rdf:value "http://worldcat.org/entity/work/id/638612"
>>> ] .
>>> 
>>> bf:URI a skos:Concept .
>>> 
>>> [1] https://github.com/dcmi/usage/blob/master/minutes/2018/2018-11-20.dcub-decisions.md
>>> 
>>> Best,
>>> 
>>> Lars
>>> 

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 2024
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