Description
Split a section reference using the longest explicitly permitted prefix.
A regulatory record check applies a supplied rule to labels, dates, identifiers, or amounts. Exact matches and clock boundaries matter, but a consistent record does not itself establish legal compliance. The governing jurisdiction, rule version, and authoritative evidence must be selected separately.
Split a section reference using the longest explicitly permitted prefix.
When to use this tool
Use it for dossier section reference prefix token when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter reference, allowedPrefixes. Keep parallel arrays aligned and use the stated units and conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read prefix, remainder. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Keep nonempty allowedPrefixes matching the start of reference, choose the longest, and return that prefix and remaining text. Reject a reference with no permitted match.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| reference | Reference | Required. Text; maximum UTF-16 length 8192. |
| allowedPrefixes | Allowed Prefixes | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| prefix | Prefix | Required. Text; maximum UTF-16 length 8192. |
| remainder | Remainder | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"reference": "3.2.S.4",
"allowedPrefixes": [
"3.",
"3.2."
]
},
"output": {
"prefix": "3.2.",
"remainder": "S.4"
}
}Limitations and assumptions
- This is literal startsWith matching, not token-boundary matching or directory traversal validation. Supplied prefixes determine the interpretation rather than a regulatory section registry.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For dossier section reference prefix token, check the source records and the supplied rule before comparing the result with another method. Consult the applicable authoritative rule when deciding eligibility, legal timing, fees, or obligations.
References
Similar or alternative tools
- Dossier Page Prefix Ambiguity
Find literal supplied page-identifier prefix collisions without validating a dossier structure.
- Dossier Sequence Gap Token
Compare explicitly formatted dossier sequence tokens without enforcing a regulator-specific submission rule.