← Prev in month ← Prev in thread
Next in thread → Next in month →

[OASIS Issue Tracker] Created: (OBIX-143) 3.3.4 Str Encodings

From
OASIS Issues Tracker <>
Date
2014-02-21T03:26:19+00:00
ID
1352295114.12711392953231807.JavaMail.tomcat@customer-jira
Thread
[OASIS Issue Tracker] Created: (OBIX-143) 3.3.4 Str Encodings
3.3.4 Str Encodings
-------------------

                 Key: OBIX-143
                 URL: http://tools.oasis-open.org/issues/browse/OBIX-143
             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


"3.3.4 Str Encodings 

Table 3.5 Str Encodings confuses string encoding with value types. 

The first entry references (without citation) one assumes the XML Schema datatypes documents for UTF8. Which is a recognized string *encoding.* 

The second entry uses a heretofore unknown type of encoding called ""prev."" The description says: ""u2 index of previously defined string."" 

u2 appears in 3.3.8 prior to year, 3.3.2 Int Encodings for Unsigned 16-bit integer value, which along with the explanation implies u2 is a unsigned 16-bit integer value for an index. 

However that may be, an index is not a string encoding but value. Which is ok so long as values and string encodings are not confused. 

A better way to state the allowed values would be UTF8 strings or index values that refer to UTF8 strings. There you can define the index value."

-- 
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
← Prev in month ← Prev in thread
Next in thread → Next in month →