There are many very useful static representations of forms, not least of
which is to document the design thereof. My first exposure to SGML was
writing a process to generate printed specifications for an online
application of several 100 (if not thousands) of interactive panels, all
created in SGML using a now-defunct language IBM developed for use in OS/2
(it may still live in CICS, I'm not sure--it was also used there for a
while). Because the documents that defined the panels included references
to variables, described branching and control structures, and on so, I was
able to generate both pictures of the panels (using character-based
graphics, no less) and generate lots of information about the panels. By
doing this, we eliminated the need to do screen snaps to document the
panels, which we estimated saved a minimum of two calandar weeks per rev of
the spec (that being the amount of time it would take to make the snaps and
assemble the document).
Likewise, hyperlinks can be represented in print in any number of ways
(witness the SGML handbook). The interactivity of hyperlinks is not what
distinquishes them, it is the relationship they represent. There are many
ways to present and make useful such relationships, of which interactive
traversal is only one (and not necessarily the most useful).
Cheers,
E.
-- <Address HyTime=bibloc> W. Eliot Kimber, Senior Consulting SGML Engineer Highland Consulting, a division of ISOGEN International Corp. 2200 N. Lamar St., Suite 230, Dallas, TX 95202. 214.953.0004 www.isogen.com </Address>xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To (un)subscribe, mailto:majordomo@ic.ac.uk the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)