The spec generally just asks that feature ids be unique, and should be
stable across different representations. This gets tricky when the same
feature is represented in two different datasets - something we have never
(as an industry) figured out how to address.
As a quick way to prevent two features called "5" from conflicting we
prepend the type name so we get "road.5" and "river.5".
You have found the case where a user often has several copies of the "same"
shapefile (perhaps different versions). By focusing on what we hope is the
type name it is an attempt to keep featureIds consistent across the files.
So "my_shapefile.5" is represented in my_shapefile.v1.shp and
my_shapefile.v2.shp.
You can check the GML spec for restrictions on FeatureId and TypeName. I
assume any restrictions on TypeName are based on the XSD format.
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
