diff --git a/Charles Wyble Resume.docx b/Charles Wyble Resume.docx
index 9994b39..7a30ddb 100644
Binary files a/Charles Wyble Resume.docx and b/Charles Wyble Resume.docx differ
diff --git a/generateResume.sh b/generateResume.sh
new file mode 100644
index 0000000..9c16d7a
--- /dev/null
+++ b/generateResume.sh
@@ -0,0 +1,88 @@
+#!/bin/bash
+
+# A script to generate pdf/doc resume file
+# Two versions
+# Comprehensive (more for long form reading by humans)
+# Chronological (more for machine consumption/short form reading for humans)
+
+#Globals
+
+export ai1_resume_file="AllInOneResume.md"
+export ai1_PDF_OUTPUT_FILE="CharlesNWyble-December2023-ComprehensiveResume.pdf"
+export ai1_DOC_OUTPUT_FILE="CharlesWyble-December2023-ComprehensiveResume.docx"
+
+export chron_resume_file="ChronologicalResume.md"
+export chron_PDF_OUTPUT_FILE="CharlesNWyble-December2023-ChronologicalResume.pdf"
+export chron_DOC_OUTPUT_FILE="CharlesWyble-December2023-ChronologicalResume.docx"
+
+export ar24_resume_file="CharlesNWyble-Apple-2024Resume.md"
+export ar24_PDF_OUTPUT_FILE="CharlesNWyble-February2024-ComprehensiveAppleResume.pdf"
+export ar24_DOC_OUTPUT_FILE="CharlesWyble-February2024-ComprehensiveAppleResume.docx"
+
+
+function prevRunCleanup()
+{
+#echo "Cleaning up all in one resume output files..."
+#rm output/$ai1_DOC_OUTPUT_FILE
+#rm output/$ai1_PDF_OUTPUT_FILE
+
+#echo "Cleaning up chronological resume output files..."
+#rm output/$chron_DOC_OUTPUT_FILE
+#rm output/$chron_PDF_OUTPUT_FILE
+
+echo "Cleaning up apple 2024 internal fte resume output files..."
+rm output/$ar24_DOC_OUTPUT_FILE
+rm output/$ar24_PDF_OUTPUT_FILE
+}
+
+function makeOutput()
+{
+
+echo "Creating all in one PDF..."
+
+#pandoc \
+# < input/$ai1_resume_file \
+# --from=markdown \
+# --output=output/$ai1_DOC_OUTPUT_FILE
+
+echo "Creating all in one DOC..."
+
+#pandoc \
+# < input/$ai1_resume_file \
+# --from=markdown \
+# -V geometry:margin=0.0in \
+# --output=output/$ai1_PDF_OUTPUT_FILE
+
+echo "Creating chronological DOC..."
+
+#pandoc \
+# < input/$chron_resume_file \
+# --from=markdown \
+# --output=output/$chron_DOC_OUTPUT_FILE
+
+echo "Creating chronological PDF..."
+
+#pandoc \
+# < input/$ai1_resume_file \
+# --from=markdown \
+# -V geometry:margin=0.0in \
+# --output=output/$chron_PDF_OUTPUT_FILE
+
+echo "Creating apple FTE DOC..."
+
+pandoc \
+ < input/$ar24_resume_file \
+ --from=markdown \
+ --output=output/$ar24_DOC_OUTPUT_FILE
+
+echo "Creating apple FTE PDF..."
+
+pandoc \
+ < input/$ar24_resume_file \
+ --from=markdown \
+ -V geometry:margin=0.5in \
+ --output=output/$ar24_PDF_OUTPUT_FILE
+}
+
+prevRunCleanup
+makeOutput
\ No newline at end of file
diff --git a/legacy-resumes/charlesnw-resume-detailed.xml b/legacy-resumes/charlesnw-resume-detailed.xml
new file mode 100644
index 0000000..4ac8d0c
--- /dev/null
+++ b/legacy-resumes/charlesnw-resume-detailed.xml
@@ -0,0 +1,299 @@
+
+
+
+
The XML Résumé Library copyrighted, © + 2000-2002 by Sean Kelly. See the copying conditions, license, and + disclaimer. +
+ +Sean Kelly | +Project Manager | +
Stewart Evans | +Information Analyst/Designer | +
Bruce Christensen | +Developer and Project Manager | +
Robert Dubinski | +Developer | +
Olivier Eymere | +Developer | +
Rob Kelley | +Developer | +
Dave Lee | +Developer | +
Brian May | +Developer | +
Paul Sargent | +Developer | +
Mark Miller | +Developer | +
Nick Chalko | +Developer | +
Vlad Korolev + provided the plain text transformation. +
+ +Roel Vanhout suggested the + date of birth element. Formatting of the date of birth will + appear later. +
+ +Will Sargent + contributed the cygwin shell script for those who don't like + Makefiles on Windows. +
+ +Payam Mirrashidi + contributed the Windows batch file for those who don't like + cygwin on Windows. +
+ +Andre van Dijk + contributed the Dutch translation layer. +
+ +And thanks go to Norman Walsh for unwittingly providing the the
+ iso-lat1.ent
file.
+
The XML Résumé Library copyrighted, © + 2000-2002 by Sean Kelly. See the copying conditions, license, and + disclaimer. +
+ +This file lists low-level changes to the library and is + intended for developers. For user-visible changes, see the + news. +
+ + +2002-11-28 brandondoyle + + * /cvsroot/xmlresume/resume/src/www/xsl/params.xsl: + default output format is now 2-column for referees + +2002-11-26 brandondoyle + + * /cvsroot/xmlresume/resume/src/www/xsl/country/br.xsl: + improved translations, courtesy of Felipe Leme + +2002-11-25 brandondoyle + + * /cvsroot/xmlresume/resume/src/www/xsl/format/text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/lib/textlayout.xsl: + Bug fix for "variable accessed before it was bound" bug 635211 + Didn't I already check this in? + +2002-11-21 brandondoyle + + * /cvsroot/xmlresume/resume/src/www/css/compact.css, /cvsroot/xmlresume/resume/src/www/maxbenson_contemporary.htm, /cvsroot/xmlresume/resume/src/www/maxbenson_contemporary.xml, /cvsroot/xmlresume/resume/src/www/maxbenson_professional.htm, /cvsroot/xmlresume/resume/src/www/maxbenson_professional.xml: + Removing maxbenson files because they seem to serve no purpose whatsoever. + compact.css: minor style changes + +2002-11-20 brandondoyle + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Added the "targets" attribute to every element to allow for DTD validation + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Changed the ordering of the elements in a degree to reflect what + "annotation" means. This changes nothing, technically speaking. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml: + Started a new section for DTD changes for the next release + + * /cvsroot/xmlresume/resume/build.xml: + Added doc.manual.pdf back into the build process + + * /cvsroot/xmlresume/resume/src/doc/manual/en/getting-started/explore.xml: + Updated docs in response to bug reports and questions. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/getting-started/explore.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/getting-started/setup.xml: + User guide docs... I guess I forgot to add these a long time ago. + +2002-11-19 brandondoyle + + * /cvsroot/xmlresume/resume/src/www/css/compact.css: + improved referee spacing + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/Filter.java: + Bugfixes for ant support, comment and code cleanups. + + * /cvsroot/xmlresume/resume/examples/Makefile, /cvsroot/xmlresume/resume/examples/build.xml: + Changed some variable names to standardize them + +2002-11-18 brandondoyle + + * /cvsroot/xmlresume/resume/src/www/xsl/country/es.xsl, /cvsroot/xmlresume/resume/src/www/xsl/country/propogate-params.sh: + Added a check to propogate-params to look for outdated params + + * /cvsroot/xmlresume/resume/src/www/xsl/country/es.xsl, /cvsroot/xmlresume/resume/src/www/xsl/country/fr.xsl, /cvsroot/xmlresume/resume/src/www/xsl/country/it.xsl, /cvsroot/xmlresume/resume/src/www/xsl/country/nl.xsl, /cvsroot/xmlresume/resume/src/www/xsl/country/propogate-params.sh, /cvsroot/xmlresume/resume/src/www/xsl/country/uk.xsl: + Added propogate-params.sh, an UGLY shell script to propogate new parameters + defined in us.xsl to other country.xsl files with a default translation of + "TRANSLATION NEEDED". See Bruce's Feature Request 557492 for more info. + The changed files reflect the changes made after running this new script. + + * /cvsroot/xmlresume/resume/src/www/xsl/country/br.xsl: + Updated brazilian translations courtesy of Felipe Leme + + * /cvsroot/xmlresume/resume/examples/build.xml: + Added build.xml, an Ant Makefile for building the example resumes. + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/FileWriterHandler.java: + updated DOCTYPE definition from 1.3.1 to 1.5.0. There needs to be a better + solution to this. It would be nice if we could handle the <!DOCTYPE> events, but they don't seem to be generated anywhere. + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/TargetFilter.java: + Added notationDecl and unparsedEntityDecl methods... which don't do much. + +2002-11-15 brandondoyle + + * /cvsroot/xmlresume/resume/src/www/xsl/country/de.xsl: + Improved German language support, contributd by anon in bug# 638455 + +2002-11-10 brandondoyle + + * /cvsroot/xmlresume/resume/src/www/xsl/format/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/text.xsl, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + The "projects" element may now be included in the "degree" element + + * /cvsroot/xmlresume/resume/examples/Makefile: + Added "es" (espanol) as a language (country) option. + +2002-11-07 brandondoyle + + * /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html, /cvsroot/xmlresume/resume/etc/replace_changelog.py: + doc changes, changed python location to /usr/local/bin/python + + * /cvsroot/xmlresume/resume/README, /cvsroot/xmlresume/resume/build.xml, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/test/ResumeTest.java: + Random fixes while trying to build a release. + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/test/ResumeTest.properties: + mved ResumeTest.properties to test/ResumeTest.properties + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/ResumeTest.properties, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/test/testdata/basic.xml, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/test/testdata/empty.xml, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/test/testdata/huge.xml: + mved testdata to test/testdata + mved targetdata to test/targetdata + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/test/ResumeTest.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/test/Setting.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/test/Parameter.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/ResumeTest.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/Setting.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/Parameter.java: + Moved the regression testing classes into a "test" package + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/javadoc.sh, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/doc.tgz, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/javadoc.sh: + Moved documentation to net/sourceforge/xmlresume/doc.tgz + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/FileWriterHandler.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/Filter.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/README, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/TargetFilter.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/CategoryFilter.java: + Replaced "categories" with "targets" in all source files. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/getting-started/convert.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/getting-started/create.xml, /cvsroot/xmlresume/resume/README: + Replaced these files with explore and setup + + * /cvsroot/xmlresume/resume/build.xml: + Replaced old "cutting a release" checklist with more extensive one from + http://sourceforge.net/docman/display_doc.php?docid=10468&group_id=29512 + + * /cvsroot/xmlresume/resume/src/www/css/blueorange.css: + It wasn't the dash. It was the ampersand I had inside the file. + + * /cvsroot/xmlresume/resume/src/www/css/blue-orange.css, /cvsroot/xmlresume/resume/src/www/css/blueorange.css: + The dash was causing problems, I think + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml, /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html: + Doc bugs and a changelog addition. + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/FileWriterHandler.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/Filter.java: + Proper character-encoding support which should work with all VMs going back to 1.2 or perhaps even 1.1 + +2002-11-06 brandondoyle + + * /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html, /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + yup... more doc changes for 1.5.0 + + * /cvsroot/xmlresume/resume/src/doc/README.src: + Added a pointer to the news section of the docs + + * /cvsroot/xmlresume/resume/src/doc/manual/en/glossary.xml: + Added a few glossary terms. + + * /cvsroot/xmlresume/resume/build.xml: + Release support for the java filter stuff + + * /cvsroot/xmlresume/resume/src/www/xsl/country/es.xsl: + Spanish language support, contributed by Miguel Coca. + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/Filter.java: + Restored specification of UTF-8 in the PrintStream constructor; this is + required to prevent character codes from being translated too early. + + Unfortunately, this precludes the possibility of using the filter with + Jre 1.3.1 or earlier... bad luck all around. + + * /cvsroot/xmlresume/resume/src/www/xsl/params.xsl: + Changed the value of css.href so that show up in the right spot for the release users + + * /cvsroot/xmlresume/resume/examples/Makefile, /cvsroot/xmlresume/resume/examples/example2.xml: + Added parts to example2.xml to represent new parts of the DTD and demonstrate the filter idea. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/intro.xml, /cvsroot/xmlresume/resume/src/doc/manual/entities/divisions.ent, /cvsroot/xmlresume/resume/src/doc/release/todo/index.html, /cvsroot/xmlresume/resume/src/doc/manual/en/bookinfo.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/glossary.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/intro.xml, /cvsroot/xmlresume/resume/src/doc/manual/manual.xml: + User guide changes and additions + +2002-11-05 brandondoyle + + * /cvsroot/xmlresume/resume/src/doc/release/news/index.html, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.project.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml, /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html: + Final (really this time) doc changes for 1.5.0 + + * /cvsroot/xmlresume/resume/README: + typo fixes + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/www/xsl/format/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/lib/common.xsl, /cvsroot/xmlresume/resume/src/www/xsl/params.xsl: + Allow for a title attribute in the project element. + $skills.title.separator and $subjects.title.separator have been replaced by + $title.separator + +2002-11-04 brandondoyle + + * /cvsroot/xmlresume/resume/src/www/xsl/format/html.xsl: + whitespace stuff + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + "degree" element no longer requires a "major" element (feature req 594173) + because not all international universities require a major. Support for + optional majors has been in xsl for awhile, this just changes the dtd to + reflect that. + + * /cvsroot/xmlresume/resume/src/www/xsl/format/html.xsl: + bug 601475, changed <xsl:output method="html" ...> (was method="xml"). + This allows us to skip the forced output of the + <META http-equiv="Content-Type" content="text/html; charset=UTF-8"> + + * /cvsroot/xmlresume/resume/src/www/xsl/format/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/fo.xsl: + The "period" element can now be used in place of "date" in "award" and + "clearance". Also fixed a bug in fo.xsl that forced 2-column referee + layout on people, and some minor whitespace fixes that are only partially + done. + + * /cvsroot/xmlresume/resume/README: + it's cvs tag release-X_Y_Z, not release-X.Y.Z + + * /cvsroot/xmlresume/resume/README: updated release procedure + + * /cvsroot/xmlresume/resume/src/doc/release/news/index.html, /cvsroot/xmlresume/resume/src/doc/release/todo/index.html, /cvsroot/xmlresume/resume/build.xml, /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html, /cvsroot/xmlresume/resume/src/doc/release/index.html: + doc changes for release 1.5.0 + + * /cvsroot/xmlresume/resume/examples/Makefile: + Added $(resume).rtf to list of files to rm during clean. + + * /cvsroot/xmlresume/resume/examples/Makefile, /cvsroot/xmlresume/resume/examples/example2.xml: + Updated Makefile to support filtering and add targeted elements to example2.xml + + * /cvsroot/xmlresume/resume/src/www/xsl/country/it.xsl, /cvsroot/xmlresume/resume/src/www/xsl/country/us.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/lib/common.xsl, /cvsroot/xmlresume/resume/src/www/xsl/country/fr.xsl: + Bugs 624365, 629607 request that we allow non-english users to use different + phrases for "Mobile Phone", "Home Phone", and the like. This change replaces + the home.word param (and mobile.word, and work.word respectively) with + phone.home.phrase and fax.home.phrase. + + * /cvsroot/xmlresume/resume/examples/Makefile: + Added Makefile support for RTF using xmlmind's fo->rtf converter, which seems + to work ok. + + * /cvsroot/xmlresume/resume/src/www/xsl/format/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/params.xsl: + Added two column support for the referees section + + * /cvsroot/xmlresume/resume/src/www/xsl/country/br.xsl: + fixed the character code for "pagina" + + * /cvsroot/xmlresume/resume/src/www/css/blue-orange.css, /cvsroot/xmlresume/resume/src/www/css/compact.css, /cvsroot/xmlresume/resume/src/www/css/gray.css, /cvsroot/xmlresume/resume/src/www/css/original.css, /cvsroot/xmlresume/resume/src/www/css/professional.css: + css support for 2-column format, misc. fixes + + * /cvsroot/xmlresume/resume/src/www/css/CSS_Classes.txt, /cvsroot/xmlresume/resume/src/www/css/cssClasses.sh, /cvsroot/xmlresume/resume/src/www/css/cssClasses.txt: + cssClasses.(sh|txt)-- create or maintain a list of available CSS classes. + +2002-11-03 brandondoyle + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml, /cvsroot/xmlresume/resume/src/www/xsl/format/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/text.xsl, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Allow the use of "date" elements in place of "period" in membership and jobs. + + * /cvsroot/xmlresume/resume/src/www/xsl/paper/letter.xsl: + Reduced margin size to use the page more efficiently. New settings should allow enough room for printing/faxing. + +2002-10-29 brandondoyle + + * /cvsroot/xmlresume/resume/src/www/xsl/misc/html_contemporary.xsl, /cvsroot/xmlresume/resume/src/www/xsl/misc/html_professional.xsl: + Deprecated the use of these files; it seems like a heap of trouble to maintain + when CSS can be used about as easily. (And by deprecating, I just put + a note in the file saying "don't use this.") + + * /cvsroot/xmlresume/resume/src/www/xsl/country/fr.xsl: + Support request # 629607, changes and additions to reflect the french style + + * /cvsroot/xmlresume/resume/src/www/xsl/params.xsl: + forgot a closing comment tag + + * /cvsroot/xmlresume/resume/src/www/xsl/params.xsl: + added reminder about finding the right css directory. + + * /cvsroot/xmlresume/resume/src/www/xsl/format/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/params.xsl: + * Simple cleanup of params.xsl comments + * Added param "css.embed" to allow for optional embedding of css style tags directly into the html file. Allows for easier file transfer (one file instead of two) + +2002-10-28 brandondoyle + + * /cvsroot/xmlresume/resume/src/www/css/resume_professional.css, /cvsroot/xmlresume/resume/src/www/css/resume_contemporary.css, /cvsroot/xmlresume/resume/src/www/css/resume1.css, /cvsroot/xmlresume/resume/src/www/css/resume2.css, /cvsroot/xmlresume/resume/src/www/css/resume3.css, /cvsroot/xmlresume/resume/src/www/css/resume4.css, /cvsroot/xmlresume/resume/src/www/css/original.css, /cvsroot/xmlresume/resume/src/www/css/professional.css, /cvsroot/xmlresume/resume/src/www/css/gray.css, /cvsroot/xmlresume/resume/src/www/css/blue-orange.css, /cvsroot/xmlresume/resume/src/www/css/compact.css, /cvsroot/xmlresume/resume/src/www/css/NOTICE, /cvsroot/xmlresume/resume/src/www/css/CSS_Classes.txt: + * Replaced/removed resume*.css with equivalent, descriptively named files. + * Wrapped all CSS with xml tags to allow embedding into the generated html files (allows for easy emailing of an html resume) + * Moved Copyright/usage notice into NOTICE + * Created CSS_Classes.txt, which lists all available CSS classes for the xmlresume, plus a command to update the list. + +2002-10-26 brandondoyle + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/Filter.java: + PrintStream.PrintStream(OutputStream, boolean, String charset) does not exist + prior to JRE 1.3, so I've changed it to use a different constructor. + +2002-10-22 brandondoyle + + * /cvsroot/xmlresume/resume/src/www/xsl/country/fr.xsl: + Changed in.word and achievements.word to better reflect current french + style. SF Patch # 618302 + +2002-10-19 brandondoyle + + * /cvsroot/xmlresume/resume/examples/Makefile: + Added all the countries we support to the list of possible vals for "country" + + * /cvsroot/xmlresume/resume/src/www/xsl/country/it.xsl: + Italian pluralization rules: + male: cano -> cani + female: porta -> porte + +2002-07-16 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/release/todo/index.html: + Added a note about looking on the SF feature request page for more things + to do. + + * /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html: + The <h1> on this was copied-and-pasted from the authors file. Fixed to say + "changelog". + + * /cvsroot/xmlresume/resume/etc/replace_changelog.py: + Replaced the actual changelog text (leaving surrrounding text intact) in + src/doc/release/changelog/index.html. + + * /cvsroot/xmlresume/resume/build.xml: Updated version to 1.4.2. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml, /cvsroot/xmlresume/resume/src/doc/release/authors/index.html, /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Updated for 1.4.2. + + * /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html: + Updated changelog for 1.4.2. + + * /cvsroot/xmlresume/resume/src/doc/manual/xsl/fo.xsl: + Fixed some parameters that were causing FOP to choke (or else emit more + than 50000 lines of error messages). + + * /cvsroot/xmlresume/resume/build.xml: + Build and copy PDF manual for web site. + + * /cvsroot/xmlresume/resume/build.xml: + Commented out patch-for-fop section, as it doesn't seem to be needed with + FOP 0.20.3 and docbook-xsl-1.52.2 + + * /cvsroot/xmlresume/resume/src/www/css/compact.css: + Added, thanks to Mark Miller. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/param.subjects.format.xml: + Updated with better formatting for examples. + +2002-07-15 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/param.subjects.format.xml: + Added documentation for the subjects.format parameter. + + * /cvsroot/xmlresume/resume/src/www/xsl/format/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/lib/common.xsl, /cvsroot/xmlresume/resume/src/www/xsl/params.xsl: + Applied Mark Miller's patch (cleaned up by me) for comma-separated degree + subject formatting. + +2002-06-29 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/getting-started/convert.xml: + Updated and clarified wording a bit. + +2002-06-24 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/www/xsl/misc/normalize-whitespace.xsl: + This file normalizes whitespace in an XML file similar to the way HTML + processors condense whitespace: + - all whitespace characters are replaced with space characters + ("	" -> " ") + - all-whitespace text nodes are removed ("<url> </url>" -> "<url></url>") + - whitespace at the beginning and end of element contents is removed + ("<url> a </url>" -> "<url>a</url>") + - consecutive whitespace characters are converted into a single space + character ("this is a test" -> "this is a test") + + * /cvsroot/xmlresume/resume/src/www/xsl/format/text.xsl: + Fixed bug 566653 (unexpected line breaks in text output). + +2002-06-16 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Fixed erroneous version number. + + * /cvsroot/xmlresume/resume/build.xml: Added a release.upload target. + + Fixed the install.web target. (It should have depended on + doc.manual.html-multiple.web, but it didn't.) + + * /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html: + /Really/ updated for 1.4.1 this time. I fixed something after I commited + this last time. + + * /cvsroot/xmlresume/resume/build.xml, /cvsroot/xmlresume/resume/src/doc/manual/img/box-0.gif, /cvsroot/xmlresume/resume/src/doc/manual/img/box-1.gif, /cvsroot/xmlresume/resume/src/doc/manual/img/caret-l.gif, /cvsroot/xmlresume/resume/src/doc/manual/img/caret-r.gif, /cvsroot/xmlresume/resume/src/doc/manual/img/caret-t.gif, /cvsroot/xmlresume/resume/src/doc/manual/img/caret-u.gif: + Added images for HTML-formatted manual (stolen from the php.net web site). + + * /cvsroot/xmlresume/resume/build.xml: Updated version to 1.4.1. + + * /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html: + Updated for release 1.4.1. + + * /cvsroot/xmlresume/resume/src/doc/release/index.html: + Updated for release 1.4.1. (Changed XSL paths to include output directory). + + * /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Fixed an HTML error. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml: + Fixed a typo. + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/ResumeTest.java: + Fixed to point to new location for output stylesheets. + + * /cvsroot/xmlresume/resume/src/www/xsl/format/text.xsl: + Changed the structure of the template that formats subjects to work around + (what I think is) a bug in Xalan. + + * /cvsroot/xmlresume/resume/src/www/xsl/lib/common.xsl: + Switch from <xsl:include>ing string.xsl to <xsl:import>ing it. This avoids + a double-inclusion, since the output format stylesheets include string.xsl. + +2002-06-15 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml: + Added a note about the new <location> element to this list of changes for + version 1.4.1. + + * /cvsroot/xmlresume/resume/src/www/dtd/iso-lat1.ent: + Updated this file with the latest version from: + http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/docbook/xmlcharent/iso-lat1.ent?rev=1.3&content-type=text/vnd.viewcvs-markup + + It includes fixes for a few erroneous characters in the previous version. + It also includes an appropriate copyright notice, which the original + version did not. + +2002-06-14 Sean Kelly + + * /cvsroot/xmlresume/resume/src/doc/release/authors/index.html, /cvsroot/xmlresume/resume/src/doc/release/index.html, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/ResumeTest.properties: + Add notes about Dutch resumes; add Dutch resume to test properties. + + * /cvsroot/xmlresume/resume/src/www/xsl/country/nl.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/nl-a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/nl-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/nl-text.xsl: + Dutch resumes, contributed by Andre van Dijk + + * /cvsroot/xmlresume/resume/contrib/resume.bat: + Format resume with Windows batch file, courtesy of Payan Mirrashidi. + + * /cvsroot/xmlresume/resume/contrib/format-cygwin.sh: + Cygwin-compatible shell script to format resumes, courtesy of Will + Sargent. + + * /cvsroot/xmlresume/resume/build.xml: + Make the img directory if it doesn't exist. + +2002-06-14 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.name.xml: + Removed the list of required and allowed elements, since we automatically + generate that information. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml: + Added a note that <name> may now contain a <title>. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.title.xml, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/www/xsl/format/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/lib/common.xsl, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.name.xml: + Added support for a <title> element within a <name> (feature request + 568565). + + Also moved the templates that format a name from each of the format XSLT + files (html.xsl, text.xsl, and fo.xsl) into common.xsl, since they were all + exactly the same. + +2002-06-10 Bruce Christensen + + * /cvsroot/xmlresume/resume/build.xml: + The install.web target now filters the files it copies. + + * /cvsroot/xmlresume/resume/src/www/xsl/format/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/params.xsl: + Renamed the copyright.font.size parameter to fineprint.font.size. It is now + applied to the "last modified" date in FO output. + +2002-06-08 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/xsl/common.xsl, /cvsroot/xmlresume/resume/src/doc/manual/xsl/fo.xsl, /cvsroot/xmlresume/resume/src/doc/manual/xsl/html-common.xsl, /cvsroot/xmlresume/resume/src/doc/manual/xsl/html-multiple.web.xsl, /cvsroot/xmlresume/resume/src/doc/manual/xsl/html-multiple.xsl, /cvsroot/xmlresume/resume/build.xml, /cvsroot/xmlresume/resume/src/doc/manual/css/manual.css, /cvsroot/xmlresume/resume/src/doc/manual/manual.xml: + - Added ability to build a version of the manual suitable for inclusion + on the XML resume web site. + - Prettied up the manual (fonts, colors, navigation bars) + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/www/xsl/format/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/lib/common.xsl, /cvsroot/xmlresume/resume/src/www/xsl/lib/textlayout.xsl, /cvsroot/xmlresume/resume/src/www/xsl/params.xsl, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.location.xml: + - Added support for a <location> sub-element in <job>, <membership>, and + <degree>. + - Normalized formatting a bit between HTML, text, and PDF output. Jobs and + memberships are now formatted as: + + Title + Organization[, location] + Date + + [Description...] + +2002-06-07 Bruce Christensen + + * /cvsroot/xmlresume/resume/README: + Added a section on how to change the DTD. + + * /cvsroot/xmlresume/resume/src/doc/manual/README: Minor updates. + + Removed mention of the sgml dir, as we no longer include the SGML tools; + external versions installed on a developer's machine are used instead. + +2002-06-01 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Made <title> an allowable child of <clearances> instead of <clearance>. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/cssref/chapter.xml: + The text about the achievement class now refers to the achievement element. + (It referred to the skill element before.) + +2002-05-31 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/Filter.java: + Fixed a stupid bug included in the last commit (mixed up arguments between + two constructors). + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/FileWriterHandler.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/Filter.java: + Removed code from FileWriterHandler that escaped any non-ASCII character + with a hex entity. Instead, we now set the output character set to UTF-8 in + Filter, thus solving the problem (non-ASCII characters are converted to "?" + when output) in a simpler way. + + * /cvsroot/xmlresume/resume/src/www/css/resume1.css, /cvsroot/xmlresume/resume/src/www/css/resume2.css, /cvsroot/xmlresume/resume/src/www/css/resume3.css, /cvsroot/xmlresume/resume/src/www/css/resume4.css, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/www/xsl/country/us.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/params.xsl, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.clearance.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.clearances.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.date.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.level.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml: + Added support for security clearances (feature request 396338). This is + based on patch 562652, submitted by Nick Chalko, but with heavy changes by + myself. + + * /cvsroot/xmlresume/resume/src/www/xsl/format/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/lib/common.xsl: + Fixed a rather nasty bug described in + http://sourceforge.net/forum/forum.php?thread_id=687115&forum_id=92731. + + The problem was with whitespace normalization in <skills>. We wanted to + normalize whitespace, so we would grab the result of <xsl:apply-templates/> + into $Text, and then output normalize-space($Text). Of course, + normalize-space converts its argument into a string, so if a skill contains + any other elements (say, a <link>), those elements get killed by the + normalization. + + Solution? Roll our own space normalization, of course! We process + skill//text() nodes individually, normalizing space in each of them, and + outputting a space after each if needed. + +2002-05-30 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Added support for inlines (including <link> and <url>) to <organzation> and + <institution>, per feature request 562428. + + * /cvsroot/xmlresume/resume/src/www/xsl/format/fo.xsl: + Changed a bunch of instances of "<xsl:value-of select="."/>" to + "<xsl:apply-templates/>". + + * /cvsroot/xmlresume/resume/src/www/css/resume4.css: + Nice-looking new stylesheet. (If I do say so myself. :) + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/www/xsl/country/us.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/params.xsl, /cvsroot/xmlresume/resume/src/doc/manual/en/cssref/chapter.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.gpa.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.possible.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.score.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml: + Added support for GPAs. + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/CategoryFilter.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/FileWriterHandler.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/Filter.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/Props.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/README, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/filter/javadoc.sh: + Added category filter support, written by Mark Miller . + + * /cvsroot/xmlresume/resume/src/doc/manual/en/cssref/chapter.xml, /cvsroot/xmlresume/resume/src/www/xsl/format/html.xsl: + Some updates to HTML formatting: + - Unified HTML heading formatting. There are no longer different CSS + classes for each heading; they're all in the "heading" class. Also + there's a named template (called Heading) that should be used to output + any section heading. + - Removed "resume" css class from the body tag, instead wrapping each + resume in a <div class="resume"> instead. It's forseeable that there + would be multiple resumes per source file, so it didn't make sense to + have that tag in the body. + - The header is now wrapped with <div class="header"> in both standard and + centered modes. The headerBlock class has been removed. + - Contact information is now wrapped in parapgraph tags. This fixes an + XHTML validation problem. It used to be that a single <p>...</p> + contained both address and contact information in the header, but the + address was also wrapped in a <p>...</p>. This created invalid XHTML, so + the <p> tags were removed from the header, but added to contact + information. + +2002-05-26 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/www/xsl/misc/html_professional.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/br-a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/br-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/br-text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/de-a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/de-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/de-text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/fr-a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/fr-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/fr-text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/it-a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/it-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/it-text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/uk-a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/uk-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/uk-text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/us-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/us-letter.xsl, /cvsroot/xmlresume/resume/src/www/xsl/output/us-text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/paper/a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/paper/letter.xsl, /cvsroot/xmlresume/resume/examples/Makefile, /cvsroot/xmlresume/resume/src/www/xsl/124-130.xsl, /cvsroot/xmlresume/resume/src/www/xsl/13x-140.xsl, /cvsroot/xmlresume/resume/src/www/xsl/br-a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/br-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/br-params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/br-text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/country/br.xsl, /cvsroot/xmlresume/resume/src/www/xsl/country/de.xsl, /cvsroot/xmlresume/resume/src/www/xsl/country/fr.xsl, /cvsroot/xmlresume/resume/src/www/xsl/country/it.xsl, /cvsroot/xmlresume/resume/src/www/xsl/country/uk.xsl, /cvsroot/xmlresume/resume/src/www/xsl/country/us.xsl, /cvsroot/xmlresume/resume/src/www/xsl/de-a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/de-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/de-params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/de-text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/default.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/format/text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/fr-a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/fr-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/fr-params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/fr-text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/html_contemporary.xsl, /cvsroot/xmlresume/resume/src/www/xsl/html_professional.xsl, /cvsroot/xmlresume/resume/src/www/xsl/it-a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/it-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/it-params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/it-text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/lib/address.xsl, /cvsroot/xmlresume/resume/src/www/xsl/lib/common.xsl, /cvsroot/xmlresume/resume/src/www/xsl/lib/deprecated.xsl, /cvsroot/xmlresume/resume/src/www/xsl/lib/pub.xsl, /cvsroot/xmlresume/resume/src/www/xsl/lib/string.xsl, /cvsroot/xmlresume/resume/src/www/xsl/lib/textlayout.xsl, /cvsroot/xmlresume/resume/src/www/xsl/misc/124-130.xsl, /cvsroot/xmlresume/resume/src/www/xsl/misc/13x-140.xsl, /cvsroot/xmlresume/resume/src/www/xsl/misc/default.xsl, /cvsroot/xmlresume/resume/src/www/xsl/misc/html_contemporary.xsl, /cvsroot/xmlresume/resume/src/www/xsl/params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/uk-a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/uk-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/uk-params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/uk-text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/us-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/us-letter.xsl, /cvsroot/xmlresume/resume/src/www/xsl/us-params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/us-text.xsl: + Major directory refactoring in in src/www/xsl. + +2002-05-25 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/www/xsl/us-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/us-letter.xsl, /cvsroot/xmlresume/resume/src/www/xsl/us-params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/us-text.xsl: + Factored out all US-specific words into us-params.xsl. + + * /cvsroot/xmlresume/resume/src/www/xsl/us-letter.xsl: + Moved all letter (paper size)-specific parameters into letter.xsl. + +2002-05-24 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html: + Updated changelog for version 1.4.0. + + * /cvsroot/xmlresume/resume/etc/rcs2log: + Changed my email address from " at " separator to "@" so that it is + properly stripped by cltohtml. + + * /cvsroot/xmlresume/resume/build.xml: + Added the doc.manual.create-missing target. + + * /cvsroot/xmlresume/resume/etc/cltohtml: + Added. This program is used when cutting a release. + + * /cvsroot/xmlresume/resume/src/doc/release/index.html: + Changed "will see some harmless error messages" (from FOP) to "may see...", + since I don't see any. :) + + * /cvsroot/xmlresume/resume/build.xml: + Fixed a path that was out of sync with ResumeTest.java, thus causing + run.test to fail. + +2002-05-23 Bruce Christensen + + * /cvsroot/xmlresume/resume/build.xml: + Added the doc.manual.check target, which runs "dtddoc.py --check". + +2002-05-22 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.degree.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.major.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.minor.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml, /cvsroot/xmlresume/resume/src/doc/release/news/index.html, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Feature request 558871: + - Added the <minor> element. + - <degree>s may now contain multiple <major>s. + +2002-05-16 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/param.referees.display.xml: + Added. Documents the referees.display parameter. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/cssref/chapter.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.award.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.awards.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.title.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml, /cvsroot/xmlresume/resume/src/doc/release/news/index.html, /cvsroot/xmlresume/resume/src/www/css/resume3.css, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Added <awards> and <award> to the DTD. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/cssref/chapter.xml: + Referees are now formatted using lots of divs, instead of an <h3> and a + <p>. Introduced three new CSS classes: referee, refereeName, and + refereeContact. + + * /cvsroot/xmlresume/resume/src/www/css/resume3.css: + Added formatting for .resume and .resumeName. + +2002-05-15 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.referee.xml, /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Added the referees.display parameter. + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/ResumeTest.properties: + Added support for: + - interest.description.format + - skills.level.display + - Portuguese + - German + + * /cvsroot/xmlresume/resume/build.xml: Updated version number to 1.4.0. + + * /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Fixed broken links to pages in the user guide. + + * /cvsroot/xmlresume/resume/src/doc/release/news/index.html, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/www/xsl/131-134.xsl, /cvsroot/xmlresume/resume/src/www/xsl/13x-140.xsl, /cvsroot/xmlresume/resume/examples/Makefile, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.date.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.docpath.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.head.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.label.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.node.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.pubDate.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.publisher.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skillareas.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skills.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.tail.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.uri.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.url.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml, /cvsroot/xmlresume/resume/src/doc/release/index.html: + Release 1.3.4 has been renamed to release 1.4.0 because there have been + many changes since 1.3.3. + + * /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Added a list of user-visible changes for version 1.3.4. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml: + Added a note indicating that <pub> may now contain <url>. + + * /cvsroot/xmlresume/resume/src/doc/release/index.html: + Added a section about using 131-134.xsl to upgrade resumes. + + * /cvsroot/xmlresume/resume/examples/Makefile: + Changed output file of 1.3.1 to 1.3.4 upgrade from $(resume).134.xml to + $(resume)-134.xml. + +2002-05-14 Bruce Christensen + + * /cvsroot/xmlresume/resume/examples/Makefile, /cvsroot/xmlresume/resume/src/www/xsl/131-134.xsl: + Added a stylesheet to convert a resume from version 1.3.1, 1.3.2, or 1.3.3 + to version 1.3.4. + + Modified the Makefile to easily call this stylesheet. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/cssref/chapter.xml: + Documented the "address" CSS class, which applies to the <p> of postal + addresses. + + * /cvsroot/xmlresume/resume/examples/example2.xml: + Added some new elements that have been introduced in the DTD, and removed + deprecated elements. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/param.address.format.xml: + Corrected a whitespace error. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Un-deprecated use of <url> in <publisher>. I was a wee bit confused when I + deprecated it. + + * /cvsroot/xmlresume/resume/src/www/css/resume3.css: + Made degreeTitle bold. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml: + Added a message about examining the <resume> refpage to get started. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/bookinfo.xml: + Fixed a whitespace problem. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml: + Made formatting a bit more consistent. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml: + Added a list of changes to the DTD in each version. + + * /cvsroot/xmlresume/resume/src/www/css/resume3.css: + A new style, slightly based on resume3.css. Section headings are outdented, + and have a rule underneath them that extends to the right margins. + + * /cvsroot/xmlresume/resume/src/www/css/resume2.css: + Added new CSS classes. + +2002-05-12 Bruce Christensen + + * /cvsroot/xmlresume/resume/etc/rcs2log: Added Bruce Christensen. + + * /cvsroot/xmlresume/resume/src/www/xsl/html_contemporary.xsl, /cvsroot/xmlresume/resume/src/www/xsl/html_professional.xsl, /cvsroot/xmlresume/resume/src/doc/manual/en/cssref/chapter.xml, /cvsroot/xmlresume/resume/src/www/css/resume1.css: + Removed the <code> tags that were output around <url>s formatted in HTML. + They were causing some extraneous-whitespace problems in the output. + + Added the linkA CSS class. + +2002-05-11 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.publisher.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.url.xml, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Deprecated the use of <url> as a child of <publisher>. + + <url> is now allowed as a child of <pub>. + + <link> is now allowed in artTitle, bookTitle, and publisher. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.title.xml, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Allowed <title> and <organization> as children of <referee>. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.organization.xml: + Fixed a typo. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.description.xml: + Updated and corrected wording, as description may now be contained in + additional elements. + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/doc/manual/en/cssref/chapter.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.lastModified.xml: + Added the lastModified element, as requested in 460165. + +2002-05-10 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/cssref/chapter.xml: + Text and HTML formatting of <degree>s is now similar to FO formatting (the + institution is now on a line below other information except subjects). + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Added support for <period>s in <degree>s. Before only date could be used; + now either date or period can appear in a degree. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.date.xml: + Removed an extraneous comment end tag. + + * /cvsroot/xmlresume/resume/src/www/xsl/html_professional.xsl, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.docpath.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.head.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.label.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.node.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.tail.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.uri.xml, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/www/xsl/html_contemporary.xsl: + Deprecated docpath, head, node, tail, label, and uri. + + * /cvsroot/xmlresume/resume/src/www/xsl/de-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/de-params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/de-text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/de-a4.xsl: + Added support for German language formatting, fulfilling feature request + 522570. de-params.xsl courtesy of an anonymous donor on SourceForge. + Thanks! + +2002-05-08 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.pubDate.xml, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.date.xml: + Deprecated the <pubDate> element. <date> should now be used instead. + + * /cvsroot/xmlresume/resume/src/doc/manual/AUTHORING: + Fixed a syntax error in example code. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.date.xml, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Made <month> optional as a child of <date>. + +2002-05-07 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.email.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.instantMessage.xml: + Added the instantMessage element, with XSLT and user guide changes. + + * /cvsroot/xmlresume/resume/src/doc/release/index.html: + Added the release date (er, actually the build date) to the text. + +2002-05-01 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/www/xsl/br-a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/br-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/br-params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/br-text.xsl: + Support for Brazilian Portuguese localization, thanks to Felipe Leme + . + +2002-04-30 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.email.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.fax.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.pager.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.phone.xml, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Added a <pager> element and updated docs and stylesheets accordingly. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.fax.xml: + Fixed a copy-and-paste error where the fax element was being called + "phone". + + * /cvsroot/xmlresume/resume/src/doc/manual/scripts/dtddoc.py: + Er, made the last change actually work. :) + + I had changed the variable start- and end-markers from "<$" style to + "<?resumevar " style in the code that runs at build time, but not the code + that creates missing elementref pages. That's now fixed. + + I also updated the usage message to reflect this and the last change. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.email.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.emphasis.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.employer.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.fax.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.firstname.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.from.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.head.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.header.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.history.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.institution.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.interest.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.interests.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.job.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.jobtitle.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.keyword.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.keywords.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.label.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.legalnotice.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.level.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.link.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.major.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.membership.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.memberships.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.middlenames.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.misc.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.month.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.name.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.node.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.note.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.objective.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.organization.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.pageNums.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.para.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.period.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.phone.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.postalCode.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.prefecture.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.present.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.project.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.projects.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.province.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.pub.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.pubDate.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.publisher.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.pubs.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.referee.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.referees.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.result.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.resume.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.resumes.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skill.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skillarea.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skillareas.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skills.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skillset.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.state.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.street.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.street2.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.subject.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.subjects.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.suburb.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.suffix.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.surname.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.tail.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.title.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.to.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.uri.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.url.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.ward.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.year.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.zip.xml, /cvsroot/xmlresume/resume/src/doc/manual/scripts/dtddoc.py, /cvsroot/xmlresume/resume/src/doc/manual/scripts/refentry.template.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.academics.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.achievement.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.achievements.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.address.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.annotation.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.artTitle.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.author.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.birth.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.bookTitle.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.break.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.citation.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.city.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.company.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.contact.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.copyright.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.country.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.county.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.date.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.dayOfMonth.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.degree.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.degrees.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.description.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.docpath.xml: + Change variables in DocBook elementref source files from this: + - <$CONTENT_MODEL$> + to this: + - <?resumevar CONTENT_MODEL?> + + In other words, they're now real XML processing instructions, so the source + files should now be 100% well-formed XML. This is necessary to to automatic + well-formed-ness and validity checking of the examples in the DocBook + source (which I'm working on). + +2002-04-26 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/param.skills.level.display.xml, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.level.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skill.xml: + Changed the r:skill/r:level element to an attribute of the r:skill element. + Change suggested by Brian May. + +2002-04-25 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.fax.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.phone.xml, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Added a fax element. + + Contact now allows any number of phone, fax, email, or url children in any + order. Some people have more than one of each type of contact method. + + Added a @location attribute to phone and fax. This attribute is optional, + and allowed values are (home | work | mobile) for phone, (home | work) for + fax. + + Updated docs and stylesheets accordingly. + + * /cvsroot/xmlresume/resume/src/www/xsl/html_contemporary.xsl: + Added explicit encoding="UTF-8" and updated the comment header a bit with + correct filename and info about the file. + + * /cvsroot/xmlresume/resume/src/www/xsl/default.xsl: + Added explicit encoding="UTF-8". + + * /cvsroot/xmlresume/resume/src/www/xsl/html_professional.xsl: + Added explicit encoding="UTF-8" and updated the comment header a bit with + correct filename and info about the file. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/param.skills.level.display.xml, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.level.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.resume.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skill.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.title.xml: + Made <level> a valid child of <skill>. It indicates a person's proficiency + in a particular skill. + + Updated docs accordingly. + + * /cvsroot/xmlresume/resume/build.xml: + Un-commented and updated sections for building FO and PDF versions of the + user guide. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/TEMPLATE.xml: + Made a bit closer to what typical parameter reference pages look like. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/getting-started/convert.xml: + Fixed a broken entity reference. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skills.xml: + Added a "see also" link to the skills.format paramter. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.header.xml: + Added a note about, and link to, the header.format parameter. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/cssref/chapter.xml: + Added a link to a parameter. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/bookinfo.xml: + Changed the textual reference to the GFDL in the legal statement to a + hyperlink. + +2002-04-24 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/getting-started/convert.xml: + Fixed a duplicate id. + +2002-04-23 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skill.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skillarea.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skillareas.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skills.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skillset.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.title.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/param.skills.format.xml, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/examples/example1.xml, /cvsroot/xmlresume/resume/examples/example2.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.resume.xml: + Deprecated the <skillareas> and <skills> elements. <skill> may now be a + direct child of <skillset>, and <skillarea> may now be a child of <resume>. + + Updated docs to reflect this change. Documented the two elements as + deprecated, and removed them from example code. + + Updated example resume files, removing deprecated elements. + + Added deprecated.xsl, which emits warnings through the XSL processor if it + encounters a deprecated element. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.interest.xml: + Fixed a broken link. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.break.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.company.xml: + Added a note that these elements were deprecated as of version 1.3.3. + + * /cvsroot/xmlresume/resume/src/doc/manual/xsl/html-common.xsl: + Made refclass tags show up as bold in the TOC. This makes "Deprecated" + warnings stand out better. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/cssref/chapter.xml: + Added docs for achievement and project classes, clarified docs for skills + class. + + * /cvsroot/xmlresume/resume/src/doc/manual/css/manual.css: + Added colored backgrounds and 1-pixel borders for important, note, tip, + warning, and caution classes. + +2002-04-22 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/bookinfo.xml: + Changed reference to &library.version; to &library.version.dots; + + Put copyright years directly in this file -- no reference to + &book.copyright.years; anymore. + + Added Peter Hutnick as a copyright holder, since he wrote the "convert" + chapter. + + * /cvsroot/xmlresume/resume/src/doc/manual/AUTHORING: + Changed reference to guide.* to getting-started.*. + + * /cvsroot/xmlresume/resume/src/doc/manual/entities/divisions.ent, /cvsroot/xmlresume/resume/src/doc/manual/manual.xml: + Renamed guide.* sections to getting-started.*. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/appendices/gfdl.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/bookinfo.xml, /cvsroot/xmlresume/resume/src/doc/manual/entities/divisions.ent, /cvsroot/xmlresume/resume/src/doc/manual/manual.xml: + Placed the manual under the GNU Free Documentation License: + - Added a <legalnotice> section to bookinfo.xml. + - Added gfdl.xml, a DocBook version of the GFDL. + - Added an entity declaration for gfdl.xml to divisions.ent, and a + reference to that entity in manual.xml. + + * /cvsroot/xmlresume/resume/src/doc/manual/entities/global.ent: + Added lots of URL and email address entities that are used in + getting-started/convert.xml. + + Also renamed library.version to library.version.dots, and added + library.version.underscore. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.url.xml: + Corrected and expanded documentation on how the URL element is formatted. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.title.xml: + Added documentation on semantics of <title> when contained in <interest>. + Also added an example. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/getting-started/convert.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/getting-started/create.xml: + Renamed guide directory to getting-started. + + Renamed overview.xml to convert.xml. convert.xml now contains a chapter on + converting a resume from XML to other formats. It was written by Peter + Hutnick, and edited and converted to DocBook by myself. Thanks Peter! + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.interest.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.interests.xml: + Documented the <interests> and <interest> elements. + + * /cvsroot/xmlresume/resume/src/doc/manual/xsl/fo.xsl, /cvsroot/xmlresume/resume/src/doc/manual/xsl/html-common.xsl, /cvsroot/xmlresume/resume/src/doc/manual/xsl/html-multiple.xsl, /cvsroot/xmlresume/resume/src/doc/manual/xsl/html-single.xsl, /cvsroot/xmlresume/resume/src/doc/manual/manual.xml: + Removed docbook-xml and docbook-xsl files from the repository and updated + user guide to use versions defined by Ant during the build process. + + Also moved our customized versions of the DocBook XSL stylesheets from the + sgml dir to the xsl dir. + + * /cvsroot/xmlresume/resume/src/doc/release/address.html, /cvsroot/xmlresume/resume/src/doc/release/header.html, /cvsroot/xmlresume/resume/src/doc/release/index.html, /cvsroot/xmlresume/resume/src/doc/release/skills.html: + Updated release notes, adding references to the user guide in appropriate + places, and removing information that's now contained in the user guide. + + * /cvsroot/xmlresume/resume/src/doc/release/todo/index.html: + Fix: changed ©r; to ©. + + * /cvsroot/xmlresume/resume/build.xml: + (Last commit message was meant for README, not this file. This commit + contains no changes, just the log message meant for r1.21.) + + Updated to use system DocBook DTD and XSL files, instead of versions in our + repository. This means the doc.manual.* targets may be broken on your + system. You'll probably need to override $doc.manual.docbook-xsl.dir and + $doc.manual.docbook-xml.file in your ~/.ant.properties file. DON'T CHANGE + THOSE PROPERTIES IN BUILD.XML. Instead, override them in your local + ~/.ant.properties. That'll keep unneeded commits out of CVS. + + * /cvsroot/xmlresume/resume/README, /cvsroot/xmlresume/resume/build.xml: + Minor updates to reflect changes to the user guide and Makefile. + +2002-04-19 Bruce Christensen + + * /cvsroot/xmlresume/resume/build.xml: + Added VERSION_UNDERSCORE as a filter token. + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Added the <interest> and <interests> element. + + Added a comment marking <company> as deprecated. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/param.address.format.xml: + Added example tags around examples. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/param.interest.description.format.xml: + Added documentation for interest.description.format parameter. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.address.xml: + Fixed erroneous whitespace in an example. + +2002-04-17 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.memberships.xml: + Added a missing <title> element to the memberships example code. + + * /cvsroot/xmlresume/resume/src/doc/manual/css/manual.css: + Color informalexamples instead of literallayouts. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/TEMPLATE.xml: + Added more boilerplate text for the "Applies To" section. + +2002-04-16 Sean Kelly + + * /cvsroot/xmlresume/resume/src/doc/release/index.html: + Add a link to the user guide. + + * /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html: + Changelog for 1.3.3. + + * /cvsroot/xmlresume/resume/build.xml, /cvsroot/xmlresume/resume/src/doc/release/authors/index.html, /cvsroot/xmlresume/resume/src/doc/release/index.html: + Bump version # to 1.3.3. Update version numbers of tools in release + documentation. Update team members list. + + * /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Add news items for release 1.3.3 + + * /cvsroot/xmlresume/resume/examples/Makefile: + Patch 542171: Bruce's new and improved Makefile. + +2002-04-12 robjkelley + + * /cvsroot/xmlresume/resume/src/www/maxbenson_contemporary.xml, /cvsroot/xmlresume/resume/src/www/maxbenson_professional.htm, /cvsroot/xmlresume/resume/src/www/maxbenson_professional.xml, /cvsroot/xmlresume/resume/src/www/maxbenson_contemporary.htm, /cvsroot/xmlresume/resume/src/www/xsl/html_contemporary.xsl, /cvsroot/xmlresume/resume/src/www/xsl/html_professional.xsl, /cvsroot/xmlresume/resume/src/www/css/resume_contemporary.css, /cvsroot/xmlresume/resume/src/www/css/resume_professional.css: + original commit + +2002-04-12 Bruce Christensen + + * /cvsroot/xmlresume/resume/src/doc/manual/.cvsignore, /cvsroot/xmlresume/resume/src/doc/manual/scripts/.cvsignore: + Moved src/doc/manual/.cvsignore to src/doc/manual/scripts, where I had + intended to put it in the first place. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.address.xml: + Documented the new @format attribute. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.memberships.xml: + Fixed a typo. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.url.xml: + Corrected factual errors about how <url>s are formatted. Also added a See + Also link to the new <link> element. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.institution.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.membership.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.name.xml: + Correction: changed overlooked "ATTRIBUTE_NAME" boilerplate text to "id". + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.company.xml: + Changed deprecation notice from a <para> to an <important><para>. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.break.xml: + Documented this element as deprecated. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.address.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.street.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.street2.xml: + Documented <street2> as deprecated and updated related docs. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.link.xml: + Documented the <link> element. + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Added format attribute to <address>. Its possible values are standard, + european, and italian. It has no default (#IMPLIED). + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/Setting.java: + Fixed a spelling mistake in a comment. + + * /cvsroot/xmlresume/resume/src/doc/manual/scripts/fix_cdata_space.py: + Changed message displayed for each modified file from "<filename> fixed" to + "<filename> CDATA trimmed". This should help authors better understand what + the build process is doing "behind their backs". + + * /cvsroot/xmlresume/resume/src/doc/manual/scripts/dtddoc.py: + 1. Improved formatting of attribute tables to handle enumerated attribute + values. + + 2. Output displayed with --list-missing, --list-unknown, and --check is + indented and no longer displays "(None)". + + 3. --filter now only filters files that exist. (Before, it tried to filter + a file for every element in the DTD, even it the file didn't exist.) + + * /cvsroot/xmlresume/resume/src/doc/manual/scripts/dir2entities.py, /cvsroot/xmlresume/resume/src/doc/manual/scripts/resumedoc.py: + Moved make_relative_path function to newly-created module resumedoc.py, a + library file for common XML Resume documentation code. + + * /cvsroot/xmlresume/resume/src/doc/manual/entities/global.ent: + Changed book title from "User's Guide" to "User Guide". + + * /cvsroot/xmlresume/resume/src/doc/manual/en/glossary.xml: + Fixed whitespace problem with code in a CDATA section. + + * /cvsroot/xmlresume/resume/src/doc/manual/AUTHORING: + Wrote BCP for documenting deprecated elements. + + * /cvsroot/xmlresume/resume/src/doc/manual/.cvsignore: + Added. Makes CVS ignore compiled Python bytecode files (*.pyc). + +2002-04-10 Sean Kelly + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Make 532279 actually work. + +2002-04-10 bmay + + * /cvsroot/xmlresume/resume/examples/example1.xml: + Fix last (???) name space issues, and incorrect name of example1.xml. + Thanks Bruce. Closes tracker requests 542167, and 542168 (Sean, I think + you will have to do this). + +2002-04-10 Sean Kelly + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Patch 532279: link element for hyperlinking to employers. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.phone.xml: + Typo: libarary => library. + + * /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/TEMPLATE.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/intro.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/param.address.format.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/param.css.href.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/param.header.format.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/paramref/param.skills.format.xml, /cvsroot/xmlresume/resume/src/doc/manual/entities/divisions.ent, /cvsroot/xmlresume/resume/src/doc/manual/entities/global.ent, /cvsroot/xmlresume/resume/src/doc/manual/scripts/dir2entities.py, /cvsroot/xmlresume/resume/src/doc/manual/scripts/dtddoc.py, /cvsroot/xmlresume/resume/src/doc/manual/scripts/fix_cdata_space.py, /cvsroot/xmlresume/resume/src/doc/manual/scripts/refentry.template.xml, /cvsroot/xmlresume/resume/src/doc/manual/scripts/test/dir2entities_test.py, /cvsroot/xmlresume/resume/README, /cvsroot/xmlresume/resume/build.xml, /cvsroot/xmlresume/resume/src/doc/manual/AUTHORING, /cvsroot/xmlresume/resume/src/doc/manual/README, /cvsroot/xmlresume/resume/src/doc/manual/css/manual.css, /cvsroot/xmlresume/resume/src/doc/manual/en/bookinfo.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/cssref/chapter.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.academics.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.achievement.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.achievements.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.address.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.annotation.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.artTitle.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.author.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.birth.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.bookTitle.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.break.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.citation.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.city.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.company.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.contact.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.copyright.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.country.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.county.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.date.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.dayOfMonth.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.degree.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.degrees.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.description.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.docpath.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.email.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.emphasis.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.employer.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.firstname.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.from.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.head.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.header.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.history.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.institution.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.job.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.jobtitle.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.keyword.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.keywords.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.label.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.legalnotice.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.level.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.major.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.membership.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.memberships.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.middlenames.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.misc.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.month.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.name.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.node.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.note.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.objective.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.organization.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.pageNums.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.para.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.period.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.phone.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.postalCode.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.prefecture.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.present.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.project.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.projects.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.province.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.pub.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.pubDate.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.publisher.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.pubs.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.referee.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.referees.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.result.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.resume.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.resumes.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skill.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skillarea.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skillareas.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skills.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.skillset.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.state.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.street.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.street2.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.subject.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.subjects.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.suburb.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.suffix.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.surname.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.tail.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.title.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.to.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.uri.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.url.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.ward.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.year.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/element.zip.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/elementref/intro.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/glossary.xml, /cvsroot/xmlresume/resume/src/doc/manual/en/intro.xml, /cvsroot/xmlresume/resume/src/doc/manual/manual.xml: + Patch 541347 courtesy of Bruce Christensen. + +2002-03-28 bmay + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Support for namespaces. + +2002-02-16 Sean Kelly + + * /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html: + Update changelog for 1.3.2 + + * /cvsroot/xmlresume/resume/build.xml, /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Bump version # to 1.3.2 and update news file with notes about what's + been fixed: punctuation and spacing in academic degrees and widening + FO subject list. + +2002-01-18 Sean Kelly + + * /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html: + Really update the changelog. (I shouldn't have had two martinis + before doing this. :-) + + * /cvsroot/xmlresume/resume/src/doc/release/news/index.html, /cvsroot/xmlresume/resume/src/doc/release/index.html: + Add news items about <div class="description">... + + * /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html: + Update changelog for 1.3.1. + + * /cvsroot/xmlresume/resume/build.xml, /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Bump version to 1.3.1. Add news item about big fix to catalog file. + +2002-01-17 Sean Kelly + + * /cvsroot/xmlresume/resume/src/www/dtd/catalog: Fix unbalanced "--". + +2002-01-16 Sean Kelly + + * /cvsroot/xmlresume/resume/build.xml: + Make sure the addressing dir and the .xml, README, and Makefiles go + into the release. + + * /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html: + Changelog for 1.3.0. + + * /cvsroot/xmlresume/resume/examples/Makefile, /cvsroot/xmlresume/resume/examples/example2.xml, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/Parameter.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/ResumeTest.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/ResumeTest.properties, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/Setting.java, /cvsroot/xmlresume/resume/src/www/dtd/catalog, /cvsroot/xmlresume/resume/src/www/dtd/resume.dcl, /cvsroot/xmlresume/resume/src/www/xsl/124-130.xsl: + Sigh. MS-DOS end-of-line files got in there---apparently my configuration + of Emacs, CVS, and Cygwin on Windoze 2000 is fubar'd. Convert these + back to Unix end-of-line conventions. + + * /cvsroot/xmlresume/resume/src/doc/README.src, /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Update copyright. Add news items about half.space and word wrap in + the text transformation. + + * /cvsroot/xmlresume/resume/build.xml: + Specify test target data via a property with a default value. + +2002-01-14 Sean Kelly + + * /cvsroot/xmlresume/resume/src/www/xsl/124-130.xsl: + Convert version 1.2.4 resumes into version 1.3.0 resumes. + + * /cvsroot/xmlresume/resume/src/doc/release/news/index.html, /cvsroot/xmlresume/resume/src/www/dtd/catalog, /cvsroot/xmlresume/resume/src/www/dtd/resume.dcl: + Added an SGML catalog file and declaration. Updated news accordingly. + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Make graudation <date> optional on a <degree> and format correctly if + provided or not. Add feature note to news. + + * /cvsroot/xmlresume/resume/src/doc/release/todo/index.html, /cvsroot/xmlresume/resume/src/doc/release/authors/index.html, /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html, /cvsroot/xmlresume/resume/src/doc/release/copying/index.html, /cvsroot/xmlresume/resume/src/doc/release/install/index.html, /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Update copyrights and fix HTML. + + * /cvsroot/xmlresume/resume/src/www/xsl/fr-params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/it-params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/uk-params.xsl: + Add formatting of projects, subjects, and referees. Add localized + headings. + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Add referees, subjects, projects, and referees. + + * /cvsroot/xmlresume/resume/src/www/css/resume2.css: + Add styles for references. + + * /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Add news items for memberships, projects, subjects, and attributes + features and element name change. + + * /cvsroot/xmlresume/resume/examples/example2.xml: + Add example projects, subjects, and memberships, and an example of + using the name attribute to refer to the <name> element with the + matching id attribute. + + * /cvsroot/xmlresume/resume/examples/example1.xml: + Change <subject> to <major>. Clean up <skill>s. + + * /cvsroot/xmlresume/resume/examples/Makefile: Update copyright. + + * /cvsroot/xmlresume/resume/build.xml: + Change output directory for test data generation from c:/tmp/testdata + to /tmp/testdata. + +2002-01-12 Sean Kelly + + * /cvsroot/xmlresume/resume/build.xml: + Add compilation of Java code and running of regression tests. + + * /cvsroot/xmlresume/resume/examples/example2.xml: + Add example memberships. + + * /cvsroot/xmlresume/resume/src/doc/release/news/index.html, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Feature: memberships and professional societies. + + Feature: let name in a publication refer to the <name> in the header. + + Refactoring: clean up lots of duplicated publication transformations. + + Documentation: updates about new features to date. + + * /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/Parameter.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/ResumeTest.java, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/ResumeTest.properties, /cvsroot/xmlresume/resume/src/java/net/sourceforge/xmlresume/Setting.java: + Regression tests for the XML Resume Library. + +2002-01-07 Sean Kelly + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: Add memberships. + + * /cvsroot/xmlresume/resume/examples/example1.xml, /cvsroot/xmlresume/resume/examples/example2.xml: + Add sample memberships. + + * /cvsroot/xmlresume/resume/src/doc/release/index.html: + Add documentation about CSS specifications for professional memberships. + + * /cvsroot/xmlresume/resume/src/www/css/resume1.css: + Add some sample CSS specifications for professional memberships. + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: Add memberships. + +2002-01-05 Sean Kelly + + * /cvsroot/xmlresume/resume/build.xml: Bump version # to 1.3.0. + + * /cvsroot/xmlresume/resume/examples/example1.xml, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Commit patch from b1gdave: make redundant specification of <name> in a + <copyright> unnecessary by grabbing the mandatory name from the + resume's header. You can still specify a <name> in the <copyright> if + you want to. + + Remove the <name> from example1.xml to test and demonstrate the + feature. + + * /cvsroot/xmlresume/resume/examples/Makefile: + Add XSLFLAGS and FOFLAGS parameters to command lines. + + * /cvsroot/xmlresume/resume/README: + Update release instructions to include updating of changelog file. + + * /cvsroot/xmlresume/resume/examples/example1.xml: Remove blank lines. + +2001-12-18 Stewart Evans + + * /cvsroot/xmlresume/resume/src/doc/release/header.html, /cvsroot/xmlresume/resume/src/doc/release/index.html, /cvsroot/xmlresume/resume/src/doc/release/skills.html: + added alternate formatting for skills, controlled by skills.format parameter + +2001-12-15 Stewart Evans + + * /cvsroot/xmlresume/resume/examples/example2.xml: + made address compatible with new formatting style + + * /cvsroot/xmlresume/resume/examples/addressing/Makefile, /cvsroot/xmlresume/resume/examples/addressing/README, /cvsroot/xmlresume/resume/examples/addressing/brazil.xml, /cvsroot/xmlresume/resume/examples/addressing/canada.xml, /cvsroot/xmlresume/resume/examples/addressing/ireland.xml, /cvsroot/xmlresume/resume/examples/addressing/italy.xml, /cvsroot/xmlresume/resume/examples/addressing/norway.xml, /cvsroot/xmlresume/resume/examples/addressing/nz.xml, /cvsroot/xmlresume/resume/examples/addressing/uk.xml, /cvsroot/xmlresume/resume/examples/addressing/untagged.xml, /cvsroot/xmlresume/resume/examples/addressing/usa.xml, /cvsroot/xmlresume/resume/src/doc/release/address.html, /cvsroot/xmlresume/resume/src/doc/release/header.html, /cvsroot/xmlresume/resume/src/doc/release/index.html, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/www/xsl/fr-params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/it-a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/it-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/it-params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/it-text.xsl: + New address processing: addresses are either formatted according to + predefined templates or completely free-form with linebreaks preserved. + +2001-11-18 Stewart Evans + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + add middlenames and suffix to name element. + +2001-11-07 Sean Kelly + + * /cvsroot/xmlresume/resume/build.xml: + Don't just grab everything under the examples, but instead specify + what files to put in. This helps prevent the official release from + going out with all sorts of turds that I've left in my directory. + +2001-10-28 Stewart Evans + + * /cvsroot/xmlresume/resume/src/www/xsl/fr-params.xsl: + changes suggested by Cyril Rognon (crognon) in help forum. + +2001-10-17 Stewart Evans + + * /cvsroot/xmlresume/resume/src/www/css/resume2.css: + add rule to center-align the headerBlock + +2001-09-03 Sean Kelly + + * /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html: + Update changelog for 1.2.4. + + * /cvsroot/xmlresume/resume/etc/rcs2log: Add Stewart. + + * /cvsroot/xmlresume/resume/src/doc/release/index.html, /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Fix docs. + + * /cvsroot/xmlresume/resume/examples/example2.xml: + Updated example to demonstrate inline elements in skills and + achievements and with a more complex international address. + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Update content model for achievement and skill to use same mixed model + as para, so formatting and semantics of inline elements can be used + in these locations. Update stylesheets and news file appropriately. + +2001-09-02 Sean Kelly + + * /cvsroot/xmlresume/resume/build.xml, /cvsroot/xmlresume/resume/src/doc/release/authors/index.html, /cvsroot/xmlresume/resume/src/doc/release/index.html, /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Remove "Skills" heading formatting and skills.word for <skillareas>. + Fix bullet lists of achievements; make it produce correct FO (XEP + rightly complained, but FOP let the incorrect FO go). Update + release procedure to grab examples from correct directory. + Update authors and news items. + +2001-09-01 Sean Kelly + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Stewart Evans's patches: HTML span class "employer", "nameHeading", + achievements section, real bulleted list items in text style, + formatting of the new achievements section, "skills.word" parameter, + suppression of blank fields, and formatting of contact/url in + HTML. Whoa ... that's a lot; thanks Stewart! + + * /cvsroot/xmlresume/resume/src/www/css/resume1.css, /cvsroot/xmlresume/resume/src/www/css/resume2.css: + Actually commit the sample CSS files. + + * /cvsroot/xmlresume/resume/README, /cvsroot/xmlresume/resume/build.xml, /cvsroot/xmlresume/resume/examples/Makefile, /cvsroot/xmlresume/resume/examples/example1.xml, /cvsroot/xmlresume/resume/examples/example2.xml, /cvsroot/xmlresume/resume/src/doc/release/authors/index.html, /cvsroot/xmlresume/resume/src/doc/release/index.html, /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Move examples out from under src so that developers can more easily + use them. Update developers README to reflect this. Update release + information. Add sample CSS files. + +2001-08-05 Sean Kelly + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Add content model for dayOfMonth. + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Fix reference to fullDate by using date with optional dayOfMonth field. + +2001-08-02 Sean Kelly + + * /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html: + Update changelog for 1.2.3. + + * /cvsroot/xmlresume/resume/build.xml, /cvsroot/xmlresume/resume/src/doc/release/authors/index.html, /cvsroot/xmlresume/resume/src/doc/release/index.html, /cvsroot/xmlresume/resume/src/doc/release/news/index.html, /cvsroot/xmlresume/resume/src/doc/release/todo/index.html, /cvsroot/xmlresume/resume/src/www/xsl/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/fr-a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/fr-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/fr-params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/fr-text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/uk-a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/uk-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/uk-params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/uk-text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/us-html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/us-letter.xsl, /cvsroot/xmlresume/resume/src/www/xsl/us-text.xsl: + Better parameterization support and factoring of common parameters. + Added French localization. Updated documentation for 1.2.3 release. + + * /cvsroot/xmlresume/resume/src/www/xsl/params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/uk-a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/us-letter.xsl, /cvsroot/xmlresume/resume/src/doc/release/news/index.html: + Support for internationalization: parameters for paper sizes and phrasing, + and international addresses. + +2001-07-27 Sean Kelly + + * /cvsroot/xmlresume/resume/README: + Add a note about building the examples from the developers' edition. + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: + Add Roel's suggestion to have a date of birth. + + * /cvsroot/xmlresume/resume/src/www/xsl/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/text.xsl, /cvsroot/xmlresume/resume/src/www/xsl/uk-a4.xsl, /cvsroot/xmlresume/resume/src/www/xsl/us-letter.xsl: + Parameteri[zs]e stylesheets for localization. + +2001-07-26 Sean Kelly + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/www/xsl/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/text.xsl: + Provide support for international addresses. Maintain backwards + compatibility with resumes using US style address schema. + +2001-07-17 Sean Kelly + + * /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html: + Update change log for version 1.2.2. + + * /cvsroot/xmlresume/resume/build.xml, /cvsroot/xmlresume/resume/src/doc/release/news/index.html, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/www/xsl/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/html.xsl, /cvsroot/xmlresume/resume/src/www/xsl/params.xsl, /cvsroot/xmlresume/resume/src/www/xsl/text.xsl: + Add rich content for publications, such as <bookTitle>, <author>, + <publisher>, and so forth. Update stylesheets to format these + elements. + + Add params.xsl file to contain user-overridable parameters. + + Update version number to 1.2.2. + +2001-07-11 Sean Kelly + + * /cvsroot/xmlresume/resume/src/doc/release/index.html: + Ooops ... rather important file I forgot! + +2001-07-06 Sean Kelly + + * /cvsroot/xmlresume/resume/etc/rcs2log: + This generates changelog info and is preconfigured for the current + members of the XML Resume Library team. + + * /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html: + Add changelog info. + + * /cvsroot/xmlresume/resume/README, /cvsroot/xmlresume/resume/build.xml, /cvsroot/xmlresume/resume/src/doc/README.src, /cvsroot/xmlresume/resume/src/doc/release/AUTHORS.html, /cvsroot/xmlresume/resume/src/doc/release/COPYING.html, /cvsroot/xmlresume/resume/src/doc/release/ChangeLog.html, /cvsroot/xmlresume/resume/src/doc/release/INSTALL.html, /cvsroot/xmlresume/resume/src/doc/release/NEWS.html, /cvsroot/xmlresume/resume/src/doc/release/README.html, /cvsroot/xmlresume/resume/src/doc/release/TODO.html, /cvsroot/xmlresume/resume/src/doc/release/authors/index.html, /cvsroot/xmlresume/resume/src/doc/release/changelog/index.html, /cvsroot/xmlresume/resume/src/doc/release/copying/index.html, /cvsroot/xmlresume/resume/src/doc/release/install/index.html, /cvsroot/xmlresume/resume/src/doc/release/news/index.html, /cvsroot/xmlresume/resume/src/doc/release/todo/index.html: + Break out HTML documentation into standard dir structure. + + Update version number. + + Fix release generation so it includes examples and partitions + DTD and XSL files into subdirectories. + + Incorporate lost changes into developers' README file. + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/www/xsl/fo.xsl: + Fix VERSION_DOTS generation. + + Fix accent marks on "resume" in running footer of FO stylesheet. + +2001-06-21 Sean Kelly + + * /cvsroot/xmlresume/resume/src/www/xsl/default.xsl: + Handy XSL file to have around ... formats XML into an HTML presentation + that looks like colorful XML. + + * /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd: Update FPI comment. + +2001-06-20 Sean Kelly + + * /cvsroot/xmlresume/resume/README: README for developers. + +2001-06-18 Sean Kelly + + * /cvsroot/xmlresume/resume/build.xml: + Add "install" target which, currently, installs web-accessible + XML files to the web server directory. + + * /cvsroot/xmlresume/resume/build.xml: + Cosmetic; make indentation happier for psgml mode. + + * /cvsroot/xmlresume/resume/build.xml: Remove redundant <filter> tags. + +2001-06-17 Sean Kelly + + * /cvsroot/xmlresume/resume/src/doc/README.src, /cvsroot/xmlresume/resume/src/doc/release/AUTHORS.html, /cvsroot/xmlresume/resume/src/doc/release/COPYING.html, /cvsroot/xmlresume/resume/src/doc/release/ChangeLog.html, /cvsroot/xmlresume/resume/src/doc/release/INSTALL.html, /cvsroot/xmlresume/resume/src/doc/release/NEWS.html, /cvsroot/xmlresume/resume/src/doc/release/README.html, /cvsroot/xmlresume/resume/src/doc/release/TODO.html, /cvsroot/xmlresume/resume/src/www/xsl/text.xsl: + Initial import into SourceForge CVS. + + * /cvsroot/xmlresume/resume/src/doc/README.src, /cvsroot/xmlresume/resume/src/doc/release/AUTHORS.html, /cvsroot/xmlresume/resume/src/doc/release/COPYING.html, /cvsroot/xmlresume/resume/src/doc/release/ChangeLog.html, /cvsroot/xmlresume/resume/src/doc/release/INSTALL.html, /cvsroot/xmlresume/resume/src/doc/release/NEWS.html, /cvsroot/xmlresume/resume/src/doc/release/README.html, /cvsroot/xmlresume/resume/src/doc/release/TODO.html, /cvsroot/xmlresume/resume/src/www/xsl/text.xsl: + New file. + + * /cvsroot/xmlresume/resume/build.xml, /cvsroot/xmlresume/resume/src/www/dtd/iso-lat1.ent, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/www/xsl/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/html.xsl: + Initial import into SourceForge CVS. + + * /cvsroot/xmlresume/resume/build.xml, /cvsroot/xmlresume/resume/src/www/dtd/iso-lat1.ent, /cvsroot/xmlresume/resume/src/www/dtd/resume.dtd, /cvsroot/xmlresume/resume/src/www/xsl/fo.xsl, /cvsroot/xmlresume/resume/src/www/xsl/html.xsl: + New file. + ++ + + diff --git a/legacy-resumes/resume-1/doc/copying/index.html b/legacy-resumes/resume-1/doc/copying/index.html new file mode 100644 index 0000000..b014565 --- /dev/null +++ b/legacy-resumes/resume-1/doc/copying/index.html @@ -0,0 +1,45 @@ + + + +
The XML Résumé Library copyrighted, © + 2000-2002 by Sean Kelly. All rights reserved. +
+ +Redistribution and use in source and binary forms, with or + without modification, are permitted provided that the following + conditions are met: +
+ +THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS + IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT + LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND + FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT + SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, + INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF + SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR + BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF + LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT + (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF + THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + SUCH DAMAGE. +
+ + diff --git a/legacy-resumes/resume-1/doc/index.html b/legacy-resumes/resume-1/doc/index.html new file mode 100644 index 0000000..8d3d61e --- /dev/null +++ b/legacy-resumes/resume-1/doc/index.html @@ -0,0 +1,318 @@ + + + +The XML Résumé Library is an XML Document Type + Definition (DTD) and Extensible Stylesheet Language (XSL) file + set for declaration, B2B exchange, and presentation of + résumés. +
+ +This library is copyrighted, © 2000-2002 by Sean Kelly. + See the copying conditions, + license, and disclaimer. +
+ +This is version 1.5.1, released on 27 November 2002. For the + latest version, please visit the website. +
+ +The XML Résumé Library includes the following: +
+ +dtd/resume.dtd
- An XML DTD for describing
+ résumés. To make your own
+ résumé, create an XML document that validates
+ to this DTD.
+ example2.xml
in the
+ examples
directory for a demonstration.
+ xsl/output/us-html.xsl
, xsl/output/us-text.xsl
,
+ xsl/output/us-letter.xsl
- XSLT files for transforming
+ XML résumés into HTML, plain text, and XSL
+ Formatting Objects (FO) with letter-size paper, respectively,
+ using terminology common to résumés in the
+ United States. These files let you present your
+ résumés on the web using HTML, in email or entry
+ forms that require plain text, or (after formatting with a FO
+ processor), as Portable Document Format (PDF) files suitable
+ for printing.
+ xsl/output/uk-html.xsl
, xsl/output/uk-text.xsl
,
+ xsl/output/uk-a4.xsl
- As above, but using A4 size paper
+ and terminology common to résumés in the United
+ Kingdom (such as "CV" instead of "résumé").
+ xsl/output/fr-html.xsl
, xsl/output/fr-text.xsl
,
+ xsl/output/fr-a4.xsl
- As above with A4 size paper,
+ but with terminology common to résumés in
+ France (such as "objectif professionnel" instead of
+ "professional objective").
+ br
for Brazillian, de
for German,
+ it
for Italian, and nl
for Dutch.
+ In addition, there are two example résumés and a
+ Makefile
that automates production of HTML, plain
+ text, and PDF output from an XML file using the Apache XML
+ Project tools and/or RenderX's XEP. See the
+ examples
directory.
+
The following documents are available:
+ +The XML Résumé Library uses the XML 1.0 DTD + syntax. The XSL files are version 1.0. We have tested these + files with the Apache XML + Project's tools: +
+ +In addition, the library works quite well with the Saxon XSL processor + and RenderX's XEP Formatting Objects + processor. +
+ +Use of the Résumé Filter described above requires a + Java Runtime Environment (JRE) and is known to work with version + 1.3.1 and greater. +
+ +There have been a number of changes to the DTD in version 1.4.0
+ of the XML Résumé Library. To ease migration to this new
+ version, a stylesheet, 13x-140.xsl
has been provided that
+ will automatically convert a résé from version 1.3.1, 1.3.2,
+ or 1.3.3 to the new version, 1.4.0.
+
The easiest way to use the stylesheet is with the Makefile
.
+ To convert myresume.xml to myresume-140.xml, run this command:
+
make 13x-140 resume=myresume
+
+ To create your own résumés using the XML + Résumé DTD, use the following document type + declaration in your XML file: +
+ +<!DOCTYPE resume PUBLIC "-//Sean Kelly//DTD Resume 1.5.1//EN" + "http://xmlresume.sourceforge.net/dtd/resume.dtd">+ +
If you'd rather refer to a local copy of the DTD, change the
+ system-part of the DOCTYPE to refer to it with a
+ file
URL, for example:
+
<!DOCTYPE resume PUBLIC "-//Sean Kelly//DTD Resume 1.5.1//EN" + "file:/usr/local/share/xml/dtd/resume.dtd">+ +
Note that the iso-lat1.ent
file is referenced by
+ the resume.dtd
file, so if you move one, be sure
+ you move the other, too.
+
All available tags are documented in the Element Reference in the User + Guide. +
+ +For an idea of how the tags work, see the comments in the
+ resume.dtd
file and the example
+ résumé files.
+
You can format the XML resume into HTML for online viewing, + into XSL Formatting Objects (FO) for rendering into PDF for + printing, or into plain text. +
+ +The Getting Started + section of the user guide will help you create your first XML + résumé and convert it to HTML, PDF, and plain text. It + contains a chapter on Converting an XML + Résumé to Other Formats. +
+ +To create an HTML presentation of your résumé, + run your XSLT engine on the XML file containing the + résumé along with the one of the HTML stylesheet + files: +
+us-html.xsl
for US English
+ résumés.
+ uk-html.xsl
for UK English CVs.fr-html.xsl
for French
+ résumés.The stylesheet will turn your XML résumé into + HTML using appropriate phrasing and terminology. +
+ +
+ The XSL stylesheet generates generic HTML output and abuses no
+ special HTML tricks to create special formatting effects. You
+ can use Cascading Stylesheets (CSS) to customize the output to
+ your tastes. By default, the HTML output embeds a cascading
+ stylesheet named compact.css
, located in the
+ css
directory. Other CSS files are included in the
+ same directory, you can modify these or create your own to
+ personalize your HTML résumé.
+
To specify a different stylesheet reference than
+ compact.css
, give your XSLT engine a value for the
+ css.href
parameter (how you do so depends on your
+ XSLT engine).
+
For information on the CSS classes available, and where they are used, + please consult the CSS Class + Reference in the User Guide. +
+ +To create a PDF presentation, follows these steps:
+ +us-letter.xsl
for US English
+ résumés on US-Letter size paper.
+ uk-a4.xsl
for UK English CVs on A4 size paper.
+ fr-a4.xsl
for French résumés on
+ A4 size paper.
+ This will transform your XML file into another XML file
+ that defines formatting objects (usually named with a
+ .fo
extension).
+
To create a plain text presentation, run your XSLT engine on + the résumé XML file and one of the following: +
+ +us-text.xsl
for US English plain text
+ résumés.
+ uk-text.xsl
for UK English plain text CVs.
+ fr-text.xsl
for French plain text
+ résumés.
+ To automate formatting a résumé to all three
+ output formats, consider using the Makefile
. It
+ uses the Java versions of the Apache XML tools Xerces/Xalan/FOP
+ to create both web and print presentations of a
+ résumé. Adjust the resume
value
+ in the Makefile
to point to the file name of the
+ résumeé you want to format, without the
+ .xml
extension.
+
The Makefile
is in the examples
directory.
Several parameters are available to control how a + résumé is formatted. They are documented in the XSL Parameter Reference in the User + Guide. +
+ + + diff --git a/legacy-resumes/resume-1/doc/install/index.html b/legacy-resumes/resume-1/doc/install/index.html new file mode 100644 index 0000000..307778b --- /dev/null +++ b/legacy-resumes/resume-1/doc/install/index.html @@ -0,0 +1,28 @@ + + + +The XML Résumé Library copyrighted, © + 2000-2002 by Sean Kelly. See the copying conditions, license, and + disclaimer. +
+ +The XML Résumé Library is not your typically + installed software system. Instead, it's an XML Document Type + Definition (DTD) with three Extensible Stylesheet Language (XSL) + transformation files. +
+ +See the main documentation for more + details. +
+ + + diff --git a/legacy-resumes/resume-1/doc/manual/html/appendixes.html b/legacy-resumes/resume-1/doc/manual/html/appendixes.html new file mode 100644 index 0000000..a01eacc --- /dev/null +++ b/legacy-resumes/resume-1/doc/manual/html/appendixes.html @@ -0,0 +1,4 @@ + + +Table of Contents
+ 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é. + |
academics — Container for information about academic experience
+ The academics element contains + information about a person's academic experience. +
+ academics may be contained in these + elements: + resume +
+ pubs, memberships. +
<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”). +
+ achievement may be contained in these + elements: + achievements +
<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. +
+ achievements may be contained in these + elements: + job +
+ For examples, see achievement. +
address — A postal address
(#PCDATA|street|street2|suburb|ward|city|state|province|county|prefecture|zip|postalCode|country|break)*
Name | Type | Default | |||
---|---|---|---|---|---|
format | Enumeration:
| None | |||
id | ID | None | |||
targets | CDATA | None |
+ 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. +
+ A string used to uniquely identify an address. The address may + then be referred to by this identifier. +
+ 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. +
+ address.format. +
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
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The annotation element provides + additional information about an academic degree. It could be used to + describe special honors (“Graduated summa cum laude”) or + circumstances (“Completed degree in one year in accelerated + program”). +
+ annotation may be contained in these + elements: + degree +
<degree> + <level>BS</level> + <major>Street Cleaning Technology</major> + <annotation> + Graduated with highest honors. + </annotation> +</degree>
<degree> + <level>BFA</level> + <major>Chalkboard Scratching Composition</major> + <annotation> + Received dean's award in 1984. + </annotation> +</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. +
+ artTitle may be contained in these + elements: + pub +
+ bookTitle. +
<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
(#PCDATA)
Name | Type | Default |
---|---|---|
name | IDREF | None |
targets | CDATA | None |
+ 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. +
+ author may be contained in these + elements: + pub +
+ 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>). +
+ name. +
<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
(title,organization?,(date|period)?,description?)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The award element describes + an award or other honor received by a person (e.g. “Nobel + Prize”, “MacArthur Fellow”). +
+ award may be contained in these + elements: + awards +
<award> + <title>Dean's List</title> + <organization>ACME University</organization> +</award>
<award> + <title>Honor Roll</title> + <organization>Littleton Middle School</organization> + <date> + <year>1995</year> + </date> + <description> + <para>Maintained a 4.0 GPA.</para> + </description> +</award>
awards — Container for one or more awards
+ The awards element contains one or more + awards. +
+ awards may be contained in these + elements: + resume +
<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
+ The birth element contains a single + date that specifies when a person was + born. +
+ birth may be contained in these + elements: + header +
<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. +
+ bookTitle may be contained in these + elements: + pub +
+ 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
EMPTY
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ 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. +
+ break may be contained in these + elements: + address +
+ None. +
citation — The name of a work being referenced
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ 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 +
+ pub. +
<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
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The city element contains a the name + of a single city or other similar municipality. +
+ A string used to uniquely identify a city. The city may + then be referred to by this identifier. +
+ county, prefecture, suburb, ward. +
<address> + <street>3400 N. 5230 S.</street> + <city>Salt Lake City</city> + <state>UT</state> + <zip>84352</zip> +</address>
clearance — A security clearance
(level,organization?,(date|period)?,note?)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The clearance element contains a single + security clearance (e.g. “Top Secret”). +
+ clearance may be contained in these + elements: + clearances +
<clearance> + <level>Super-duper it-doesn't-even-exist extra secret</level> + <organization>NATO</organization> +</clearance>
<clearance> + <level>Top Secret</level> + <organization>CIA</organization> + <date><year>2002</year></date> + <note>Full polygraph test performed.</note> +</clearance>
clearances — One or more security clearances
+ The clearances element contains one or + more security clearances. It is a top-level section of a résumé. +
+ clearances may be contained in these + elements: + resume +
<clearances> + <clearance> + <level>Top Secret</level> + <organization>NSA</organization> + </clearance> + <clearance> + <level>Secret</level> + <organization>US Navy</organization> + </clearance> +</clearances>
company — The name of a company
Deprecated
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ This element is deprecated as of XML Résumé Library version 1.3.3. It should + not be used. +
+ company may be contained in these + elements: + None +
+ institution, organization. +
None.
contact — Container for one or more methods of contacting someone
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The contact element is a container + that holds elements that specify how to contact a person. The + information it contains is similar to what would be printed on a + business card. +
+ address. +
<contact> + <phone>555-555-1212</phone> + <email>sam.jones@xyz.bob</email> + <url>http://www.xyz.bob/~sam.jones/</url> +</contact>
<contact> + <phone>123-123-1234 x123</phone> +</contact>
<contact> + <email>kawanza_eloma@hotmail.bob</email> +</contact>
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. +
+ copyright may be contained in these + elements: + resume +
<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>
country — A country name
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The country element marks the name of + a country. +
+ A string used to uniquely identify a country. The country may + then be referred to by this identifier. +
<address> + <city>Portland</city> + <state>Oregon</state> + <country>USA</country> +</address>
<address> + <street>2621 Green Loop</street> + <street>Southam</street> + <city>Wiggleworm</city> + <postalCode>S521 2GR</postalCode> + <country>UK</country> +</address>
county — A county name
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ 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.) +
+ A string used to uniquely identify a county. The county may + then be referred to by this identifier. +
+ state, province, prefecture. +
<address> + <city>North Willow</city> + <county>Washington</county> + <state>New Canada</state> +</address>
<address> + <street>1 O'Leary Place</street> + <city>Coby</city> + <county>Co. Cork</county> + <country>Ireland</country> +</address>
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 +
+ period. +
<date> + <dayOfMonth>27</dayOfMonth> + <month>November</month> + <year>1634</year> +</date>
<date> + <month>July</month> + <year>1457</year> +</date>
dayOfMonth — An ordinal day of the month
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ Represents a specific day in a month. Its value is numeric; the first + day of the month is written 1, the fifteenth + 15, etc. +
+ dayOfMonth may be contained in these + elements: + date +
+ For examples, see date. +
degree — Container for information about a degree or similar certification
(level,annotation?,major*,minor*,(date|period)?,(institution,location?)?,gpa?,subjects?,projects?)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The degree element is a container for + information about an academic degree (Bachelor of Science, Doctor of + Psychology, etc.) or other similar certification. +
+ degree may be contained in these + elements: + degrees +
+ A string used to uniquely identify a degree. The degree may + then be referred to by this identifier. +
<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
+ The degrees element is a container + for at least one degree. +
+ degrees may be contained in these + elements: + academics +
<degrees> + <degree> + <level>BA</level> + <major>Interstellar Basket Weaving</major> + </degree> + <degree> + <level>Ph.D</level> + <major>Aquatic Tennis Teaching</major> + </degree> +</degree>
description — An explanation of something
+ The description element specifies a + person's role, their activities, or other descriptive information. +
+ description may be contained in these + elements: + award, interest, job, membership +
+ projects, achievements. +
<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
+ This element is deprecated as of XML Résumé Library version 1.4.0. It should + not be used, and will be removed in a future version. +
+ +
+ docpath may be contained in these + elements: + resume +
<!-- TODO -->
email — An e-mail address
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The email element specifies a single + e-mail address. +
+ email may be contained in these + elements: + contact +
+ fax, instantMessage, pager, url. +
<contact> + <email>john@johnny.bob</email> + <phone>555-555-1212</phone> +</contact>
emphasis — An emphasized block of text
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ 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 +
<para> + I really, really, <emphasis>really</emphasis> want a job. +</para>
<skill> + I am <emphasis>extremely</emphasis> at using rocket-powered cheese graters. +</skill>
employer — A name of an employer
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The employer element specifies the + name of a person, company, or other entity for whom a person works or + has worked. +
+ employer may be contained in these + elements: + job +
+ A string used to uniquely identify an employer. The employer may + then be referred to by this identifier. +
+ institution, organization. +
<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
(#PCDATA)
Name | Type | Default | ||
---|---|---|---|---|
location | Enumeration:
| None | ||
targets | CDATA | None |
+ 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.) +
+ fax may be contained in these + elements: + contact +
+ Indicates the location that the phone number connects to. This + attribute is optional. +
<fax>555-555-1212</fax>
<fax location="work">(123) 456-7890</fax>
<fax location="home">345.324.2721</fax>
firstname — A person's given name
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The firstname element specifies a + person's first, or given, name. For example, in the name “Mr. + Thomas B. Jones”, the first name is “Thomas”. +
+ firstname may be contained in these + elements: + name +
+ middlenames, surname. +
<name> + <firstname>Caroline</firstname> + <surname>Francisca</surname> +</name>
from — The beginning point in a period of time
+ The from element specifies the + instant at which a given period of time begins. It is always followed by + a to element in a period. +
+ from may be contained in these + elements: + period +
+ to. +
<period> + <from> + <date> + <dayOfMonth>26</dayOfMonth> + <month>December</month> + <year>1936</year> + </date> + </from> + <to> + <date> + <dayOfMonth>14</dayOfMonth> + <month>January</month> + <year>2015</year> + </date> + </to> +</period>
gpa — Information about a grade point average
Name | Type | Default | ||
---|---|---|---|---|
targets | CDATA | None | ||
type | Enumeration:
| overall |
+ The gpa element contains a information + about a grade point average, or GPA. A GPA is a number that averages the + scores of different subjects (such as mathematics, English, history, + etc.). +
+ gpa may be contained in these + elements: + degree +
+ Indicates whether the GPA refers to all courses taken toward a + degree, or just those in the major field of study. Possible + values: overall and major. + Default is overall. +
<gpa type="major"> + <score>3.78</score> + <possible>4.00</possible> + <note>This is on a weighted scale.</note> +</gpa>
<gpa> + <score>3</score> +</gpa>
head —
Deprecated
+ This element is deprecated as of XML Résumé Library version 1.4.0. It should + not be used, and will be removed in a future version. +
+ +
+ head may be contained in these + elements: + docpath +
<!-- TODO -->
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. +
+ The header.format + parameter influences the formatting of headers in all output formats. +
+ header may be contained in these + elements: + resume +
+ header.format. +
<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 may be contained in these + elements: + resume +
<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
(#PCDATA)
Name | Type | Default |
---|---|---|
service | CDATA | None |
targets | CDATA | None |
+ The email element contains a username + or address that can be used to contact a person via an internet instant + messaging service, such as AOL Instant Messenger (AIM) or Jabber. +
+ instantMessage may be contained in these + elements: + contact +
+ Specifies the service that the username or address is to be used + with. Acceptable values are: +
AOL Instant Messenger
ICQ
Internet Relay Chat
Jabber
MSN Messenger
Yahoo! Messenger
+
+ email. +
<instantMessage service="yahoo">joesmith</instantMessage>
<instantMessage service="aim">janedoe</instantMessage>
<instantMessage service="jabber">sammybob@jabber.com</instantMessage>
institution — A name of an academic institution
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The institution element specifies the + name of a degree-awarding institution, such as a university, college, or + trade school. +
+ institution may be contained in these + elements: + degree +
+ A string used to uniquely identify an institution. The + institution may then be referred to by this identifier. +
+ organization. +
<degree> + <level>BA</level> + <major>Daisy Chain Manufacturing</major> + <institution>Harvard</institution> +</degree>
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 may be contained in these + elements: + interests +
+ skill. +
<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. +
+ The interests element is formatted as + a top-level section in a résumé. The + interests.word parameter is used as the title + text if the interests doesn't contain + a title element. +
+ Child interest elements are formatted + as a bulleted list in all output formats. +
+ interests may be contained in these + elements: + resume +
+ skillarea. +
<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
(jobtitle,employer,location?,(date|period),description?,projects?,achievements?)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The job element describes a job, + contract, or other employment engagement. +
+ job may be contained in these + elements: + history +
+ A string used to uniquely identify a job. The job may then be + referred to by this identifier. +
<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
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The jobtitle element specifies the + offical title or name of the position a person held at a job. +
+ jobtitle may be contained in these + elements: + job +
+ For examples, see job +
keyword — A keyword to be used for résumé indexing and searching
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The keyword element specifies a word + or phrase that is to be used to index and/or search a résumé, usually on + a computer. +
+ Keywords are often used to specify “buzzwords” that are not + (or that are) in the main text of the résumé, but may be used by + employers or recruiters to find résumés. +
+ keyword may be contained in these + elements: + keywords +
<keywords> + <keyword>forward-thinking</keyword> + <keyword>self-starter</keyword> + <keyword>independent</keyword> + <keyword>flexible</keyword> +</keywords>
keywords — Container for a list of keywords
+ The keywords element contains one or + more keywords. These keywords are included in the HTML presentation as + <meta name="keywords" content="..."> + tags. +
+ keywords may be contained in these + elements: + resume +
+ For examples, see keyword. +
label —
Deprecated
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ This element is deprecated as of XML Résumé Library version 1.4.0. It should + not be used, and will be removed in a future version. +
+ +
<!-- TODO -->
lastModified — Information about when a résumé was last modified
+ The lastModified element contains the + date that a résumé was last updated. +
+ lastModified may be contained in these + elements: + resume +
<lastModified> + <date> + <dayOfMonth>4</dayOfMonth> + <month>July</month> + <year>1796</year> + </date> +</lastModified>
legalnotice — A legal statement
+ The legalnotice element contains text + that is intended to specify the legal use of a résumé. +
+ legalnotice may be contained in these + elements: + copyright +
+ For examples, see copyright +
level — A degree type
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The semantic of the title element + vary depending on which element contains it: + +
+ 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”. +
+ 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
(#PCDATA)
Name | Type | Default |
---|---|---|
href | CDATA | None |
targets | CDATA | None |
+ 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 +
+ The URL that the link should point to. + then be referred to by this identifier. +
<employer> + <link href="http://www.acme.bob/">Acme Corporation</link> +</employer>
<para> + The <link href="http://xmlresume.sf.net/">XML Résumé + Project</link> supplies tools that easily convert a single XML + résumé to multiple output formats. +</employer>
location — A location, with city-level granularity
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The location element specifies a + level location, such as “London, England”, “Seattle, + Washington”, “St. Louis, Missouri, USA”, or + “Newfoundland, Canada”. +
+ location may be contained in these + elements: + degree, job, membership +
+ address. +
<location> + <city>Los Angeles<city> + <state>California</state> + <country>USA</country> +</location>
<location> + <city>Paris<city> + <country>France</country> +</location>
major — A main course of study
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The major element names the main + (“major”) course of study in a degree. A major is the area + that is focused on the most by a student. +
+ major may be contained in these + elements: + degree +
+ minor. +
+ For examples, see degree. +
membership — A professional membership
(title?,(organization,location?)?,(date|period)?,description?)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The membership element contains + information about a person's membership in a professional organization. +
+ membership may be contained in these + elements: + memberships +
+ A string used to uniquely identify a membership. The membership + may then be referred to by this identifier. +
+ For examples, see memberships. +
memberships — Container for one or more memberships
+ The memberships element contains one + or more memberships. +
+ memberships may be contained in these + elements: + resume +
<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
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The middlenames element contains all + of the names of a person, excluding their first (given) name and surname. + If the person has multiple middle names, they should be space-separated. +
+ middlenames may be contained in these + elements: + name +
<middlenames>Samione</middlenames>
<middlenames>Luís Garcia Márquez</middlenames>
minor — A minor course of study
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The major element names the main + (“major”) course of study in a degree. A major is the area + that is focused on the most by a student. +
+ minor may be contained in these + elements: + degree +
+ major. +
+ For examples, see degree. +
misc — Miscellaneous remarks
+ The misc element contains paragraphs + of text that don't fit into any other top-level categories. +
+ misc may be contained in these + elements: + resume +
<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
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The month element contains the name + of a month, such as “March” (English), “marzo” + (Spanish), or “mars” (French). +
+ dayOfMonth, year. +
<month>April</month>
name — A person's name
(title?,firstname,middlenames?,surname,suffix?)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The name element contains a person's + name. +
+ A string used to uniquely identify a name. The name may then be + referred to by this identifier. +
<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
+ This element is deprecated as of XML Résumé Library version 1.4.0. It should + not be used, and will be removed in a future version. +
+ +
+ node may be contained in these + elements: + docpath +
<!-- TODO -->
note — Additional information
+ The note element contains additional + information about its parent element. +
+ annotation, legalnotice. +
<academics> + <degrees> + ... + </degrees> + <note> + <para> + I take education very seriously. After all, I'm in 37th grade now! + </para> + </note> +</academics>
objective — A person's employment goal
+ The objective element contains a + statement of a person's goal. It commong specifies the industry or + position in which a person would like to work. +
+ objective may be contained in these + elements: + resume +
+ A string used to uniquely identify an objective. The objective + may then be referred to by this identifier. +
<objective> + <para> + I seek a high-paying job in the golf playing industry. I would like at + least 20 weeks of vacation per year. + </para> +</objective>
organization — A name of an organization
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The organization element contains the + name of a professional or other type of organization. +
+ organization may be contained in these + elements: + award, clearance, membership, referee +
+ A string used to uniquely identify an organization. The + organization may then be referred to by this identifier. +
+ institution. +
<membership> + <organization>Croquet Players' Association of the UK</organization> +</membership>
pageNums — One or more page numbers or ranges
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The pageNums element specifies one + or more page numbers or ranges of page numbers, and is used in citing a + publication. +
+ pageNums may be contained in these + elements: + pub +
<pub> + <artTitle>Ancient Mayan Anthropology</artTitle> + <bookTitle>Nature</bookTitle> + <pageNums>13-54</pageNums> +</pub>
<pub> + <artTitle>The New Fad: Bottle Cap Collecting</artTitle> + <bookTitle>Time Magazine</bookTitle> + <pageNums>14</pageNums> +</pub>
pager — A pager telephone number
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ 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.) +
+ pager may be contained in these + elements: + contact +
<pager>456-145-4468</pager>
<pager>736.272.4673 x 235</pager>
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 may be contained in these + elements: + award, clearance, degree, job, membership +
+ element. +
<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
(#PCDATA)
Name | Type | Default | |||
---|---|---|---|---|---|
location | Enumeration:
| None | |||
targets | CDATA | None |
+ 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 may be contained in these + elements: + contact +
+ Indicates the location that the phone number connects to. This + attribute is optional. +
<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
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The possible element contains a number + that indicates the highest possible score that can be attained in a GPA. + In other words, a “perfect” score. +
+ possible may be contained in these + elements: + gpa +
+ score. +
+ For examples, see gpa. +
postalCode — A postal code
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ 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. +
+ postalCode may be contained in these + elements: + address +
+ zip. +
A Brazilian postal code: +
<postalCode>85070-200</postalCode>
+
A Canadian postal code: +
<postalCode>V2B 5S8</postalCode>
+
prefecture — A name of a prefecture or other administrative district
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The prefecture element contains the + name of a prefecture or other administrative district of a city, province, + state, or other area. +
+ This element is currently ignored during formatting. +
+ prefecture may be contained in these + elements: + address +
+ A string used to uniquely identify a prefecture. The prefecture + may then be referred to by this identifier. +
<prefecture>Basilius</prefecture>
present — Indicates the current time
EMPTY
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ 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/>. +
+ date. +
<period> + <from><date> + <month>May</month> + <year>1995</year> + </from> + <to> + <present/> + </to> +</period>
project — Container for information about a project
Name | Type | Default |
---|---|---|
targets | CDATA | None |
title | CDATA | None |
+ The project element describes a + project that a person participated in at a job. +
+ project may be contained in these + elements: + projects +
+ The title of the project. +
+ achievement. +
+ For examples, see projects. +
projects — Container for one or more projects
+ The projects element groups together + one or more project elements. +
+ achievements. +
<projects> + <project>Organization of Paperclips</project> + <project>Development of rocket booster fuel</project> + <project>1997 Papercut Convention</project> +</projects>
province — A name or abbreviation of a province
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The province element contains the + name or abbreviation of a single province or similar political division. +
+ A string used to uniquely identify a province. The province may + then be referred to by this identifier. +
<province>Saskatchewan</province>
<province>BC</province>
pub — A work published by the résumé “owner”
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ 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. +
+ pub may be contained in these + elements: + pubs +
+ A string used to uniquely identify a publication. The + publication may then be referred to by this identifier. +
+ citation. +
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. +
+ pubDate may be contained in these + elements: + pub +
+ date. +
<pub> + <bookTitle>How to Drink Water for Fun and Profit</bookTitle> + <pubdate> + <year>1996</year> + </pubdate> +</pub>
<pub> + <artTitle>Modern Neo-Classical Baroque Music</bookTitle> + <bookTitle>Journal of Classical Music</bookTitle> + <pubdate> + <month>July</month> + <year>1931</year> + </pubdate> +</pub>
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. +
+ publisher may be contained in these + elements: + pub +
pubs — A group of one or more publications
+ The pubs element groups together one + or more publications. +
+ pubs may be contained in these + elements: + resume +
<pubs> + <pub> + <bookTitle>General Relativity for Idiots</bookTitle> + <author>Einstein</author> + </pub> + <pub> + <artTitle>String Theory for Dummies</artTitle> + <bookTitle>Topics in Physics</bookTitle> + <author>Stephen Hawking</author> + </pub> +</pubs>
referee — Someone who can provide additional information about the person the résumé describes
(name,title?,organization?,address?,contact?)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ 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. +
+ The display of referee is influenced + by the referees.display parameter. +
+ referee may be contained in these + elements: + referees +
<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
+ The referees element groups together + one or more referee elements. +
+ referees may be contained in these + elements: + resume +
<referees> + <referee> + <name>Mr. Samuel J. Black</name> + <contact> + <phone>555.555.1212</phone> + </contact> + </referee> + <referee> + <name>Mom</name> + <contact> + <email>my_mommy@moms.bob</email> + </contact> + </referee> + <referee> + <name>Dad</name> + </referee> +</referees>
result — An outcome of a subject
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The result element describes the + outcome or result of a subject. result often contains the letter or numeric + grade awarded for an academic class. +
+ result may be contained in these + elements: + subject +
<subjects> + <subject> + <title>Math</title> + <result>A-</result> + </subject> + <subject> + <title>English</title> + <result>C</result> + </subject> + <subject> + <title>Science</title> + <result>B+</result> + </subject> + <subject> + <title>Spanish</title> + <result>B</result> + </subject> +</subjects>
resume — A résumé or curriculum vitae
(docpath?,header?,((objective|history|academics|skillareas|skillarea|pubs|misc|referees|keywords|memberships|interests|clearances|awards))*,lastModified?,copyright?)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
xmlns | CDATA | http://xmlresume.sourceforge.net/resume/0.0 |
xmlns:xsi | CDATA | http://www.w3.org/2001/XMLSchema-instance |
xsi:schemaLocation | CDATA | None |
+ 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 may be contained in these + elements: + resumes +
+ A string used to uniquely identify a résumé. The résumé may + then be referred to by this identifier. +
<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
(resume*)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
xmlns | CDATA | http://xmlresume.sourceforge.net/resume/0.0 |
xmlns:xsi | CDATA | http://www.w3.org/2001/XMLSchema-instance |
xsi:schemaLocation | CDATA | None |
+ 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 may be contained in these + elements: + None +
+ A string used to uniquely identify a group of résumés. The + résumés may then be referred to by this identifier. +
<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
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The score element contains the GPA + score that a person has earned. +
+ score may be contained in these + elements: + gpa +
+ possible. +
+ For examples, see gpa. +
skill — A name and/or description of a skill
Name | Type | Default |
---|---|---|
id | ID | None |
level | CDATA | None |
targets | CDATA | None |
+ The skill element describes something + that a person is skilled at. +
+ 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. +
<skill>Singing</skill>
<skill level="3 years">Java Programming</skill>
<skill level="certified glutton">Eating</skill>
<skill level="beginner"> + Throwing <emphasis>large</emphasis> objects +</skill>
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. +
+ The text of skill area's title element is displayed as a + top-level heading in all output formats. Then all contained skill sets + are displayed sequentially. See skillset for information about skill + set formatting. +
+ skillarea may be contained in these + elements: + resume, skillareas +
+ A string used to uniquely identify a skill area. The skill area + may then be referred to by this identifier. +
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 may be contained in these + elements: + resume +
<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. +
+ skills may be contained in these + elements: + skillset +
+ A string used to uniquely identify a skills group. The group may + then be referred to by this identifier. +
+ skills.format. +
<skills> + <skill>Leaping over tall buildings in a single bound</skill> + <skill>Flying</skill> + <skill>Quickly changing clothes</skill> +</skill>
skillset — A titled group of one or more related skills
+ The skillset element contains a + titled set of (usually closely) related skills. +
+ The skills.format + parameter controls the formatting of skill sets. +
+ skillset may be contained in these + elements: + skillarea +
+ A string used to uniquely identify a skill set. The skill set + may then be referred to by this identifier. +
<skillset> + <title>Eating Utinsels</title> + <skill>Knife</skill> + <skill>Fork</skill> + <skill>Spoon</skill> + <skill>Soup Spoon</skill> +</skillset>
state — A name or abbreviation of a state
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The state element contains the name + or abbreviation for the name of a state or other similar political + entity. +
+ The state element represents a + division of a country. It should not be confused with the country element, which represents a + nation-state. +
+ A string used to uniquely identify a state name. The name may + then be referred to by this identifier. +
+ province, county, prefecture. +
street — A street name, number, and other related information
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The street element contains a street + name and number, a suite or apartment number, or other similar + information. +
+ Multiple street elements + are allowed. It is preferred to use multiple street elements instead of the deprecated + street2 element. +
+ street may be contained in these + elements: + address +
+ A string used to uniquely identify a street. The street may then + be referred to by this identifier. +
+ For examples, see address. +
street2 — A second line of a street address
Deprecated
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ 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. +
+ street2 may be contained in these + elements: + address +
+ A string used to uniquely identify the second line of a street + address. The line may then be referred to by this identifier. +
+ street. +
+ None. +
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). +
+ subject may be contained in these + elements: + subjects +
<subject> + <title>English</title> + <result>A-</result> +</subject>
<subject> + <title>PE 194 Crabwalking</title> + <result>F</result> +</subject>
subjects — A group of one or more subjects
+ The subjects element contains one or + more subjects that were studied as part of + the degree represented by the parent of the + subjects. +
+ subjects may be contained in these + elements: + degree +
<subjects> + <subject> + <title>Chemistry</title> + <result>C</result> + </subject> + <subject> + <title>Physics</title> + <result>B-</result> + </subject> +</subjects>
suburb — A name of a suburb
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The suburb element contains the name + of a suburb, as used by a postal service to deliver mail. +
+ suburb may be contained in these + elements: + address +
+ A string used to uniquely identify a suburb. The suburb may then + be referred to by this identifier. +
+ city, prefecture, ward. +
suffix — A suffix of a name, usually specifying lineage
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The suffix element contains a suffix + or suffix abbreviation that follows a name, such as “Jr.”, + “Senior”, or “III”. +
+ suffix may be contained in these + elements: + name +
<name> + <firstname>Leonard</firstname> + <middlenames>Scott Quink</middlenames> + <surname>Waggenblast</surname> + <suffix>IV</suffix> +</name>
<name> + <firstname>Dolores</firstname> + <surname>Sanchez</surname> + <suffix>Jr.</suffix> +</name>
surname — A family name
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The surname element contains a + person's family, or last name. +
+ surname may be contained in these + elements: + name +
+ For examples, see name. +
tail —
Deprecated
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ This element is deprecated as of XML Résumé Library version 1.4.0. It should + not be used, and will be removed in a future version. +
+ +
+ tail may be contained in these + elements: + docpath +
<!-- TODO -->
title — A title or heading
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The title element contains a title or + heading. Its semantics vary depending on the element that contains it: + +
+ When contained in this element, title contains a person's formal title, + such as “Dr.”, “Ms.”, or + “Professor”. +
+ When contained in this element, title contains the name of an interest, + such as “Cooking”, or “Politics”. +
+ 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”. +
+ 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. +
+ When contained in this element, title contains the name of a skill + category. Examples: “Teaching”, + “Computers”, “Woodworking”, + “Soap Carving”. +
+ 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
+ The to element specifies the + instant at which a given period of time ends. It is always preceeded by + a from element in a period. +
+ to may be contained in these + elements: + period +
+ from. +
uri — A Uniform Resource Indicator
Deprecated
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ This element is deprecated as of XML Résumé Library version 1.4.0. It should + not be used, and will be removed in a future version. +
+ +
<!-- TODO -->
url — A Uniform Resource Locator
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ 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 +
<para> + The Apache XML Project web page is located at + <url>http://xml.apache.org/</url>. +</para>
<skill> + Python (see <url>http://www.python.org/</url>) +</skill>
ward — A name of a division of a city, town, or county
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The ward element contains the name of + a ward, as needed to deliver mail to an address. A ward is an + administrative division a city, and of some English, Scottish, and + American counties. +
+ ward may be contained in these + elements: + address +
+ A string used to uniquely identify a ward. The ward may then be + referred to by this identifier. +
+ county, prefecture, suburb. +
<address> + <street>Rua Afonso Camargo, 805</street> + <ward>Santana</ward> + <city>Guarapuava</city> + <state>PR</state> + <postalCode>85070-200</postalCode> + <country>Brazil</country> +</address>
year — A year
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The year element contains a year + number, along with a possible string that identifies the date system, + such as “B.C.” or “A.D.”. +
<year>1995</year>
<year>240 A.D.</year>
zip — A zip code
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ 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. +
+ zip may be contained in these + elements: + address +
+ A string used to uniquely identify a zip code. The zip code may + then be referred to by this identifier. +
+ postalCode. +
+ For examples, see address. +
+ 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, 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 pub element may now contain a url + element. +
+ 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
+ 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>. +
+ 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. +
+ 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 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é. +
+ 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 + [youraddress@yourdomain.tld] in the + body to <xmlresume-devel-request@lists.sourceforge.net>. +
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 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. +
+ 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. +
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.
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.
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.
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.
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. +
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”. +
27 November 2002
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. +
+
address.format — controls default formatting of the address element
+ This parameter controls the formatting of the address element in all output + formats. +
+ 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. +
+ Formats addresses in North American layout: + +
<street>
+<street2>
+<suburb | ward>
+<city>, <state | province | county > <zip | postalCode>
+<country>
+ +
+ Formats addresses in European layout: + +
<street>
+<street2>
+<suburb | ward>
+<zip | postalCode> <city>, <state | province | county > <country>
+
+ Formats 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
+ This parameter applies to only the HTML output format. +
+ 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. +
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. +
+ Produces 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. +
+ Produces 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>
+
+ 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. +
+ +
+ 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. +
+ +
referees.display — Determines whether or not referees are visible in formatted + output
+ This parameter controls the formatting of the referee + element in all output formats. +
+ Possible values include 1 (display referees) and + 0 (display alternate text). +
+ Referees are displayed in formatted output. +
+ The text of the referees.hidden.phrase + parameter (default: Available upon request.) is + displayed in place of referees. +
skills.format — controls formatting of the skillset element
+ This parameter controls the formatting of the skillset element in all output + formats. +
+ 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). +
+ 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). +
+ 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
+ This parameter controls the formatting of the subjects element in all output formats. +
+ 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>
+ +
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
Table of Contents
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”. +
27 November 2002
Table of Contents
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. +
Table of Contents
+ 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 + [youraddress@yourdomain.tld] in the + body to <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, 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 pub element may now contain a url + element. +
+ 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
+ The academics element contains + information about a person's academic experience. +
+ academics may be contained in these + elements: + resume +
+ pubs, memberships. +
<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”). +
+ achievement may be contained in these + elements: + achievements +
<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. +
+ achievements may be contained in these + elements: + job +
+ For examples, see achievement. +
address — A postal address
(#PCDATA|street|street2|suburb|ward|city|state|province|county|prefecture|zip|postalCode|country|break)*
Name | Type | Default | |||
---|---|---|---|---|---|
format | Enumeration:
| None | |||
id | ID | None | |||
targets | CDATA | None |
+ 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. +
+ A string used to uniquely identify an address. The address may + then be referred to by this identifier. +
+ 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. +
+ address.format. +
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
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The annotation element provides + additional information about an academic degree. It could be used to + describe special honors (“Graduated summa cum laude”) or + circumstances (“Completed degree in one year in accelerated + program”). +
+ annotation may be contained in these + elements: + degree +
<degree> + <level>BS</level> + <major>Street Cleaning Technology</major> + <annotation> + Graduated with highest honors. + </annotation> +</degree>
<degree> + <level>BFA</level> + <major>Chalkboard Scratching Composition</major> + <annotation> + Received dean's award in 1984. + </annotation> +</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. +
+ artTitle may be contained in these + elements: + pub +
+ bookTitle. +
<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
(#PCDATA)
Name | Type | Default |
---|---|---|
name | IDREF | None |
targets | CDATA | None |
+ 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. +
+ author may be contained in these + elements: + pub +
+ 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>). +
+ name. +
<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
(title,organization?,(date|period)?,description?)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The award element describes + an award or other honor received by a person (e.g. “Nobel + Prize”, “MacArthur Fellow”). +
+ award may be contained in these + elements: + awards +
<award> + <title>Dean's List</title> + <organization>ACME University</organization> +</award>
<award> + <title>Honor Roll</title> + <organization>Littleton Middle School</organization> + <date> + <year>1995</year> + </date> + <description> + <para>Maintained a 4.0 GPA.</para> + </description> +</award>
awards — Container for one or more awards
+ The awards element contains one or more + awards. +
+ awards may be contained in these + elements: + resume +
<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
+ The birth element contains a single + date that specifies when a person was + born. +
+ birth may be contained in these + elements: + header +
<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. +
+ bookTitle may be contained in these + elements: + pub +
+ 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
EMPTY
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ 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. +
+ break may be contained in these + elements: + address +
+ None. +
citation — The name of a work being referenced
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ 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 +
+ pub. +
<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
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The city element contains a the name + of a single city or other similar municipality. +
+ A string used to uniquely identify a city. The city may + then be referred to by this identifier. +
+ county, prefecture, suburb, ward. +
<address> + <street>3400 N. 5230 S.</street> + <city>Salt Lake City</city> + <state>UT</state> + <zip>84352</zip> +</address>
clearance — A security clearance
(level,organization?,(date|period)?,note?)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The clearance element contains a single + security clearance (e.g. “Top Secret”). +
+ clearance may be contained in these + elements: + clearances +
<clearance> + <level>Super-duper it-doesn't-even-exist extra secret</level> + <organization>NATO</organization> +</clearance>
<clearance> + <level>Top Secret</level> + <organization>CIA</organization> + <date><year>2002</year></date> + <note>Full polygraph test performed.</note> +</clearance>
clearances — One or more security clearances
+ The clearances element contains one or + more security clearances. It is a top-level section of a résumé. +
+ clearances may be contained in these + elements: + resume +
<clearances> + <clearance> + <level>Top Secret</level> + <organization>NSA</organization> + </clearance> + <clearance> + <level>Secret</level> + <organization>US Navy</organization> + </clearance> +</clearances>
company — The name of a company
Deprecated
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ This element is deprecated as of XML Résumé Library version 1.3.3. It should + not be used. +
+ company may be contained in these + elements: + None +
+ institution, organization. +
None.
contact — Container for one or more methods of contacting someone
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The contact element is a container + that holds elements that specify how to contact a person. The + information it contains is similar to what would be printed on a + business card. +
+ address. +
<contact> + <phone>555-555-1212</phone> + <email>sam.jones@xyz.bob</email> + <url>http://www.xyz.bob/~sam.jones/</url> +</contact>
<contact> + <phone>123-123-1234 x123</phone> +</contact>
<contact> + <email>kawanza_eloma@hotmail.bob</email> +</contact>
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. +
+ copyright may be contained in these + elements: + resume +
<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>
country — A country name
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The country element marks the name of + a country. +
+ A string used to uniquely identify a country. The country may + then be referred to by this identifier. +
<address> + <city>Portland</city> + <state>Oregon</state> + <country>USA</country> +</address>
<address> + <street>2621 Green Loop</street> + <street>Southam</street> + <city>Wiggleworm</city> + <postalCode>S521 2GR</postalCode> + <country>UK</country> +</address>
county — A county name
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ 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.) +
+ A string used to uniquely identify a county. The county may + then be referred to by this identifier. +
+ state, province, prefecture. +
<address> + <city>North Willow</city> + <county>Washington</county> + <state>New Canada</state> +</address>
<address> + <street>1 O'Leary Place</street> + <city>Coby</city> + <county>Co. Cork</county> + <country>Ireland</country> +</address>
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 +
+ period. +
<date> + <dayOfMonth>27</dayOfMonth> + <month>November</month> + <year>1634</year> +</date>
<date> + <month>July</month> + <year>1457</year> +</date>
dayOfMonth — An ordinal day of the month
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ Represents a specific day in a month. Its value is numeric; the first + day of the month is written 1, the fifteenth + 15, etc. +
+ dayOfMonth may be contained in these + elements: + date +
+ For examples, see date. +
degree — Container for information about a degree or similar certification
(level,annotation?,major*,minor*,(date|period)?,(institution,location?)?,gpa?,subjects?,projects?)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The degree element is a container for + information about an academic degree (Bachelor of Science, Doctor of + Psychology, etc.) or other similar certification. +
+ degree may be contained in these + elements: + degrees +
+ A string used to uniquely identify a degree. The degree may + then be referred to by this identifier. +
<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
+ The degrees element is a container + for at least one degree. +
+ degrees may be contained in these + elements: + academics +
<degrees> + <degree> + <level>BA</level> + <major>Interstellar Basket Weaving</major> + </degree> + <degree> + <level>Ph.D</level> + <major>Aquatic Tennis Teaching</major> + </degree> +</degree>
description — An explanation of something
+ The description element specifies a + person's role, their activities, or other descriptive information. +
+ description may be contained in these + elements: + award, interest, job, membership +
+ projects, achievements. +
<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
+ This element is deprecated as of XML Résumé Library version 1.4.0. It should + not be used, and will be removed in a future version. +
+ +
+ docpath may be contained in these + elements: + resume +
<!-- TODO -->
email — An e-mail address
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The email element specifies a single + e-mail address. +
+ email may be contained in these + elements: + contact +
+ fax, instantMessage, pager, url. +
<contact> + <email>john@johnny.bob</email> + <phone>555-555-1212</phone> +</contact>
emphasis — An emphasized block of text
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ 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 +
<para> + I really, really, <emphasis>really</emphasis> want a job. +</para>
<skill> + I am <emphasis>extremely</emphasis> at using rocket-powered cheese graters. +</skill>
employer — A name of an employer
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The employer element specifies the + name of a person, company, or other entity for whom a person works or + has worked. +
+ employer may be contained in these + elements: + job +
+ A string used to uniquely identify an employer. The employer may + then be referred to by this identifier. +
+ institution, organization. +
<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
(#PCDATA)
Name | Type | Default | ||
---|---|---|---|---|
location | Enumeration:
| None | ||
targets | CDATA | None |
+ 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.) +
+ fax may be contained in these + elements: + contact +
+ Indicates the location that the phone number connects to. This + attribute is optional. +
<fax>555-555-1212</fax>
<fax location="work">(123) 456-7890</fax>
<fax location="home">345.324.2721</fax>
firstname — A person's given name
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The firstname element specifies a + person's first, or given, name. For example, in the name “Mr. + Thomas B. Jones”, the first name is “Thomas”. +
+ firstname may be contained in these + elements: + name +
+ middlenames, surname. +
<name> + <firstname>Caroline</firstname> + <surname>Francisca</surname> +</name>
from — The beginning point in a period of time
+ The from element specifies the + instant at which a given period of time begins. It is always followed by + a to element in a period. +
+ from may be contained in these + elements: + period +
+ to. +
<period> + <from> + <date> + <dayOfMonth>26</dayOfMonth> + <month>December</month> + <year>1936</year> + </date> + </from> + <to> + <date> + <dayOfMonth>14</dayOfMonth> + <month>January</month> + <year>2015</year> + </date> + </to> +</period>
gpa — Information about a grade point average
Name | Type | Default | ||
---|---|---|---|---|
targets | CDATA | None | ||
type | Enumeration:
| overall |
+ The gpa element contains a information + about a grade point average, or GPA. A GPA is a number that averages the + scores of different subjects (such as mathematics, English, history, + etc.). +
+ gpa may be contained in these + elements: + degree +
+ Indicates whether the GPA refers to all courses taken toward a + degree, or just those in the major field of study. Possible + values: overall and major. + Default is overall. +
<gpa type="major"> + <score>3.78</score> + <possible>4.00</possible> + <note>This is on a weighted scale.</note> +</gpa>
<gpa> + <score>3</score> +</gpa>
head —
Deprecated
+ This element is deprecated as of XML Résumé Library version 1.4.0. It should + not be used, and will be removed in a future version. +
+ +
+ head may be contained in these + elements: + docpath +
<!-- TODO -->
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. +
+ The header.format + parameter influences the formatting of headers in all output formats. +
+ header may be contained in these + elements: + resume +
+ header.format. +
<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 may be contained in these + elements: + resume +
<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
(#PCDATA)
Name | Type | Default |
---|---|---|
service | CDATA | None |
targets | CDATA | None |
+ The email element contains a username + or address that can be used to contact a person via an internet instant + messaging service, such as AOL Instant Messenger (AIM) or Jabber. +
+ instantMessage may be contained in these + elements: + contact +
+ Specifies the service that the username or address is to be used + with. Acceptable values are: +
AOL Instant Messenger
ICQ
Internet Relay Chat
Jabber
MSN Messenger
Yahoo! Messenger
+
+ email. +
<instantMessage service="yahoo">joesmith</instantMessage>
<instantMessage service="aim">janedoe</instantMessage>
<instantMessage service="jabber">sammybob@jabber.com</instantMessage>
institution — A name of an academic institution
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The institution element specifies the + name of a degree-awarding institution, such as a university, college, or + trade school. +
+ institution may be contained in these + elements: + degree +
+ A string used to uniquely identify an institution. The + institution may then be referred to by this identifier. +
+ organization. +
<degree> + <level>BA</level> + <major>Daisy Chain Manufacturing</major> + <institution>Harvard</institution> +</degree>
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 may be contained in these + elements: + interests +
+ skill. +
<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. +
+ The interests element is formatted as + a top-level section in a résumé. The + interests.word parameter is used as the title + text if the interests doesn't contain + a title element. +
+ Child interest elements are formatted + as a bulleted list in all output formats. +
+ interests may be contained in these + elements: + resume +
+ skillarea. +
<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
(jobtitle,employer,location?,(date|period),description?,projects?,achievements?)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The job element describes a job, + contract, or other employment engagement. +
+ job may be contained in these + elements: + history +
+ A string used to uniquely identify a job. The job may then be + referred to by this identifier. +
<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
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The jobtitle element specifies the + offical title or name of the position a person held at a job. +
+ jobtitle may be contained in these + elements: + job +
+ For examples, see job +
keyword — A keyword to be used for résumé indexing and searching
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The keyword element specifies a word + or phrase that is to be used to index and/or search a résumé, usually on + a computer. +
+ Keywords are often used to specify “buzzwords” that are not + (or that are) in the main text of the résumé, but may be used by + employers or recruiters to find résumés. +
+ keyword may be contained in these + elements: + keywords +
<keywords> + <keyword>forward-thinking</keyword> + <keyword>self-starter</keyword> + <keyword>independent</keyword> + <keyword>flexible</keyword> +</keywords>
keywords — Container for a list of keywords
+ The keywords element contains one or + more keywords. These keywords are included in the HTML presentation as + <meta name="keywords" content="..."> + tags. +
+ keywords may be contained in these + elements: + resume +
+ For examples, see keyword. +
label —
Deprecated
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ This element is deprecated as of XML Résumé Library version 1.4.0. It should + not be used, and will be removed in a future version. +
+ +
<!-- TODO -->
lastModified — Information about when a résumé was last modified
+ The lastModified element contains the + date that a résumé was last updated. +
+ lastModified may be contained in these + elements: + resume +
<lastModified> + <date> + <dayOfMonth>4</dayOfMonth> + <month>July</month> + <year>1796</year> + </date> +</lastModified>
legalnotice — A legal statement
+ The legalnotice element contains text + that is intended to specify the legal use of a résumé. +
+ legalnotice may be contained in these + elements: + copyright +
+ For examples, see copyright +
level — A degree type
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The semantic of the title element + vary depending on which element contains it: + +
+ 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”. +
+ 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
(#PCDATA)
Name | Type | Default |
---|---|---|
href | CDATA | None |
targets | CDATA | None |
+ 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 +
+ The URL that the link should point to. + then be referred to by this identifier. +
<employer> + <link href="http://www.acme.bob/">Acme Corporation</link> +</employer>
<para> + The <link href="http://xmlresume.sf.net/">XML Résumé + Project</link> supplies tools that easily convert a single XML + résumé to multiple output formats. +</employer>
location — A location, with city-level granularity
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The location element specifies a + level location, such as “London, England”, “Seattle, + Washington”, “St. Louis, Missouri, USA”, or + “Newfoundland, Canada”. +
+ location may be contained in these + elements: + degree, job, membership +
+ address. +
<location> + <city>Los Angeles<city> + <state>California</state> + <country>USA</country> +</location>
<location> + <city>Paris<city> + <country>France</country> +</location>
major — A main course of study
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The major element names the main + (“major”) course of study in a degree. A major is the area + that is focused on the most by a student. +
+ major may be contained in these + elements: + degree +
+ minor. +
+ For examples, see degree. +
membership — A professional membership
(title?,(organization,location?)?,(date|period)?,description?)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The membership element contains + information about a person's membership in a professional organization. +
+ membership may be contained in these + elements: + memberships +
+ A string used to uniquely identify a membership. The membership + may then be referred to by this identifier. +
+ For examples, see memberships. +
memberships — Container for one or more memberships
+ The memberships element contains one + or more memberships. +
+ memberships may be contained in these + elements: + resume +
<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
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The middlenames element contains all + of the names of a person, excluding their first (given) name and surname. + If the person has multiple middle names, they should be space-separated. +
+ middlenames may be contained in these + elements: + name +
<middlenames>Samione</middlenames>
<middlenames>Luís Garcia Márquez</middlenames>
minor — A minor course of study
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The major element names the main + (“major”) course of study in a degree. A major is the area + that is focused on the most by a student. +
+ minor may be contained in these + elements: + degree +
+ major. +
+ For examples, see degree. +
misc — Miscellaneous remarks
+ The misc element contains paragraphs + of text that don't fit into any other top-level categories. +
+ misc may be contained in these + elements: + resume +
<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
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The month element contains the name + of a month, such as “March” (English), “marzo” + (Spanish), or “mars” (French). +
+ dayOfMonth, year. +
<month>April</month>
name — A person's name
(title?,firstname,middlenames?,surname,suffix?)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The name element contains a person's + name. +
+ A string used to uniquely identify a name. The name may then be + referred to by this identifier. +
<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
+ This element is deprecated as of XML Résumé Library version 1.4.0. It should + not be used, and will be removed in a future version. +
+ +
+ node may be contained in these + elements: + docpath +
<!-- TODO -->
note — Additional information
+ The note element contains additional + information about its parent element. +
+ annotation, legalnotice. +
<academics> + <degrees> + ... + </degrees> + <note> + <para> + I take education very seriously. After all, I'm in 37th grade now! + </para> + </note> +</academics>
objective — A person's employment goal
+ The objective element contains a + statement of a person's goal. It commong specifies the industry or + position in which a person would like to work. +
+ objective may be contained in these + elements: + resume +
+ A string used to uniquely identify an objective. The objective + may then be referred to by this identifier. +
<objective> + <para> + I seek a high-paying job in the golf playing industry. I would like at + least 20 weeks of vacation per year. + </para> +</objective>
organization — A name of an organization
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The organization element contains the + name of a professional or other type of organization. +
+ organization may be contained in these + elements: + award, clearance, membership, referee +
+ A string used to uniquely identify an organization. The + organization may then be referred to by this identifier. +
+ institution. +
<membership> + <organization>Croquet Players' Association of the UK</organization> +</membership>
pageNums — One or more page numbers or ranges
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The pageNums element specifies one + or more page numbers or ranges of page numbers, and is used in citing a + publication. +
+ pageNums may be contained in these + elements: + pub +
<pub> + <artTitle>Ancient Mayan Anthropology</artTitle> + <bookTitle>Nature</bookTitle> + <pageNums>13-54</pageNums> +</pub>
<pub> + <artTitle>The New Fad: Bottle Cap Collecting</artTitle> + <bookTitle>Time Magazine</bookTitle> + <pageNums>14</pageNums> +</pub>
pager — A pager telephone number
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ 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.) +
+ pager may be contained in these + elements: + contact +
<pager>456-145-4468</pager>
<pager>736.272.4673 x 235</pager>
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 may be contained in these + elements: + award, clearance, degree, job, membership +
+ element. +
<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
(#PCDATA)
Name | Type | Default | |||
---|---|---|---|---|---|
location | Enumeration:
| None | |||
targets | CDATA | None |
+ 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 may be contained in these + elements: + contact +
+ Indicates the location that the phone number connects to. This + attribute is optional. +
<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
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The possible element contains a number + that indicates the highest possible score that can be attained in a GPA. + In other words, a “perfect” score. +
+ possible may be contained in these + elements: + gpa +
+ score. +
+ For examples, see gpa. +
postalCode — A postal code
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ 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. +
+ postalCode may be contained in these + elements: + address +
+ zip. +
A Brazilian postal code: +
<postalCode>85070-200</postalCode>
+
A Canadian postal code: +
<postalCode>V2B 5S8</postalCode>
+
prefecture — A name of a prefecture or other administrative district
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The prefecture element contains the + name of a prefecture or other administrative district of a city, province, + state, or other area. +
+ This element is currently ignored during formatting. +
+ prefecture may be contained in these + elements: + address +
+ A string used to uniquely identify a prefecture. The prefecture + may then be referred to by this identifier. +
<prefecture>Basilius</prefecture>
present — Indicates the current time
EMPTY
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ 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/>. +
+ date. +
<period> + <from><date> + <month>May</month> + <year>1995</year> + </from> + <to> + <present/> + </to> +</period>
project — Container for information about a project
Name | Type | Default |
---|---|---|
targets | CDATA | None |
title | CDATA | None |
+ The project element describes a + project that a person participated in at a job. +
+ project may be contained in these + elements: + projects +
+ The title of the project. +
+ achievement. +
+ For examples, see projects. +
projects — Container for one or more projects
+ The projects element groups together + one or more project elements. +
+ achievements. +
<projects> + <project>Organization of Paperclips</project> + <project>Development of rocket booster fuel</project> + <project>1997 Papercut Convention</project> +</projects>
province — A name or abbreviation of a province
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The province element contains the + name or abbreviation of a single province or similar political division. +
+ A string used to uniquely identify a province. The province may + then be referred to by this identifier. +
<province>Saskatchewan</province>
<province>BC</province>
pub — A work published by the résumé “owner”
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ 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. +
+ pub may be contained in these + elements: + pubs +
+ A string used to uniquely identify a publication. The + publication may then be referred to by this identifier. +
+ citation. +
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. +
+ pubDate may be contained in these + elements: + pub +
+ date. +
<pub> + <bookTitle>How to Drink Water for Fun and Profit</bookTitle> + <pubdate> + <year>1996</year> + </pubdate> +</pub>
<pub> + <artTitle>Modern Neo-Classical Baroque Music</bookTitle> + <bookTitle>Journal of Classical Music</bookTitle> + <pubdate> + <month>July</month> + <year>1931</year> + </pubdate> +</pub>
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. +
+ publisher may be contained in these + elements: + pub +
pubs — A group of one or more publications
+ The pubs element groups together one + or more publications. +
+ pubs may be contained in these + elements: + resume +
<pubs> + <pub> + <bookTitle>General Relativity for Idiots</bookTitle> + <author>Einstein</author> + </pub> + <pub> + <artTitle>String Theory for Dummies</artTitle> + <bookTitle>Topics in Physics</bookTitle> + <author>Stephen Hawking</author> + </pub> +</pubs>
referee — Someone who can provide additional information about the person the résumé describes
(name,title?,organization?,address?,contact?)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ 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. +
+ The display of referee is influenced + by the referees.display parameter. +
+ referee may be contained in these + elements: + referees +
<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
+ The referees element groups together + one or more referee elements. +
+ referees may be contained in these + elements: + resume +
<referees> + <referee> + <name>Mr. Samuel J. Black</name> + <contact> + <phone>555.555.1212</phone> + </contact> + </referee> + <referee> + <name>Mom</name> + <contact> + <email>my_mommy@moms.bob</email> + </contact> + </referee> + <referee> + <name>Dad</name> + </referee> +</referees>
result — An outcome of a subject
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The result element describes the + outcome or result of a subject. result often contains the letter or numeric + grade awarded for an academic class. +
+ result may be contained in these + elements: + subject +
<subjects> + <subject> + <title>Math</title> + <result>A-</result> + </subject> + <subject> + <title>English</title> + <result>C</result> + </subject> + <subject> + <title>Science</title> + <result>B+</result> + </subject> + <subject> + <title>Spanish</title> + <result>B</result> + </subject> +</subjects>
resume — A résumé or curriculum vitae
(docpath?,header?,((objective|history|academics|skillareas|skillarea|pubs|misc|referees|keywords|memberships|interests|clearances|awards))*,lastModified?,copyright?)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
xmlns | CDATA | http://xmlresume.sourceforge.net/resume/0.0 |
xmlns:xsi | CDATA | http://www.w3.org/2001/XMLSchema-instance |
xsi:schemaLocation | CDATA | None |
+ 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 may be contained in these + elements: + resumes +
+ A string used to uniquely identify a résumé. The résumé may + then be referred to by this identifier. +
<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
(resume*)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
xmlns | CDATA | http://xmlresume.sourceforge.net/resume/0.0 |
xmlns:xsi | CDATA | http://www.w3.org/2001/XMLSchema-instance |
xsi:schemaLocation | CDATA | None |
+ 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 may be contained in these + elements: + None +
+ A string used to uniquely identify a group of résumés. The + résumés may then be referred to by this identifier. +
<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
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The score element contains the GPA + score that a person has earned. +
+ score may be contained in these + elements: + gpa +
+ possible. +
+ For examples, see gpa. +
skill — A name and/or description of a skill
Name | Type | Default |
---|---|---|
id | ID | None |
level | CDATA | None |
targets | CDATA | None |
+ The skill element describes something + that a person is skilled at. +
+ 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. +
<skill>Singing</skill>
<skill level="3 years">Java Programming</skill>
<skill level="certified glutton">Eating</skill>
<skill level="beginner"> + Throwing <emphasis>large</emphasis> objects +</skill>
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. +
+ The text of skill area's title element is displayed as a + top-level heading in all output formats. Then all contained skill sets + are displayed sequentially. See skillset for information about skill + set formatting. +
+ skillarea may be contained in these + elements: + resume, skillareas +
+ A string used to uniquely identify a skill area. The skill area + may then be referred to by this identifier. +
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 may be contained in these + elements: + resume +
<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. +
+ skills may be contained in these + elements: + skillset +
+ A string used to uniquely identify a skills group. The group may + then be referred to by this identifier. +
+ skills.format. +
<skills> + <skill>Leaping over tall buildings in a single bound</skill> + <skill>Flying</skill> + <skill>Quickly changing clothes</skill> +</skill>
skillset — A titled group of one or more related skills
+ The skillset element contains a + titled set of (usually closely) related skills. +
+ The skills.format + parameter controls the formatting of skill sets. +
+ skillset may be contained in these + elements: + skillarea +
+ A string used to uniquely identify a skill set. The skill set + may then be referred to by this identifier. +
<skillset> + <title>Eating Utinsels</title> + <skill>Knife</skill> + <skill>Fork</skill> + <skill>Spoon</skill> + <skill>Soup Spoon</skill> +</skillset>
state — A name or abbreviation of a state
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The state element contains the name + or abbreviation for the name of a state or other similar political + entity. +
+ The state element represents a + division of a country. It should not be confused with the country element, which represents a + nation-state. +
+ A string used to uniquely identify a state name. The name may + then be referred to by this identifier. +
+ province, county, prefecture. +
street — A street name, number, and other related information
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The street element contains a street + name and number, a suite or apartment number, or other similar + information. +
+ Multiple street elements + are allowed. It is preferred to use multiple street elements instead of the deprecated + street2 element. +
+ street may be contained in these + elements: + address +
+ A string used to uniquely identify a street. The street may then + be referred to by this identifier. +
+ For examples, see address. +
street2 — A second line of a street address
Deprecated
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ 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. +
+ street2 may be contained in these + elements: + address +
+ A string used to uniquely identify the second line of a street + address. The line may then be referred to by this identifier. +
+ street. +
+ None. +
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). +
+ subject may be contained in these + elements: + subjects +
<subject> + <title>English</title> + <result>A-</result> +</subject>
<subject> + <title>PE 194 Crabwalking</title> + <result>F</result> +</subject>
subjects — A group of one or more subjects
+ The subjects element contains one or + more subjects that were studied as part of + the degree represented by the parent of the + subjects. +
+ subjects may be contained in these + elements: + degree +
<subjects> + <subject> + <title>Chemistry</title> + <result>C</result> + </subject> + <subject> + <title>Physics</title> + <result>B-</result> + </subject> +</subjects>
suburb — A name of a suburb
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The suburb element contains the name + of a suburb, as used by a postal service to deliver mail. +
+ suburb may be contained in these + elements: + address +
+ A string used to uniquely identify a suburb. The suburb may then + be referred to by this identifier. +
+ city, prefecture, ward. +
suffix — A suffix of a name, usually specifying lineage
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The suffix element contains a suffix + or suffix abbreviation that follows a name, such as “Jr.”, + “Senior”, or “III”. +
+ suffix may be contained in these + elements: + name +
<name> + <firstname>Leonard</firstname> + <middlenames>Scott Quink</middlenames> + <surname>Waggenblast</surname> + <suffix>IV</suffix> +</name>
<name> + <firstname>Dolores</firstname> + <surname>Sanchez</surname> + <suffix>Jr.</suffix> +</name>
surname — A family name
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The surname element contains a + person's family, or last name. +
+ surname may be contained in these + elements: + name +
+ For examples, see name. +
tail —
Deprecated
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ This element is deprecated as of XML Résumé Library version 1.4.0. It should + not be used, and will be removed in a future version. +
+ +
+ tail may be contained in these + elements: + docpath +
<!-- TODO -->
title — A title or heading
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The title element contains a title or + heading. Its semantics vary depending on the element that contains it: + +
+ When contained in this element, title contains a person's formal title, + such as “Dr.”, “Ms.”, or + “Professor”. +
+ When contained in this element, title contains the name of an interest, + such as “Cooking”, or “Politics”. +
+ 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”. +
+ 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. +
+ When contained in this element, title contains the name of a skill + category. Examples: “Teaching”, + “Computers”, “Woodworking”, + “Soap Carving”. +
+ 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
+ The to element specifies the + instant at which a given period of time ends. It is always preceeded by + a from element in a period. +
+ to may be contained in these + elements: + period +
+ from. +
uri — A Uniform Resource Indicator
Deprecated
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ This element is deprecated as of XML Résumé Library version 1.4.0. It should + not be used, and will be removed in a future version. +
+ +
<!-- TODO -->
url — A Uniform Resource Locator
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ 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 +
<para> + The Apache XML Project web page is located at + <url>http://xml.apache.org/</url>. +</para>
<skill> + Python (see <url>http://www.python.org/</url>) +</skill>
ward — A name of a division of a city, town, or county
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ The ward element contains the name of + a ward, as needed to deliver mail to an address. A ward is an + administrative division a city, and of some English, Scottish, and + American counties. +
+ ward may be contained in these + elements: + address +
+ A string used to uniquely identify a ward. The ward may then be + referred to by this identifier. +
+ county, prefecture, suburb. +
<address> + <street>Rua Afonso Camargo, 805</street> + <ward>Santana</ward> + <city>Guarapuava</city> + <state>PR</state> + <postalCode>85070-200</postalCode> + <country>Brazil</country> +</address>
year — A year
(#PCDATA)
Name | Type | Default |
---|---|---|
targets | CDATA | None |
+ The year element contains a year + number, along with a possible string that identifies the date system, + such as “B.C.” or “A.D.”. +
<year>1995</year>
<year>240 A.D.</year>
zip — A zip code
(#PCDATA)
Name | Type | Default |
---|---|---|
id | ID | None |
targets | CDATA | None |
+ 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. +
+ zip may be contained in these + elements: + address +
+ A string used to uniquely identify a zip code. The zip code may + then be referred to by this identifier. +
+ postalCode. +
+ For examples, see address. +
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
+ This parameter controls the formatting of the address element in all output + formats. +
+ 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. +
+ Formats addresses in North American layout: + +
<street>
+<street2>
+<suburb | ward>
+<city>, <state | province | county > <zip | postalCode>
+<country>
+ +
+ Formats addresses in European layout: + +
<street>
+<street2>
+<suburb | ward>
+<zip | postalCode> <city>, <state | province | county > <country>
+
+ Formats 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
+ This parameter applies to only the HTML output format. +
+ 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. +
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. +
+ Produces 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. +
+ Produces 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>
+
+ 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. +
+ +
+ 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. +
+ +
referees.display — Determines whether or not referees are visible in formatted + output
+ This parameter controls the formatting of the referee + element in all output formats. +
+ Possible values include 1 (display referees) and + 0 (display alternate text). +
+ Referees are displayed in formatted output. +
+ The text of the referees.hidden.phrase + parameter (default: Available upon request.) is + displayed in place of referees. +
skills.format — controls formatting of the skillset element
+ This parameter controls the formatting of the skillset element in all output + formats. +
+ 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). +
+ 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). +
+ 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
+ This parameter controls the formatting of the subjects element in all output formats. +
+ 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>
+ +
Table of Contents
+ 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
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.
The XML Résumé Library copyrighted, © + 2000-2002 by Sean Kelly. See the copying conditions, license, and + disclaimer. +
+ +This document lists user-visible changes to the library. +
+ +This document does not list all DTD changes, nor does it give complete + detail on those that it does list. For a full list of changes to the DTD, + please see the Element Reference + in the User Guide. +
+ +example/example2.xml
examples
directory) has been
+ added for using XMLMind's XFC package or the JFOR package to
+ produce RTF output. This requires a separate download and is not
+ strongly supported by the XMLRésumé Project.
+ (Thanks to James Manning)compact.css
that can be used
+ to easily open an HTML résumé in Microsoft Word and save
+ it as a DOC file. (Contributed by Mark Miller.)us-html.xsl
,
+ br-a4.xsl
, etc.) are now in the xsl/output
+ directory. (They were previously in the xsl
directory.<clearances>
+ and
+ <clearance>
.
+ These elements may be used to note security clearances that you may
+ have.
+ (Feature request 556633.)<gpa>
,
+ <score>
+ and
+ <possible>
.
+ You can use these tags to include a GPA in a degree.
+ résumé.
+ (Feature request 560641.)<location>
.
+ This element can be used to indicate the city of a
+ <job>
,
+ <degree>
,
+ or
+ <membership>
.
+ (Feature request 505444.)<name>
+ may now contain an optional
+ <title>
.
+ <institution>
+ and
+ <organization>
+ may now contain inline elements.
+ <awards>
+ and
+ <award>
.
+ You can use these tags to include awards or other honors in a
+ résumé.
+ (Feature request 548619.)<interests>
+ and
+ <interest>
.
+ You can use these tags to include your interests or hobbies in a
+ résumé.
+ (Feature request 504269.)<fax>
,
+ <pager>
,
+ and
+ <instantMessage>
+ (feature requests 485930 and 522200).<minor>
+ (feature request 558871).<lastModified>
+ (feature request 460165).<skillareas>
,
+ <skills>
,
+ and
+ <pubDate>
.<phone>
+ (as well as the new <fax>
element) now has a
+ location
attribute (feature request 448039).<skill>
+ now has a level
attribute (feature request 485930).<degree>
+ may now contain multiple
+ <major>
s
+ (feature request 558871).<contact>
+ may now contain any number of elements, in any order (feature request 448039).<pub>
+ may now contain a
+ <url>
+ (feature request 548584).<degree>
+ may now optionally contain either a
+ <date>
or a
+ <period>
+ (feature requests 485930 and 460156).<referee>
+ may now contain an optional
+ <title>
+ and an optional
+ <organization>
+ (feature request 539028).referees.display
parameter.resume3.css
skills.format
parameter was set to
+ comma
.<link>
element to support hyperlinks to employers.Bug fix release:
+ +This release fixes a minor bug in the catalog file for the DTD.
+ It also puts descriptions in the HTML output into a
+ <div>
block with the CSS class description,
+ enabling you to format descriptions of jobs specially.
+
<subject>
element under a
+ <degree>
in order to list your college
+ major is now a <major>
element. You will
+ need to change your résumés and/or software.
+
+ As a convenience, we have provided an XSLT transformation
+ in xsl/124-130.xsl
that will turn version 1.2.4
+ résumés into 1.3.0 with the
+ <major>
element.
+
<name>
under a
+ <copyright>
is now optional. If omitted,
+ the name will be taken from the <header>
.
+ header.format
parameter.
+ skills.format
+ parameter.
+ address.format
parameter and also by allowing
+ freeform addresses.
+ <memberships>
+ element.
+ <subjects>
element. Subjects are
+ formatted for print and web, but not yet for text.
+ <referees>
element.
+ id
attributes
+ now. You can use the name
attribute in an
+ <author>
element to refer to a publication
+ author by id
.
+ <projects>
element.
+ <date>
on a degree is
+ optional now.
+ half.space
is used for a
+ smaller amount of space between certain types of paragraphs.
+ Additionally, we've fixed some bugs in the XSL files.
+ +Bugs fixed:
+<dayOfMonth>
was missing a content
+ model; it has one now (PCDATA).
+ <fullDate>
wasn't referenced anywhere.
+ It's gone.
+ text.xsl
+ contained an invalid template that Xalan allowed but 4Suite
+ correctly disallowed. That's fixed now.
+ New features:
+resume1.css
and resume2.css
are in
+ the css
directory.
+ example2.xml
résumé for an
+ example. Older résumés using the US address
+ schema are still compatible. Note that FOP 0.19.0
+ does not handle line breaks in addresses correctly yet. Use
+ XEP from RenderX until
+ the Apache XML Project can fix this bug!
+ <birth>
element to record date of birth.
+ This element is currently not formatted.
+ This release lets you specify rich content for publications in
+ addition to free-form paragraphs, including
+ <artTitle>
, <bookTitle>
,
+ <author>
, <pubDate>
,
+ <publisher>
, and
+ <pageNums>
. The stylesheets will format
+ these elements appropriately.
+
The news document is new in this release, 1.2.0. +
+ + + diff --git a/legacy-resumes/resume-1/doc/todo/index.html b/legacy-resumes/resume-1/doc/todo/index.html new file mode 100644 index 0000000..4315f68 --- /dev/null +++ b/legacy-resumes/resume-1/doc/todo/index.html @@ -0,0 +1,47 @@ + + + +The XML Résumé Library copyrighted, © + 2000-2002 by Sean Kelly. See the copying conditions, license, and + disclaimer. +
+ +Below are a few suggestions. There's also a whole list of user-submitted + at feature + requests on the SourceForge project page.
+ +zip
element should be renamed to postalcode deprecated (bug 632271)<present/>
structure is kind of odd.
+ 123 Elm #456
Garbonzoville, NX 99999-9999
Phone: 555.555.5555
Email: doe@doe.doe
URL: http://doe.com/~doe/
I really, really, really, really want a + job. +
Senior Toilet Cleaner
HM Secret Service
August 1943-Present
Cleaned out public lavoratories using my toothbrush. + Assissted with enterprise resource planning. +
Junior Bedpan Cleaner
Framingham Palace
October 1633-October 1634
Analyzed bedpan cleanliness strategies for royal + family. Learned how to make soufflés. +
Speak multiple European languages with no discernable accent, Able to predict earthquakes.
So there!
El Monte, CA
Mobile Phone: 818.280.7059
Email: charles@knownelement.com
URL: http://www.knownelement.com/
+ I’m looking to reduce costs and improve efficiency in an IT service delivery organization, + by rapidly sourcing and fielding whatever is necessary to get the job done on time and within budget. +
Linux systems engineer with extensive knowledge/experience on both Debian and RedHat based Linux distributions in a wide variety of applications. Very comfortable with shell scripting, package management, user account administration, configuration management, etc. A frequent speaker/writer on a wide variety of IT and open source matters, as well as a frequent contributer to open source projects.
Core IT infrastructure: Daily administration tasks in support of Mailman, Postfix, Bind, PXE boot (Debian Fully Automated Install (FAI) and Red Hat Kickstart on both Xen guests and physical hardware.
Linux Server Applications: Debian and Ubuntu / Red Hat Enterprise Linux (3/4/5) shell scripting/automation (bash/sed/awk) assisting tier3 support with software debugging (PHP/Python/Perl/Java) Apache 1.30/2.0/2.2 Postfix and Courier Samba/ProfFTPD IpTables/Snort/Nessus/Nmap/OpenVAS.
Networking (switches, load balancers and security): F5/BigIP Global Traffic Manager and Local Traffic Manager Cisco LocalDirector, 2600/1800 series routers, 3745/2900 switches Linux Virtual Server (LVS) IPTables, Snort, ClamAV OpenVPN.
Monitoring: Nagios, HP OpenView, HP SiteScope and What’s Up Gold.
Storage: Hewlett Packard SAN (20 terabytes total storage supporting VmWare workloads) EMC Clarion cx400 and cx700 (200 terabytes total storage supporting Oracle/MySQL/SQL server workloads) Promise and Equallogic iSCSI Network Attached Storage (100 terabytes total storage supporting near line storage and development workloads) NFS on Linux supporting distributed web work loads.
Other: Basic systems administration of HP-UX 11i Basic systems administration of Solaris 8/9/10/opensolaris Panther CDN ATT Edge Cache Akamai VmWare Virtual Infrastructure 3.5 XEN KVM/Qemu/Virtual Server/OpenVZ/VmWare Server.
Linux System Engineer
Targetcast Networks (via acquisition of RippleTV)
October 2008-January 2010
+ Provided system engineering expertise for customer facing advertising platform (AdSpot) and internal fleet management tool (CPanel). + Utilized Nginx, Mongrel, Thin, Rails, Merb, Rack, MySQL (with replication), memcached and slack to support 2000+ systems. +
Linux, Windows, network and security consulting
Multiple entities including Cast And Crew Entertainment Services Inc, Evite.com and Siderean Software
September 2007-October 2008
+ Provided Linux and Cisco systems engineering expertise for Evite.com, across 2 geographically dispersed data centers supporting + 10 million visitors and 2 million e-mails per day. Utilized Apache/Tomcat on Gentoo and Ubuntu. +
+ Provided Linux systems engineering expertise for Cast And Crew Entertainment Services. Utilized Centos to host several green screen + and J2EE web based applications for payroll processing. +
+ Provided Linux systems engineering expertise for Siderean Software. Utilized Fedora and Centos on dedicated hardware and ec2 to + host numerous web properties including sites for Oracle Software. +
Linux/Windows System Engineer
The Walt Disney Company - Parks and Resorts Online - Walt Disney Internet Group
August 2006-September 2007
+ Provided system engineering and PCI compliance expertise for Disneyland.com, Disneyworld.com, DisneyCruiseLines.com + and 23 related properties generating 2 billion dollars a year. Business logic was handled by Jboss instances on RHEL3/4 + and frontend application serving was done via Windows 2003 and Tomcat/IIS. +
Linux Systems Engineer
Intuit Inc (via acquistion of Electronic Clearing House)
October 2005-June 2006
+ Linux systems engineer for a 24x7 transaction processing/ecommerce/ + financial services environment. Responsibilities included working closely + with the network administration and infrastructure design teams and ensuring continuous + uptime of multiple high visibility/high impact/high value envrironments including + + 1TB MySQL database, 300 TB Oracle database, 1.5 TB Oracle Data warehouse and a + 4,000-store LAMP based ecommerce system (MerchantAmerica.com). +
Projects:
Linux, Windows, network and security consulting for various startups and defense contractors
Multiple entities
February 2005-October 2005
Projects:
Linux/Windows Systems Engineer
GSI Commerce (via acquisition of Newroads Inc)
July 2002-February 2005
Projects:
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ |
+
+ |
+
+
+
+
+
+
+
+ --> +
+ ]]> +
+ |
+
+ |
+
+ + + |
+
+
+
+ |
+
+
+ |
+
+
+
+ |
+
+
+ |
+
+
+
+ |
+
+
+ |
+
+
+ |
+ |
+ + |
+ |
+
+
+
+
+
+
+
+
+
+
+ |
+
+
+ |
+
+ |
+
+ |
+
+ + + |
+
+
+ |
+
+
+ |
+
+
+ |
+
+
+ |
+
+
+ |
+
+
+ |
+
+
+ |
+ |
+ + |
+ |
+
+
+
+
+
+
+
+
+
+
+ |
+
+
+ |
+