Book Chapter Editing Guidelines
This document presents a set of recommendations for writing the book chapters to help promoting the quality of submissions, and unifies the general structure of the book chapters.
Š Paper length is typically 20 pages. Two extra pages in case needed will be allowed.
Š The writing quality of the book chapter is very important. If the paper is not well written, reviewers (and readers) may not be able to understand the merits of the paper and may lead to rejection. It is highly recommended to proofread the chapter extensively before submission, and make sure about the readability of the paper.
Š Every book chapter must contain an abstract that summarizes the technical contributions. It must be between 180 and 200 words. The abstract must clearly and briefly present the main results.
Š At the end of the introduction, it is highly recommended to add a short paragraph entitled “Contributions of the Book Chapter” in which you present the technical contributions of the chapter, and compare with the state of the art. This is very helpful for reviewers to identify the added value of your chapter. You may use bullets to enumerate the contributions of the chapter.
Š Even in case of a survey paper, the authors should clarify the contributions of their survey as compared to existing surveys.
Š Each book chapter must include a background section in which the authors present the technical materials needed as background for readers who are not necessarily expert on the topic of the chapter.
For example, if the chapter deals with a particular concept or technology in robotics or sensor networks, (e.g. UAVs, network/communication protocol, etc.), or is based on a mathematical model or technique (e.g. Markov process, Bayesian Theory, Filtering, Signal processing technique, etc.), then the background section should give enough introductory materials for readers to understand the remaining part of the chapter. The background section length should be between 1-2 pages maximum. It is recommended to avoid being too much verbose, but just presenting the essentials of needed background.
Š In addition to the background section, it is important to have a section on related works where the authors discuss relevant previous works. It is important that authors clarify the contributions of their work in comparison with previous works. This will help convincing the reviewers about the novelty of the proposed work. A simplistic description of previous works without technical depth is not recommended.
Š If the chapter proposes an algorithm, a mathematical model, or any technical contribution, it is crucial to clearly present the system model and assumptions, accurately describe notations, and discuss the assumption and limitations of your model. This will help the reviewer understanding and evaluating better your technical contribution.
Š If you present a simulation study or experimental work, make sure to provide all details about experimental set-up, environments, and settings. Adding figures and technical details about the real deployment, simulation environment is very important.
Š It is recommended to summarize the main outcomes of the chapter at the end in a paragraph called lessons learned, if relevant.
Š The conclusion should summarize the contribution of the paper, discusses the possible limitation of the presented work, and present insight on future work to improve/extend the proposed work.
Š References must be well formatted and contain all information about the publication. In addition, references must be up-to-date, recent, and refer to publications of high quality.