XML Reference Manual

` PDF 2 XML Conversion Work Instructions for Conference

Confidential – Aptara Proprietary Version 1.1.0.1 6 September’13 Page 1 of 28

Input PDF and Meta XML file

Output XML, HTML, Images

Process

1. Convert extracted TBXML to XML using conversion script. Script Converts

Conversion of TBXML to XML based on conf-jats1.dtd DTD (version 1.5)

Injection of Tex tagging from the server

Renaming of extracted Images as per specifications

2. Manual Review and Fixing

Points for manual review and fixing are mentioned below

3. Validation

Validation of XML files according to DTD RULES.

Validation of TeX files according to Vtex RULES.

4. QA Checks

Run QA script and fix the error logs, if any

Source Input Folder Structure

+Year

+Publication Number

+Issue Number

+Article Number

PDF/XML/Images



Manual Review and Fixing

1. Sequence for lines of XML and Doctype declaration as

Example tagging

<?xml version="1.0" encoding="utf-8"?>

<!DOCTYPE conf-article PUBLIC "-//IEEE//DTD IEEE Conferences JATS-based DTD v1.5 20130121//EN" "conf-jats1.dtd">

RULES

Word “utf” should be in lower case

DTD version may vary as per current provided DTD by IEEE.

2. Element “conf-article”

Example tagging <conf-article article-type="research" content-type="orig-research" dtd-version="1.5" peer-reviewed=”yes” open-access="no"

xml:lang="en" show-flag=”show” lifecycle="final">

RULES

Validate content-type attribute value from the XML metadata element <contenttype/>

Attribute “article-type” may vary according to the content of article

Need to capture the attributes as defined in example only. No attribute should be extra or missing in the final file

Validate open access attribute value from Meta xml file

a. If element value <articleopenaccess/> is “F”, “open-access="no”

b. If element value <articleopenaccess/> is “T”, “open-access="yes”

Generatre @xml:lang=”en”

Generate @show-flag to the element <conf-article> based on Metadata element <articleshowflag>

a. If value appears in Meta as “F”, capture as “no-show”

b. If value appears in Meta as “T”, capture as “show”

Attribute peer-reviewed as “yes” to <conf-article>

If attribute “show-flag” do not appear in Meta xml, we need to capture as “show”

3. Comment Tags

Example tagging







RULES

Delivery Date: Should be uploading date

XML Script: Should be current TBXML 2 XML conversion script version

Batch: Should be generated as per guidelines



4. Conference Acronym

Example tagging

<conf-proc-id conf-proc-id-type="conf-acronym">CIPS</conf-proc-id>

RULES

Always be in Capital Letters

Should be captured from Meta XML from below tag

<acronym acronymtype="CONFERENCE_ACRONYM">CIPS</acronym>

5. Conference full title

Example tagging

<conf-full-title>2012 7th International Conference on Integrated Power Electronics Systems (CIPS)</conf-full-title>

RULES


<publication> <title><![CDATA[2012 7th International Conference on Integrated Power Electronics Systems

(CIPS)]]></title>

Capture the content case as appearing in Meta XML

6. Conference Normalized Title

Example tagging

<conf-normalized-title>Integrated Power Electronics Systems (CIPS), 2012 7th International Conference</conf-normalized-

title>

RULES


<normtitle><![CDATA[Integrated Power Electronics Systems (CIPS), 2012 7th International Conference

on]]></normtitle>

Do not capture word “on” appearing at the end of title

Capture the content case as appearing in Meta XML

7. Volume

Example tagging

<volume>1</volume>

RULES

Capture from meta XML file “<volumenum>”

If dummy tag is appearing in Meta XML, capture the element as dummy <volume/>



8. ISBN

Example tagging

<isbn content-type="print">978-3-8007-3414-6</isbn>

RULES

Capture from meta XML file “<isbn>”

Attribute “mediatype” appearing in meta xml should be captured as attribute “content-type” in output xml file

Do not convert the attribute “isbntype”, if appearing in meta xml

Multiple ISBN appearing in Meta xml should be captured in output xml file

If duplicate ISBN appearing with same element and attribute value, it should be captured as once

If 2 ISBN appearing with same element value, but different attribute value or vice versa, need to capture as 2

elements in output xml file

Do not capture the dummy markup, if appearing in meta xml file

Capture @content-type="paper" in <isbn> as content-type=”print”

Capture @content-type="CD" in <isbn> as content-type=”online”

All attributes should be in lowercase

9. ISSN

Example tagging

<issn content-type="print">1530-1591</issn>

RULES

Capture from meta XML file “<issn>”

Attribute “mediatype” appearing in meta xml should be captured as attribute “content-type” in output xml file

Do not convert the attribute “issntype”, if appearing in meta xml

Multiple ISSN appearing in Meta xml should be captured in output xml file

Capture @content-type="paper" in <issn> as content-type=”print”

Capture @content-type="CD" in <issn> as content-type=”online”

All attributes should be in lowercase

If duplicate ISSN appears

Case 1: If duplicate ISSN values are appearing with same attribute

Capture it at once

Case 2: If duplicate ISSN values are appearing with different attribute

Use the mediatype "Paper" ISSN only and omit the others

Do not capture the dummy markup, if appearing in meta xml file

10. Conference Name

Example tagging

<conf-name>2012 Design, Automation & Test in Europe Conference & Exhibition (DATE 2012)</conf-

name>

RULES

Should be captured from Meta XML from element “conftitle”

Capture the content case as per Meta xml file



11. Conference Start Date

Example tagging

<conf-start iso-8601-date =”2012-03-12”><day>12</day><month>03</month><year>2012</year></conf-start>

RULES

Should be captured from Meta XML from element “<confdate confdatetype="Start">”

Capture the value as per Meta xml file.

Capture the month/day/Year value as per Meta file. Need to convert as numeric value

Month and Day should be captured as 2 digit numeric and year should be 4 digit numeric value

Generate the attribute “iso-8601-date” in format of “YYYY-MM-DD”

While generating @yyyy-mm-dd, need to check if element value of day is either blank or “0” or “00”,

generate the attribute value in format “yyyy-mm”

12. Conference End Date

Example tagging

<conf-end iso-8601-date =”2012-03-16”><day>16</day><month>03</month><year>2012</year></conf-end>

RULES

Should be captured from Meta XML from element “<confdate confdatetype="End">”



While generating @yyyy-mm-dd, need to check if element value of day is either blank or “0” or “00”, generate

the attribute value in format “yyyy-mm”

13. Conference Location

Example tagging

<conf-loc><city>Nuremberg</city>, <country>Germany</country></conf-loc>

RULES

Should be captured from Meta XML from element “<conflocation>”

Need to mark the content as “city”, “state” or “country”

14. Article DOI

<article-id pub-id-type="doi">10.1109/ICBBE.2009.5162321</article-id>

RULES

Should be captured from Meta XML from element “<articledoi>”

15. Xplore Article ID

Example tagging

<xplore-article-id>6176423</xplore-article-id>

RULES

Should be captured from Meta XML from element “<article><amsid>”

If either element does not appear in meta xml or appearing as dummy or “0”, need to generate the value from

folder structure. The value will be same as article number



16. Xplore Issue

Example tagging

<xplore-issue>6176405</xplore-issue>

RULES

Should be captured from Meta XML from element “<volume><amsid>”


folder structure. The value will be same as Issue number

17. Xplore Publication Id

Example tagging

<xplore-pub-id>6171057</xplore-pub-id>

RULES

Should be captured from Meta XML from element “<publicationinfo><amsid>”


folder structure. The value will be same as Publication number

18. Article Title

Example tagging

<article-title>Automated Generation of Directed Tests for Transition Coverage in Cache Coherence Protocols</article-

title>

RULES

Should be captured from PDF file

If subtitle appears, should be captured as <subtitle>

Content case should be captured as per PDF file

Do not capture period if appearing at the end of title

19. Authors and Affiliation

Example tagging

<contrib-group>

<contrib contrib-type=”author” id=”contrib1”><string-name specific-use="display"><surname>Qin</surname><given-

names>Xiaoke</given-names></string-name>

<email>[email protected]</email>

<xref ref-type="aff" rid="aff1"/>

<xref ref-type="bio" rid="bio1"/>

</contrib>

<contrib contrib-type=”author” id=”contrib2”><string-name specific-use="display"><surname>Mishra</surname><given-

names>Prabhat</given-names></string-name>

<email>[email protected]</email>

<xref ref-type="aff" rid="aff1"/></contrib>



</contrib-group>

<aff id="aff1">

<institution content-type="division">Computer and Information Science and Engineering</institution>

<institution content-type="institution">University of Florida</institution>

<country>USA</country>

</aff>

RULES

Content case for Author name <degrees>, <given-names>, <surname>, <suffix> should be as per PDF file

Multiple authors should be tagged in individual <contrib.> element

If corresponding information is available, need to provide the attribute corresp=”yes” to the element <contrib>.

Note that no need to mark corresp=”no” to remaining authors.

No need to capture the text “Corresponding Author” along with its link in the output xml file

No need to capture the text “Primary Author” along with its link in the output xml file

If article has only 1 author, we need to set the value as corresp=”yes”

If primary information is available, need to provide the attribute primary=”yes” to the element <contrib.>. Note

that no need to mark primary=”no” to remaining authors

Personal information of authors like email address should be captured in element <contrib>

No need to capture word “Email”

If Biography of particular author appears in article, need to provide element <xref ref-type="bio" rid="bio1">

If affiliation links appears as superscript in PDF, need to capture as superscript or otherwise as PCDATA

Generate @id to the element <contrib>. The id format should be “contrib1”. Need to maintain the sequence based

on Authors in @id

Generate @specific-use="display" to <string-name> in Front Matter only

Generate attribute contrib-type=”author” to element <contrib>. Incase word “editor” appear in <aff> or <strin-

name> of particular author, value should be contrib-type=”editor”

Need to generate an attribute to converted <institution> as

<institution content-type="division">

If words “division” or “Div.”

<institution content-type="institution">

If words like “Institute “, “inst.”, “univ.” or “university”, “Laboratory”, “Lab.”, “School”, “College”, “Co.”,

“Pvt.”, “Center”, “Company” or “Institut”

<institution content-type="department">

If words like “dept.” or “department” or “dept.”

If no above condition matches, generate @ as <institution content-type="division">

Element Role

Need to capture additional information like “editor-in-chief, chief scientist, photographer, research associate” as

element <role/>



Society Member Type

Member Type information should be captured as an attribute “society-member-type“ to the element <contrib./>.

No need to capture the value in Element Role

We need to capture the value as per below chart

Value Meaning

Associate_Member Associate Member

Fellow Fellow

Graduate_Student_Member Graduate Student Member

Honorary_Fellow Honorary Fellow

Honorary_Life_Member Honorary Life Member

Honorary_Member Honorary Member

Life_Associate_Member Life Associate Member

Life_Fellow Life Fellow

Life_Member Life Member

Life_Senior_Member Life Senior Member

Member Member

Senior_Member Senior Member

Student_Member Student Member

If Author name appears in other language including accented characters

Need to generate the element <string-name specific-use="index">

<name-alternatives><string-name specific-use="display">

<surname>Válek</surname>

<given-names>Jirí</given-names></string-name>

<string-name specific-use="index">

<surname>Valek</surname>

<given-names>Jiri</given-names></string-name>

</name-alternatives>

If non-latin characters (such as Chinese, Japanese, Korean, Russian, etc.) are present, Use Unicode symbols.

20. Affiliation Link

Example tagging

<xref ref-type="aff" rid="aff1"><sup>1</sup></xref></contrib>

RULES

Each author must have <xref> element if affiliation is appearing

Element value of <xref> should be as per PDF file

If content like “1” “dagger” is appearing as superscript, need to capture in element <sup>

If no label is appearing in PDF file, need to capture as dummy element like <xref ref-type=”aff” rid=”aff1”/>



21. Affiliations

<aff id="aff1">

<sup>1</sup>

<institution>Dept. of High-Frequency Electronics, University of Paderborn</institution>

<addr-line>Warburgerstr. 100, D-33098</addr-line>

<city>Paderborn</city>

<country>Germany</country></aff>

RULES

Each unique affiliation should be captured in individual element <aff>

Affiliation label should be captured, if appearing in PDF file

Mark the content as “institution”, “addr-Line”, “city”, “state” “country”…..

If different markup of same type appears in 2 line, example 2 institutes appears in an affiliation, mark the content

in 2 element “institution”. Do not merge the content with adding comma

22. Publication date

Example tagging

<pub-date iso-8601-date=”2012-03”><month>03</month><year>2012</year></pub-date>

RULES

Capture from Meta xml from the element “<date datetype="OriginalPub">”

If Day appears with value “0” or “00”, do not capture in output xml file



23. First and Last Page

Example tagging

<fpage>1</fpage><lpage>2</lpage>

RULES

Should be captured from PDF

24. Copyright Statement

Example tagging

<copyright-statement>ISBN 978-3-8007-3414-6 © VDE VERLAG GMBH · Berlin · Offenbach,

Germany</copyright-statement>

RULES

Should be captured from PDF file

Capture the complete statement (including ISBN, location….)

If appears as footnote, need to capture both as copyright statement and footnote



25. Copyright Year

Example tagging

<copyright-year>2012</copyright-year>

RULES

Should be captured from meta xml file from element <copyright><year>

26. Copyright Holder

Example tagging

<copyright-holder copyright-owner="Other">VDE VERLAG GmbH</copyright-holder>

RULES

Should be captured from meta xml file from element <copyright> <holder>

Generate attribute “copyright-owner” as per below specifications

27. Price

Conversion of element <price> from copyright statement

<license><license-p><price currency="USD">25.00</price></license-p></license>

Place the element after </copyright-holder> in element <permission>

If not appearing in PDF file, do not capture the dummy tag

28. Abstract

Example tagging

<abstract xml:lang="en"><title>Abstract</title>

RULES

A. If Abstract is appearing in PDF file

Capture from PDF file

Crown Crown copyright

IBM The IBM corporation

IEEE IEEE

NA Not applicable

Other Copyright holder is not one of the other named values.

Unknown Copyright holder is not known.

USGov United States Government



B. If Abstract is NOT appearing in PDF file

Case 1: If first paragraph of PDF is same as Abstract appearing in Meta xml

Capture content as abstract section from Meta xml and also as first paragraph in body section

Case 2: If first paragraph of PDF is not same as Abstract appearing in Meta xml

Capture content as abstract section from Meta xml

Case 3: If Body section do not starts with Paragraph, but appearing in Meta xml

Capture content as abstract section from Meta xml

Case 4: If abstract is not appearing in both PDF and Meta XML

Capture first paragraph (wherever it appears in the PDF) as Abstract

Always capture the attribute “xml:lang”

Capture title if appearing in PDF file

29. Keywords

Example tagging

<kwd-group kwd-group-type="Inspec">

<kwd>thermomechanical treatment</kwd>

</kwd-group>

<kwd-group kwd-group-type="InspecFree">

<kwd>thermo mechanical reliability</kwd>

<kwd>low-temperature low-pressure die bonding</kwd>

</kwd-group>

<kwd-group kwd-group-type="IEEE">

<kwd>Microassembly</kwd>

<kwd>Bonding</kwd>

</kwd-group>

RULES

a. Capture keywords from both PDF and Meta XML file

b. Keywords from Source PDF file should be captured with attribute “AuthorFree”

c. Keywords where exact match is found between captured from PDF and Meta XML file would be captured for

single time in output xml file

d. Duplicate keywords should be deleted from the bottom

30. Copyright statement appearing as footnote

Despite this non-standard copyright location in the PDF, it does not change the XML tagging, The copyright information

is still tagged in the front matter in the <permissions> block. The important thing is, this is still copyright data and its PDF

location is not relevant in the XML. The fact that it appears as a footnote in the PDF is ignored in the XML. The correct

XML tagging is as follows:



<permissions>

<copyright-statement>9781-4244-2622-5/09/$25.00 ©2009 IEEE</copyright-statement>

<copyright-year>2009</copyright-year>

<copyright-holder copyright-owner="IEEE">IEEE</copyright-holder>

</permissions>

If not appearing in PDF file, provide the dummy tag

31. Counts

<equation-count count=""/> Count of numbered display equations. Need to count the total unique IDs of <disp-formula>.

Example, if an article has 6 equations and 1 to 5 equation is captured as single equation, need to capture the value

as <equation-count count="2"/>

<fig-count count=""/>

Count of numbered figures

<page-count count=""/>

Count of total pages

<ref-count count=""/> Count of total references

<table-count count=""/> Count of numbered tables

Do not capture element <word-count>

Note: If element do not appears in XML file, mark the attribute value as “0”



32. Funding Statement

Example tagging

<funding-group>

<award-group id="grant1">

<funding-source>University of Toronto, the Connaught Fund, 863 Program of China</funding-source>

<award-id>2012AA010302</award-id>

</award-group>


<funding-source>NSFC</funding-source>

<award-id>61070037, 61025009, 60903039, 61103016</award-id>

</award-group>


<funding-source>China Edu. Fund.</funding-source>

<award-id>20094307120012</award-id>

</award-group>

<funding-statement>This work is supported by the University of Toronto, the Connaught Fund, 863 Program of China

(2012AA010302) NSFC (61070037, 61025009, 60903039, 61103016), China Edu. Fund.(20094307120012), Hunan Prov. Innov.

Fund. For PostGrad. (CX2010B032).</funding-statement>

</funding-group>

RULES

Need to mark the multiple Award ids in different elements

If acknowledgement section contains words like “funded” or “supported”, the line should also need to mark as

finding statement (along with award ID and funding source)

Generate @id to <award-group > as <award-group id="grant4"> in sequence

If sentence starts with “Color versions” appears in <funding-statement>, the element <funding-statement> should

be converted as <supplementary-material><p> and move the content before element <permission>

If sentence starts with “DOI” appears in <funding-statement>, the element <funding-statement> should be

converted as <author-comment><p> and move the content in <contrib.-group> after last closing of </contrib>

element

If sentence have Information that does not have any other clearly designated element such as "reviewed by...";

"approved by..."; a conference website; an authors website; corresponding author, etc., should be tagged under

<author-comment><p> and move the content in <contrib.-group> after last closing of </contrib> element

33. Inline Formula in <kwd>, <funding-statement>, <source>

When confronted with an <inline-formula> or <inline-graphic> within author supplied <kwd>, <funding-statement> or

<source>, a temporary work-around for the XML tagging until the DTDs are updated. IEEE will then programmatically

search and replace this with the proper tagging:

Example Tagging

<kwd><named-content content-type="math"><inline-formula><tex-math>$a^2+b^2=c^2$</tex-math></inline-

formula></named-content></kwd>

<kwd><named-content content-type="graphic"><inline-graphic xlink:href="kwd-graphic1234567.tif"/></named-

content></kwd>



34. Section

Example tagging

<sec id="sec1">

<label>1</label><title>Introduction</title>

RULES

Label should be captured in element <label>

Title should be captured as per PDF file

Section hierarchy should be as per PDF file

If all section (like level 3) is appearing in italic, no need to mark the same

If title appears as small caps, need to mark the content as small caps

<title>I<sc>ntroduction of</sc> P<sc>rogramming</sc></title>

35. Algorithm

Example tagging

<algorithm rule=”both”>

<label>Algorithm 1:</label><title>The Moral Science</title>

<alg-item><p><graphic xlink:href="6292298-alg-1-source.tif"/></p></alg-item></algorithm>

RULES

Should be captured as Image

Naming convention should be “alg”

Attribute “rule” with value “both” should be captured in element <algorithm>

36. Figure

Example tagging

<fig id="fig1">

<label>Fig. 1</label>

<caption><title>Die bonding shear strength of dummy chips bonded onto a Cu substrate metalized with Ag as a function

of bonding temperature.</title></caption>

<graphic xlink:href="6170664-fig-1-source.tif"/>

</fig>

RULES

All numbered graphic should be renamed as per specifications

Need to place at the end of paragraph where it is appearing

Content case for caption should be as per PDF file

Label should be captured in element <label> as per PDF file

Unnumbered Figure should be named as “graphic”. Example “6170664-graphic-1-source.tif”

Only ID and xlink:href should appears as attribute



37. Tables

Example tagging

<table-wrap id="table3">

<label>TABLE III.</label><caption><title>LOCATION</title></caption>

<table rules="all" frame="box" cellpadding="5">

<colgroup>

<col span="5"/>

</colgroup>

<thead>

<tr><th rowspan="2"/><th colspan="4">Where was the questionnaire filled?</th></tr>

<tr><th>Location</th><th>Frequency</th><th>Valid%</th><th>Cumulative%</th></tr>

</thead>

<tbody>

<tr><td rowspan="8">Valid</td><td>Sandton</td><td>39</td><td>18.7</td><td>18.7</td></tr>

<tr><td>Durban</td><td>39</td><td>18.7</td><td>37.3</td></tr>

<tr><td>Polokwane</td><td>10</td><td>4.8</td><td>42.1</td></tr>

<tr><td>Kimberly</td><td>14</td><td>6.7</td><td>48.8</td></tr>

<tr><td>Zululand</td><td>46</td><td>22.0</td><td>70.8</td></tr>

<tr><td>White River</td><td>38</td><td>18.2</td><td>89.0</td></tr>

<tr><td>Auckland Park</td><td>23</td><td>11.0</td><td>100.0</td></tr>

<tr><td>Total</td><td>209</td><td>100.0</td><td/></tr>

</tbody>

</table>

</table-wrap>

RULES

1. Need to capture as Text in XML and as Image in HTML other than complex tables like

a. Tables with multiple tgroups

b. Multiple images spanning over multiple columns and rows

2. No cell shading or coloring should be captured



3. No alignment is required

4. Need to insert attribute values: @cellpadding="5"; @frame="box" and @rules="all" to element <table>

5. Linking of References, Figures, Tables needs to be done, if appearing

6. Use <table-wrap-foot> for any footer text that appears below the <table>

Need to mark for emphasis in <td> and <th> as appearing in PDF file

Need to place at the end of paragraph where it is appearing

Content case for caption should be as per PDF file

Label should be captured in element <label> as per PDF file

7. If content appears in tabular format and does not contain a label, title, caption, or table headings (column heads),

need to capture in element <array>

Example Tagging

<array>

<tbody>

<tr><td align="center" rowspan="1" colspan="1"><bold>U.S. Patent Documents</bold></td></tr>

<tr><td rowspan="1" colspan="1">7010440</td><td rowspan="1" colspan="1">Mar. 2006</td>

<td rowspan="1" colspan="1">Lillis <italic>et al.</italic></td></tr>

</tbody>

</array>

8. Diagonal Text I table head

Need to capture as Text

Diagonal text should be captured with element <break/>. Example <th>remark<break/>index</th>

38. Inline equations

Example tagging

<inline-formula><tex-math notation="TeX">$v1$</tex-math></inline-formula>

RULES

All inline math content (including Greek entities) appearing in running text should be mark as Math based on

Vtex RULES

Chemical equations should be captured as text

Should be enclosed with single “$”

39. Display equations

Example tagging

<disp-formula id="deqn1"><tex-math notation="TeX">$$M=r{H}\cdot X(t)+r_{L}\cdot[D-X(t)]\eqno{\hbox{(1)}}$$</tex-

math></disp-formula>

RULES

All display math content appearing in running text should be mark as Math based on Vtex RULES

Should be enclosed with double “$$”

Numbered equation should have an id like “deqn1”

If multiple numbered equations are tagged as single equation, ID need to be provided in range as “deqn3-6”

(Here, equation 6, 7 and 8 are tagged as single_)

No need to provide the ID to unnumbered display equation



Example tagging

<disp-formula><tex-math>$$ {\BBP}_{m}(y)=2^{-\bar {d}_{B}(H({\tilde {Y}}\vert \bar {X})+D(\bar {X} {\tilde

{Y}}\vert\vert \bar {X}Y))} $$</tex-math></disp-formula>

and

<disp-formula><tex-math>$$ {\BBP}_{\star}(y)=2^{-\bar {d}_{B}(H({\tilde {Y}})+D({\tilde {Y}}\Vert Y_{\star}))}. $$</tex-

math></disp-formula>

Hence,

<dis-formula><tex-math>$$ \eqalignno{ {\BBP}_{\star}(y)& ={\BBP}_{m}(y)2^{-\bar {d}_{B}(D(\bar {X} {\tilde

{Y}}\Vert \bar {X}Y_{\star})-D(\bar {X} {\tilde {Y}}\Vert \bar {X}Y))}\cr & ={\BBP}_{m}(y)2^{-

{d}_{B}(D(XY\VertXY_{\star})+o(1))}} $$</tex-math></disp-formula>

40. Sidebars

<boxed-text id="sidebar1" position=”float”>

<sec>

<title>Boxed Text/Sidebar</title>

<p> There are many transitions that start and end in the same state. </p>

</sec>

</boxed-text>

RULES

If linking is appearing for the text in running body matter, needs to provide the ID for the element

Generate @position as “float” to the element <boxed-text>

41. Footnotes

Example tagging

<xref ref-type="fn" rid="fn1"/><fn id="fn1"><p>There are many transitions that start and end in the same state. </p></fn>

RULES

Should be captured at its callouts

If label appears, need to capture in <label>

If copyright statement is appearing as footnote symbol, need to capture both as Footnote and Copyright

42. Emphasis Markup

<bold> Bold

<italic> Italic

<monospace> Monospace Text (Typewriter Text)

<sc> Small Caps

<underline> Underline



43. List

Ordered List

Example tagging

<list list-type="order">

<list-item><label>1.</label><p>We propose a dynamic migration policy, that decides at run-time.</p></list-item>

<list-item><label>2.</label><p>The DSR architecture uses the traditional least recently used (LRU).</p></list-item>

</list-item></list>

<list list-type="bullet">

<list-item><label>—</label><p>We propose a dynamic migration policy, that decides at run-time.</p></list-item>

<list-item><label>—</label><p>The DSR architecture uses the traditional least recently used (LRU).</p></list-item>

</list-item></list>

<list list-type="order" prefix-word="Step">

<list-item><label>1.</label><p>Poodles</p></list-item>

<list-item><label>2.</label><p>Persian Cats</p></list-item></list>

RULES

All numeric list should be marked as <list list-type="order">

All labels need to capture in element <label> (like “1.”, or “1)” or “(1)”, “a”, “A.”, “I”……)

For ordered list appearing with prefix labels like “Step 1”, need to insert an attribute “prefix-word”

If list get continue, generate the attribute “continued-from”

Attribute value for “list-type“ can be either of below

Order Ordered list. Prefix character is a number or a letter, depending on style.

Bullet Unordered or bulleted list. Prefix character is a bullet and dash

alpha-lower Ordered list. Prefix character is a lowercase alphabetical character.

alpha-upper Ordered list. Prefix character is an uppercase alphabetical character.

roman-lower Ordered list. Prefix character is a lowercase roman numeral.

roman-upper Ordered list. Prefix character is an uppercase roman numeral.

Simple Simple or plain list (No prefix character before each item)

44. Definition List

Example tagging

<def-list>

<def-item><term>Diagnostic coverage</term><def><p>The fractional decrease in the probability </p></def></def-item>

<def-item><term>Dangerous failure</term><def><p>A failure having the potential </p></def></def-item>

<def-item><term>Dangerous failure detected</term><def><p>A failure detected by on-line diagnostic tests</p></def>

</def-item>

45. Statement

Example tagging

<statement id="state1"><label>Proof of Theorem 1.</label>

<p>First, we obtain the two predicted parities of block 1</p></statement>



RULES

Capturing sections like “Theorem”, “Lemma”, “Remark”, “Proof”, and “Prepositions” etc. as <statement> and its

linking in body text

If colon appears at the end of label, we need to capture the same

46. Appendix

Example tagging

<app-group><app id=”appa”>

<label>Appendix A</label>

<statement id="state1"><label>Proof of Theorem 1.</label>

<p>First, we obtain the two predicted parities of block 1</p>

</statement></app>

<app id=”appb”><label>Appendix B</label>

<p>As seen in <xref ref-type="fig" rid="f2">Fig. 2</xref>, the S-box and the inverse S-box share</p></app></app-group>

RULES

Must have an ID attribute to the element <app>

47. Acknowledgments

Example tagging

<ack>

<label>VI</label><title>Acknowledgments</title>

<p> First, we obtain the two predicted parities of block 1</p></ack>

RULES

If appears exactly before the References, should be captured as part of <back>

48. Biography

Example tagging

<bio id="bio1">

<title>B<sc>iographical</sc> S<sc>ketch</sc></title>

<graphic xlink:href="6170667-photo-1-source.tif"/>

<p><xref ref-type=”contrib” rid=”contrib1”>Ailamaki</xref> is a Professor of Computer Sciences at the Ecole

Polytechnique Federale de Lausanne (EPFL) in Switzerland.</p></bio></bio-group>

RULES

1. Needs to provide the link to the Author name with element <contrib>



49. Manuscript Date

We need to capture in element <pub-date>

Example Tagging

Manuscript accepted January 30, 2012

<pub-date date-type=”accepted” iso-8601-date=”2012-01-30”><day>30</day><month>01</month><year>2012</year>

</pub-date>

Below attribute value can be captured in XML file for the attribute

Attribute Value Description

accepted The date a document, typically a manuscript, was accepted

corrected The date an article was corrected.

pub The publication date (electronic or print)

preprint Preprint dissemination date (electronic or print)

retracted The date an article was retracted

received The date a document, typically a manuscript, was received

rev-recd The date a revised document was received

rev-request The date revisions were requested

If the Value do not match with above chart, do not capture the @date-type in element <date/>

50. References

RULES

Need to capture both label and title if appearing

Punctuations should be captured as per PDF file

Always capture punctuation like comma outside the element

Each Reference will be captured in <ref/> element

No need to generate the attribute for <institution> in Reference Section

References appearing without labels, we need to generating the sequence number as “[1] [2] [3]….”and link the

same in body text

Note: If articles are appearing without labels in Reference, but linked with labels like “a”, “a-c”, in the body

text, we need to generate the labels for each reference and link the same in body text and ignore the content

like “a”..



No need to generate attribute “iso-8601-date“ in references

No need to mark as <city>, <state> or <country> to the element <conf-loc>, if appearing in References.

Generate attribute specific-use="IEEE", if word IEEE appears in element <source>

<source specific-use="IEEE">IEEE Trans. Microw. Theory Tech.</source>

Note: No need to generate attribute otherwise

Generate attribute “country” to the element <patent>

Attribute value of “publication-format” can be either from

Need to capture the any one value from “print”, “online” or “other”

If a reference clearly only has a URL, with no volume/issue/page number print-specific information, then set

the @publication-format attribute to "online."

If a reference has a URL, but also has volume/issue/page number data, then set the @publication-format

attribute to "print."

DOI: <pub-id pub-id-type=”doi”> 10.1109/COMPSACW.2012.55</pub-id>

<named-content content-type="ref-degree">M.S. thesis, Ph.d degree, Ph.D. dissertation</ named-content >

If a reference does not have a URL, not a clear reference to a CD or other electronic media, then set the

@publication-format attribute to "print."

If a reference has specific information about a CD, DVD or other media, then set the @publication-format

attribute to "other."

Note: The vast majority of IEEE references will be either "print" or "online".

Attribute value of publication type can be either from

a. periodical

b. report

c. thesis

d. standard

e. manual

f. confproc

g. confpaper

h. patent

i. unpubd

j. software



k. other [Need to capture the attribute, if appears]

l. online

m. government

n. book

Examples for each type

Periodical

<ref id=“ref1"><label>[1]</label><mixed-citation publication-type="periodical" publication-format="print"><person-group

person-group-type=”author”><string-name><given-names>F.</given-names> <surname>Rusin</surname></string-name>

and <string-name><given-names>G. </given-names> <surname>Bogom </surname></string-name></person-group>,

“<article-title>Oratron</article-title>,” <source>Proc. of the IEEE</source>, vol. <volume>57</volume>,

<year>1969</year>, <fpage>720</fpage>-<lpage>722</lpage>.</mixed-citation></ref>

Book

<ref id=“ref13"><label>[13]</label><mixed-citation publication-type="book" publication-format="print"><person-group

person-group-type=”author”><string-name><given-names>D.J.</given-names> <surname>Smith</surname></string-

name></person-group>, <source>Reliability, Maintainability, and Risk</source>. <publisher-loc>London, UK</publisher-

loc>: <publisher-name>Butterworth Heinemann</publisher-name>; <year>2000</year>.</mixed-citation></ref>

Conference Proceedings

<ref id=“ref1"><label>[1]</label><mixed-citation publication-type="confproc" publication-format="print"><person-group

person-group-type=”author”><string-name><given-names>I.</given-names> <surname>Pandis</surname></string-

name>, <string-name><given-names>R.</given-names> <surname>Johnson</surname></string-name>, </person-group>:

<article-title>Data-Oriented Transaction </article-title>. <conf-name>VLDB Conference</conf-name>, <source>Proceedings

of the VLDB Endowment</source>, <volume>3</volume>(<issue>1</issue>), <conf-date>2010</conf-date>.</mixed-

citation></ref>

Conference Paper

<ref id=“ref6"><label>[6]</label><mixed-citation publication-type="confpaper" publication-format="print"><person-group

person-group-type=”author”><string-name><given-names>R.</given-names> <surname>Johnson</surname></string-

name>, <string-name><given-names>N.</given-names> <surname>Hardavellas</surname></string-name>, </person-

group>: <article-title>To Share or Not To Share?</article-title> <conf-name>33rd VLDB Conference</conf-name>, <conf-

loc>Vienna, Austria</conf-loc>, <conf-date>2007</conf-date>.</mixed-citation></ref>

Report

<ref id=“ref9"><label>[9]</label><mixed-citation publication-type="report" publication-format="print"><person-group

person-group-type=”author”><string-name><given-names>D. X.</given-names> <surname>Zhang</surname></string-

name></person-group>. <source>Olympic Traffic Monitoring Report</source>, <publisher-name>Beijing Transportation

Research Center</publisher-name>, (<year>2008</year>).</mixed-citation></ref>

Online

<ref id=“ref5"><label>[5]</label><mixed-citation publication-type="online" publication-format="print"><person-group

person-group-type=”author”><string-name><given-names>A.A.</given-names>

<surname>Frederickson</surname></string-name></person-group>. “<article-title>Comparison of programmable

electronic safety-related system architectures</article-title>”. [Web Page]. Available at:

<uri>http://www.safetyusersgroup.com/ default.asp</uri> Accessed <date-in-citation content-type="access-

date"><year>2005</year> <month>Apr</month> <day>25</day></date-in-citation>.</mixed-citation></ref>



<ref id=“ref9"><label>[9]</label><mixed-citation publication-type="online" publication-format="online">Available at:

<uri>http://www.safetyusersgroup.com/ default.asp</uri>.</mixed-citation></ref>

Note: If only URI information appears in Reference, need to capture @ publication-format as “online”

Government Document

<ref id=“ref5"><label>[5]</label><mixed-citation publication-type="government" publication-

format="print"><collab>Reliability Analysis Center</collab>. <gov>NPRD-95 Nonelectronic Parts Reliability Data</gov>.

<publisher-loc>Rome, NY</publisher-loc>; <year>1995</year>.</mixed-citation></ref>

Thesis

<ref id=“ref21"><label>[21]</label><mixed-citation publication-type="thesis" publication-format="print"><person-group

person-group-type=”author”><string-name><given-names>P. S.</given-names> <surname>Wellman</surname></string-

name></person-group>. <source>Tactile Imaging</source>. PhD thesis, <institution>Harvard University</institution>,

<year>1999</year>.</mixed-citation></ref>

Patent <ref id=“ref1"><label>[1]</label><mixed-citation publication-type="patent" publication-format="print"><person-group person-group-

type=”author”><string-name><surname>Seaholtz</surname>, <given-names>John W.</given-names></string-name>, <etal/></person-

group>, <source>United States Patent Number</source> <patent country="US">5,812,786</patent>, <year>1998</year>.</mixed-

citation></ref>

Standard <ref id=“ref2"><label>[2]</label><mixed-citation publication-type="standard" publication-format="print"><std>ANSI Standard T1.413-

1998, Network and customer installation interfaces — Asymmetrical Digital Subscriber Line (ADSL) Metallic Interface</std>,

<year>1998</year>.</mixed-citation></ref>

Generation of @person-group-type=”author” to <person-group> in references

51. Notes

Sections like "Note in Proof", "Translator Note", "Conflict of Interest" should be captured element <notes> with attributes

like “note-in-proof”, “translator-note” or “conflict-of-interest”

Example Tagging

<notes notes-type="note-in-proof">

<p><italic>Note in Proof:</italic> These recommended practices were approved by IEEE Standards Board on June 14, 1984

and have been referred to the Manager of Standards Publications.</p></notes>



52. Supplementary Material

Supplementary content is appearing after the reference section in articles needs to be captured as Appendix. Please tag as

“Appendix 1- Supplementary Material”. In general if this material is an appendix, labels it an appendix. The way to map

this is the text “Appendix” goes into the <label> element and the authors text “Supplementary Material” goes into the

<title> elements as follows:

Example Tagging

<back>

<app-group>

<app id="app1">

<label>Appendix 1</label>

<title>Supplementary Material</title>

53. General Terms

Some terms are appearing before the Keyword section, Capture the data within a <kwd-group> as shown below. These

are essentially special kinds of keywords. Output them in HTML as normal keywords with the labels provided.

Example Tagging



<kwd-group kwd-group-type="Categories and Subject Descriptors">

<label>Categories and Subject Descriptors</label>

<compound-kwd><compound-kwd-part>C.3 [Special-Purpose and Application-Based Systems]</compound-kwd-part>

<compound-kwd-part>Real-time and embedded systems</compound-kwd-part></compound-kwd>

<compound-kwd><compound-kwd-part>B.3.2 [Design Styles]</compound-kwd-part>

<compound-kwd-part>Cache Memories</compound-kwd-part></compound-kwd>

<compound-kwd><compound-kwd-part>I.4.2 [Compression (Coding)]</compound-kwd-part>

<compound-kwd-part>Approximate Methods</compound-kwd-part>

</compound-kwd></kwd-group>

<kwd-group kwd-group-type="General Terms">

<label>General Terms</label>

<kwd>Algorithms</kwd><kwd>Design</kwd><kwd>Management</kwd></kwd-group>

54. Footnote in Article Title/Abstract

Funding/manuscript information is appearing as footnote and references are appearing either in Article Title or Abstract.

Need to capture the information both within the <funding-group> element as metadata and also within the <fn> tag, for

display purposes, like this:

Example Tagging

<title-group><article-title>Studying Group Behaviors<xref ref-type="fn" rid="fn0"><sup>*</sup></xref>

<fn fn-type="supported-by" id="fn0"><label><sup>*</sup></label><p>This research was supported in part by National

Science Foundation (NSF) under the Grants CNS-0831673 and CNS-0831853.</p></fn></article-title>

<funding-group><award-group id="grant1">

<funding-source>National Science Foundation (NSF)</funding-source>

<award-id>CNS-0831673</award-id><award-id>CNS-0831853</award-id>

</award-group><funding-statement>

<styled-content style="footnote">This research was supported in part by National Science Foundation (NSF) under the

Grants CNS-0831673 and CNS-0831853.</styled-content></funding-statement></funding-group>

55. Box Tagging

If the display equation appears in the box, we need to tag the same in Box and as an image in HTML

Example Tagging {\hbox{\vrule\vbox{\hrule\hbox{\hfil\kern6pt\vbox{\kern6pt\vfil \hbox{${\rm Overall Overlap} = {\rm Sum} (P_8 +

P_9 + \ldots P_{29} + P_{30})$} \kern6pt\vfil}\hfil\kern6pt}\hrule}\vrule}}\end

56. Linking

1. For external links like URLs or emails, need to use the element <uri>

2. The id values must be unique within an XML document. The values are [a-z][0-9] and "-" [hypen] character for

separating ranges. Other punctuation characters should not be used.

3. ID for footnotes must be in sequence in XML file as “fn1”, “fn2”….



4. DO NOT USE ATTRIBUTE “RID” in any element except <xref>

5. Use of the "other" ref-type: Only use the value "other" when the desired ref-type value is not in the IEEE DTD. Be

sure to use the "other" value with a sequential-numeric counter to ensure that these values are unique within an

XML article. Please inform IEEE when it's necessary to use this construct, as IEEE would like to add any necessary

values to the DTDs, as part of normal maintenance practices.

Link Type

ID/RID

Prefix ID/RID Example

Valid ref-type

AttributeValues Complete Example

affiliation aff rid="aff1" Aff <xref ref-type="aff" rid="aff1">

algorithm alg rid="alg1" Algorithm <xref ref-type="alg" rid="alg1">

appendix app rid="app1"

rid="app1A"

App <xref ref-type="app" rid="app1">

<xref ref-type="app" rid="app1A">

assumption assumption rid="assumption1" Assumption <xref ref-type="assumption" rid="assumption1">

author-notes author-notes rid="author-notes1" author-notes <xref ref-type="author-notes" rid="author-

notes1">

biography bio rid="bio1" Bio <xref ref-type="bio" rid="bio1">

contributor contrib rid="contrib1" Contrib. <xref ref-type="contrib" rid="contrib1">

correspondent corresp rid="corresp1" Corresp <xref ref-type="corresp" rid="corresp1">

corollary corollary rid="corollary1" Corollary <xref ref-type="corollary" rid="corollary1">

definition definition rid="definition1" Definition <xref ref-type="definition" rid="definition1">

def-list def-list rid="def-list1" def-list <xref ref-type="def-list" rid="def-list1">

display formula deqn rid="deqn1" disp-formula <xref ref-type="display-formula" rid="deqn1">

example example rid="example1" Example <xref ref-type="example" rid="example1">

figure fig rid="fig1" Fig <xref ref-type="fig" rid="fig1">

footnote fn rid="fn1" Fn <xref ref-type="fn" rid="fn1">

grant grant rid="grant1" Grant <xref ref-type="grant" rid="grant1">

graphic graphic rid="graphic1" Graphic <xref ref-type="graphic" rid="graphic1">

lemma lemma rid="lemma1" Lemma <xref ref-type="lemma" rid="lemma1">

list list rid="list1" List <xref ref-type="list" rid="list1">

other other rid="other1" Other <xref ref-type="other" rid="other1">

<xref ref-type="other" rid="other2">

<xref ref-type="other" rid="other3">

plate plate rid="plate1" Plate <xref ref-type="plate" rid="plate1">

proof proof rid="proof1" Proof <xref ref-type="proof" rid="proof1">

reference ref rid="ref1" Bibr <xref ref-type="bibr" rid="ref1">

Remark remark rid="remark1" Remark <xref ref-type="remark" rid="remark1">

scenario scenario rid="scenario1" Scenario <xref ref-type="scenario" rid="scenario1">

Scheme scheme rid="scheme1" Scheme <xref ref-type="scheme" rid="scheme1">

Section sec rid="sec1" or "sec1a"

or "sec1a1"

Sec <xref ref-type="sec" rid="sec1">

<xref ref-type="sec" rid="sec1a">

<xref ref-type="sec" rid="sec1a1">

Sidebar sidebar rid="sidebar1" boxed-text <xref ref-type="sidebar" rid="sidebar1">

statement statement rid="statement1" Statement <xref ref-type="statement" rid="statement1">



supplementary

material

supp-mat rid="supp-mat1" supplementary-

material

<xref ref-type="supp-mat" rid="supp-mat1">

Table table rid="table1" Table <xref ref-type="table" rid="table1">

table footnote table-fn rid="table-fn1" table-fn <xref ref-type="table-fn" rid="table-fn1">

theorem theorem rid="theorem1" Theorem <xref ref-type="theorem" rid="theorem1">

Linking Pattern for References

Case I: A simple range. If the print representation is: "[10],[11],[12],[13],[14],[15]", XML coding is: <xref ref-type="bibr" rid="ref10">[10]</xref>, <xref ref-type="bibr" rid="ref11">[11]</xref>, <xref ref-type="bibr" rid="ref12">[12]</xref>,

<xref ref-type="bibr" rid="ref13">[13]</xref>, <xref ref-type="bibr" rid="ref14">[14]</xref>, <xref ref-type="bibr" rid="ref15">[15]</xref>

Case II: A range with one skip. If the print representation is: "[10]-[13],[15]" , XML coding is: <xref ref-type="bibr" rid="ref10">[10]</xref>–<xref ref-type="bibr" rid="ref11"/><xref ref-type="bibr" rid="ref12"/><xref ref-

type="bibr" rid="ref13">[13]</xref>, <xref ref-type="bibr" rid="ref15">[15]</xref>

Case III: A range with one skip and a connector-word. If the print representation is: "[10]-[13] and [15]." XML coding is: <xref ref-type="bibr" rid="ref10">[10]</xref>–<xref ref-type="bibr" rid="ref11"/><xref ref-type="bibr" rid="ref12"/>

<xref ref-type="bibr" rid="ref13">[13]</xref> and <xref ref-type="bibr" rid="ref15">[15]</xref>.

Case IV: A simple range with only a connector-word. If the print representation is: "[11] through [15]", XML coding is: <xref ref-type="bibr" rid="ref11">[11]</xref><xref ref-type="bibr" rid="ref12"/><xref ref-type="bibr" rid="ref13"/><xref ref-type="bibr"

rid="ref14"/> through <xref ref-type="bibr" rid="ref15">[15]</xref>

Linking Pattern for Display Equations

Case I: Single display equation if the print respresentation is: (1) then the XML coding is: <xref ref-type=disp-formula" rid="deqn1">(1)</xref>

Case II: Multiple equations when they are in separate <disp-formula>'s. If the print representation is:

"(11),(12),(13),(14),(15)", XML coding is: <xref ref-type="disp-formula" rid="deqn11">(11)</xref>, <xref ref-type="disp-formula" rid="deqn12">(12)</xref>, <xref ref-type="disp-

formula" rid="deqn13">(13)</xref>, <xref ref-type="disp-formula" rid="deqn14">(14)</xref>, <xref ref-type="disp-formula"

rid="deqn15">(15)</xref>

Case III: Multiple equations when they are in separate <disp-formula>'s. If the print representation is: "(11)-(15)",

XML coding is: <xref ref-type="disp-formula" rid="deqn11">(11)</xref>–<xref ref-type="disp-formula" rid="deqn12"/><xref ref-type="disp-

formula" rid="deqn13"/><xref ref-type="disp-formula" rid="deqn14"/><xref ref-type="disp-formula" rid="deqn15">(15)</xref>

Case IV: A simple range when all equations are in one <disp-formula>. If the print representation is: "(10)-(15)", XML

coding is: <xref ref-type="disp-formula" rid="deqn10-15">(10) – (15)</xref>

Case V: A single numbered equation is within a block of multiple numbered equations in one <disp-formula>. Ie

equations (10)-(15) are in that single block and the print representation is: "(13)", XML coding is: <xref ref-type="disp-formula" rid="deqn10-15">(13)</xref>



Case VI: A range with one skip when all equations are in separate <disp-formula>'s If the print representation is:

"(10)-(13),(15)", XML coding is: <xref ref-type="disp-formula" rid="deqn10">(10)</xref>–<xref ref-type="disp-formula" rid="deqn11"/><xref ref-type="disp-

formula" rid="deqn12"/><xref ref-type="disp-formula" rid="deqn13">(13)</xref>, <xref ref-type="disp-formula" rid="deqn15">(15)</xref>

Case VII: A range with one skip and a connector-word when all equations are in separate <disp-formula>'s. If the print

representation is: "(10)-(13) and (15)." , then the XML coding is: <xref ref-type="disp-formula" rid="deqn10">(10)</xref>–<xref ref-type="disp-formula" rid="deqn11"/><xref ref-type="disp-

formula" rid="deqn12"/><xref ref-type="disp-formula" rid="deqn13">(13)</xref> and <xref ref-type="disp-formula"

rid="deqn15">(15)</xref>.

Case VIII: A simple range with only a connector-word when all equations are in one <disp-formula>. If the print

representation is: "(11) through (15)", XML coding is: <xref ref-type="disp-formula" rid="deqn11-15">(11) through (15)</xref>

Note: We do not need to generate the dummy links for other blocks like Figures, Tables

Linking Pattern for Footnotes

Case I: Simple numeric cross-reference <xref ref-type="fn" rid="fn1"/>

Case II: Asterisk in a cross-reference <xref ref-type="fn" rid="fn2"><sup>*</sup></xref>

Case III: Alpha-numeric cross-reference (rarely occurs) <xref ref-type="fn" rid="fn1a"/>

Important Notes

1. PDF file must be deleted in final package in XML folder

2. For external links, use element <uri>

3. Do not process Non Original Research articles

4. Do not process articles with Multimedia

5. Place the Non English article on hold

6. Do not use hexadecimal entity in Tex. SGML entity should only for <, > and &

7. Graphic Naming and calling. Match the graphics call outs with XML file

8. Needs to validate the Tex tagging against Vtex RULES

9. Ensure to run the XML QA tool and fix the log, if any