COnformance clause is not precise enough

The wording of the conformance section is too informal. It should:

(1) have 2 "clauses" (in subsections), one clause per conformance target (here, possible targets are client, service)

(2) define even if informally its conformance targets. Service: is it an ODATA service? what does it do? Client is mentioned just once before the clause. Same questions. Why does the clause for client talk about "[EDM] model" and not the one for "service"?

(3) Each clause should refer explicitly to normative content sections, ideally both by number and title. Current way is too imprecise. For example, in the "Conforming services" says "follow all rules of this specification document for the types, sets, functions, actions, containers and annotations they expose". How do you recognize these rules? (use "normative requirements" or "normative statements" instead). Also, I see no reference to 4.4 "Terms". I see also no references to section 5 or 6 which seem normative. And how about section 3 (requesting JSON CSDL format ) isn't that something a service should always honor?

(4) what does "clients MUST be prepared to consume a model " mean? Does that mean it just needs be up and running, and yet does not need to really process all the constructs according to their semantics? Also what does "MUST ignore " mean? Is it not OK to generate an error message either internally or externally?

See the "conformance clauses guidelines" linked from theTAB public page: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tab