Skip to content

fix(ontology): preserve singleton relations across export pages #934

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
seonghobae wants to merge 6 commits into
base: fix/voice-export-authority-20260828
Choose a base branch
from
Draft

fix(ontology): preserve singleton relations across export pages #934

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
0538425
fix(ontology): retain singleton relationships in paged exports
Sep 5, 2026
0b36ea0
docs(gaps): record exact implementation and bounded runtime evidence
Sep 5, 2026
7ed5a41
docs(gaps): record verified activity review repair
Sep 5, 2026
6beed92
test(ontology): pin order-insensitive JSON-LD continuation dedup
seonghobae Sep 5, 2026
eae1e72
fix(ontology): deduplicate JSON-LD values structurally
seonghobae Sep 5, 2026
3060dd7
docs(adr): trace JSON-LD continuation identity
seonghobae Sep 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions docs/adr/0256-evidence-bearing-voice-combinations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,18 @@ attributes rather than from one exhaustive industry-role list.

## Decision

Continuation clarification (2026-09-05): accumulating authorized pages retains
every value of a repeated JSON-LD subject property, whether represented as a
single value or an array. Repeated values are deduplicated; a later fragment
must not replace an earlier relationship, type, or label. JSON object member
order is not part of value identity, consistent with RFC 8259's unordered
object model, so equivalent node/value objects remain one value when a later
page serializes their members in a different order. The accumulator preserves
JSON array sequence rather than pretending to perform full JSON-LD expansion,
set normalization, or RDF canonicalization. This implements ADR 0184's export
parity under the W3C JSON-LD 1.1 node-object contract without changing
authorization, truth, cutoff, or Voice assignment identity.

Represent composition as rows in normalized `source_post_voice`, not as
compound lookup codes.

Expand Down Expand Up @@ -155,6 +167,10 @@ release claim still requires protected-main delivery evidence.
AccountAbility. (2015). *AA1000 stakeholder engagement standard*.
https://www.accountability.org/standards/aa1000-stakeholder-engagement

Bray, T. (2017). *The JavaScript Object Notation (JSON) data interchange
format* (RFC 8259). Internet Engineering Task Force.
https://www.rfc-editor.org/rfc/rfc8259

International Organization for Standardization. (2010). *Guidance on social
responsibility* (ISO Standard No. 26000:2010).
https://www.iso.org/standard/42546.html
Expand All @@ -167,3 +183,7 @@ Mitchell, R. K., Agle, B. R., & Wood, D. J. (1997). Toward a theory of
stakeholder identification and salience: Defining the principle of who and
what really counts. *Academy of Management Review, 22*(4), 853–886.
https://doi.org/10.5465/amr.1997.9711022105

World Wide Web Consortium. (2020). *JSON-LD 1.1: A JSON-based serialization
for linked data* (W3C Recommendation).
https://www.w3.org/TR/json-ld11/
Loading
Loading