IEFRA_ — Compliance section confusing

Section 2.2 says there are 4 compliance points, but then later on says "A vendor or integrator may select one of the compliance points described below, or combine the capabilities to form additional compliant configurations", implying that implementers may ignore the compliance points - which means they aren't actually compliance points at all. The relationship between components, configurations and compliance points isn't clear. I would also expect each of the 4 compliance points to have their own section at the same heading level, but "File Share" is section 2.3.2.1 while "Structured Messaging" is 2.3.1.

Overall, this section needs more work.

(This issue was raised during the specification's pre-adoption AB review).

Readdress Compliace wording

The wording should have been - "combine the compliance points" vs the capabilities.

Meaning an implementer can develop a solution with one or more of the compliance points addressed.