Uploaded image for project: 'OASIS OSLC Lifecycle Integration Core (OSLC Core) TC'
  1. OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
  2. OSLCCORE-134

literal_value of the oslc_where syntax is not well-defined

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: Query
    • Labels:
      None
    • Proposal:
      Hide

      I can only suggest we add more strict rule on how to interpret strings "true" and "false", how numbers w/o a fractional part shall be treated as integers and that double-precision decimals are the default.

      Show
      I can only suggest we add more strict rule on how to interpret strings "true" and "false", how numbers w/o a fractional part shall be treated as integers and that double-precision decimals are the default.

      Description

      The spec is not clear on how to interpret the literals w/o the xsd data type.

      E.g.

      The terms boolean and decimal are short forms for typed literals. For example, true is a short form for "true"^xsd:booleancode>, 42 is a short form for "42"xsd:integer and 3.14159 is a short form for "3.14159"^xsd:decimal.

      does not specify how I am supposed to know whether 42 is an integer but 3.14 is a decimal (or a single-precision float?), let alone how I am supposed to ensure that 'true' is a boolean True, not a "true" string literal.

        Attachments

          Activity

            People

            • Assignee:
              DavidHoney David Honey
              Reporter:
              berezovskyi Andrii Berezovskyi
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: