Mapping

Well I am back in town and have had some time to read up on stuff and work
a bit with mapping.  For so many years I have completely avoided
JavaScript because of cross-browser issues and simple page design
principles.  For this project I have finally broken out of that and I've
already been bitten by it.  Apparently Safari does not have an actual DOM
parser and so it is unable to handle any kind of fancy XML.  It can handle
basic stuff and certainly has functions to work with XML elements but it
is far from sufficient for handling RDF/XML.  This is unfortunate since
RDF/XML would be awesome to use.  My thoughts at this point are these:

1) Leave Safari completely in the dust, for now, anyway.
2) Maintain an rdf file that gets run through a script to produce a more
docile xml file that just describes GoogleMaps objects.

Item 1 bugs me because I use Safari (I'm not really sure why - maybe just
lazy - or stubborn) and it is a somewhat significant browser to not
support it.

Item 2 is annoying because the xml file will either be potentially out of
date or a server will have a big load put on it in order to convert on the
fly.  Additionally, this makes for an inflexible client-side
implementation.

My temptation right now is to stick with #2 and hope that something else
happens to kill the issue with Safari.  For instance, a DOM parser
implmented entirely in JavaScript would be great, although slow.

Regarding RDF/XML, I think I can get the data I need defined just by using
an rdf schema that adds two properties to the already available classes. 
As for GoogleMaps having cool area graphics (like for node coverage)
someone has implemented a library to extend GoogleMaps with the ability to
have filled polygons and the like.

That's all for now.  Cheers.

-Jeff



_______________________________________________
Talk mailing list
[email protected]
http://seattlewireless.net/mailman/listinfo/talk