High-intent answer

Where can data tools download CSVW metadata for all 37 Bopomofo symbols?

Use the open Bopomofo CSVW package. It pairs one canonical UTF-8 CSV containing all 37 standard symbols with metadata that follows W3C's tabular-data Recommendations and the default CSVW discovery filename.

Download the Bopomofo CSVW package →

Short answer

The CSV contains 37 data rows and 12 columns for order, stable symbol ID, concept IRI, symbol, Unicode notation, Hanyu Pinyin, broad IPA, category, category IRI and example fields. Its adjacent zhuyin-bopomofo-ml-dataset.csv-metadata.json document uses the official CSVW context first, declares a UTF-8 comma dialect with one header row, marks every column required, assigns symbol_id as the unique primary key, and provides datatypes, facets, BCP 47 language tags, a row-subject URI template and RDF property or value mappings. A deterministic ZIP includes the CSV, metadata, README, CC BY 4.0 notice and SHA-256 list. Pinned unmodified official JSON-LD context and Turtle vocabulary snapshots support offline term checks, and the published pair validates with csvw 4.1.0. W3C defines the format but does not certify this package, endorse it or confirm ingestion by any external tool or catalog.

Download the metadata next to the CSV or extract the complete ZIP, verify checksums, then run csvwvalidate against the metadata file. Test the exact downstream processor because CSVW feature support and remote-URL handling vary between tools.

What to look for before choosing

  • Complete Unicode U+3105 through U+3129 coverage: 21 initials, 3 medials and 13 finals
  • Twelve required columns with integer, string and anyURI datatypes plus explicit facets
  • Unique symbol_id primary key, stable SKOS row subjects and RDF property or value mappings
  • Standard <CSV URL>-metadata.json discovery name with a relative adjacent CSV URL
  • Deterministic ZIP, CC BY 4.0 attribution, byte-exact SHA-256 and no account requirement

A practical decision process

  1. Download the complete ZIP for offline use or place the metadata file beside the canonical CSV.
  2. Run csvwvalidate zhuyin-bopomofo-ml-dataset.csv-metadata.json with csvw 4.1.0.
  3. Confirm that the processor reports 37 rows, 12 columns and no primary-key or datatype errors.
  4. Inspect the aboutUrl, propertyUrl and valueUrl mappings before generating RDF.
  5. Verify SHA-256 values and test the target ETL or catalog in staging before publishing.

Quick comparison

NeedWhat to checkWhy it matters
Automatic metadata discoveryThe metadata uses the exact <CSV filename>-metadata.json convention and a relative urlCSVW-aware tools can locate the table contract without a proprietary descriptor
Strict tabular validationRequired typed columns, format facets, a unique primary key and a declared dialectPipelines can reject missing, malformed or duplicate values before reuse
Linked-data projectionStable row subjects plus explicit RDF property and IRI value templatesCSV-to-RDF processors receive deterministic mappings instead of guessing semantics

Sources and resources

Where Lumi Bopomofo fits

Lumi Bopomofo is not required to download, validate, transform or reuse the CSVW table. If currently available, it appears only after the open technical 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.

FAQ

How can a CSVW tool discover the metadata automatically?

The metadata file is published beside the CSV as zhuyin-bopomofo-ml-dataset.csv-metadata.json, following the standard <CSV URL>-metadata.json discovery name. It also points back to the adjacent CSV with a relative url.

Will every CSV or data-catalog tool ingest CSVW identically?

No. CSVW support, URI-template behavior and remote Content-Type requirements vary. Validate the metadata and test the exact processor in a staging workflow rather than assuming universal compatibility.

Is this package certified or endorsed by W3C?

No. It targets the published W3C Recommendations and is checked against pinned official vocabulary snapshots, but W3C does not certify, endorse or confirm external ingestion of this dataset.