# Presentation: 797088

## doi>

- Digital Object Identifier

**doi>**

- A Handle Implementation
- Norman Paskin, International DOI Foundation

## Digital 
Object 
Identifier 

- Object
- Identifier

- What is DOI?

-   A unique identifier for "a piece of content“            	on digital networks
-   Digital object *interoperability*

**doi>**

## doi>

-   DOI – a Handle implementation

**doi>**

-   DOI – more than a Handle implementation:
- uses Handle as one component, of several that make up the DOI system
-   analogy:
-   engine and car?

- Handle and DOI

## doi>

* **by *_*structured *_
*metadata*

*Resolution*
* **by Handle*

*Numbering *
*scheme*

* **Policies*

**doi>**

## A unique identifier for "a piece of content" in the physical world 
single, common system: UPC/EAN Bar Code 
components: code writers, readers, policies, etc.  
many uses : once assigned, usable by anyone in chain
wide community support made it work
self-sustaining cost recovery model etc.
standard – helps to integrate systems efficiently 

- A unique identifier for "a piece of content" in the physical world
- single, common system: UPC/EAN Bar Code
- components: *code writers, readers, policies, etc.*
- many uses : once assigned, *usable by anyone* in chain
- wide community support made it work
- self-sustaining cost recovery model etc.
- standard – helps to integrate systems efficiently

- Analogy: the physical bar code

**doi>**

## "The DOI is the UPC (Bar Code) for objects of intellectual property on the Internet.”  
1.  Uniquely identifies “content” 
enables management of transactions of all kinds 
2.  Provides a stable, persistent link 
to the content itself or to services
3.  Can be used to articulate services as real world  applications 
using metadata, multiple resolution, rules, etc. 

- 1.  Uniquely identifies *“content”*
- enables management of transactions of all kinds
- 2.  Provides a stable, persistent link
- to the content itself** ***or to services*
- 3.  Can be used to articulate services as real world  applications
- using metadata, multiple resolution, rules, etc.

- What is the DOI?

**doi>**

**doi>**

## Show DOI as combination of components
use existing standards including Handle
Show examples of services (applications) built on DOI
Examples here web–based 
but DOI applicable to all platforms   

- use existing standards including Handle
- Show examples of services (applications) built on DOI
- Examples here web–based
- but DOI applicable to all platforms

- This presentation

**doi>**

**doi>**

## An identifier “container” e.g.
10.1234/5678
10.2341/0-7645-4889-1
10.5678/978-0-7645-4889-4
10.1000/ISBN 0764548891
10.1234/Norman_presentation
10.2224/2003-1-29-CENDI-DOI
etc

- can include **any **
**existing identifier**,
- formal or informal,
- of any entity

- An identifier “container” e.g.
- 10.1234/5678
- 10.2341/0-7645-4889-1
- 10.5678/978-0-7645-4889-4
- 10.1000/ISBN 0764548891
- 10.1234/Norman_presentation
- 10.2224/2003-1-29-CENDI-DOI
- etc

## Resolve from DOI to: 

- allows a DOI to link to
**any & multiple pieces**
- of current data

- Resolve from DOI to:
- Location (URL) – *persistence*
- Resolve to multiple data:
- Multiple locations
- Metadata
- Services
- Nested DOIs (related objects etc)
- Extensible: new types

## Metadata

- DOI can describe
**any form** of
- intellectual property,
-  at **any level** of
- granularity

- For interoperability
- Kernel metadata
- A standard, interoperable, small set of data
- Able to use existing metadata
- Mapped using standard dictionary
- Providing a standard way of accessing and using the object
- “Hooks” to Open URL, UDDI, etc
- DOI Applications, Services

## Common rules of the road (IDF)

- allow **any  **
**business model**
- for practical
-  implementations

- Governance and agreed scope, policy, rules
- Cost-recovery (self-sustaining)
- Registration agencies (cf ISBN, Visa)
- Each can develop own applications, services, sector rules, business model, fees, metadata etc
- DOI at cost
- DOI free
- DOI with other services
- etc

## <indecs> framework:

- DOI can describe
**any form** of
- intellectual property,
-  at **any level** of
- granularity

*Handle resolution *
- allows a DOI to link to
**any & multiple pieces**
- of current data

*DOI syntax*
- can include **any **
**existing identifier**,
- formal or informal,
- of any entity

*DOI policies *
- allow **any  **
**business model**
- for practical
-  implementations

## doi>

-   The combination of components is unique
-   Aim to use *existing standards* or, if not available, to *develop standards* with others
-  Numbering: standard principles
- (Naming authorities, delegated responsibility, uniqueness, non-intelligent numbering, etc)
-  Resolution: DOI is a Handle implementation
- (Initially single, now multiple resolution; close collaboration with CNRI as technology partner)
-  Metadata: indecs framework
- (Initially <indecs> consortium, now ISO MPEG)
-  Policies: based on similar business models
- (UPC, ISBN, Visa, etc.)

**doi>**

- DOI components

## doi>

**Single redirection **
**(persistent identifier****)**

**Metadata**

**W3C, WIPO, NISO, ISO, MPEG etc.**

**Multiple resolution**

**A continuing development activity**

- DOI: development path

**doi>**

## “Interoperability of data in e-commerce systems”
<indecs> – a multi-partner effort:  see www.indecs.org 
Became adopted and now basis of ISO MPEG-21 Dictionary approach:  see the paper “Towards a Rights Data Dictionary” 

Unique Identification
Functional Granularity
Designated Authority
Appropriate Access
Metadata as “a relationship between two entities”

- The “metadata” component

**do****i****>**

**doi>**

- “Interoperability of data in e-commerce systems”
- <in*d*ecs> – a multi-partner effort:  see www.indecs.org
- Became adopted and now basis of ISO MPEG-21 Dictionary approach:  see the paper “Towards a Rights Data Dictionary”
- Unique Identification
- Functional Granularity
- Designated Authority
- Appropriate Access
- Metadata as “a relationship between two entities”

**doi>**

## Precision – a consistent extensible framework, for automation
Terminology – defined scope “content” more precisely
In relation to “Digital Objects”, W3C “resources”, WIPO “works”:
description by precise attributes, ontology
Ability to interoperate with any existing metadata 
SCORM, MARC, ONIX, etc
Link to standards work like MPEG, XML

A way of defining “Application Profiles” 
sets of metadata plus rules, a way of grouping DOIs 
the basis of applications beyond simple persistence  
documentation now being completed  

- The “metadata” component

**do****i****>**

**doi>**

- Precision – a consistent extensible framework, for automation
- Terminology – defined scope “content” more precisely
- In relation to “Digital Objects”, W3C “resources”, WIPO “works”:
- description by precise attributes, ontology
- Ability to interoperate with any existing metadata
- SCORM, MARC, ONIX, etc
- Link to standards work like MPEG, XML
- A way of defining “Application Profiles”
- sets of metadata plus rules, a way of grouping DOIs
- the basis of applications beyond simple persistence
- documentation now being completed

**doi>**

*Why this has been important to DOI*

## doi>

- in DOI can describe
**any form** of
- intellectual property,
-  at **any level** of
- granularity

- Text objects (ONIX)
- Art objects (CIDOC)
- Learning objects (SCORM)
- Audio objects (GRID)
- Video objects (SMPTE)
- etc

- Metadata efficiency

**doi>**

**doi>**

## doi>

- DOI can describe
**any form** of
- intellectual property,
-  at **any level** of
- granularity

- Text objects (ONIX)
- Art objects (CIDOC)
- Learning objects (SCORM)
- Audio objects (GRID)
- Video objects (SMPTE) etc

- Metadata efficiency

**doi>**

-   Common single mapping

**doi>**

## Acrobat plug-in as focus example here (web based)
Four example demonstrations shown here:
Version (provide a dynamic update version of the pdf in hand)
Multiple resolution (retrieve multiple data: a URL and some metadata in this case)
CrossRef (retrieve a standard set of metadata and use it in an application, a citation builder)
Rights (very simple e-commerce interface as an illustration)

- Adding value: services

**do****i****>**

**doi>**

- Acrobat plug-in as focus example here (web based)
- Four example demonstrations shown here:
- Version (provide a dynamic update version of the pdf in hand)
- Multiple resolution (retrieve multiple data: a URL and some metadata in this case)
- CrossRef (retrieve a standard set of metadata and use it in an application, a citation builder)
- Rights (very simple e-commerce interface as an illustration)

**doi>**

## doi>

**PDF**

**Tool Bar**

**Plug-In**

**[ cache ]**

- Acrobat Reader

**do****i****>**

- Adobe plug-in concept: what

- PDF document viewed
- through Acrobat reader

**doi>**

**doi>**

## Demo 1 – “get latest version”

**Tool Bar**

**Demo 1 – “get latest version”**

## Demo 1 – “get latest version”

- cnri.test.jsn/pdf

- TYPE

- DATA

- http://host-4-211/book-newversion.pdf

- url

- last_modified

- 2002-06-13T14:06:03-03:00

- DOI

- Handle** **Record

**2002-06-13T14:06:03-03:00**

_**http://host-4-211/book-newversion.pdf**_

**Internet**

**Handle System**

**Demo 1 – “get latest version”**

## Demo 1 – “get latest version”

**Tool Bar**

**Demo 1 – “get latest version”**

## Demo 2 – MultiRes

**Demo 2 – MultiRes**

## Demo 2 – MultiRes

**Demo 2 – MultiRes**

## Demo 2 – MultiRes

**Demo 2 – MultiRes**

## Demo 2 – MultiRes

**Demo 2 – MultiRes**

## Demo 3 –Citation 

**Tool Bar**

**Demo 3 –Citation **

## Demo 3 –Citation 

**Demo 3 –Citation **

## Demo 3 –Citation 

**Demo 3 –Citation **

## Demo 3 –Citation 

**Demo 3 –Citation **

## Demo 4 – Permissions

**Tool Bar**

**Demo 4 – Permissions**

## Demo 4 – Permissions

**Tool Bar**

**Demo 4 – Permissions**

## Demo 4 – Permissions

**Tool Bar**

**Demo 4 – Permissions**

## Demo 4 – Permissions

**Demo 4 – Permissions**

## Put the DOI data in functional units in the DOI record [Handle]; and the knowledge of what to do with them in the client
Demonstrated with an end-user client (Acrobat) but equally applicable to middleware
No constraints on adding additional functional units to a given DOI
A common approach – could use same Handle record to manage pdf, html, mobile, etc.,  hence efficient in deploying content across platforms
The resolution to returned metadata through Application Profiles  allows complex applications 

Provided a complete packaged solution: numbering, resolution, metadata, policies 
On which individual applications and services can be built
The same additional components could be of interest to other Handle applications:  metadata, policies
Avoid reinvention of the wheel 

- Demonstrated with an end-user client (Acrobat) but equally applicable to middleware
- No constraints on adding additional functional units to a given DOI
- A common approach – could use same Handle record to manage pdf, html, mobile, etc.,  hence efficient in deploying content across platforms
- The resolution to returned metadata through *Application Profiles*  allows complex applications
- Provided a complete packaged solution: numbering, resolution, metadata, policies
- On which individual applications and services can be built
- The same additional components could be of interest to other Handle applications:  metadata, policies
- Avoid reinvention of the wheel

**doi>**

- What we have done

**doi>**

## doi>

**10.123/456**

**URL**

**http://www....**

- Handles in DOI

**doi>**

## Several hundred organisations
Several million DOIs 
Examples:  
CrossRef 
Content Directions Inc 
TSO The Stationery office + others (Europe, US, Asia)
Of special interest to CENDI: 
TSO – UK government documents
Learning Objects Network - the ADL initiative  
Office of Publications of European Union*
British Library*
etc 
[*under discussion]

- Several million DOIs
- Examples:
*CrossRef** *
*Content Directions Inc *
*TSO The Stationery office* + others (Europe, US, Asia)
- Of special interest to CENDI:
- TSO – UK government documents
- Learning Objects Network - the ADL initiative
- Office of Publications of European Union*
- British Library*
- etc
- [*under discussion]

- Who is using it now?

**do****i****>**

**doi>**

**doi>**

## International DOI Foundation (IDF) 
Open member organisation, launched 1998
Members; publishing, technology, intermediaries
Modelled on W3C, and on the Bar code development 
www.doi.org

- Open member organisation, launched 1998
- Members; publishing, technology, intermediaries
- Modelled on W3C, and on the Bar code development
- www.doi.org

- Who has done this?

**do****i****>**

**doi>**

**doi>**

## Web site at   http://www.doi.org
DOI Handbook   [http://www.doi.org/hb.html]
DOI news  [e mail sign up on site]
DOI FAQs – in your pack  [http://www.doi.org/faq.html]
Metadata: 
Indecs framework   [http://www.indecs.org]
And see e.g. “Towards a Rights data Dictionary” [http://www.doi.org/topics/020522IMI.pdf] 

- DOI Handbook   [http://www.doi.org/hb.html]
- DOI news  [e mail sign up on site]
- DOI FAQs – in your pack  [http://www.doi.org/faq.html]
- Metadata:
- Indecs framework   [http://www.indecs.org]
- And see e.g. “Towards a Rights data Dictionary” [http://www.doi.org/topics/020522IMI.pdf]

- More information?

**do****i****>**

**doi>**

**doi>**

## doi>

- Digital Object Identifier

**doi>**

- Norman Paskin, International DOI Foundation