Gold Standard · Information specialist guide
Find the nearest question, then follow the evidence
OAI-ORE makes a compound web object citable and exchangeable by giving the aggregation, its description and each contextual relationship a deliberate identity.
A research object may include an article, data, code, images and supplementary files spread across several web locations. A learning collection may combine readings, exercises and recordings owned by different services. A folder metaphor is not enough when the parts have independent URIs, change at different times and can belong to several collections.
The Open Archives Initiative Object Reuse and Exchange model, usually called OAI-ORE, describes bounded aggregations of web resources. It distinguishes the Aggregation from the Resource Map that describes it, and it provides Proxies when a resource needs an identity or assertion that is true only inside one aggregation. This guide focuses on those boundary and context decisions rather than treating RDF syntax as the whole problem.
Choose a reading route
Name the object
Aggregation, Resource Map and stable URIs.ROUTE 2 · CHAPTERS 4–5
State the boundary
Membership, context, proxies and lineage.ROUTE 3 · CHAPTERS 6–7
Work a map
Model a fictional research object and serialization.ROUTE 4 · CHAPTERS 8–10
Publish safely
Discovery, validation, versions and nested sets.ROUTE 5 · CHAPTERS 11–12
Transfer and audit
Citation, preservation and reproducible review.
Open the full chapter index · Use the field check · Return to the Information root
Chapter contents
Chapters 1–3 · Core identities and web architecture
Chapters 4–6 · Membership, context and lineage
Chapters 7–9 · Publication, discovery and change
Chapters 10–12 · Transfer, preservation and audit
CHAPTER 1 OF 12 · Name the object
1. Separate the Aggregation from its Resource Map
An OAI-ORE Aggregation is the compound resource being described. A Resource Map is a distinct resource that asserts which resources are aggregated and can add relationships and metadata. The map is not the collection itself, just as a catalogue record is not the books on its shelves.
Assign a URI to the Aggregation and a different URI to each Resource Map. Assert that the Resource Map describes the Aggregation, record who created the map and when, and keep map metadata separate from claims about the Aggregation. A map can be replaced or serialized differently while the conceptual Aggregation retains its identity.
A fictional research object has one Aggregation URI. Its Turtle and RDF/XML Resource Maps have separate document URIs and both describe the same Aggregation. A citation to the Aggregation does not silently become a citation to one serialization.
Changed-context transfer check
Apply the distinction to a museum exhibition whose resource list is published in HTML and JSON-LD. Identify which properties belong to the exhibition, the map and the individual objects.
Limit and misconception
A Resource Map is an assertion by a publisher. Its existence does not prove completeness, authority, persistence or permission to reuse every aggregated resource.
Evidence practice
Keep the Aggregation URI, Resource Map URI, describes relationship, authorship and map date. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.
Deliberately test for this failure: using one URI for both the compound object and its description, then creating ambiguous links. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.
CHAPTER 2 OF 12 · Name the object
2. Treat aggregation membership as an explicit boundary claim
The ore:aggregates relationship states that a resource is a member of an Aggregation. Membership is finite in the Resource Map being published, but the Web resources can live anywhere and can belong to other aggregations. Boundary semantics therefore depend on declared membership, not on URL prefixes or visual proximity.
Inventory every intended member and justify why it belongs. Decide whether landing pages, metadata records, thumbnails, source files and generated derivatives are members or merely links. Test duplicates, redirects, missing members and resources that appear only through an embedded page. Preserve the publisher and time of the boundary assertion.
A dataset page links to ten files and an external documentation site. The team aggregates the ten versioned files and a frozen documentation snapshot, but not every page reachable from the external site. The boundary remains inspectable instead of expanding by hyperlink traversal.
Changed-context transfer check
Transfer the test to a course pack with licensed readings. Decide whether a link, a local copy and an access-control page play the same membership role.
Limit and misconception
Explicit membership does not guarantee that a Resource Map is exhaustive for every purpose. A publisher can issue different maps around the same subject with different boundaries.
Evidence practice
Keep a member inventory, inclusion rule, exclusions, map publisher and observation time. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.
Deliberately test for this failure: inferring membership from a shared domain, directory or page link without an explicit assertion. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.
Contents · Previous chapter · Next chapter
CHAPTER 3 OF 12 · Name the object
3. Design URIs and dereferencing behaviour deliberately
OAI-ORE relies on web identifiers. The Aggregation, Resource Map, Aggregated Resources and Proxies may each need URIs with different persistence and dereferencing behaviour. A URI identifies; an HTTP response helps agents obtain representations and relationships but should not collapse distinct resources.
Document URI ownership, persistence, redirect policy, content negotiation and failure behaviour. Test the Aggregation URI in an ordinary browser and an RDF-aware client. Keep 303-style redirection or link relations consistent with the implementation guidance, and ensure that Resource Map representations identify the same map and aggregation.
A repository migrates its Resource Map endpoint. It keeps the Aggregation URI stable, redirects the old map URI to a versioned successor and preserves prior map bytes for audit. Consumers can distinguish a moved description from a renamed research object.
| Resource | Identity job | Typical error |
|---|---|---|
| Aggregation | Name the compound object | Reusing the map URI |
| Resource Map | Name one description | Treating it as the object |
| Aggregated Resource | Name a member | Inferring membership from location |
| Proxy | Name a member in context | Using it as a global replacement |
Changed-context transfer check
Change the case to identifiers minted by two institutions during a merger. Build a reconciliation rule without asserting owl:sameAs merely because titles match.
Limit and misconception
Dereferenceability helps discovery but does not make an identifier permanent. Persistence depends on organisational governance and monitored redirects.
Evidence practice
Keep a URI registry, ownership record, redirect tests, content-negotiation tests and retirement rules. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.
Deliberately test for this failure: treating current HTTP success as proof of durable identity or merging similar resources automatically. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.
Contents · Previous chapter · Next chapter
CHAPTER 4 OF 12 · State the boundary
4. Use Proxies for aggregation-specific context
A Proxy stands for an Aggregated Resource in the context of one Aggregation. It is useful when an assertion is true only in that context, such as position, local label, role or sequence. Without a Proxy, a triple about the underlying resource can be misread as globally true.
Create a Proxy only when contextual identity adds real meaning. Link it to its resource with ore:proxyFor and to its aggregation with ore:proxyIn. Put context-specific assertions on the Proxy and global assertions on the resource. Validate that every Proxy resolves to exactly the intended pair.
The same PDF appears in two reading lists. In one it is “Week 2 core reading”; in another it is “Optional background”. Two Proxies carry those local roles while the PDF keeps one global identity.
Changed-context transfer check
Apply the pattern to an artwork reused in two virtual exhibitions. Decide which caption, order and rights notice are contextual and which facts remain global.
Limit and misconception
A Proxy does not copy, secure or preserve its resource. It is a modelling device for contextual assertions and can become stale when the underlying resource changes.
Evidence practice
Keep proxy URIs, proxyFor and proxyIn links, contextual properties and validation results. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.
Deliberately test for this failure: attaching a local role directly to the global resource or creating Proxies with no useful context. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.
Contents · Previous chapter · Next chapter
CHAPTER 5 OF 12 · State the boundary
5. Represent lineage and nested aggregations without flattening them
Compound objects can be nested, and one publisher may derive a contextual member from another publisher’s Proxy. ORE lineage relates Proxies that stand for the same underlying resource across aggregations. Nesting keeps meaningful sub-objects visible instead of expanding every component into one undifferentiated list.
Choose whether a subcollection is itself an Aggregation member or whether its members are also directly aggregated. State the choice and avoid assuming transitive membership. Use lineage only when both Proxies point to the same resource and the provenance of contextual inclusion matters.
A journal issue aggregates article Aggregations; each article aggregates files. The issue map includes article Aggregation URIs, not every image and dataset transitively. A separate service can publish its own map and link contextual Proxies through lineage.
Changed-context transfer check
Transfer the structure to a heritage collection with folders curated by different institutions. Explain which boundary should remain independently citable.
Limit and misconception
Aggregation is not automatically transitive. Flattening can erase curatorial boundaries, while excessive nesting can make retrieval expensive and confusing.
Evidence practice
Keep the nesting policy, direct member sets, Proxy pairs, lineage assertions and provenance. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.
Deliberately test for this failure: assuming every member of a member Aggregation is automatically a direct member of its parent. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.
Contents · Previous chapter · Next chapter
A fictional study includes a paper, a versioned dataset, analysis code, an environment file and three figures. The team wants readers to cite the study as a compound object while preserving independent identities and licences for each part.
The team mints an Aggregation URI and a versioned Resource Map URI, lists the six direct resources, records map authorship and date, and uses Proxies to label the execution order of code and data. The paper points to the Aggregation; each member keeps its own checksum, licence and provenance outside ORE where appropriate.
A second release changes the dataset and code. The team publishes a new versioned Aggregation rather than silently altering the earlier boundary. It links releases with a version relationship and retains both Resource Maps so the original paper can still be reconstructed.
| Element | Fictional choice | Evidence |
|---|---|---|
| Aggregation | One study release | Persistent version URI |
| Resource Map | One dated description | Saved RDF and creator |
| Members | Paper, data, code, environment, figures | Resolvable URIs and fixity |
| Proxies | Execution-order context | proxyFor, proxyIn and local role |
Changed-context transfer check
Change the case so one figure is generated live from an API. State which endpoint, query, response snapshot and time evidence are needed to make the aggregation reproducible.
Limit and misconception
The study is fictional. ORE describes composition and relationships; reproducibility still requires executable code, stable data, environments, rights and validation.
Evidence practice
Keep the two versioned maps, member URIs, Proxy roles, licences, checksums and execution evidence. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.
Deliberately test for this failure: updating members behind one aggregation URI and leaving earlier citations unable to recover their boundary. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.
Contents · Previous chapter · Next chapter
CHAPTER 7 OF 12 · Work a map
7. Serialize the same model without changing its meaning
ORE is an abstract RDF model with several possible serializations. Turtle, RDF/XML, RDFa or other supported representations can express the same graph. Byte differences and syntax choices are not semantic differences unless triples, identifiers or datatypes change.
Choose a supported profile, declare media types and namespaces, and generate serializations from one canonical graph. Parse every representation back into a graph, normalise blank-node handling where needed and compare the asserted relationships. Preserve source serializations when signatures or custody matter.
A Turtle map and an RDFa landing page both list the same members, but the RDFa page accidentally omits one Proxy. Visual review passes; graph comparison reveals the semantic loss.
Changed-context transfer check
Transfer the check to JSON-LD generated by a client library. Verify contexts, compacted terms and datatype interpretation against the expanded graph.
Limit and misconception
Graph equivalence does not guarantee identical presentation, signatures or provenance. Canonicalisation and digital signatures need additional, explicit methods.
Evidence practice
Keep the source graph, serialization profile, parsed graphs, comparison report and original bytes. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.
Deliberately test for this failure: calling two maps equivalent because they render similarly while their triples differ. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.
Contents · Previous chapter · Next chapter
CHAPTER 8 OF 12 · Publish safely
8. Publish discovery links that agents can actually follow
A useful Resource Map must be discoverable from the Aggregation or an Aggregated Resource. ORE guidance describes link relations, HTML profile patterns and HTTP mechanisms that let a client move from a resource to its map without guessing URLs.
Publish the appropriate describedby or related links, test them from member and aggregation pages, and state whether more than one Resource Map is available. Verify media types, redirects, relative URI resolution and cross-origin access where relevant. Keep discovery links updated when maps move.
A repository publishes an accurate map but exposes it only through a search form. Automated clients cannot discover it from the dataset landing page. Adding a tested link relation repairs the information path without changing the graph.
Changed-context transfer check
Apply the test to a resource with two maps: an authoritative publisher map and a community annotation map. Explain how clients can retain provenance rather than merging them blindly.
Limit and misconception
Discovery is not authority. Anyone can describe an aggregation, so agents must evaluate who published a Resource Map and for what purpose.
Evidence practice
Keep hTTP headers, HTML links, media types, redirect traces and publisher identity. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.
Deliberately test for this failure: publishing a correct but undiscoverable map or treating every discovered map as equally authoritative. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.
Contents · Previous chapter · Next chapter
CHAPTER 9 OF 12 · Publish safely
9. Validate graph constraints and boundary semantics separately
RDF syntax validation checks only whether a graph parses. ORE conformance also depends on required types and relationships, cardinality expectations, URI roles and coherent Proxy pairs. Local boundary rules add another layer: a map can be ORE-conformant yet wrong for the object it claims to describe.
Validate syntax, ORE model constraints, URI dereferencing, membership completeness, contextual assertions and local policy as separate gates. Report warnings and failures with the exact triples and resources involved. Use test fixtures for missing aggregation links, orphan Proxies, duplicate descriptions and unreachable members.
A map parses and states that a Resource Map describes an Aggregation, but one Proxy has proxyFor without proxyIn. Model validation catches the orphan; a later local check catches a missing data file that the conformant map never listed.
Changed-context transfer check
Transfer the layered check to a large nested collection. Design sampling without losing exact validation of every direct member link.
Limit and misconception
No validator can determine the intended real-world boundary without a declared inventory or responsible publisher. Semantic review remains necessary.
Evidence practice
Keep parser output, ORE constraint report, URI checks, intended inventory and exception decisions. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.
Deliberately test for this failure: equating RDF syntax success with a complete and truthful aggregation. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.
Contents · Previous chapter · Next chapter
CHAPTER 10 OF 12 · Publish safely
10. Version Resource Maps and Aggregations without rewriting history
A Resource Map can change because errors are corrected, descriptions improve or aggregation membership changes. These are not the same event. Map metadata can be revised while the Aggregation remains stable, but a material boundary change may require a new aggregation version so prior citations retain meaning.
Define which changes create a new map version, a corrected assertion or a new Aggregation. Preserve timestamps, supersession links, change notes and old maps. Monitor member redirects and disappearance, but do not silently replace a cited member with a convenient substitute.
A spelling correction to a map creator name produces a corrected map. Replacing the dataset with new measurements produces a new study-release Aggregation. The policy makes the difference predictable.
Changed-context transfer check
Change the case to a member whose host redirects to an updated file. Decide when to preserve the old target, mint a new member URI or record unavailability.
Limit and misconception
Version relations describe change but do not preserve bytes. Archival storage and fixity remain separate responsibilities.
Evidence practice
Keep a version policy, dated maps, change log, supersession links and member availability checks. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.
Deliberately test for this failure: editing a mutable map in place until old citations describe a different resource set. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.
Contents · Previous chapter · Next chapter
CHAPTER 11 OF 12 · Transfer and audit
11. Connect ORE boundaries to citation and preservation packages
ORE supplies web-scale composition, while data citation, PREMIS and BagIt answer different questions about version identity, preservation events and transfer packaging. A trustworthy workflow connects these layers without pretending one standard replaces the others.
Cite the versioned Aggregation, preserve the Resource Map and its dependencies, record preservation actions in PREMIS and transfer the captured files and metadata in a validated package. Map each identifier across systems and verify that the packaged member set matches the cited ORE boundary.
A repository captures a study Aggregation, exports its members into BagIt and records the capture Event in PREMIS. A reconciliation table proves that every direct ORE member is either packaged, intentionally referenced remotely or documented as unavailable.
Changed-context transfer check
Transfer the workflow to a dynamic teaching collection. Decide which live services can remain references and which content must be snapshotted for future evidence.
Limit and misconception
A complete ORE map can point to volatile or inaccessible resources. Composition metadata alone is not preservation.
Evidence practice
Keep the cited Aggregation, captured map, identifier crosswalk, package inventory and PREMIS Events. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.
Deliberately test for this failure: preserving a map without its members or packaging files whose relationship to the cited aggregation is unknown. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.
Contents · Previous chapter · Next chapter
CHAPTER 12 OF 12 · Transfer and audit
12. Audit a Resource Map from URI to reproducible boundary
An audit should let a second reader start at the Aggregation URI, discover the Resource Map, enumerate direct members, interpret contextual Proxies and reproduce the boundary and version decision. It should also expose unavailable resources and assertions that depend on one publisher.
Resolve URIs in a controlled environment, save responses and headers, parse the map, validate constraints, compare the member set with the intended inventory, traverse Proxy links and sample member identity and fixity. Record redirects, failures, publisher identity and the exact audit time.
A fictional audit discovers that two members redirect to newer versions and one Proxy links to the wrong Aggregation. The team preserves the evidence, repairs the map through a new dated version and leaves the prior map available with a correction notice.
Changed-context transfer check
Design the audit for an aggregation described by three independent maps. Explain how disagreements are surfaced without manufacturing one false consensus graph.
Limit and misconception
A successful audit proves only the tested map, resources and time. The open Web can change immediately afterward, so monitoring and versioned capture remain necessary.
Evidence practice
Keep saved responses, graph validation, inventory comparison, Proxy traversal, fixity samples and correction log. Label every field as observed, computed, assumed or chosen. Give the record to a second reader and ask them to reproduce the result without the original author explaining what was meant. Differences reveal hidden definitions, missing versions or decision rules that still need to be made explicit.
Deliberately test for this failure: reporting a green status while redirects, unavailable members or publisher disagreements remain hidden. Record the earliest point at which the process can detect it, the correction applied and whether later conclusions change. A method is transferable only when its controls work on an altered case, not merely on the example used to teach it.
Contents · Previous chapter · Connected articles
Advanced boundary cases
Blank nodes and durable identity
Blank nodes can be valid RDF but are awkward for long-lived cross-document reference. Mint governed URIs for entities that require independent citation, provenance or reconciliation rather than assuming a serializer-local label will persist.
Several maps for one aggregation
Different publishers can describe the same Aggregation. Keep map authorship, time and purpose visible; compare assertions rather than collapsing provenance into one supposedly authoritative graph.
Dynamic and query-defined aggregations
A live query can describe a useful set, but reproducibility needs the query, endpoint, execution time, ordering, version and captured results. Do not call a moving result boundary fixed merely because it has one landing-page URI.
A practical field check
Use this check when publishing, ingesting or preserving a Resource Map for a compound web object.
- Name the Aggregation and Resource Map separately.
- Declare the direct member boundary and exclusions.
- Test URI ownership, redirects and discovery links.
- Use Proxies only for context-specific assertions.
- Document nesting, lineage and non-transitive membership.
- Parse and compare every supported serialization.
- Version material boundary changes and preserve prior maps.
- Reconcile the map with citation, package and preservation evidence.
Run the check as a small workbook
Use linked sheets for resources, URIs, direct membership, Proxies, discovery links, versions, HTTP checks and validation exceptions. Each row should identify the asserting map and time so disagreements remain attributable.
| Gate | Pass condition | Stop condition |
|---|---|---|
| Identity | Aggregation and maps have distinct governed URIs | One URI carries conflicting roles |
| Boundary | Direct membership is explicit and justified | Membership inferred from location |
| Context | Proxies have coherent proxyFor and proxyIn links | Context attached globally |
| Reproduction | A second reader can recover the dated member set | Mutable map or missing members |
Chapter-by-chapter evidence audit
| Chapter | Evidence to keep | Failure to catch |
|---|---|---|
| 1. Separate the Aggregation from its Resource Map | The Aggregation URI, Resource Map URI, describes relationship, authorship and map date | Using one URI for both the compound object and its description, then creating ambiguous links |
| 2. Treat aggregation membership as an explicit boundary claim | A member inventory, inclusion rule, exclusions, map publisher and observation time | Inferring membership from a shared domain, directory or page link without an explicit assertion |
| 3. Design URIs and dereferencing behaviour deliberately | A URI registry, ownership record, redirect tests, content-negotiation tests and retirement rules | Treating current HTTP success as proof of durable identity or merging similar resources automatically |
| 4. Use Proxies for aggregation-specific context | Proxy URIs, proxyFor and proxyIn links, contextual properties and validation results | Attaching a local role directly to the global resource or creating Proxies with no useful context |
| 5. Represent lineage and nested aggregations without flattening them | The nesting policy, direct member sets, Proxy pairs, lineage assertions and provenance | Assuming every member of a member Aggregation is automatically a direct member of its parent |
| 6. Worked example: map a fictional reproducible study | The two versioned maps, member URIs, Proxy roles, licences, checksums and execution evidence | Updating members behind one aggregation URI and leaving earlier citations unable to recover their boundary |
| 7. Serialize the same model without changing its meaning | The source graph, serialization profile, parsed graphs, comparison report and original bytes | Calling two maps equivalent because they render similarly while their triples differ |
| 8. Publish discovery links that agents can actually follow | HTTP headers, HTML links, media types, redirect traces and publisher identity | Publishing a correct but undiscoverable map or treating every discovered map as equally authoritative |
| 9. Validate graph constraints and boundary semantics separately | Parser output, ORE constraint report, URI checks, intended inventory and exception decisions | Equating RDF syntax success with a complete and truthful aggregation |
| 10. Version Resource Maps and Aggregations without rewriting history | A version policy, dated maps, change log, supersession links and member availability checks | Editing a mutable map in place until old citations describe a different resource set |
| 11. Connect ORE boundaries to citation and preservation packages | The cited Aggregation, captured map, identifier crosswalk, package inventory and PREMIS Events | Preserving a map without its members or packaging files whose relationship to the cited aggregation is unknown |
| 12. Audit a Resource Map from URI to reproducible boundary | Saved responses, graph validation, inventory comparison, Proxy traversal, fixity samples and correction log | Reporting a green status while redirects, unavailable members or publisher disagreements remain hidden |
Connected articles across the eduKate ecosystem
Start with the governing route
- The Gold Standard of Information
- The Gold Standard of Education | Learning That Transfers into Life
- How X Works hub
Continue into verified specialist studies
- The Gold Standard of Information Preservation Engineering — place Resource Maps inside a broader preservation and repository-control system.
- PREMIS Events, Agents, Objects and Preservation Evidence — record the preservation actions applied to captured aggregation resources.
- BagIt Profiles, Payload Manifests, Fixity and Transfer Validation — package an aggregation for controlled transfer.
- Data Citation, Versioned Queries, Fixity and Reproducible Subsets — connect aggregation identity with reproducible citation.
- Canonical Serialization, Deterministic Encoding, Hash Stability and Signature Verification — separate graph meaning from deterministic bytes and signatures.
Questions readers often ask
Is a Resource Map the same as its Aggregation?
No. The Resource Map is a separately identified description of the Aggregation.
Must every linked page be an aggregated resource?
No. Membership is asserted explicitly; ordinary hyperlinks do not define the boundary.
When is a Proxy useful?
Use one when an assertion is true of a resource only in the context of a particular Aggregation.
Is aggregation membership transitive?
Not automatically. A parent can aggregate a child Aggregation without directly aggregating every child member.
Does valid RDF prove a complete Resource Map?
No. Syntax, ORE constraints, URI behaviour and intended boundary all require separate checks.
Does OAI-ORE preserve the resources it describes?
No. Preservation requires capture, fixity, storage, rights and ongoing governance beyond the composition graph.
Sources and scope
OAI-ORE Specification: Abstract Data Model — official model for Aggregations, Resource Maps, Aggregated Resources and Proxies.
OAI-ORE User Guide: Primer — official introductory examples and identity relationships.
OAI-ORE Specification: Vocabulary — official classes, properties and usage constraints.
OAI-ORE User Guide: Resource Map Discovery — official discovery and Proxy guidance.
OAI-ORE User Guide: HTTP Implementation — official guidance for web access, links, redirects and Proxy URIs.
The study, collection and repository examples are fictional. OAI-ORE 1.0 is a mature specification whose implementation choices must still be tested against current web infrastructure, repository policy, rights and preservation requirements.
“Gold standard” describes the educational benchmark explained in this guide. It is not an official accreditation, legal opinion, policy determination or professional certification.
Back to contents · Return to the Information root · Return to the Gold Standard of Education