[ View/Print a PDF Version of this document. ]

This factsheet provides a bullet-point overview of the value added by the DOI System. It aims to provide a useful checklist of the functionality of the DOI System and its value compared to other systems which provide some or all of the functionality provided by DOI^® names.

For more detail on certain aspects of the DOI System underlying technologies, see the accompanying DOI Factsheets.

Principles of comparison

The value of the DOI System derives from three functions:

• Persistent identification
• Network actionability
• Semantic interoperability

Value is added by each of these three. Comparison with alternative systems depends on which of the functions (none, one, or more) is provided by the compared system.

Design

A system for persistent, semantically interoperable, identification of intellectual property entities on any digital network.

• Persistent Identifier: identifies the intellectual property entity itself rather than its location. Managed directory system relates to services such as location, enabling management of digital objects for long-term access. If ownership of the entity or the rights in the entity change, the identification of that entity does not change; the responsibility for managing the DOI name may change, but not the DOI name itself
• Actionable Identifier: a user can use a DOI name to do something; facilitates simple location finding but also much more complex applications
• Interoperable Identifier: allows use in services outside the direct control of the issuing assigner
• Neutral as to technical implementation: designed to interoperate with past, present and future technologies. Assumes only the existence of Internet connectivity (not necessarily its underlying transport mechanisms)
• Neutral as to sector or media type: can apply to any format of physical, digital or abstract entities such as resources, parties, licences, abstractions

Standards based

The DOI System utilises existing components in building an added value application.

• Uses existing standards based components, which are also in use elsewhere — advantages of widespread use and support
• System as a whole to be an ISO standard (in process in TC46SC9): value of validation through an external standards process

Syntax

Standard NISO Z39.84 syntax.

• Standardised through NISO: provides branding recognition and ease of application.
• Unicode compliant
• No length or character restrictions
• No semantic requirement, but can incorporate semantics where appropriate and meaningful for other related applications
• Can incorporate existing identifiers (from other schemes) where appropriate

Resolution

Uses Handle System^®.

• The Handle System provides a general-purpose global name service enabling secure name resolution over the Internet, designed to enable a broad set of communities to use the technology to identify digital content independent of location.
• In use in many other applications
• Standardised as IETF RFCs
• Separates identity of underlying digital objects from location; ensures persistence by resolving the DOI name to a current associated value such as a URL
• Resolution may be to multiple pieces of data (multiple resolution)
• Supports administration granularity down to the level of individual DOI names
• Allows internationalized character sets; supports non-ASCII native characters
• Secured resolution service: supports client/server authentication, service integrity, and confidentiality, public key infrastructure if required
• Architecture of the Handle System is flat, scalable, and extensible: number of steps needed to resolve is independent of number of Handles in existence
• Logically central, but physically decentralized
• Supports Local Handle Servers, when desired
• Handle resolutions return entire "Handle Records" or portions thereof
• Handle records are also digital objects
• Handle servers are certificated with the system
• Handle records are signed by the servers
• DOI names are handles whose primary prefix is "10"; provides recognition
• Enhanced browser support available for direct handle access: handle plug-in, and available e.g. for Adobe Acrobat as plug-in
• Uses proxy servers for unenhanced browsers
• Types are resolvable in the Handle System
• Types may be created dynamically
• Types may be locally named, mapped into bit strings without semantics
• Runs on 24/7 secure extensible servers

Data structure

Multiple resolution of handles allows one entity to be resolved to multiple other entities; this can be used to embody relationships, e.g. a parent-children relationship, or any other relationship. Handle System technology allows this; the DOI System provides a framework to achieve it.

• Allows precise specification of exactly what is being identified.
• Data model available for optional specification of DOI name records, grouping in application profiles and services for re-use, shared and/or common use
• Data dictionary available, based on (and consistent with) ISO MPEG-21 RDD standard and other <indecs> activities; consistent with systems such as ONIX and Grid
• Data Dictionary standardised (MPEG21) and in use elsewhere
• Does not mandate one metadata scheme; allows use of any existing metadata scheme whilst enabling mappings between
• Allows declaration of metadata to any level of functional granularity

Technical Infrastructure

The International DOI Foundation funds, on behalf of all its members and DOI System users, certain aspects of technical infrastructure underlying the DOI System.

• Redundant distributed servers, both handle servers and any proxy or application servers required, plus backup procedures
• DOI System specific development and implementation of proxy features (e.g. open URL functionality)
• Central DOI System Directory, staffed and outsourced with backup and reliability guarantees
• Service agreement for management and implementation of shared technical resolution infrastructure
• Data dictionary shared with ONIX (and potentially others), staffed and outsourced
• Uses improved Berkeley database compared to standard Handle System release; benefits of shared expertise, community of users with knowledge and service agreement for support

Social infrastructure

The Handle System technology provides persistence if used with appropriate social infrastructure. The International DOI Foundation (IDF) builds on the technical infrastructure of the Handle System a social structure guaranteeing persistence. Persistence is a function of organizations, not of technology; a persistent identifier system requires a persistent organization and defined processes.

• Not-for-profit neutral organisation open to anyone to join
• Aligned with standards setting organisations, to promote level playing field
• Strength in numbers and economies of scale: for both technical and social infrastructure, leverage joint efforts of a community
• Facilitates applications to be developed & deployed
• Facilitates Metadata registries to be created and maintained
• Encourages third-party value-added providers
• Shared managed use of Trademark and intellectual property: branding, ease of concept marketing
• Shared outreach to other standards communities and potential user communities
• Shared research and development as necessary
• Participates in defining wider Persistent Identifier space through Handle System governance and development
• Common policies and procedures for assignment of DOI names; provides rules and mechanisms for implementation
• Certification process for "Qualified" Registration Agencies
• Scalable extensible franchise model to bring in new RAs
• Agreements to take over orphaned identifiers, distributed shared expertise in various areas e.g. proxy functionality, and potentially a number of agreements on how to structure applications
• Shared licensing and purchasing agreements for technical services

Business potential

The DOI System enables registrants to incorporate persistent, semantically interoperable, identification of intellectual property entities as part of services providing added value.

• Providing identification, management and metadata services
• Enabling third-party value-added capabilities: allows individual registration agencies to provide their own added value functionality on top of an agreed common infrastructure
• Selling infrastructure technology
• Helping organizations manage their own information better & offer new types of services
• Stimulating access to "surface information" and "embedded information" with appropriate access controls and conditions of use
• Necessary infrastructure for digital policy enforcement (including DRM)

[ View/Print a PDF Version of this document. ]