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

BIBFRAME February 2019

Subject:

Re: When a bf:Identifier is a URI

From:

"Svensson, Lars" <[log in to unmask]>

Reply-To:

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

Date:

Thu, 28 Feb 2019 12:43:36 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Hi Ray,

On Friday, February 22, 2019 8:42 PM, Denenberg, Ray wrote:

> I’m still wondering why you’d want to do this:
> 
> some:resource bf:identifiedBy [
>          a some:type ;
>          rdf:value “ http://issn.org/resource/ISSN/1084-5305” ]
> 
> (quoted or not)
> 
> Vs.
> 
> some:resource bf:identifiedBy [
>          a bf:Issn ;
>          rdf:value “1084-5305” ]

You're right, Ray: I don't want to do the first when it comes to ISSNs. If, however, the canonical identifier for a resource happens to be a URI, I'd want to treat that URI as any other identifier and put it in quotes.

Best,

Lars

> 
> 
> From: Bibliographic Framework Transition Initiative Forum
> <mailto:[log in to unmask]> On Behalf Of Svensson, Lars
> Sent: Thursday, February 21, 2019 11:26 AM
> To: mailto:[log in to unmask]
> Subject: Re: [BIBFRAME] When a bf:Identifier is a URI
> 
> Dan,
> 
> Re your question if „the requirement to quote the ISSN URI as a string when used
> as the bf:Issn object of bf:identifiedBy hold true?” :
> 
> My take would be that an instance of the class bf:Issn cannot be a quoted string
> since that would lead to a literal in the subject position:
> 
> some:resource bf:identifiedBy “http://issn.org/resource/ISSN/1234-5678#ISSN” .
> 
> which implies
> 
> “http://issn.org/resource/ISSN/1234-5678#ISSN” a bf:Issn .
> 
> since we have
> 
> bf:Issn rdfs:subClassOf bf:Identifier.
> 
> If we on the other hand have
> 
> some:resource bf:identifiedBy [
>          a bf:Issn ;
>          rdf:value “http://issn.org/resource/ISSN/1234-5678#ISSN” .
> ] .
> 
> we should be fine.
> 
> Or did I misunderstand your proposal?
> 
> Best,
> 
> Lars
> 
> *** Lesen. Hören. Wissen. Deutsche Nationalbibliothek ***
> --
> Dr. Lars G. Svensson
> Deutsche Nationalbibliothek
> Informationsinfrastruktur
> Adickesallee 1
> 60322 Frankfurt am Main
> Telefon: +49 69 1525-1752
> Telefax: +49 69 1525-1799
> mailto:[log in to unmask]
> http://www.dnb.de
> 
> From: Bibliographic Framework Transition Initiative Forum
> [mailto:[log in to unmask]] On Behalf Of Dan Scott
> Sent: Wednesday, February 20, 2019 11:45 PM
> To: mailto:[log in to unmask]
> Subject: Re: [BIBFRAME] When a bf:Identifier is a URI
> 
> Ray et al:
> 
> Thank you to both the BIBFRAME mailing list and the LC BIBFRAME team for taking
> this seriously.
> 
> > Still, bibframe does not preclude declaring that a particular URI is an identifier for
> a particular resource (although we would still welcome a use case).
> 
> ISSNs have had dereferenceable URIs for almost two years now
> (https://www.issn.org/wp-content/uploads/2017/12/ISSN-
> LinkedDataApplicationProfile-v0_9.pdf). Does the requirement to quote the ISSN
> URI as a string when used as the bf:Issn object of bf:identifiedBy hold true?
> 
> Thanks,
> Dan
> 
> P.S. In a side channel, Sarven Capadisli pointed me at the 2017 document
> https://www.w3.org/DesignIssues/QuotingURIs.html which describes a rationale for
> quoting URIs in certain situations, where owl:sameAs may result in two different
> URIs no longer being distinguished properly. I found this helpful, although I don't
> think it comes into play here, as bf:identifiedBy does not make any owl:sameAs
> assertions that would trigger the detrimental outcomes outlined in the design note.
> 
> On Tue, 19 Feb 2019 at 15:58, Denenberg, Ray <mailto:[log in to unmask]> wrote:
> The LC bibframe team discussed this at length this morning.
> 
> There were only about four messages at the time and now there are now many
> more, too many to keep up with it all.  Among those early messages there seemed to
> be only this use case:
> 
> <http://example.org/2335409#Work> a bf:Text, bf:Work ;
>    bf:identifiedBy <http://worldcat.org/entity/work/id/638612>.
> 
> Which seems to say, there is a work, http://example.org/2335409#Work, at
> institution A, and this, http://worldcat.org/entity/work/id/638612, at institution B,
> is the same work.
> 
> (Nevermind what constitutes sameness -  whatever institution A considers it to
> be.  Could be matched based on author and title for example.)
> 
> We don’t think this is an appropriate use of
> bf:identifiedBy.     http://worldcat.org/entity/work/id/638612    doesn't identify
> http://example.org/2335409#Work. Rather, the assertion is that they are the same
> resource.
> 
> We recognize that there is a need to make such an assertion, that bibframe
> currently does not provide one, and we will investigate this further.
> 
> Still, bibframe does not preclude declaring that a particular URI is an identifier for a
> particular resource (although we would still welcome a use case).   As has been
> suggested, it should be quoted (a string) rather than a resource.  bf:identifiedBy is
> intended for string identifiers, not for identifiers that are themselves linked data
> resources.
> 
> Example:
> 
> <http://example.org/workA>
>        bf:identifiedBy [
>                    a   xs:anyURI ;
>                   rdf:value     “http://example.org/identifierA” ]
> 
> Ray
> 
> From: Bibliographic Framework Transition Initiative Forum
> <mailto:[log in to unmask]> On Behalf Of Dan Scott
> Sent: Friday, February 15, 2019 7:45 PM
> To: mailto:[log in to unmask]
> Subject: [BIBFRAME] When a bf:Identifier is a URI
> 
> While the description for bf:Identifier
> (http://id.loc.gov/ontologies/bibframe.html#c_Identifier) is "Token or name that is
> associated with a resource, such as a URI or an ISBN", its subclasses include bf:Isbn
> but not bf:Uri[1].
> 
> For now I've interpreted this as "just use bf:Identifier if you have a URI," but if that
> interpretation is correct, it might make sense to clarify the description.
> 
> Example:
> 
> @prefix bf: <http://id.loc.gov/ontologies/bibframe/> .
> <http://example.org/2335409#Work> a bf:Text, bf:Work ;
>    bf:identifiedBy <http://worldcat.org/entity/work/id/638612>.
> 
> <http://worldcat.org/entity/work/id/638612> a bf:Identifier .

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