referencing object map definition

[ghsnd]

The current spec states that a referencing object map is represented by a resource that MUST have [...] one or more join condition properties [...]. A bit further it states that no join condition is required if the logical source(s) of parent and child maps are effectively equal.

So the refencing object map

• MUST have zero or more join condition properties, or
• MAY have one or more join conditions properties, no?

[pmaria]

The reason we used MUST and not MAY is because of RFC-2911's meaning for the keywords.

MAY This word, or the adjective "OPTIONAL", mean that an item is
truly optional. One vendor may choose to include the item because a
particular marketplace requires it or because the vendor feels that
it enhances the product while another vendor may omit the same item.

However, I agree it reads somewhat awkward.

We could consider rewriting it to:

The referencing object map

• may have zero or more join condition properties. Implementations MUST support join condition properties.