Description
Preserve an explicit community-approval version-date record.
Community-supplied names, credits, permissions and source versions carry their own authority and context. A recorded access or precision label does not itself grant permission or hide a location. Preserving requested wording and attribution order is distinct from authenticating rights, community approval or adequate protection.
Preserve an explicit community-approval version-date record.
When to use this tool
Use Community Approval Version Date Pair when you already have approvalReference, suppliedVersion, recordedDateText and need to preserve an explicit community-approval version-date record.
How to use the tool and how it works
- Enter approvalReference, suppliedVersion, recordedDateText. 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 approvalReference, suppliedVersion, recordedDateText 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 |
|---|---|---|
| approvalReference | Approval Reference | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| suppliedVersion | Supplied Version | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| recordedDateText | Recorded Date Text | 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": {
"approvalReference": "APP17",
"suppliedVersion": "v2",
"recordedDateText": "2026-11-01"
},
"output": {
"token": "[\"APP17\",\"v2\",\"2026-11-01\"]"
}
}Limitations and assumptions
- The result records supplied values without verifying or granting approval. 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
Consult the original community-provided permissions, attribution instructions and controlled records for actual use. Apply access and location protection to the underlying material, rather than treating a display mask or status label as the complete safeguard.
References
Similar or alternative tools
- Community Resource Explicit Access Date
Preserve explicit community-resource access-date and permission-reference metadata.
- Community Preferred Name Period Label
Preserve an explicitly supplied community preferred-name and period label.