Hi, Al Johnson wrote:
Is this raw data , or data intended for direct use by olocationd? Raw data should be as close to what you store as possible, while olocationd should have a format optimised for size and speed of search. It's a bit like the situation with raw OSM data and Navit binary format.
I am talking here of raw data, so that contributor can get back (and more) what they contributed. My idea was: is there a format which would in addition to keep the data intact, would bring more flexibility, etc.
What does your privacy policy say about this? I would think a list of contributors would satisfy the attribution requirement, but check with CC as I'm not a copyright lawyer. A numeric submitter id would save space while allowing removal of data from an untrustworthy source.
A numeric submitter? If I compare to GPL, a source code could contain a numeric identifier instead of a "real name"? I don't know in fact.
But so far, in order to protect privacy of people, we are going in direction of a file containing the list of contributors, and all the raw XML files without being linked to its contributor.
Thanks for your input! Onen _______________________________________________ smartphones-standards mailing list smartphones-standards@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-standards
