[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OBIX-143) 3.3.4 Str Encodings
[ https://tools.oasis-open.org/issues/browse/OBIX-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37159#comment-37159 ] Markus Jung commented on OBIX-143: ---------------------------------- Should be discussed in next TC 04/24/2014. > 3.3.4 Str Encodings > ------------------- > > Key: OBIX-143 > URL: https://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 > > "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 was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]