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: Giving up on XML From:"Gene Kim-Eng" <techwr -at- genek -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 21 Mar 2007 07:52:04 -0700
I don't think the situation is quite that dire for XML or
some other single-source or structured documentation
scheme. What's required is for some company to devise
a killer tool that enables a master user with a password to
create templates and structures that generate all of the
necessary under-the-hood configuration stuff relative
ease (that is, more than there is now) and lock the interface
against rogue modifications, for tech writers or tech pubs
managers who want to be able to lock down their doc
structures to decide to adopt this tool and for company
management to decide that the price of this tool is not
prohibitive. That's a lot, but it's really no more than was
required for FrameMaker to become ubiquitous in the
industry. All the "cooperation" that is required once
the killer app is developed takes place within companies
and doesn't require competitors to work together. The
little software startup doesn't have to give a hoot whether
its doc schemes are standardized or compatible with the
mega chip or automobile company down the road.
> And from /., on the topic of "Why XML may fail," we
> have the following insight:
> Seems to apply both to technical writers not using
> stylesheets, the problems standardizing XML
> implementations, the conflict between DocBook and
> Frame and DITA and custom solutions, and much else.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-