General Actions:
Log-in
Wiki:
CreativeIT
▼
:
Document Index
»
Space:
ASU Workshop
▼
:
Document Index
»
Page:
test conversion
Page Actions:
Export
▼
:
Export as PDF
Export as RTF
Export as HTML
More actions
▼
:
Print preview
View Source
Welcome to the CreativeIT Wiki!
»
Workshops
»
Success Factors Workshop
»
Proceedings of the NSF CreativeIT workshop at Arizona State University
»
test conversion
Wiki source code of
test conversion
Last modified by
Hal Eden
on 2009/04/17 09:32
Content
·
Comments
(0)
·
Attachments
(0)
·
History
·
Information
Hide line numbers
1: {{html}} 2: <html> 3: 4: <body class="print"> 5: <h2>test conversion</h2> 6: <div id ="container"> <div id = "content"> 7: <div id="title">Word Template for NSF CreativeIT Workshop</div> 8: <p></p> 9: 10: <div id="author">1st Author</div> 11: 12: <div id="affiliation">1st author's affiliation 13: 1st line of address 14: 2nd line of address 15: Telephone number, incl. country code</div> 16: 17: <div id="emailaddress">1st author's email address</div> 18: 19: <div id="author"> 20: 2nd Author</div> 21: 22: <div id="affiliation">2nd author's affiliation 23: 1st line of address 24: 2nd line of address 25: Telephone number, incl. country code</div> 26: 27: <div id="emailaddress">2nd E-mail</div> 28: 29: <div id="author"> 30: 3rd Author</div> 31: 32: <div id="affiliation">3rd author's affiliation 33: 1st line of address 34: 2nd line of address 35: Telephone number, incl. country code</div> 36: 37: <div id="emailaddress">3rd E-mail</div> 38: 39: 40: <center><p></p> 41: </center><b><p>ABSTRACT</p></b> 42: In this paper, we describe the formatting guidelines for the NSF CreativeIT workshop "Success factors in fostering creativity in IT research and education" 43: <b><p>Keywords</p></b> 44: <p>Keywords are your own designated keywords.</p> 45: 46: <h1>INTRODUCTION</h1> 47: <p>The proceedings are the records of the conference. We ask that authors follow some simple guidelines. In essence, we ask you to make your paper look exactly like this document. </p> 48: 49: <h1>PAGE SIZE</h1> 50: <p>All material on each page should fit within a rectangle of 18 x 23.5 cm (7" x 9.25"), centered on the page, beginning 2.54 cm (1") from the top of the page and ending with 2.54 cm (1") from the bottom. The right and left margins should be 1.9 cm (.75").</p> 51: <p>The text should be in two 8.45 cm (3.33") columns with a .83 cm (.33") gutter.</p> 52: 53: <h1>TYPESET TEXT</h1> 54: 55: <h2>Normal or Body Text</h2> 56: 57: <p>Please use a 9-point Times Roman font, or other Roman font with serifs, as close as possible in appearance to Times Roman in which these guidelines have been set. The goal is to have a 9-point text, as you see here. Please use sans-serif or non-proportional fonts only for special purposes, such as distinguishing source code text. If Times Roman is not available, try the font named Computer Modern Roman. On a Macintosh, use the font named Times. Right margins should be justified, not ragged. </p> 58: 59: <h2>Title and Authors</h2> 60: <p>The title (Helvetica 18-point bold), authors' names (Helvetica 12-point) and affiliations (Helvetica 10-point) run across the full width of the page ? one column wide. We also recommend phone number (Helvetica 10-point) and e-mail address (Helvetica 12-point). See the top of this page for three addresses. If only one address is needed, center all address text. For two addresses, use two centered tabs, and so on. For more than three authors, you may have to improvise.<sup> </sup></p> 61: 62: <h2>First Page Copyright Notice</h2> 63: <p>Please leave 3.81 cm (1.5") of blank text box at the bottom of the left column of the first page for the copyright notice.</p> 64: 65: <h2>Subsequent Pages</h2> 66: <p>For pages other than the first page, start at the top of the page, and continue in double-column format. The two columns on the last page should be as close to equal length as possible.</p> 67: <p></p> 68: 69: <caption>Table 1. Table captions should be placed above the table</caption> 70: <table><th><center><b>Graphics</b></center> 71: </th> <th><center><b>Top</b></center> 72: </th> <th><center><b>In-between</b></center> 73: </th> <th><center><b>Bottom</b></center> 74: </th> 75: <tr><td><center>Tables</center></td> <td><center>End</center></td> <td><center>Last</center></td> <td><center>First</center></td> 76: </tr> 77: <tr><td><center>Figures</center></td> <td><center>Good</center></td> <td><center>Similar</center></td> <td><center>Very well</center></td> 78: </tr> 79: </table> 80: <p></p> 81: 82: <h2>References and Citations</h2> 83: <p>Footnotes should be Times New Roman 9-point, and justified to the full width of the column.</p> 84: <p>Use the "ACM Reference format" for references ? that is, a numbered list at the end of the article, ordered alphabetically and formatted accordingly. See examples of some typical reference types, in the new "ACM Reference format", at the end of this document. Within this template, use the style named <i>references</i> for the text. Acceptable abbreviations, for journal names, can be found here: <a href="http://library.caltech.edu/reference/abbreviations/">http://library.caltech.edu/reference/abbreviations/</a> 85: </p> 86: <p>The references are also in 9 pt., but that section (see Section 7) is ragged right. References should be published materials accessible to the public. Internal technical reports may be cited only if they are easily accessible (i.e. you can give the address to obtain the report within your citation) and may be obtained by any reader. Proprietary information may not be cited. Private communications should be acknowledged, not referenced (e.g., "[Robertson, personal communication]").</p> 87: 88: <h2>Page Numbering, Headers and Footers</h2> 89: <p>Do not include headers, footers or page numbers in your submission. These will be added when the publications are assembled.</p> 90: 91: <h1>FIGURES/CAPTIONS</h1> 92: <p>Place Tables/Figures/Images in text as close to the reference as possible (see Figure 1). It may extend across both columns to a maximum width of 17.78 cm (7").</p> 93: <p></p> 94: <p>Captions should be Times New Roman 9-point bold. They should be numbered (e.g., "Table 1" or "Figure 2"), please note that the word for Table and Figure are spelled out. Figure?s captions should be centered beneath the image or picture, and Table captions should be centered above the table body.</p> 95: 96: <h1>SECTIONS</h1> 97: <p>The heading of a section should be in Times New Roman 12-point bold in all-capitals flush left with an additional 6-points of white space above the section head. Sections and subsequent sub- sections should be numbered and flush left. For a section head and a subsection head together (such as Section 3 and subsection 3.1), use no additional space above the subsection head.</p> 98: 99: <h2>Subsections</h2> 100: <p>The heading of subsections should be in Times New Roman 12-point bold with only the initial letters capitalized. (Note: For subsections and subsubsections, a word like <i>the</i> or <i>a</i> is not capitalized unless it is the first word of the header.)</p> 101: 102: <h3>Subsubsections</h3> 103: <p>The heading for subsubsections should be in Times New Roman 11-point italic with initial letters capitalized and 6-points of white space above the subsubsection head.</p> 104: 105: <h4>Subsubsections</h4> 106: <p>The heading for subsubsections should be in Times New Roman 11-point italic with initial letters capitalized.</p> 107: 108: <h1>ACKNOWLEDGMENTS</h1> 109: <p>Our thanks to the NSF for sponsoring this workshop.</p> 110: 111: <h1>REFERENCES</h1> 112: 113: <p>Bowman, M., Debray, S. K., and Peterson, L. L. 1993. Reasoning about naming systems. ACM Trans. Program. Lang. Syst. 15, 5 (Nov. 1993), 795-825. DOI= <font color="#0000FF"><u>http://doi.acm.org/10.1145/161468.161471</u></font>.</p> 114: 115: <p>Ding, W. and Marchionini, G. 1997 A Study on Video Browsing Strategies. Technical Report. University of Maryland at College Park. </p> 116: 117: <p>Fröhlich, B. and Plate, J. 2000. The cubic mouse: a new device for three-dimensional input. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (The Hague, The Netherlands, April 01 - 06, 2000). CHI '00. ACM Press, New York, NY, 526-531. DOI= <a href="http://doi.acm.org/10.1145/332040.332491">http://doi.acm.org/10.1145/332040.332491</a></p> 118: 119: <p>Tavel, P. 2007 Modeling and Simulation Design. AK Peters Ltd.</p> 120: 121: <p>Sannella, M. J. 1994 Constraint Satisfaction and Debugging for Interactive User Interfaces. Doctoral Thesis. UMI Order Number: UMI Order No. GAX95-09398., University of Washington.</p> 122: 123: <p>Forman, G. 2003. An extensive empirical study of feature selection metrics for text classification. J. Mach. Learn. Res. 3 (Mar. 2003), 1289-1305.</p> 124: 125: <p>Brown, L. D., Hua, H., and Gao, C. 2003. A widget framework for augmented interaction in SCAPE. In Proceedings of the 16th Annual ACM Symposium on User interface Software and Technology (Vancouver, Canada, November 02 - 05, 2003). UIST '03. ACM Press, New York, NY, 1-10. DOI= <font color="#0000FF"><u>http://doi.acm.org/10.1145/964696.964697</u></font></p> 126: 127: <p>Y.T. Yu, M.F. Lau, "A comparison of MC/DC, MUMCUT and several other coverage criteria for logical decisions", Journal of Systems and Software, 2005, in press.</p> 128: 129: 130: 131: <p> 132: </p> 133: 134: <div id="title">Columns on Last Page Should Be Made As Close As Possible to Equal Length</div> 135: </div></div><br> 136: <br> 137: 138: </body> 139: </html>{{/html}}
Quick Links
Home
Index
What's New
Blog
Calendar
Photo Albums
Sandbox
Tags
Bulletin Board
My Recent Modifications
PamelaJennings
|
rwakkary
|
HaledenSands
|
ByronLahey