E1AR0002@SMUVM1.BITNET (10/09/86)
[Lawrence Leff at SMU, who provides all those lengthy bibliographies and
article summaries, has sent the following correction for the Subject line
I added to one of the bibliographies. -- KIL]
ai.bib35 was mistitled as references on computer vision/robotics.
This reference list contained articles on such subjects as neural
networks, urban planning, logic programming, and theorem proving as
well as vision/robotics.
In order to prevent this problem in the future, I will entitling the
materials as ai.bibnnxx
where nn is a consecutive number and
xx is C for citations without descriptions
TR for technical reports
AB for citations for citations with descriptions
(annotated bibliographies)
Thus ai.bib40C means the 40th AI list in bibliography format
and the C indicates that we have a bunch of bib format references
without significant commentary.
The nn is unique over all types of bibliographies. Thus, if there
were an ai.bib40C, then there will NOT be an ai.bib40TR or ai.bib40AB.
These designations are actually the file names for the list on my hard disk.
The shell script that wraps up the item for mailing will automatically put
the file name in the subject field. If one of your readers uses this to
designate a file in mail to me, I can thus trivially match their query
against a specific file.
Note that I no longer will be separating out references by subject
matter. The keyword system is much more effective for allowing people
interested in specific subfields of ai to see the articles they find relevant.
Sadly the bib system program "listrefs" is having problems with citations
that contain long abstracts or commentary information. Thus TR and AB
type references will probably cause this program to spec check. I spent
a whole day trying to isolate the problem but have been unsuccessful.
One other self-described bib expert has the same problem. All references
are indexable by "invert".
TR and AB type references will not use bib definition files and thus
are usable with the refer package from AT&T. If I were not to use bib
definition files with C type reference lists, the number of bytes transmitted
for their mailing would triple.