worldKit, like PointMapper,displays points on maps, and the points can be loaded from XML files. The significant difference is this: PointMapper is controlled by a scripting API that can change the displayed content (both map and points) at any time. In contrast, worldKit provides no external control once the map has been placed on the page and supplied with its configuration; it will follow its own rules thereafter. This includes periodic update of data from a url that may deliver changing content, but not script-driven update.
Scripting provides much more flexibility in how Pointmapper is used. At its simplest, script control allows points to be highlighted under user control via links in the containing page (see Top New York Restaurants). Slightly more complex examples, such as Places in Astoria and "Where I've Lived", involve coordination of the map state with other browser content, allowing custom navigation of location-related information. Finally, we intend to update our other Mappers: Blogmapper, RDFMapper, and *Mapper, to use PointMapper; this will involve deploying PointMapper as the client-side component of an architecture that includes server-side manipluation of located content.
Indy Junior also displays points loaded from XML files on maps, but has some special features oriented towards displaying travel histories. For example, it provides the option of connecting the points with lines in temporal order. However, like worldKit, it provides no external scripting control.