Chapter 1
Appendix: a few more points being considered

1.1  In the Objects

In this list, when an object is related to a file, the name of this file can be put within brackets at the end of each line, see e.g. J/MNRAS/301/1031, or J/A+A/406/987.

1.2  In the File Summary

When a file was split into smaller pieces:

1.3  In the Byte-by-byte Description

Comments in data file
Data files may include lines of comments:

Labels new conventions
(extensions of the conventions in Section 3.3 of the conventions)

"section_title" section reference
can refer to a section of the ReadMe file (example for catalog J/A+AS/104/315)

*File* labels
indicates a column which is a file (FITSfile indicates a file in FITS format). The text of the explanation must include either the word directory (i.e. files are in the catalog directory), or the word subdirectory followed by the name of the subdirectory where the file is located.

see file "described_file"
indicates that this column refers to another file. The link to the other file is generated.

(SIMBAD name)
in the explanation of a column means that the contents of this column can be injected into the SIMBAD data-base.

name in database
In the case of an external database, this would tell what's the name of this column in the foreign data-base which might not follow the standard conventions.

specifies a date in DMF format (seconds elapsed since 1980)

1.4  In the Notes

Global Notes
are an extension of the Lenghty Notes convention (of the second alternative). This extention is to allow several tables to refer to a unique text placed after the "Byte-by-byte" descriptions. These are simply refered as (Gn) as the last word in the explanations of a column, and the corresponding lengthy note must be introduced by a left-flushed text
Note (Gn):

file "filename" explanation
indicates that further details can be found in the file named filename. This filename must end with the .txt suffix.

©UDS/CNRS  Contact: Question@simbad