Hi,
I'm trying to get a handle on what a RESTful WFS might look like and so I have reviewed a lot or material on the web about RESTful WFSs and have been thinking about the operations I might want my WFS to perform.
An obvious operation is ability to query a subset of features from a WFS. So, I though about some simple and not so simple queries that I might want to execute.
What I have found for "simple" queries was stuff like this:
http://example.com/featureserver.cgi/simple?bbox=-180,-90,0,0
http://example.com/featureserver.cgi/simple?maxfeatures=10
http://example.com/featureserver.cgi/simple?queryable=title,description&title=My%20Feature&description=Fun
My first question about these examples is: I thought that query parameters like bbox, maxfeatures, queryable, etc. are a no-no in REST. Am I wrong on that point? I hope I am some this type of parametrization would may querying a WFS a lot easier (I think).
Second question on the same examples is: I assume that all the predicates in the last example are implicitly AND'ed (i.e. title='My Feature' AND description='Fun'). Correct? What if I want to OR the predicates instead?
I also thought about some harder queries ...
Say I have two feature types, Parks and Roads. The query I want to execute is: Find all roads that cross the park named 'Algonquin Park'
What would this query look like in a RESTful invocation?
That's about it for now. Hope people don't mind if I post some more questions to these groups as I muddle my way through the world of REST.
Look forward to the responses.
Ciao.
--
Panagiotis (Peter) A. Vretanos CubeWerx Inc.
Big Kahuna (Senior Database Developer) http://www.cubewerx.com
Tel. 416-701-1985 Fax. 416-701-9870 pvretano@anonymised.com
"If you are in a spaceship that is traveling at the speed of light,
and you turn on the headlights, does anything happen?" --Stephen Wright