TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: XML as a document language From:<puff -at- guild -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 22 May 2001 16:04:43 -0400
Sean Brierley (Sean -at- Quodata -dot- Com) writes:
> It seems natural to me that, as a subset of SGML, XML will become a
> documentation standard. Currently, though, XML-based publishing, rendering
> from databases, and the like, seems to start at $10,000 for the necessary
> tools, plus implementation and training. Costs seem to rise exponentially
> from there.
That's because XML-based tools are still very much in the big
corporate space and hence get subjected to both the
custom-implementation cost-inflation effect and the typical snake oil
associated with enterprise software products.
> You can use FrameMaker+SGML to create valid XML output, but I don't know how
> useful that really is.
By itself, minimally useful, but it gets you over the biggest
hump of being able to programmatically manipulate, store, serve, etc,
your documents. One of the weakest areas of XML per se (though not
necessarily the XML tool application space, I haven't done any hunting
for tools at all) is in importing data into XML. Once you have data
in XML, you have some immensely useful, flexible and powerful tools
for manipulating it.
> Also, consider that PostScript is one of, if not the most important
> language of publications; XML does not even pretend to replace
SVG bids fair to replace Postscript as the XML-based Postscript
for the modern era. This is probably symptomatic of how Ordinary
Mortals (i.e. people who have a life :-) are going to see XML in use -
once-removed, as a foundation on which a bunch of other standards and
products are based and for interoperability layers(*).
I suspect that 10 years from now you're going to see a lot of
entry-level folks who will be boggled by the idea of proprietary
standards, having grown up in a world where most major standards are
based on XML. Though I have no doubt that some companies will strive
mightily to keep that proprietary lock-in advantage.
(* There's already a _major_ trend in the web world for companies
to provide XML transaction interfaces to their products and services,
and several major players trying to stake out that space as their turf
(see "web services", essentially an XML/HTTP based API geared to a
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
Sponsored by Information Mapping, Inc., a professional services firm
specializing in Knowledge Management and e-content solutions. See http://www.infomap.com or 800-463-6627 for more about our solutions.
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.