Short answer
The package follows the official LDES 1.0 consumer specification, vocabulary and server primer together with the TREE hypermedia specification. The canonical JSON-LD entry point is both an ldes:EventStream and the mutable root tree:Node; it has exactly one tree:view pointing to itself. It publishes ldes:timestampPath as dcterms:created, ldes:versionOfPath as dcterms:isVersionOf, a version-create class, an inline SHACL member shape, and a retention policy whose ldes:startingFrom equals the first retained event. Six typed TREE relations form paired inclusive-lower and exclusive-upper dcterms:created bounds for three JSON-LD nodes. Each node states ldes:immutable true and embeds its own tree:member descriptions. The 37 unique member IRIs contain timezone-qualified timestamps, link stable SKOS concept IRIs, and reproduce the canonical CSV fields for U+3105 through U+3129. The Turtle file is a discovery overview linking to the canonical JSON-LD root rather than a claim of server-side content negotiation. A deterministic nine-member ZIP, SHA-256 list, bilingual reuse guide and CC BY 4.0 notice support offline validation. Every JSON-LD document uses an inline context, and all RDF graphs, relation bounds, source concepts, checksums and ZIP properties are tested. This publisher-authored static snapshot does not claim a live write API, custom Cache-Control headers, registry listing, external replication, certification or LDES/TREE community endorsement.
Open the JSON-LD entry point, confirm one self tree:view and read its timestamp, version and shape paths. Follow each tree:relation/tree:node pair that your time filter cannot prune, extract the stream's tree:member IRIs, validate their dcterms:created and dcterms:isVersionOf values, and persist emitted member IRIs. For offline review, verify checksums-sha256.txt before opening the deterministic ZIP.
What to look for before choosing
- One stable ldes:EventStream and root node with exactly one self tree:view
- Thirty-seven immutable version members spanning every canonical Bopomofo symbol
- Three JSON-LD TREE nodes with paired lower and upper dcterms:created bounds
- Explicit timestampPath, versionOfPath, create semantics, retention policy and SHACL shape
- Turtle discovery overview, deterministic bundle and byte-level SHA-256 verification
A practical decision process
- Open the bilingual guide and record the canonical JSON-LD EventStream IRI.
- Parse the root and confirm its TREE view, timestamp path and version path.
- Traverse the six bounded relations to the three immutable nodes.
- Emit each unique TREE member once and verify all 37 SKOS version targets.
- Validate the SHACL paths and preserve member state before synchronizing again.
Quick comparison
| Need | What to check | Why it matters |
|---|---|---|
| Static incremental discovery | One root with paired time-bound TREE relations to three dereferenceable nodes | A client can traverse or prune finite branches without a custom query API |
| Duplicate-safe replication | Thirty-seven unique immutable member IRIs with timezone-qualified timestamps | A consumer can persist emitted IRIs and avoid replaying the same version |
| Version-aware reuse | Every event has one dcterms:isVersionOf link to a stable SKOS concept | Downstream systems can distinguish an immutable event from the entity it versions |