This document provides a template for formatting academic papers. It includes guidelines for formatting titles, authors, affiliations, sections and headings, equations, references, and other components of a paper. The template specifies font styles and sizes, margins, pagination, and other layout guidelines to ensure a uniform appearance across papers in conference proceedings. It also identifies common mistakes to avoid, such as issues with units, abbreviations, punctuation, grammar, and terminology. Authors are instructed to use the template to format their paper content while maintaining the specified styles and layout.
Fog computing or fog networking, also known as fogging, is an architecture that uses edge devices to carry out a substantial amount of computation, storage, and communication locally and routed over the internet backbone.
With the Technological advancements, it is well understood that more and more objects are getting connected together. These objects are becoming more smarter to handle many operations through its inter connectivity. Rather than requiring devices to go through the network backbone infrastructure, fog computing permits devices to connect directly with their destination with ease and allows them to handle their connections and tasks. As a result, fog computing improves quality of service, reduces latency, and gives a more satisfactory user experience.
Fog computing or fog networking, also known as fogging, is an architecture that uses edge devices to carry out a substantial amount of computation, storage, and communication locally and routed over the internet backbone.
With the Technological advancements, it is well understood that more and more objects are getting connected together. These objects are becoming more smarter to handle many operations through its inter connectivity. Rather than requiring devices to go through the network backbone infrastructure, fog computing permits devices to connect directly with their destination with ease and allows them to handle their connections and tasks. As a result, fog computing improves quality of service, reduces latency, and gives a more satisfactory user experience.
Paper Title (use style paper title)Note Sub-titles are not.docxaman341480
Paper Title* (use style: paper title)
*Note: Sub-titles are not captured in Xplore and should not be used
line 1: 1st Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 4th Given Name Surname
line 2: dept. name of organization(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 2nd Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 5th Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 3rd Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
line 1: 6th Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address
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)
I. 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.
II. Ease of Use
A. Selecting a Template (Heading 2)
First, confirm that you have the correct template for your paper size. This template has been tailored for output on the A4 paper size. If you are using US letter-sized paper, please close this file and download the Microsoft Word, Letter file.
B. Maintaining the Integrity of the Specifications
The template is used to format your paper and style the text. All margins, column widths, line spaces, and text fonts are prescribed; please do n.
a. Collect at least six published papers in one of the new tre.docxdaniahendric
a. Collect at least six published papers in one of the new trending technologies in
networking and data communications.
b. Read and prepare a report to summarize and discuss the papers you collected.
c. The report should include the following parts.
• Introduction.
• Detailed discussion of what you read (add your point of view if any on
the topic you are discussing).
• Summery.
d. Your report should be written in the following format.
• Four papers in minimum.
• Font type: Times New Romans.
• Font size: 12 pt.
• Line spacing 1.5
Paper Title* (use style: paper title)
*Note: Sub-titles are not captured in Xplore and should not be used
line 1: 1st Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address or ORCID
line 1: 4th Given Name Surname
line 2: dept. name of organization(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address or ORCID
line 1: 2nd Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address or ORCID
line 1: 5th Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address or ORCID
line 1: 3rd Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address or ORCID
line 1: 6th Given Name Surname
line 2: dept. name of organization
(of Affiliation)
line 3: name of organization
(of Affiliation)
line 4: City, Country
line 5: email address or ORCID
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)
I. 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 style ...
Week 1 Assignment InstructionsGOAL Create the initial element o.docxjessiehampson
Week 1 Assignment Instructions
GOAL: Create the initial element of your Business Model Generation—your business Model Canvas.
Introduction: Using the Osterwalder and Pigneur Business Model Canvas as a resource (coupled with the other resources of the course), create a business model canvas of the business organization where you work. Since every organization has unique features, do your best to work at the application of the various components of the building blocks of the canvas. Show as much detail as you can so that it is evident that you comprehend the general business model of your organization. There must be a demonstration of synthesis of the procedure on your part. You may need to interview some of the management team to verify the business model details of your organization. You may also benefit from conducting an Internet search of the Business Model Canvas to become comfortable with how it works. There are many other YouTube-type videos on the web that demonstrate the use of the canvas. You will also find several good sources in the Lessons area of the course under the Reading and Resources tab of weeks 1 and 2.
Instructions: Your submittal this week will be considered as a “draft” that should consist of:
1. A Cover page that provides a general description of your organization/business:
Name of the organization (preferably your present organization/business)
Date of origination (or incorporation)
Location (as appropriate; some entities require discretion)
Brief overview of the purpose of the organization/business
Description of your relationship and role in the organization/business
Other details that enable fuller explanation (if applicable)
2. Business Model Canvas with Post-It notes (as seen in the examples). You have three options for the submission of your canvas:
· You may download and use the blank PowerPoint canvas with electronic Post-Its to create your canvas (click here), or
· You may create a Word.doc that lists the nine building blocks (clearly identify each one) and uses bulleted points in the same manner as Post-Its.
· Creation of your post-its via the following web-help site, and then submission of the resulting URL for the finished canvas. See (click on link) https://canvanizer.com/new/business-model-canvas
3. Create a memo (no particular format, but neatly presented) that describes what you learned about your organization/business as a result of creating the business model canvas.
UPLOAD your finished assignment into the Assignment page. You may consolidate the cover page and memo into one document if you use the PowerPoint method of the canvas. If you do all of the assignment as a Word.doc, then you may consolidate the entire assignment into one document; it is your call. However, Each file OF YOUR WORK should be named in the following manner: Last name–truncated Week Number-Assignment name (abbreviated if necessary)
For example: Smith-Wk ...
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
To Graph or Not to Graph Knowledge Graph Architectures and LLMs
Msw a4 format_nov12
1. Paper Title* (use style: paper title)
Subtitle as needed (paper subtitle)
Authors Name/s per 1st Affiliation (Author)
Authors Name/s per 2nd Affiliation (Author)
line 1 (of Affiliation): dept. name of organization
line 2-name of organization, acronyms acceptable
line 3-City, Country
line 4-e-mail address if desired
line 1 (of Affiliation): dept. name of organization
line 2-name of organization, acronyms acceptable
line 3-City, Country
line 4-e-mail address if desired
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, or Math in Paper Title or Abstract. (Abstract)
Keywords—component; formatting; style; styling; insert (key
words)
I.
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 builtin; 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 multileveled 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.
II.
III.
Before you begin to format your paper, first write and save
the content as a separate text file. Keep your text and graphic
files separate until after the text has been formatted and styled.
Do not use hard tabs, and limit use of hard returns to only one
return at the end of a paragraph. Do not add any kind of
pagination anywhere in the paper. Do not number text headsthe template will do that for you.
Finally, complete content and organizational editing before
formatting. Please take note of the following items when
proofreading spelling and grammar:
A. Abbreviations and Acronyms
Define abbreviations and acronyms the first time they are
used in the text, even after they have been defined in the
abstract. Abbreviations such as IEEE, SI, MKS, CGS, sc, dc,
and rms do not have to be defined. Do not use abbreviations in
the title or heads unless they are unavoidable.
B. Units
•
Avoid combining SI and CGS units, such as current in
amperes and magnetic field in oersteds. This often leads
to confusion because equations do not balance
dimensionally. If you must use mixed units, clearly
state the units for each quantity that you use in an
equation.
•
Do not mix complete spellings and abbreviations of
units: “Wb/m2” or “webers per square meter,” not
“webers/m2.” Spell units when they appear in text: “...a
few henries,” not “...a few H.”
•
A. Selecting a Template (Heading 2)
First, confirm that you have the correct template for your
paper size. This template has been tailored for output on the A4
paper size. If you are using US letter-sized paper, please close
this file and download the file “MSW_USltr_format”.
Use either SI (MKS) or CGS as primary units. (SI units
are encouraged.) English units may be used as
secondary units (in parentheses). An exception would
be the use of English units as identifiers in trade, such
as “3.5-inch disk drive.”
•
EASE OF USE
B. Maintaining the Integrity of the Specifications
The template is used to format your paper and style the text.
All margins, column widths, line spaces, and text fonts are
prescribed; please do not alter them. You may note
peculiarities. For example, the head margin in this template
measures proportionately more than is customary. This
measurement and others are deliberate, using specifications
that anticipate your paper as one part of the entire proceedings,
and not as an independent document. Please do not revise any
of the current designations.
PREPARE YOUR PAPER BEFORE STYLING
Use a zero before decimal points: “0.25,” not “.25.”
Use “cm3,” not “cc.” (bullet list)
C. Equations
The equations are an exception to the prescribed
specifications of this template. You will need to determine
Identify applicable sponsor/s here. If no sponsors, delete this text box (sponsors).
2. whether or not your equation should be typed using either the
Times New Roman or the Symbol font (please no other font).
To create multileveled equations, it may be necessary to treat
the equation as a graphic and insert it into the text after your
paper is styled.
•
There is no period after the “et” in the Latin
abbreviation “et al.”
•
The abbreviation “i.e.” means “that is,” and the
abbreviation “e.g.” means “for example.”
Number equations consecutively. Equation numbers, within
parentheses, are to position flush right, as in (1), using a right
tab stop. To make your equations more compact, you may use
the solidus ( / ), the exp function, or appropriate exponents.
Italicize Roman symbols for quantities and variables, but not
Greek symbols. Use a long dash rather than a hyphen for a
minus sign. Punctuate equations with commas or periods when
they are part of a sentence, as in
An excellent style manual for science writers is [7].
a+b =γ
(1)
(1)
α + β = χ.
(1)
Note that the equation is centered using a center tab stop.
Be sure that the symbols in your equation have been defined
before or immediately following the equation. Use “(1),” not
“Eq. (1)” or “equation (1),” except at the beginning of a
sentence: “Equation (1) is ...”
D. Some Common Mistakes
•
•
•
•
The word “data” is plural, not singular.
The subscript for the permeability of vacuum µ0, and
other common scientific constants, is zero with
subscript formatting, not a lowercase letter “o.”
In American English, commas, semi-/colons, periods,
question and exclamation marks are located within
quotation marks only when a complete thought or name
is cited, such as a title or full quotation. When quotation
marks are used, instead of a bold or italic typeface, to
highlight a word or phrase, punctuation should appear
outside of the quotation marks. A parenthetical phrase
or statement at the end of a sentence is punctuated
outside of the closing parenthesis (like this). (A
parenthetical sentence is punctuated within the
parentheses.)
A graph within a graph is an “inset,” not an “insert.”
The word alternatively is preferred to the word
“alternately” (unless you really mean something that
alternates).
•
Do not use the word “essentially”
“approximately” or “effectively.”
•
In your paper title, if the words “that uses” can
accurately replace the word using, capitalize the “u”; if
not, keep using lower-cased.
•
Be aware of the different meanings of the homophones
“affect” and “effect,” “complement” and “compliment,”
“discreet” and “discrete,” “principal” and “principle.”
•
•
to mean
Do not confuse “imply” and “infer.”
The prefix “non” is not a word; it should be joined to
the word it modifies, usually without a hyphen.
IV.
USING THE TEMPLATE
After the text edit has been completed, the paper is ready
for the template. Duplicate the template file by using the Save
As command, and use the naming convention prescribed by
your conference for the name of your paper. In this newly
created file, highlight all of the contents and import your
prepared text file. You are now ready to style your paper; use
the scroll down window on the left of the MS Word Formatting
toolbar.
A. Authors and Affiliations
The template is designed so that author affiliations are not
repeated each time for multiple authors of the same affiliation.
Please keep your affiliations as succinct as possible (for
example, do not differentiate among departments of the same
organization). This template was designed for two affiliations.
1) For author/s of only one affiliation (Heading 3): To
change the default, adjust the template as follows.
a) Selection (Heading 4): Highlight all author and
affiliation lines.
b) Change number of columns: Select the Columns icon
from the MS Word Standard toolbar and then select “1
Column” from the selection palette.
c) Deletion: Delete the author and affiliation lines for
the second affiliation.
2) For author/s of more than two affiliations: To change
the default, adjust the template as follows.
a) Selection: Highlight all author and affiliation lines.
b) Change number of columns: Select the “Columns”
icon from the MS Word Standard toolbar and then select “1
Column” from the selection palette.
c) Highlight author and affiliation lines of affiliation 1
and copy this selection.
d) Formatting: Insert one hard return immediately after
the last character of the last affiliation line. Then paste down
the copy of affiliation 1. Repeat as necessary for each
additional affiliation.
e) Reassign number of columns: Place your cursor to
the right of the last character of the last affiliation line of an
even numbered affiliation (e.g., if there are five affiliations,
place your cursor at end of fourth affiliation). Drag the cursor
up to highlight all of the above author and affiliation lines. Go
to Column icon and select “2 Columns”. If you have an odd
number of affiliations, the final affiliation will be centered on
the page; all previous will be in two columns.
3. B. Identify the Headings
Headings, or heads, are organizational devices that guide
the reader through your paper. There are two types: component
heads and text heads.
Component heads identify the different components of your
paper and are not topically subordinate to each other. Examples
include ACKNOWLEDGMENTS and REFERENCES, and for
these, the correct style to use is “Heading 5.” Use “figure
caption” for your Figure captions, and “table head” for your
table title. Run-in heads, such as “Abstract,” will require you to
apply a style (in this case, italic) in addition to the style
provided by the drop down menu to differentiate the head from
the text.
Text heads organize the topics on a relational, hierarchical
basis. For example, the paper title is the primary text head
because all subsequent material relates and elaborates on this
one topic. If there are two or more sub-topics, the next level
head (uppercase Roman numerals) should be used and,
conversely, if there are not at least two sub-topics, then no
subheads should be introduced. Styles named “Heading 1,”
“Heading 2,” “Heading 3,” and “Heading 4” are prescribed.
C. Figures and Tables
1) Positioning Figures and Tables: Place figures and
tables at the top and bottom of columns. Avoid placing them
in the middle of columns. Large figures and tables may span
across both columns. Figure captions should be below the
figures; table heads should appear above the tables. Insert
figures and tables after they are cited in the text. Use the
abbreviation “Fig. 1,” even at the beginning of a sentence.
TABLE I.
Table
Head
copy
TABLE STYLES
Table Column Head
Table column subhead
Subhead
Subhead
More table copya
a.
Sample of a Table footnote. (Table footnote)
We suggest that you use a text box to insert a graphic
(which is ideally a 300 dpi resolution TIFF or EPS file with
all fonts embedded) because this method is somewhat more
stable than directly inserting a picture.
To have non-visible rules on your frame, use the
MSWord “Format” pull-down menu, select Text Box >
Colors and Lines to choose No Fill and No Line.
b.
“Magnetization, M,” not just “M.” If including units in the
label, present them within parentheses. Do not label axes only
with units. In the example, write “Magnetization (A/m)” or
“Magnetization (A ( m(1),” not just “A/m.” Do not label axes
with a ratio of quantities and units. For example, write
“Temperature (K),” not “Temperature/K.”
ACKNOWLEDGMENT (Heading 5)
The preferred spelling of the word “acknowledgment” in
America is without an “e” after the “g.” Avoid the stilted
expression “one of us (R. B. G.) thanks ...”. Instead, try “R. B.
G. thanks...”. Put sponsor acknowledgments in the unnumbered
footnote on the first page.
REFERENCES
The template will number citations consecutively within
brackets [1]. The sentence punctuation follows the bracket [2].
Refer simply to the reference number, as in [3]—do not use
“Ref. [3]” or “reference [3]” except at the beginning of a
sentence: “Reference [3] was the first ...”
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 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” [4]. Papers that have been accepted for
publication should be cited as “in press” [5]. 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 [6].
[1]
[2]
[3]
[4]
[5]
Fig. 1. Example of a figure caption. (figure caption)
[6]
Figure Labels: Use 8 point Times New Roman for Figure
labels. Use words rather than symbols or abbreviations when
writing Figure axis labels to avoid confusing the reader. As an
example, write the quantity “Magnetization,” or
[7]
G. Eason, B. Noble, and I.N. Sneddon, “On certain integrals of
Lipschitz-Hankel type involving products of Bessel functions,” Phil.
Trans. Roy. Soc. London, vol. A247, pp. 529-551, April 1955.
(references)
J. Clerk Maxwell, A Treatise on Electricity and Magnetism, 3rd ed., vol.
2. Oxford: Clarendon, 1892, pp.68-73.
I.S. Jacobs and C.P. Bean, “Fine particles, thin films and exchange
anisotropy,” in Magnetism, vol. III, G.T. Rado and H. Suhl, Eds. New
York: Academic, 1963, pp. 271-350.
K. Elissa, “Title of paper if known,” unpublished.
R. Nicole, “Title of paper with only first word capitalized,” J. Name
Stand. Abbrev., in press.
Y. Yorozu, M. Hirano, K. Oka, and Y. Tagawa, “Electron spectroscopy
studies on magneto-optical media and plastic substrate interface,” IEEE
Transl. J. Magn. Japan, vol. 2, pp. 740-741, August 1987 [Digests 9th
Annual Conf. Magnetics Japan, p. 301, 1982].
M. Young, The Technical Writer’s Handbook. Mill Valley, CA:
University Science, 1989.