Description
Qualify an explicit certificate scope identifier by version.
Regulatory records tie submissions, source versions, jurisdictions, certificates and deadline wording together. Recorded approval and certificate scope are assertions that need the authoritative record and applicable rules. A calendar margin or supplied exchange factor can support bookkeeping without determining a lawful deadline, actual authorization or fee obligation.
Qualify an explicit certificate scope identifier by version.
When to use this tool
Use Regulatory Certificate Scope Key when you already have certificateId, scopeCode, version and need to qualify an explicit certificate scope identifier by version.
How to use the tool and how it works
- Enter certificateId, scopeCode, version. 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 certificateId, scopeCode, version 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 |
|---|---|---|
| certificateId | Certificate Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| scopeCode | Scope Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| version | 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": {
"certificateId": "CERT17",
"scopeCode": "SCOPE2",
"version": "v2"
},
"output": {
"token": "[\"CERT17\",\"SCOPE2\",\"v2\"]"
}
}Limitations and assumptions
- The result records supplied values without authenticating certification. 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 authoritative submission, certificate, fee schedule and applicable deadline rules for an actual obligation or status. Reconcile controlled document versions and jurisdiction before using one label, date gap or exchange-factor product in a filing workflow.
References
Similar or alternative tools
- Regulatory Document Sequence Token
Qualify an explicit submission sequence string by authority namespace.
- Product Registration Country Code
Qualify an explicit registration country code by its supplied code source.