[OASIS Issue Tracker] (OSLCCORE-134) literal_value of the oslc_where syntax is not well-defined

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

    [ https://issues.oasis-open.org/browse/OSLCCORE-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=68508#comment-68508 ] 

James Amsden commented on OSLCCORE-134:
---------------------------------------

Isn't this already covered by RDF? OSLC shouldn't need to define these details.


> literal_value of the oslc_where syntax is not well-defined
> ----------------------------------------------------------
>
>                 Key: OSLCCORE-134
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-134
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>          Components: Query
>            Reporter: Andrii Berezovskyi
>            Assignee: David Honey
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)