Short answer
Each record describes a learning resource rather than an app. Source URLs, languages, byte lengths, modification timestamps and SHA-256 values come from the published EPUB manifest. The OAI-DC files validate against pinned official OAI and DCMI schemas. Both JSON-LD graphs use inline contexts and parse without network access; their DCMI and LRMI terms are checked against pinned official RDF vocabularies, including the LRMI supportingDocument resource type and instruction educational use. Download from https://alice51849.github.io/ios-app-guide/data/zhuyin-bopomofo-oer-repository-metadata.html. These are metadata candidates, not an OAI-PMH service, DOI assignment, institution-approved record or universal-ingest guarantee.
Ingest into a staging collection first. Map local subjects, audience fields and identifiers, verify links and hashes, and inspect English, Traditional Chinese and Bopomofo display before publishing. Strict URL importers may need local file upload because static hosting can return generic XML or JSON Content-Types.
What to look for before choosing
- Two standalone OAI-DC records, one for each exact EPUB language edition
- One DCMI Terms JSON-LD graph with audience, education level, instructional method, rights and provenance
- One LRMI JSON-LD graph with LearningResource, supportingDocument, instruction and explicit learning outcomes
- Inline JSON-LD contexts, pinned official vocabularies and deterministic SHA-256-checked bytes
- CC BY 4.0, no account required and no dependency on an app
A practical decision process
- Open the bilingual OER repository metadata guide.
- Download the complete ZIP or the individual syntax your repository accepts.
- Verify checksums and confirm that each metadata record points to the intended EPUB edition.
- Map local subjects, audiences and identifiers in a staging collection.
- Review language display and repository policy before making the record public.
Quick comparison
| Need | What to check | Why it matters |
|---|---|---|
| Simple XML crosswalk | Standalone OAI-DC record validated against official schemas | A repository can map the 15-element Dublin Core view without treating the file as an OAI-PMH response |
| Rich general-purpose RDF | DCMI Terms JSON-LD with audience, method, level, rights, relations and provenance | Repository fields retain more educational and fixity context than Simple Dublin Core |
| Learning-resource discovery | LRMI JSON-LD using official terms and controlled concept URIs | Educational catalogs can identify resource type, instructional use, level and intended outcomes |
Sources and resources
- Bopomofo OER repository metadata package
- Open Archives Initiative OAI-DC XML schema
- DCMI Metadata Terms
- LRMI Terms
- LRMI Concept Schemes
Where Lumi Bopomofo fits
Lumi Bopomofo is not required to download, validate, ingest or reuse the metadata or EPUB. If currently available, it appears only after the free OER resource as an optional on-device practice layer.
No subscriptionNo adsKid-safe
This page is an independent buying guide. App Store features and prices can change, so confirm details on the listing before purchase.