Harvest Nine Open Bopomofo Datasets from a Static DCAT 3 Catalog

Short answer

The catalog covers the 37-symbol reference data, static JSON API, SKOS and SHACL vocabulary, Croissant, CSVW and Data Package tables, Anki imports, LMS packages, EPUB and OPDS publication files, library records, and OER repository metadata. Every direct distribution records an IANA media-type IRI, byte size, CC BY 4.0 license, language IRIs and an SPDX SHA-256 checksum calculated from the published bytes. Each dcat:CatalogRecord has exactly one foaf:primaryTopic, and the static API is represented separately as a dcat:DataService. Download from https://alice51849.github.io/ios-app-guide/data/zhuyin-bopomofo-dcat3-open-data-catalog.html. This is a static DCAT description, not portal registration, W3C certification, institutional endorsement or proof that an external catalog has harvested it.

Parse the JSON-LD or Turtle in a staging catalog, read dcat:dataset and dcat:record, verify distribution hashes and byte sizes, and map themes, language policies and local identifiers before publication. Use dcat:downloadURL for files and dcat:endpointURL for the read-only API.

What to look for before choosing

Nine catalogued Bopomofo datasets with bilingual titles and descriptions
Forty-five direct distributions spanning data, linked data, tabular metadata, learning packages, publications and repository metadata
Equivalent JSON-LD and Turtle RDF graphs with stable named resources
SPDX SHA-256 checksums, exact byte sizes, IANA media-type IRIs and distribution-level CC BY 4.0 licenses
One dcat:DataService for the versioned static JSON API, with OpenAPI endpoint description

A practical decision process

Open the bilingual DCAT 3 catalog guide.
Download JSON-LD, Turtle or the deterministic ZIP bundle.
Parse the graph and confirm each CatalogRecord has one primary topic.
Verify distribution byte sizes and SPDX SHA-256 values before ingest.
Map local themes and policy fields in a staging catalog before publishing.

Quick comparison

Need	What to check	Why it matters
JSON-LD ingestion	Inline contexts and stable named IRIs for catalog, records, datasets, distributions, checksums and service	A JSON-LD processor can parse the graph without fetching a remote context
Turtle or linked-data tooling	A Turtle serialization isomorphic with the JSON-LD graph	RDF tools can choose either syntax without receiving different catalog semantics
File integrity checks	Distribution-level SPDX SHA-256 plus xsd:nonNegativeInteger byte size	Harvesters can detect changed or incomplete bytes before local publication

Sources and resources

Where Lumi Bopomofo fits

Lumi Bopomofo is not required to download, parse, verify or reuse the DCAT catalog or any listed open resource. If currently available, it appears only after the free catalog 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.

FAQ

Has this catalog been registered with a government or institutional portal?

No. It is a publicly downloadable static DCAT 3 description. It does not claim portal registration, W3C certification, institutional approval or confirmed harvesting by any third party.

Are the checksums independent authenticity proofs?

No. They are useful SHA-256 fixity values, but the catalog and files share the same host. A consumer that needs authenticity should preserve or verify the metadata through a separately protected channel.

Is the landing page itself a data distribution?

No. The graph uses dcat:landingPage for human-readable guides and dcat:downloadURL for direct file distributions. The static API is modeled as a dcat:DataService.

Where can an open-data catalog harvest a Bopomofo dataset in DCAT 3?