Sunburned Surveyor wrote: Hi,
> Andreas wrote: "But I cannot really see > the point in trying to find a common name for an ID field, as that usually > depends strongly on your use case" > > I didn't want a situation where a Feature Schema needs to have a > persistent ID attribute for my schema and another persistent ID for > another plug-in. I thought if we could come up with a fairly standard > persistent ID attribute name and datatype that other plug-ins could > use it as well. I can see the benefit of an AttributeType for IDs, preferably one that cannot be altered (or make it optional to enable modifications) by the user. Best regards, Andreas -- l a t / l o n GmbH Aennchenstrasse 19 53177 Bonn, Germany phone ++49 +228 18496-11 fax ++49 +228 1849629 http://www.lat-lon.de http://www.deegree.org
signature.asc
Description: Digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
