On Friday 08 June 2007 18:24:24 Jody Garnett wrote: > Well if there are two of you working with *version* - and it is a part > of the formal model I do not adding it back in (emphais to the current > feature model). > > I just did not want it in the model with nobody using it - figured it > would get in the way when a real user (ie you two) came along. > Do you guys mind reading over that link; talking on IRC; and then making > a recommendation? > > Here are two alternatives to think about: > - Feature.getVersion() > - Feature.getClientProperty( "version" )
ah, good point. Regarding fm it would be nice to have client properties back in Feature (actually in Attribue). We have them in PropertyDescriptor and PropertyType, but they're shared among Attribute instances and thus there's no such a thing as per-feature user/meta-data, or we need an instance of PropertyDescriptor for each instance of Attribute to hold it. Is there a good reason for not having put/getUserData in Attribute too? cheers, Gabriel > > Strictly speaking the version should not be part of the Feature (it is > not a measurement of a real world phenomenon) , it should be part of the > description of the Feature ... I view "client properties" as an informal > description used for one application, or used by convention. I am sure > we could hunt down the formal thing (cough metadata) but life is short. > > Cheers, > Jody > > Andrea Aime wrote: > > Jody Garnett ha scritto: > >> Some more thoughts ... > >> featureId is supposed to be immutable - so it makes a good hashcode / > >> equals test. > >> > >> The formal OGC feature model did have a getVersion(): String - but we > >> never used it, and never used it, and finally removed it from GeoTools. > >> Andrea has been doing some work with respect to versioning ... he may > >> be treating version as a normal attribute? > > > > Nope, version is not an attribute, and it's not there even when you > > ask features from the versioning data store. You do specify what > > revision do you want making a query, so you're supposed to know it > > in advance. > > > > I could modify the versioning data store to add the queried revision, > > or the last modification revision (different feature by feature) if > > we wanted, it would just take some work in the readers (a few hours > > if you want the revision, probably a day or more if you want the last > > modified revision instead). > > > > Cheers > > Andrea > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Geotools-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
