Description
Inspect supplied leaf-title presence and filename extension under an explicit list.
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.
Inspect supplied leaf-title presence and filename extension under an explicit list.
When to use this tool
Use it for ectd leaf title file extension pair when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter title, filename, allowedExtensions. Keep parallel arrays aligned and use the stated units and conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read extension, allowed, titlePresent. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Require a nonempty filename without path separators, take text after its last nonleading dot as a lowercase extension, compare with lowercase allowedExtensions, and test trimmed title presence.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| title | Title | Required. Text; maximum UTF-16 length 8192. |
| filename | Filename | Required. Text; maximum UTF-16 length 8192. |
| allowedExtensions | Allowed Extensions | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| extension | Extension | Required. Text; maximum UTF-16 length 8192. |
| allowed | Allowed | Required. Boolean. |
| titlePresent | Title Present | Required. Boolean. |
{
"input": {
"title": "Study report",
"filename": "report.PDF",
"allowedExtensions": [
"pdf",
"xml"
]
},
"output": {
"extension": "pdf",
"allowed": true,
"titlePresent": true
}
}Limitations and assumptions
- Leading-dot names have no extension under this rule and a trailing dot gives an empty extension. This is lexical metadata, not MIME inspection, file access, or eCTD conformance.
- 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 ectd leaf title file extension pair, 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
- Labeling Statement Claim Source Pair
Compare explicit statement/source attribution and versions without verifying a claim.
- Regulatory Submission Leaf Fragment Flag
Separate a supplied leaf reference at its first fragment marker; not a URI or regulatory submission validator.