Wednesday, June 11, 2008

X my L

Uh oh, the most unkillable meme in the OSGeo firmament is back, the XML map file. Even more unkillable than the "rasters in PostGIS" meme, the XML map file waits out the winters under the thick bark of .Net and Java programmers and blossoms every six months or so, until knocked back by the harsh frost of having-to-do-it-yourself and a Skeptical Development Community.

Me? I'm all for it. Check out my shopping list for today.



For me, it's all about human readability.
 

7 comments:

James Fee said...

You might want to depreciate tomatoes these days.

Bill said...

If it were me, type and quantity would be attributes rather than tags but you say tomato... :)

xanadont said...

Can you transform this into RSS, please? I want to subscribe to your food feed.

Allan Doyle said...

Is that valid GML? Where's the CRS?

Regina Obe said...

I guess I'm the only one that thinks XML is overrated. Sure XML is easier to validate but who cares. I write perfect map files that don't need any validation.

Rasters in PostGIS though. Think of the possibilities Paul. Not just satellite but useful analytical stuff with DEMs etc.

Paul Ramsey said...

I think you missed my smiley face, Regina. :)

Tom said...

Paul, where's the schema? :)

I think the MapServer mapfile was put forth before the days of XML, and probably would have been XML-based if it had been defined post 2001-ish.

I love the current mapfile format, in terms of creating it by hand. When it comes to programmatic access, I think XML (and the wide range of tools/parsers out there) would better serve a mapfile definition.

If we were to indeed come up with an XML-based mapfile, the possibility of cross-project interoperability becomes appealing. Having said this, there is a fine line in defining a format based on consensus, and allowing enough extensibility without allowing too much "fairy dust" (one of my favourite terms, from Rob Atkinson, 2003), which something like xs:any potentially provides.

Here's a neat link which discusses XML and when to use:

http://www.w3.org/TR/webarch/#xml-when

In the end, I think the most important thing is consensus in the community.

..Tom (who still prototypes XML schemas by hand)

About Me

My Photo
Victoria, British Columbia, Canada

Followers

Blog Archive

Labels

bc (37) it (29) postgis (19) icm (11) video (11) enterprise IT (10) sprint (9) open source (8) osgeo (8) cio (6) foippa (6) gis (6) management (6) spatial it (6) enterprise (5) foi (5) foss4g (5) mapserver (4) outsourcing (4) politics (4) bcesis (3) oracle (3) COTS (2) architecture (2) boundless (2) esri (2) idm (2) natural resources (2) ogc (2) open data (2) opengeo (2) openstudent (2) postgresql (2) rant (2) technology (2) vendor (2) web (2) 1.4.0 (1) HR (1) access to information (1) accounting (1) agile (1) aspen (1) benchmark (1) buffer (1) build vs buy (1) business (1) business process (1) cathedral (1) cloud (1) code (1) common sense (1) consulting (1) contracting (1) core review (1) crm (1) crockofshit (1) custom (1) data warehouse (1) deloitte (1) design (1) digital (1) email (1) essentials (1) evil (1) exadata (1) fcuk (1) fgdb (1) fme (1) foocamp (1) foss4g2007 (1) ftp (1) gds (1) geocortex (1) geometry (1) geoserver (1) google (1) google earth (1) government (1) grass (1) hp (1) iaas (1) icio (1) industry (1) innovation (1) integrated case management (1) introversion (1) iso (1) isss (1) isvalid (1) javascript (1) jts (1) lawyers (1) mapping (1) mcfd (1) microsoft (1) mysql (1) new it (1) nosql (1) opengis (1) openlayers (1) oss (1) paas (1) pirates (1) policy (1) portal (1) proprietary software (1) qgis (1) rdbms (1) recursion (1) redistribution (1) regression (1) rfc (1) right to information (1) saas (1) salesforce (1) sardonic (1) seibel (1) sermon (1) siebel (1) snark (1) spatial (1) standards (1) svr (1) taxi (1) tempest (1) texas (1) tired (1) transit (1) twitter (1) uber (1) udig (1) uk (1) uk gds (1) verbal culture (1) victoria (1) waterfall (1) wfs (1) where (1) with recursive (1) wkb (1)