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: expressing an identifiers as a (non http) URI (was:....identifiers)

From:

Jeff Young <[log in to unmask]>

Reply-To:

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

Date:

Sat, 19 Jul 2014 23:14:44 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (18 lines)

One of the nice things about owl:sameAs is that it mitigates the failure of centralize (hub) identifiers.

Granted, owl:sameAs assertions need to be taken with a grain of salt and they are nowhere near a declaration that the *descriptions* are "sameAs", but on the whole we should expect the aggregation of statements to "make sense".

> On Jul 19, 2014, at 10:50 PM, "[log in to unmask]" <[log in to unmask]> wrote:
>
> While I don't want to quibble with a line of thinking with which, on the whole, I entirely agree, I would point out that resolving systems haven't uniformly failed, historically. The Domain Name System works. (Imperfectly, yes, very imperfectly, and it does not support functionality we might, in a different world, desire it to, such as the recordation of provenance. But it does, on the whole, work.) In fact, we intend to rely on it to some extent if we intend to do Linked Data with "usual" URLs (as opposed to URLs with IP addresses in them).
>
> Perhaps the meaning here was that _centralized_ resolving systems (which offer a single point of failure, e.g. purl.org) have generally failed (and often at that single point)?
>
> ---
> A. Soroka
> The University of Virginia Library
>
>> On Jul 19, 2014, at 1:43 PM, "[log in to unmask]" <[log in to unmask]> wrote:
>>
>> I do not think that resolving systems can be a solution for something reliable. They failed from a historical view (there are reasons why e.g. Google never was in the need of an URN resolver).

Top of Message | Previous Page | Permalink

Advanced Options


Options

Error during command authentication.

Error - unable to initiate communication with LISTSERV (errno=111). The server is probably not started.

Log In

Log In

Get Password

Get Password


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager