One of the cool things about SVG is that it is totally namespace-conformant
and namespace-friendly which allows arbitrary supplemental data to be
included in the SVG content, such as what Lance demonstrates below with the
'tnt:' prefix.
Due to SVG DOM and JavaScript, it is possible to leverage the embedded
supplemental data to cause alternate views of the same information. The
default view is the initial SVG graphical view. Via the DOM, it is possible
to make different things appear, such as hidden layers, or to present
entirely different presentations of the same information. Instead of a map,
you might show a bar chart or a table, for example.
(I'm back to the model-view-controller notion. The original data is the
model, which can be embedded inside the SVG or XHTML in its original form
due to the wonders of XML namespaces. The controller is a combination of
server-side scripting (e.g., Perl) and client-side scripting (e.g.,
JavaScript). Multiple views are possible by generating the necessary SVG
via server-side or client-side scripting.)
Jon
At 06:23 AM 6/29/2002 -0500, you wrote:
>Jim Ley wrote:
>
> > "Lance Dyas" <lancelot@xxxxxxxxxxxx>
> > > I'm actually surprised, the boss is considering putting the print2svg
> > > capability in the TNTlite product an enticement to familiarize people
> > > with the main products of course. (TNTlite is generally export disabled
> > > so this would be in my opinion a relatively major decision)
> >
> > One thing I've noticed from the SVG output of GIS systems (never looked
> > personally at the systems, just in examples posted to the list and
> > elsewhere.) is that the SVG is a purely visual format with no semantic
> > information in it -
>
>You may have hit the nail on the head. We have two different routes of
>export svg out of our product
>at the moment the one I've demo'd is basically through a print
>process.... "layer names" and
>descriptions might be the only semantics available. This kind of limit
>might be why it is reasonable
> to make it accessable in TNTlite.
>
> > So do any of the GIS people know of any SVG tools which include semantic
> > information, or have any ideas in this direction?
> >
> > Jim.
>
>I guess this other aspect could bring the main TNTmips product back in
>the picture.
>
>The other route is via a true export during which a database attachment
>can be done, Im looking at
>including an about this on the right click menu which invokes a pop up
>listing the fields and values
>database.
>
><path d="M124,234 l3,5h2 ..... ">
> <tnt:field0>value</tnt:field0>
> <tnt:field1>value</tnt:field1>
></path>
>
>
>Lance
>
>
>
>
>
>
>-----
>To unsubscribe send a message to: svg-developers-unsubscribe@xxxxxxxxxxxxxxx
>-or-
>visit http://groups.yahoo.com/group/svg-developers and click "edit my
>membership"
>----
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
|
