Simplified GeoJSON proposal

I've come up an extremely simplified GeoJSON example which can do everything that the current GeoJSON specification can do but with only 4 core elements. Every element is a feature and can contain a list of points, lines and polygons or other features. Everything else in the GeoJSON spec is pretty much taken from some OGC standard or another. It's important not to get caught up in the past we are at the beginning of a potential standard, as Sean said in his post: "there's only one first chance to get a standard right." The only thing that I think might be questionably useful about this would be the nesting of features.

{
    "points":[
            [x0,y0], [x1,y1], ..., [xn,yn]
        ],
    "lines":[
            [x0,y0, x1,y1, ..., xn,yn],
            ...
        ],
    "polygons":[
        [
            [x0,y0, x1,y1, ..., xn,yn],
            ...
        ],
        [
            [x0,y0, x1,y1, ..., xn,yn],
            ...
        ],
        ...
    ],
    "features":[
        {
            "points":[
               [x0,y0], [x1,y1], ..., [xn,yn]
            ],
            "lines":[
                ...
            ]
        },
        ...
    ]
}

Also an optional "crs" coordinate reference system can contain an EPSG code, ESRI WKT (Well Known Text) or a PROJ.4 projection string or all 3. If none is specified, the default is decimal degrees in the WGS84 datum. The coordinate reference system of the parent cascades down the to all children until a child specifies one.

"crs":{
    "epsg":"4326",
    "wkt":"COMPD_CS["OSGB36 / British National Grid...",
    "proj4":"+proj=utm +zone=15 +ellps=GRS80 +datum=NAD83 +units=m +no_defs"
}

Another useful item would be an optional "bounds" element that specifies the bounding envelope in the element's crs.

"bounds":[min_lon, min_lat, max_lon, max_lat]

Minimalistic and precise.