[OASIS Issue Tracker] Created: (OBIX-145) 3.3 Value Encodings

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

3.3 Value Encodings
-------------------

                 Key: OBIX-145
                 URL: http://tools.oasis-open.org/issues/browse/OBIX-145
             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 Value Encodings is a mixture of possible keywords, non-normative text and notes. 

It reads: 

***** 
Each obj type and facet type may have an associated value encoding. For example, to encode the precision facet we must specify the facet code 0x40 plus the value of that facet which happens to be an integer. The object types bool, int, enum, real, str, uri, abstime, reltime, date, and time are always implied to have their value encoded (equivalent to the val attribute in XML). 
***** 

Should the first ""may"" be ""MAY?"" A non-normative example follows. What is meant by ""always implied"" isn't clear without further explanation. Implied by what?"

-- 
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