My department has used XMetal for several months now, and if all you need is
a word-processor-like interface for editing XML documents, XMetal is
probably a good choice. If you're looking for true content management,
however, XMetal may not be the best candidate.
For example, our goal is to build an XML-based content management system
where all source resides in a database rather than separate files.
Documentation for different products can then be generated by querying the
database to extract the relevant information for each product. This approach
allows maximum reuse of content, and makes it possible to more effectively
track changes and revisions, etc. Given this, we need an authoring system
that integrates with a database. We've looked at a number of tools; so far
Epic from Arbortext appears to be the leading contender.
From: Lindsey Thomas Martin [mailto:[log in to unmask]]
Sent: Wednesday, January 10, 2001 11:13 AM
To: [log in to unmask]
Subject: Re: xml-based office suite?
At 10:08 1/10/01 -0600, Jerry Muelver wrote:
>I've got XMetal, just got upgraded to version 2, and I'm getting up to
>on it. With the configurable interface, it may be the way to go. I just
>don't want to have to retrain the staff, or train the occasional
>contributors at all, if I don't have to.
I have just begun to learn XMetaL but was under the impression
that it could be customised so that staff and other contributors
would be exposed only to an interface very like a normal word-processor.
Is this not the case or are there are reasons why it would not
be a suitable tool in Mr Muelver's situation?