Rob Atkinson ha scritto: > Perhaps we are missing the point a little here. What is the point of > advertising a feature type at all? If it has no potentiall meaning, but > is just an identifier, its more honest just to assign it a unique > identfier - perhaps a UUID would be correct. > > In the context of Spatial Data Infrastructures - the main driver of open > standards and the deployment of re-usable data access services - the > feature type must be recognisable by the client. The client will bind to > a specific feature type, having discovered this in some fashion from a > registry - maybe via a persistent binding like a Web Map Context docuement, > > in this case, can someone please explain just how a "Cascading WFS" > would be used practically? > > I can see that for a desktop GIS application, the WFS source just wants > to be bound to objects you can manpulate - but the name (machine id) > should not form part of the user experience, you should assign an > arbitrary identifier to reflect the arbitrary semantics you intend, and > propagate the Title and other metadata to the user interface. > (including possible the Title of the source server).
The issues that I was talking about are totally technical, you can in fact show title to the user, but not use it in GML encoding. If your feature type name is "xxx:yyy" and you add it another prefix you get something like "ppp:xxx:yyy" which is an invalid element name in XML, so you're generating invalid GML. As for the title, hum... it occurs to me that we're probably not cascading all the feature type metadata, but just using the feature type name (that's because we are treating the WFS data store just like any other data store, ignoring that it can provide us more info about the feature type compared to other data stores). This is another place where gt2 data stores do not match the WFS expectations, that is, we have no place for title, abstract, metadata urls, keywords... We should add it, and we would need to advertise this extra info in a "capabilities" object that we sorely lack, too, in our datastore architecture. Cheers Andrea Aime ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
