OAIS mapping for CCSDS Meeting in COlorado Springs
http://example.org/archive/m365/f253c3cb/item/ccee9f8c7bc5d525ea58accb
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). |
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
Information Object / Content Information
http://example.org/archive/m365/f253c3cb/item/ccee9f8c7bc5d525ea58accb/ci
RiC-O description(s):
http://example.org/archive/m365/f253c3cb/item/ccee9f8c7bc5d525ea58accb
im:hasDataObject →
Digital Object
http://example.org/archive/m365/f253c3cb/item/ccee9f8c7bc5d525ea58accb/do/1
im:hasStorageLocation →
CCSDS-Meeting-in-COlorado-Springs.eml
https://archive-manager.oais.info/api/bits/8faf0685-c21f-4f07-b5ba-e8b84d8e97b2/CCSDS-Meeting-in-COlorado-Springs.eml
← im:hasStorageLocation (referenced by)
Digital Object
http://example.org/archive/m365/f253c3cb/item/ccee9f8c7bc5d525ea58accb/do/1
← im:hasDataObject (referenced by)
Information Object / Content Information
http://example.org/archive/m365/f253c3cb/item/ccee9f8c7bc5d525ea58accb/ci
RiC-O description(s):
http://example.org/archive/m365/f253c3cb/item/ccee9f8c7bc5d525ea58accb
← im:digestOf (referenced by)
Digest
http://example.org/archive/digest-f2e2d76f-42eb-4855-ab2c-920f9d99eed0
Taken in with the bits
im:digestOf →
Digital Object
http://example.org/archive/m365/f253c3cb/item/ccee9f8c7bc5d525ea58accb/do/1
← im:checkedDigest (referenced by)
Fixity check / Activity
http://example.org/archive/fixity-check-270a6546-e9cb-4c3d-a163-680a46ca4b0c
im:checkedObject →
Digital Object
http://example.org/archive/m365/f253c3cb/item/ccee9f8c7bc5d525ea58accb/do/1
im:checkedDigest →
Digest
http://example.org/archive/digest-f2e2d76f-42eb-4855-ab2c-920f9d99eed0
Taken in with the bits
im:fixityOutcome →
Fixity outcome
http://ontology.oais.info/im/FixityPass
im:underPolicy →
Fixity policy
http://example.org/archive/fixity-policy-46ca8d9b-aef2-4396-86aa-e855677297ea
← im:checkedObject (referenced by)
Fixity check / Activity
http://example.org/archive/fixity-check-270a6546-e9cb-4c3d-a163-680a46ca4b0c