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: To XML or to UI From:"technicoid" <technicoid -at- cableone -dot- net> To:<techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 18 Feb 2004 22:24:26 -0700
I'm inclined to go with Mark Baker's suggestion. If this is a class on
XML basics, you can learn that on your own. If it's something on a more
advanced XML topic with some hands-on practice (like writing XSL-FOs),
then it might be worthwhile. I like all that lovely technology that
works with XML, but XML in itself is very simple.
If you want to expand the position beyond documenting the interface
and/or what's behind it to helping developers make better UI design
decisions (and helping to develop the functional specs so you can then
use them to develop user docs), go with UI design. XML is just another a
tool, and JP has been around the block long enough to figure out how
such technologies work.
