Description
Separate a supplied leaf reference at its first fragment marker; not a URI or regulatory submission validator.
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.
Separate a supplied leaf reference at its first fragment marker; not a URI or regulatory submission validator.
When to use this tool
Use it for regulatory submission leaf fragment flag when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter reference. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read leaf, fragment, fragmentPresent, duplicateSeparators. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Split the supplied reference at its first hash into leaf and fragment, recording fragmentPresent even for an empty fragment. Flag any further hash as duplicateSeparators.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| reference | Reference | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| leaf | Leaf | Required. Text; maximum UTF-16 length 8192. |
| fragment | Fragment | Required. Text; maximum UTF-16 length 8192. |
| fragmentPresent | Fragment Present | Required. Boolean. |
| duplicateSeparators | Duplicate Separators | Required. Boolean. |
{
"input": {
"reference": "leaf.xml#section-2"
},
"output": {
"leaf": "leaf.xml",
"fragment": "section-2",
"fragmentPresent": true,
"duplicateSeparators": false
}
}Limitations and assumptions
- The remainder retains later hash characters. This is literal metadata inspection rather than URI parsing, file access, eCTD validation, or a determination that fragments are allowed.
- 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 regulatory submission leaf fragment flag, 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
- Authority Receipt Submission Time Offset
Compare explicit submission/receipt clocks after supplied common-reference offsets.
- eCTD Leaf Title File Extension Pair
Inspect supplied leaf-title presence and filename extension under an explicit list.