I am not asking for disallowing the community to edit my answers. What I am asking for is to disallow an answer to get rewritten by somebody else when it is already high voted (and thus accepted by the community at large as an acceptable answer).
This is the portion that got edited from the original post.
Spatialite is awesome because it gets all the free functionality from SQLite. SQLite is used everywhere. It is on your Android Phone, on your iPhone/iPad, on Firefox, on Google Chrome, on several commercial embedded devices - can go on forever. To truly make it into a Geoformat (and not just do dumb bounding box operations), it needs to leverage the same geometry library that PostGIS uses: GEOS. Sadly, GEOS is based on another even more awesome geometry library known as JTS. All the algorithms in JTS are extremely powerful, so what is the problem?
Well, JTS is licensed as Open Source LGPL, and LGPL is a viral license. JTS is LGPL, means GEOS is LGPL, means spatialite linked statically with GEOS is LGPL. This sucks. Why? Without explaining open source licenses too much, I can tell you that, for example, I cannot use Spatialite on, say, an iPhone app because that would make my entire app automatically open source (iOS only allows static linking). Any type of GPL license (reasonably) scares the crap out of ESRI, and so they will not touch it with a 10 foot pole. Hence, ArcGIS, the most popular GIS system in the world does not (and will probably never) support spatialite natively. This automatically kills it as a viable format.
Contrast this with the revised format:
Spatialite is awesome because it gets all the free functionality from SQLite. SQLite is used everywhere. It is on your Android Phone, on your iPhone/iPad, on Firefox, on Google Chrome, on several commercial embedded devices - can go on forever.
SQLite itself is a perfectly usable geospatial format - Spatialite extends it to make it sort of a portable PostGIS, but that level of power is beyond what's needed by most applications - after all, Shapefiles, GeoJSON, etc., don't have GEOS-provided query abilities and have become quite popular.
Spatialite uses GEOS, which is based on JTS. It's licensed under the MPL, GPL, and LGPL partially because of this dependency.(from the docs)
Thus simple SQLite (licensed under Public Domain) is a more viable format for closed-source applications to use.
So in my original post (the one that got 15+ votes from the community), I actually state that spatialite is not a viable format. In his revised version, sqlite is (which actually, it is not! sqlite has no spatial support whatsoever!)
I understand editing to improve the quality, but this is seriously ridiculous. If he wants to express his opinion, he is free to POST IT and let people vote for it. But editing the top accepted answer should be done very carefully, and in my humble opinion it is highly unethical to completely change the message of the answer in such a way.
I followed Kirk's suggestion and looked for a precedent in the StackOverflow Meta site:
For editors, it says:
- fix grammatical or spelling errors
- clarify meaning without changing it
- correct minor mistakes
- add related resources or links
- always respect the original author
and in this case, this was clearly violated.