<HTML><HEAD>
<META content="text/html; charset=ISO-8859-1" http-equiv=Content-Type></HEAD>
<BODY dir=ltr bgColor=#ffffff text=#000000>
<DIV dir=ltr>
<DIV style="FONT-FAMILY: 'Times New Roman'; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>Cameron -</DIV>
<DIV> </DIV>
<DIV>Thanks for the comments.</DIV>
<DIV> </DIV>
<DIV>In response to your question regarding an Open Source reference
implementation, the question is valid. However, at this point in the standards
track process (public comment), there is no requirement for a reference
implementation. Reference implementations are typically developed provided as
part of the compliance testing framework. That said, once the public comment
period is over your questions and comments need to be discussed and answered by
the SWG.</DIV>
<DIV> </DIV>
<DIV>Regards</DIV>
<DIV> </DIV>
<DIV>Carl</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">
<DIV style="FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A
title=cameron.shorter@lisasoft.com
href="mailto:cameron.shorter@lisasoft.com">Cameron Shorter</A> </DIV>
<DIV><B>Sent:</B> Tuesday, July 24, 2012 4:51 PM</DIV>
<DIV><B>To:</B> <A title=requests@lists.opengeospatial.org
href="mailto:requests@lists.opengeospatial.org">requests@lists.opengeospatial.org</A>
</DIV>
<DIV><B>Cc:</B> <A title=standards@lists.osgeo.org
href="mailto:standards@lists.osgeo.org">standards@lists.osgeo.org</A> </DIV>
<DIV><B>Subject:</B> Re: [OSGeo-Standards] JSON in OGC standards (REST API
CandidateStandard)</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">
<DIV class=moz-cite-prefix>OGC,<BR>As an OGC member (from LISAsoft), I would
like to second Volker's comment's below regarding GeoJSON.<BR><BR>I would also
like to ask:<BR>* Has the REST API standard been tested amongst multiple client
and server applications, as is usually done in OGC Open Web Services
Testbeds?<BR><BR>* Is there an Open Source reference implementation of the REST
API standard, as has been the case for most (all?) OGC standards to
date.<BR><BR>I'm nervous that the proposed REST API standard may be supported by
one vendor, but has not been given the attention required to be adopted broadly
by other applications.<BR><BR>On 24/07/2012 7:57 PM, Volker Mische
wrote:<BR></DIV>
<BLOCKQUOTE cite=mid:500E717E.7090808@gmail.com type="cite"><PRE wrap="">Hi all,
I've just discovered that the upcoming GeoServices REST API [1] standard
doesn't make use of GeoJSON, but has it's own JSON format for geometries.
I'm well aware that GeoJSON is not an OGC standard, but no one can argue
that it's not widely used. The objective of the GeoServices REST API is
to be backwards compatible to the ESRI implementation. This of course
makes sense for ESRI, but is it really what the OGC wants/is about?
Does the OGC really want to have a standard with JSON encoded geometries
which are not compatible to an already existing specification?
"Widely used" is hard to put into numbers, but I think it this case, we
could just count how many GeoJSON parsers out there, and how many
GeoServices REST API JSON encoded geometry parsers are out there.
Would it make sense to file an official change request? Or is it not
worth the hassle as it would be taken down immediately, as it is a
backwards incompatible change?
[1] <A class=moz-txt-link-freetext href="http://www.opengeospatial.org/standards/requests/89">http://www.opengeospatial.org/standards/requests/89</A>
Cheers,
Volker
_______________________________________________
Standards mailing list
<A class=moz-txt-link-abbreviated href="mailto:Standards@lists.osgeo.org">Standards@lists.osgeo.org</A>
<A class=moz-txt-link-freetext href="http://lists.osgeo.org/mailman/listinfo/standards">http://lists.osgeo.org/mailman/listinfo/standards</A>
</PRE></BLOCKQUOTE><BR><BR>
<DIV class=moz-cite-prefix>On 20/07/2012 4:31 AM, <A
class=moz-txt-link-abbreviated
href="mailto:announce@opengeospatial.org">announce@opengeospatial.org</A>
wrote:<BR></DIV>
<BLOCKQUOTE cite=mid:38a2f8f06dcaf34b60d1032705fe4dbb@lists.opengeospatial.org
type="cite">
<P> <A href="http://www.opengeospatial.org/" moz-do-not-send="true"><IMG
alt=OGC
src="wlmailhtml:{8528F953-D77A-4723-82D4-7F66E6A7ADAF}mid://00000337/!cid:part1.03060201.05050204@lisasoft.com"></A></P>
<HR>
<P>FOR IMMEDIATE RELEASE <BR><BR>Contact: <A
class=moz-txt-link-abbreviated
href="mailto:info@opengeospatial.org">info@opengeospatial.org</A>
<BR><BR><BR>OGC Seeks Comments on GeoServices REST API Candidate
Standard<BR><BR>19 July 2012. The Open Geospatial Consortium (OGC®) seeks
public comment on the candidate OGC GeoServices REST API standard. The
GeoServices REST Application Programming Interface (API) provides a standard
way for web clients to communicate with geospatial technologies, such as
Geographic Information System (GIS) servers, based on Representational State
Transfer (REST) principles.<BR><BR>Using this API, clients, such as a web
browser application, issue requests to resources on the server identified by
structured Uniform Resource Locators (URLs). The server responds with map
images, text-based location details or other representations of geospatial
information. From a services perspective the API offers a mechanism to
interact with map, image and feature services and perform geospatial analysis.
This JavaScript Object Notation (JSON)-based, RESTful API is intended to make
implementing servers instantly usable by developers working with widely used
REST-based scripting and programming languages, as well as mobile platforms.
End users can then use these developers' Web applications to discover and
access the services and use them in their workflows. <BR><BR>In early 2011,
Esri contacted the Open Geospatial Consortium about submitting the GeoServices
Rest API as a candidate OGC standard. This submission was approved through the
OGC process and then a Standards Working Group (SWG), composed of many OGC
members, performed a detailed review and rewrote the API as an OGC interface
standard, removing Esri-specific software references. The OGC’s adoption of
this candidate standard will provide the wider Web developer community with
additional standards-based choices for leveraging geospatial
information.<BR><BR>The candidate OGC GeoServices REST API standard documents
are available for review and comment at <A class=moz-txt-link-freetext
href="http://www.opengeospatial.org/standards/requests/89">http://www.opengeospatial.org/standards/requests/89</A>.<BR><BR>The
closing date for comments will be 18 August 2012.<BR><BR>The OGC is an
international consortium of more than 445 companies, government agencies,
research organizations, and universities participating in a consensus process
to develop publicly available geospatial standards. OGC Standards support
interoperable solutions that "geo-enable" the Web, wireless and location-based
services, and mainstream IT. OGC Standards empower technology developers to
make geospatial information and services accessible and useful with any
application that needs to be geospatially enabled. Visit the OGC website at <A
class=moz-txt-link-freetext
href="http://www.opengeospatial.org/contact">http://www.opengeospatial.org/contact</A>.</P>
<HR>
<P> </P>
<DIV class=icons><A title="Join on
LinkedIn"
href="http://www.linkedin.com/groups?mostPopular=&gid=55322"
moz-do-not-send="true"><IMG alt="Join on LinkedIn"
src="wlmailhtml:{8528F953-D77A-4723-82D4-7F66E6A7ADAF}mid://00000337/!cid:part3.07070207.05050900@lisasoft.com"></A>
<A title="Follow on Twitter" href="https://twitter.com/opengeospatial"
moz-do-not-send="true"><IMG alt="Follow
on Twitter"
src="wlmailhtml:{8528F953-D77A-4723-82D4-7F66E6A7ADAF}mid://00000337/!cid:part5.04010802.04000609@lisasoft.com"></A>
<A title="OGC Youtube Channel" href="http://www.youtube.com/user/ogcvideo"
moz-do-not-send="true"><IMG alt="OGC
Youtube Channel"
src="wlmailhtml:{8528F953-D77A-4723-82D4-7F66E6A7ADAF}mid://00000337/!cid:part7.04040808.03010107@lisasoft.com"></A></DIV><BR><BR>
<DIV class=emailfooter>--<BR><BR>If you do not want to receive any more
messages, please visit <A
href="http://lists.opengeospatial.org/lists/?p=unsubscribe&uid=fc172449de56bd8945a043139bc9388d"
moz-do-not-send="true">this link</A><BR>To update your preferences and to
unsubscribe visit <A
href="http://lists.opengeospatial.org/lists/?p=preferences&uid=fc172449de56bd8945a043139bc9388d"
moz-do-not-send="true">this link</A><BR>To forward a message to someone you
may use <A
href="http://lists.opengeospatial.org/lists/?p=forward&uid=fc172449de56bd8945a043139bc9388d&mid=101"
moz-do-not-send="true">this link</A></DIV></BLOCKQUOTE><BR><BR><PRE class=moz-signature cols="72">--
Cameron Shorter
Geospatial Solutions Manager
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254
Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source
<A class=moz-txt-link-freetext href="http://www.lisasoft.com">http://www.lisasoft.com</A>
</PRE><BR><PRE class=moz-signature cols="72">--
Cameron Shorter
Geospatial Solutions Manager
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254
Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source
<A class=moz-txt-link-freetext href="http://www.lisasoft.com">http://www.lisasoft.com</A>
</PRE>
<P>
<HR>
_______________________________________________<BR>Standards mailing
list<BR>Standards@lists.osgeo.org<BR>http://lists.osgeo.org/mailman/listinfo/standards<BR></DIV></DIV></DIV></BODY></HTML>