From n² wiki

When representing identifiers in RDF it's preferable to use a URI so that the identifier can be easily disambiguated. The following table lists a number of commonly encountered bibliographic identifiers and their commonly accepted URI schemes

!Identifier Type	URI Example
ARK (Archival Resource Key)	http://loc.gov/ark:/12025/654xz321
DOI (Digital Object Identifier)	http://dx.doi.org/10.1000/182 or info:doi/
Handle	http://hdl.handle.net/4263537/4069 or info:hdl/
ISBN (International Standard Book Number)	urn:isbn:1565921496
ISSN (International Standard Serial Number)	urn:issn:13613200
SICI (Serial Item and Contribution Identifier)	info:sici/1046-8188(199501)13:1%3C69:FTTHBI%3E2.0.TX;2-4
Library of Congress Control Number	info:lccn/ (see http://www.loc.gov/marc/lccn-namespace.html#syntax)
OCLC Worldcat Control Numbers	info:oclcnum/3393962
RLG Database Record identifiers	info:rlgid/
National Bibliography Number	??
ISRC (International Standard Recording Code)	??
UPC (Universal Product Code)	??
ISMN (International Standard Music Number)	??
EAN (International Article Number)	??
Fingerprint	??
Publisher number (commonly used for audio and video recordings)	??
CODEN (used for chemical journal articles)	??
Musical Incipits (only used by a few specialist libraries)	??
System Control Number (unique id for a record from a given institution)	??

[edit] Sources

• Guidelines for using resource identifiers in Dublin Core metadata and IEEE LOM
• Registered "info" URI Schemes
• Using info URIs with RDF
• Official IANA Registry of URN Namespaces
• RFC2288: Using Existing Bibliographic Identifiers as Uniform Resource Names
• RFC3187: Using International Standard Book Numbers as Uniform Resource Names
• RFC3044: Using The ISSN (International Serial Standard Number) as URN (Uniform Resource Names) within an ISSN-URN Namespace
• RFC4452: The "info" URI Scheme for Information Assets with Identifiers in Public Namespaces

---