-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: ENCODINGS PR02
-
Fix Version/s: None
-
Component/s: ENCODINGS Specification
-
Labels:None
-
Environment:
TAB Review
"4.1.4 Other types and facets reads in part:
""Facets are mapped to name/value pairs as described by the rules above.""
4.2 XML Namespace reads in part:
""as shown in the examples below:""
4 JSON encoding - reads in part:
""The following grammar is used to represent OBIX objects:""
above occurs 3 times, below 2 times and following 22 times, not to mention similar terms being used.
The problem this presents is that every reader of this specification, which hopefully will number if the thousands if not hundreds of thousands, will have the same experience with uncertainty, every time they read this specification.
It is a simple enough matter to say: Facets are mapped to name/value pairs as described by the rules defined in Section ***.
Which removes the ambiguity but also in this case, discloses that there are no rules for mapping facets in JSON. (4.1.4)
The next mention ""upwards"" of facets comes in 3.5 Children, which is in the OBIX Binary section. Is that the source of rules for facets in JSON?"