[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (OBIX-140) Encoding - Overloading terminology
Encoding - Overloading terminology
----------------------------------
Key: OBIX-140
URL: http://tools.oasis-open.org/issues/browse/OBIX-140
Project: OASIS Open Building Information Exchange (oBIX) TC
Issue Type: Bug
Components: ENCODINGS Specification
Affects Versions: ENCODINGS PR02
Environment: TAB Review
Reporter: Toby Considine
Assignee: Toby Considine
"The term ""encoding"" is applied to XML, JSON, EXI but also to Bool (?) 3.3.1, Int 3.3.2, Real 3.3.3, Str 3.3.4, 3.3.5 Abstime, etc. not to mention in the conformance clause: ""An implementation MUST specify its supported encodings.""
XML ""encoding"" normally refers to the use of XML syntax. A string ""encoding,"" at least in Unicode conformant documents, refers to a Unicode defined byte sequence that represents characters. The various other uses of ""encoding"" in this document appear to be data types but it isn't possible to say for sure.
If in the enumeration of various values ""encoding"" was meant to be data type, then use ""data type"" and not encoding.
BTW, this specification does not specify or reference another document that specifies how ""An implementation MUST specify its supported encodings.""
Lacking any means to declare an encoding and no meaningful definition of encoding, it is difficult to see how any application could conform to this specification."
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]