Gabriel I have tried it a number of ways now and am pretty disgusted :-)
I am coming around to something similar to your plan. I do have to keep
ResrouceId as an extension of FeatureId ... because most code we use has
Set as part of the request; and I think we want to mix up a range of
reques
On Thu, Oct 20, 2011 at 9:05 PM, Jody Garnett wrote:
> I had a quick scan as well; I am starting to feel they screwed up this
> specification. Sometimes it is the case that the wfs spec plans around
> functionality that does not end up making it into filter spec. I wonder if
> they just dropped th
I had a quick scan as well; I am starting to feel they screwed up this
specification. Sometimes it is the case that the wfs spec plans around
functionality that does not end up making it into filter spec. I wonder if they
just dropped the ball here.
Do any of the temporal functions apply in th
On Thu, Oct 20, 2011 at 11:02 AM, Jody Garnett wrote:
> Q: I was not able to find any evidence in the specification for a
> getPreviousVersionFID() method; did I just miss it in the WFS 2 and Filter
> 2
> specification or is this something that came out of the GeoGit work?
>
> no it doesn't come
> > Q: I was not able to find any evidence in the specification for a
> > getPreviousVersionFID() method; did I just miss it in the WFS 2 and Filter 2
> > specification or is this something that came out of the GeoGit work?
> no it doesn't come out of anything GeoGit specific.
> It matches FES 2.0
Hi Jody,
sorry for the late reply.
comments inline.
On Tue, Oct 18, 2011 at 10:36 AM, Jody Garnett wrote:
> Okay Gabriel / Justin:
> Can I ask you to look over the following:
> - http://docs.codehaus.org/display/GEOTOOLS/ResouceId
sure.
> I have outlined two options:
> * ResourceId (as your de
Okay Gabriel / Justin:
Can I ask you to look over the following:
- http://docs.codehaus.org/display/GEOTOOLS/ResouceId
I have outlined two options:
* ResourceId (as your described in your patch)
* FeatureId (adding the additional data to FeatureId and removing our unused
Identifier classes Obj
no problem; I will have a look this afternoon and see what I can come up with.
--
Jody Garnett
On Tuesday, 18 October 2011 at 8:03 AM, Justin Deoliveira wrote:
> Here you go. I haven't tested it at all on trunk... just that it applies
> cleanly. It still requires discussion.
>
> On Mon, Oct
That wound be good; make me a patch I will get the rest of it done.
--
Jody Garnett
On Tuesday, 18 October 2011 at 12:16 AM, Justin Deoliveira wrote:
> The stuff we did for resource id (mostly just the interface/class and the xml
> bindings for it) has not been committed along with the other
The stuff we did for resource id (mostly just the interface/class and the
xml bindings for it) has not been committed along with the other wfs2 work.
Reason being simple... it is experimental. Plus given how over deadline we
are for getting this work committed onto the trunk of geotools and geoserv
10 matches
Mail list logo
