Difference between revisions of "DC I/O Paper Template"
Abel Maciel (talk | contribs) |
Abel Maciel (talk | contribs) (→INTRODUCTION (HEADING 1)) |
||
Line 7: | Line 7: | ||
=Keywords= | =Keywords= | ||
Component, Formatting, Style, Styling, Insert (Key Words) | Component, Formatting, Style, Styling, Insert (Key Words) | ||
− | = | + | =Introduction (HEADING 1)= |
This template, modified in MS Word 2007 and saved as a “Word 97-2003 Document” for the PC, provides authors with most of the formatting specifications needed for preparing electronic versions of their papers. All standard paper components have been specified for three reasons: (1) ease of use when formatting individual papers, (2) automatic compliance to electronic requirements that facilitate the concurrent or later production of electronic products, and (3) conformity of style throughout a conference proceedings. Margins, column widths, line spacing, and type styles are built-in; examples of the type styles are provided throughout this document and are identified in italic type, within parentheses, following the example. Some components, such as multi-leveled equations, graphics, and tables are not prescribed, although the various table text styles are provided. The formatter will need to create these components, incorporating the applicable criteria that follow. | This template, modified in MS Word 2007 and saved as a “Word 97-2003 Document” for the PC, provides authors with most of the formatting specifications needed for preparing electronic versions of their papers. All standard paper components have been specified for three reasons: (1) ease of use when formatting individual papers, (2) automatic compliance to electronic requirements that facilitate the concurrent or later production of electronic products, and (3) conformity of style throughout a conference proceedings. Margins, column widths, line spacing, and type styles are built-in; examples of the type styles are provided throughout this document and are identified in italic type, within parentheses, following the example. Some components, such as multi-leveled equations, graphics, and tables are not prescribed, although the various table text styles are provided. The formatter will need to create these components, incorporating the applicable criteria that follow. | ||
+ | |||
=Motivation & Background= | =Motivation & Background= | ||
The theoretical framework, reasoning, Intellectual background. Includes detailed '''Characteristics''' and '''Theory'''. | The theoretical framework, reasoning, Intellectual background. Includes detailed '''Characteristics''' and '''Theory'''. |
Revision as of 22:57, 6 August 2019
Pages in designcomputation.org are as short as possible and focus only on computational design taxonomies, cultures and ontologies. A page might be a simple definition that gradually evolves to have Motivation & Background, Structures and Applications with many detailed subtopics. Always categorize your pages.
Contents
Abstract
This electronic document is a “live” template and already defines the components of your paper [title, text, heads, etc.] in its style sheet. *CRITICAL: Do Not Use Symbols, Special Characters, Footnotes, or Math in Paper Title or Abstract. (Abstract)
Keywords
Component, Formatting, Style, Styling, Insert (Key Words)
Introduction (HEADING 1)
This template, modified in MS Word 2007 and saved as a “Word 97-2003 Document” for the PC, provides authors with most of the formatting specifications needed for preparing electronic versions of their papers. All standard paper components have been specified for three reasons: (1) ease of use when formatting individual papers, (2) automatic compliance to electronic requirements that facilitate the concurrent or later production of electronic products, and (3) conformity of style throughout a conference proceedings. Margins, column widths, line spacing, and type styles are built-in; examples of the type styles are provided throughout this document and are identified in italic type, within parentheses, following the example. Some components, such as multi-leveled equations, graphics, and tables are not prescribed, although the various table text styles are provided. The formatter will need to create these components, incorporating the applicable criteria that follow.
Motivation & Background
The theoretical framework, reasoning, Intellectual background. Includes detailed Characteristics and Theory.
Structures
The mechanism depiction of the topic clarifying.
Principle
Generality of the method or theory.
Precision
Generality of the method or theory.
Generality
Generality of the method or theory.
Application
Description of cases and application with steps-by-step explanations. This includes Examples with scrips, computer code or mathematical model illustrating the application in the many design development platform available (listed in alphabetical order). For each platform (Dynamo, Grasshopper, Processing, etc.), one might find internal and external links.
Examples
Platform | Application 1A Links |
---|---|
C# | App A; App B; |
Catia | App A App B |
Dynamo | App A App B |
Grasshopper | App A App B |
Java | App A App B |
JavaScript | App A App B |
OpenFrameworks | App A App B |
Processing | App A App B |
Python | App A App B |
Rhino Script | App A App B |
Future Directions
Avoid the term Discussion as this will be addressed on Talk.