Perhaps another question to ask is why someone doesn't explain, in the
rules for news.answers, why one is required to do what is there.
It is my understanding that the guidelines *do*, in fact, explain
themselves. For example (taken from "*.answers submission
guidelines"):
> A. Why the guidelines?
>
> There are three main reasons for the guidelines:
>
> 1. Appropriateness
>
> Only periodic informational postings that are intended to be read
> by people belong in news.answers. The guidelines are meant to
> prevent other types of postings, including discussion of periodic
> informational postings, from appearing in the group.
>
> 2. Usefulness to people
>
> The newsgroup should be as useful as possible to the people who
> read it. Requirements such as effective "Subject:" and
> "Summary:" lines (see below) further this goal.
>
> 3. Automatic archiving
>
> One of the main points of news.answers is that it can be archived
> automatically in order to build up a database of periodic
> informational postings. Requirements such as the "Archive-name:"
> line further that goal.
>
>...
>
> The purpose of the archive name is two-fold. First of all, it
> specifies where the FAQ should be stored in archives of the
> news.answers newsgroup. Second, it should give people, even
> people who do not read the home newsgroup of the FAQ, a pretty
> good idea of what's in it. Therefore, abbreviations which will
> only be recognized by people already familiar with the topic
> covered by the FAQ should be avoided if possible.
If you think that there are specific items in the guidelines whose
purpose needs to be explained explained further, please send your
comments to news-answers-request@MIT.Edu, and we'll try to address
your concerns. Note, however, that we have to temper any requests to
add material to the guidelines against the desire to keep them as
brief as possible.
Jonathan Kamens | OpenVision Technologies, Inc. | jik@security.ov.com
[
Usenet Hypertext FAQ Archive |
Search Mail Archive |
Authors |
Usenet
]
[
1993 |
1994 |
1995 |
1996 |
1997
]
© Copyright The Landfield Group, 1997
All rights reserved