Reston, September 19 2000

1. DOI Workshop: Future plans and progress Reston, September 19 2000 doi>

2. Metadata issues and DOI • First workshop since “full implementation” • 37 people registered • IDF members, prefix holders, others • Flexible agenda, open discussion

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. 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. Agenda • DOI update /overview - break - • Metadata issues: designing DOI genres - lunch - • Resolution issues - break - • Deployment issues • Whats needed; how to proceed; prototypes and practical next steps

6. DOI: Review of progress • What has been achieved? • Where are we heading?

7. DOI: 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. Standards tracking Full implementation Initial implementation DOI: development in three tracks W3C, WIPO, NISO, ISO, etc, other initiatives Metadata Single redirection Multiple resolution A continuing development activity

9. DOI: Review of progress • Components of the DOI

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

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

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

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

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

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

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

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

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

19. DOI: Review of progress • An extensible infrastructure, architecture • a firm basis for building consistent, reliable, systems • More members, more prefixes, more DOIs

20. DOI: Review of progress • a major implementation • other implementations near • more signs of influence: • W3C; ISTC; E-Books • clear vision: “conceptual integrity” (Brookes)

21. Advantages: and potential pitfalls • STM • Rigorous approach • Technical • Anglo-American • Key individuals • Open development • Unifying too identified with text,STM? “theoretical”? not understandable? not international? in depth support? not yet ready? fragmentation?

22. DOI: Time frame • “If this stuff wasn’t difficult we wouldn’t 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); HDL (1994-); W3C (1994-); IMS (1996-); RosettaNet (1998-)

23. DOI: 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. DOI: Applications (cont.) • E-Books - working with: ONIX/EPICS; OEB; EBX and AAP E-Books standards activity - community is diffuse and hence applications as yet undefined: eBooks (ISBN?); components; links? • Instructional materials (NICEM) • Music industry • Others? E-News; Legal information; Patents; “Grey literature”; etc. Applications will drive deployment

25. DOI: Applications and metadata • approach vindicated • See recent papers by Carl Lagoze; Priscilla Caplan • practical implementation of <indecs> 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. 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. 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. Extensibility: Digital Object Architecture • 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. 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. Marketing • “W3C approach” up to now: • don’t promise what can’t deliver; show by example • CD-ROM marks start of next wave • outreach and applications

31. Other key activities • Handle: • New release of second major version • Handle infrastructure improved • CNRI plans for Handle • Browser support: Mozilla, IE? • Metadata, rights: • ONIX/EPICS etc implementing indecs • XrML • W3C: • URI Activity • “intellectual property on the web” workshop

32. 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. Community involvement • Workshops • Prototypes • New working groups (E mail lists) proposed: • Handle/resolution • Identifiers/metadata • Information interchange

34. The future • genres: articulation and development • metadata declarations • multiple resolution: services • Service@DOI:10.1000/182 • e.g. Rights@DOI:10.1000/182 (YBP, 1998) • e.g Metadata@….. * Services will drive applications • rights * Rights services will drive killer apps • outreach to i.p. communities • commonality of identifier/ metadata/ i.p.issues communities

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. DOI: 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