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.
Less Bias in Tech Topics? [was Re: DITA - how to start?]
Subject:Less Bias in Tech Topics? [was Re: DITA - how to start?] From:Yves JEAUROND <jingting -at- rogers -dot- com> To:Fred Ridder <docudoc -at- hotmail -dot- com> Date:Fri, 31 Aug 2007 13:28:48 -0400 (EDT)
Fred ridder:
"Topics that relate to technical and technological issues
are much less subject to bias or hidden agendas."
Huh? With respect, are you referring to drug trials?
Pushing buggy software out the door? Commercial fishing
equipment that destroys ocean habitats? Weaponry?
The Space Shuttle? Producing HW that will quickly be
obsolete and non-recyclable? Global-warming?
Evolutionary theory? The best authoring SW?
TWs can also benefit for Thomas Kuhn's take on things in
_The Structure of Scientific Revolutions_ (1962)
which is still a standard text in many universities for
courses in the philosophy of science, sociology of science
and history of science. It is mighty useful towards understanding
where TWs come in, in the whole process of technology.
But don't look up Kuhn on Wikipedia, or take my word for it :-)
Regards,
YJ
Fred Ridder <docudoc -at- hotmail -dot- com> a écrit :
While many people have issues with the accuracy and reliability
(e.g. freedom from bias) of Wikipedia articles, these issues relate
more to subject areas that involve interpretation such as history,
politics, philosophy, sociology, psychology, and world view.
Topics that relate to technical and technological issues are much
less subject to bias or hidden agendas. This is particularly true
for topics on current technology because the people who are
actually responsible for the technology (in this case the original
architects of DUTA at IBM and the members of the OASIS DITA
technical committee) tend to keep an eye on the articles that
are relevant to their technology and keep things from getting too
far out of line with reality. And in the case of such a niche
topic as DITA, it is very likely that everybody who contributed
to the DITA article is an actual DITA user (who else would be
motivated to write or revise an article such a specialized subject),
while I'm quite sure that no more than a few dozen Techwr-l
members have actually used DITA for anything more than an
experiment or pilot project.
Also, it seems to me that the list of external references in
a Wikipedia article is inherently more reliable than the article
itself as long as you know enough to pay some attention to
who is behind the referenced information. The list may contain
some questionable or marginally useful secondary references,
but when you're looking for "foundational resources" (such as
the defining specifications for DITA) I think Wikipedia is both
useful and highly reliable.
>From: "Rob Hudson"
>To: techwr-l -at- lists -dot- techwr-l -dot- com
>Subject: Re: DITA - how to start?
>Date: Thu, 30 Aug 2007 22:28:00 -0500
>
>Fred said:
>
> >> I have to wonder whether posting to Techwr-l was really
> >> easier and more productinve than a quick check of Wikipedia
> >> and Google...
>
>I agree with you, Fred, that I could have done Wikipedia and Google.
>However, I figured the expertise here would give me a nice foundation
>from which to further research Dita. I could get a notion of where to
>begin from a good sampling of practitioners and then whittle down the
>resources from there.
>
>Regarding Wikipedia: Can I trust it more than I can trust a list of
>experts? Is it more valid for technical matters than for other types
>of issues?
>
>Thanks, all, for the primer.
>
>Rob
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as jingting -at- rogers -dot- com -dot-
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-