07.04.2015 Views

Digital Object Identifier - DOIs

Digital Object Identifier - DOIs

Digital Object Identifier - DOIs

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ANSI/NISO Z39.xx-199x<br />

<strong>Digital</strong> <strong>Object</strong> <strong>Identifier</strong><br />

Status:<br />

A Draft American National Standard<br />

Developed by the<br />

National Information Standards Organization<br />

1


ANSI/NISO Z39.xx-199x<br />

About NISO Draft Standards<br />

This is a draft standard and subject to change. To learn the current status of this<br />

proposed standard contact the NISO Office: 4733 Bethesda Avenue, Suite 300, Bethesda, MD<br />

20814 USA; Telephone: 301-654-2512; Fax: 301-654-1721; Internet nisohq@niso.org.<br />

NISO standards are developed by the Standards Committees of the National<br />

Information Standards Organization. A rigorous review process includes offering each NISO<br />

voting member and other interested parties an opportunity to review the proposed standard. In<br />

addition, approval requires verification by the American National Standards Institute that its<br />

requirements for due process, consensus, and other criteria for approval have been met by<br />

NISO; NISO standards thus also become American National Standards.<br />

This standard may be revised or withdrawn at any time. Purchasers may receive<br />

current information on all NISO standards by calling or writing the National Information<br />

Standards Organization.<br />

©1997 National Information Standards Organization<br />

This draft standard may be photocopied for noncommercial purposes to facilitate the review<br />

and approval process.<br />

Address inquiries to NISO, 4733 Bethesda Avenue, Suite 300, Bethesda, MD 20814;<br />

nisohq@niso.org; Telephone: 301-654-2512; Fax: 301-654-1721.<br />

To Order Any NISO Standard Contact:<br />

NISO Press Fulfillment, P.O. Box 338, Oxon Hill, MD 20750-0338 USA<br />

Telephone: 1-800-282-6476 or 301-567-9522<br />

2


ANSI/NISO Z39.xx-199x<br />

Contents<br />

Foreword<br />

Background<br />

Goals<br />

Elements of the DOI String<br />

The DOI and Metadata<br />

The DOI in Context (DOI System, Handle System, IDF)<br />

Character Set Issues<br />

1. Introduction<br />

1.1 Purpose<br />

1.2 Scope<br />

2. Standards and References<br />

2.1 Referenced Standards<br />

2.2 Secondary Standards and References<br />

2.3 Other Standards and References<br />

3. Definitions<br />

4. Format and Characteristics of the DOI<br />

4.1 Prefix<br />

4.2 Suffix<br />

Maintenance Agency<br />

APPENDIX A<br />

Designation of Maintenance Agency<br />

APPENDIX B<br />

Examples<br />

APPENDIX C<br />

Related Standards and References<br />

APPENDIX D<br />

Application Issues<br />

Location and Presentation of the DOI<br />

Representation to End Users<br />

Table 1 – Mandatory Encoding<br />

Table 2 – Recommended Encoding<br />

3


ANSI/NISO Z39.xx-199x<br />

Foreword<br />

This foreword is not part of the American National Standard for the <strong>Digital</strong> <strong>Object</strong> <strong>Identifier</strong><br />

(DOI), ANSI/NISO Z39.xx-199x. It is included for information only.<br />

This standard defines the syntax for the <strong>Digital</strong> <strong>Object</strong> <strong>Identifier</strong> (DOI). The <strong>Digital</strong> <strong>Object</strong><br />

<strong>Identifier</strong> (DOI) system is an identification system for intellectual property in the digital<br />

environment. Developed by the International DOI Foundation on behalf of the publishing<br />

industry, its goals are to provide a framework for managing intellectual content including such<br />

activities such as linking customers with content owners, facilitating electronic commerce, and<br />

enabling automated copyright management.<br />

Background<br />

Some history on the development of this draft standard is needed to understand how and why<br />

the draft standard appears in its present form.<br />

DOI System Background<br />

The Internet is a new environment for commerce of information, and requires new enabling<br />

technologies to provide services and to protect both customer and publisher. Systems must be<br />

developed to identify, authenticate, and protect content to insure that what the customer is<br />

requesting is what is being delivered. At the same time, the rights owner of the information<br />

must be sure that copyright in content is respected and protected.<br />

In considering the new systems required international publishers realized that a first step would<br />

be the development of an identification system to be used for content in the digital<br />

environment. Such a system was launched at the Frankfurt Book Fair in October 1997: the<br />

<strong>Digital</strong> <strong>Object</strong> <strong>Identifier</strong> (DOI) system provides a unique identification mechanism for content,<br />

and also a way to link users of the materials to the rights holders (or their agents) to facilitate<br />

automated digital commerce in the new digital environment.<br />

NISO Involvement and Role of the International DOI Foundation (IDF)<br />

The ongoing management of the DOI System is handled by an international, not-for-profit,<br />

membership-based organization called the International DOI Foundation with offices in the<br />

United States and Geneva, Switzerland. The Foundation is responsible for licensing Directory<br />

Managers/Registration Agencies and technology providers, for setting policy for the system,<br />

and for encouraging development of the related enabling technologies to build the<br />

infrastructure for electronic publishing such as copyright management systems.<br />

Though the DOI System was originally developed by the publishing industry, it was recognized<br />

4


ANSI/NISO Z39.xx-199x<br />

that the DOI system would have a broader scope and that it should work with established<br />

standard bodies as much as possible. ANSI/NISO involvement was requested in early 1998 in<br />

order to recognize the broader potential use of a digital object identifier and it was decided to<br />

develop a standard for the syntax of the DOI identifier string.<br />

Goals<br />

*Decide on the syntax for the DOI identifier string to enable DOI registration. It has been<br />

possible to register <strong>DOIs</strong> for quite awhile but there has been concern that the syntax had<br />

not been conclusively set. This standard will remedy the situation.<br />

*Decide on the elements of the DOI identifier string. A number of proposals were made<br />

to add certain elements to the DOI identifier string and the committee spent much of its<br />

time deciding whether to include them or not.<br />

*Limit the scope of the standard to the DOI identifier string. The DOI system is made up<br />

of a number of parts including the identifier string, the resolution mechanism and the<br />

Directory. This standard addresses only the syntax for the identifier string so the actual<br />

standard is brief.<br />

While limiting itself to the DOI identifier string, the Syntax Committee took into account<br />

the wider context of the DOI system, the Handle system, the International DOI<br />

Foundation and the Internet. In order to provide further information about this context<br />

there is this Forward and a number of Appendices; however, these are not part of the<br />

Standard. They do provide important information and references for understanding the<br />

DOI system, how the DOI is being used, how it relates to other standards and the Internet<br />

and where to get more information.<br />

Elements of the DOI String<br />

The DOI string is made up of a Prefix and Suffix. The Registration Agency assigns the<br />

Prefix while the Registrant determines the Suffix. There were a number of proposals to<br />

add elements to the Prefix and Suffix, the most important being the identifier, or<br />

bracketed, code for the Suffix. This code would have been added in parentheses as the<br />

beginning of the Suffix when a standard identifier, such as the ISRC, ISBN or SICI, was<br />

used. This raised the issue of whether the DOI would be “dumb” or “intelligent”, i.e.<br />

whether the DOI string would contain any meaningful data about the thing it identified.<br />

The DOI string was originally created to be a “dumb” number and adding the identifier<br />

code would have fundamentally changed the nature of the DOI string. So, a conscious<br />

decision was made to leave out the identifier code and keep the DOI string a dumb<br />

number. However, this decision raised many important issues and highlighted the<br />

importance of metadata in the DOI system.<br />

5


ANSI/NISO Z39.xx-199x<br />

The DOI and Metadata<br />

The DOI in Context (DOI System, Handle System, IDF)<br />

The DOI System is an implementation of the Handle System, developed by the Corporation<br />

for National Research Initiatives (CNRI). The DOI System is managed by the International<br />

DOI Foundation, which sets policies, appoints service providers and ensures the successful<br />

operation of the System.<br />

Character Set Issues<br />

The Handle System allows any Unicode character to be used. However, considering the<br />

current and foreseeable application environment for <strong>DOIs</strong>, the Committee decided that <strong>DOIs</strong><br />

should be expressible in 7-bit ASCII. This same decision was taken in ANSI/NISO Z39.56-<br />

1996, Serial Item and Contribution <strong>Identifier</strong> (SICI).<br />

The one excluded character is “space”(%20 hexadecimal). This is excluded because it signifies<br />

the end of a DOI string.<br />

There are certain issues (addressed in Appendix D) concerning character encoding when using<br />

<strong>DOIs</strong> in URLs that are sent via HTTP.<br />

NISO Voting Members<br />

[list]<br />

NISO Board of Directors<br />

[list]<br />

Standards Committee xx<br />

NISO acknowledges with thanks and appreciation the contributions of the following<br />

persons who served on NISO Standards Committee xx that drafted the proposed<br />

standards for the <strong>Digital</strong> <strong>Object</strong> <strong>Identifier</strong> syntax.<br />

[list]<br />

6


ANSI/NISO Z39.xx-199x<br />

<strong>Digital</strong> <strong>Object</strong> <strong>Identifier</strong><br />

1. Introduction<br />

1.1 Purpose<br />

ANSI/NISO Z39.xx-199x defines the syntax for a unique and persistent alphanumeric<br />

character string called the <strong>Digital</strong> <strong>Object</strong> <strong>Identifier</strong> (DOI). The DOI is part of an identification<br />

system for intellectual property in the digital environment called the <strong>Digital</strong> <strong>Object</strong> <strong>Identifier</strong><br />

(DOI) system.<br />

1.2 Scope<br />

This standard defines the syntax of the DOI character string, which is made up of a prefix and<br />

suffix and registered according to the requirements set by the International DOI Foundation<br />

(IDF). Policies governing the assigning and use of <strong>DOIs</strong> are determined by the IDF and are<br />

outside the scope of this document.<br />

2. Standards and References<br />

The Referenced Standards are those that are required to construct a DOI. Secondary<br />

Standards and References includes citations to documents that can be used in conjunction with<br />

or as part of the DOI.<br />

2.1 Referenced Standards<br />

ANSI X3.4:1986 American National Standard for Information Systems – Coded<br />

Character Sets – 7- Bit American National Standard Code for Information Interchange<br />

(7-bit ASCII)<br />

2.2 Secondary Standards and References<br />

International DOI Foundation Guidelines<br />

Uniform Resource <strong>Identifier</strong> (URI)<br />

Uniform Resource Locator (URL)<br />

Uniform Resource Number (URN)<br />

Handle System RFC<br />

ISSN<br />

ISBN<br />

ISWC<br />

1


ISAN, etc<br />

2.3 Other Standards and References<br />

3. Definitions<br />

Creation<br />

An item of intellectual property; a product of human imagination and/or endeavor in which<br />

rights may exist.<br />

<strong>Digital</strong> <strong>Object</strong> <strong>Identifier</strong> system (DOI system)<br />

An identification system for items of intellectual property in the digital environment which<br />

uses a <strong>Digital</strong> <strong>Object</strong> <strong>Identifier</strong> for each item and associates with these various digital<br />

services. The rules of the DOI system are determined by the International DOI<br />

Foundation. The DOI system is an implementation of the Handle system developed by<br />

the Corporation for National Research Initiatives (CNRI).<br />

<strong>Digital</strong> <strong>Object</strong> <strong>Identifier</strong> (DOI)<br />

An alphanumeric character string, conforming to the rules of the DOI system, which<br />

uniquely identifies an item of intellectual property (a Creation).<br />

Directory<br />

A repository in which are registered and maintained <strong>DOIs</strong>, together with the digital<br />

services associated with each DOI, including the location of digital objects.<br />

Directory manager<br />

The entity which controls the Directory.<br />

DOI prefix [ = DOI prefix number]<br />

The unique character string issued by the Registration agency to a registrant for use as the<br />

prefix in the <strong>DOIs</strong> allocated by the registrant.<br />

DOI suffix<br />

The character string allocated by a registrant for use as the suffix in the DOI (uniquely<br />

identifying an item of intellectual property) formed using the DOI prefix held by the<br />

registrant. The suffix is unique within the range of <strong>DOIs</strong> specified by the DOI prefix held<br />

by the registrant.<br />

International DOI Foundation<br />

The body set up to support the needs of the intellectual property community in the digital<br />

environment by establishing and governing the DOI System, setting policies for the<br />

2


System, appointing service providers for the System, and overseeing the successful<br />

operation of the System.<br />

Registration agency [DOI registration agency]<br />

One of the agencies appointed by the International DOI Foundation to register and<br />

allocate DOI prefixes to registrants, and which subsequently registers all <strong>DOIs</strong> issued by<br />

the registrant using the prefix. A registration agency uses the Directory and provides the<br />

information entered into the Directory. The Registration Agency may also be the<br />

Directory Manager in certain cases.<br />

Registrant<br />

An organization or entity which has requested and been allocated a DOI prefix by a<br />

Registration Agency and which subsequently allocates <strong>DOIs</strong> (constructed using that<br />

prefix) to items of intellectual property and registers these in the Directory, with the<br />

permission of, or via, the Registration Agency.<br />

Registration<br />

The act of entering into the Directory a DOI and associated information necessary for the<br />

DOI to be used.<br />

4. Format and Characteristics of the DOI<br />

The DOI is made up of the Prefix and the Suffix. Within the prefix are the Directory <br />

and the Registrant Prefix . The suffix is made up of the DOI Suffix String . The<br />

allowed value of the DOI is a maximum of 128 characters.<br />

The syntax of the DOI string is:<br />

. /<br />

Detailed explanations of each section of the DOI string follow.<br />

4.1 Prefix<br />

- Directory (required, numeric, two digits) –<br />

The current value of is “10”. This is currently the only allowed value. In future, other<br />

numbers may be assigned with the approval of NISO. The Maintenance Agency for this<br />

standard should be contacted regarding other values.<br />

Registrant’s Prefix (required, numeric, no limit)<br />

Separated from by “.” and no spaces. This is the number assigned to the registrant by<br />

the Registration Agency.<br />

3


4.2 Suffix<br />

DOI Suffix String (required, any alphanumeric character except space, no limits)<br />

Preceded by the end “/” of the DOI Prefix, this is the actual identifier string assigned by the<br />

Registrant.<br />

Excluded character – Space (SP). Any 7-bit ASCII character can be used except “space” as<br />

this denotes the end of a DOI string.<br />

4


Maintenance Agency<br />

The maintenance agency designated in Appendix A shall review suggestions for new data<br />

elements, interpret the rules prescribed by this standard, and maintain a listing of inquiries and<br />

responses that may be used for potential future enhancement of this standard. Questions<br />

concerning the implementation of this standard and requests for information should be sent to<br />

the maintenance agency.<br />

APPENDIX A<br />

Designation of Maintenance Agency<br />

This appendix is not part of the American National Standard for <strong>Digital</strong> <strong>Object</strong> <strong>Identifier</strong> (DOI), ANSI/NISO Z39.xx-<br />

199x. It is included for information only.<br />

Maintenance Agency Administered by the International DOI Foundation<br />

The functions assigned to the maintenance agency as specified in Section 7 will be administered<br />

by the International DOI Foundation. Questions concerning the implementation of this standard<br />

and requests for information should be sent to:<br />

Norman Paskin<br />

International DOI Foundation<br />

1718 Connecticut Avenue, NW<br />

Washington, DC 20009, USA<br />

Phone: 202-232-3335 x 222<br />

Fax: 202-745-0694<br />

E-Mail: n.paskin@doi.org<br />

APPENDIX B<br />

Examples<br />

This appendix is not part of the <strong>Digital</strong> <strong>Object</strong> <strong>Identifier</strong> (DOI), ANSI/NISO Z39.xx-199x. It is included for<br />

information only.<br />

An example of an actual DOI is:<br />

10.1006/(ISBN)0120001047<br />

5


The example is made up of the ISBN for the online version of the Encyclopedia of<br />

Immunology from Academic Press.<br />

Another example shows one publisher’s approach to assigning <strong>DOIs</strong> using the SICI.<br />

For journals, assign the DOI based on the ISSN number; 10.1002/0002-8231<br />

For journal issues, assign the DOI based on the issue SICI number; e.g., 10.1002/0002-<br />

8231(199601)47:11.0.TX;2-J<br />

•.<br />

•.<br />

For journal articles, assign the DOI based on the article SICI number; e.g.,<br />

10.1002/(SICI)0002-8231(199601)47:12.0.TX;2-2<br />

For journal abstracts, assign the DOI based on the abstract SICI number; e.g.,<br />

10.1002/(SICI)0002-8231(199601)47:12.3.TX;2-U<br />

6


APPENDIX C<br />

Related Standards and References<br />

This appendix is not part of the <strong>Digital</strong> <strong>Object</strong> <strong>Identifier</strong> (DOI), ANSI/NISO Z39.xx-199x. It is included for<br />

information only.<br />

Other Standards and References<br />

ANSI/NISO Z39.9-1992, International Standard Serial Numbering (ISSN)<br />

ANSI/NISO Z39.21-1988, Book Numbering (ISBN)<br />

ANSI/NISO Z39.56-1996, Serial Item and Contribution <strong>Identifier</strong> (SICI)<br />

Authority List of Standards<br />

International<br />

Standard<br />

ANSI/NISO<br />

Standard<br />

BICI<br />

Book Item and<br />

Contribution <strong>Identifier</strong><br />

Proposed NISO<br />

development<br />

ISAN<br />

ISBN<br />

ISMN<br />

Information and<br />

Documentation -<br />

International Standard<br />

Audio Visual Number<br />

(AGICOA)<br />

Information and<br />

Documentation -<br />

International Standard<br />

Book Numbering<br />

(ISBN)<br />

Information and<br />

Documentation -<br />

International Standard<br />

Music Number (ISMN)<br />

New Work Item<br />

Proposal<br />

ISO/TC46/SC9<br />

N223 (1996-09-<br />

12)<br />

ISO 2108:1992<br />

ISO 10957:1993<br />

Association<br />

de Gestion<br />

Internationale<br />

Collective<br />

des Oevres<br />

Audiovisuelle<br />

s (film<br />

industry)<br />

7


ISRC Documentation -<br />

International Standard<br />

Recording Code<br />

(ISRC)<br />

ISRN Information and<br />

Documentation-<br />

International Standard<br />

Technical Report<br />

Number (ISRN)<br />

ISSN Documentation -<br />

International Standard<br />

Serial Numbering<br />

(ISSN)<br />

ISWC International Standard<br />

Work Code<br />

PII<br />

SICI<br />

Publisher Item<br />

<strong>Identifier</strong><br />

Serial Item and<br />

Contribution <strong>Identifier</strong><br />

(SICI)<br />

ISO 3901:1986<br />

ISO 10444:1997<br />

(revision of ISO<br />

10444:1994)<br />

ISO 3297:1986<br />

Proposed TC46<br />

development<br />

ANSI/NISO<br />

Z39.23-199X<br />

(proposed revision<br />

of ANSI/NISO<br />

Z39.23-1990)<br />

ANSI Z39.9:1979<br />

(R1984)<br />

ANSI/NISO<br />

Z39.56-199X<br />

(Version 2)<br />

(A revision of<br />

Z39.56-1991)<br />

Administered<br />

by IFPI -<br />

International<br />

Federation of<br />

Phonographic<br />

Industries<br />

(London)<br />

TC46 - ISO<br />

Technical<br />

Committee<br />

46:<br />

Information<br />

and<br />

Documentati<br />

on Standards<br />

http://www.el<br />

sevier.nl/hom<br />

epage/about/<br />

pii<br />

http://sunsite.<br />

berkeley.edu/<br />

SICI<br />

8


APPENDIX D<br />

Application Issues<br />

Location and Presentation of the DOI<br />

Representation to End Users<br />

Using <strong>DOIs</strong> in HTML pages requires decisions as to how the <strong>DOIs</strong> will appear on the pages.<br />

The DOI will be represented as a normal hypertext link, so a word or phrase or title can be<br />

designated to appear in a specific color to signal that it is a DOI that will result in an action<br />

when "clicked." In many of the Prototype applications of the DOI, copyright holders chose to<br />

signal the use of <strong>DOIs</strong> by providing an icon or a distinctive button that would tell the user that<br />

the link was in fact a DOI and could be trusted. But for design purposes this is not necessary.<br />

Conventional hypertext links will work as well. Encoding issues complicate presentation to<br />

users (see Appendix D for encoding requirements). The idea is that in most cases the user<br />

should not need to see the DOI or could cut and paste. However, it is inevitable that in some<br />

cases <strong>DOIs</strong> will be printed and read and rekeyed by humans.<br />

Directories<br />

An identifier is created by the Registrant who registers it with the appropriate directory. The<br />

directory maintains the current location (e.g., a Uniform Resource Locator, or URL) of the<br />

digital object.<br />

Administration of the DOI<br />

A Registration Agency assigns the DOI Prefix and the DOI Registrant determines the Suffix.<br />

The components of the DOI make it unique in the world and over time, and also allow the DOI<br />

to be assigned by the content owner locally. Once a DOI is assigned to an object it will never<br />

be reassigned. There is no limit to the number of objects that can be identified by <strong>DOIs</strong>, nor is<br />

there a minimum size or characteristic of an object. A DOI may identify a poem, an abstract or<br />

an entry in a reference work as well as an article or a book, a chapter within a book or an<br />

image within the chapter.<br />

In determining what objects should be assigned <strong>DOIs</strong>, the registrant should consider what<br />

objects are likely to be individually bought, sold and electronically downloaded or retrieved.<br />

Encoding Requirements<br />

9


This appendix is not part of the <strong>Digital</strong> <strong>Object</strong> <strong>Identifier</strong> (DOI), ANSI/NISO Z39.xx-199x. It is included for<br />

information only.<br />

There are special encoding requirements when a <strong>Digital</strong> <strong>Object</strong> <strong>Identifier</strong> is used with certain<br />

other identifiers. The syntax for Uniform Resource <strong>Identifier</strong>s (URIs) is very restrictive. A<br />

URI is a Uniform Resource Locator (URL) or a Uniform Resource Name (URN). The DOI<br />

operates within the URL system and conforms to the URN specification.<br />

Encoding Characters<br />

Since URL syntax conventions are more restrictive than DOI conventions, hexadecimal (%)<br />

encoding must be used for characters in a DOI that are not allowed, or have other meanings, in<br />

URLs. Hex encoding, or escaping characters, consists of substituting for the given character its<br />

hexadecimal value preceded by percent. Thus, # becomes %23 and<br />

http://dx.doi.org/10.1000/456#789 is encoded as http://dx.doi.org/10.1000/456%23789. The<br />

browser does not now encounter the bare #, which it would normally treat as the end of the<br />

URL and the start of a fragment, and so sends the entire string off to the DOI network of<br />

servers for resolution, instead of stopping at the #. The DOI itself does not change, merely its<br />

representation in a URL. A DOI that has been encoded is decoded before being sent to the<br />

DOI Registry. At the moment the decoding is handled by the proxy server dx.doi.org. Only<br />

unencoded <strong>DOIs</strong> are stored in the DOI Registry database.<br />

DOI creators and maintainers need to keep the following rules in mind:<br />

There are no character restrictions for DOI number strings per se. When <strong>DOIs</strong> are<br />

embedded in URLs, they must follow the URL syntax conventions, but the same <strong>DOIs</strong><br />

need not follow those conventions in other contexts, e.g. inventory databases, DOI<br />

Registry.<br />

Always present <strong>DOIs</strong> in URLs in their encoded form to end users.<br />

The percent character (%) must always be hex encoded (%25) in any web form, batch<br />

input, or URL. Other excluded characters must always be hex encoded in URLs, but do<br />

not need to be encoded when registering the <strong>DOIs</strong> through the web forms or batch mode.<br />

Mandatory/Recommended Encoding<br />

Table 1 shows a list of characters that are not allowed within the URL syntax: these native<br />

characters must therefore be replaced by hex-encoding. Table 2 shows additional characters<br />

where it is recommended that characters be replaced by hex-encoding. The distinction between<br />

Tables 1 and 2 is between practical experience with current web browsers and the more formal<br />

specification of URL syntax. The web is still a relatively new environment and both the formal<br />

10


specifications and web browser implementations are something of a moving target. It can say<br />

with certainty that the characters in Table 1 must be hex encoded. It cannot say with certainty<br />

that the characters in Table 2 must or must not be hex encoded, only that the formal<br />

specifications recommend it but no recent set of browsers require it.<br />

The tables are formatted to show the given character, the encoding required by the DOI system<br />

for input, the encoding required for use of a DOI within a URL, and finally what is stored. The<br />

| symbol is used to show a series of acceptable alternatives, e.g., the fact that # can be entered<br />

into a web form as either # or %23 is shown as # | %23. Note that all the given characters must<br />

be hex encoded within URLs but that only %, because of its use as marking the start of a hex<br />

encoding, must be hex encoded in the various DOI forms.<br />

11


Table 1 – Mandatory Encoding<br />

Character Input URLs DOI Database<br />

Web Form Batch<br />

# # | %23 # | %23 %23 #<br />

% %25 %25 %25 %<br />

SP SP | %20 SP | %20 %20 SP<br />

" " | %22 " | %22 " | %22 "<br />

Table 2 – Recommended Encoding<br />

Character Input URLs DOI Database<br />

Web Form Batch<br />

< > | %62 > | %62 %62 ><br />

{ { | %123 { | %123 %123 {<br />

} } | %125 } | %125 %125 }<br />

^ ^ | %94 ^ | %94 %94 ^<br />

[ [ | %91 [ | %91 %91 [<br />

] ] | %93 ] | %93 %93 ]<br />

` ` | %96 ` | %96 %96 `<br />

| "|" | %124 "|"| %124 %124 |<br />

\ \ | %92 \ | %92 %92 \<br />

12

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!