The best description for date and time is a timestamp. Further anonymizing should be done at query time.
cheers Wolfgang > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Sascha Silbe > Sent: Wednesday, December 03, 2008 12:43 PM > To: Marcus Wolschon > Cc: [email protected] > Subject: Re: [Routing] Crowdsourced costing - offer of writing > aclient+metric for it > > > On Wed, Dec 03, 2008 at 12:11:46PM +0100, Marcus Wolschon wrote: > > > I tried to not make it to make my firt draft not too > > fine-grained due to privacy and not-enough-data -concerns. > > > We can have a * day = > > > (weekday,weekend,holiday,beforeHoliday,afterHoliday,schoolVacation > ,beforeSchoolVacation,afterSchoolVacation) > > ** weekday (mo,...sa,so) > That's better, though you still miss some cases (e.g. the christmas > shopping period). In addition, the user is required to enter more data, > making it more likely (s)he just doesn't bother enough to submit the > data. > How about just making the (full) date field optional? Send it by > default, but give the user the choice of anonymizing the data. > > [Vandalism] > > We do have the option of ignoring that part for a prototype for the > > time being and care about it later. > That's probably the best option. I'm not sure how much storing the IP > address would help anyway since a malicious user can upload from many > different IP addresses anyway (anonymizer networks, "Call by call" > dial-up ISPs, ...). Statistical filtering might (or might not) be much > better at getting the junk out (though probably only if the noise level > is low enough). > > > The server need never hand out data of a single upload. > > To be meaningfull it even needs to be averaged for many > > users. > To be useful to a single end-user, it needs to be aggregated some way, > yes. But there are many ways to aggregate the data, so tool developers > would want excerpts of the raw data as well. > > > I suggested soap because it is supported by many > > systems, it is type-safe and trivial to check and > > there is good tooling. > Type-safety is certainly good to have. Though I'd rather like a format > that can be used for offline storage and exchange as well... > > CU Sascha > > -- > http://sascha.silbe.org/ > http://www.infra-silbe.de/ > _______________________________________________ Routing mailing list [email protected] http://lists.openstreetmap.org/listinfo/routing
