Copyright © 2002 Bruce Christensen, Peter Hutnick, Mark Miller
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no invariant sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”.
6 August 2005
Table of Contents
The XML Résumé Library is, at its heart, a DTD, a Document Type Definition. That means it is really someone's idea of how a résumé should, or at least could, be structured in XML. Beyond that, it comes with
Several XSLT style sheets (used to convert the XML version of a résumé to other formats such as plaintext, HTML, PDF, and if you're lucky, RTF).
A Java-based filter to help you target your résumé(s) toward a particular industry, employer, or job.
CSS stylesheets, used to control the presentation of the HTML version.
A helpful Makefile that you can customize
for your own purposes.
Table of Contents
This chapter explains how to install the XML Résumé Library, an Open Source, XML based résumé management system, on UNIX systems. It is written based on the author's experience installing on a Red Hat Linux system. Other systems may vary somewhat.
The resources in this document provide enough information to convert your XML résumé to HTML, PDF, and plain text. The programs to exploit these resources, however, are not included. Any capable XML parser, XSLT stylesheet processor and XSL formatting objects processor will get the job done. Many of the XML Résumé Library developers use the free tools produced by the Apache XML Project, and we recommend that you do as well. These tools include Xerces, Xalan, and FOP.
For the purposes of this document a functioning JRE (Java Runtime Environment) is a requirement. Obtaining and installing a JRE is outside the scope of this document. However, you might find Sun's J2SE web site a good starting point.
A minimal understanding of XML is an asset for using the XML Résumé Library. Most users find that they can get by following the examples in the absence of XML experience.
For a more in-depth tutorial on authoring a résumé in XML, see the section called “Writing your first XML Résumé”. For a reference on XML elements available in the XML Résumé Library DTD, see Element Reference.
The XML Résumé Library is available for download at http://sourceforge.net/project/showfiles.php?group_id=29512 and is linked from the main XML Résumé Library page at http://xmlresume.sourceforge.net/.
Xerces is an XML parser, which is needed by the tools used in later steps of processing. It converts an XML document into a format that other computer programs can more easily use.
The main Xerces for Java2 page is http://xml.apache.org/xerces2-j/, with the download page at http://xml.apache.org/dist/xerces2-j/.
Xalan does the actual conversion of a résumé from XML to other formats. When combined with the XSL stylesheets provided by the XML Résumé Library, it produces directly usable HTML and plain text. It also produces an intermediate format called XSL-FO (XSL Formatting Objects) that can be converted to PDF by an FO processor.
The Xalan-Java project page is http://xml.apache.org/xalan-j/, with downloads at http://xml.apache.org/dist/xalan-j/.
FOP is a print formatter for XSL formatting objects. It converts XSL-FO documents to PDF.
The main FOP page is http://xml.apache.org/fop/, and the download page is http://xml.apache.org/fop/download.html.
The XML Résumé Library comes in a tarball (or zip archive aimed at Windows users) that includes:
The DTD
XSL stylesheets, for converting your XML résumé to plain text, HTML, or XSL Formatting Objects (XSL-FO). (XSL-FO can then be rendered to PDF by an FO processor like FOP.)
Some sample résumés in XML format
A Makefile, for generating résumé formats with a simple make command
A few CSS stylesheets that can be used to fine-tune the appearance of the HTML version of your résumé.
The most straightforward way to make use of these resources is to recursively copy the "examples" directory to where you want to work with your résumé. For instance:
[resume-1_5_1]$ cp -a examples ~/resume
The Makefile uses the filename resume.xml by
default. If this is unacceptable you will need to edit the line
resume = resume to match the filename you use, such
as resume = myresume if your résumé is
myresume.xml.
You can also indicate your résumé filename on the command line when you build your résumé, e.g.:
[resume]$ make resume=myresume
The DTD and XSL files you've downloaded to your computer aren't used by default when building your résumé. Instead, the versions on the XML Résumé Library web site are used. This ensures that you're always using the most recent version; however, it also means that builds take longer (since file have to be downloaded each time you build your résumé) and that you can't build a résumé offline.
If you'd like to use your local copy of the XSL stylesheets, edit the
xsl_base variable in the example Makefile to point
to your local XSL directory. For example:
xsl_base = ~/resume-1_5_1/xsl
To use your local copy of the DTD, change the
DOCTYPE declaration at the top of your resume to
look like this:
<!DOCTYPE resume PUBLIC "-//Sean Kelly//DTD Resume 1.5.1//EN" "~/resume-1_5_1/dtd/resume.dtd">
Each of these three packages need to be untarred and their jar files
copied to your JRE's ext/
directory. This is typically /usr/java/jdk1.3.1_02/jre/lib/ext/, but may
vary depending on who packaged your JRE. We will simply refer to it as
the ext/ directory.
Xerces consists of the jars
xmlParserAPIs.jar,
xercesSamples.jar, and
xercesImpl.jar,
which are in the top directory of the Xerces zip archive.
Xalan consists of the jars
runtime.jar,
xalanservlet.jar,
xalansamples.jar,
regexp.jar,
JLex.jar,
java_cup.jar,
bsf.jar,
xml-apis.jar,
BCEL.jar,
xsltc.jar,
xalan.jar, and
xercesImpl.jar
in the bin/
directory. All of these need to be copied to the ext/ directory.
This chapter provides an overview of the features and usage of the XML Résumé Library, an Open Source, XML based résumé management system, on UNIX systems.
To get a feel for the power of the XML Résumé Library you should run
the example résumés through their paces and see how they turn
out after processing. You can do this by renaming the file
example2.xml
to resume.xml with the command mv
example2.xml resume.xml. Then simply issue the command
gmake while connected to the internet. This
should generate the files
resume.txt,
resume.html,
resume.fo, and
resume.pdf
— all versions of Alexis Kernighan's résumé.
Filtering allows you to maintain a single, complete resume.xml file that represents the entirety of your career/academic record, while allowing for the simple creation of targeted résumés. In other words, you can start to think of your XML Résumé as a database of your every skill, every accomplishment, every _____ without worrying about cluttering up the résumé your employer sees. Read on to find out how.
Consider the following snippet of Jane Doe's resume:
<skillset>
<skill>Carpentry</skill>
<skill>Welding</skill>
<skill>Java Programming</skill>
<skill>XML</skill>
<skill>C++</skill>
<skill>Good communicator</skill>
<skill>Gourmet Pastry Creation</skill>
<skill>Cooking for construction workers</skill>
</skillset>The problem here is that Jane needs to maintain a record of all her skills, but she doesn't need to tell a potential employer about all of those skills. Sure, Jane could selectively comment out portions of her résumé, but this can be tedious. Instead, she should use attributes to describe the categories of résumé to which a given element applies:
<skillset>
<skill targets="construction,woodworking">Carpentry</skill>
<skill targets="construction">Welding</skill>
<skill targets="programming">Java Programming</skill>
<skill targets="programming">XML</skill>
<skill targets="programming">C++</skill>
<skill>Good communicator</skill>
<skill targets="foodservice">Gourmet Pastry Creation</skill>
<skill targets="foodservice+construction">Cooking for construction workers</skill>
</skillset>After defining her targets, Jane can filter her résumé to produce beautifully-formatted, well-focused résumés to send to employers. Her "construction" résumé will contain only those elements applicable to the construction industry, and the job foreman won't have to read about her vast knowledge of meringues and bundt cakes, or her experience coding up an application server in Java.
You may have noticed that some of Jane's skills apply to more than one target, or apply only when two (or more) targets are defined. By specifying a list of targets (separated by commas), Jane can ensure that her Carpentry skill will be included in both "construction" and "woodworking" résumés. Similarly, her "Cooking for construction workers" skill will apply only to résumés where both "foodservice" AND "construction" are targeted.
Elements that have no "targets" attribute are always included in the filtered output. Thus Jane's communications skills will apply to every résumé.
The "targets" attribute can be used in ANY element, but keep in mind that using targets on a high-level element (e.g., history or academics element) will affect all children of that element. Thus if the history element includes a 'targets="foo"' attribute, and "foo" is not included in the targets list during the filtering process, then the entire history section will be filtered out, even if there are subelements of history that do not have the 'targets="foo"' attribute.
Now, keep in mind that defining targets is entirely up to you. You can use the targets attribute in any element, and you can specify any number of values for the target— just keep in mind that comma (,) and plus (+) represent OR and AND, respectively, as per the example above. If the list of possible targets starts to pile up, just look at the end of a filtered resume.xml file: a list of the possible and selected targets is included for convenience.
To get a better idea of how this all works, take a look at
examples/example2.xml. Trying making
the complete resume (with make all resume=example2),
and then the filtered version (make filter
resume=example2). Then compare
example2.txt with
example2-filtered.txt. To create résumés
targeted to other purposes, change filter_targets
in Makefile.
With just a few tweaks, you can dramatically change the look of your résumés.
The first thing to do to customize your resume is to
check out the parameters files. The main file is
xsl/params.xsl, which contains general
parameters that you can change. We suggest making a backup of
this file by issuing the command cp params.xsl
params.xsl.dist, and then playing around with the values
inside params.xsl to see how they affect
the formatting and output of your resumes.
You will need to change xsl_base in
Makefile to point to your local xsl directory
before any of your changes can take effect. Otherwise, the
default parameters stored on the XMLRésumé website are used
instead.
Located in the xsl/paper directory
are the a4.xsl and
letter.xsl files. These files specify
things like margin size and indent size for their respective
paper formats.
The xsl/country directory contains
country-specific parameter files, which contain translations for
everything from "Résumé" to "Mobile Telephone". If you would
prefer your résumé to be called a Curriculum Vitae, this is
where to look. The files are sorted by a 2-letter country code
(e.g., nl.xsl for the Netherlands). If you don't see your
country there, or if there are errors/omissions in the
translations, please attempt a translation and submit the
changes back to the project-- while XML may work across all
languages, the gentle developers of the XML Résumé Library Project
do not.
Cascading Style Sheets (CSS) are a powerful way to format the
look of your HTML Résumé. A selection of sample CSS files are
provided in the css
directory. If you have not already done so, try changing the value
of css.href in params.xsl
to a different stylesheet (you may have to adjust the location
of the stylesheets). Once you find one you like, you can tweak
it by editing the CSS file by hand, or create one that is
entirely your own. If you think other people would find your
CSS file useful, please consider submitting it back to the
project.
This is the fun part. Take a look at both example résumés and choose
one suits you best. Then replace the existing
information with your own. You may also be able to find example
résumés of real people by search for XML resume on
the internet.
For complete information on the elements valid for the XML Résumé Library see Element Reference.
More detailed information about creating and building résumés is available in other sections of this user guide.
For more information about the XML Résumé Library, see the HTML
documentation included in the doc/ directory.
For questions about the package and the DTD, there is a mailing list and a support forum web site.
The online support forum is located at http://sourceforge.net/tracker/?group_id=29512&atid=396336.
To join the mailing list, either visit http://lists.sourceforge.net/lists/listinfo/xmlresume-devel or send a message with
subscribe
in the
body to [youraddress@yourdomain.tld]<xmlresume-devel-request@lists.sourceforge.net>.
This chapter was originally written by Peter Hutnick. It was edited and converted to DocBook format by Bruce Christensen. Further editing and additions were done by Mark Miller
Please send comments, suggestions, and especially corrections for
this chapter to <peter at hutnick dot com>.
Table of Contents
XML Résumé files are XML files composed mostly of elements. This part of the user guide documents the semantics (meaning) and syntax (structure) of all of the elements that you can use to construct a résumé.
To get started with creating a résumé, take a look Chapter 2, Exploring the Features of XML Résumé Library, which is a tutorial on creating an XML
résumé. Alternatively, you could examine the content model for the resume
element, and drill down from there.
This sections documents changes to the XML Résumé Library DTD.
Deprecated elements will still be formatted, and are still valid elements in an XML résumé. However, their use is discouraged, and they will be removed in a future version of the DTD.
Changed elements:
date
can now be used in place of
period
in
membership
and
job.
Changed elements:
period
can be used in place of
date
in award and
clearance.
Changed element:
major
is no longer a required child of
degree.
Changed element:
The project
element now supports an optional
title
attribute.
New elements:
clearances and
clearance.
New element:
location.
It may be contained in
job,
degree,
or
membership.
Change:
institution and
organization
may now contain inline elements
(emphasis,
citation,
url, and
link).
New element: minor.
New element: lastModified.
New elements:
fax,
pager, and
instantMessage.
These may be contained in contact.
New attribute: the phone element now has a location attribute.
New attribute: the skill element now has a level attribute.
Change: the degree element may now contain
multiple major elements.
Change: the contact element may now contain any
number of its allowed child elements, and they may appear in any
order.
Change: the resume element may now directly
containskillarea elements.
Change: the skillset element may now directly
contain skill elements.
Change: the degree element may now contain either
a
period or a
date element. It could previously
contain only a
date.
Change: the artTitle and
The bookTitle elements may now contain
link elements.
Change: the referee element may now contain an
optional
title element and an optional
organization element.
Change: the month element is no longer required
in the
date element.
(However, it must appear if the date contains a
dayOfMonth element.)
Deprecated element: skillareas.
You may simply remove the start and end tags from your résumé.
Deprecated element: skills.
You may simply remove the start and end tags from your résumé.
Deprecated element: pubDate.
Replace it with a date element.
Deprecated elements: docpath,
head,
node,
tail,
label, and
uri.
Instances of these elements should be removed.
New element: link.
New attribute: the address element now has an optional
format attribute.
New attributes: Added namespace support. More specifically, added
xmlns, xmlns:xsi, and xsi:schemaLocation attributes to the resumes and resume elements.
Change: employer may now contain inline
elements
(emphasis,
citation,
url, and
link).
Deprecated element: break. Instances of this element
should be removed.
Deprecated element: company. Instances of this element
should be removed.
Deprecated element: street2. These elements should be
converted to street elements.
Table of Contents
academics — Container for information about academic experience
<academics>
<degrees>
<degree>
<level>Ph.D</level>
<major>Toothpick Manufacturing</major>
<institution>Stanford University</institution>
</degree>
</degrees>
<note>
<para>
I also have an honorary doctorate in toothpick structural analysis from
MIT.
</para>
</note>
</academics><academics>
<degrees>
<degree>
<level>BA</level>
<major>Culinary Psychology</major>
</degree>
</degrees>
</academics>achievement — An accomplishment made at a job
The achievment element contains a
single accomplishment made while working at a particular job (e.g.
“increased sales by 20%”, or “improved employee
efficiency”).
<job>
<jobtitle>Eggroll Engineer</jobtitle>
<employer>Chineese Cuisine Systems, Inc.</employer>
<period>
<from>
<date>
<month>August</month>
<year>1993</year>
</date>
</from>
<to>
<present/>
</to>
</period>
<achievements>
<achievement>
Wrote an <emphasis>excellent</emphasis> article on shell crispiness for
the <citation>European Journal of Egg Food Engineering</citation>,
published at <url>http://www.ejeps.org/articles/crispiness.html</url>.
</achievement>
<achievement>
Decreased filling greasiness by a <emphasis>whopping</emphasis> 30%!
</achievement>
</achievements>
</job>achievements — Container for one or more job achievements
achievements is a wrapper element
that contains one or more achievement elements. Achievements are
specific things that were accomplished at a job.
address — A postal address
The address element defines a single
postal address. It does not contain
information about a person who resides at the address.
Different countries have different address formatting conventions.
Address formatting is controlled by the address.format
parameter.
If an address cannot be specified using address's child elements (street, city, etc.), it may be specified in untagged
format. In this case, the address will be formatted verbatim, with line
breaks preserved.
idA string used to uniquely identify an address. The address may then be referred to by this identifier.
format
The address format. This attribute specifies the format of an
address, and overrides the global address.format
parameter for each address that it appears in.
Example 1. U.S.-style address
<address> <street>123 Pickle St.</street> <street>Apt. #12</street> <city>Sourville</city> <state>NX</state> <zip>99999-9999</zip> </address>
Formatted as:
123 Pickle St. Apt. #12
Sourville, NX 99999-9999
Example 2. Italian address
<address> <street>Via Garibaldi, 23</street> <city>Sorrento</city> <postalCode>123 456</postalCode> <province>NA</province> <country>Italy</country> </address>
Example 3. Untagged address
<address>Reina #35, apt. 4a, e/ Gervasio y Escobar Ciudad de La Habana, CP 11900 CUBA</address>
Formatted as:
Reina #35, apt. 4a, e/ Gervasio y Escobar
Ciudad de La Habana, CP 11900
CUBA
You may have noticed that the XML for this address isn't indented as usual. This is because untagged addresses are formatted verbatim, and so any indentation would be preserved in the formatted address. The address text begins on the same line as the start tag for the same reason (we don't want a leading linebreak in the formatted address).
For additional address examples, look at the XML files in the examples/addressing directory of the
XML Résumé Library distribution.
annotation — Additional information about a degree
artTitle — A title of an article or other work
The artTitle element marks the title
of a sub-work (such as an article or poem) in a book, journal, magazine,
newspaper, anthology, or other compilation.
<pub> <artTitle>Lion Brainwashing During the Late 20th Century</artTitle> <bookTitle>Journal of the American Feline Psychiatric Association</bookTitle> </pub>
<pub> <artTitle>Cucumber Pickling Process Management</artTitle> <bookTitle>Proceedings of the European Brine Process Engineers' Group</bookTitle> </pub>
author — An author of a publication
The author element contains the name
of an author of a work or publication. It may also reference a
previously-defined name through its name attribute. In this case, the element will
be processed and displayed as if it were actually the referenced name.
name
The name attribute contains
the id of a name element.
If an author element
specifies this attribute, it should not have any content. In
other words, there should be a single tag with a reference
(<author name="joe.smith"/>)
instead of two tags enclosing content
(<author>Joe Smith</author>).
<pub> <bookTitle>Nuclear Engineering for Dummies</bookTitle> <author>Edgar Neutron</author> </pub>
<name id="shirly.mendoza"> <firstname>Shirly</firstname> <surname>Mendoza</surname> </name> <pub> <artTitle>Cooking Wire-Core Pretzels</artTitle> <author name="shirly.mendoza"/> <bookTitle>Journal of Metal-Reinforced Confections</bookTitle> </pub>
award — An award or other honor
awards — Container for one or more awards
<awards>
<title>Awards and Honors</title>
<award>
<title>Employee of the Month</title>
<organization>ACME, Inc.</organization>
<date><month>May</month><year>2002</year></date>
<description>
<para>
Received for <emphasis>exceptional</emphasis> customer service.
</para>
</description>
</award>
<award>
<title>AP Scholar</title>
<organization>College Board</organization>
<date><year>2002</year></date>
</award>
</awards>birth — Container for information about a person's birth
<header>
<name>
<firstname>Scotty</firstname>
<surname>O'Reilly</surname>
</name>
<birth>
<date>
<dayOfMonth>17</dayOfMonth>
<month>March</month>
<year>1931</year>
</date>
</birth>
</header><header>
<name>
<firstname>Josè</firstname>
<middlenames>Luis Miguel</middlenames>
<surname>Domingo</surname>
</name>
<birth>
<date>
<dayOfMonth>23</dayOfMonth>
<month>Mayo</month>
<year>1834</year>
</date>
</birth>
</header>bookTitle — A title of a book or similar work
The bookTitle element marks the title
of a book, magazine, journal, anthology, or other similar work. To
denote the title of a sub-work (like an article), see artTitle.
<pub> <bookTitle>Tropical Siberian Vacations</bookTitle> <author>Boris Tzchleikovsy</author> </pub>
<pub> <bookTitle>Children's Bedtime Stories</bookTitle> <artTitle>Jack the Axe Murderer</artTitle> <author>Caroline Black</author> </pub>
<pub>
<artTitle>Global Commodities Market Downturn</artTitle>
<bookTitle>The Economist</bookTitle>
<pubDate>
<month>June</month>
<year>1992</year>
</pubdate>
</pub>break — A linebreak
Deprecated
This element is deprecated as of XML Résumé Library version 1.3.3. It should not be used.
break was introduced to allow
linebreaks in free-form addresses, but the stylesheets have been
modified so that they don't need an explicit linebreak marker. Instead,
linebreaks in source text are formatted as linebreaks in formatted text.
The break element indicates a
position in text where a linebreak should occur.
citation — The name of a work being referenced
The citation element marks the title
of a book, website, course, or other work.
citation may be contained in these
elements:
achievement, employer, institution, organization, para, project, skill
<achievement> Increased earnings 341%, thereby landing Acme Widgets on <citation>Fortune Magazine</citation>'s Fortune 500 list. </achievement>
<para> More information on the AHTM system is published in <citation>Developing Today</citation> at <url>http://www.dtoday.bob/tips.html</url>. </para>
city — The name of a city
clearance — A security clearance
clearances — One or more security clearances
company — The name of a company
Deprecated
contact — Container for one or more methods of contacting someone
copyright — A copyright notice
The copyright element defines a
copyright notice. The notice must include the year of copyright; it may
also include the name of the copyright owner and a legal notice.
<resume>
<copyright>
<year>1892</year>
<name>
<firstname>Fluisha</firstname>
<surname>Copenhagen</surname>
</name>
<legalnotice>
<para>
All rights reserved. This document may not be copied or distributed
without permission.
</para>
</legalnotice>
</copyright>
</resume><copyright> <year>2001</year> </copyright>
county — A county name
The county element specifies the name
of a county (not to be confused with country). In the United States, a
county is “an administrative subdivision of a state”. In
the UK, it is a “territorial division exercising administrative,
judicial, and political functions.” (Source: The American Heritage Dictionary of the English
Language, 1979 Ed. Houghton Mifflin, Boston.)
date — A specific instant in time
The date element represents a
specific instant in time, with at least year-level granularity, and at
most day-level granularity.
When contained inside a pub element, date represents the date that the work was
published.
When contained inside a clearance element, date represents the date that the security
clearance was granted.
The month element was made optional
in version 1.4.0 of the XML Résumé Library. It was previously required.
To represent a period of time, instead of a specific instant, use period.
date may be contained in these
elements:
award, birth, clearance, degree, from, job, lastModified, membership, pub, to
dayOfMonth — An ordinal day of the month
degree — Container for information about a degree or similar certification
The degree element is a container for
information about an academic degree (Bachelor of Science, Doctor of
Psychology, etc.) or other similar certification.
<degree> <level>Ph.D</level> <major>Microbiology</major> <annotation>Thesis on effect of hot dogs on canine amino acids</annotation> </degree>
<degree>
<level>BA</level>
<major>Toilet Paper Pattern Design</major>
<date>
<month>June</month>
<year>1745</year>
</date>
<institution>British Design Academy</institution>
<annotation>
On dean's list for duration of studies.
</annotation>
</degree><degree>
<level>BS</level>
<major>Computer Science</major>
<major>English</major>
<minor>Graphic Design</minor>
<minor>Geography</minor>
<subjects>
<subject>
<title>Compilers</title>
<result>A-</result>
</subject>
<subject>
<title>Data Structures</title>
<result>B</result>
</subject>
<subject>
<title>Classic Literature</title>
<result>A</result>
</subject>
</subjects>
</degree>degrees — Container for one or more degrees
description — An explanation of something
The description element specifies a
person's role, their activities, or other descriptive information.
<job>
<jobtitle>Supersonic Vacuum Technician</jobtitle>
<employer>Joe's Vacuum Shop</employer>
<period>
<from><date><month>June</month><year>2344</year></date></from>
<to><present/></to>
</period>
<description>
Repaired hyperdynamic microbial particle accelerators in Supersonic vacuum
models XL144 and XP2000.
</description>
</job><membership>
<title>Treasurer</title>
<organization>Mars Vacuum Repair Association</organization>
<description>
Kept books and collected membership dues.
</description>
</job>docpath —
Deprecated
emphasis — An emphasized block of text
The emphasis element is an inline
element that indicates that the text it contains should be emphasized.
The presentation of text contained in this element varies depending on the output format.
Rendered as bold (using the <strong> tag) by default.
Presentation may be overridden by creating or modifying a CSS
stylesheet that formats the emphasis class.
Text is surrounded in *astrisks* by default. May be overridden
by specifying the text.emphasis.start
and text.emphasis.end parameters when
processing the résumé with an XSLT processor like
Xalan or
Saxon.
Rendered as bold text.
emphasis may be contained in these
elements:
achievement, employer, institution, organization, para, project, skill
employer — A name of an employer
The employer element specifies the
name of a person, company, or other entity for whom a person works or
has worked.
<job>
<jobtitle>Angelfish Fitness Trainer</jobtitle>
<employer>Fish Fitness Systems, Inc.</employer>
<period>
<from><date><month>July</month><year>1998</year></date</from>
<to><present/></to>
</period>
<description>
<para>
Helped to ensure optimum fish health by training fish on weights and
and fin and tail exercises.
</para>
</description>
</job><job>
<jobtitle>House Cleaner</jobtitle>
<employer>Mrs. Shirlock</employer>
<period>
<from><date><month>July</month><year>1954</year></date</from>
<to><date><month>January</month><year>1956</year></date</to>
</period>
<para>Dusted the blinds. That is all.</para>
</job>fax — A fax telephone number
The fax element contains a
telephone number that can be used to connect to a facsimile machine. The
phone number is not required to be in a specific format. (See phone
for examples of numbers.)
firstname — A person's given name
from — The beginning point in a period of time
gpa — Information about a grade point average
head —
Deprecated
header — Container for information about the person being described in a résumé
The header element is a container for
information typically contained in the header at the top of a résumé.
This includes biographic and contact information about the person who
the résumé describes.
<header>
<name>
<firstname>Hector</firstname>
<surname>Gomez</surname>
</name>
<address>
<street>245 San Bernadino</street>
<city>Los Gatos</city>
<state>LX</state>
<zip>94262</zip>
</address>
<birth>
<date>
<dayOfMonth>30</dayOfMonth>
<month>April</month>
<year>1942</year>
</date>
</birth>
<contact>
<phone>555-1212</phone>
<email>hector.gomez@xyz.bob</email>
</contact>
</header>history — Container for a person's previous (and possibly current) jobs
The history element contains a
person's job history (the jobs that they have worked at in the past). It
is also common to include their current job in this element.
<history>
<job>
<jobtitle>Counselor</jobtitle>
<employer>Shrink Inc.</employer>
<period>
<from><date><month>August</month><year>1490</year></date></from>
<to><date><month>January</month><year>1497</year></date></to>
</period>
<description>
<para>
Counseled King Ferdinand and Queen Isabella. Helped to calm their fears
about their large investment in a man named Christopher Columbus.
</para>
<para>
When Columbus returned with gold, I was "downsized" by beheading.
</para>
</description>
</job>
<job>
<jobtitle>Angel</jobtitle>
<employer>Heaven</employer>
<period>
<from><date><month>January</month><year>1497</year></date></from>
<to><date><month>June</month><year>2344</year></date></to>
</period>
<description>
<para>
Saved souls.
</para>
</description>
</job>
<job>
<jobtitle>Supersonic Vacuum Technician</jobtitle>
<employer>Joe's Vacuum Shop</employer>
<period>
<from><date><month>June</month><year>2344</year></date></from>
<to><present/></to>
</period>
<description>
<para>
Allowed to return to earth to help my great-great-great-(you get the
picture)-grandson Joe with his business.
</para>
<para>
Repaired hyperdynamic microbial neutron particle accelerators in
Supersonic vacuum models XL144 and XP2000.
</para>
</description>
</job>
</history>instantMessage — An instant message username or address
institution — A name of an academic institution
interest — Something a person is interested in
The interest element describes
something that a person is interested in. A common use for interest elements is to list hobbies.
The formatting of interest is more
complex than that of many other elements. The title is always displayed
first, in standard font. Then, if there is a description, and the
interest.description.format parameter value is
single-line, a period and a space
(“. ”) are displayed. Finally, the description is
output, formatted according to the interest.description.format parameter.
<interest> <title>Sewing</title> </interest>
<interest>
<title>Seattle Mariners</title>
<description>
<para>I'm a season ticket holder.</para>
<para><emphasis>GO MARINERS!</emphasis></para>
</description>
</interest>
For additional examples, see interests.
interests — Container for one or more interests
The interests element contains one or
more interest elements.
<interests>
<title>Hobbies</title>
<interest>
<title>Swimming</title>
</interest>
<interest>
<title>Fine foods</title>
<description>
<para>I do quite well in pie-eating contests.</para>
</description>
</interest>
<interest>
<title>Australia</title>
</interest>
</interests><interests>
<interest>
<title>My belly button</title>
</interest>
<interest>
<title>Fire ants</title>
</interest>
<interest>
<title>Fertilizer</title>
</interest>
</interests>job — A specific employment engagement
<job>
<jobtitle>Sr. VP of Soap Suds Engineering</jobtitle>
<employer>Proctor and Gamble</employer>
<period>
<from><date>
<month>May</month>
<year>1982</year>
</date></from>
<to><date>
<month>June</month>
<year>1988</year>
</date></to>
</period>
</job><job>
<jobtitle>Dirt</jobtitle>
<employer>Earth</employer>
<period>
<from><date>
<month>Januaray</month>
<year>30,000 B.C.</year>
</date></from>
<to><present/></to>
</period>
<description>
Provided nutrients, absorbed water, and got tracked into houses.
</description>
<achievements>
<achievement>
Grew a 300-ft. tree.
</achievement>
</achievements>
<projects>
<project>
Took part in the construction of the construction of the Empire State
Building in New York City. (Was excavated from its basement.)
</project>
</projects>
</job>jobtitle — A job title
keyword — A keyword to be used for résumé indexing and searching
keywords — Container for a list of keywords
label —
Deprecated
lastModified — Information about when a résumé was last modified
legalnotice — A legal statement
level — A degree type
The semantic of the title element
vary depending on which element contains it:
clearance
When contained in this element, the level element specifies the level of
security clearance that a person has been granted, such as
“Top Secret” or “Restricted”.
degree
When contained in this element, the level element specifies a degree type,
such as “BFA” (bachelor of fine arts) or
“Ph.D” (doctor of philosophy). It typically contains
the abbreviation (“BS”) not the full spelling
(“bachelor of science”).
link — A titled hyperlink
The link element defines a single
hyperlink, much like HTML's a (anchor)
element.
In FO/PDF and plain text output formats, the text contained in the
link element is formatted as if the
surrounding link tags were not
present. The href attribute is
ignored.
In the HTML output format, the link
element is formatted as an a (anchor)
hyperlink.
link may be contained in these
elements:
achievement, artTitle, bookTitle, employer, institution, organization, para, project, publisher, skill
location — A location, with city-level granularity
major — A main course of study
membership — A professional membership
memberships — Container for one or more memberships
<memberships>
<title>Professional Memberships</title>
<membership>
<organization>Foobar State Technology Association</organization>
</membership>
<membership>
<title>President</title>
<organization>Smallville Internet Developers' Group</organization>
<period>
<from><date>
<month>September</month>
<year>1998</year>
</date></from>
<to><present/></to>
</period>
<description>
<para>
Founded group and guided its growth from 4 to 150 members.
</para>
</description>
</membership>
</memberships>middlenames — One or more “middle” names of a person
minor — A minor course of study
misc — Miscellaneous remarks
The misc element contains paragraphs
of text that don't fit into any other top-level categories.
<misc>
<para>What can't be captured on a résumé is my sheer
level of <emphasis>enthusiasm</emphasis> for not just cooking
food, but dealing with people. I'm told I make nearly every
kitchen run more smoothly because I know how to manage and make
people want to <emphasis>do their best</emphasis>.
</para>
<para>I'm listed in <citation>Who's Who in American
Restaurants</citation> as well as <citation>La
Rubachòn</citation>.
</para>
</misc>month — A month name
name — A person's name
<name> <title>Mr.</title> <firstname>John</firstname> <middlenames>Q.</middlenames> <surname>Doe</surname> </name>
<name> <firstname>Joe</firstname> <middlenames>Sam George Bob</middlenames> <surname>Flamboyzo</surname> <suffix>Jr.</suffix> </name>
<name> <firstname>King</firstname> <surname>Louis</surname> <suffix>VIII</suffix> </name>
node —
Deprecated
note — Additional information
objective — A person's employment goal
organization — A name of an organization
pageNums — One or more page numbers or ranges
pager — A pager telephone number
The pager element contains a
telephone number that can be used to connect to a pager. The phone number
is not required to be in a specific format. (See phone
for examples of numbers.)
para — A paragraph of text
The para element contains a single
paragraph of text. Its contents are not preserved verbatim; instead, it
is treated much like HTML. Multiple whitespace characters (including
spaces and tabs) are compressed into a single space, and linebreaks are
treated as space characters instead of newlines. This allows flexibility
in formatting XML source code.
Paragraphs may contain basic markup to indicate emphasis, URLs, and citations.
para may be contained in these
elements:
description, legalnotice, misc, note, objective, pub
<para> This is a boring paragraph. </para>
<para> I like to <emphasis>emphasize</emphasize> my words; in fact, I've written an article on the topic. It is published on the <emphasis><citation>Really Exciting WRITING!</citation></emphasis> web site at <url>http://www.really-exciting-writing.bob/EMPHASIS.html</url>. </para>
period — A period of time
The period element defines a specific
period in time by specifying the period's start time and end time.
If you want to specify an instant in time instead of a period, use
date.
<period>
<from><date>
<dayOfMonth>10</dayOfMonth>
<month>February</month>
<year>1246</year>
</date></from>
<to><date>
<dayOfMonth>19</dayOfMonth>
<month>November</month>
<year>1351</year>
</date></to>
</period><period>
<from><date>
<month>May</month>
<year>1985</year>
</date></from>
<to>
<present/>
</to>
</period>phone — A voice telephone number
The phone element contains a
telephone number. The number is not required to be in a specific format;
these are all valid phone numbers:
555-555-1212
555.555.1212
(555) 555-1212
(555) 555-1212 x555
(011) 47 8931-858128
(011) 59-3331-8580
<phone>555.555.1212</phone>
<phone location="mobile">345-262-4567</phone>
<phone location="home">(261) 345-1616</phone>
For additional examples, see contact.
possible — The highest possible score in a GPA
postalCode — A postal code
The postalCode element contains an
alphanumeric string used by postal services to route mail to its
destination.
For postal codes in the United States, use zip.
prefecture — A name of a prefecture or other administrative district
present — Indicates the current time
The present element denotes the
current time, as opposed to a fixed time in the past or future. It is
most commonly used in date ranges, to express things like “From
May 1995 to present”.
present is a null element, that is,
it has no content or attributes. It is always written as
<present/>.
project — Container for information about a project
projects — Container for one or more projects
province — A name or abbreviation of a province
pub — A work published by the résumé “owner”
The pub element contains elements
that describe a work (like an article, a book, a poem, or a scholarly
paper) that was published by the person the résumé describes.
pubDate — The date a work was published
Deprecated
This element is deprecated as of XML Résumé Library version 1.4.0. It should not be used.
date elements should be used instead
of pubDate elements.
The pubDate element indicates when a
literary, scholarly, or other work was published. It must contain a
year, and may contain a month.
publisher — Information about a publisher of a work
The use of the url element as a child
of publisher is deprecated as of
XML Résumé Library version 1.4.0.
We recommend that you convert all urls contained in publishers to links.
The publisher element contains
the name, and possibly location, of the organization that published a
literary, artistic, scholary, or other work.
pubs — A group of one or more publications
referee — Someone who can provide additional information about the person the résumé describes
The referee element contains the name
and contact information information of a person who knows the job
seeker (the person that the résumé describes). Referees (also called
references) can provide additional information about the job seeker.
They often supply background information, confirm facts, and describe
the job seeker's character.
<referee>
<name>Joe</name>
<address>
<street>123 Main St.</street>
<city>Anytown</city>
<state>ST</state>
<zip>12345</zip>
<country>USA</country>
</address>
<contact>
<phone>123.456.7890</phone>
<email>joe@hotmail.bob</email>
</contact>
</referee>
For additional examples, see referees.
referees — Contains one or more referees
result — An outcome of a subject
The result element describes the
outcome or result of a subject. result often contains the letter or numeric
grade awarded for an academic class.
resume — A résumé or curriculum vitae
(docpath?,header?,((objective|history|academics|skillareas|skillarea|pubs|misc|referees|keywords|memberships|interests|clearances|awards))*,lastModified?,copyright?)
The resume element represents a
single résumé or curriculum vitae (CV). It is a summary of a person's
experience that is revelant to employment.
<resume id="a8df262">
<header>
<name id="harry.potter">
<firstname>Harry</firstname>
<surname>Potter</surname>
</name>
<address>
<street>4 Privet Drive</street>
<city>Little Whinging</city>
<county>Surrey</county>
<postalCode>RO51 5NF</postalCode>
<country>UK</country>
</address>
</header>
<objective>
<para>To defeat Lord Voldemort once and for all, then to become an Auror
for the Ministry of Magic.</para>
</objective>
<skillarea>
<title>Magical Skills</title>
<skillset>
<title>Charms</title>
<skill>Levitation</skill>
<skill>Cheering</skill>
<skill>Summoning</skill>
<skill>Banishing</skill>
</skillset>
<skillset>
<title>Spells and Curses</title>
<skill>Unlocking Spell</skill>
<skill>Patronus Spell</skill>
<skill>Stunning Spell</skill>
<skill>Disarming Spell</skill>
<skill>Reductor Curse</skill>
<skill>Impediment Curse</skill>
<skill>Imperious Curse Evasion</skill>
</skillset>
<skillset>
<title>Potions</title>
<skill>Polyjuice</skill>
<skill>Enlarging</skill>
<skill>Antidotes</skill>
</skillset>
<skillset>
<title>Flying</title>
<skill>High-speed</skill>
<skill>Wronski Feint</skill>
<skill>Steep dives</skill>
<skill>Bludger Evasion</skill>
<skill>No-hands</skill>
<skill>High-altitude</skill>
</skillset>
<skillset>
<title>Languages</title>
<skill>English</skill>
<skill>Parsel Tounge</skill>
<skill>Troll (point and grunt)</skill>
</skillset>
</skillarea>
<skillarea>
<title>Muggle Skills</title>
<skillset>
<title>Daily Life</title>
<skill>Telephone</skill>
<skill>Mailbox</skill>
<skill>Riding in cars</skill>
<skill>Electric lights</skill>
<skill>Hammering</skill>
</skillset>
<skillset>
<title>Camping</title>
<skill>Setting up tents</skill>
<skill>Lighting Matches</skill>
</skillset>
</skillarea>
<history>
<job>
<jobtitle>Student</jobtitle>
<employer>Hogwarts</employer>
<period>
<from>
<date>
<month>September</month>
<year>ca. 1995</year>
</date>
</from>
<to>
<present/>
</to>
</period>
<achievements>
<achievement>
On Gryffindor House Quidditch team four years running
</achievement>
<achievement>
Quidditch Cup
</achievement>
<achievement>Youngest Seeker in a century</achievement>
<achievement>
Faced Lord Voldemort four times and lived.
</achievement>
</achievements>
</job>
<job>
<jobtitle>De-gnomer</jobtitle>
<employer>Mrs. Weasley</employer>
<period>
<from>
<date>
<month>August</month>
<year>ca. 1995</year>
</date>
</from>
<to>
<date>
<month>August</month>
<year>ca. 1995</year>
</date>
</to>
</period>
<description>
<para>Removed gnomes from the Weasleys' garden.</para>
</description>
</job>
</history>
<academics>
<degrees>
<degree>
<level>Fourth Year</level>
<major>Wizarding</major>
<institution>Hogwards School of Witchcraft and Wizardry</institution>
<subjects>
<subject>
<title>Transfiguration</title>
<result>B</result>
</subject>
<subject>
<title>Charms</title>
<result>A-</result>
</subject>
<subject>
<title>Defense Against the Dark Arts</title>
<result>A</result>
</subject>
<subject>
<title>Potions</title>
<result>D</result>
</subject>
<subject>
<title>Care of Magical Creature</title>
<result>A+</result>
</subject>
<subject>
<title>Divination</title>
<result>B</result>
</subject>
</subjects>
</degree>
</degrees>
</academics>
<memberships>
<title>School Clubs</title>
<membership>
<organization>Dueling Club</organization>
<description><para>Trained in wizard dueling, with focus on
disarming.</para></description>
</membership>
<membership>
<title>Secretary</title>
<organization>Society for the Protection of Elfish Workers
(S.P.E.W.)</organization>
</membership>
</memberships>
<interests>
<interest><title>Cho Chang</title></interest>
</interests>
<referees>
<referee>
<name>
<firstname>Minerva</firstname>
<surname>McGonagall</surname>
</name>
<address>Hogwarts School of Witchcraft and Wizardry
Via Owl Post</address>
</referee>
<referee>
<name>
<firstname>Albus</firstname>
<surname>Dumbledore</surname>
</name>
<address>Hogwarts School of Witchcraft and Wizardry
Via Owl Post</address>
</referee>
</referees>
</resume>
For additional examples, look at the sample résumés in the examples directory of the XML Résumé Library
distribution.
resumes — A collection of one or more résumés
The resumes element contains one or
more résumés. It could be used,
for example, to distribute the résumés of all applicants for a job as
a single file.
The formatting of this element is currently undefined.
<resumes id="resumes.tech.titans">
<resume id="resume.gates">
<header>
<name>
<firstname>Bill</firstname>
<surname>Gates</surname>
</name>
</header>
</resume>
<resume id="resume.jobs">
<header>
<name>
<firstname>Steve</firstname>
<surname>Jobs</surname>
</name>
</header>
</resume>
</resumes>score — The score earned in a GPA
skill — A name and/or description of a skill
The skill element describes something
that a person is skilled at.
level
The level attribute indicates
a person's level of proficiency at a skill. “Level of
proficiency” may be expressed in any manner, such as
“3 years” (three years of experience with a
particular skill), “expert”, or “7/10”.
The skills.level.display parameter
determines whether or not skill levels are displayed in formatted
output.
skillarea — A group of broadly related skill sets
The skillarea element contains one or
more skillsets. Usually the skill sets it
contains are related to each other, at least in a general sense.
For example, a “Computer Skills” skill area may contain skillsets titled “Programming”, “Office Programs”, and “Hardware”.
It is quite common for a résumé to contain only one skill area.
Example 8. Broad skill area
<skillarea>
<title>Skills</title>
<skillset>
<title>Computers</title>
<skill>Typing (<emphasis>150 WPM!!</emphasis>)</skill>
<skill>Dropping little food crumbs in keyboards</skill>
</skillset>
<skillset>
<title>Writing</title>
<skill>Editing</skill>
<skill>Cursive</skill>
</skillset>
</skillarea>Example 9. More focused skill area
<skillarea>
<title>Financial Skills</title>
<skillset>
<title>Investing</title>
<skill>Stocks</skill>
<skill>Bonds</skill>
<skill>Money market accounts</skill>
<skill>Retirement accounts</skill>
</skillset>
<skillset>
<title>Bookkeeping</title>
<skill>Amortization</skill>
<skill>Loan schedules</skill>
<skill>Book balancing</skill>
</skillset>
<skillset>
<title>Advising</title>
<skill>Retirement investment</skill>
<skill>College investment</skill>
<skill>Philanthropy</skill>
</skillset>
</skillarea>skillareas — Group of one or more skill areas
Deprecated
This element is deprecated as of XML Résumé Library version 1.4.0. It should not be used.
skillarea elements are now allowed as
direct children of resume, so
skillareas is no longer necessary.
skillareas is still allowed in this
release of XML Résumé Library, but may be removed in future versions. It is
recommended that you remove all skillareas elements from XML résumés.
The skillareas element contains one
or more skillareas.
This element is a top-level section of a résumé.
<skillareas>
<skillarea>
<title>Aviation</title>
<skillset>
<title>Piloting</title>
<skill>Biplanes</skill>
<skill>Jumbo Jets</skill>
<skill>Space Shuttle</skill>
</skillset>
<skillset>
<title>Navigation</title>
<skill>Map and charts</skill>
<skill>Instruments</skill>
<skill>Stars</skill>
</skillset>
</skillarea>
<skillarea>
<title>Cleaning</title>
<skillset>
<title>Tools</title>
<skill>Rag</skill>
<skill>Sponge</skill>
<skill>Towel</skill>
</skillset>
<skillset>
<title>Chemicals</title>
<skill>Bleach</skill>
<skill>Water</skill>
<skill>Soap</skill>
</skillset>
</skillarea>
</skillareas>skills — Group of one or more skills
Deprecated
This element is deprecated as of XML Résumé Library version 1.4.0. It should not be used.
skill elements are now allowed as
direct children of skillset, so
skills is no longer necessary.
skills is still allowed in this
release of XML Résumé Library, but may be removed in future versions. It is
recommended that you remove all skills elements from XML résumés.
The skills element contains one or
more (usually related) skills.
skillset — A titled group of one or more related skills
state — A name or abbreviation of a state
street — A street name, number, and other related information
street2 — A second line of a street address
Deprecated
This element is deprecated as of XML Résumé Library version 1.3.3. It should not be used.
Because multiple street elements are now allowed,
street2 is unneeded. street2 is still supported in this release of
the XML Résumé Library, but may be removed in future versions. It is
recommended that all street2 elements
be converted to street elements.
The street2 element is similar in
semantics to the street element. It often contains more
specialized routing information than street, such as a suite or apartment number.
subject — A name of a class or topic of study
The subject element contains the
title of a class or other course of
study, as well as its result.
A subject's title can be as general as “mathematics” (a general field of study), or as specific as “ECEn 224 Electrostatics Fall 1994” (a specific university class, along with the date the class was taken).
subjects — A group of one or more subjects
suburb — A name of a suburb
suffix — A suffix of a name, usually specifying lineage
surname — A family name
tail —
Deprecated
title — A title or heading
The title element contains a title or
heading. Its semantics vary depending on the element that contains it:
name
When contained in this element, title contains a person's formal title,
such as “Dr.”, “Ms.”, or
“Professor”.
interest
When contained in this element, title contains the name of an interest,
such as “Cooking”, or “Politics”.
membership, referee
When contained in these elements, title contains the name of the
person's role or capacity withing an organization. Examples:
“Treasurer”, “Member”, “Chief
Officer of Toothpaste Policy”, “Lead
Programmer”.
awards, interests, memberships, skillarea
When contained in these elements, title contains a heading for that
section of a résumé. It is formatted as a top-level heading.
The title element is optional
in awards and interests. If it is not present, the
awards.word and
interests.word parameters will be used
as the heading text in formatted résumés, respectively.
skillset
When contained in this element, title contains the name of a skill
category. Examples: “Teaching”,
“Computers”, “Woodworking”,
“Soap Carving”.
subject
When contained in this element, title contains the name of a subject.
It can be as general as “English” (a very broad
field of study), or as specific as “Eng 115 Intro to
Writing Fall 2001” (a specific university course name,
number, and date of study).
title may be contained in these
elements:
award, awards, clearances, interest, interests, membership, memberships, name, referee, skillarea, skillset, subject
Example 13.
interest title
<interest>
<title>Fly fishing for sharks</title>
<description><para>
I once caught a 300-kg. Great White off the coase of Florida using a green
and gold-colored dragonfly that I tied.
</para></description>
</interest>Example 14.
membership and memberships titles
<memberships>
<title>Professional Memberships</title>
<membership>
<organization>American Society of Blower-Uppers</organization>
</membership>
<membership>
<title>Spokesperson</title>
<organization>Smallville Demolitioneers</organization>
</membership>
<membership>
<title>President</title>
<organization>Willow County Pyrotechnicans' Guild</organization>
</membership>
</membership>Example 15.
skillarea and skillset titles
<skillarea>
<title>Computer Skills</title>
<skillset>
<title>Word Processing</title>
<skill>Microsoft Word</skill>
<skill>Corel WordPerfect</skill>
</skillset>
<skillset>
<title>Programming</title>
<skill>Perl</skill>
<skill>Python</skill>
<skill>XML</skill>
<skill>C++</skill>
</skillset>
</skillarea>to — The ending point in a period of time
uri — A Uniform Resource Indicator
Deprecated
url — A Uniform Resource Locator
The use of the url element as a child
of publisher is deprecated as of
XML Résumé Library version 1.4.0.
We recommend that you convert all urls contained in publishers to links.
The url element contains a single
Uniform Resource Locator, as specified by RFC
1738 and RFC 1808.
There are two contexts in which a URL is formatted. The first is as an
inline (e.g. when contained in a para). The second is as contact
element (contained in a contact).
When an inline, displayed as a hyperlink in a fixed-width font
(enclosed in code tags). The
“hot” text is the value of the element.
When a contact element, displayed the same as when an inline,
except not enclosed in code
tags.
When an inline, displayed as non-hyperlinked text, using the font
specified by the url.font.family parameter.
(Default: monospace
When a contact element, displayed as non-hyperlinked text, using the normal font.
Formatted as the value of the element.
url may be contained in these
elements:
achievement, contact, employer, institution, organization, para, project, pub, publisher, skill
ward — A name of a division of a city, town, or county
year — A year
zip — A zip code
The zip element contains a single zip
code (United States postal code). It may contain any format, such as
standard five-digit (“34525”), ZIP+4
(“34525-1625”), or any other valid format.
For non-U.S. postal codes, use postalCode.
Parameters are settings that affect all files that are generated by the XSL templates. They are analogous to attributes that affect everything instead of just one element.
This section is a partial listing of user-configurable parameters.
There are many more tunable parameters in
params.xsl. Take a look at
the file in a text editor if you're interested.
Table of Contents
address.format — controls default formatting of the address element
Possible values include standard (the default),
european, and italian.
In the examples below, <street> means the
value of XML element <street>, if
defined. <suburb | ward> means the value
of XML element <suburb>, if defined,
otherwise the value of XML element <ward>, otherwise blank.
standardFormats addresses in North American layout:
<street>
<street2>
<suburb | ward>
<city>, <state | province | county > <zip | postalCode>
<country>
europeanFormats addresses in European layout:
<street>
<street2>
<suburb | ward>
<zip | postalCode> <city>, <state | province | county > <country>
italianFormats addresses in Italian layout:
<street>
<street2>
<postalCode> <city> (<province>)
<country>
If none of these formats suit your needs, there is the option of entering your address as a single text block, in which case it will be formatted with line breaks intact. For example:
<address>Sr. Héctor García Marizó Reina #35, apt. 4a, e/ Gervasio y Escobar Ciudad de La Habana, CP 11900 CUBA</address>
css.href — indicates the CSS stylesheet to use to format HTML output
The value of css.href is a URL that points to a
Cascading Style Sheet file. The HTML version of the résumé will link to
this file.
For information on the CSS classes that are available for formatting, see Chapter 3, CSS Class Reference.
header.format — controls formatting of the header element
This parameter controls the formatting of the header
element in HTML and text output formats. The FO/PDF formatter is not
affected by this parameter; it produces output similar to the
centered option, but with the text left-justified
within a centered block.
Possible values include standard (the default) and
centered.
standardProduces a centered line with the name and the word “Résumé”, followed by a left-justified contact information block:
Jo Doe - Résumé
Contact Information:
Jo Doe
123 Elm #456
Garbonzoville, NX 99999-9999
Phone: 555.555.5555
Email: doe@doe.doe
URL: http://doe.com/~doe/
This value is the default for header.format.
centeredProduces a single centered block with the name and contact information.
Jo Doe
123 Elm #456
Garbonzoville, NX 99999-9999
Phone: 555.555.5555
Email: doe@doe.doe
URL: http://doe.com/~doe/
interest.description.format — controls formatting of interest descriptions
This parameter controls the formatting of the description element when it is contained
in an interest. It affects all output formats.
Possible values include single-line and
block. single-line is the default.
The examples below demonstrate the formatting of this XML fragment:
<interests>
<interest>
<title>Scuba diving</title>
</interest>
<interest>
<title>Flying</title>
<description>
<para>I have my pilot's license, and have logged over 1000 in-flight
hours.</para>
<para>I have also constructed my own airplane from a kit.</para>
</description>
</interest>
</interests>
single-line
This value is the default. Formats all of the para elements in the description on
the same logical line as the interest title. The title is separated
from the description by a period, and the description paragraphs are
separated from each other by
description.para.separator.text, which
defaults to an em-dash (“—”).
For example, the XML above would be formatted similar to the following:
Scuba diving
Flying. I have my pilot's license, and have logged over 1000 in-flight hours. — I have also constructed my own airplane from a kit.
block
Formats each of the para elements
in the description as a separate block below the interest title.
For example, the XML above would be formatted similar to the following:
Scuba diving
Flying
I have my pilot's license, and have logged over 1000 in-flight hours.
I have also constructed my own airplane from a kit.
skills.format — controls formatting of the skillset element
Possible values include bullet (the default) and
comma.
The examples below show how a <skillset>
like this would be rendered:
<skillarea>
<title>Technical Skills</title>
<skillset>
<title>Programming Languages</title>
<skill>Java</skill>
<skill>C++</skill>
<skill>C</skill>
<skill>perl</skill>
</skillset>
</skillarea>
skills.level.display — Determines whether or not skill level attributes are visible in formatted output
This parameter controls the formatting of the level attribute of skill
elements in all output formats.
Possible values include 1 (display the attribute) or
0 (suppress the attribute).
1 (true)
level attributes of
skills are displayed after all of
the rest of the content of the skill. The level is displayed
surrounded by skills.level.start and
skills.level.end (parenthesis, by default).
0 (false)
level attributes contained in
skills are suppressed; they are
treated as if the didn't exist for formatting purposes.
subjects.format — controls formatting of the subjects element
Possible values include comma (the default) and
table.
The examples below show how a <subjects>
section like this would be rendered:
<subjects>
<subject>
<title>English</title>
<result>C</result>
</subject>
<subject>
<title>Science</title>
<result>A</result>
</subject>
<subject>
<title>Math</title>
<result>B-</result>
</subject>
</subjects>
This section of the manual describes the Cascading Stylesheets classes that are available for formatting HTML output. For more information on CSS, visit the W3C web site.
Table 3.1. Table of CSS Classes
| Class | Where Used |
|---|---|
achievement |
On the li for a single
achievement.
|
address |
On the p that contains a postal
address.
|
award |
On the li for a single award.
|
awardTitle |
On the span of an award title.
|
bookTitle |
On the cite used to refer to a
title of a book in one of your publications.
|
citation |
On all HTML cites generated from
all XML citations.
|
copyright |
On the address for copyright
information.
|
degree |
On the li for a single degree.
|
degrees |
On the ul for the list of
degrees you hold.
|
degreeTitle |
On the span surrounding a
degree level and major, such as “B.S. in Political
Science”.
|
description | Around descriptions of items. |
emphasis |
On all HTML strongs generated
from all XML emphasiss.
|
employer | Around all employer names. |
gpaPreamble |
On the span around the preamble
to a GPA, such as “Overall GPA”.
|
heading |
On the h2 of résumé section
headings, such as “Professional Objective” or
“Employment History”.
|
headingText |
On the span that contains
heading text. This element is contained directly within the
h2 with the
heading class, and allows style to be applied
to just the heading text, instead of the whole heading line.
|
jobTitle |
On the span enclosing the title
you held at job.
|
lastModified |
On the p for the “last
modified” notice.
|
level |
On the acronym for the level
attained in a degree.
|
linkA |
On the a of a hyperlink
generated from a link element
in a résumé.
|
membershipTitle | On the position title in a membership. |
nameHeading | Around your name at the top of the résumé. |
note |
On the span of a note.
|
organization | On the name of the organization of which you're a member. |
para |
On all HTML ps generated from all
XML paras.
|
project |
On the li for a single project.
|
pub | On a single publication. |
pubs |
On the ul for the list of
publications.
|
referee |
On the div of a referee.
|
refereeName |
On the div of a referee name.
|
refereeContact |
On the div of a referee
contact.
|
resume |
On the body of the entire HTML
output.
|
skill |
On the li for a single skill.
|
skills |
If skills.format
is bullet, on the ul for a list of skills. If
skills.format is comma,
on the span for a list of
skills.
|
skillsetTitle |
On the h3 for a title of a set
of skills.
|
urlA |
On the a of a hyperlink
generated from a url element in
a résumé.
|
Attributes provide additional information about element that they appear in. They take the form of name-value pairs in the element. The emphasized parts of this example are attributes:
<author name="a.kernighan"> <resume id="r25a4">
An element of an XML document that defines an
“object”, such as <resume> or <firstname>. HTML tags are
examples of elements. Additionally, elements can have attributes. Elements
have a start (or "open") tag (e.g., <firstname>) and an end (or "close") tag
(e.g., </firstname>).
Each element (except for the root
<resume>) has exactly one
parent element and
0 or more child
elements.
The element whose start tags and end tags surround a given element.
Any element positioned between the start tags and end tags of a given element.
Table of Contents
Version 1.1, March 2000
Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
The purpose of this License is to make a manual, textbook, or other written document “free” in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.
This License is a kind of “copyleft”, which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.
We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.
This License applies to any manual or other work that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. The “Document”, below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as “you”.
A “Modified Version” of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.
A “Secondary Section” is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (For example, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.
The “Invariant Sections” are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License.
The “Cover Texts” are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License.
A “Transparent” copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, whose contents can be viewed and edited directly and straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup has been designed to thwart or discourage subsequent modification by readers is not Transparent. A copy that is not “Transparent” is called “Opaque”.
Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML designed for human modification. Opaque formats include PostScript, PDF, proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML produced by some word processors for output purposes only.
The “Title Page” means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, “Title Page” means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.
You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and you may publicly display copies.
If you publish printed copies of the Document numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.
If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a publicly-accessible computer-network location containing a complete Transparent copy of the Document, free of added material, which the general network-using public has access to download anonymously at no charge using public-standard network protocols. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.
You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:
Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.
List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has less than five).
State on the Title page the name of the publisher of the Modified Version, as the publisher.
Preserve all the copyright notices of the Document.
Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.
Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.
Include an unaltered copy of this License.
Preserve the section entitled “History”, and its title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section entitled “History” in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.
Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the “History” section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.
In any section entitled “Acknowledgements” or “Dedications”, preserve the section's title, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.
Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.
Delete any section entitled “Endorsements”. Such a section may not be included in the Modified Version.
Do not retitle any existing section as “Endorsements” or to conflict in title with any Invariant Section.
If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.
You may add a section entitled “Endorsements”, provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.
You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.
You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice.
The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections entitled “History” in the various original documents, forming one section entitled “History”; likewise combine any sections entitled “Acknowledgements”, and any sections entitled “Dedications”. You must delete all sections entitled “Endorsements.”
You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.
A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, does not as a whole count as a Modified Version of the Document, provided no compilation copyright is claimed for the compilation. Such a compilation is called an “aggregate”, and this License does not apply to the other self-contained works thus compiled with the Document, on account of their being thus compiled, if they are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one quarter of the entire aggregate, the Document's Cover Texts may be placed on covers that surround only the Document within the aggregate. Otherwise they must appear on covers around the whole aggregate.
Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License provided that you also include the original English version of this License. In case of a disagreement between the translation and the original English version of this License, the original English version will prevail.
You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License “or any later version” applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.
To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:
Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. A copy of the license is included in the section entitled "GNU Free Documentation License".
If you have no Invariant Sections, write "with no Invariant Sections" instead of saying which ones are invariant. If you have no Front-Cover Texts, write “no Front-Cover Texts” instead of “Front-Cover Texts being LIST”; likewise for Back-Cover Texts.
If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.