Description
Record an ordered pair of explicitly supplied discourse-role codes.
Critical annotations distinguish source voices, editorial insertions, omission markers, edition locators and caller-assigned interpretations. Case preservation and half-open text offsets describe representation rather than meaning. A bracketed token or source-role label does not verify faithful quotation, authority, an argument or its historical context.
Record an ordered pair of explicitly supplied discourse-role codes.
When to use this tool
Use Discourse Role Caller Code Pair when you already have passageId, firstRole, secondRole and need to record an ordered pair of explicitly supplied discourse-role codes.
How to use the tool and how it works
- Enter passageId, firstRole, secondRole. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter passageId, firstRole, secondRole using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| passageId | Passage Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| firstRole | First Role | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| secondRole | Second Role | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"passageId": "P17",
"firstRole": "speaker",
"secondRole": "addressee"
},
"output": {
"token": "[\"P17\",\"speaker\",\"addressee\"]"
}
}Limitations and assumptions
- The result records supplied values without deriving power or identity claims. Sources and asserted relationships are not independently authenticated.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Read the original passage and relevant edition with the stated interpretive and editorial conventions. Verify source context and attribution before reuse; local span labels and interpretation-objection pair keys organize records without evaluating the argument or granting quotation rights.
References
Similar or alternative tools
- Editorial Normalization Disclosure Tag
Record an explicit editorial normalization disclosure.
- Historical Label Use Date Precision
Preserve a historical term-use date transcription and explicit precision.