Page Tree:

Child pages
  • Candidate Collections Interoperability Standards

This wiki space contains archival documentation of Project Bamboo, April 2008 - March 2013.

Skip to end of metadata
Go to start of metadata


Potentially Relevant Interoperability Standards, Protocols, Application Profiles, Best Practices

Metadata Schemes and Schemas (incomplete)

The following questions can be used to organize classes of metadata standards (i.e., what is the purpose of the standard?)

  1. What do we need to know about an object?
    (A separate issue, possibly relevant: standardized data dictionaries and vocabularies)
  2. How is that information encoded?
    • Record format/markup language
    • Metadata Wrappers

  3. How is that information transmitted and accessed?
    This is a gray zone: although not strictly metadata standards per se, many APIs also require that data be encoded in certain markup languages. Transformations come into play here.
  4. What do we need to know about a Collection? Relevant resources (putting this here as a placeholder until CI subgroup 1 forms its pages; 12/20/2010 Claire Stewart)
    1. Asset Action project (view and get stuff, object-specific? but can make assertions at the collection level, hopefully? about which actions are supported throughout)
    2. IESR collection description (mostly descriptive about a collection, but permits entry of OAI information, Z39.50 including location of ZeeRex explain file, indication that other methods like FTP, OpenURL, SRU, SRW, etc. are supported)
    3. RSLP collection description
    4. RIF-CS Registry Interchange Format - Collections and Services collection description
    5. Collection Description Specification , draft NISO Z39.91
  5. Making Collections Web Friendly (informal notes. Added by E. Kansa 1/7/11)
    1. In addition to the metadata standards etc. described above, there needs to be some emphasis placed on best-practices for Web-architecture. This means measures to promote interoperability / use of collections in the context of the open Web.Some things to consider:
      1. URL/URI design, linked data.
      2. Content negotiation, publication of multiple representations of resources (JSON, XML, etc.) to facilitate use with mobile devices, ebooks, mashups, etc.
      3. Other attributes of RESTful design.
    2. Serviced based on the Atom Syndication Format
      1. For data portability. Serialize query results as paged Atom-feeds. Useful for retrieving subsets of collections that may be of interest (one can then further annotate resources in such subsets according to whatever ontology is needed for a given research question)
      2. For data preservation / archiving. Digital libraries can crawl feeds to get lists of resources (and metadata about such resources) to archive.
  • No labels