Attribute type (Type 1, 1C, 2, 2C, 3)

How strongly a module requires an element — required, conditional, or optional.

The usage type (PS3.3 §7.4) says how strongly a module requires an element:

• Type 1 — required; must be present and carry a non-empty value.
• Type 1C — conditionally required; when its condition applies, the Type 1 rule holds.
• Type 2 — required; must be present, but may be empty.
• Type 2C — conditionally required; when its condition applies, the Type 2 rule holds.
• Type 3 — optional.

Note The type belongs to the module, not to the tag. The same element can be Type 1 in one module and Type 3 in another, which is why the app always shows a type next to the module that imposes it. An element with no declared type shows none.

This is what the QA tab’s conformance findings mean by “Type n”: a missing Type 2 element is a different defect from a missing Type 1, and an absent Type 3 is not a defect at all.

Hover any Type badge — in Standard docs, the edit modal, or the QA tab — for the same description inline.