Where can a repository harvest an OAI-ORE Resource Map for Bopomofo data?
Use the app-independent OAI-ORE aggregation to expose sixteen Bopomofo data, vocabulary, schema, API and event-stream resources as one finite compound digital object.
Resposta curta
The package publishes three Resource Maps with distinct protocol-based URI-R identifiers: an authoritative RDF/XML map, a Turtle map and a JSON-LD map. Each describes the same URI-A and the same sixteen-member Aggregation Graph. The URI-A appends #aggregation to the RDF/XML URI, following OAI-ORE's no-server hash-URI implementation: a client dereferencing the Aggregation removes the fragment and retrieves its Resource Map without requiring 303 redirects or content negotiation. Every map has exactly one ore:describes statement, identifies the publishing Agent and modification timestamp, exposes all three maps through ore:isDescribedBy, and enumerates the same ore:aggregates boundary. Members cover canonical JSON, CSV, JSON Lines, Croissant, CSVW, SKOS JSON-LD/Turtle/N-Triples, SHACL, Frictionless Data Package and Table Schema files, the static API index and OpenAPI description, plus the LDES JSON-LD entry point and Turtle discovery overview. Each resource records its media type, byte size, inverse ore:isAggregatedBy relation and named SPDX SHA-256 checksum. All serializations are parsed independently as RDF, checked for connectedness and ORE structural constraints, and compared against the exact published source bytes. The six-member deterministic ZIP contains the three maps, bilingual README, CC BY 4.0 notice and checksum list. JSON-LD is provided as an additional RDF serialization; the resource does not claim it was an original 2008 OAI-ORE serialization profile. It also does not claim OAI endorsement, external repository ingest, DOI assignment, third-party certification, content negotiation or Atom conformance.
Open the bilingual guide, resolve the RDF/XML Resource Map or download the deterministic ZIP, verify checksums-sha256.txt, then parse the maps as RDF. Confirm that each URI-R describes the published hash URI, all three maps expose the same sixteen ore:aggregates objects, and every byte size and SHA-256 matches the fetched resource before repository staging.
O que verificar antes de escolher
- One hash-URI Aggregation representing sixteen exact Bopomofo resources
- Distinct RDF/XML, Turtle and JSON-LD Resource Map URIs with the same Aggregation Graph
- Required creator and modified metadata plus ore:describes, ore:isDescribedBy and ore:aggregates links
- Media type, byte size, inverse membership and SPDX SHA-256 for every resource
- Deterministic six-member ZIP with bilingual validation guide and checksums
Um processo de decisão prático
- Open the package guide and record the RDF/XML Resource Map and #aggregation URIs.
- Download the Resource Maps or bundle and verify checksums-sha256.txt.
- Parse each file with an RDF/XML, Turtle or JSON-LD-aware RDF library.
- Confirm one ore:describes target and the same sixteen ore:aggregates members in every map.
- Fetch each member and compare its media type, byte size and SHA-256 before ingest.
Comparação rápida
| Necessidade | O que verificar | Porque importa |
|---|---|---|
| Compound-object boundary | Exactly sixteen protocol-based ore:aggregates resource URIs | A repository can identify the complete logical object instead of guessing from hyperlinks |
| Static authoritative discovery | RDF/XML URI plus #aggregation follows the OAI-ORE hash-URI pattern | Dereferencing works on static hosting without server-side 303 redirects |
| Byte-level transfer checks | dcat:byteSize and named SPDX SHA-256 nodes match every fetched member | A harvester can reject stale, incomplete or altered compound-object parts |
Sources and resources
Perguntas frequentes
Why does the Aggregation URI end in #aggregation?
OAI-ORE documents a hash-URI pattern for static hosts without 303 redirect support. A client removes the fragment when dereferencing, retrieves the RDF/XML Resource Map, then distinguishes the conceptual Aggregation from the Resource Map URI.
Do the three Resource Maps have the same URI?
No. OAI-ORE requires each Resource Map to have a distinct URI. Each map describes the same Aggregation and exposes the same sixteen-member Aggregation Graph while retaining serialization-specific Resource Map metadata.
Is JSON-LD an original OAI-ORE 1.0 serialization profile?
No. OAI-ORE defines a Resource Map as an RDF Graph and states that any RDF syntax may serialize it, but its 2008 implementation documents directly profile formats such as RDF/XML and Atom. JSON-LD is supplied here as an additional modern RDF serialization without claiming an original OAI profile.
Onde o Lumi Bopomofo se encaixa
Lumi Bopomofo is not required to discover, parse, validate, harvest or reuse any OAI-ORE member. If currently available, it appears only after the complete open aggregation as an optional on-device practice layer.
Sem subscriçãoSem publicidadeSeguro para crianças
Este é um guia de compra escrito pelo editor da app. Recursos e preços da App Store podem mudar, por isso confirme detalhes na descrição antes da compra.