info:sid/localhost:CollectionRegistryFramework:RfaOverview info:sid/localhost:CollectionRegistryFramework CollectionRegistryFramework http://alcme.oclc.org:80/wikid/search/WikiDb.localhost RfaOverview display Registry Framework Information about the Registry Framework userAssigned mailto:jyoung@oclc.org no info:sid/localhost:CollectionSimpleSchemas:wiki info:sid/localhost:CollectionExternalSchemas:xhtml info:sid/localhost:CollectionExternalSchemas:xhtml 1.1 1 c23qm8 300 http://www.oclc.org/schemas/WikiRepository xml http://alcme.oclc.org:80/wikid/docs/WikiRepository info:sid/localhost:CollectionRegistryFramework:RfaOverview anonymous CollectionRegistryFramework 2007/05/01/12 inf_3asid_2flocalhost_3aCollectionRegistryFramework_3aRfaOverview_5f20070501121029389 text/xml CollectionRegistryFramework:RfaOverview 2007-05-01 2007-05-01 1 1.1 repos.hasDate = "hasdate" and oai.identifier exact "info:sid/localhost:CollectionRegistryFramework:RfaOverview" cql.any = huh? 1 1 xml default 2007-05-01 http://alcme.oclc.org:80/wikid/docs/WikiRepository/2007/05/01/12/inf_3asid_2flocalhost_3aCollectionRegistryFramework_3aRfaOverview_5f20070501121029389 = Registry Framework Architecure (RFA) Conceptual Overview = The best available demonstration of the Registry Framework is currently OCLC’s Institution Registry (http://worldcat.org/registry/Institutions''''''). The Registry Framework is a system for publishing, maintaining, and accessing “collections of items” on the web. The general idea is that if you have a collection of digital items, you can make it accessible through a Registry Framework installation by mounting it as an SRU database with this minimal configuration: 1 An identifier index (taken from the identifier field in the Admin''''''Data record) 1 Two XML delivery record formats: *** Content (http://worldcat.org/registry/xsd/content.xsd'''''') **** The native content byte array (Base64-encoded to satisfy SRU’s XML bias) **** Content-Type *** Admin''''''Data (http://worldcat.org/registry/xsd/adminData.xsd'''''') **** The item's URI- info'''''':rfa/localhost/{collectionLabel}/{itemLabel} **** A brief results label **** Application-specific data (optional) The Registry Framework doesn’t care how this data is actually produced or stored, as long as it can be accessed through this interface. Given such a configuration (whether local or remote), the collection can be “installed” in a deployed instance of the Registry Framework by registering the baseURL in a special bootstrap collection called the “Collection Collection”. Assuming nothing more than this, the Registry Framework is able to provide a fair number of general-purpose services to access the collection. Additional services can be enabled by adding other assumptions. For example, OAI-PMH harvesting can be enabled by adding a datestamp index to the SRU service. RSS access can be enabled by adding a sort on the datestamp index in SRU. Online updates (including HTML FORM submittals) can be enabled by adding an SRU Update interface that recognizes a known deposit schema (http://worldcat.org/registry/xsd/iwsaDeposit.xsd''''''). And so on. Sets of assumptions and corresponding services should be modular so that when the Registry Framework is made available as open-source, people can share sets of features as jar files that others can install by dropping onto the classpath.

Registry Framework Architecure (RFA) Conceptual Overview

The best available demonstration of the Registry Framework is currently OCLC’s Institution Registry (http://worldcat.org/registry/Institutions).

The Registry Framework is a system for publishing, maintaining, and accessing “collections of items” on the web. The general idea is that if you have a collection of digital items, you can make it accessible through a Registry Framework installation by mounting it as an SRU database with this minimal configuration:
  1. An identifier index (taken from the identifier field in the AdminData record)
  2. Two XML delivery record formats:
The Registry Framework doesn’t care how this data is actually produced or stored, as long as it can be accessed through this interface. Given such a configuration (whether local or remote), the collection can be “installed” in a deployed instance of the Registry Framework by registering the baseURL in a special bootstrap collection called the “Collection Collection”.

Assuming nothing more than this, the Registry Framework is able to provide a fair number of general-purpose services to access the collection. Additional services can be enabled by adding other assumptions. For example, OAI-PMH harvesting can be enabled by adding a datestamp index to the SRU service. RSS access can be enabled by adding a sort on the datestamp index in SRU. Online updates (including HTML FORM submittals) can be enabled by adding an SRU Update interface that recognizes a known deposit schema (http://worldcat.org/registry/xsd/iwsaDeposit.xsd). And so on. Sets of assumptions and corresponding services should be modular so that when the Registry Framework is made available as open-source, people can share sets of features as jar files that others can install by dropping onto the classpath.