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

BIBFRAME May 2013

Subject:

Re: bibframe properties with isomorphic URLs

From:

Tim Cole <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Wed, 8 May 2013 12:33:59 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (66 lines)

Perhaps it's overly pedantic for BIBFRAME purposes or explicitly excluded by
BIBFRAME use cases, but in RDF generically the use of
http://orcid.org/0000-0003-1809-1062 as the identifier for Stuart Yates the
individual creates the potential for ambiguity since this same identifier is
also the identifier of an HTML Web page (i.e., the ORCID Web server returns
an HTML file and status 200 when the URI is de-referenced, at least for some
agents). There is therefore the possibility that a machine process might
confuse annotations of the Web page (e.g., 'this Web page does not conform
to HTML 5') with annotations concerning the person (e.g., 'The gender of
Stuart Yates is male') since both annotations would 'annotate' (target in OA
terms) the exact same URI.

A solution commonly used is to mint a separate identifier for the individual
(or concept) and redirect to a description of the individual (or concept)
when that identifier is de-referenced (either human-readable or RDF,
depending on attributes of the agent doing the de-referencing). See for
example what the id.loc.gov Webserver does when you de-reference
http://id.loc.gov/authorities/subjects/sh2007001751.

ORCID has chosen not to do this, so the solution of defining a separate
identifier class for ORCID is more rigorous than simply reusing the URI of
the HTML web page for the individual. But perhaps this rigor is not needed
for BIBFRAME assuming there is community agreement that everyone using
BIBFRAME will rely on other ways to avoid ambiguity when using ORCID-based
URIs?

Tim Cole
University of Illinois at UC


-----Original Message-----
From: Bibliographic Framework Transition Initiative Forum
[mailto:[log in to unmask]] On Behalf Of Wallis,Richard
Sent: Wednesday, May 08, 2013 5:07 AM
To: [log in to unmask]
Subject: Re: [BIBFRAME] bibframe properties with isomorphic URLs

+2

On 08/05/2013 01:14, "Young,Jeff (OR)" <[log in to unmask]> wrote:

>+1
>
>Sent from my iPad
>
>On May 7, 2013, at 8:13 PM, "stuart yeates" <[log in to unmask]>
>wrote:
>
>> Some properties (orcid, viaf, etc) are isomorphic with dereferencable
>>URLs. That is these properties can be mapped to a canonical URI property
>>and back again and no information is lost.
>>
>> For example my ORCID is 0000-0003-1809-1062 and that can be mapped to
>>and from the URI http://orcid.org/0000-0003-1809-1062
>>
>> It seems to me that the orcid and viaf properties should be dropped
>>from bibframe, reducing the complexity of the vocabulary.
>>
>> cheers
>> stuart
>> --
>> Stuart Yeates
>> Library Technology Services http://www.victoria.ac.nz/library/
>>
>

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

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