-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: ENCODINGS PR02
-
Fix Version/s: None
-
Component/s: ENCODINGS Specification
-
Labels:None
-
Environment:
TAB Review
-
Resolution:
"Encoding" is a specification on its own. As such it must have a detailed Conformance Clause.
That will not do:
"An implementation is compliant with this specification if it implements all MUST or REQUIRED level requirements. An implementation MUST specify its supported encodings"
1. What constitutes an "implementation" is everyone's guess: we see in this document "client and server implementation.", "EXI implementation", "reference implementation", etc. I don't know what kind of entity is supposed to conform. The closest I see is something called an "Encoder" and maybe a decoder too. That seems to suggest there are at least two types of implementations to take care of.
2. Not clear how to "specify its supported encodings". A reference to the normative text that says how to do that is needed.
3. Because there are different types of encodings with their own requirements, it may be good to distinguish different conformance profiles (for JSON, EXI...), combinations of which can of course be claimed. Right now, ""if it implements all MUST or REQUIRED level requirements"" seems to imply that all encodings must be supported...