1. Digital Object Identifier doi> Norman Paskin The International DOI Foundation W3C DRM workshop January 22/23 2001

2. Content meets digital infrastructure Digital Object Identifier (DOI), from International DOI Foundation: a member of W3C Topics covered: –issues –DOI doi> Perspective

3. See position paper for fuller details During 3 years of development, we’ve encountered practical issues, in developing an identifier system within an architecture which recognises rights Key influences: INDECS analysis (see Godfrey Rust’s paper) –and implementations of it like our own, ONIX, etc Digital Object infrastructure (see Larry Lannom’s paper) –and implementations of it such as Handle IDF Position paper doi>

4. DRM = Digital Management of Rights not Management of Digital Rights DOI = Digital Identifier of “objects” (Creations, entities) We must be able to deal with all relevant entities because: practical rights management encompasses both digital and non-digital rights The Web is not the end point of evolution Maximal extensibility is required doi>

5. Manuscript mss #ABC123 Not only digital things... paper journal/volume/page ISBN, ISSN, etc. doi>

6. MS Vol/page; ISBN; SICI, etc URL “intangible abstraction” “intangible abstraction” ISTC?

7. Transactions require automation Automation requires disambiguity –e.g “book” Knowledge representation: “what is a book, work, etc?”  Practical: “What is a book in the context of…?” (namespaces, applications)  – every entity should be uniquely defined within an identified namespace (indecs) Disambiguity is key doi>

8. For the content communities: –indecs analysis Practical sector implementations: –ONIX; SMPTE; MPEG21... Interoperable principles  There won’t be ONE model Criteria... Strong underlying data model Multi-purpose Extensive, structured vocabulary Commercial critical mass Outward-looking doi>

9. Any item of descriptive metadata could be used in a rights transaction Cannot leave “rights” out of your architecture because it’s too difficult But it does not need to be (and cannot be) complete - in fact it must be extensible Corollary: simple resource discovery descriptions are insufficient (i.e. limited) “Description” and “Rights” inseparable doi>

10. Every element of description must be precise ISO language, territory, currency, time Others needed: contributor codes, derivation types, forms, measures… add: preferentially dumb identifiers –do not hard wire two data together Unique identification is essential doi>

11. All metadata is just a view In each of role, different IDs and attributes. True for any Creation in an application doi> A manuscript The abstract work A draft A (class of) physical copy in a publication A (class of) digital copy (not in a publication) A (class of) digital copy in a publication A (class of) digital format A specific digital copy A (class of) paper copy A specific paper copy An edition A reprint A translation etc…and many combinations of the above E.g. an identifier for a published article may refer to...

12. A name is a location in a defined namespace –so “all names are locations” is trivially true Practical needs for “content” –multiple instances –persistence in the face of valid change –management of entities other than digital files including classes, abstract rights –de-referencing, resolution Contextualisation –e.g. “appropriate copy”; IETF URN, URI, URL: ? –W3C URI activity should be consistent Names and locations doi>

13. Standards bodies, collectives? –EAN/UPC bar code system –ISBN system –URI scheme etc. have different methods, governance There won’t be one place –e.g. Directory of Parties by... –e.g. ontology of “scientific article” by... “By the people for the people” –relevant tasks should be done closest to the community of interest Who should be responsible? doi>

14. Media convergence = people convergence Formalisms are essential in their place –but must be explained the danger of jargon and “common assumptions” it’s not just the Web. Need for explanation doi>

15. Identifiers enable us to manage content Physical world: –EAN/UPC Bar codes; ISBN, ISSN, ISMN, SICI, etc –good systems for publishers Digital world: ? URL? –poor systems for publishers –how to use existing identifier systems? DOI Background doi>

16. International DOI Foundation: founded 1998 –following demonstration of prototype in 1997 Not-for-profit; paid membership support –similarities to W3C; Bar code system Open to all interested parties Democratic board elected from members Full time staff 45+ organisations (growing) –Content owners (text publishers, music, etc ) –Technology companies –Content intermediaries (etc) DOI - organisation doi>

17. Establish a way of identifying content in the digital environment –actionable identifier Which can be the basis of rights management –extensible; can be developed further DOI: aim doi>

18. POLICIES Any form of identifier NUMBERING DESCRIPTION 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 pieces of current data doi> extensible

19. Conclusion: DOI “DOI is the most ambitious identifier in the history of the world”. (G. Rust 1998) But now several things are becoming established... …it has a persistent, granular, flexible, unique identifier which can be a “wrapper” for other IDs. Not competitive - enhances legacy identifiers’ functionality in d- commerce. DOI as the integrating digital identifier?...a strong, established metadata model and vocabulary. …a controlled but flexible development structure. …it does not confuse names with addresses. …allows multiple, standardised automated actions. Nothing else comes close... doi>

20. n.paskin@doi.org http://www.doi.org doi> Norman Paskin The International DOI Foundation