-
Notifications
You must be signed in to change notification settings - Fork 265
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
Improve Local time support in Orion #2663
Comments
Both A and B are compatible? I mean, if the client specified With regards to B, in order to ensure backward compatibility default timezone in the case of not using the global parameter must be UTC. |
@LeonanCarvalho feedback on this topic, raised at #2660 (comment):
|
This issue is not especifically related with NGISv2, so APIv2 label is removed. The issue keeps opened. |
It would be great to improve local time support in Orion after #2660 lands.
This is important because we expect to have a myriad of data belonging to local scopes (cities, countries), etc. and users and developers would expect a decent support of local date and times.
We have the following options (we can support both):
A/ Support the
Timezone
experimental HTTP header or a variant of it (Fiware-Timezone
) and be able to provide data localized to what a client is requesting and interpret timezoneless data as referred to such local timezone.https://tools.ietf.org/html/draft-sharhalakis-httptz-05
B/ Instantiate Orion (global parameter) with a default timezone that will be used anytime a timezoneless datestring is used.
What do you think?
The text was updated successfully, but these errors were encountered: