Description
Pair explicit agreement and translation version identifiers.
Treaty and diplomatic records separate action labels, recorded conditions, versions, source locators and financial contributions. A set of true condition flags differs from a verified legal act or entry into force. Dates and translations need the authoritative record and applicable definitions before legal interpretation.
Pair explicit agreement and translation version identifiers.
When to use this tool
Use Public Agreement Translation Version Pair when you already have agreementId, sourceVersion, translatedVersion and need to pair explicit agreement and translation version identifiers.
How to use the tool and how it works
- Enter agreementId, sourceVersion, translatedVersion. 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 agreementId, sourceVersion, translatedVersion 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 |
|---|---|---|
| agreementId | Agreement Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| sourceVersion | Source Version | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| translatedVersion | Translated Version | 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": {
"agreementId": "AGR17",
"sourceVersion": "v2",
"translatedVersion": "tr-v2"
},
"output": {
"token": "[\"AGR17\",\"v2\",\"tr-v2\"]"
}
}Limitations and assumptions
- The result records supplied values without generating or authenticating translations. 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
Check the original treaty, notice, authentic text and status record when assessing an obligation or effective act. Reconcile full contribution ledgers and condition evidence; a local count, share or source-qualified key does not establish legal effect.
References
Similar or alternative tools
- Treaty Notice Received Dispatched Date Pair
Preserve explicit treaty-notice dispatch and receipt date wording.
- Agreement Article Paragraph Citation
Build an explicit agreement article-paragraph citation key.