[OASIS Issue Tracker] (OBIX-140) Encoding - Overloading terminology

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://tools.oasis-open.org/issues/browse/OBIX-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37511#comment-37511 ] 

Markus Jung commented on OBIX-140:
----------------------------------

The encoding specifies how the information is expressed in some format. Since there are multiple available formats there is some kind of overloading of this term. Regarding the conformance section a separate issue OBIX-141 deals with this issue.

> Encoding - Overloading terminology
> ----------------------------------
>
>                 Key: OBIX-140
>                 URL: https://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: Markus Jung
>
> "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 was sent by Atlassian JIRA
(v6.2.2#6258)