Description
Check supplied metadata occurrence count against required/repeatable flags.
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.
Check supplied metadata occurrence count against required/repeatable flags.
When to use this tool
Use Metadata Repeatability Flag when you already have occurrenceCount, repeatable, required and need to check supplied metadata occurrence count against required/repeatable flags.
How to use the tool and how it works
- Enter occurrenceCount, repeatable, required. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read missingRequired, repeatsDisallowed, conformsUnderFlags. Inspect missingRequired, repeatsDisallowed, conformsUnderFlags before interpreting the associated values.
Require nonnegative safe whole count; missingRequired=required && count=0, repeatsDisallowed=!repeatable && count>1, and conformsUnderFlags combines both constraints.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| occurrenceCount | Supplied count only; fields and values are not inspected. | Required. Safe integer; minimum 0. |
| repeatable | Repeatable | Required. Boolean. |
| required | Required | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| missingRequired | Missing Required | Required. Boolean. |
| repeatsDisallowed | Repeats Disallowed | Required. Boolean. |
| conformsUnderFlags | Conforms Under Flags | Required. Boolean. |
{
"input": {
"occurrenceCount": 2,
"repeatable": false,
"required": true
},
"output": {
"missingRequired": false,
"repeatsDisallowed": true,
"conformsUnderFlags": false
}
}Limitations and assumptions
- Counts and rules are supplied; no record, actual field values, schema or complete metadata conformance is inspected.
- 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.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
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.