Future Functionality and CrossRef Policy Special Member Meeting December 4th, 2001

2 We want your input Your survey responses will influence future directions and developments Join the Technical Working Group, which meets monthly via teleconference –Implementation –DTD –Parameter passing

3 Directives from last year’s member meeting Citation linking for conference proceedings and major reference works – nearing completion Inexact matching of queries – in process as part of system rewrite Parameter passing – under development

4 More enhancements underway Localized linking – nearing completion Multiple resolution – in process Cross-publisher search – under consideration

5 Preliminary survey results: Three most highly rated initiatives 1. Software toolkit to facilitate DOI deposit and retrieval - 86% of members support 2. Open up full membership/deposit to non- traditional publishers of scholarly content - 77% of members support Register archival content for linking through collections such as JSTOR - 73% of members support

6 Two priorities for Enhance support, documentation, and reporting to membership 2. Broaden membership (and revenue) base –Libraries with electronic archives of public domain content –Corporate technical reports –Government documents –Patents, standards –Dissertations –Special collections (JSTOR) with publisher cooperation

7 CrossRef XML Schema for Deposit of Books, Proceedings, and Journal Article Metadata

8 Rationale for new content types Members want to register conference proceedings and major reference works Another way to expand deposit base, hence increase revenue Extend linking connectivity throughout online scholarly publications Enable direct access to, and PPV sales of, conference papers and book chapters

9 Background Contracted Inera, a consulting company specializing in SGML and XML based solutions Conducted publisher survey and document analysis of conference proceedings and reference works Publisher meeting in NYC, July 2001 Decided on a unified schema for all content types

10 Why a unified deposit schema? To keep publisher deposit process simple by avoiding multiple input formats for citation metadata To make it easier for CrossRef to control versions and propagate changes to the schema Extensible to other new content types

11 Some key features DOIs can be assigned at the journal and issue level as well as the article level - important for the development of multiple resolution and capturing hierarchical information Captures more data because of the way in which conference papers and book chapters are cited –e.g., with title but no page numbers –robustness of data will us develop other services, such as reference editing/clean-up tools ONIX-compatible

12 Why not just use ONIX? Schedule: ONIX DTDs are still in development Little demand so far: Majority of members do not currently use ONIX Less is more: CrossRef has a well-defined application and only collects metadata for citation linking Simplicity: Our schema is simpler than the ONIX DTD, hence easier for all publishers to implement Data validation: A general-purpose DTD like ONIX creates more opportunity for error during the metadata submission process

13 CrossRef Support for ONIX Mapping of ONIX 2.0 elements to CrossRef elements/attributes We will provide documentation on how to use ONIX to deposit data with CrossRef CrossRef is a member of EDItEUR and is providing input on the development of ONIX-for-Serials

14 Current DTD will be left in place Intended to replace previous CrossRef journal DTD, but publishers may continue to submit journal metadata using the earlier DTD