Re: Re: STC Transformation -- info

Subject: Re: Re: STC Transformation -- info
From: eric -dot- dunn -at- ca -dot- transport -dot- bombardier -dot- com
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Tue, 13 Jul 2004 14:41:35 -0400


bounce-techwr-l-106467 -at- lists -dot- raycomm -dot- com wrote on 07/13/2004 01:55:21 PM:
> Ah, there's the conundrum. Focus on the common denominator--
> the writing, editing, information structuring, process
> management--and everyone dismisses the effort as not
> technical enough. Focus on the technical--software languages,
> communication protocols--and everyone says you're too
> exclusive and not meeting the needs of the writers in other
> industries.

> Da*ned if you do...

> -Sue Gallagher

Depends entirely on the approach. If 'technical' topics were presented
that were not applicable to a wide range of industries the STC would be
alienating participants from other industries. But, if technical topics
were instead presented to illustrate cross-specialty application it would
be useful regardless of the technology used for the demonstration (not
sure that would be easy).

Perhaps an STC conference could be a collection of presentations that are
provided by the various specialised fields. Perhaps a common theme could
be determined for various activities in the past year and have each
industry organisation present their yearly review concentrating on the
central theme. Then it would be a sort of annual 'heads-up' so that
participants could be aware of developing treads and mature practices in
other industries so that they may investigate adopting them for their own
areas of expertise.

For example, XML presentations should be given by representatives from
www.xmlconference.org or www.trixml.org. SIGs covering similar ground to
specific industries or groups should be abolished and replaced with
cooperation between those industries or groups and the STC. Instead of
forming new SIGs, the STC should seek out concerned industries or groups
and lobby them to join with the STC and support communication focused
groups within their industries or groups.

The STC could even get round to certifying technical communicators in a
similar way. Just as ANSI approves/certifies groups to develop standards,
the STC could certify/approve/recognise groups to set qualification
requirements.

Eric L. Dunn
Senior Technical Writer

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

ROBOHELP X5: Featuring Word 2003 support, Content Management, Multi-Author
support, PDF and XML support and much more!
TRY IT TODAY at http://www.macromedia.com/go/techwrl

WEBWORKS FINALDRAFT: New! Document review system for Word and FrameMaker
authors. Automatic browser-based drafts with unlimited reviewers. Full
online discussions -- no Web server needed! http://www.webworks.com/techwr-l

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -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.



References:
Re: Re: STC Transformation -- info: From: Susan W . Gallagher

Previous by Author: Re: STC Transformation -- info
Next by Author: RE: STC Transformation -- info
Previous by Thread: Re: Re: STC Transformation -- info
Next by Thread: RE: STC Transformation -- info


What this post helpful? Share it with friends and colleagues:


Sponsored Ads