Might choose/need not

4.3 Conformance of DITA processors reads in part:

*****
Processors that store, manage, or edit DITA documents might choose to not implement specific features that would be required for final-form processing. However, such processors MUST enable the creation or storage of DITA documents that use all DITA features, even if the processor is not aware of the DITA semantics for those features.

For example, a DITA-aware editor need not provide specific support for creating or resolving content references, but it must allow, using normal XML editing methods, the creation and editing of content references. A content management system that supports map types that allow relationship tables but does not directly support relationship table processing must be able to store and manage conforming map documents that include relationship tables.
*****

Ouch! might choose? I would miss that as a requirement, should be reworded to say MAY.

Same for "need not." Note "need not" occurs 20 times in the draft. Should all be MAY.

Might choose occurs 2 times.

BTW, the must I have marked above is likely meant to be MUST from its context.