Commons (3 of 6)
4 specifications, 144 requirements. All libraries
0019 IFC Mizan Integrations
| Requirement | Mechanism | Who | Note |
|---|---|---|---|
FR-001 | check | bun test suite/ | mizan-boundaries.test.ts: pure/ imports only the kernel and itself, host/ exists, the module is exported |
FR-002 | check | bun test suite/ | mizan-integrations.test.ts: the registry looks integrations up by formats and refuses an identifier or a pair twice; the record is typed |
FR-003 | none | Planned, Phase 4 of issue #10: the module is not built yet | |
FR-004 | check | bun test suite/ | mizan-integrations.test.ts: the reader reads the Turtle the kernel writes back to the same graph; kernel/rdf.test.ts: the kernel exports no reader |
FR-005 | check | bun test suite/ | mizan-integrations.test.ts: only the slice is taken, an empty slice and a term the source lacks are refused |
FR-006 | check | bun test suite/ | mizan-integrations.test.ts: a pin mismatch, no license and no right to copy are refused; the module's header names its source; the command writes and checks it |
FR-007 | check | bun test suite/ | mizan-integrations.test.ts: a blank node and a collection are named as losses, in the slice only, and the rest is read |
FR-008 | none | Planned, Phase 4 of issue #10: the module is not built yet | |
FR-009 | check | bun test suite/ | mizan-integrations.test.ts: the provenance is PROV-O Turtle the reader reads back, deterministic; the command writes it beside the manifest |
FR-010 | check | bun test suite/ | mizan-integrations.test.ts: SQL, SKOS, SHACL, JSON Schema and SSSOM written from a class schema, a code list and the mappings of terms; tests/commons-mizan-ontology.test.ts: Mizan's own exports are current. RDF/XML, OWL and DCAT: FR-016 to FR-019 |
FR-011 | check | bun test ./tests/ | tests/commons-mizan-ontology.test.ts: rdflib parses the Turtle, pySHACL finds Mizan's ontology conforms to the shapes made from its schemas and rejects a broken one, jsonschema checks the JSON Schema; skipped where Python and these three are not installed (CI installs them, pinned) |
FR-012 | none | Planned, Phase 4 of issue #10: the module is not built yet | |
FR-013 | none | Planned, Phase 4 of issue #10: the module is not built yet | |
FR-014 | check | bun test suite/ | mizan-integrations.test.ts: a source served over HTTP is written, checked offline, checked with a fetch, refused when its bytes change and named when it cannot be fetched |
FR-015 | check | bun test suite/ | mizan-integrations.test.ts: a catalog read into typed controls, a slice imported deterministically, a missing control, a pin mismatch and no right to copy refused, the command run from a manifest with no namespace |
FR-016 | check | bun test suite/ | mizan-exporters.test.ts: the triples are written as canonical RDF/XML (the order of the statements does not matter, a plain string, a language, a datatype and a blank node are each written, text is escaped, a predicate with no XML name and a control character are named); tests/commons-mizan-ontology.test.ts: rdflib parses the RDF/XML into a graph isomorphic to the Turtle's, skipped where Python and rdflib are not installed |
FR-017 | check | bun test suite/ | mizan-exporters.test.ts: classes and properties are written as OWL functional syntax (declarations, SubClassOf, domain, range, annotations, the ontology's version IRI, the classes it names and does not define, the datatypes), deterministic, and a datatype range of an object property or a class range of a datatype property is named; tests/commons-mizan-ontology.test.ts: a reader written in the test checks the axioms against the Turtle graph (no OWL functional-syntax reader is a pinned dependency; the RDF/XML was also loaded once by hand into owlready2) |
FR-018 | check | bun test suite/ | mizan-exporters.test.ts: the catalog is written as DCAT 3 Turtle (catalog, dataset, one distribution for each file with its media type, download URL and license), the same bytes for the same catalog, a bad IRI and a bad media type are named; tests/commons-mizan-ontology.test.ts: rdflib parses the catalog and finds the datasets and distributions, each distribution's file in the repository |
FR-019 | check | bun test ./tests/ | tests/commons-mizan-ontology.test.ts: mizan.auto.rdf, mizan.auto.ofn and mizan-catalog.auto.ttl are what the generator makes, each says it is generated, the catalog lists a distribution for every file the generator writes for the ontology; textOf throws ExportRefused where an exporter refuses, which main turns into exit 2 (tested at textOf: the Mizan ontology itself is never refused, so the whole command has no failing case to run) |
FR-020 | check | bun test suite/ | mizan-integrations-formats.test.ts: compacted and expanded JSON-LD read with vocab, base, aliases, coerced and typed values, a list, a reverse, a nested node and the text of a number; tests/commons-mizan-importers.test.ts: the graph equals rdflib's (skipped where Python is not installed) |
FR-021 | check | bun test suite/ | mizan-integrations-formats.test.ts: a remote context, a scoped context, a named graph, a nest and a JSON literal are named with their line and the rest is read; bad JSON stops with its line |
FR-022 | check | bun test suite/ | mizan-integrations-formats.test.ts: a slice of $defs becomes code lists and field-name unions (allOf and $ref followed, enums lifted), deterministically, a missing definition and one with nothing to hold end the import; tests/commons-mizan-importers.test.ts: the lists and names agree with jsonschema and an independent resolution |
FR-023 | check | bun test suite/ | mizan-integrations-formats.test.ts: additionalProperties as a schema, anyOf, value constraints, a $ref outside $defs, an earlier draft and a clash of identifiers are named |
FR-024 | check | bun test suite/ | mizan-integrations-formats.test.ts: RDF/XML read with entities, base, rdf:ID, language, datatype, parseType, property attributes, rdf:li, CDATA and reification, and RFC 3986 resolution; tests/commons-mizan-importers.test.ts: the graph equals rdflib's. Twelve W3C RDF/XML files (8,848 triples) were also read to rdflib's graph while this was written, and are not copied here |
FR-025 | check | bun test suite/ | mizan-integrations-formats.test.ts: an XML literal and an external entity are named and the rest is read; a document that is not well formed stops with its line |
FR-026 | check | bun test suite/ | mizan-integrations-formats.test.ts: the same slice imported from JSON-LD and RDF/XML gives the same vocabulary, a blank-node value is named and a pin mismatch is refused; the command runs a json-ld and an rdf-xml manifest |
FR-027 | check | bun test suite/ | mizan-integrations-formats.test.ts: the command runs a json-schema manifest with no namespace, and --check names a slice that drifted from the module's header |
FR-028 | check | bun test ./tests/ | tests/commons-mizan-importers.test.ts: rdflib reads the JSON-LD and RDF/XML to the reader's graph and jsonschema accepts the lists the import writes; skipped where Python and these tools are not installed (CI installs them, pinned) |
FR-029 | review | 0017-two-languages FR-007 | Whether an XML reader needs a pinned tool is judged on evidence recorded in the requirement: twelve W3C RDF/XML files read to rdflib's graph by the hand-written reader; the test of FR-024 keeps its features checked |
FR-030 | check | bun test suite/ | mizan-nist-import.test.ts: the committed module names the controls the specifications cite, with the titles of the pinned catalog, and the import's offline check passes |
0020 Intellectual Frontiers Capabilities Configuration Management
| Requirement | Mechanism | Who | Note |
|---|---|---|---|
FR-001 | none | Not built in M2 of issue #10: no rule reads the words a tracker or a commit message uses for a unit of change; the class ifccm:Capability exists and is audited (ifccm-ontology.test.ts) | |
FR-002 | none | Not read by any rule: whether a body of work has one change request, with its tasks as checkbox items, is judged by a person, because the host cannot say which change requests belong to one body of work | |
FR-003 | check | bun test suite/ | mizan-changes-pure.test.ts: the four sections in order, the Done when requirements and the checkbox items are read from a body; a missing or misordered section is a problem, and changes/issue-shape finds it on a Closes of a capability |
FR-004 | check | bun test suite/ | mizan-changes-pure.test.ts: checkbox items are read with whether each is ticked, outside code blocks; mizan-changes-git.test.ts: --strict finds a Closes on an issue with an item not ticked (changes/early-close) |
FR-005 | check | bun test suite/ | mizan-changes-pure.test.ts: Refs and Closes on a line of their own, in this or another repository, two issues on two lines, prose and quoted lines not read; mizan-changes-git.test.ts: the commits of a real range |
FR-006 | check | bun test suite/ | mizan-changes-pure.test.ts: changes/early-close on a Closes whose items are not all ticked, none where all are; mizan-changes-git.test.ts: the command with --strict |
FR-007 | check | bun test suite/ | mizan-changes-pure.test.ts: changes/no-issue with the revision, a merge never reported itself, its parent that names none reported once, a revert reported; mizan-changes-git.test.ts: a real range with a merge and a revert, and default merge commits with no body judged by their parents |
FR-008 | check | bun test suite/ | mizan-changes-pure.test.ts: the closing words other than Closes are read wherever they stand and changes/closing-keyword reports them; mizan-changes-git.test.ts: a real commit that says Fixes |
FR-009 | check | bun test suite/ | mizan-changes-git.test.ts: --strict asks the host for each issue a commit names (this repository and another's) and finds unknown, closed and not-ticked ones; without --strict the host is never asked; mizan-changes-pure.test.ts: the rules over the answers |
FR-010 | check | bun test suite/ | mizan-changes-pure.test.ts: the declaration is typed data read and never run, its regulated domains are the code list's, a domain with no production day is refused (changes/declaration), a harness that states nothing is not regulated |
FR-011 | check | bun test suite/ | mizan-changes-pure.test.ts: warn before the declared day and gate from it, today included, and holdHarness never holds a gate finding by a baseline; mizan-changes-git.test.ts: the command holds warnings by changes.baseline.txt and fails a gate whatever it holds |
FR-012 | check | bun test suite/ | mizan-changes-git.test.ts: the history of a real declaration file gives changes/gate-relaxed for a day moved later after it passed, a day removed and a domain dropped, cleared only by a Decision that covers the revision; mizan-changes-pure.test.ts: the judgement over versions |
FR-013 | check | bun test suite/ | mizan-changes-pure.test.ts: rungsRequired gives rungs 9 and 10 from the declared day for a harness that claims a regulated domain, none otherwise; 0016-ladder FR-011 reads it |
FR-014 | check | bun test suite/ | ifccm-ontology.test.ts: the chain is six TraceStage individuals in order, each with the annotation that already links it |
FR-015 | check | bun test suite/ | mizan-changes-pure.test.ts: the chain of a requirement ends at the first stage with no link (term, code, test, run); mizan-changes-git.test.ts: the command --trace over the Done when of an issue body |
FR-016 | check | bun test suite/ | mizan-changes-pure.test.ts: the view of capabilities by rung is generated between the markers and its check fails where the document differs; mizan-changes-git.test.ts: the command writes it and --check fails where the document differs |
FR-017 | check | bun test suite/ | mizan-changes-pure.test.ts: a capability is open on a rung while a command of the rung has no passing run at its last revision, proved otherwise; mizan-changes-git.test.ts: the command |
FR-018 | check | bun test suite/ | ifccm-ontology.test.ts: the four AuthorityFunction individuals and the instrument that carries each |
FR-019 | check | bun test suite/ | mizan-changes-pure.test.ts: a departure (Departs:) with no Decision that names it, or naming one the harness does not record, is changes/no-decision; nothing of an issue's comment, label or state is read as authority |
FR-020 | check | bun test suite/ | mizan-changes-pure.test.ts: where a regulated domain is declared, a Decision approved by the role of the commit's author, or with the author's role not recorded, is changes/self-approved |
FR-021 | check | bun test suite/ | ifccm-ontology.test.ts: the kinds (capability request, problem) and states (open, closed) are the words the specification names, and a change request has exactly one kind, state and host |
FR-022 | check | bun test suite/ | ifccm-ontology.test.ts: a change names its change requests and revisions, a baseline its items and the Decision that establishes it |
FR-023 | check | bun test suite/ | ifccm-ontology.test.ts: ChangeRequest specializes oslc_cm:ChangeRequest, Change prov:Activity, ConfigurationItem prov:Entity and Baseline prov:Collection, each with its audit record |
FR-024 | check | bun test suite/ | ifccm-ontology.test.ts: the requirement names cm-2, cm-3, cm-4, cm-5 and cm-9 and the crosswalk row repeats them; the typed code list of the OSCAL controls is imported by the lead (0019-mizan-integrations FR-015) |
FR-025 | check | bun test suite/ | ifccm-ontology.test.ts: each crosswalk row has a relation SSSOM has and requirements that exist, the standards are there, and no clause is a term |
FR-026 | none | Not built in M2 of issue #10: that a DeviceQuality harness keeps its change records so that they can be handed over is a practice no check reads yet; the records of FR-021 to FR-023 are terms (ifccm-ontology.test.ts) and the Authority citation is held by mizan/authority-citation | |
FR-027 | check | bun test suite/ | ifccm-ontology.test.ts: the host kinds are the three of ifccm:GitManagerKind (Github, Gitlab, Git), and ifccm:hostedOn ranges over them |
FR-028 | check | bun test suite/ | mizan-changes-pure.test.ts: the files of the changes check reach a host only through GitHostClient and name no host API or URL; the adapters are M4's (the githost folder) |
FR-029 | none | Planned, M4 of issue #10 (the adapters): the adapters read a pull request and a merge request as part of a change and #N as the issue | |
FR-030 | check | bun test suite/ | mizan-changes-git.test.ts: --strict on plain Git is not_run with the reason that there is no host API, and so are no client given and an unreachable host; never passed |
FR-031 | check | bun test suite/ | quality-changes-record.test.ts (commons/quality/suite): each run of libraries/tools/changes.ts leaves a quality record with each rule as a case, each finding a failed case with rule, file and line, and each rule that could not run (strict on plain Git, no client, no --strict, no --range) not_run with its reason |
FR-032 | check | bun test suite/ | mizan-changes-pure.test.ts: the findings are Mizan findings (MizanRule, held by a baseline) and holdHarness runs the declaration rule as a plugin; mizan-changes-git.test.ts: the command runs as a program with its exit statuses; the commit rules need a range and are the command's |
FR-033 | check | bun test suite/ | mizan-changes-pure.test.ts: Departs and Decision lines are read from a commit and judged (changes/no-decision, changes/self-approved), and the record file's declaration, decisions and roles are read as data |
FR-034 | none | Planned, owner decision 2026-11-17 (issue #10): a repository with no Git host account may keep its change requests as a typed file in Git; not built | |
FR-035 | check | bun test suite/ | mizan-harness-requests.test.ts: on a real repository with no host, the capabilities of a range are the change requests the commits name, their requirements come from messages, spec diffs, a Done when and the Spec:/Proves: lines of changed files, and a commit naming only another repository is listed apart |
FR-036 | check | bun test suite/ | mizan-harness-requests.test.ts: the change requests as JSON, the terms as JSON or as a module loaded by the file URL of a path with a space (audit records too), the rungs with homes and the specs are read; a missing file, a module with no terms and a bad format are named; --trace reads --terms |
FR-037 | check | bun test suite/ | mizan-harness-requests.test.ts: each requirement's stages, the stage where its chain ends and its spec, terms, code and tests on each rung are given as a table and as JSON, the same bytes twice, with LF, and written to --output |
FR-038 | check | bun test suite/ | mizan-harness-requests.test.ts: the view of capabilities by rung is made from the commits between the markers of a document and --check finds no difference after it; the exit status is 1 for a closed capability whose chain stops before its run, 0 for an open one, 2 and 3 for usage and inputs |
FR-039 | review | 0032-libraries-by-concern FR-010 | kept by the library githost: githost 0001-githost FR-001 |
FR-040 | review | 0032-libraries-by-concern FR-010 | kept by the library githost: githost 0001-githost FR-002 |
FR-041 | review | 0032-libraries-by-concern FR-010 | kept by the library githost: githost 0001-githost FR-003 |
FR-042 | review | 0032-libraries-by-concern FR-010 | kept by the library githost: githost 0001-githost FR-004 |
FR-043 | review | 0032-libraries-by-concern FR-010 | kept by the library githost: githost 0001-githost FR-005 |
FR-044 | review | 0032-libraries-by-concern FR-010 | kept by the library githost: githost 0001-githost FR-006 |
FR-045 | check | bun test suite/ | mizan-changes-pure.test.ts: an Impact line is read as major, minor or patch in any case, and one that is none of the three is changes/impact with its value, a warning or a gate by the phase |
FR-046 | check | bun test suite/ | mizan-changes-git.test.ts: in a real Git repository a commit with no Refs fails and the same range passes with a Decision that covers its revision (full or by a 7-character prefix), and a different commit is not covered; mizan-changes-pure.test.ts: the entry syntax, the person, day and reason |
FR-047 | check | bun test suite/ | mizan-changes-git.test.ts: the command reports the exempted commit as covered with the Decision, the person, the day and the reason, and still reports the commit it does not name |
FR-048 | check | bun test suite/ | mizan-changes-pure.test.ts and mizan-changes-git.test.ts: a Decision with no person, a role, no day or reason, a malformed entry, a revision outside the range, an ambiguous prefix or a commit that names an issue is changes/decision, and exempts nothing |
0021 Intellectual Frontiers Quality System
| Requirement | Mechanism | Who | Note |
|---|---|---|---|
FR-001 | none | Planned, M3 of issue #10: a principle held by the requirements under it: what runs is graded above what is stated (FR-021); the grade list exists (ifqs-ontology.test.ts) | |
FR-002 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-011 |
FR-003 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-012 |
FR-004 | none | Planned, M9 of issue #10: the generator of the public page is built (quality-trust.test.ts, `quality trust`) and the pack is the form an assessor gets on request (quality-pack.test.ts); commons' own page is published with the documentation site by 0022-trust FR-006, which is not yet | |
FR-005 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-013 |
FR-006 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-014 |
FR-007 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-015 |
FR-008 | check | bun test suite/ | ifqs-ontology.test.ts: each crosswalk row has a relation SSSOM has and requirements that exist, and the standards the specification is held to are there |
FR-009 | none | Planned, M3 of issue #10: the test record is kept as the objective evidence of verification for a harness that claims ifccm:DeviceQuality; the Authority citation is held by mizan/authority-citation | |
FR-010 | check | bun test suite/ | ifqs-ontology.test.ts: the requirement names ca-2, ca-5, ca-7, sa-11 and si-2 by their OSCAL identifiers |
FR-011 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-016 |
FR-012 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-017 |
FR-013 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-018 |
FR-014 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-019 |
FR-015 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-020 |
FR-016 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-021 |
FR-017 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-022 |
FR-018 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-023 |
FR-019 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-024 |
FR-020 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-025 |
FR-021 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-026 |
FR-022 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-027 |
FR-023 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-028 |
FR-024 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-029 |
FR-025 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-030 |
FR-026 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-031 |
FR-027 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-032 |
FR-028 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-033 |
FR-029 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-034 |
FR-030 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-035 |
FR-031 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-036 |
FR-032 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-037 |
FR-033 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-038 |
FR-034 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-039 |
FR-035 | none | Planned, M3 of issue #10: the layers check holds rung 9 as an observer once 0016-ladder amends the ladder | |
FR-036 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-040 |
FR-037 | none | The quality console is a harness's own user interface and is not built in commons: its data is the index (`quality index`) and the JSON of the page (`quality trust --audience internal`), each figure with its evidence file (FR-019); Planned, a harness's console | |
FR-038 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-041 |
FR-039 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-042 |
FR-040 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-043 |
FR-041 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-044 |
FR-042 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-045 |
FR-043 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-046 |
FR-044 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-047 |
FR-045 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-048 |
FR-046 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-049 |
FR-047 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-050 |
FR-048 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-051 |
0022 Trust
| Requirement | Mechanism | Who | Note |
|---|---|---|---|
FR-001 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-052 |
FR-002 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-053 |
FR-003 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-054 |
FR-004 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-055 |
FR-005 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-056 |
FR-006 | none | Planned, M9 of issue #10: the page is generated; its publication with the documentation site of commons (0011-documentation) waits for a quality branch of commons' own to publish and the lead's docs build | |
FR-007 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-057 |
FR-008 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-058 |
FR-009 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-059 |
FR-010 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-060 |
FR-011 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-061 |
FR-012 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-062 |
FR-013 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-063 |
FR-014 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-064 |
FR-015 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-065 |
FR-016 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-066 |
FR-017 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-067 |
FR-018 | review | 0032-libraries-by-concern FR-010 | kept by the library quality: 0001-quality-evidence FR-068 |