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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  March 2019

BIBFRAME March 2019

Subject:

Re: When a bf:Identifier is a URI

From:

Martynas Jusevičius <[log in to unmask]>

Reply-To:

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

Date:

Wed, 6 Mar 2019 21:59:02 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (100 lines)

Dereferencing a URI identifier to get a description of the resource is
not appropriate? That is literally the definition of Linked Data.

On Wed, Mar 6, 2019 at 9:30 PM Denenberg, Ray <[log in to unmask]> wrote:
>
> Can I bring the discussion back to the original question, whether a URI, supplied as the value (rdf:value) of bf:identifiedBy, should be encoded as a literal or an actionable URI.
>
>
>
> I believe the question is probably irrelevant, because, I still believe, there is no practical purpose served by doing so.
>
>
>
> Let me ask this: if it is to be an actionable URI, what do you expect to get upon dereferencing it?
>
> · Do you expect to get a description of the resource? We’ve established that that’s not an appropriate use of an identifier.
>
> · Do you expect to get a copy of the resource? Not only is that also not an appropriate use of an identifier, but there is an existing bibframe property to do that.
>
>
>
> So what do you expect to get?
>
>
>
> Ray
>
>
>
>
>
> From: Bibliographic Framework Transition Initiative Forum <[log in to unmask]> On Behalf Of Young,Jeff (OR)
> Sent: Tuesday, March 05, 2019 8:37 AM
> To: [log in to unmask]
> Subject: Re: [BIBFRAME] When a bf:Identifier is a URI
>
>
>
> Osma,
>
>
>
> Humpf. I checked with WebProtoge and you’re right. I wasn’t expecting that because owl:deprecated is an owl:AnnotationProperty rather than an owl:DatatypeProperty.
>
>
>
> It would still make sense, though, for ISSN (and others) to add this in their linked data RDF to reconcile old school URI schemes and the current Cool http: scheme:
>
>
>
> <urn:ISSN:0044-1570> owl:sameAs <http://issn.org/resource/ISSN/0044-1570>
>
>
>
> That way the tools can deal with differences in practice over time. The same can’t be said for treating the URN as a literal or as an rdf:value.
>
>
>
> Maybe I’m still missing the point?
>
>
>
> Jeff
>
>
>
> From: Bibliographic Framework Transition Initiative Forum <[log in to unmask]> on behalf of Osma Suominen <[log in to unmask]>
> Reply-To: Bibliographic Framework Transition Initiative Forum <[log in to unmask]>
> Date: Tuesday, March 5, 2019 at 3:43 AM
> To: "[log in to unmask]" <[log in to unmask]>
> Subject: Re: [BIBFRAME] When a bf:Identifier is a URI
>
>
>
> Hi Jeff!
>
> Young,Jeff (OR) kirjoitti 4.3.2019 klo 19.43:
> > I agree that identifier agencies should migrate old URI schemes to http:
> > and deprecate them in their RDF with mappings to the modern form for
> > backward compatibility. There’s even a W3C standard for expressing this:
> >
> > <oldURI> owl:deprecated true ;
> > owl:sameAs <newURI> .
>
> Not sure this expresses what you intend. owl:sameAs means that both its
> subject and object are the same thing, the same individual. Thus this
> combination of statements implies that <newURI> is also deprecated.
>
> -Osma
>
> --
> Osma Suominen
> D.Sc. (Tech), Information Systems Specialist
> National Library of Finland
> P.O. Box 26 (Kaikukatu 4)
> 00014 HELSINGIN YLIOPISTO
> Tel. +358 50 3199529
> [log in to unmask]
> http://www.nationallibrary.fi

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

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