Conformance clause is missing

The very terse and vague Conformance section is not what a reader or implementer would expect in order to help conform to this specification.

See on TAB public page the list of guidelines: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tab
See the "Guidelines to Writing Conformance Clauses for OASIS Specifications " : http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html

First of all, what is an "implementation"? there seems to be different types (which would be normal), but which normative requirement applies to which type?
In other words, what are the possible conformance targets? what kind of object or product do we allow to claim conformance? is it:

• a Service Interaction Profile?
• each ECF exchange? (Message) (some normative requirements appear to these)
• Major Design Elements (MDEs)?
• An MDE operation?

A well formed conformance section should include:

• definitions of the valid conformance targets (types of implementation for this specification that we'd expect to claim conformance.)
• for each conformance target, a conformance clause.
  Refer to the TAB conformance clauses guideline for the writing of a well-formed conformance clause.