Skip to content

Open semantic locator/sort vocabularies; document JSON-LD hashing and collaboration rendering#74

Merged
gvonnessi merged 1 commit into
mainfrom
phase6d-semantic-collab-prose
Jun 28, 2026
Merged

Open semantic locator/sort vocabularies; document JSON-LD hashing and collaboration rendering#74
gvonnessi merged 1 commit into
mainfrom
phase6d-semantic-collab-prose

Conversation

@gvonnessi

Copy link
Copy Markdown
Collaborator

Summary

  • Open the citation locatorType and glossary sort fields from closed enums to open strings with RECOMMENDED lists, so a non-enumerated locator or sort order is preserved rather than rejected (open-world, mirroring the earlier enum relaxations). +2 schema-closure vectors.
  • Document that a block-level JSON-LD semantic annotation is hashed as opaque JSON: object key order is normalized by JCS, but JSON-LD equivalences beyond it (compaction/expansion, @context phrasing, unordered-@set ordering) are not preserved across document IDs.
  • Document the semantic:ref internal/external rule (an external target MUST set external: true; an internal target is a Content Anchor URI).
  • Pin collaboration rendering with RFC 2119: replies render in created order, duplicate reactions collapse, a resolved comment is distinguished but not silently dropped, and resolved/replies apply to comment and suggestion records only.

Test plan

  • All 19 validation gates pass from a clean npm ci.
  • Document ids and manifest projections unchanged — opening the enums is validation-only; the example's in-enum locatorType/sort values are unchanged.

…and collaboration rendering

Open the citation locatorType and glossary sort fields from closed enums to
open strings with recommended lists, so a non-enumerated locator or sort order
is preserved rather than rejected; add schema-closure vectors for both.

Document that a block-level JSON-LD annotation is hashed as opaque JSON — object
key order is normalized by JCS, but JSON-LD equivalences beyond it (compaction,
context phrasing, unordered-set ordering) are not preserved across document IDs
— and that a semantic cross-reference must declare external for an
out-of-document target.

Pin collaboration rendering with RFC 2119: replies render in created order,
duplicate reactions collapse, a resolved comment is distinguished but not
dropped, and the resolved/replies fields apply to comment and suggestion
records only.
@gvonnessi gvonnessi merged commit a6bcde2 into main Jun 28, 2026
2 checks passed
@gvonnessi gvonnessi deleted the phase6d-semantic-collab-prose branch June 28, 2026 21:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant