Repository navigation
YuCe 0.1.6
YuCe 0.1.6: a withdrawal closes text of a document.
The blind grading of the first run on four makers found the gap: after a withdrawal a reader went back to the page and stored the
withdrawn sentence with its list number, three bytes wider, and the answer of the kernel's side cited it.
Fixed
- A wider quote no longer brings withdrawn text back. The kernel refused only the exact span, so any quote that contained it was a new
record with its support. A new quote that overlaps the withdrawn bytes is now refused withEVIDENCE_REVOKED, which names the span. The
text stays closed wherever those bytes stand in the document, in any version. - A withdrawal takes every stored quote that overlaps it. It reached one record: the others were found only by the benchmark's runner.
The answer now says how many other records went with it (also_revoked). A quote that went with another can still be withdrawn itself,
which closes the rest of its text. LIMITATIONS.mdsaid too much. "No claim stays grounded on a withdrawn quote" held for the record, not for its text. It is corrected,
andBENCHMARKS.mdnames the one wider quote of the published runs, which no answer cited.
New
audit_withdraw_textwithdraws text nobody has quoted yet, so a withdrawal no longer depends on a stored record. The Python client has
it aswithdraw_text.
Old journals
New journals record the rule in their genesis (r2r-audit-genesis/2). A journal of an earlier release replays under the rule it was written
with, so the published runs verify with the same roots. An earlier binary refuses a new journal.
Pre-registration
benchmarks/PREREGISTRATION_0.1.6.md fixes the repeat
of the run from this tag. That run and the run of 0.1.5 are in BENCHMARKS.md, both as they came out.
Full list: CHANGELOG.md.
Assets
- Binaries:
yuce-v0.1.6-<target>for Linux x86_64, Windows x86_64 and macOS (arm64, x86_64), each withsbgk, its alias
yuce, LICENSE, NOTICE, THIRD_PARTY_LICENSES.md and README;SHA256SUMS-<platform>.txt. - The Python client: organetic-yuce on PyPI.
- The two runs on four makers:
makers1-*andmakers2-*, one archive per run and per grading, with a manifest each andSHA256SUMS-runs.txt. - The earlier recorded runs of BENCHMARKS section 1 stay in the v0.1.0 release.
Check a download with sha256sum -c SHA256SUMS-<platform>.txt.