<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="+1">Chris, <br>
<br>
The major thing a fast track needs is an extant set of conformance
classes; what essentially is a complete abstract test suite for
the proposed standard. This is the principle gotcha that force the
GeoServices REST API into an SWG. <br>
<br>
Regards, <br>
John <br>
<br>
There is a crack in everything <br>
That's how the light gets in.<br>
-- 'Anthem' by Leonard Cohen,
1992<br>
<br>
The opinions expressed in this email are purely my own and do not
necessarily<br>
represent the opinions of any organization or otherwise sane
person or persons.<br>
<br>
John R. Herring<br>
Architect, Spatial Products<br>
Oracle Corporation<br>
One Oracle Drive<br>
Nashua, New Hampshire 03062<br>
ph: +1 (603) 897 3216<br>
fx: +1 (603) 897 3334<br>
<br>
Annue c½ptis - Novus Ordo Seclorum<br>
<br>
</font><br>
On 2011-07-25 12:57 PM, Chris Holmes wrote:
<blockquote
cite="mid:CAGbd94uML4Aeu2HrrMBVBqExuXvxdCRmX=gVTihJUEAjhGdxng@mail.gmail.com"
type="cite">I've already been talking to Carl, OGC is for sure
interested in bringing it in, and Carl was the one who told me
about the existence of the fast track process. Of course it is a
consensus process of the members, so some may put up resistance,
but I believe there are good arguments to keep it just as it is.
<div>
<br>
</div>
<div>Chris<br>
<br>
<div class="gmail_quote">On Fri, Jul 22, 2011 at 12:36 PM, Carl
Smyth <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:steve@mobilegis.com">steve@mobilegis.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size: 11pt;
color: rgb(31, 73, 125);">As a developer using and
occasionally defending GeoJSON I don’t see how
fast-tracking it through the OGC process without
changes can hurt. It might well prevent some of the
app-breaking forks and changes/extensions proposed
from time to time. I guess the one
danger/opportunity that might be a consideration is
that the OGC Simple Features SWG deals with the same
concepts. There might be some resistance to
approving a standard offering incomplete
compatibility with OGC’s simple features (which are
growing less simple). This would be a question for
the OGC Architectural Board and Carl Reed <a
moz-do-not-send="true"
href="mailto:creed@opengeospatial.org"
target="_blank">creed@opengeospatial.org</a> could
give a read on this if he hasn’t already.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
color: rgb(31, 73, 125);">…steve</span></p>
<p class="MsoNormal"><a moz-do-not-send="true"
name="13152b3711bdb836__MailEndCompose"><span
style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></a></p>
<p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span
style="font-size: 10pt;"> <a moz-do-not-send="true"
href="mailto:geojson-bounces@lists.geojson.org"
target="_blank">geojson-bounces@lists.geojson.org</a>
[mailto:<a moz-do-not-send="true"
href="mailto:geojson-bounces@lists.geojson.org"
target="_blank">geojson-bounces@lists.geojson.org</a>]
<b>On Behalf Of </b>Chris Holmes<br>
<b>Sent:</b> Friday, July 22, 2011 9:17 AM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:geojson@lists.geojson.org"
target="_blank">geojson@lists.geojson.org</a><br>
<b>Subject:</b> [Geojson] GeoJSON as OGC standard?</span></p>
<div>
<div class="h5">
<p class="MsoNormal"> </p>
<p class="MsoNormal">I've been talking to OGC folks
recently, and was wondering if this group would
have interest in getting GeoJSON becoming an
official OGC standard. They are becoming more
interested in lighter weight standards, and said
that GeoJSON could likely move on a 'fast track'
process. One other thing that I didn't know is
that candidate specs developed outside the OGC can
be brought in and approved as an OGC standard
while at the same time the spec development can
remain external to the OGC. So the spec can
continue to evolve on this list (though I feel
it's been quite stable for awhile, so may not need
to), with this community having control of it.
After it's updated then can be submitted to OGC.</p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">I'd personally like to see
this happen. I know some in this group aren't
that excited about OGC specs, but they do have
really great international visibility, and we'd
likely see even more adoption of GeoJSON as some
implementors want to be able to point at an
official approved international standard. I'd
be happy to shepherd it through the process, and
I definitely will be against any type of forking
or changes to it (I was quite unhappy with how
OGC took TMS type ideas and came out with the
much more confusing WMTS). But definitely don't
want to put the time in if people in this
community are against it, as I think the process
of GeoJSON development has been great, and
wouldn't want to change it. I'd just ideally
like the best of both worlds - specs developed
openly, but the best adopted and promoted by
OGC.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">best regards,</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Chris</p>
<div>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Geojson mailing list<br>
<a moz-do-not-send="true"
href="mailto:Geojson@lists.geojson.org">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>
<br>
</blockquote>
</div>
<br>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Geojson mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Geojson@lists.geojson.org">Geojson@lists.geojson.org</a>
<a class="moz-txt-link-freetext" href="http://lists.geojson.org/listinfo.cgi/geojson-geojson.org">http://lists.geojson.org/listinfo.cgi/geojson-geojson.org</a>
</pre>
</blockquote>
</body>
</html>