Description
Construct escaped caller edit fragments using ins/del/s annotations with an explicit before/after ledger and lexical tag keys, without assigning legal meaning.
A protocol fixture is local test data representing headers, messages, identifiers, or request decisions. Serialization and parsing can be checked without contacting a server, while authentication, delivery, and actual client behavior require separate tests.
Construct escaped caller edit fragments using ins/del/s annotations with an explicit before/after ledger and lexical tag keys, without assigning legal meaning.
When to use this tool
Use this generator to create reproducible semantic edit markup fixture cases from the supplied model or bank. Inspect the returned evidence before using cases in a test or exercise.
How to use the tool and how it works
- Supply fragments, kinds, count in the field shapes below. Set seed when you need an explicit replay.
- Run the tool and correct any input error. For generated controls, distinguish a successful fixture containing an invalid case from failure to generate the fixture.
- Read ledger, beforeText, afterText, html. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.
Sample edit fragments and insertion, deletion, replacement, or obsolete modes. Serialize escaped text inside ins, del, or s tags with data-edit indexes, parse the opening tags, and concatenate beforeText and afterText from the ledger.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| fragments | Fragments | Required. Array of Object; no unknown keys.; minimum items 1; maximum items 32. |
| fragments[].before | Before | Required. Text; maximum UTF-16 length 256. |
| fragments[].after | After | Required. Text; maximum UTF-16 length 256. |
| kinds | Kinds | Required. Array of Text; one of "replacement", "insertion", "deletion", "obsolete".; minimum items 1; maximum items 4. |
| count | Requested count; the mechanics explain whether one draw expands into several returned records. | Required. Safe integer; minimum 1; maximum 32. |
| seed | Optional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed. | Optional. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| ledger | Ledger | Required. Array of Object; no unknown keys.; minimum items 1; maximum items 32. |
| ledger[].index | Index | Required. Safe integer; minimum 0; maximum 31. |
| ledger[].kind | Kind | Required. Text; one of "replacement", "insertion", "deletion", "obsolete". |
| ledger[].suppliedBefore | Supplied Before | Required. Text; maximum UTF-16 length 256. |
| ledger[].suppliedAfter | Supplied After | Required. Text; maximum UTF-16 length 256. |
| ledger[].before | Before | Required. Text; maximum UTF-16 length 256. |
| ledger[].after | After | Required. Text; maximum UTF-16 length 256. |
| ledger[].markup | Markup | Required. Text; maximum UTF-16 length 131072. |
| ledger[].tags | Tags | Required. Array of Object; no unknown keys.; minimum items 1; maximum items 2. |
| ledger[].tags[].name | Name | Required. Text; maximum UTF-16 length 256. |
| ledger[].tags[].attributes | Attributes | Required. Array of Object; no unknown keys.; minimum items 0; maximum items 16. |
| ledger[].tags[].attributes[].name | Name | Required. Text; maximum UTF-16 length 256. |
| ledger[].tags[].attributes[].value | Value | Required. Text; maximum UTF-16 length 2048. |
| beforeText | Before Text | Required. Text; maximum UTF-16 length 8192. |
| afterText | After Text | Required. Text; maximum UTF-16 length 8192. |
| html | Html | Required. Text; maximum UTF-16 length 131072. |
| randomness | Replay metadata: source is seed or context; seed is the normalized 32-bit seed or null for a context source. | Required. Object; no unknown keys. |
| randomness.seed | Optional numeric replay seed; normalization and precedence are explained below. | Required. Safe integer. or Null. |
| randomness.source | Source | Required. Text; one of "context", "seed". |
An explicit safe-integer seed takes precedence over injected context randomness and is normalized to an unsigned 32-bit integer. With no seed and no context source, replay uses the fixed tool.io default seed. A context source must return finite values from zero inclusive to one exclusive; its advancing state must be retained separately. randomness records the source and normalized seed, or null for context. These generators are not cryptographic random sources.
{
"input": {
"fragments": [
{
"before": "Old",
"after": "New"
},
{
"before": "Draft",
"after": "Final"
}
],
"kinds": [
"replacement",
"insertion",
"deletion",
"obsolete"
],
"count": 1,
"seed": 42
},
"output": {
"ledger": [
{
"index": 0,
"kind": "insertion",
"suppliedBefore": "Draft",
"suppliedAfter": "Final",
"before": "",
"after": "Final",
"markup": "<ins data-edit=\"0\">Final</ins>",
"tags": [
{
"name": "ins",
"attributes": [
{
"name": "data-edit",
"value": "0"
}
]
}
]
}
],
"beforeText": "",
"afterText": "Final",
"html": "<ins data-edit=\"0\">Final</ins>",
"randomness": {
"seed": 42,
"source": "seed"
}
}
}Limitations and assumptions
- Obsolete text remains in both text views, unlike deletion. Markup is synthetic semantic-edit evidence, not a browser diff or a general HTML sanitizer; supplied originals remain available separately.
- A replay requires the same complete input and implementation. Randomized construction does not guarantee uniform coverage of every feasible output; finite samples can repeat unless a distinct-selection rule is explicitly stated.
- The field tables state structural bounds; cross-field constraints and bounded search or output budgets also apply. Unknown keys are rejected where the object contract disallows them. Input errors are distinct from null fields and deliberate invalid controls in a successful output.
Alternative or Complementary methods
For a supplied example, inspect the returned construction or delegated check directly. To evaluate a consumer, also test cases chosen for its own boundaries; a generated finite corpus does not establish exhaustive coverage.
References
Similar or alternative tools
- Random HTML Attribute Quoting Corpus Generator
Compose bounded benign start-tag source with caller text, delegated five-character entity escaping, feasible double/single/unquoted/Boolean attribute forms, and duplicate attributes; retain the lexical parser's raw character references and first-duplicate rule, not DOM-decoded values, sanitization, or HTML conformance certification.
- Random HTML Boolean Attribute Fixture Generator
Construct supported Boolean-attribute spellings with lexical parser outputs, separate presence-based interpretation and author-spelling keys, including the nonconforming false-value control.