We're shooting fish with a shotgun instead of just lobbing a grenade in the
lake.
Wiki combines the gist of many email threads and tries to abstract out a
common problem, discussing two solutions w.r.t. larger problems.
This is a superset of:
1] Axes swapping
2] ESRI and Cubewerks authorities hiding in EPSG namespace.
3] Publishing data with a Custom CRS
I also deal with the topic of coming up with theoretical solutions to
practical problems. 
http://docs.codehaus.org/display/GEOS/Unambiguous+Communication+of+CRS
It needs polish, but I need food.
Bryce
Updated the page with a quote from the WFS 1.1 specification, and explained that the URN approach was an experiment carried out by the OGC as part of OWS-3. I do expect a future WMS specification to use this approach, however you are correct that only a standards body can "force" agreement on these issues. Can we please ask our representatives at TOPP to explore these issues within the context of OWS-4, possible referring to your page.
We're shooting fish with a shotgun instead of just lobbing a grenade in the
lake.
Wiki combines the gist of many email threads and tries to abstract out a
common problem, discussing two solutions w.r.t. larger problems.
This is a superset of:
1] Axes swapping
2] ESRI and Cubewerks authorities hiding in EPSG namespace.
3] Publishing data with a Custom CRS
I also deal with the topic of coming up with theoretical solutions to
practical problems.
http://docs.codehaus.org/display/GEOS/Unambiguous+Communication+of+CRS
It needs polish, but I need food.
Bryce
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
geoserver-devel-bounces@lists.sourceforge.net wrote on 08/17/2006 11:02:47
PM:
Updated the page with a quote from the WFS 1.1 specification, and
explained that the URN approach was an experiment carried out by the OGC
as part of OWS-3. I do expect a future WMS specification to use this
approach, however you are correct that only a standards body can "force"
agreement on these issues. Can we please ask our representatives at TOPP
to explore these issues within the context of OWS-4, possible referring
to your page.
Thanks! It helps to have background from those who made the history. 
OWS-3 : <= 2004
WMS1.3.0: 2006
I think I see signs that WMS 1.3.0, while not flat-out adopting the URN
approach, produced a solution that appears to be informed by OWS-3. For
instance, the provision to use a URL wherever a EPSG:<code> is found smacks
of OWS-3 results (particularly option 2, using
http://www.opengis.net/gml/srs/epsg.xml#<EPSG code>. It appears that
they've expanded on the concept by allowing any URL which points to a file
with a CRS definition. So where OWS-3 uses a URL as an alternate means of
CRS ID reference (e.g., maybe that URL doesn't refer to a file at all?),
WMS 1.3.0 seems to use a URL in the more "normal" sense of locating a file
on the web. By doing so, they just happen to have gone a long way to
addressing most of our major issues.
I would like our buddies at TOPP to use WMS 1.3.0 in OWS-4, since it
appears that it makes some improvements in this very area...
Updated with an "education of data providers" solution.
Jody Garnett wrote:
Updated the page with a quote from the WFS 1.1 specification, and explained that the URN approach was an experiment carried out by the OGC as part of OWS-3. I do expect a future WMS specification to use this approach, however you are correct that only a standards body can "force" agreement on these issues. Can we please ask our representatives at TOPP to explore these issues within the context of OWS-4, possible referring to your page.
I wonder if we could get one of you communicating directly somehow under the TOPP umbrella?
Also please note that our OWS-4 is quite different than your OWS-3 stuff Jody. We're just doing CITE, so we're really breaking no new ground, aren't involved in the conversations about the future of specs at all.
best regards,
Chris
We're shooting fish with a shotgun instead of just lobbing a grenade in the
lake.
Wiki combines the gist of many email threads and tries to abstract out a
common problem, discussing two solutions w.r.t. larger problems.
This is a superset of:
1] Axes swapping
2] ESRI and Cubewerks authorities hiding in EPSG namespace.
3] Publishing data with a Custom CRS
I also deal with the topic of coming up with theoretical solutions to
practical problems.
http://docs.codehaus.org/display/GEOS/Unambiguous+Communication+of+CRS
It needs polish, but I need food.
Bryce
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:1003,44e54aa1238571365099012!
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
> I would like our buddies at TOPP to use WMS 1.3.0 in OWS-4, since it
appears that it makes some improvements in this very area...
Unfortunately we're only doing WFS 1.1 reference implementation, not WMS 1.3. Though we should have the full infrastructure in place to do different specs, it'd be great to start to implement some of the useful stuff in 1.3 (like returning text/xml for the mime type instead of the weird ogc type that no browsers recognize).
Chris
Updated with an "education of data providers" solution.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:1003,44e5db72292254820651628!
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
Chris Holmes wrote:
Updated the page with a quote from the WFS 1.1 specification, and explained that the URN approach was an experiment carried out by the OGC as part of OWS-3. I do expect a future WMS specification to use this approach, however you are correct that only a standards body can "force" agreement on these issues. Can we please ask our representatives at TOPP to explore these issues within the context of OWS-4, possible referring to your page.
I wonder if we could get one of you communicating directly somehow under the TOPP umbrella?
Now that you have a PSC that may be possible.
Also please note that our OWS-4 is quite different than your OWS-3 stuff Jody. We're just doing CITE, so we're really breaking no new ground, aren't involved in the conversations about the future of specs at all.
No worries, you still have an ear to those all important email lists Consider this as representing a concerned community of developers, your developers.
Jody