DigitalKoans

The National Information Standards Organization and the Association of Learned and Professional Society Publishers have published Recommended Practice Journal Article Versions (JAV): Recommendations of the NISO/ALPSP JAV Technical Working Group.

Here's an excerpt from the press release:

The publication is designed to provide a simple, practical way of describing the versions of scholarly journal articles that typically appear online before, during, and after formal journal publication. . . .

"Static, single copies of research papers that are essentially facsimiles of a single, unambiguously identified printed document are a thing of the past," stated Bernard Rous, Deputy Director of Publications at the Association for Computing Machinery (ACM) and Co-Chair of the JAV Working Group. "Changes in the way we create, produce, and store articles lead to multiple versions that are often all discovered together through web searches. Our working group addressed the consequent problem: how to identify the versions retrieved and clarify the relationships among them." . . .

Several variables were considered as possible dimensions to identify a particular article version:

• Time: from first draft to latest version
• Added Value: from rough draft to polished publication
• Manifestation/Rendition: different document formats and layouts
• Siblings: multiple mappings between technical reports, conference papers, lectures, journal articles, review articles, etc.
• Stakeholders: author, editor, referee, publisher, librarian, reader, funding organization

Components of the JAV Recommended Practice include a narrative that explains the project background and rationale for recommended terms and definitions, and appendices that cover "Graphical Representation of Journal Article Versions and Relationships with Formal and Grey Literature; Assumptions, Primary Challenges, and Best Practices," use cases, and comments from JAV Review Group on recommendations received on an earlier draft document.

JISC has published Metadata for Digital Libraries: State of the Art and Future Directions.

Here's an excerpt from the "Executive Summary":

At a time when digitization technology has become well established in library operations, the need for a degree of standardization of metadata practices has become more acute, in order to ensure digital libraries the degree of interoperability long established in traditional libraries. The complex metadata requirements of digital objects, which include descriptive, administrative and structural metadata, have so far mitigated against the emergence of a single standard. However, a set of already existing standards, all based on XML architectures, can be combined to produce a coherent, integrated metadata strategy.

An overall framework for a digital object's metadata can be provided by either METS or DIDL, although the wider acceptance of the former within the library community makes it the preferred choice. Descriptive metadata can be handled by either Dublin Core or the more sophisticated MODS standard. Technical metadata, which is contingent on the type of files that make up a digital object, is covered by such standards as MIX (still images), AUDIOMD (audio files), VIDEOMD or PBCORE (video) and TEI Headers (texts). Rights management may be handled by the METS Rights schema or by more complex schemes such as XrML or ODRL. Preservation metadata is best handled by the four schemas that make up the PREMIS standard.

Integrating these standards using the XML namespace mechanism is straightforward technically although some problems can arise with namespaces that are defined with different URIs, or as a result of duplications and consequent redundancies between schemas: these are best resolved by best practice guidelines, several of which are currently under construction.

The next ten years are likely to see further degrees of metadata integration, probably with the consolidation of these multiple standards into a single schema. The digital library community will also work towards firmer standards for metadata content (analogous to AACR2), and software developers will increasingly adopt these standards. The digital library user will benefit from developments in enhanced federated searching and consolidated digital collections. The same developments are likely to take place in the archives and museums sectors, although the different metadata traditions that apply here are likely to make the form they take somewhat different.

At a March 3rd meeting at the Johns Hopkins University, the Open Archives Initiative (OAI) introduced the Object Reuse and Exchange (ORE) specifications. The ORE Specification and User Guide was released the prior day.

Here's an excerpt from the press release about the meeting:

The ORE specifications are developed in response to a significant challenge that has emerged in eScholarship. In contrast to the paper publications of traditional scholarship, or even their digital counterparts, the artifacts of eScholarship are complex aggregations. These aggregations consist of multiple resources with varying media types, semantics types, network locations, and intra- and inter-relationships. The future scholarly communication, research, and higher education infrastructure requires standardized approaches to identify, describe, and exchange these new outputs of scholarship.

The ORE specifications address this challenge with the ORE data model that defines how to associate an identifier, a URI, with aggregations of web resources. By referring to these identifiers, aggregations can then be linked to, cited, and described with metadata, in the same manner as any web resource. The ORE data model also makes it possible to describe the structure and semantics of these aggregations. The ORE specifications define how these descriptions can then be packaged in the XML-based Atom syndication format or in RDF/XML, making them available to a variety of applications.

In addition to their utility in eScholarship, the ORE specifications also apply to our everyday web use where we often encounter aggregations such as multi-page HTML documents, and collections of multi-format images on sites like flickr. OAI-ORE descriptions of these aggregations can be used to improve search engine behavior, provide input for browser-based navigation tools, and develop automated web services to analyze and preserve this information.

Read more about it at "The Vision of ORE."

The Digital Preservation Coalition has published JPEG 2000—A Practical Digital Preservation Standard?.

Here's an excerpt from the "Executive Summary":

With JPEG 2000, an application can access and decode only as much of the compressed image as needed to perform the task at hand. This means a viewer, for example, can open a gigapixel image almost instantly by retrieving and decompressing a low resolution, display-sized image from the JPEG 2000 codestream.

JPEG 2000 also improves a user’s ability to interact with an image. The zoom, pan, and rotate operations that users increasingly expect in networked image systems are performed dynamically by accessing and decompressing just those parts of the JPEG 2000 codestream containing the compressed image data for the region of interest. The JPEG 2000 data can be either converted to JPEG and delivered for viewing with a standard image browser or delivered to a native JPEG 2000 viewer using the JPIP client-server protocol, developed to support the JPEG 2000 feature set.

Using a single JPEG 2000 master to satisfy user requests for dynamic viewing reduces storage costs and management overhead by eliminating the need to maintain multiple derivatives in a repository.

Beyond image access and distribution, JPEG 2000 is being used increasingly as a repository and archival image format. What is remarkable is that many repositories are storing “visually lossless” JPEG 2000 files: the compression is lossy and irreversible but the artefacts are not noticeable and do not interfere with the performance of applications. Compared to uncompressed TIFF, visually lossless JPEG 2000 compression can reduce the amount of storage by an order of magnitude or more.

The National Information Standards Organization has released SERU: A Shared Electronic Resource Understanding. The document "codifies best practices for the sale of e-resources without license agreements."

Here's an excerpt from the press release:

SERU offers publishers and librarians the opportunity to save both the time and the costs associated with a negotiated and signed license agreement by agreeing to operate within a framework of shared understanding and good faith.

Publication of SERU follows a trial-use period of June through December 2007, during which time librarians and publishers reported—all positively—on their experiences using the draft document. . . .

The SERU Working Group was launched in late 2006 following the recommendation of participants in a meeting exploring opportunities to reduce the use of licensing agreements. The 2006 meeting was sponsored by ARL, NISO, the Association of Learned and Professional Society Publishers (ALPSP), the Scholarly Publishing and Academic Resources Coalition (SPARC), and the Society for Scholarly Publishing (SSP). More information about the SERU Working Group, including FAQs and an electronic mailing list, can be found at http://www.niso.org/committees/seru/.

The Open Archives Initiative Object Reuse and Exchange has released an alpha version of the ORE Specification and User Guide. Comments can be made on the OAI-ORE discussion group or via email to ore@openarchives.org.

Here's an excerpt from the introduction:

The World Wide Web is built upon the notion of atomic units of information called resources that are identified with URIs such as http://www.openarchives.org/ore/0.1/toc (this page). In addition to these atomic units, aggregations of resources are often units of information in their own right. . . .

A mechanism to associate identities with these aggregations and describe them in a machine-readable manner would make them visible to Web agents, both humans and machines. This could be useful for a number of applications and contexts. For example:

• Crawler-based search engines could use such descriptions to index information and provide search results sets at the granularity of the aggregations rather than their individual parts.
• Browsers could leverage them to provide users with navigation aids for the aggregated resources, in the same manner that machine-readable site maps provide navigation clues for crawlers.
• Other automated agents such as preservation systems could use these descriptions as guides to understand a "whole document" and determine the best preservation strategy.
• Systems that mine and analyze networked information for citation analysis/bibliometrics could achieve better accuracy with knowledge of aggregation structure contained in these descriptions.
• These machine-readable descriptions could provide the foundation for advanced scholarly communication systems that allow the flexible reuse and refactoring of rich scholarly artifacts and their components [Value Chains].

The International Organization for Standardization (ISO) has approved Adobe PDF (Portable Document Format) 1.7 as the ISO 32000 standard (DIS). Comments about the new standard will be addressed early next year, and they will either be resolved, followed by the publication of a revision of the standard, or the DIS standard will become a Final Draft International Standard (FDIS), subject to a two-month vote.

Read more about it at: "Adobe's PDF Now an ISO Standard" and "PDF Approved as International Standard."

The LITA Standards Interest Group has established a mailing list: lita-stand@ala.org.

EDItEUR has released "ONIX for Serials Coverage Statement Draft Release 0.9 (june 2007)" for comment through September 2007.

Here’s an excerpt from the draft’s Web page:

ONIX for Serials Coverage Statement is an XML structure capable of carrying simple or complex statements of holdings of serial resources, in paper or electronic form, to be included in ONIX for Serials messages for a variety of applications; for example, to express:

• The holdings of a particular serial version by a library
• The coverage of a particular serial version supplied by an online content hosting system
• The coverage of a particular serial version included in a subscription or offering

EDItEUR has also released "SOH: Serials Online Holdings Release1.1 (Draft June 2007)" for comment.