Specification v1.1: clause 11 change operations, Annex E business interchange

[ronaldtse]

CC 36010 v1.1: change operations + Annex E business interchange

Companion to metanorma/basicdoc-models#61
(Change operations v1.1). Together they answer two TC 154 questions
on the document:

1. How are fine-grained operations on tables and computed content
   exchanged? — clause 11 gains the whole table-change family with
   grid coordinates that account for colspan/rowspan, plus a
   computed-content clause covering formulas in cells.
2. How does change ordering relate to concurrent editing? — clause
   11 gains an Ordering-and-concurrent-changes clause that states the
   boundary plainly: changes are operation records; parentIdentifier
   carries the causal DAG; OT/CRDT/diff algorithms are out of scope,
   the same neutrality as serialization.

Clause 11 additions

• Addressing model (foundational, after General): three addressing
  modes (identifier reference, ordinal position, text cursor range);
  multi-valued slot semantics; the SHOULD note that change targets
  carry an id register entry.
• NodePosition entry; NodeInsert gains the +position
  attribute.
• Table changes ([[table-changes]]): the full family
  (RowInsert/Delete/Move, ColumnInsert/Delete/Move,
  CellUpdate/Merge/Split) with grid semantics that account for
  colspan/rowspan. New TableChanges.png embedded (from the model
  repo).
• Computed content ([[computed-content]]): formula blocks as
  cells; notation via stemType and the scheme register key;
  evaluation, reference resolution and recompute are out of scope.
• Ordering and concurrent changes ([[ordering]]): changes are
  operation records; parentIdentifier carries the causal DAG; how
  concurrent operations transform against each other (OT, CRDT,
  diff/patch) is out of scope, the same neutrality pattern as
  serialization.

A relation to in-document change markup (AmendBlock) is recorded in
the General clause.

Annex E (new, informative)

sources/sections/ae-business-interchange.adoc — worked commercial
document (purchase order) mapping and revision-round story. The
worked instance lives alongside the model as
examples/business-document.yaml (validated by rake fixtures:yaml).
Nothing in this annex adds a construct to the model — everything
shown is ordinary BasicDocument content, register entries, and
changes. This is the TC 154 positioning answer: business documents
are a first-class application of the generic base, like ISO 8601 is
generic time that commerce profiles.

Annex D extension

• Added the change-operations conformance class row.
• Extended the test-material paragraph to name the business instance
  and the change twin.

Intro and scope positioning

sources/sections/00-intro.adoc adds a paragraph on business document
interchange and cites ISO 8601 and ISO 6523 as the element standards
this complements. 01-scope.adoc adds an informative pointer to
Annex E.

Bibliography

ISO 6523 and ISO 9735 added (informative) for the intro paragraph.

Cover changes (cc-36010.adoc)

:edition: 1
→ :edition: 1.1
:revdate: 2026-08-31
→ :revdate: 2026-09-07
:published-date: 2026-08-31
→ :published-date: 2026-09-07

:status: published retained.

Publication staging — these cover values reflect a published
v1.1 directly on merge. If CalConnect policy requires a draft round
before publication, the commit can be amended before merge to flip
:status: published → :status: draft (and reset
published-date); say the word. The ISO copy
(iso-36010.adoc) is left at docstage: 40 / docsubstage: 00
(DIS) per the current fast-track status; Annex E is included so the
DIS copy renders the same content, but its cover is untouched.

Submodule pin coordination

sources/basicdoc-models is advanced to the models PR branch tip
cfe50c1 so the new TableChanges.png resolves in this PR's build.
When models PR #61 merges, a follow-up commit will advance the pin to
the merged main SHA before the final CC 36010 v1.1 publication.

Gates

The model half (PR #61) ran rake check, rake fixtures,
rake profiles green. This repo's CI
(.github/workflows/generate.yml) builds both cc-36010 and iso-36010
via metanorma-generate against the advanced submodule.