Description
Preserve explicit knowledge-record assertion time and valid-time bounds.
Information records distinguish identifiers, controlled vocabularies, language fallbacks, assertion times and valid times. A supplied inverse predicate differs from an inferred semantic relation. Text offsets require an explicit code-point or code-unit basis, and a metadata count check does not validate field content or an entire schema.
Preserve explicit knowledge-record assertion time and valid-time bounds.
When to use this tool
Use Knowledge Record Validtime Assertion Pair when you already have recordId, assertionTimeText, validStartText, validEndText and need to preserve explicit knowledge-record assertion time and valid-time bounds.
How to use the tool and how it works
- Enter recordId, assertionTimeText, validStartText, validEndText. 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 recordId, assertionTimeText, validStartText, validEndText 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 |
|---|---|---|
| recordId | Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| assertionTimeText | Assertion Time Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| validStartText | Valid Start Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| validEndText | Valid End 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": {
"recordId": "R17",
"assertionTimeText": "2026-11-01",
"validStartText": "2025-01-01",
"validEndText": "2025-12-31"
},
"output": {
"token": "[\"R17\",\"2026-11-01\",\"2025-01-01\",\"2025-12-31\"]"
}
}Limitations and assumptions
- The result records supplied values without conflating transaction and valid time. 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
Use the actual record, vocabulary authority and complete metadata schema for semantic or conformance questions. Apply the identifier scheme's real comparison rules and the intended language/offset policy rather than inferring them from a local string operation.
References
Similar or alternative tools
- Metadata Language Script Pair
Preserve explicit metadata language and script tags.
- Metadata Controlled Value Source Key
Qualify a literal controlled metadata value by its supplied vocabulary source.