itut-drafting

# ITU-T Contribution Drafting Use this skill for ITU-T-specific document structure, template conventions, and concrete Word style names. For formatting rules (headings, enumerations, notes, tables, figures, citations), see `sdo-docx-formatting`. For officecli operations (tab-run injection, field codes, bookmarks), see `sdo-docx-operations`. ## Critical rules from delegated skills These key constraints are inlined here to reduce cross-referencing: **From `sdo-docx-formatting`:** - Apply formatting through **named styles** from the template, never manual overrides (bold, italic, font size, colour). - Keep numbering **update-safe** — use SEQ fields and bookmarks, never hard-coded numbers. - Use **non-breaking spaces** (`\u00a0`) for semantic units (number+unit, Figure/Table+number). - Use **real tab runs** (`<w:tab/>`), never spaces, for structural tabs (heading number+title, enumeration bullet+text, note label+text). **From `sdo-docx-operations`:** - Open in resident mode (`officecli open <doc>`) before multi-step edits; close at end. - Prefer style/ordinal or explicit XPath targeting, not paraId targeting. - Never use `raw-set --action replace` with an empty XML payload. - Always preserve non-breaking spaces and explicit tab runs. - Validate with `officecli validate <doc>` after every major batch update. ## Assets - `assets/template.docx` -- canonical ITU-T contribution Word template with all required styles and header structure (9-row header table, abstract table, running header, footer). Copy or use as reference when starting a new contribution. This is a user-provided template carrying ITU-T branding, predefined styles, and placeholder content. Do **not** modify the original; always work on a copy. - `assets/itu-t-sg12-contribution-template.docx` -- downloaded official ITU-T contribution template (SG12 example) for reproducible offline use. - `assets/itu-t-sg12-liaison-statement-template.docx` -- downloaded official ITU-T Liaison Statement template (SG12 example) for drafting outgoing LS documents. - `../itut-recommendations/assets/itu-t-recommendation-skeleton.docx` -- downloaded official ITU-T Recommendation skeleton for style-baseline checks. ## Canonical ITU-T template sources (online) These are the upstream sources for the downloaded assets above: - Contribution template (example SG12): `https://www.itu.int/dms_pub/itu-t/oth/0A/0F/T0A0F00002F0012MSWE.docx` - Liaison Statement template (example SG12): `https://www.itu.int/dms_pub/itu-t/oth/0A/0F/T0A0F00000B0006MSWE.docx` - New Recommendation skeleton (latest Word styles baseline): `https://www.itu.int/en/ITU-T/studygroups/Documents/Doc-ITUT-Recs-Skelet.docx` ### Template selection rule - For **meeting contributions**: start from `assets/itu-t-sg12-contribution-template.docx`. - For **outgoing Liaison Statements**: start from `assets/itu-t-sg12-liaison-statement-template.docx`. - For **Recommendation drafting or style refresh checks**: use `../itut-recommendations/assets/itu-t-recommendation-skeleton.docx` to confirm style definitions (including appendix and bibliography headings). - Use the online URLs only to refresh these local files when needed. ______________________________________________________________________ ## ITU-T style-name mapping Concrete Word style IDs for ITU-T documents. Use these when applying formatting rules from `sdo-docx-formatting`. | Abstract name (`sdo-docx-formatting`) | ITU-T concrete style ID | Notes | |---|---|---| | `body-text` | `Body Text` | If absent, fall back to `Normal`; verify with `officecli get <doc> /styles` | | `heading-1` | `Heading 1` | Section headings (numbered) | | `heading-2` | `Heading 2` | Subsection headings | | `heading-3` | `Heading 3` | Sub-subsection headings | | `enum-1` | `enumlev1` | First-level enumeration | | `enum-2` | `enumlev2` | Second-level enumeration | | `enum-3` | `enumlev3` | Third-level enumeration (if used) | | `table-caption` | `Table_No & title` | officecli styleId: `TableNotitle` | | `table-header` | `Table_head` | officecli styleId: `Tablehead` | | `table-data` | `Table_text` | officecli styleId: `Tabletext` | | `table-note` | (varies by template) | If not found in template, omit styling and add a TODO comment for manual review | | `figure-para` | `Figure` | Paragraph containing image | | `figure-caption` | `Figure_No & title` | Below figure | | `figure-note` | (varies by template) | If not found in template, omit styling and add a TODO comment for manual review | | `note-main` | `Note` | Last note in block | | `note-continuation` | (varies by template) | If not found in template, omit styling and add a TODO comment for manual review | | `reference-entry` | `References` | Each references entry (normative references *and* bibliography entries) | | `appendix-heading` | `Appendix_No & title` | Non-integral (informative) appendix headings | | `bibliography-heading` | `Appendix_No & title` | Bibliography clause heading (same style as appendix) | | `code-text` | `Macro Text` | officecli styleId: `MacroText` | Additional ITU-T-specific styles (no abstract equivalent): | Style ID | Purpose | |----------|---------| | `Equation` | Display equation paragraph (centred equation + right-aligned label via tab stops) | | `Equation_legend` | officecli styleId: `Equation_legend` -- annotation paragraph following equation | | `Headingb` | Sub-headings within a proposed clause block (not auto-numbered) | | `TSBHeaderSummary` | Abstract table cell content | ______________________________________________________________________ ## Bibliography clause The **Bibliography** is an optional, non-normative clause that lists informative references. It appears as the **very last element** of a Recommendation, after all integral and non-integral annexes. ### Three mandatory rules — never drop any of them 1. **Heading style** — Use style `Appendix_No & title` (abstract: `bibliography-heading`), **not** `Heading 1`. The Bibliography is a non-integral appendix in ITU-T, so it shares the appendix heading style. Write the heading text as `Bibliography` without a number prefix. 2. **Page break before heading** — Insert a page break immediately before the `Bibliography` heading paragraph. Apply it as a paragraph property (`w:pageBreakBefore` = `true`, or `pageBreakBefore: true` in the officecli `set` command) on the heading paragraph itself — **do not** insert a separate empty paragraph with a manual page break. ```json { "command": "set", "path": "/body/p[<bibliography-heading-ordinal>]", "props": { "style": "Appendix_No & title", "pageBreakBefore": true, "text": "Bibliography" } } ``` 3. **Entry style** — Each bibliography entry uses style `References` (abstract: `reference-entry`) — the **same** style as normative reference entries in clause 2. Do not use `Body Text`, `Normal`, or any other style for bibliography entries. ### Entry format Format identical to normative references: ```text [N]\t<citation text> ``` - Square-bracket-wrapped `{SEQ Ref \* ARABIC}` field (no hard-coded number). - Real `<w:tab/>` run between the bracket and the citation text. - Bookmark `ref_<short_name>` around the sequence field only. - Style: `References` on every entry paragraph. ### Common agent failure modes | Mistake | Correct behaviour | |---------|-------------------| | Using `Heading 1` for the Bibliography heading | Use `Appendix_No & title` | | Omitting the page break before Bibliography | Set `pageBreakBefore: true` on the heading paragraph | | Styling entries with `Body Text` or `Normal` | Apply `References` style to every entry | | Hard-coding `[1]`, `[2]` as plain text | Use `{SEQ Ref \* ARABIC}` field with bookmark | ______________________________________________________________________ ## Template structure ITU-T contribution documents use a structured header **table** (not paragraphs). This differs from 3GPP. ### Header table (`/body/tbl[1]`) 9 rows with the following cell layout: | Row | Cell | Content | |-----|------|---------| | tr[1]/tc[3] | Document number | 3rd run is the highlighted placeholder; set text to `0xxx` | | tr[4]/tc[2] | Question(s) | e.g. `Question 9/12` | | tr[4]/tc[3] | Place and date | e.g. `Geneva, 09-17 June 2026` | | tr[6]/tc[2] | Source organization | e.g. `HEAD acoustics GmbH` | | tr[7]/tc[2] | Title | Contribution title | | tr[8]/tc[2] | Contact 1 | Tab-separated: `Name\tOrganization\tCountry` | | tr[8]/tc[3]/p[1]/r[4] | Tel number | Highlighted run | | tr[8]/tc[3]/p[1]/r[8] | E-mail | Highlighted run | | tr[9] | Contact 2 | Clear with `""` if unused | ### Abstract table (`/body/tbl[2]`) 1 row x 2 cells: `"Abstract:"` label (tc[1]) + content (tc[2]/p[1]). ### Running header `/header[1]/p[@paraId=00100052]/r[4]` -- document number (e.g. `SG12-C0xxx`). ### Instruction paragraphs to delete Remove all 8 yellow-highlighted instruction paragraphs (paraIds `0010003A` through `00100048`) using `remove` commands in a setup batch before adding content. ### Horizontal rule `/body/p[@paraId=0010004C]` -- `_______________________` separator. ### First content paragraph `/body/p[@paraId=0010004E]` -- empty paragraph after the rule; first content goes after this. > **Key finding:** The ITU-T template may NOT contain a `Body Text` style. > If absent, use `Normal` for body paragraphs. Always verify with > `officecli get <doc> /styles --depth 1` on any new template. ______________________________________________________________________ ## Liaison Statement template structure The LS template (`assets/itu-t-sg12-liaison-statement-template.docx`) uses an 11-row header table. This differs from the contribution template above. ### Header table (`/body/tbl[1]`) | Row | Cell | Content | Style | |-----|------|---------|-------| | tr[1]/tc[2] | Question(s) | e.g. `4/12` | `TSBHeaderQuestion` | | tr[1]/tc[4] | Meeting | e.g. `Geneva, 9-17 June 2026` | `VenueDate` (right-aligned) | | tr[2]/tc[2] | Study Group | e.g. `12` | `Normal` | | tr[2]/tc[4] | Working Party | e.g. `WP1/12` | `Normal` | | tr[3]/tc[2] | Source | e.g. `ITU-T Study Group 12` | `TSBHeaderSource` | | tr[4]/tc[2] | Title | LS title | `TSBHeaderTitle` | | tr[5] | "LIAISON STATEMENT" banner | merged across all 6 columns, centred | `Normal` + bold | | tr[6]/tc[2] | For action to | e.g. `ITU-T Q10/21` | `LSForAction` |