Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with datatype Any #7

Open
mjacoby opened this issue Sep 8, 2016 · 1 comment
Open

Issues with datatype Any #7

mjacoby opened this issue Sep 8, 2016 · 1 comment
Labels
sensing v2.0 This change should be discussed for v2.0 of the sensing document. tbd to be discussed

Comments

@mjacoby
Copy link

mjacoby commented Sep 8, 2016

This issue has already been submitted as change request and is just posted here to have a central place where all the issues can be found

SensorThings API introduces the datatype Any for some entity properties (namely Sensor.metadata, Location.location, Observation.result, FeatureOfInterest.feature) which can take any value specified in JSON. This raises two issues:

  • How are these values stored? Should the JSON datatype be preserved when inserting a property of datatype Any (e.g. when inserted as JSON Number can it be expected that it will be stored and returned as JSON Number)?
  • Semantics of some operators are undefined when used on properties of type Any
    • $orderby clauses on properties of type Any
    • built-in filter operation using properties of type Any as operand
    • built-in query function using properties of type Any as parameter

For the detailed description please see the change request 383

@hylkevds
Copy link
Contributor

hylkevds commented Mar 24, 2017

I've reworked the changes for this issue into a specific branch:
https://github.com/hylkevds/SensorThingsAPI/compare/master...dataTypes

hylkevds added a commit to hylkevds/sensorthings that referenced this issue Nov 9, 2018
@taniakhalafbeigi taniakhalafbeigi added sensing v2.0 This change should be discussed for v2.0 of the sensing document. tbd to be discussed labels Dec 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sensing v2.0 This change should be discussed for v2.0 of the sensing document. tbd to be discussed
Projects
None yet
Development

No branches or pull requests

3 participants