Issue 68 in ioostech: GET requests with indeterminate 'eventtime' values?

[ioos...@googlecode.com]

Status: Accepted
Owner: abir...@gmail.com
CC: derrick....@noaa.gov, sh...@axiomalaska.com, emilioma...@gmail.com,
wilcox.k...@gmail.com
Labels: Type-Enhancement Milestone-Release2.0 Priority-Low

New issue 68 by abir...@gmail.com: GET requests with indeterminate
'eventtime' values?
http://code.google.com/p/ioostech/issues/detail?id=68

At the moment, the 'eventtime=T_1/T_2' values in GET request must strictly
conform to ISO format (T=YYYY-MM-DDTHH:mm:ss±HH). Because of that, the only
way to query for the latest observation with GET KVP request is to
use 'eventtime=T_last/T_last'. With POST request, indeterminate time
filtering values such as "latest" or "first" may be used; however, it is
not possible in GET requests for now.
Will it make sense to allow indeterminate time values in GET KVP
'eventtime' for Milestone 2?


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[ioos...@googlecode.com]

Comment #1 on issue 68 by srstcl...@gmail.com: GET requests with

indeterminate 'eventtime' values?
http://code.google.com/p/ioostech/issues/detail?id=68

FWIW, i52n SOS accepts "first" and "latest" in GetObs KVP requests:

http://ioossos.axiomalaska.com/52n-sos-ioos-stable/service?service=SOS&version=1.0.0&request=GetObservation&offering=urn%3Aioos%3Anetwork%3Atest%3Aall&observedProperty=http%3A%2F%2Fmmisw.org%2Font%2Fcf%2Fparameter%2Fair_temperature&procedure=urn%3Aioos%3Astation%3Atest%3A1&responseFormat=text%2Fxml%3B%20subtype%3D%22om%2F1.0.0%2Fprofiles%2Fioos_sos%2F1.0%22&eventTime=latest

http://ioossos.axiomalaska.com/52n-sos-ioos-stable/service?service=SOS&version=1.0.0&request=GetObservation&offering=urn%3Aioos%3Anetwork%3Atest%3Aall&observedProperty=http%3A%2F%2Fmmisw.org%2Font%2Fcf%2Fparameter%2Fair_temperature&procedure=urn%3Aioos%3Astation%3Atest%3A1&responseFormat=text%2Fxml%3B%20subtype%3D%22om%2F1.0.0%2Fprofiles%2Fioos_sos%2F1.0%22&eventTime=first

[ioos...@googlecode.com]

Comment #2 on issue 68 by abir...@gmail.com: GET requests with

indeterminate 'eventtime' values?
http://code.google.com/p/ioostech/issues/detail?id=68

Hmm, technically it violates the respective IOOS Convention requirement
described in WSDD. So, to do the same in ncSOS we should either loosen or
completely deprecate that requirement, and update the WSDD. Or we may agree
to postpone it till Milestone 2...

[ioos...@googlecode.com]

Updates:
Labels: -Milestone-Release2.0 Milestone-Release1.1

Comment #3 on issue 68 by abir...@gmail.com: GET requests with

indeterminate 'eventtime' values?
http://code.google.com/p/ioostech/issues/detail?id=68

After talking to Derrick, we decided that ncSOS must accept the same
indeterminate time values for 'eventtime' as i52N, i.e. "eventtime=first"
and "eventtime=latest". That should be a part of Milestone 1.x rather than
be delayed till Milestone 2.

I will make necessary changes to the IOOS Convention rules in the IOOS SOS
WSDD.