resolution issues and doi

Resolution issues and DOI

doi>

POLICIES

Any form of identifier

NUMBERING

DESCRIPTION

<indecs> framework:DOI can describe any form of intellectual property, at any level of granularity

ACTION

Handle resolution allows a DOI to link to any and multiple piecesof current data

doi>extensible

Handle System

Web Browser

Local Client www.pub.com

DOI?

URLabc

abc.doc

Handle resolution

Handle resolution

Client

GHS LHSLHS

LHS LHS

Handle system: - a collection of Handle services

Site3

- each of which consists of one or more replicated sites

Site2 Site1

Site n

http://www.loc.gov/.....loc.ndlp/amrlp.123456 URL

URLhttp://www.loc2.gov/.....

Handle record

Handle query

- each of which may have one or more servers

#1#2#3 #n

Handle

• CNRI (www.handle.net); open standard• Proven• Scalable: the number of steps to get to any

one Handle is independent of the number of Handles in existence

• A layer:DOI

Handle

TCP/IP

Physical net

http, other protocols

Other HDL apps

TCP/IP

Physical net

3

DOI Handle dataDOI Data type Index

10.123/456 URL http://srv1.pub.com/.....3

URL http://srv2.pub.com/.....2

9URL http://srv3.pub.com/.....59MD http://lu.cr.com/10.123..10

999EM [email protected]

9IP 10.456/7894

Handles (DOIs) resolve to Typed Data

Handle Handle data

3

Handle dataDOI Data type Index





9IP 10.456/7894

DOIs resolve to Typed Data

Multiple typed values per DOI

3






9IP 10.456/7894


Extensible typing

3


10.123/456 URL http://srv1.pub.com/.....3URL http://srv2.pub.com/.....2



9IP 10.456/7894


Query by type

There are two types of Handle query

1. Request all data 2. Request all data of a given type

(Because Handle is a lightweight efficient protocol)


1. Request all data

Handle System

“Give me all data associated with 10.1000/123”

HandleClient

3251094

10.1000/123 URL1(Server in US)URL2 (Server in Asia)URL3 (Server in Europe)public keyemail addressrights data

URLURLURLPKEMIP

Index Type DataHandle

32 5

10.1000/123 URL1(Server in US)URL2 (Server in Asia)URL3 (Server in Europe)

URLURLURL

Index Type DataHandle

“Give me all data of type URL associated with 10.1000/123”

HandleClient

2. Request all data of a given type

Handle System

In each type of query, the client could then do something else with the data it gets back.


Screenshot of multiple resolution tool

D-Lib articles are available at four mirrored sites

Screenshot of multiple resolution tool

Some Other

Process

(1)

Handle System

(2)

3251094

10.1000/39505468499584974 URL1(Server in US)URL2 (Server in Asia)URL3 (Server in Europe)public keyemail addressrights data

URLURLURLPKEMIP

Some other handle aware process uses a DOI to contact the Handle System and request all URLs associated with that DOI. . .

doi:10.1000/39505468499584974

Internet

Future resolution (1)

URL1 (Server in US)URL2 (Server in Asia)URL3 (Server in Europe)

Handle System

(3)

325

10.1000/39505468499584974 URLURLURL

. . . and then ranks those URLs based on performance or best location . . .

Some Other

Process


URL2 (Server in Asia)

. . . chooses the best one, and resolves it.

(4)

URL2 (Server in Asia)

Some Other

Process


A process might use an email address, rights data, or any other “current state” data.

Handle System

(2)

(3)

3251094

10.1000/46578 URL1(US)URL2 (Asia)URL3 (Europe)public keyemail addressrights data

URLURLURLPKEMIP

doi:10.1000/46578

(1)

(4)

rights data

Some Other

Process

Interoperable metadata!


(1)

XML file with embedded DOI

User clicks on a DOI embedded in an XML document.

Future Applicationwith nativeunderstanding of handles and XML

doi:10.1000/5467


The application connects to the Handle System . . .


Handle System(2)

3294

10.1000/5467 http://www.pub.org/http://rights.explain/[email protected]://crossref.org/...

URLIPEMMD


. . . and retrieves DOI data.


(3)

3294

10.1000/5467 http://www.pub.org/http://rights.explain/[email protected]://crossref.org/..

URLIPEMMD


Handle System

Application analyzes the data associated with that DOI.


http://www.pub.org/http://rights.explain/[email protected]://crossref.org/..

URLIPEMMD

Interoperable metadata!


and dynamically displays for the user a list of options based on the data in the DOI System.


(5)


1. Retrieve document2. Explain rights3. Email query4. Show metadata


Mouseover?

User clicks on which path to follow.


(6)


metadata record

1. Retrieve document2. Explain rights3. Email query

4. Show metadata


• We’ve published some analysis:– “One to many”

• We’re working on implementations (MD type)

• We’ve been doing some experiments:– CNRI + IDEAL + CrossRef + DLF + SFX Framework www.sfxit.com

From theory to practice

• I have found what I want to link to, but:– I have a copy locally; or– I use an aggregator; or– The publisher provides alternative

sources; (etc.)• so I want to go to the “appropriate copy”

– rights issues (access control) are implicit• wider issue is context (“contextualisation”)

– other reasons (paper copies, other services, etc.)

Example issue: getting the appropriate copy

appropriate full text

appropriate abstract

10.1000/123

http://acme.com/pg1.html http://acme.com/pg1.html

10.1000/123

pg1.html

Article withCrossRef

Link

Client

XYZ University

Local copy

DOI as used by CrossRef

Handle Systemdx.doi.org

acme.pub

proxy

10.1000/123?cookie

Redirect to local SFX Server

Handle System

dx.doi.orgUnderstands SFX Cookies

CrossRef

Metadata?

Metadata

localCopy.html


Link

Client

Local SFX Server

XYZ University

First experiment (CrossRef)

“hardcoded”

10.1000/123?cookie

Redirect to local SFX Server

Metadata location?

Meta1.com

Handle Systemdx.doi.org

Understands SFX Cookies

Meta1.comMetadata Collection Service

XYZ University

Client


Link

Local SFX Server

localCopy.html

Metadata?Metadata

Second experiment (CrossRef)

Metadata indirection

Data type in HDL

3



K (url for kernel metadata)2

9MD (url for fuller metadata)3

Multiple resolution for making metadata available?

Handle Handle data

Must have

Could have - User Community decides

• User communities want to control their own activities as far as possible– DTIC; OEBF; RIAA...

– Principle of Subsidiarity

• There must be some common rules – Principle of Interoperability

• Equivalent of constitutional rules?– operations and standards “council”?

Governance issues: “subsidiarity”

• Identifiers are most useful when they can be used anywhere in a supply chain - not just by the assigner – that’s why we need some declared metadata– that’s why DOIs are not private identifers

• General issue is: How to make “assertions” about DOIs

- e.g. appropriate copy issue: local copy@DOI:10.1000/123

- e.g. Amazon@DOI:10.1000/123

Supply chain usage of DOIs and metadata

3





999AMZ Amazon.com/1234569

9IP 10.456/7894

Multiple resolution - consequences

Handle Handle data

Amazon@DOI:10.123/456

3



Handle Handle data

“Who can assign a DOI?”Currently: Registrant is “exclusively responsible for

maintaining the accuracy of data associated with each DOI,

including maintaining the validity of the URL”


3






9IP 10.456/7894


…define a data type

Who can...

…change a data type record

…add a further record

…assign a DOI to an entity

instructions to client when it gets a DOI (so that it can then do something else…):

• on interacting with whole handle – e.g. type=PK; query=Authoritative

• on actions to take with a returned value– e.g. URL?source=JournalABC

• on actions to take with a returned object– loc=chap23

• syntax under discussion

Parameters

• extensible framework can cope with anything we want it to do – spreadsheet analogy

• requires logical framework for identification, metadata (indecs)

• requires prototypes, – DOI-X, DOI-EB, DOI-R, etc

• requires software developers to adopt– Microsoft E-Book reader, etc

• requires thinking (business requirements) !

So:

resolution issues and doi

Documents