<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Tim,<br>
<br>
yes I know, that there are partial clean-up attempts with focus on
a specific topic (like your patch #6 removing crsURN) but not
transporting the document into a consistent state, which is ok,
but I think as time goes by not the best we can achieve. As I had
to base my clean-up patch on some revision and repo, I picked the
latest you merged, to be on the safe side. <br>
<br>
In the light of the latest somehow diverging discussions, I
thought a minimal consensus edition might help remain patient and
have a clear view on the remanining tasks before entering the
public comment phase, that will start when submitting the first
revision to IETF I-D queue. The submission will just be the
beginning :-)<br>
<br>
So applying the patch #10 as wrap-up gives us all the advantage of
a clean start for the finish and if many of the authors meet in
person during this north american conference in
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Minneapolis, MN, USA all the better, to start placing the final
golden minimal CRS statements into the cleaned-up consistent
document as close as possible to a broad consensus (in my
understanding of the exchanged messages).<br>
<br>
My proposal is thus: <br>
a) Apply #10, <br>
b) some discuss the final statements about the relation of
Coordinate Reference Systems and GeoJSON during the conference, <br>
c) short discussion on concrete pull request based on the
outcome of b) then <br>
d) merge and<br>
...) <br>
r) ready for submission we are :-).<br>
<br>
Good idea? Not so good idea? Please share your thoughts.<br>
<br>
Stefan.<br>
<br>
On 21.05.13 18:57, Tim Schaub wrote:<br>
</div>
<blockquote
cite="mid:CAGk9+j3wX8VBc2Z3mB9Dtsz29H5-p2OVSzO_3n6ZaLU1yMbccQ@mail.gmail.com"
type="cite">
<div dir="ltr">Note also that I have a pull request outstanding to
remove crsURN:
<div><a moz-do-not-send="true"
href="https://github.com/GeoJSONWG/draft-geojson/pull/6">https://github.com/GeoJSONWG/draft-geojson/pull/6</a></div>
<div><br>
</div>
<div>
I think we'd all agree that there needs to be some discussion
of CRS in the spec. This is missing from your pull request.
Minor work to add it in, but it needs to be there.</div>
<div><br>
</div>
<div>I imagine a number of us will be at the FOSS4G-NA
conference through the end of the week. So while discussion
on this list might stagnate, we could have some in-person
discussion about this.</div>
<div><br>
</div>
<div>Tim</div>
<div><br>
<div><br>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, May 20, 2013 at 7:31 AM, Stefan
Drees <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:stefan@drees.name" target="_blank">stefan@drees.name</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Dear all,<br>
<br>
I snet a pull request, where I:<br>
<br>
* simply removed the CRS (and any crsURI stuff),<br>
* also removed my intermediate notes,<br>
* and removed the now unused references to HTTP, TLS, URx
RFCs,<br>
* rephrased the Polygon section for readability,<br>
* edited some lines to remain inside line length limit,<br>
* updated the date to May 2013,<br>
* enhanced the security considerations section (using the
JSON Patch<br>
RFC as role model) to somehow delegate security back to
JSON where it<br>
belongs, as we do not add anything security relevant on
top<br>
* and sync'ed the section number for the bounding box
references inside<br>
our document.<br>
<br>
The pull request #10 is at<br>
<br>
<a moz-do-not-send="true"
href="https://github.com/GeoJSONWG/draft-geojson/pull/10"
target="_blank">https://github.com/GeoJSONWG/draft-geojson/pull/10</a><br>
<br>
If one likes to se the outcome of merging it, maybe<br>
<br>
<a moz-do-not-send="true"
href="http://sdrees.github.io/draft-geojson/draft.html"
target="_blank">http://sdrees.github.io/draft-geojson/draft.html</a><br>
<br>
is a good place or<br>
<br>
<a moz-do-not-send="true"
href="http://sdrees.github.io/draft-geojson/draft.txt"
target="_blank">http://sdrees.github.io/draft-geojson/draft.txt</a><br>
<br>
This patch should merge the essence of our latests planned
changes for the to be submitted draft (as far as I
understood the ideas of most on this list).<br>
<br>
Am I right? Not so right? What do you think?<br>
<br>
PS: If you read an archived version of this mail, some links
stated in above text may result in HTTP 404 Not found as
these mostly point to intermediate working material.<br>
<br>
All the best,<br>
Stefan Drees.<br>
_______________________________________________<br>
GeoJSON mailing list<br>
<a moz-do-not-send="true"
href="mailto:GeoJSON@lists.geojson.org" target="_blank">GeoJSON@lists.geojson.org</a><br>
<a moz-do-not-send="true"
href="http://lists.geojson.org/listinfo.cgi/geojson-geojson.org"
target="_blank">http://lists.geojson.org/listinfo.cgi/geojson-geojson.org</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
Tim Schaub<br>
OpenGeo <a moz-do-not-send="true" href="http://opengeo.org/"
target="_blank">http://opengeo.org/</a><br>
Expert service straight from the developers.<br>
</div>
</blockquote>
<br>
</body>
</html>