A fast abstract is a short, lightly reviewed technical article that is usually presented with a short talk at a scientific conference. The length of the document is usually limited to 2 pages (including all text, figures, references and appendices), although some conferences may allow slightly higher limits . If the conference doesn't provide a specific document style, the standard double-column IEEE format is a common recommendation . The concept of a "fast abstract" was created at the 28th Fault-Tolerant Computing Symposium, 1998, by Ram Chillarege, who was the program co-chair of the conference. They are meant to promote communication and discussion of subjects that haven't yet been established or completed as research projects, and to provide a venue for reporting barely tested ideas, early experiments, or opinions. While informal discussions, stand-up talks, and round tables provide an avenue for such sharing, they lack the written record that is essential for academic progress. Fast abstracts aim to fill this gap. Since their inception, fast abstract sessions have been gradually adopted by several conferences, in some cases even being among the most attended sessions. Due to their purpose and short length, fast abstracts don't require a full treatment of results as expected of a full paper published at a conference or journal. Even less formal publications such as working papers and technical reports are usually based on established research projects, and on the other hand these rarely are peer reviewed before publication, and there is no formal publishing procedures for such reports. Fast abstracts differ in these two aspects, and being (as the name indicates) fast to write and fast to review, they create a mechanism to promote a rich and timely exchange of experiences, and receive early feedback from the community.
A fast abstract is a short, lightly reviewed technical article that is usually presented with a short talk at a scientific conference. The length of the document is usually limited to 2 pages (including all text, figures, references and appendices), although some conferences may allow slightly longer articles . If the conference does not specify a document style, the standard double-column IEEE format is a common practice . The concept of a "fast abstract" was created at the 28th Fault-Tolerant Computing Symposium, 1998, by Ram Chillarege, who was the program co-chair of the conference. They are meant to promote communication and discussion of subjects that have yet to be established or completed as research projects, and to provide a venue for reporting barely tested ideas, early experiments, or opinions. While informal discussions, stand-up talks, and round tables provide an avenue for such sharing, they lack the written record that is essential for academic progress. Fast abstracts aim to fill this gap. Since their inception, fast abstract sessions have been gradually adopted by several conferences, in some cases even being among the most attended sessions. Due to their purpose and short length, fast abstracts do not require a full treatment of results as expected of a full paper published at a conference or journal. Even less formal publications such as working papers and technical reports are usually based on established research projects, and on the other hand these rarely are peer reviewed before publication, and there is no formal publishing procedures for such reports. Fast abstracts differ in these two aspects, and being (as the name indicates) fast to write and fast to review, they create a mechanism to promote a rich and timely exchange of experiences, and receive early feedback from the community.
R
higher limits
longer articles
R
doesn't provide a specific
does not specify a
R
recommendation
practice
R
haven't yet been
have yet to be
R
don't
do not