Difference between revisions of "DC I/O Abstract Template"
(→Abstract Template Structure)
|Line 48:||Line 48:|
Please download the DC I/O Abstract template in
Please download the DC I/O Abstract template in -[https://www.dropbox.com/s/snqtr2z7gsszuyx/DCIO_AbstractTemplate.docx?dl=0 HERE]
Latest revision as of 10:17, 10 October 2019
On this article, you can find the template guidance to complete the DC I/O abstract template. DC I/O extended abstract is no more than 1000 words and two pages, including references.
Abstract Template Structure
Use a concise and precise title for your abstract.
1ST GIVEN NAME SURNAME1, 2ST GIVEN NAME SURNAME2, 3ST GIVEN NAME SURNAME3, ETCETC. 1Dept. name of the organization (of Affiliation), City, Country. 2Dept. name of the organization (of Affiliation), City, Country. Etc. firstname.lastname@example.org or ORCID, 2 email@example.com or ORCID, 3 firstname.lastname@example.org or ORCID,
Please use a high-resolution image (300dpi to 600 dpi) and vector-graphics whenever possible. Images must not take more than 1/4 of the front page.
The body of your abstract begins here. It should be an explicit summary of your presentation that states the problem, the methods used, and the major results and conclusions. Do not include scientific symbols, acronyms, numbers, bullets or lists in the abstract. It should be single-spaced in 8.5-point Times New Roman. The first part of your abstract should state the problem you set out to solve or the issue you set out to explore and explain your rationale for pursuing the project. The problem or issue might be a research question, a gap in critical attention to a computational design method, a societal concern, etc. The purpose of your study is to solve this problem and/or add to the body of knowledge of Computational Design in the understanding of the issue. This section of the abstract should explain how you went about solving the problem or exploring the issue you identified. Your abstract should also describe the research methods; this section should include a concise description of the process by which you conducted your research. Next, your abstract should list the results or outcomes of the work you have done so far. If your project is not yet complete, you may still include preliminary results or your hypotheses about what those results will be. Finally, your abstract should close with a statement of the project’s implications and contributions to its field. It should convince readers that the project is interesting, valuable, and worth investigating further. In particular, it should convince the conference registrants to attend your presentation. The content of the abstract will be the basis for acceptance of the paper presented at the international research conference.
The conference publications are peer-reviewed and include the classic structure of a literature review, hypothesis, methodology, results, and conclusion but they give particular emphasis to the structured statement of the computational method used and how this method represents a progression in the field of research. Accepted papers have to demonstrate testable evidence in the progression of a working hypothesis of a computational method for design.
Be sure to adhere to the word limit for the abstract (300 to 500 words) and two pages maximum. These directions are written in the format required for the abstract of the paper for the Design Computation Conference. We recommend that you use the MS Word document text formatting and use it as the template for your abstract as it contains all necessary formats and styles.
For keywords, please also refer to this wiki and the Zotero Design Computation Library.
DC I/O uses Harvard (no abbreviations) within square brackets [Eason et al. 1955]. The sentence punctuation follows the bracket [Strunk and White 1999]. Refer simply to the reference, as in [Shalunts 2015] - do not use “Ref. [Shalunts 2015]” or “reference ”.
Number footnotes separately in superscripts. Place the actual footnote at the bottom of the column in which it was cited. Do not put footnotes in the abstract or reference list. Use letters for table footnotes. Unless there are six authors or more give all authors’ names; do not use “et al.”. Papers that have not been published, even if they have been submitted for publication, should be cited as “unpublished” [K. Elissa]. Papers that have been accepted for publication should be cited as “in press” [Nicole]. Capitalize only the first word in a paper title, except for proper nouns and element symbols.
For papers published in translation journals, please give the English citation first, followed by the original foreign-language citation [Yorozu 1982].
For Creative Commons articles shared in the Design Computation Wiki (or DCWIKI) [Maciel 2017], always check the initiator of the page (under ‘View history’) and add the correct link to the page. In instances where the originator of the article is not identifiable, please refer to the wiki itself [DCWIKI 2019].
Please note that all articles in the DCWIKI are shared under the ‘Attribution-NonCommercial-ShareAlike 4.0 International’ licence.
Repositories can be referenced using the author's name [Maciel 2019] or the repository’s name [Project X 2019].
For all DC I/O conference material, please search 'DCIO' in this wiki. The DCIO category tags all conference information content in this platform. For general information to create articles in the DCWIKI please refer to the Manual of Style.
Please download the DC I/O Abstract template in MS-Word HERE We do accept LaTeX submission but we are currently developing the LaTeX template for distribution. If you are using LaTeX, this has to mirror the PDF model and the MS-Word template.