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: Y2K compliance - how to inform users From:Lydia Wong <lydiaw -at- FPOINT -dot- COM> Date:Wed, 16 Sep 1998 15:12:47 -0400
Geoff makes some very valid points in his response to Nancy Burns' post
concerning Y2K compliance. Guy McDonald's list of sites was also very
helpful. (Thanks, Guy!)
I just wanted to chime in to clarify something about "compliance." The
bottom line on this is that there is no set standard for what "compliant"
means. Therefore, you need to be very clear about what your product does and
how it deals with date information so users have all the information they
need concerning year 2000 issues.
For an excellent introduction to Y2K issues and compliance, check out GTE's
document on compliance, which is posted at http://www.year2000.com/archive/gte-article/gte-compliance.html GTE has
summarized Y2K issues and problems well. They also provide an excellent
section that details their tests for compliance on different software
products (such as databases).
Just to respond to Nancy's question, our company was getting beseiged with
requests to provide Y2K information about our products. Our approach has
been to create an area on our web site devoted to Y2K information about our
products (all of our products, even ones we no longer sell or support--they
have been updated to provide "compliant" versions). We will be documenting
whatever features we provide to assist with date handling (and therefore,
Y2K issues), too, as we update our existing product line. So far, this
method is working well for us.
HTH,
Lydia
--------------------------
Lydia Wong
Technical Writer
FarPoint Technologies, Inc.
Morrisville, NC USA
www.fpoint.com