Describes the current state. Live figures are on current status.
Review register
Every review OpenRiC has received, what it found, what we did about it, and what is still open. A reviewer is named only with their permission; otherwise the entry says “not named”. Reviewer type says whether a review came from outside the project (external), from the maintainer (internal), or from an automated tool; “not recorded” means the type was not written down when the review arrived. So far only R-1 is recorded as external, and most reviews are from a single week in October 2026: read the register with that in mind. The review page explains how to add to it, and known issues holds the problems we know about and have not fixed.
None of these reviews is the formal external technical review the Standard Acceptance Gate requires: that reviewer is not yet appointed (K-1).
Reviews
| # | Date | Reviewer | Reviewer type | Scope | Main findings | Response | Status |
|---|---|---|---|---|---|---|---|
| R-1 | April 2026 | Not named (a reviewer from the ICA-EGAD community) | External | RiC-O conformance of the terms OpenRiC emits | Terms in the RiC-O namespace that RiC-O 1.1 does not define | The RiC-O 1.1 audit; every non-RiC-O term moved to the openricx: extension namespace (v0.37.0) |
Resolved |
| R-2 | 14 Oct 2026 | Not named | Not recorded | openric.org site and the plan for a full application | Contradictory profile counts and hand-typed figures; a stale drift log; a demonstration record presented with a real institution’s name; “contract” and “application” confused; keys in browser storage, open anonymous writes and a wide CORS policy on the reference service | Site figures rendered from release data and checked in CI (v0.44.0 to v0.46.0); evidence labels; the application named OpenRiC Workspace and separated from the specification; service security fixes (v0.17.x) | Resolved, except the second independent implementation (K-6) |
| R-3 | 15 Oct 2026 | Not named | Not recorded | Website deep review and enhancement plan | Getting-started writes not safe to copy; status unreadable without JavaScript; demonstration data unlabelled in the viewer; no SPARQL probe | Safe getting-started and minimal-server writes, a no-script status snapshot, demonstration labels, a SPARQL Access probe | Resolved |
| R-4 | 19 Oct 2026 | Not named | Not recorded | Developers, status and institutions pages | OpenAPI 3.1 and 3.0 both claimed; “four documents” against seven; release and tested versions confused; institutional claims stronger than the evidence | Each corrected (v0.49.3) | Resolved |
| R-5 | 19 Oct 2026 | Not named | Not recorded | How review and evaluation work | No single entry point for reviewers; RiC and OpenRiC easily confused; conformance reporting not explicit about skips; no way to test without AHG’s code | Review page, RiC and OpenRiC compared, status-page sections on version alignment, what a pass proves and every check that did not pass, and evaluating independently (v0.50.0) | Resolved |
| R-6 | 19 Oct 2026 | Comparison by the maintainer against independently published work: Matthew Bruton’s ISAD(G) to RiC crosswalk (MIT), the RiC-O Converter by Sparna and the Archives nationales de France Lab (CeCILL-B), and the biax and ITDT extension ontologies | Internal (the maintainer, comparing with others’ published work) | The mapping and the extension ontology | Literal values on RiC-O object properties (dates, date type, legal status); rico:hasOrHadLanguage used on record sets outside its domain; a non-existent finding-aid IRI; a false claim of alignment with the converter; extension terms RiC-O 1.1 already covers |
Fixed in specification v0.50.0 and service v0.17.18; four extension terms deprecated and the rest anchored to RiC-O in v0.50.1 | Resolved |
| R-7 | 19 Oct 2026 | Not named | Not recorded | Version figures, governance and known issues | Pages showing different versions; the v1.0 gate stated two ways; the reference service shown as tested against an old release; known issues keyed to an old baseline | Version mismatch traced to page caching during two releases, not to the data; a hand-typed figure removed; governance separates the v1.0 gate from maturity goals; known issues given a status per entry (v0.50.2) | Resolved |
| R-8 | 19 Oct 2026 | Not named | Not recorded | Governance, review evidence, conformance claims, known issues | The developers page still listed three v1.0 conditions; review findings not public; Round-Trip Editing reported as a pass while its writes are skipped; open, resolved and accepted issues mixed together | The single v1.0 gate stated the same way on every page; this register; skipped write checks reported as “not verified”; known issues split into open, accepted and resolved | Resolved |
| R-9 | 19 Oct 2026 | Not named | Not recorded | Governance, conformance claims, the review register, names and titles, the proof page | governance.html reported as stale (an April version number, the old company name, no v1.0 gate section); the reference service failing a normative profile it does not declare; review entries indistinguishable from internal passes; the doctoral title; a third form of the company name; the proof page claiming the same graph shape “from every conformant server” and a nightly reset that did not mention the shared database | The live governance page was checked as served (GitHub Pages, modified 19 October) and is up to date; the reviewer’s copy predates 15 October. Reviewer type column added here; the extension ontology’s creator name corrected; the proof page reworded; the service’s OpenAPI document made 3.1 (service release 0.17.21). Provenance & Event stays open as K-10 | Resolved, except K-10 and the external reviewer (K-1) |
Unresolved objections
What reviewers have raised that OpenRiC has not resolved, and why.
| Raised in | Objection | Where it stands | |
|---|---|---|---|
| R-2 | OpenRiC has no implementation outside the organisation that wrote it, so its claims to portability are not yet tested. | Accepted as the central gap. It is the v1.0 gate and known issue K-6. | Not recorded |
| R-2 | Every fixture is synthetic or comes from the reference service’s demonstration data. | Open, K-7: it closes when an institution contributes publishable data. | Not recorded |
| R-5 | Nothing about RiC’s usability for the public has been tested with users. | Open. The review page asks reviewers for exactly this, and summarises what earlier research found. | Not recorded |
| R-4 | The reference service published its own OpenAPI document as version 3.0.3, while the specification’s contract is 3.1. | Resolved in service v0.17.21: the service document is OpenAPI 3.1.0, validated against the official 3.1 schema, and reports the service’s own version. | Not recorded |