added note to discuss naming for new optional profile/namespace member and enhanced section security considerations by motivating and pointing to the relevant section in the JSON RFC
Removing crs

This makes all GeoJSON objects Geographic/WGS84 in sensible longitude, latitude order.
Merge branch 'master' of https://github.com/sgillies/draft-geojson
merged pull request from sgillies which promotes the practice of long, lat coords using the default CRS (which is the same as with KML) over the practice of using projected coordinates or, worst of all, lat/lng coordinates
added T. Schaub to the list of authors as requested per the mailing list
added T. Schaub to the list of authors as requested per the mailing list and handled middle.mkd merge conflict from attempted 2nd pull merge by cowardly ignoring changes for now. Please request pull again based on new revision. Thanks
Fixed typos and some language

Interior rings must fall within the geometry of the exterior ring, not just the convex hull of the exterior ring.
Interior rings must fall within the geometry of the exterior ring, not just the convex hull of the exterior ring. (merged pull request by mpdaly
Reverting back to 8543af59326a596a1320e1d5c7ee717143c91f01 (closes #4)
Adding tschaub to authors as discussed on mailing list

This is a subset of 61b837402eb0b5ec19f7c19e7710fdfbdbf47d71 (which was reverted in b4d6c641a84eb50d49cd50f1983bf06dd6659181).
Update readme with hints on generating built docs

This extracts the portion of df367f71065aa52bcb06e6ffa1bea944a83ec3e9 (authored by @sdrees) that updated the README.md.
Removing built docs and updating instructions on building them
Merge pull request #4 from tschaub/master

This reverts us to 8543af59326a596a1320e1d5c7ee717143c91f01, uncomments me as an author, removes built docs from the repo, and adds some instructions on building them.
Fixed typos and some language

Interior rings must fall within the geometry of the exterior ring, not just the convex hull of the exterior ring.
Removing validity constraint for polygons
Merge pull request #7 from tschaub/invalid

Remove validity constraint from polygons
Clearly state that GeoJSON is a RFC6906 profile of JSON.

RFC4267 doesn't specify any media type parameters, but a profile
parameter is a big help to GeoJSON. Without it, we'd probably need
a custom media type. GeoJSON's use of a profile parameter does not
alter the (JSON) processing model, it only indicates that the root
object contains geographic features to be interpreted according to
the GeoJSON spec.