2.4 Identifier - Perils of distributed definitions - STIX Part 1

2.4 Identifier reads in part:

*****
An identifier universally and uniquely identifies a SDO, SRO, Bundle, or Marking Definition. Identifiers MUST follow the form [object-type]--[UUIDv4], where [object-type] is the exact value (all type names are lowercase strings, by definition) from the type property of the object being identified or referenced and where the [UUIDv4] is an RFC 4122-compliant Version 4 UUID. The UUID MUST be generated according to the algorithm(s) defined in RFC 4122, section 4.4 (Version 4 UUID) [RFC4122].
*****

Not the clearest prose but you think, at this point, that the pattern is:

[object-type]--[UUIDv4]

Not really.

If you remember 1.5.1 Naming conventions, then you know that [object-type] can have tokens separated by a "dash" and are between three and 250 characters long.

Moreover, if you have read STIX Part 1 before, if this is a custom property, then the [object-type] is limited to [a-z0-9\-]{3,250} followed by two dashes, then [UUIDv4] (custom properties defined in 7.2.1)

But I have to remember and consult three separate parts of Part 1 to derive that condition.