OAIS mapping for IUE processing software
http://example.org/archive/other-representation-information-0531bcde
Class-level correspondences (from the bridging ontology)
rico:Record
| skos:broadMatch | im:InformationObject | im:InformationObject ('A Data Object together with its Representation Information') is broader than rico:Record: it does not distinguish a single Record from a RecordPart or a RecordSet, and it bundles in an explicit Representation Information object that a bare rico:Record does not itself carry (see the RepresentationInformation gap noted below). |
rico:OtherRepresentationInformation
No bridge mapping declared for this class.
Note — a deliberate gap:
RiC-O v1.1 defines no class corresponding to OAIS Representation Information (the structure/semantic information needed to render a Data Object's bits meaningful). RiC-O instead scatters partial, non-bundled coverage of this ground across typed properties of rico:Instantiation: rico:hasRepresentationType, rico:hasDocumentaryFormType, rico:hasCarrierType, rico:hasProductionTechniqueType, rico:technicalCharacteristics (see its own relatedMatch to im:OtherRepresentationInformation below), and the free-text rico:qualityOfRepresentationNote. None of these constitute a class that could stand in an equivalentClass, closeMatch, or broadMatch relation to im:RepresentationInformation; they are individual attributes rather than a bundled Structure/Semantic Representation Information object (im:StructureRepresentationInformation / im:SemanticRepresentationInformation). Institutions needing to carry full Representation Information in a RiC-O graph should extend RiC-O locally, e.g. with a bridge-defined subclass of rico:Thing, or attach it as an external (non-RiC-O) resource linked from the Instantiation.
Linked OAIS structural description
This resource has no bridge:hasOAISCounterpart individual linked in the data graph, so there is no OAIS-side structure to walk — only the class-level mapping above applies.