SVG links and resources

Data-Driven SVG Apps: A Rapid Development Approach
Consider the business example of a building floor plan. The user wants to be able to pull up a digital image (GIF or JPEG file) of the floor plan; review and annotate the drawing to note locations of electrical outlets, phone jacks, and ethernet jacks; and save the changes into a database. Annotations are done by creating red rectangles for electrical outlets, blue rectangles for phone jacks, and green rectangles for Ethernet jacks. In addition to the graphics, the user can specify properties like the number of electrical outlets at the location, the number of phone jacks and the telephone numbers at each location; and the number of Ethernet jacks and the IP addresses at the location. For the above example, the appeal of SVG is that an XML document can be created dynamically on the server while pulling content (graphical and business) from a database, while changes made by the user can be updated in the database. This role is traditionally performed by the middle tier. The middle tier, in this case, will create the SVG file by extracting data from database, and parse the SVG file and update the database. [Full Article]
Demo that shows dragging houses onto a satellite map and then entering data.
Includes detailed explanation of how-to. Data is stored in an Oracle
Example of a database-driven map using PostgreSQL and the PostGIS plug-in
PostGIS adds support for geographic objects to the PostgreSQL database, follows the “Simple Features Specification for SQL” defined by the OpenGIS Consortium (OGC) and allows to store, index and query geometric features like point, line, polygon, multipoint, multiline, multipolygon
and geometry collections in 2d as well as 3d coordinate space. [Full Article]