To support decoupling Oaisys' need for OAI:DC & OAI:ETDMS serializations of specific Jupiter models, and decoupling Jupiter from needing to know the specifics about serializaiton formats, ActsAsRDFable (which is increasing misnamed, so this will probably change soon) is gaining support for generating serializations of these formats.
Contents
Adds a formats parameter to the model-level acts_as_rdfable DSL, so that models can indicate which serializations they intend to support.
Adds a top-level Serialization abstraction that handles registration of models and the formats they intend to serialize into, obtaining presenters specific to a metadata format for registered classes, and renderers that handle the low-level detains of generating serializations of a presented model.
Adds an OAI:DC renderer
Adds an OAI:ETDMS renderer
Not Included
Support for querying all registered classes (necessary for the remaining optional ListMetadataFormats verb behaviour in Oaisys)
N3 renderer (next-up)
removal of the add_annotation_bindings! hack (will happen when the N3 renderer lands)
tests (waiting to see if N3 support and the corresponding refactor of the code in Jupiter requires further changes to the API before I set it in stone by building tests around it)
Context
To support decoupling Oaisys' need for OAI:DC & OAI:ETDMS serializations of specific Jupiter models, and decoupling Jupiter from needing to know the specifics about serializaiton formats, ActsAsRDFable (which is increasing misnamed, so this will probably change soon) is gaining support for generating serializations of these formats.
Contents
acts_as_rdfableDSL, so that models can indicate which serializations they intend to support.Not Included
add_annotation_bindings!hack (will happen when the N3 renderer lands)