Uploaded image for project: 'OASIS Open Building Information Exchange (oBIX) TC'
  1. OASIS Open Building Information Exchange (oBIX) TC
  2. OBIX-145

3.3 Value Encodings

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: ENCODINGS PR02
    • Fix Version/s: ENCODINGS WD13
    • Component/s: ENCODINGS Specification
    • Labels:
      None
    • Environment:

      TAB Review

    • Resolution:
      Hide

      The "may" in this case refers to a situation that can occur and is not normative in the sense that an implementation may or may not implement some feature. So I keep it lower-case.

      The rest of the sentence is rephrased: 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 have always their value encoded (equivalent to the val attribute in XML).

      Show
      The "may" in this case refers to a situation that can occur and is not normative in the sense that an implementation may or may not implement some feature. So I keep it lower-case. The rest of the sentence is rephrased: 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 have always their value encoded (equivalent to the val attribute in XML).

      Description

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

        Attachments

          Activity

            People

            • Assignee:
              mjung Markus Jung (Inactive)
              Reporter:
              Toby.Considine Toby Considine
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: