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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  July 2014

BIBFRAME July 2014

Subject:

Re: Bibframe and Linked Data (Authorities)

From:

"[log in to unmask]" <[log in to unmask]>

Reply-To:

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

Date:

Thu, 10 Jul 2014 14:33:16 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (73 lines)

It is useful and convenient, and it won't serve all purposes-- it's good to have, it's just not enough.

That second principle stands entire in a world in which provenance information is separate from DNS. Let's say you publish an HTTP URI identifying an author interesting to me, and I make some assertions using your URI. Then someone consuming my data can "travel through" that URI to find out _something_ more about that author, which is to say, to discover more assertions involving that author (presumably with a subject of that author). So far so good, and that's as far as the second principle takes us. Provenance becomes interesting when my hypothetical patron asks, "Wait, how much can I trust this information about my author? Of what value are these assertions published by Jeff Young to _me_?"

Now, we're no longer in the realm of questions that can be answered by the DNS.

I wouldn't propose that we somehow "outlaw" letting assumptions about provenance rely on DNS, and we couldn't if I was odd enough to demand it. I do propose that we frequently need more than that, and that we should be thinking about how to do it. That doesn't seem too controversial to me. {grin}

---
A. Soroka
The University of Virginia Library

On Jul 10, 2014, at 2:21 PM, "Young,Jeff (OR)" <[log in to unmask]> wrote:

> It depends on how strictly you interpret "provenance" and the need/willingness to carry it's burden. If people are overly concerned about DNS, then what's the point of TimBL's 2nd principle of Linked Data?
>
> 2. Use HTTP URIs so that people can look up those names.
>
> This isn't a heavy-weight form of provenance and won't serve all purposes, but it's useful and convenient.
>
> Jeff
>
>
>> -----Original Message-----
>> From: Bibliographic Framework Transition Initiative Forum
>> [mailto:[log in to unmask]] On Behalf Of [log in to unmask]
>> Sent: Thursday, July 10, 2014 2:04 PM
>> To: [log in to unmask]
>> Subject: Re: [BIBFRAME] Bibframe and Linked Data (Authorities)
>>
>> No, it does not!
>>
>> We need to distinguish carefully between the URI, which is a pure
>> identifier, and the URI-that-happens-to-be-an-URL, which is also a
>> pointer or link. Much of the power of linked data comes precisely from
>> combining those roles, but that needs to be a conscious decision and
>> not a matter of faith. {grin}
>>
>> Let's say that a very small institution publishes a number of URIs like
>> "http://www.littlelibrary.org/authorities/4535". Then Little Library
>> disappears as an organization, and its domain is purchased by someone
>> else. It becomes instantly possible for that someone else to publish
>> anything at all into that namespace and, if we base provenance on the
>> DNS, we have no way to distinguish these groups of identifiers. You
>> might say that VIAF is unlikely to disappear tomorrow, and that's true,
>> but the point is that relying on domain name registrars to manage the
>> provenance information of our metadata would be an accident waiting to
>> happen.
>>
>> ---
>> A. Soroka
>> The University of Virginia Library
>>
>> On Jul 10, 2014, at 1:40 PM, "Smith-Yoshimura,Karen"
>> <[log in to unmask]> wrote:
>>
>>> Kevin -
>>>
>>> Re:
>>>> There's been lots of talk about provenance and the like in a global
>> graph of data, but I feel most of those discussions rely on fairly
>> technical mechanisms, the complexity of >which outweigh the simplicity
>> of minting one's own URI. (Also, the provenance statements will need
>> their own URIs!)
>>>
>>> Doesn't http://viaf.org/viaf/54202464 show the provenance is VIAF?
>> What's complex about this?
>>>
>>> Karen S-Y
>>>
>>>
>>>

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