1. Reston, September 19 2000 doi> Workshop: future plans and directions for DOI

2. 2 Welcome First workshop since full implementation 37 people registered Mix of IDF members, prefix holders, others Flexible agenda, open discussion

3. 3 Documents See www.doi.org for DOI Handbook CD ROM (in folder) IDF Annual Report 2000 Indecs document (re metadata framework) Further information

4. 4 Documents Also available here for consultation : DOI Handbook (printed) Metadata background: BioImage, ONIX, EPICS Recent articles etc all available (or linked) from www.doi.org

5. 5 Agenda DOI update /overviewNorman Metadata issues: designing DOI genres - coffee break - Resolution issuesLarry - lunch - Whats needed (all) How to proceed Prototypes and practical next steps

6. 6 DOI update : review of progress What has been achieved? Where are we heading?

7. 7 Review of progress Consistency: no major U turns Progress: design and implementation Engagement: wider and deeper –metadata discussions –identifier issues Development and Product –The road ahead analogy

8. 8 Standards tracking Standards tracking Full implementation Full implementation Initial implementation Initial implementation DOI: development in three tracks Single redirection Metadata W3C, WIPO, NISO, ISO, etc, other initiatives Multiple resolution A continuing development activity

9. 9 Review Components of the DOI

10. 10 A number (or name) –assign a number to something –(compare: telephone number)

11. 11 A number (or name) –assign a number to something –(compare: telephone number) A description –say what the number is assigned to –(compare: directory entry)

12. 12 A number (or name) –assign a number to something –(compare: telephone number) A description –say what the number is assigned to –(compare: directory entry) An action –make the number able to do something –(compare: the telephone system)

13. 13 A number (or name) –assign a number to something –(compare: telephone number) A description –say what the number is assigned to –(compare: directory entry) An action –make the number able to do something –(compare: the telephone system) Policies –how to get a phone number; billing –(compare: social /business structures)

14. 14 POLICIES Syntax 10.1234/5678 NUMBERING DESCRIPTION Metadata Pieces of data which describe uniquely that which is identified Resolution System able to link the number to something useful ACTION

15. 15 Syntax 10.1234/5678 NUMBERING DESCRIPTION Metadata Pieces of data which describe uniquely that which is identified Resolution System able to link the number to something useful ACTION

16. 16 Syntax 10.1234/5678 NUMBERING Resolution System able to link the number to something useful ACTION

17. 17 Syntax 10.1234/5678 NUMBERING Resolution Link to one URL only ACTION

18. 18 POLICIES Any form of identifier ENUMERATION DESCRIPTION framework allows a DOI to describe any form of intellectual property, at any level of granularity RESOLUTION Handle System allows a DOI to resolve to any and multiple pieces of current data doi>

19. 19 Progress An extensible infrastructure, architecture –a firm basis for building consistent, reliable, systems More members, more prefixes, more DOIs

20. 20 Progress a major implementation other implementations near more signs of influence: –W3C; ISTC; E-Books clear vision: conceptual integrity (Brookes)

21. 21 Potential pitfalls STM - identified with text and with STM esp? Rigorous approach - theoretical? Technical - not understandable? Anglo-American - not international? Key individuals - in depth support? Open development - not yet ready? Unifying - fragmentation?

22. 22 A note on time frame If this stuff wasnt difficult we wouldnt be doing it The first actionable identifier (all the components) Oct 1997 concept launched (simple form) March 1998 IDF launched; two years of work Some comparisons: –URN: 1991 - ; DC: 1994- ; FRBR: 1992-98; –W3C: 1994-; IMS: 1996-; RosettaNet 1998-

23. 23 Applications Crossref (PILA) –Crossref is the first practical demonstration of why the DOI is important, and how it can be used to improve Web publishing. Though it was implemented by journal publishers…the concept could be applied to other genres… (Seybold Report, 14 June) –see IDF E-Citations paper * Images –BioImage; and extension?

24. 24 Applications E-Books - working with: ONIX/EPICS; OEB; EBX and AAP E- Books standards activity (David Martin) - community is diffuse and hence applications as yet undefined: eBooks (ISBN?); components; links? Instructional materials (NICEM) Music industry Others? E-News; Legal; Patents; Grey literature Applications will drive deployment

25. 25 Applications and metadata approach vindicated –See recent papers by Carl Lagoze; Priscilla Caplan practical implementation of through ONIX/EPICS dictionary –extension/collaboration with other areas e.g.music/video; SMPTE; MerchEnt; etc documentation in detail: –Handbook (section 5, and appendices 2&5) –More detailed template for genres coming shortly mechanism for metadata (e.g. metadata@DOI 123…) –XML declarations; schemas

26. 26 Commercial implementation: deployment Technology is (relatively) easy Basis for Deployment outlined (end of 1999) Initial financial model (June): simple First and second wave of interested parties Terms document Applications will drive deployment (genres etc)

27. 27 Extensibility: metadata framework more on this in next session rights transactions see latest indecs framework document role of XrML to be investigated DOI-R proposed by analogy to DOI-X scope problems now looking at more defined prototype with FBF Rights is not just another application

28. 28 Extensibility: Digital Object Architecure Digital Object Architecture includes Handle, repositories, etc. –see papers by Kahn et al * multiple resolution workflow tools repository: –stated operations = DOI services? –genre definitions, schema, etc? public key infrastructure

29. 29 Documentation Review 1999: –DOI Current Status and Outlook May 1999 Review 2000 Handbook (DOI 10.1000/182) Papers –DOI: implementing a standard …. –one to many –etc

30. 30 Marketing W3C approach up to now: –dont promise what cant deliver; show by example CD-ROM marks start of next wave –outreach and applications

31. 31 Some other key activities (1) Handle: –New release of second major version –Handle infrastructure improved –CNRI plans for Handle –Browser support: Mozilla? Metadata, rights: –ONIX/EPICS etc implementing indecs –XrML W3C: – URI Activity –intellectual property on the web workshop

32. 32 Some other key activities (2) Other intellectual property activities: –e.g. MPEG-21 as possible focus for cIDF, SMPTE, etc. Legacy identifiers (ISBN, ISSN, etc) –common issues for identifiers Work with new identifiers (e.g. ISTC; E-books) Major issue: mindshare support for standards –avoid fragmentation

33. 33 Your involvement Workshops Prototypes New working groups (E mail lists) proposed: –Handle/resolution –Identifiers/metadata –Information interchange

34. 34 The future genres: articulation and development (Hdbk, Appx 2) –metadata declarations multiple resolution: services –Service@DOI:10.1000/182 –e.g. Rights@DOI:10.1000/182 (YBP, 1998) –e.g Metadata@….. rights outreach identifier/ metadata/ standards/ i.p. community

35. 35 Multiple resolution: services To be investigated: Metadata pointer for all DOIs (kernel) XML schema for genre metadata List of other desired services and policies Registry of data types = service (and tools) Registry of genres Tools to make all this easier

36. 36 Review of progress Consistency: no major U turns Progress: development and implementation Conceptual integrity Practical results; and development More to be done on advocacy More to be done on applications, developments - this workshop

37. Reston, September 19 2000 doi> Workshop: future plans and directions for DOI