Sunburned Surveyor wrote: > Martin wrote: "I think I'm keen on pursuing the Super-Simple GML > route. That has the best chance of being readable by other tools, I > think." > > That is too bad. I was starting to like YAML. :] I'm actually going to > try using it for a parseable change log on the SurveyOS SVN Repository > module for JTSWarped. I'll let you know how that goes. > Go for it! YAML does seem nifty. And there's nothing saying that someone shouldn't write a GeoYAML parser (wanna get 15 mnin of fame? Start a GeoYAML wikipedia entry...) > There was some discussion of the super-simple GML route on the OSGeo > standards mailing list this morning. (You really should subscribe > Martin.) :] > And I will... > Raj pointed me to these samples of a simple GML proposal made about > five (5) years ago. Here is part of his message: > > " BXFS (http://www.ogcnetwork.net/node/189): basically the "GML 2 > > > What do you think? > I think it's *too* simple. It would need typing information added. Given that, I'd opt for either adding metadata attributes to constrainted GML, or using the in-line schema idea.
And the example doesn't even contain any spatial! > -- Martin Davis Senior Technical Architect Refractions Research, Inc. (250) 383-3022 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
