diff --git a/CurrentResume/common/@ReachableCEO/Resume/Common/Contact-Info.md b/common/@ReachableCEO/Resume/Common/Contact-Info.md similarity index 100% rename from CurrentResume/common/@ReachableCEO/Resume/Common/Contact-Info.md rename to common/@ReachableCEO/Resume/Common/Contact-Info.md diff --git a/CurrentResume/common/@ReachableCEO/Resume/Common/Education.md b/common/@ReachableCEO/Resume/Common/Education.md similarity index 100% rename from CurrentResume/common/@ReachableCEO/Resume/Common/Education.md rename to common/@ReachableCEO/Resume/Common/Education.md diff --git a/CurrentResume/common/@ReachableCEO/Resume/Common/Skills.md b/common/@ReachableCEO/Resume/Common/Skills.md similarity index 100% rename from CurrentResume/common/@ReachableCEO/Resume/Common/Skills.md rename to common/@ReachableCEO/Resume/Common/Skills.md diff --git a/CurrentResume/common/HumanOutput.yml b/common/HumanOutput.yml similarity index 86% rename from CurrentResume/common/HumanOutput.yml rename to common/HumanOutput.yml index cc0465e..8f99441 100644 --- a/CurrentResume/common/HumanOutput.yml +++ b/common/HumanOutput.yml @@ -5,7 +5,7 @@ date: \today header-left: "\\hspace{1cm}" header-center: "\\leftmark" header-right: "Page \\thepage" -footer-left: "[Charles Github](https://www.github.com/reachableceo/)" +footer-left: "Charles N Wyble" footer-center: "[Source code for this resume](https://git.knownelement.com/reachableceo/ReachableCEOResume) " footer-right: "Tenacity. Velocity. Focus" urlcolor: blue diff --git a/CurrentResume/common/WorkHistory.csv b/common/WorkHistory.csv similarity index 100% rename from CurrentResume/common/WorkHistory.csv rename to common/WorkHistory.csv diff --git a/CurrentResume/common/WorkHistory.md b/common/WorkHistory.md similarity index 100% rename from CurrentResume/common/WorkHistory.md rename to common/WorkHistory.md diff --git a/CurrentResume/cv/@ReachableCEO/Resume/CV/3M.md b/cv/@ReachableCEO/Resume/CV/3M.md similarity index 100% rename from CurrentResume/cv/@ReachableCEO/Resume/CV/3M.md rename to cv/@ReachableCEO/Resume/CV/3M.md diff --git a/CurrentResume/cv/@ReachableCEO/Resume/CV/Apple Computer.md b/cv/@ReachableCEO/Resume/CV/Apple Computer.md similarity index 100% rename from CurrentResume/cv/@ReachableCEO/Resume/CV/Apple Computer.md rename to cv/@ReachableCEO/Resume/CV/Apple Computer.md diff --git a/CurrentResume/cv/@ReachableCEO/Resume/CV/CDK Global.md b/cv/@ReachableCEO/Resume/CV/CDK Global.md similarity index 100% rename from CurrentResume/cv/@ReachableCEO/Resume/CV/CDK Global.md rename to cv/@ReachableCEO/Resume/CV/CDK Global.md diff --git a/CurrentResume/cv/@ReachableCEO/Resume/CV/Dell Residency.md b/cv/@ReachableCEO/Resume/CV/Dell Residency.md similarity index 100% rename from CurrentResume/cv/@ReachableCEO/Resume/CV/Dell Residency.md rename to cv/@ReachableCEO/Resume/CV/Dell Residency.md diff --git a/CurrentResume/cv/@ReachableCEO/Resume/CV/Electronic Clearing House.md b/cv/@ReachableCEO/Resume/CV/Electronic Clearing House.md similarity index 100% rename from CurrentResume/cv/@ReachableCEO/Resume/CV/Electronic Clearing House.md rename to cv/@ReachableCEO/Resume/CV/Electronic Clearing House.md diff --git a/CurrentResume/cv/@ReachableCEO/Resume/CV/GSI Commerce.md b/cv/@ReachableCEO/Resume/CV/GSI Commerce.md similarity index 100% rename from CurrentResume/cv/@ReachableCEO/Resume/CV/GSI Commerce.md rename to cv/@ReachableCEO/Resume/CV/GSI Commerce.md diff --git a/CurrentResume/cv/@ReachableCEO/Resume/CV/HostGator.com.md b/cv/@ReachableCEO/Resume/CV/HostGator.com.md similarity index 100% rename from CurrentResume/cv/@ReachableCEO/Resume/CV/HostGator.com.md rename to cv/@ReachableCEO/Resume/CV/HostGator.com.md diff --git a/CurrentResume/cv/@ReachableCEO/Resume/CV/RippleTV.md b/cv/@ReachableCEO/Resume/CV/RippleTV.md similarity index 100% rename from CurrentResume/cv/@ReachableCEO/Resume/CV/RippleTV.md rename to cv/@ReachableCEO/Resume/CV/RippleTV.md diff --git a/CurrentResume/cv/@ReachableCEO/Resume/CV/SHEIN.COM.md b/cv/@ReachableCEO/Resume/CV/SHEIN.COM.md similarity index 100% rename from CurrentResume/cv/@ReachableCEO/Resume/CV/SHEIN.COM.md rename to cv/@ReachableCEO/Resume/CV/SHEIN.COM.md diff --git a/CurrentResume/cv/@ReachableCEO/Resume/CV/TippingPoint.md b/cv/@ReachableCEO/Resume/CV/TippingPoint.md similarity index 100% rename from CurrentResume/cv/@ReachableCEO/Resume/CV/TippingPoint.md rename to cv/@ReachableCEO/Resume/CV/TippingPoint.md diff --git a/CurrentResume/cv/@ReachableCEO/Resume/CV/Walt Disney Internet Group.md b/cv/@ReachableCEO/Resume/CV/Walt Disney Internet Group.md similarity index 100% rename from CurrentResume/cv/@ReachableCEO/Resume/CV/Walt Disney Internet Group.md rename to cv/@ReachableCEO/Resume/CV/Walt Disney Internet Group.md diff --git a/CurrentResume/cv/MachineOutput.yml b/cv/MachineOutput.yml similarity index 100% rename from CurrentResume/cv/MachineOutput.yml rename to cv/MachineOutput.yml diff --git a/CurrentResume/cv/build.sh b/cv/build.sh similarity index 98% rename from CurrentResume/cv/build.sh rename to cv/build.sh index fdc2fe3..a9bdd78 100644 --- a/CurrentResume/cv/build.sh +++ b/cv/build.sh @@ -44,7 +44,7 @@ TITLE="$(echo $position|awk -F ',' '{print $2}')" DATEOFEMPLOY="$(echo $position|awk -F ',' '{print $3}')" echo " " >> "$HumanIntermediateOutputFile" -echo "**$COMPANY** $TITLE $DATEOFEMPLOY" >> $HumanIntermediateOutputFile +echo "**$COMPANY** | $TITLE | $DATEOFEMPLOY" >> $HumanIntermediateOutputFile echo " " >> "$HumanIntermediateOutputFile" cat ../cv/@ReachableCEO/Resume/CV/$COMPANY.md >> "$HumanIntermediateOutputFile" diff --git a/CurrentResume/cv/output/intermediate/human/CharlesNWybleCV.md b/cv/output/intermediate/human/CharlesNWybleCV.md similarity index 86% rename from CurrentResume/cv/output/intermediate/human/CharlesNWybleCV.md rename to cv/output/intermediate/human/CharlesNWybleCV.md index 5b6a8c3..76be860 100644 --- a/CurrentResume/cv/output/intermediate/human/CharlesNWybleCV.md +++ b/cv/output/intermediate/human/CharlesNWybleCV.md @@ -7,19 +7,19 @@ Senior (Staff level) System Engineer/SRE/Architect with extensive Linux/Windows/ ## Employment History -**CDK Global** Senior System Engineer July 2024 - October 2024 +**CDK Global** | Senior System Engineer | July 2024 - October 2024 - Security Compliance : worked with risk management/audit to remediate insecure configurations - Created Alma9 Packer image from scratch -**Apple Computer** Senior System Administrator March 2024 - July 2024 +**Apple Computer** | Senior System Administrator | March 2024 - July 2024 - Day to day server operations scheduling downtime etc -**SHEIN.com** Staff Site Reliability Engineer December 2022 - August 2023 +**SHEIN.com** | Staff Site Reliability Engineer | December 2022 - August 2023 - Streamlined engineer onboarding by documenting and overhauling the process, consolidating disparate guides into a comprehensive modular set of documents. @@ -28,13 +28,13 @@ Senior (Staff level) System Engineer/SRE/Architect with extensive Linux/Windows/ - Focused on fostering a culture of automation and skill development within the SRE team, emphasizing code review, infrastructure as code, versioning, testing, and effective ticket management. - Contributed to Linux server administration both internally and externally, aiding colleagues with scripting/automation and assisting in the migration from AWS to Azure with zero customer-facing system impact. Additionally, provided day-to-day support for AWS and Azure activities and troubleshooting. -**3M** Senior Site Reliability Engineer March 2020 November 2022 +**3M** | Senior Site Reliability Engineer | March 2020 November 2022 - Supported Vendavo on RedHat Linux, managed releases, and provided day-to-day developer support. - Created a homegrown YAML conflguration management system, utilizing bash scripting and YAML templates with a CSV-based key/value store to eThciently manage and regenerate environment-speciflc variables for a line-of-business application across multiple development, testing, staging, and production environments. -**TippingPoint** Staff System/Network Architect March 2012 - June 2019 +**TippingPoint** | Staff System/Network Architect | March 2012 - June 2019 - Conducted code and design reviews for internal/external team projects and actively participated in broad enterprise collaboration, focusing on large-scale fleet management. @@ -43,20 +43,20 @@ Senior (Staff level) System Engineer/SRE/Architect with extensive Linux/Windows/ - Deployed network monitoring systems (Zenoss, observium/librenms), utilized librenms as a Conflguration Management Database (CMDB), and implemented a fleet orchestration system (Rundeck). - Executed extensive vulnerability remediation, OS/application/kernel patching, NIC customization/ optimization, and data migrations while developing and maintaining custom scripts for tasks such as LDAP management and SSL scenarios. Automated processes like re-imaging and ensured continuous distribution of a 40GB dataset of packet captures across a global fleet. -**HostGator.com** Automation and Escalation Engineer March 2011 - May 2012 +**HostGator.com** | Automation and Escalation Engineer | March 2011 - May 2012 - Provided senior-level Linux and web application support globally. - Developed standardized reply language and scripts, reducing errors in Level I Linux administrator department. -**RippleTV** Systems Engineer October 2008 - Jaunary 2010 +**RippleTV** | Systems Engineer | October 2008 - Jaunary 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, memcached, and F5 LTM. -**Walt Disney Internet Group** Site Reliability Engineer August 2006 - September 2007 +**Walt Disney Internet Group** | Site Reliability Engineer | August 2006 - September 2007 - Engaged in dynamic work environment focusing on popular web/ecommerce sites, including disneyworld.com and disneyland.com. @@ -68,7 +68,7 @@ Senior (Staff level) System Engineer/SRE/Architect with extensive Linux/Windows/ - Managed the migration from Windows NT to Windows 2003 Active Directory domain controllers, including experience with Windows 2008, Centrify, and Samba/Winbind/LDAP/Kerberos. -**Electronic Clearing House** Senior Linux System Administrator April 2005 - July 2006 +**Electronic Clearing House** | Senior Linux System Administrator | April 2005 - July 2006 - Linux systems engineer in a 24x7 transaction processing/ecommerce/flnancial services environment, collaborating with network administration and infrastructure design teams. @@ -76,14 +76,14 @@ Senior (Staff level) System Engineer/SRE/Architect with extensive Linux/Windows/ - Successfully deployed an enterprise-wide Linux backup system, featuring encrypted backups stored on a central server with ISCSI attached network storage, utilizing GNUPG and tar over SSH. Regular backups and restores were tested weekly. - Led the deployment of Oracle database infrastructure, implementing two Oracle RAC clusters with Dell 6850 servers, Qual Dual Core Xeon processors, and 32GB of RAM each. The clusters ran on RedHat Enterprise Linux 4.0 64bit edition, serving Data Warehouse, Transaction Processing Software, and Credit Card Clearing applications. -**GSI Commerce** HPUX/Windows/Linux System Administrator March 2002 - February 2005 +**GSI Commerce** | HPUX/Windows/Linux System Administrator | March 2002 - February 2005 - Contributed to disaster recovery from an Informix Database failure. - Streamlined FTP server conflguration and deployed open-source remote control software. - Upgraded network infrastructure from hubs to managed switches. -**Reachable CEO Enterprises** Freelancer January 2001 - december 2024 +**Reachable CEO Enterprises** | Freelancer | January 2001 - december 2024 diff --git a/CurrentResume/cv/output/intermediate/machine/glassdoor/CharlesNWybleCV.md b/cv/output/intermediate/machine/glassdoor/CharlesNWybleCV.md similarity index 100% rename from CurrentResume/cv/output/intermediate/machine/glassdoor/CharlesNWybleCV.md rename to cv/output/intermediate/machine/glassdoor/CharlesNWybleCV.md diff --git a/legacy-resumes/Charles Wyble Resume.docx b/legacy-resumes/Charles Wyble Resume.docx deleted file mode 100644 index 7a30ddb..0000000 Binary files a/legacy-resumes/Charles Wyble Resume.docx and /dev/null differ diff --git a/legacy-resumes/CharlesWyble-resume.doc b/legacy-resumes/CharlesWyble-resume.doc deleted file mode 100644 index 001343b..0000000 Binary files a/legacy-resumes/CharlesWyble-resume.doc and /dev/null differ diff --git a/legacy-resumes/CharlesWyble.doc b/legacy-resumes/CharlesWyble.doc deleted file mode 100644 index 749591a..0000000 Binary files a/legacy-resumes/CharlesWyble.doc and /dev/null differ diff --git a/legacy-resumes/CharlesWyble.docx b/legacy-resumes/CharlesWyble.docx deleted file mode 100644 index cf9ada6..0000000 Binary files a/legacy-resumes/CharlesWyble.docx and /dev/null differ diff --git a/legacy-resumes/CharlesWyble2020Resume.docx b/legacy-resumes/CharlesWyble2020Resume.docx deleted file mode 100644 index ff6aaa4..0000000 Binary files a/legacy-resumes/CharlesWyble2020Resume.docx and /dev/null differ diff --git a/legacy-resumes/CharlesWyble2020Resume.pdf b/legacy-resumes/CharlesWyble2020Resume.pdf deleted file mode 100644 index d85fc48..0000000 Binary files a/legacy-resumes/CharlesWyble2020Resume.pdf and /dev/null differ diff --git a/legacy-resumes/CharlesWybleResume-aa.doc b/legacy-resumes/CharlesWybleResume-aa.doc deleted file mode 100644 index 785d66b..0000000 Binary files a/legacy-resumes/CharlesWybleResume-aa.doc and /dev/null differ diff --git a/legacy-resumes/CharlesWybleResume.doc b/legacy-resumes/CharlesWybleResume.doc deleted file mode 100644 index 96ffbca..0000000 Binary files a/legacy-resumes/CharlesWybleResume.doc and /dev/null differ diff --git a/legacy-resumes/CharlesWybleResume.odt b/legacy-resumes/CharlesWybleResume.odt deleted file mode 100644 index dd0a9f1..0000000 Binary files a/legacy-resumes/CharlesWybleResume.odt and /dev/null differ diff --git a/legacy-resumes/CharlesWybleResume.pdf b/legacy-resumes/CharlesWybleResume.pdf deleted file mode 100644 index 636e581..0000000 Binary files a/legacy-resumes/CharlesWybleResume.pdf and /dev/null differ diff --git a/legacy-resumes/charlesnw-resume-detailed.xml b/legacy-resumes/charlesnw-resume-detailed.xml deleted file mode 100644 index 4ac8d0c..0000000 --- a/legacy-resumes/charlesnw-resume-detailed.xml +++ /dev/null @@ -1,299 +0,0 @@ - - - - -
- Charles Wyble -
El Monte CA
- 818.280.7059 charles@knownelement.com 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. - - - - - Skills Summary - Linux systems engineer with extensive knowledge/experience on both Debian and RedHat based Linux distrubutions in a wide variety of applications. - A superb communicator who will thoroughly and efficiently handle any situation requiring communication with clarity and conciseness. - A frequent speaker/writer on a wide variety of I.T and open source matters, as well as a frequent contributer to open source projects. - - Linux Server Applications - Debian (stable/testing/unstable) - Red Hat Enterprise Linux (3/4) - Shell scripting/automation/software debugging (bash/php/python/perl/java/awk/sed) - Apache 1.30/2.0/2.2 - Postfix and Courier - /Samba - IpTables/Snort/Nessus/Nmap - Proftpd - - Networking (switches, load balancers and security) - F5/BigIP Global Traffic Manager and Local Traffic Manager - Cisco LocalDirector, PIX, 2600/1800 series routers - 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 (used at Ripple/Targetcasat) - ATT Edge Cache (used at Disney) - Akama (used at Evite and Disney) - - - - - - - Linux System Engineer - Targetcastnetworks INC (via acquisition of RippleTV) - - October2008 - January2010 - - - - - Linux/Windows/network/security consulting - Multiple entities including Cast And Crew Entertainment Services Inc, Evite.com and Siderean Software - - September2007 - October2008 - - - - - Linux/Windows System Engineer - The Walt Disney Company - Parks and Resorts Online - Walt Disney Internet Group - - August2006 - September2007 - - - - - Linux Systems Engineer - Intuit Inc (via acquistion of Electronic Clearing House) - - October2005 - June2006 - - - - - Linux systems engineer for a 24x7 transaction processing/ecommerce/ - financial services environment. Responsibilities included: Working closely - with the network administration and infrastructure design teams. Ensuring continuous - uptime of multiple high visibility/high impact/high value envrironments including: - - - - A 1TB MySQL database. - A 300 TB Oracle database. - A 1.5 TB Oracle Data warehouse. - A 4,000 store LAMP based ecommerce system. - - - - - - Deployment of encrypted backups - - Designed/tested/documented/deployed an enterprise wide Linux backup system. - All data stored on a central server with ISCSI attached network storage. - Uses GNUPG and tar over ssh. Backups/Restores tested on a weekly basis. - - - - - Deployment of core database infrastructure. - - Deployed 2 Oracle RAC clusters, each consisting of 3 Dell 6850's. They are equipped with Qual Dual Core - Xeon's and 32 Gb of RAM, running RedHat Enterprise Linux 4.0 64bit edition. - One environment is for staging and one is for production. EMC attached. This environment is used for - our Data Warehouse, our Transaction Processing Software and our Credit Card Clearing application. It is a - fundamental infrastructure component. The hardware and software was deployed in 3 business days. - - - - - File Integrity Checking - - Deployment of file integrity checking across 100 UNIX servers using fully open source software. - Used integrit http://integrit.sf.net and some custom shell scripts which were submitted - back upstream for inclusion. - - - - - - - - Linux/Windows/network/security consulting for various startups and defense contractors - Multiple entities - - February2005 - October2005 - - - - - LAMP Deployment: Deployed a Debian Linux/Apache/MySQL/PHP system and educated the System Administration and Development - staff on configuration and use for an insurance company - - - - - - Corporate Linux Deployment/Migration: Provided assistance to a medium sized engineering firm with a near 100% - conversion to Linux on the desktop and server. Utilizing SUSE Professional 6.5 for desktops and Debian GNU/Linux for - servers (Email/File Server/DNS/DHCP). - - - - - - Linux Deployment/Migration: Providing on going assistance to a small software development firm with a near 100% - conversion to Linux. Utilizing Ubuntu Linux for desktops and Debian GNU/Linux for servers - (Email/File/LDAP/DNS/DHCP). - - - - - - - Linux/Windows Systems Engineer - GSI Commerce (via acquistion of Newroads Inc) - - July2002 - February2005 - - - - - Disaster Recovery from an Informix Database Failure - - Assisted in the design/testing/and execution of a disaster recovery in real time - (on-the-fly). Wrote and documented the use of several utilities that cut down the amount of time to recovery by 30 - percent. - - - - - Streamlined the FTP Server Configuration process - - Streamlined the system configuration and new account creation process for ProFTPD on a mission critical FTP server. - This allowed faster turn around times and freed up I.T. resources. - - - - - Deployed open-source Remote Control Software - - Deplopyed/Secured/Optimized/Maintained UltraVNC remote control software. This allowed the Infrastructure Support team to more - rapidly respond to users support requests, and by doing so increase compliance with Service Level Agreements and increase - end-user satisfaction. - - - - - Network Infrastructure Upgrade - - Upgraded the network from hubs to Linksys managed switches to increase network performance and usability/reliability. - No network downtime occurred in the process of the upgrade - - - - - Hardware/Software Inventory Solution - - Wrote a custom software/hardware monitoring/reporting system to ensure compliance with software licensing and obtain an - accurate overview of company assets for inventory and disaster recovery purposes. Utilized WMI/Visio/Microsoft Access - - - - - - - - Classes/Courses - - Course 319: Technical Writing A Comprehensive Hands On Introduction - Learning Tree International - May 2004 - - This course showed the entire process of developing clear concise effective technical writing in less time, that meets the needs - of the audience. - - - - - Course 364: Introduction to Internetworking Switches And Routers - Learning Tree International - October2004 - - This workshop presented a conceptual overview of networking fundemntals and technology. - - - - - - - I founded an open source project to capture information on the Excel file format. - - - - - The Chicago Project - - If you ever open an Excel file in OpenOffice you are using code that I helped write via extensive research on the Excel file format. - I also am the maintainer of the stand alone xlhtml software which is a command line xls convertor. - This project produced code and documentation to assist developers working with the Microsoft Excel and compound - document/structured storage file formats on non Microsoft platforms. - - - - - - I am a very active participant in the greater Los Angeles information technology community. - - - - - User groups - - I have presented numerous times at the Unix Users Association of Southern California (LA and OC chapters). Please see http://www.uuasc.org for details. - I am a frequent contributor to the mailing list as well. - - - - I am a frequent presenter and participant (both in person and via mailing lists) at numerous Linux User Groups throughout the southern California region. - This includes LiLAX, SFVLUG, SCLUG, SGVLUG. - - - - - - - 2010 - - Redistrubtion as is allowed. No modifications without prior written consent. - - - - diff --git a/legacy-resumes/charlesnw-resume.xml b/legacy-resumes/charlesnw-resume.xml deleted file mode 100644 index e9a44ef..0000000 --- a/legacy-resumes/charlesnw-resume.xml +++ /dev/null @@ -1,328 +0,0 @@ - - - - -
- Charles Wyble -
El Monte CA
- 818.280.7059 charles@knownelement.com 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. - - - - - - Skills Summary - - Linux systems engineer with extensive knowledge/experience on both Debian and RedHat based Linux distrubutions in a wide variety of applications. - Very comfortable with shell scripting, package management, user account administration, configuration management etc) - - A superb communicator who will thoroughly and efficiently handle any situation requiring communication with clarity and conciseness. - A frequent speaker/writer on a wide variety of I.T 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 (formerly nessus) - - 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 (used at Ripple/Targetcasat) - ATT Edge Cache (used at Disney) - Akamai (used at Evite and Disney) - - - - - - - Linux System Engineer - Targetcastnetworks INC (via acquisition of RippleTV) - - October2008 - January2010 - - - - - Provided system engineering expertise for customer facing advertising platform (AdSpot) and internal fleet management tool (CPanel). - Utilized Nginx, Mongrel, Thin, Rails, Merb and Rack. Also used MySQL and memcached. - - - - - - Linux/Windows/network/security consulting - Multiple entities including Cast And Crew Entertainment Services Inc, Evite.com and Siderean Software - - September2007 - October2008 - - - - - Provided system 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. - - - - - - Linux/Windows System Engineer - The Walt Disney Company - Parks and Resorts Online - Walt Disney Internet Group - - August2006 - September2007 - - - - - 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. - - - - - - Linux Systems Engineer - Intuit Inc (via acquistion of Electronic Clearing House) - - October2005 - June2006 - - - - - Linux systems engineer for a 24x7 transaction processing/ecommerce/ - financial services environment. Responsibilities included: Working closely - with the network administration and infrastructure design teams. Ensuring continuous - uptime of multiple high visibility/high impact/high value envrironments including: - - - - A 1TB MySQL database. - A 300 TB Oracle database. - A 1.5 TB Oracle Data warehouse. - A 4,000 store LAMP based ecommerce system. (MerchantAmerica.com) - - - - - - Deployment of encrypted backups - - Designed/tested/documented/deployed an enterprise wide Linux backup system. - All data stored on a central server with ISCSI attached network storage. - Uses GNUPG and tar over ssh. Backups/Restores tested on a weekly basis. - - - - - Deployment of core database infrastructure. - - Deployed 2 Oracle RAC clusters, each consisting of 3 Dell 6850's. They are equipped with Qual Dual Core - Xeon's and 32 Gb of RAM, running RedHat Enterprise Linux 4.0 64bit edition. - One environment is for staging and one is for production. EMC attached. This environment is used for - our Data Warehouse, our Transaction Processing Software and our Credit Card Clearing application. It is a - fundamental infrastructure component. The hardware and software was deployed in 3 business days. - - - - - File Integrity Checking - - Deployment of file integrity checking across 100 UNIX servers using fully open source software. - Used integrit http://integrit.sf.net and some custom shell scripts which were submitted - back upstream for inclusion. - - - - - - - - Linux/Windows/network/security consulting for various startups and defense contractors - Multiple entities - - February2005 - October2005 - - - - - LAMP Deployment: Deployed a Debian Linux/Apache/MySQL/PHP system and educated the System Administration and Development - staff on configuration and use for an insurance company - - - - - - Corporate Linux Deployment/Migration: Provided assistance to a medium sized engineering firm with a near 100% - conversion to Linux on the desktop and server. Utilizing SUSE Professional 6.5 for desktops and Debian GNU/Linux for - servers (Email/File Server/DNS/DHCP). - - - - - - Linux Deployment/Migration: Providing on going assistance to a small software development firm with a near 100% - conversion to Linux. Utilizing Ubuntu Linux for desktops and Debian GNU/Linux for servers - (Email/File/LDAP/DNS/DHCP). - - - - - - - Linux/Windows Systems Engineer - GSI Commerce (via acquistion of Newroads Inc) - - July2002 - February2005 - - - - - Disaster Recovery from an Informix Database Failure - - Assisted in the design/testing/and execution of a disaster recovery in real time - (on-the-fly). Wrote and documented the use of several utilities that cut down the amount of time to recovery by 30 - percent. - - - - - Streamlined the FTP Server Configuration process - - Streamlined the system configuration and new account creation process for ProFTPD on a mission critical FTP server. - This allowed faster turn around times and freed up I.T. resources. - - - - - Deployed open-source Remote Control Software - - Deplopyed/Secured/Optimized/Maintained UltraVNC remote control software. This allowed the Infrastructure Support team to more - rapidly respond to users support requests, and by doing so increase compliance with Service Level Agreements and increase - end-user satisfaction. - - - - - Network Infrastructure Upgrade - - Upgraded the network from hubs to Linksys managed switches to increase network performance and usability/reliability. - No network downtime occurred in the process of the upgrade - - - - - Hardware/Software Inventory Solution - - Wrote a custom software/hardware monitoring/reporting system to ensure compliance with software licensing and obtain an - accurate overview of company assets for inventory and disaster recovery purposes. Utilized WMI/Visio/Microsoft Access - - - - - - - - Classes/Courses - - Course 319: Technical Writing A Comprehensive Hands On Introduction - Learning Tree International - May 2004 - - This course showed the entire process of developing clear concise effective technical writing in less time, that meets the needs - of the audience. - - - - - Course 364: Introduction to Internetworking Switches And Routers - Learning Tree International - October2004 - - This workshop presented a conceptual overview of networking fundemntals and technology. - - - - - - - I founded an open source project to capture information on the Excel file format. - - - - - The Chicago Project - - If you ever open an Excel file in OpenOffice you are using code that I helped write via extensive research on the Excel file format. - I also am the maintainer of the stand alone xlhtml software which is a command line xls convertor. - This project produced code and documentation to assist developers working with the Microsoft Excel and compound - document/structured storage file formats on non Microsoft platforms. - - - - - - I am a very active participant in the greater Los Angeles information technology community. - - - - - User groups - - I have presented numerous times at the Unix Users Association of Southern California (LA and OC chapters). Please see http://www.uuasc.org for details. - I am a frequent contributor to the mailing list as well. - - - - I am a frequent presenter and participant (both in person and via mailing lists) at numerous Linux User Groups throughout the southern California region. - This includes LiLAX, SFVLUG, SCLUG, SGVLUG. - - - - - - - 2010 - - Redistrubtion as is allowed. No modifications without prior written consent. - - - - diff --git a/legacy-resumes/code/legacy-generateResume.sh b/legacy-resumes/code/legacy-generateResume.sh deleted file mode 100644 index 9c16d7a..0000000 --- a/legacy-resumes/code/legacy-generateResume.sh +++ /dev/null @@ -1,88 +0,0 @@ -#!/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/cover-letter.docx b/legacy-resumes/cover-letter.docx deleted file mode 100644 index f7d790e..0000000 Binary files a/legacy-resumes/cover-letter.docx and /dev/null differ diff --git a/legacy-resumes/old/CharlesNWyble2009.doc b/legacy-resumes/old/CharlesNWyble2009.doc deleted file mode 100644 index f3e469f..0000000 Binary files a/legacy-resumes/old/CharlesNWyble2009.doc and /dev/null differ diff --git a/legacy-resumes/old/CharlesNWybleResume2009.doc b/legacy-resumes/old/CharlesNWybleResume2009.doc deleted file mode 100644 index 187e12f..0000000 Binary files a/legacy-resumes/old/CharlesNWybleResume2009.doc and /dev/null differ diff --git a/legacy-resumes/old/CharlesNWybleResume2009.odt b/legacy-resumes/old/CharlesNWybleResume2009.odt deleted file mode 100644 index a14bcc3..0000000 Binary files a/legacy-resumes/old/CharlesNWybleResume2009.odt and /dev/null differ diff --git a/legacy-resumes/old/Headhunters in L.A..doc b/legacy-resumes/old/Headhunters in L.A..doc deleted file mode 100644 index 24eb9d9..0000000 Binary files a/legacy-resumes/old/Headhunters in L.A..doc and /dev/null differ diff --git a/legacy-resumes/old/Headhunters in L.A_.doc b/legacy-resumes/old/Headhunters in L.A_.doc deleted file mode 100644 index 24eb9d9..0000000 Binary files a/legacy-resumes/old/Headhunters in L.A_.doc and /dev/null differ diff --git a/legacy-resumes/old/charlesnw-resume-detailed.xml b/legacy-resumes/old/charlesnw-resume-detailed.xml deleted file mode 100644 index 4ac8d0c..0000000 --- a/legacy-resumes/old/charlesnw-resume-detailed.xml +++ /dev/null @@ -1,299 +0,0 @@ - - - - -
- Charles Wyble -
El Monte CA
- 818.280.7059 charles@knownelement.com 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. - - - - - Skills Summary - Linux systems engineer with extensive knowledge/experience on both Debian and RedHat based Linux distrubutions in a wide variety of applications. - A superb communicator who will thoroughly and efficiently handle any situation requiring communication with clarity and conciseness. - A frequent speaker/writer on a wide variety of I.T and open source matters, as well as a frequent contributer to open source projects. - - Linux Server Applications - Debian (stable/testing/unstable) - Red Hat Enterprise Linux (3/4) - Shell scripting/automation/software debugging (bash/php/python/perl/java/awk/sed) - Apache 1.30/2.0/2.2 - Postfix and Courier - /Samba - IpTables/Snort/Nessus/Nmap - Proftpd - - Networking (switches, load balancers and security) - F5/BigIP Global Traffic Manager and Local Traffic Manager - Cisco LocalDirector, PIX, 2600/1800 series routers - 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 (used at Ripple/Targetcasat) - ATT Edge Cache (used at Disney) - Akama (used at Evite and Disney) - - - - - - - Linux System Engineer - Targetcastnetworks INC (via acquisition of RippleTV) - - October2008 - January2010 - - - - - Linux/Windows/network/security consulting - Multiple entities including Cast And Crew Entertainment Services Inc, Evite.com and Siderean Software - - September2007 - October2008 - - - - - Linux/Windows System Engineer - The Walt Disney Company - Parks and Resorts Online - Walt Disney Internet Group - - August2006 - September2007 - - - - - Linux Systems Engineer - Intuit Inc (via acquistion of Electronic Clearing House) - - October2005 - June2006 - - - - - Linux systems engineer for a 24x7 transaction processing/ecommerce/ - financial services environment. Responsibilities included: Working closely - with the network administration and infrastructure design teams. Ensuring continuous - uptime of multiple high visibility/high impact/high value envrironments including: - - - - A 1TB MySQL database. - A 300 TB Oracle database. - A 1.5 TB Oracle Data warehouse. - A 4,000 store LAMP based ecommerce system. - - - - - - Deployment of encrypted backups - - Designed/tested/documented/deployed an enterprise wide Linux backup system. - All data stored on a central server with ISCSI attached network storage. - Uses GNUPG and tar over ssh. Backups/Restores tested on a weekly basis. - - - - - Deployment of core database infrastructure. - - Deployed 2 Oracle RAC clusters, each consisting of 3 Dell 6850's. They are equipped with Qual Dual Core - Xeon's and 32 Gb of RAM, running RedHat Enterprise Linux 4.0 64bit edition. - One environment is for staging and one is for production. EMC attached. This environment is used for - our Data Warehouse, our Transaction Processing Software and our Credit Card Clearing application. It is a - fundamental infrastructure component. The hardware and software was deployed in 3 business days. - - - - - File Integrity Checking - - Deployment of file integrity checking across 100 UNIX servers using fully open source software. - Used integrit http://integrit.sf.net and some custom shell scripts which were submitted - back upstream for inclusion. - - - - - - - - Linux/Windows/network/security consulting for various startups and defense contractors - Multiple entities - - February2005 - October2005 - - - - - LAMP Deployment: Deployed a Debian Linux/Apache/MySQL/PHP system and educated the System Administration and Development - staff on configuration and use for an insurance company - - - - - - Corporate Linux Deployment/Migration: Provided assistance to a medium sized engineering firm with a near 100% - conversion to Linux on the desktop and server. Utilizing SUSE Professional 6.5 for desktops and Debian GNU/Linux for - servers (Email/File Server/DNS/DHCP). - - - - - - Linux Deployment/Migration: Providing on going assistance to a small software development firm with a near 100% - conversion to Linux. Utilizing Ubuntu Linux for desktops and Debian GNU/Linux for servers - (Email/File/LDAP/DNS/DHCP). - - - - - - - Linux/Windows Systems Engineer - GSI Commerce (via acquistion of Newroads Inc) - - July2002 - February2005 - - - - - Disaster Recovery from an Informix Database Failure - - Assisted in the design/testing/and execution of a disaster recovery in real time - (on-the-fly). Wrote and documented the use of several utilities that cut down the amount of time to recovery by 30 - percent. - - - - - Streamlined the FTP Server Configuration process - - Streamlined the system configuration and new account creation process for ProFTPD on a mission critical FTP server. - This allowed faster turn around times and freed up I.T. resources. - - - - - Deployed open-source Remote Control Software - - Deplopyed/Secured/Optimized/Maintained UltraVNC remote control software. This allowed the Infrastructure Support team to more - rapidly respond to users support requests, and by doing so increase compliance with Service Level Agreements and increase - end-user satisfaction. - - - - - Network Infrastructure Upgrade - - Upgraded the network from hubs to Linksys managed switches to increase network performance and usability/reliability. - No network downtime occurred in the process of the upgrade - - - - - Hardware/Software Inventory Solution - - Wrote a custom software/hardware monitoring/reporting system to ensure compliance with software licensing and obtain an - accurate overview of company assets for inventory and disaster recovery purposes. Utilized WMI/Visio/Microsoft Access - - - - - - - - Classes/Courses - - Course 319: Technical Writing A Comprehensive Hands On Introduction - Learning Tree International - May 2004 - - This course showed the entire process of developing clear concise effective technical writing in less time, that meets the needs - of the audience. - - - - - Course 364: Introduction to Internetworking Switches And Routers - Learning Tree International - October2004 - - This workshop presented a conceptual overview of networking fundemntals and technology. - - - - - - - I founded an open source project to capture information on the Excel file format. - - - - - The Chicago Project - - If you ever open an Excel file in OpenOffice you are using code that I helped write via extensive research on the Excel file format. - I also am the maintainer of the stand alone xlhtml software which is a command line xls convertor. - This project produced code and documentation to assist developers working with the Microsoft Excel and compound - document/structured storage file formats on non Microsoft platforms. - - - - - - I am a very active participant in the greater Los Angeles information technology community. - - - - - User groups - - I have presented numerous times at the Unix Users Association of Southern California (LA and OC chapters). Please see http://www.uuasc.org for details. - I am a frequent contributor to the mailing list as well. - - - - I am a frequent presenter and participant (both in person and via mailing lists) at numerous Linux User Groups throughout the southern California region. - This includes LiLAX, SFVLUG, SCLUG, SGVLUG. - - - - - - - 2010 - - Redistrubtion as is allowed. No modifications without prior written consent. - - - - diff --git a/legacy-resumes/old/charlesnw-resume.xml b/legacy-resumes/old/charlesnw-resume.xml deleted file mode 100644 index e9a44ef..0000000 --- a/legacy-resumes/old/charlesnw-resume.xml +++ /dev/null @@ -1,328 +0,0 @@ - - - - -
- Charles Wyble -
El Monte CA
- 818.280.7059 charles@knownelement.com 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. - - - - - - Skills Summary - - Linux systems engineer with extensive knowledge/experience on both Debian and RedHat based Linux distrubutions in a wide variety of applications. - Very comfortable with shell scripting, package management, user account administration, configuration management etc) - - A superb communicator who will thoroughly and efficiently handle any situation requiring communication with clarity and conciseness. - A frequent speaker/writer on a wide variety of I.T 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 (formerly nessus) - - 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 (used at Ripple/Targetcasat) - ATT Edge Cache (used at Disney) - Akamai (used at Evite and Disney) - - - - - - - Linux System Engineer - Targetcastnetworks INC (via acquisition of RippleTV) - - October2008 - January2010 - - - - - Provided system engineering expertise for customer facing advertising platform (AdSpot) and internal fleet management tool (CPanel). - Utilized Nginx, Mongrel, Thin, Rails, Merb and Rack. Also used MySQL and memcached. - - - - - - Linux/Windows/network/security consulting - Multiple entities including Cast And Crew Entertainment Services Inc, Evite.com and Siderean Software - - September2007 - October2008 - - - - - Provided system 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. - - - - - - Linux/Windows System Engineer - The Walt Disney Company - Parks and Resorts Online - Walt Disney Internet Group - - August2006 - September2007 - - - - - 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. - - - - - - Linux Systems Engineer - Intuit Inc (via acquistion of Electronic Clearing House) - - October2005 - June2006 - - - - - Linux systems engineer for a 24x7 transaction processing/ecommerce/ - financial services environment. Responsibilities included: Working closely - with the network administration and infrastructure design teams. Ensuring continuous - uptime of multiple high visibility/high impact/high value envrironments including: - - - - A 1TB MySQL database. - A 300 TB Oracle database. - A 1.5 TB Oracle Data warehouse. - A 4,000 store LAMP based ecommerce system. (MerchantAmerica.com) - - - - - - Deployment of encrypted backups - - Designed/tested/documented/deployed an enterprise wide Linux backup system. - All data stored on a central server with ISCSI attached network storage. - Uses GNUPG and tar over ssh. Backups/Restores tested on a weekly basis. - - - - - Deployment of core database infrastructure. - - Deployed 2 Oracle RAC clusters, each consisting of 3 Dell 6850's. They are equipped with Qual Dual Core - Xeon's and 32 Gb of RAM, running RedHat Enterprise Linux 4.0 64bit edition. - One environment is for staging and one is for production. EMC attached. This environment is used for - our Data Warehouse, our Transaction Processing Software and our Credit Card Clearing application. It is a - fundamental infrastructure component. The hardware and software was deployed in 3 business days. - - - - - File Integrity Checking - - Deployment of file integrity checking across 100 UNIX servers using fully open source software. - Used integrit http://integrit.sf.net and some custom shell scripts which were submitted - back upstream for inclusion. - - - - - - - - Linux/Windows/network/security consulting for various startups and defense contractors - Multiple entities - - February2005 - October2005 - - - - - LAMP Deployment: Deployed a Debian Linux/Apache/MySQL/PHP system and educated the System Administration and Development - staff on configuration and use for an insurance company - - - - - - Corporate Linux Deployment/Migration: Provided assistance to a medium sized engineering firm with a near 100% - conversion to Linux on the desktop and server. Utilizing SUSE Professional 6.5 for desktops and Debian GNU/Linux for - servers (Email/File Server/DNS/DHCP). - - - - - - Linux Deployment/Migration: Providing on going assistance to a small software development firm with a near 100% - conversion to Linux. Utilizing Ubuntu Linux for desktops and Debian GNU/Linux for servers - (Email/File/LDAP/DNS/DHCP). - - - - - - - Linux/Windows Systems Engineer - GSI Commerce (via acquistion of Newroads Inc) - - July2002 - February2005 - - - - - Disaster Recovery from an Informix Database Failure - - Assisted in the design/testing/and execution of a disaster recovery in real time - (on-the-fly). Wrote and documented the use of several utilities that cut down the amount of time to recovery by 30 - percent. - - - - - Streamlined the FTP Server Configuration process - - Streamlined the system configuration and new account creation process for ProFTPD on a mission critical FTP server. - This allowed faster turn around times and freed up I.T. resources. - - - - - Deployed open-source Remote Control Software - - Deplopyed/Secured/Optimized/Maintained UltraVNC remote control software. This allowed the Infrastructure Support team to more - rapidly respond to users support requests, and by doing so increase compliance with Service Level Agreements and increase - end-user satisfaction. - - - - - Network Infrastructure Upgrade - - Upgraded the network from hubs to Linksys managed switches to increase network performance and usability/reliability. - No network downtime occurred in the process of the upgrade - - - - - Hardware/Software Inventory Solution - - Wrote a custom software/hardware monitoring/reporting system to ensure compliance with software licensing and obtain an - accurate overview of company assets for inventory and disaster recovery purposes. Utilized WMI/Visio/Microsoft Access - - - - - - - - Classes/Courses - - Course 319: Technical Writing A Comprehensive Hands On Introduction - Learning Tree International - May 2004 - - This course showed the entire process of developing clear concise effective technical writing in less time, that meets the needs - of the audience. - - - - - Course 364: Introduction to Internetworking Switches And Routers - Learning Tree International - October2004 - - This workshop presented a conceptual overview of networking fundemntals and technology. - - - - - - - I founded an open source project to capture information on the Excel file format. - - - - - The Chicago Project - - If you ever open an Excel file in OpenOffice you are using code that I helped write via extensive research on the Excel file format. - I also am the maintainer of the stand alone xlhtml software which is a command line xls convertor. - This project produced code and documentation to assist developers working with the Microsoft Excel and compound - document/structured storage file formats on non Microsoft platforms. - - - - - - I am a very active participant in the greater Los Angeles information technology community. - - - - - User groups - - I have presented numerous times at the Unix Users Association of Southern California (LA and OC chapters). Please see http://www.uuasc.org for details. - I am a frequent contributor to the mailing list as well. - - - - I am a frequent presenter and participant (both in person and via mailing lists) at numerous Linux User Groups throughout the southern California region. - This includes LiLAX, SFVLUG, SCLUG, SGVLUG. - - - - - - - 2010 - - Redistrubtion as is allowed. No modifications without prior written consent. - - - - diff --git a/legacy-resumes/old/employment-history.doc b/legacy-resumes/old/employment-history.doc deleted file mode 100644 index 2c7d068..0000000 Binary files a/legacy-resumes/old/employment-history.doc and /dev/null differ diff --git a/legacy-resumes/old/resume.xml b/legacy-resumes/old/resume.xml deleted file mode 100644 index 9d1883c..0000000 --- a/legacy-resumes/old/resume.xml +++ /dev/null @@ -1,321 +0,0 @@ - - - - - - -
- - Mr - Charles - Nathaniel - Wyble - - -
- 1350 Victoria Ave Suite 116 - Oxnard - CA - 93035 -
- - - 818-280-7059 - 805-984-9983 - charles@thewybles.com - http://www.thewybles.com/~charles - -
- - - - - - To obtain a Linux system administration position with your organization. - - - - - Skills Summary - - A Linux system administrator with a detailed knowledge of Linux in a wide variety of industries and environments. - - - - A superb communicator who will thoroughly and efficiently handle any situation requiring communication with clarity and - conciseness. - - - - A frequent speaker/writer on a wide variety of I.T and open source matters, as well as a frequent contributer to open source - projects. - - - - System and Network Administration Skills - - UNIX Administration - Debian (stable/testing/unstable) - Mandrake - SUSE - Red Hat Enterprise Linux (3/4) - Shell scripting/automation (bash/python/tcl/php/awk/sed) - - - - Linux Server Applications - Apache 1/2 - Postfix/Qmail And Cyrus/Courier - OpenLdap/Samba - IpTables/Snort/Nessus/Nmap - Webmin - Courier/Cyrus - Proftpd - - - - Storage Administration - EMC Clarion (cx400 and cx700) - Equal Logic - Promise ISCSI - - - - Server Hardware - Dell 26/28/6850 - Hp NetServer - Custom built/whitebox - - - - Networking - Cabling (backbone/serial/desktop/fiber) - Routers (Cisco/Linksys/Dlink) - Load balancing (Cisco/Webmux) - Switches (Cisco Catalyst/Linksys) - - - - - - - - I have founded two open source projects, and participated in many more by writing code/documentation and providing user/developer - support. - - - - - The Chicago Project - - This project produced code and documentation to assist developers working with the Microsoft excel and compound - document/structured storage file formats on non Microsoft platforms. I am the project manager and lead developer - for this project which is now in maintenance mode. (http://chicago.sourceforge.net) - - - - - The Open Source Microsoft Exchange Replacement Platform - - The goal of this project is to produce code and documentation that will provide a fully open source - drop in replacement for Microsoft Exchange. I am the project manager, and founder. - I work closely with the lead developer and a worldwide team of programmers, documenters, and beta testers. - (http://www.thewybles.com/~charles/oser) - - - - - - - - - - Senior Linux System Administrator - Electronic Clearing House (http://www.echo-inc.com) - - October2006 - June2006 - - - - - - Senior Linux administrator for a 24x7 transaction processing/ecommerce/ - financial services environment. Responsibilities include: Working closely - with the network administration and infrastructure design teams. Ensuring continuous - uptime of multiple high visibility/high impact/high value envrironments including: - - - - - A 1TB MySQL database. - - - - A 300 GB Oracle database. - - - - A 1.5 GB Oracle Data warehouse. - - - - A 4,000 store LAMP based ecommerce system. - - - - - - - Deployment of encrypted backups - - Designed/tested/documented/deployed an enterprise wide Linux backup system. - All data stored on a central server with ISCSI attached network storage. - Uses GNUPG and tar over ssh. Backups/Restores tested on a weekly basis. - - - - - Deployment of core database infrastructure. - - Deployed 2 Oracle RAC clusters, each consisting of 3 Dell 6850's. They are equipped with Qual Dual Core - Xeon's and 32 Gb of RAM, running RedHat Enterprise Linux 4.0 64bit edition. - One environment is for staging and one is for production. EMC attached. This environment is used for - our Data Warehouse, our Transaction Processing Software and our Credit Card Clearing application. It is a - fundamental infrastructure component. The hardware and software was deployed in 3 business days. - - - - - File Integrity Checking - - Deployment of file integrity checking across 100 UNIX servers using fully open source software. - Used integrit http://integrit.sf.net and some custom shell scripts which were submitted - back upstream for inclusion. - - - - - - - - - Consultant - - February2005 - September2005 - - - - - - LAMP Deployment: Deployed a Debian Linux/Apache/MySQL/PHP system and educated the System Administration and Development - staff on configuration and use for an insurance company located in Burbank CA. - - - - - - Corporate Linux Deployment/Migration: Providing on going assistance to a medium sized business with a 100% conversion to - Linux on the Desktop as well as server. Utilizing SUSE Professional 6.5 for desktops and Debian GNU/Linux for - multiple production mission critical servers (Email/File Server/DNS/DHCP). This is for a manufacturing company in - Sylmar CA. - - - - - - Linux Deployment/Migration: Providing on going assistance to a small software development firm with a 100% - conversion to Linux. Utilizing Ubuntu Linux for desktops and Debian GNU/Linux for - servers (Email/File/LDAP/DNS/DHCP). February 2004-Present - - - - - - - - - - Junior System Administrator - Newroads http://www.newroads.com - - March2002 - February2005 - - - - - Disaster Recovery from an Informix Database Failure - - Assisted in the design/testing/and execution of a disaster recovery in real time - (on-the-fly). Wrote and documented the use of several utilities that cut down the amount of time to recovery by 30 - percent. - - - - - Streamlined the FTP Server Configuration process - - Streamlined the system configuration and new account creation process for ProFTPD on a mission critical FTP server. - This allowed faster turn around times and freed up I.T. resources. (1 month project) - - - - - Deployed open-source Remote Control Software - - Deplopyed/Secured/Optimized/Maintained UltraVNC remote control software. This allowed the Infrastructure Support team to more - rapidly respond to users support requests, and by doing so increase compliance with Service Level Agreements and increase - end-user satisfaction. (2 month project) - - - - - Network Infrastructure Upgrade - - Upgraded the network from hubs to Linksys managed switches to increase network performance and usability/reliability. - No network downtime occurred in the process of the upgrade (1 week project) - - - - - Hardware/Software Inventory Solution - - Wrote a custom software/hardware monitoring/reporting system to ensure compliance with software licensing and obtain an - accurate overview of company assets for inventory and disaster recovery purposes. (2 month project) - - - - - - - - - - - - Classes/Courses - - Course 319: Technical Writing A Comprehensive Hands On Introduction - Learning Tree International - May 2004 - - This course showed the entire process of developing clear concise effective technical writing in less time, that meets the needs - of the audience. - - - - - Course 364: Introduction to Internetworking Switches And Routers - Learning Tree International - October2004 - - This workshop presented a conceptual overview of networking fundemntals and technology. - - - - - - diff --git a/legacy-resumes/resume-1/Makefile b/legacy-resumes/resume-1/Makefile deleted file mode 100644 index a600e3f..0000000 --- a/legacy-resumes/resume-1/Makefile +++ /dev/null @@ -1,165 +0,0 @@ -# Makefile -# -# Makefile for resumes -# -# Copyright (c) 2002 Bruce Christensen -# All rights reserved. -# -# Redistribution and use in source and binary forms, with or without -# modification, are permitted provided that the following conditions are -# met: -# -# 1. Redistributions of source code must retain the above copyright -# notice, this list of conditions and the following disclaimer. -# 2. Redistributions in binary form must reproduce the above copyright -# notice, this list of conditions and the following disclaimer in the -# documentation and/or other materials provided with the -# distribution. -# -# 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. - -#------------------------------------------------------------------------------ -# To create example.html, example.txt, example.fo, and example.pdf from -# example.xml, with Italian localization and a4 paper size, use this command: -# -# gmake resume=example country=it papersize=a4 -# -# To generate just the html version of cv.xml with UK localization, use this -# command: -# -# gmake html resume=cv country=uk -# -# To remove all generated files, run: -# -# gmake clean -#------------------------------------------------------------------------------ - -#------------------------------------------------------------------------------ -# Basename (filename minus .xml extension) of resume to process -# For example, put "myresume" here to process "myresume.xml". -#------------------------------------------------------------------------------ -resume = charlesnw-resume - -#------------------------------------------------------------------------------ -# Stylesheets -#------------------------------------------------------------------------------ -# Options: br de fr it nl uk us es -country = us -# Options: letter for country=us, a4 for others -papersize = letter - -xsl_base = http://xmlresume.sourceforge.net/xsl -#xsl_base = ../xsl -#xsl_base = ../src/www/xsl - -html_style = $(xsl_base)/output/$(country)-html.xsl -text_style = $(xsl_base)/output/$(country)-text.xsl -fo_style = $(xsl_base)/output/$(country)-$(papersize).xsl -upgrade_13x_140_style = $(xsl_base)/misc/13x-140.xsl - -#------------------------------------------------------------------------------ -# Processing software -#------------------------------------------------------------------------------ -make = gmake -out = output - -xsl_proc = java org.apache.xalan.xslt.Process $(xsl_flags) -in $(in) -xsl $(xsl) -out output/$(out) -#xsl_proc = java com.icl.saxon.StyleSheet $(xsl_flags) -o $(out) $(in) $(xsl) $(xsl_params) - -pdf_proc = java org.apache.fop.apps.Fop -fo $(fo_flags) $(in) -pdf $(out) -#pdf_proc = ~/bin/xep/run.sh $(fo_flags) $(in) $(out) - -# RTF generation currently requires you download a separate, closed source jar -# file and add it to your java classpath: -# http://www.xmlmind.com/foconverter/downloadperso.shtml -rtf_proc = java com.xmlmind.fo.converter.Driver $(in) $(out) -#rtf_proc = java ch.codeconsult.jfor.main.CmdLineConverter $(in) $(out) - -# Element filtering allows you to create targeted resumes. -# You can create your own targets; just specify them in your resume.xml -# file with the "targets" attribute. In this example, the foodservice -# AND carpentry elements will be included in the output, but not the -# elements targeted to other jobs. Untargeted elements (those with no -# "targets" attribute) are always included. -# Take a look at example2.xml and try changing the filter targets to get a -# feel for how the filter works. -filter_targets = foodservice carpentry -filter_proc = java net.sourceforge.xmlresume.filter.Filter -in $(in) -out $(out) $(filter_targets) - -#------------------------------------------------------------------------------ -# End configurable parameters -#------------------------------------------------------------------------------ - -.PHONY: all html text fo pdf clean 13x-140 - -all: html text fo pdf -html: $(resume).html -text: $(resume).txt -fo: $(resume).fo -pdf: $(resume).pdf -13x-140: $(resume)-140.xml -rtf: $(resume).rtf -filter: $(resume)-filtered.xml - -clean: - rm -f output/$(resume).html - rm -f output/$(resume).txt - rm -f output/$(resume).fo - rm -f output/$(resume).pdf - rm -f output/$(resume).rtf - rm -f output/$(resume)-filtered.xml - rm -f output/$(resume)-filtered.html - rm -f output/$(resume)-filtered.txt - rm -f output/$(resume)-filtered.pdf - rm -f output/$(resume)-filtered.fo - rm -f output/$(resume)-filtered.rtf - -$(resume).html: in = $(resume).xml -$(resume).html: out = $(resume).html -$(resume).html: xsl = $(html_style) -$(resume).html: $(resume).xml - $(xsl_proc) - -$(resume).txt: in = $(resume).xml -$(resume).txt: out = $(resume).txt -$(resume).txt: xsl = $(text_style) -$(resume).txt: $(resume).xml - $(xsl_proc) - -$(resume).fo: in = $(resume).xml -$(resume).fo: out = $(resume).fo -$(resume).fo: xsl = $(fo_style) -$(resume).fo: $(resume).xml - $(xsl_proc) - -$(resume).pdf: in = $(resume).fo -$(resume).pdf: out = $(resume).pdf -$(resume).pdf: $(resume).fo - $(pdf_proc) - -$(resume).rtf: in = $(resume).fo -$(resume).rtf: out = $(resume).rtf -$(resume).rtf: $(resume).fo - $(rtf_proc) - -$(resume)-140.xml: in = $(resume).xml -$(resume)-140.xml: out = $(resume)-140.xml -$(resume)-140.xml: xsl = $(upgrade_13x_140_style) -$(resume)-140.xml: $(resume).xml - $(xsl_proc) - -$(resume)-filtered.xml: in = $(resume).xml -$(resume)-filtered.xml: out = $(resume)-filtered.xml -$(resume)-filtered.xml: $(resume).xml - $(filter_proc) - $(make) all resume=$(resume)-filtered diff --git a/legacy-resumes/resume-1/charlesnw-resume.xml b/legacy-resumes/resume-1/charlesnw-resume.xml deleted file mode 100644 index 0d1eeb6..0000000 --- a/legacy-resumes/resume-1/charlesnw-resume.xml +++ /dev/null @@ -1,306 +0,0 @@ - - - -
- Charles Wyble -
El Monte CA
- 818.280.7059 charles@knownelement.com 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. - - - - - Skills Summary - - - 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) - - October2008 - January2010 - - - - - 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 - - September2007 - October2008 - - - - - 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 - - August2006 - September2007 - - - - - 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. - - - - - <emphasis>Automated numerous routine system administration tasks</emphasis> - Created numerous batch and VbScript programs to handle all aspects of Windows administration from the command line. - - - - <emphasis>Active Directory Project for WDIG</emphasis> - Designed and implemented a nation wide, 3 data center, highly available Active Directory system to handle both the - PCI and non PCI servers for the Walt Disney Internet Group. - - - - <emphasis>Windows NT to Active Directory migration</emphasis> - Migrated all the application servers off of Windows NT to Windows 2003 Active Directory domain controllers. - Also have experience with Windows 2008 (including Linux/Cisco/wireless - [wpa2 enterprise] authentication). Used both Centrify and Samba/Winbind/LDAP/Kerberos. - - - - - - - - - - Linux Systems Engineer - Intuit Inc (via acquistion of Electronic Clearing House) - - October2005 - June2006 - - - - - 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). - - - - - - <emphasis>Deployment of encrypted backups.</emphasis> - Designed/tested/documented/deployed an enterprise wide Linux backup system. - All data stored on a central server with ISCSI attached network storage. - Uses GNUPG and tar over ssh. Backups/Restores tested on a weekly basis. - - - - <emphasis>Deployment of Oracle database infrastructure.</emphasis> - Deployed 2 Oracle RAC clusters, each consisting of 3 Dell 6850's. They are equipped with Qual Dual Core - Xeon's and 32 Gb of RAM, running RedHat Enterprise Linux 4.0 64bit edition. - One environment is for staging and one is for production. EMC attached. This environment is used for - Data Warehouse, Transaction Processing Software and Credit Card Clearing applications. - The hardware and software was deployed in 3 business days. - - - - <emphasis>File Integrity Checking system for PCI compliance.</emphasis> - Deployment of file integrity checking across 100 UNIX servers using fully open source software. - Used integrit http://integrit.sf.net and some custom shell scripts which were submitted - back upstream for inclusion. - - - - - - - Linux, Windows, network and security consulting for various startups and defense contractors - Multiple entities - - February2005 - October2005 - - - - - <emphasis>LAMP Deployment </emphasis> - Deployed a Debian Linux/Apache/MySQL/PHP system and educated the System Administration and Development - staff on configuration and use for an insurance company. - - - - <emphasis>Corporate Linux Deployment/Migration</emphasis> - Provided assistance to a medium sized engineering firm with a near 100% - conversion to Linux on the desktop and server. Utilizing SUSE Professional 6.5 for desktops and Debian GNU/Linux for - servers (Email/File Server/DNS/DHCP). - - - - <emphasis>Linux Deployment/Migration</emphasis> - Provided assistance to a small software development firm with a near 100% - conversion to Linux. Utilized Ubuntu Linux for desktops and Debian GNU/Linux for servers - (Email/File/LDAP/DNS/DHCP). - - - - - - Linux/Windows Systems Engineer - GSI Commerce (via acquisition of Newroads Inc) - - July2002 - February2005 - - - - - <emphasis>Disaster Recovery from an Informix Database failure.</emphasis> - Assisted in the design/testing/and execution of a disaster recovery in real time - (on-the-fly). Wrote and documented the use of several utilities that cut down the amount of time to recovery by 30 - percent. - - - - <emphasis>Streamlined the FTP Server Configuration process.</emphasis> - Streamlined the system configuration and new account creation process for ProFTPD on a mission critical FTP server. - This allowed faster turn around times and freed up IT resources. - - - - <emphasis>Deployed open-source Remote Control Software.</emphasis> - Deplopyed/Secured/Optimized/Maintained UltraVNC remote control software. This allowed the Infrastructure Support team to more - rapidly respond to users support requests, and by doing so increase compliance with Service Level Agreements and increase - end-user satisfaction. - - - - <emphasis>Network Infrastructure Upgrade.</emphasis> - Upgraded the network from hubs to Linksys managed switches to increase network performance and usability/reliability. - No network downtime occurred in the process of the upgrade. - - - - <emphasis>Hardware/Software Inventory Solution</emphasis>: - Wrote a custom software/hardware monitoring/reporting system to ensure compliance with software licensing and obtain an - accurate overview of company assets for inventory and disaster recovery purposes. Utilized WMI/Visio/Microsoft Access. - - - - - - diff --git a/legacy-resumes/resume-1/css/NOTICE b/legacy-resumes/resume-1/css/NOTICE deleted file mode 100644 index 65f78a5..0000000 --- a/legacy-resumes/resume-1/css/NOTICE +++ /dev/null @@ -1,24 +0,0 @@ -Redistribution and use in source and binary forms, with or without -modification, are permitted provided that the following conditions are -met: - -1. Redistributions of source code must retain the above copyright - notice, this list of conditions and the following disclaimer. -2. Redistributions in binary form must reproduce the above copyright - notice, this list of conditions and the following disclaimer in the - documentation and/or other materials provided with the - distribution. - -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/css/blueorange.css b/legacy-resumes/resume-1/css/blueorange.css deleted file mode 100644 index cb4e88e..0000000 --- a/legacy-resumes/resume-1/css/blueorange.css +++ /dev/null @@ -1,62 +0,0 @@ - - - -/* - * color.css -- A high-color stylesheet that looks great on the web. - * background: blue and orange-beige, primary fonts: Verdana and Trebuchet - * - * Contributed 2001 by Bruce Christensen - * http://xmlresume.sourceforge.net - */ - -// This dummy style must be here because the xml tags above cause some -// browsers (Konqueror, Mozilla) to ignore the first style -.dummy { background-color: white } - -body { - font-family: verdana, arial, helvetica, sans-serif; - background-color: #336699; - margin: 20px; -} -.resume { - background-color: #ffcc99; - border: 1px solid white; - margin-bottom: 20px; - padding-left: 30pt; - padding-right: 30pt; -} -.heading { - margin-left: -20pt; -} -h1, h2, h3 { - font-family: trebuchet ms, verdana, arial, helvetica, sans-serif; -} -.headingText { - background-color: #336699; - color: white; - padding: 2px; - border: 1px solid #999999; -} -p { - margin-bottom: 0.5em; - margin-top: 0.5em; -} - -.awardTitle { font-weight: bold } -.bookTitle { font-style: italic } -.citation { font-style: italic } -.clearanceLevel { font-weight: bold } -.copyright { font-size: 75% } -li.degree { margin-bottom: 0.5em; } -.degreeTitle { font-weight: bold } -.employer { font-style: italic } -.jobTitle { font-weight: bold } -.lastModified { font-size: 75% } -.membershipTitle { font-weight: bold } -div.referee { margin-bottom: 1em; } -.refereeName { font-weight: bold } -.skillsetTitle { font-weight: bold } -table.referees { width: 80% ; } - - diff --git a/legacy-resumes/resume-1/css/compact.css b/legacy-resumes/resume-1/css/compact.css deleted file mode 100644 index 9ca9432..0000000 --- a/legacy-resumes/resume-1/css/compact.css +++ /dev/null @@ -1,62 +0,0 @@ - - - -/* - * compact.css -- Stylesheet suitable for printing an xmlresume to dead - * trees without using too many of them (Arial font, white background) - * - * Contributed 2002 by Mark Miller (joup at bigfoot dot com) - * http://xmlresume.sourceforge.net - */ - -// This dummy style must be here because the xml tags above cause some -// browsers (Konqueror, Mozilla) to ignore the first style -.dummy { background-color: white } - -body, table { - margin-top: 1cm; - margin-bottom: 1cm; - font-size: 8pt; - background-color: white; - font-family: Arial, Verdana, sans-serif; -} - -.resume { - padding-left: 1.5cm; - padding-right: 1.5cm; -} -h2 { - margin-left: -.8cm; - font-family: sans-serif; - color: black; - border-bottom: solid 1pt black; - font-size: 115%; -} -p { - margin-bottom: 0.05cm; - margin-top: 0.15cm; -} -em { font-weight: bold; } -ul { margin-top: 0.1cm; } - -.projects p { font-style: italic } -ul.degrees { padding-left: 0.2cm; } -.subjectsHeading { font-style: italic } -.awardTitle { font-weight: bold } -.bookTitle { font-style: italic } -.citation { font-style: italic } -.copyright { font-size: 75% } -li.degree { margin-bottom: 0.2cm; } -.degreeTitle { font-weight: bold } -.employer { font-style: italic } -.headerBlock { text-align: left } -.jobTitle { font-weight: bold } -.lastModified { font-size: 75% } -.nameHeading { font-family: sans-serif; font-size: 125%; } -div.referee { margin-bottom: 0.5cm; } -table.referees { width: 60%; margin-top: 0cm; margin-bottom: 0cm;} -.refereeName { font-weight: bold } -.skillsetTitle { font-weight: bold } -.urlA { font-family:sans-serif; color:red; } - - diff --git a/legacy-resumes/resume-1/css/cssClasses.sh b/legacy-resumes/resume-1/css/cssClasses.sh deleted file mode 100644 index 19dc123..0000000 --- a/legacy-resumes/resume-1/css/cssClasses.sh +++ /dev/null @@ -1,7 +0,0 @@ -#!/bin/sh - -# cssClasses -- create a list of all available css classes. -# If you do not have a Unix environment available, please look -# at cssClasses.txt for a (possibly outdated) list. - -perl -p -e 's/class\=\"([a-zA-Z]*)\"\>/\nXXXX $1\n/mg' ../xsl/format/html.xsl | grep XXXX | sort | uniq | awk '{print $2}' diff --git a/legacy-resumes/resume-1/css/cssClasses.txt b/legacy-resumes/resume-1/css/cssClasses.txt deleted file mode 100644 index 3839631..0000000 --- a/legacy-resumes/resume-1/css/cssClasses.txt +++ /dev/null @@ -1,46 +0,0 @@ -achievement -achievements -address -award -awardTitle -citation -clearance -clearanceLevel -copyright -degree -degreeTitle -degrees -emphasis -employer -gpaPreamble -header -heading -headingText -institution -interestTitle -job -jobTitle -lastModified -linkA -location -membershipTitle -nameHeading -note -organization -para -project -projects -pub -pubs -referee -refereeAddress -refereeContact -refereeName -referees -resume -skill -skills -skillsetTitle -subjects -subjectsHeading -urlA diff --git a/legacy-resumes/resume-1/css/gray.css b/legacy-resumes/resume-1/css/gray.css deleted file mode 100644 index e923a19..0000000 --- a/legacy-resumes/resume-1/css/gray.css +++ /dev/null @@ -1,49 +0,0 @@ - - - -/* - * gray.css -- A professional-looking stylesheet with gray background and - * sans-serif font. - * - * Contributed 2001 by Stewart Evans and Bruce Christensen - * http://xmlresume.sourceforge.net -*/ - -.dummy { background-color: white } - -.resume { - background-color: #eeeeee; - padding-left: 30pt; - padding-right: 30pt; -} -h2 { - margin-left: -20pt; - font-family: sans-serif; - color: black; - border-bottom: solid 1pt black; -} -p { - margin-bottom: 0.5em; - margin-top: 0.5em; -} - - -.awardTitle { font-weight: bold } -.bookTitle { font-style: italic } -.citation { font-style: italic } -.clearanceLevel { font-weight: bold } -.copyright { font-size: 75% } -li.degree { margin-bottom: 0.5em; } -.degreeTitle { font-weight: bold } -.employer { font-style: italic } -.headerBlock { text-align: center } -.jobTitle { font-weight: bold } -.lastModified { font-size: 75% } -.nameHeading { text-align: center; font-family: sans-serif } -div.referee { margin-bottom: 1em; } -.refereeName { font-weight: bold } -.skillsetTitle { font-weight: bold } -.urlA { font-family:sans-serif; color:red; } -table.referees { width: 80% ; } - - diff --git a/legacy-resumes/resume-1/css/original.css b/legacy-resumes/resume-1/css/original.css deleted file mode 100644 index c84b4a9..0000000 --- a/legacy-resumes/resume-1/css/original.css +++ /dev/null @@ -1,94 +0,0 @@ - - - -/* - * original.css -- The first stylesheet. From the author: "This is a - * sample only, and probably is quite offensive in terms of taste and - * style." Background: off-white, fonts: Georgia, Trebuchet - * - * Contributed 2001 by Sean Kelly - * http://xmlresume.sourceforge.net - */ - -// This dummy style must be here because the xml tags above cause some -// browsers (Konqueror, Mozilla) to ignore the first style -.dummy { background-color: white } - -body { - font-family: Georgia, Minion Web, Palatino, Book Antiqua, Utopia, Times New Roman, serif; - margin: 30px 30px 30px 30px - color: black; - background: #fffff3; -} - -pre, code { - font-family: 'Monotype.com', Courier New, monospace; -} - -ol li { - list-style-type: decimal; -} - -ol ol li { - list-style-type: lower-alpha; -} - -ol ol ol li { - list-style-type: lower-roman; -} - -h1 { - font-family: Trebuchet MS, Verdana, Myriad Web, Syntax, sans-serif; - font-weight: bold; -} - -h2 { - font-family: Trebuchet MS, Verdana, Myriad Web, Syntax, sans-serif; - font-size: 1.75em; - font-weight: bold; -} - -.bookTitle { - font-style: italic; -} - -.citation { - font-style: italic; -} - -.objectiveHeading { - color: red; -} - -.contactHeading { - color: orange; -} - -.skillareaHeading { - color: #00bb00; -} - -.historyHeading { - color: violet; -} - -.membershipsHeading { - color: magenta; -} - -.organization { - font-style: italic; -} - -.urlA { - font-family: 'Monotype.com', Courier New, monospace; - border-width: 1px; - border-style: solid solid solid solid; - border-color: blue; -} -.clearanceLevel { font-weight: bold } - -table.referees { width: 80% ; } - - diff --git a/legacy-resumes/resume-1/css/professional.css b/legacy-resumes/resume-1/css/professional.css deleted file mode 100644 index a1f4f36..0000000 --- a/legacy-resumes/resume-1/css/professional.css +++ /dev/null @@ -1,627 +0,0 @@ - - - -/* - * professional.css -- similar to MS Word's "professional" resume style. - * - * http://xmlresume.sourceforge.net - */ - -// This dummy style must be here because the xml tags above cause some -// browsers (Konqueror, Mozilla) to ignore the first style -.dummy { background-color: white } - - /* Font Definitions */ - @font-face - {font-family:Wingdings; - panose-1:5 0 0 0 0 0 0 0 0 0; - mso-font-charset:2; - mso-generic-font-family:auto; - mso-font-pitch:variable; - mso-font-signature:0 268435456 0 0 -2147483648 0;} -@font-face - {font-family:Batang; - panose-1:2 3 6 0 0 1 1 1 1 1; - mso-font-alt:\BC14\D0D5; - mso-font-charset:129; - mso-generic-font-family:roman; - mso-font-pitch:variable; - mso-font-signature:-1342176593 1775729915 48 0 524447 0;} -@font-face - {font-family:"Arial Black"; - panose-1:2 11 10 4 2 1 2 2 2 4; - mso-font-charset:0; - mso-generic-font-family:swiss; - mso-font-pitch:variable; - mso-font-signature:647 0 0 0 159 0;} -@font-face - {font-family:"\@Batang"; - panose-1:2 3 6 0 0 1 1 1 1 1; - mso-font-charset:129; - mso-generic-font-family:roman; - mso-font-pitch:variable; - mso-font-signature:-1342176593 1775729915 48 0 524447 0;} - /* Style Definitions */ -MsoNormal, p.MsoNormal, li.MsoNormal, div.MsoNormal - {margin-bottom:.0001pt; - mso-pagination:widow-orphan; - font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial"; margin-left:0in; margin-right:0in; margin-top:0in} -h1 - {mso-style-parent:"Heading Base"; - mso-style-next:"Body Text"; - margin-top:11.0pt; - margin-right:0in; - margin-bottom:11.0pt; - margin-left:-1.5in; - line-height:11.0pt; - mso-pagination:widow-orphan lines-together; - page-break-after:avoid; - mso-outline-level:1; - font-size:10.0pt; - font-family:"Arial Black"; - letter-spacing:-.2pt; - mso-font-kerning:14.0pt; - font-weight:normal;} -h2 - {mso-style-parent:"Heading Base"; - mso-style-next:"Body Text"; - margin-top:0in; - margin-right:0in; - margin-bottom:11.0pt; - margin-left:0in; - line-height:11.0pt; - mso-pagination:widow-orphan lines-together; - page-break-after:avoid; - mso-outline-level:2; - font-size:10.0pt; - font-family:"Arial Black"; - letter-spacing:-.2pt; - font-weight:normal;} -h3 - {mso-style-parent:"Heading Base"; - mso-style-next:"Body Text"; - margin-top:0in; - margin-right:0in; - margin-bottom:11.0pt; - margin-left:0in; - line-height:11.0pt; - mso-pagination:widow-orphan lines-together; - page-break-after:avoid; - mso-outline-level:3; - font-size:10.0pt; - font-family:Arial; - mso-bidi-font-family:"Arial"; - letter-spacing:-.1pt; - font-weight:normal; - font-style:italic; - mso-bidi-font-style:normal;} -h4 - {mso-style-parent:"Heading Base"; - mso-style-next:"Body Text"; - margin:0in; - margin-bottom:.0001pt; - line-height:11.0pt; - mso-pagination:widow-orphan lines-together; - page-break-after:avoid; - mso-outline-level:4; - font-size:10.0pt; - font-family:"Arial Black"; - letter-spacing:-.2pt; - font-weight:normal;} -h5 - {mso-style-parent:"Heading Base"; - mso-style-next:"Body Text"; - margin-top:0in; - margin-right:0in; - margin-bottom:11.0pt; - margin-left:0in; - line-height:11.0pt; - mso-pagination:widow-orphan lines-together; - page-break-after:avoid; - mso-outline-level:5; - font-size:8.0pt; - mso-bidi-font-size:10.0pt; - font-family:"Arial Black"; - letter-spacing:-.2pt; - font-weight:normal;} -h6 - {mso-style-next:Normal; - margin-top:12.0pt; - margin-right:0in; - margin-bottom:3.0pt; - margin-left:0in; - text-align:justify; - text-justify:inter-ideograph; - mso-pagination:widow-orphan; - mso-outline-level:6; - font-size:11.0pt; - mso-bidi-font-size:10.0pt; - font-family:Arial; - mso-bidi-font-family:"Arial"; - font-weight:normal; - font-style:italic; - mso-bidi-font-style:normal;} -MsoHeader, p.MsoHeader, li.MsoHeader, div.MsoHeader - {mso-style-parent:"Header Base"; - margin-top:0in; - margin-right:0in; - margin-bottom:0in; - margin-left:-1.5in; - margin-bottom:.0001pt; - text-align:justify; - text-justify:inter-ideograph; - line-height:11.0pt; - mso-pagination:widow-orphan; - font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial";} -MsoFooter, p.MsoFooter, li.MsoFooter, div.MsoFooter - {mso-style-parent:"Header Base"; - margin-top:0in; - margin-right:0in; - margin-bottom:0in; - margin-left:-1.5in; - margin-bottom:.0001pt; - text-align:justify; - text-justify:inter-ideograph; - line-height:11.0pt; - mso-pagination:widow-orphan; - tab-stops:right 4.75in; - font-size:9.0pt; - mso-bidi-font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial"; - font-weight:bold; - mso-bidi-font-weight:normal;} -span.MsoPageNumber - {mso-style-parent:""; - mso-ansi-font-size:9.0pt; - font-family:Arial; - mso-ascii-font-family:Arial; - mso-hansi-font-family:Arial} -MsoBodyText, p.MsoBodyText, li.MsoBodyText, div.MsoBodyText - {margin-top:0in; - margin-right:0in; - margin-bottom:11.0pt; - margin-left:0in; - text-align:justify; - text-justify:inter-ideograph; - line-height:11.0pt; - mso-pagination:widow-orphan; - font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial"; - letter-spacing:-.25pt;} -p.MsoBodyTextIndent, li.MsoBodyTextIndent, div.MsoBodyTextIndent - {mso-style-parent:"Body Text"; - margin-top:0in; - margin-right:0in; - margin-bottom:11.0pt; - margin-left:.5in; - text-align:justify; - text-justify:inter-ideograph; - line-height:11.0pt; - mso-pagination:widow-orphan; - font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial"; - letter-spacing:-.25pt;} -date,p.date,div.date,p.MsoDate, li.MsoDate, div.MsoDate - {display: inline; - margin-top:0.0pt; - margin-right:0in; - margin-bottom:12.0pt; - margin-left:0in; - text-align:justify; - text-justify:inter-ideograph; - line-height:11.0pt; - mso-pagination:widow-orphan; - page-break-after:avoid; - font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:Arial; - letter-spacing:-.25pt;} -em - {mso-style-parent:""; - mso-ansi-font-size:9.0pt; - font-family:"Arial Black"; - mso-ascii-font-family:"Arial Black"; - mso-hansi-font-family:"Arial Black"; - letter-spacing:-.4pt; - font-style:normal} -achievement, p.achievement, li.Achievement, div.Achievement - mso-style-name:Achievement; - list-style: disc; - mso-style-parent:"Body Text"; - margin-top:0in; - margin-right:12.25pt; - margin-bottom:3.0pt; - margin-left:12.25pt; - text-align:justify; - text-justify:inter-ideograph; - text-indent:-12.25pt; - line-height:11.0pt; - mso-pagination:widow-orphan; - mso-list:l0 level1 lfo1; - font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial"; - letter-spacing:-.25pt;} -address, table.address, p.Address1, li.Address1, div.Address1 - {mso-style-name:"Address 1"; - margin:0in; - margin-bottom:.0001pt; - text-align:left; - text-justify:inter-ideograph; - line-height:8.0pt; - mso-pagination:widow-orphan; - font-size:7.0pt; - mso-bidi-font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial"; - border-style:solid; - border-width: 0.0pt;} -email, url, address, phone, p.Address2, li.Address2, div.Address2 - {mso-style-name:"Address 2"; - margin:0in; - margin-bottom:.0001pt; - text-align:justify; - text-justify:inter-ideograph; - line-height:8.0pt; - mso-pagination:widow-orphan; - font-size:7.0pt; - mso-bidi-font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial";} -citystate, div.citystate,p.CityState, li.CityState, div.CityState - {mso-style-name:"City\/State"; - display:inline; - margin-top:0in; - margin-right:0in; - margin-bottom:0.0pt; - margin-left:24.0pt; - text-align:right; - text-justify:right; - line-height:11.0pt; - mso-pagination:widow-orphan; - page-break-after:avoid; - font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial"; - letter-spacing:-.25pt;} -institution, p.institution, li.Institution, div.institution - { - display: inline; - mso-style-update:auto; - mso-style-next:Normal; - margin-top:0.0pt; - margin-right:60.0pt; - margin-bottom:2.0pt; - margin-left:104.0pt; - line-height:11.0pt; - mso-pagination:widow-orphan; - tab-stops:1.5in right 4.5in; - font-size:10.0pt; - font-family:"Arial"; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial";} -div.employer, p.CompanyName, li.CompanyName, div.CompanyName - {mso-style-name:"Company Name"; - display: inline; - mso-style-update:auto; - mso-style-next:Normal; - margin-top:0.0pt; - margin-right:60.0pt; - margin-bottom:2.0pt; - margin-left:60.0pt; - line-height:11.0pt; - mso-pagination:widow-orphan; - tab-stops:1.5in right 4.5in; - font-size:10.0pt; - font-family:"Arial"; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial";} -p.CompanyNameOne, li.CompanyNameOne, div.CompanyNameOne - {mso-style-name:"Company Name One"; - mso-style-update:auto; - mso-style-parent:"Company Name"; - mso-style-next:Normal; - margin-top:12.0pt; - margin-right:0in; - margin-bottom:2.0pt; - margin-left:0in; - line-height:11.0pt; - mso-pagination:widow-orphan; - tab-stops:1.5in right 4.5in; - font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial";} -p.DocumentLabel, li.DocumentLabel, div.DocumentLabel - {mso-style-name:"Document Label"; - mso-style-next:Normal; - margin-top:0in; - margin-right:0in; - margin-bottom:11.0pt; - margin-left:0in; - text-align:justify; - text-justify:inter-ideograph; - mso-pagination:widow-orphan; - font-size:24.0pt; - mso-bidi-font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial"; - letter-spacing:-1.0pt;} -p.HeaderBase, li.HeaderBase, div.HeaderBase - {mso-style-name:"Header Base"; - margin:0in; - margin-bottom:.0001pt; - text-align:justify; - text-justify:inter-ideograph; - mso-pagination:widow-orphan; - font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial";} -p.HeadingBase, li.HeadingBase, div.HeadingBase - {mso-style-name:"Heading Base"; - mso-style-parent:"Body Text"; - mso-style-next:"Body Text"; - margin:0in; - margin-bottom:.0001pt; - text-align:justify; - text-justify:inter-ideograph; - line-height:11.0pt; - mso-pagination:widow-orphan lines-together; - page-break-after:avoid; - font-size:9.0pt; - mso-bidi-font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial"; - letter-spacing:-.2pt;} -academics, memberships - { - display:inline; - mso-style-update:auto; - margin-top:12.0pt; - margin-right:0in; - margin-bottom:3.0pt; - margin-left:0in; - line-height:11.0pt; - mso-pagination:widow-orphan; - tab-stops:1.5in right 4.5in; - font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial";} -job, span.Job - {mso-style-name:Job;} -jobtitle, p.jobtitle, li.jobtitle, div.jobtitle, JobTitle, p.JobTitle, li.JobTitle, div.JobTitle - {mso-style-name:"jobtitle"; - margin-top:0in; - margin-right:0in; - margin-bottom:0.0pt; - margin-left:0in; - line-height:11.0pt; - mso-pagination:widow-orphan; - font-size:10.0pt; - font-family:"Arial Black"; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial"; - letter-spacing:-.5pt} -span.Lead-inEmphasis - {mso-style-name:"Lead-in Emphasis"; - mso-style-parent:""; - mso-ansi-font-size:9.0pt; - font-family:"Arial Black"; - mso-ascii-font-family:"Arial Black"; - mso-hansi-font-family:"Arial Black"; - letter-spacing:-.3pt} -name, p.Name, li.Name, div.name - {mso-style-name:Name; - mso-style-next:Normal; - margin-top:0.0in; - margin-right:0in; - margin-bottom:0.0pt; - margin-left:0in; - mso-line-height-alt:12.0pt; - mso-pagination:widow-orphan; - border:none; - mso-border-bottom-alt:solid windowtext .75pt; - padding:0in; - mso-padding-alt:0in 0in 4.0pt 0in; - font-size:27.0pt; - mso-bidi-font-size:10.0pt; - font-family:"Arial Black"; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial"; - letter-spacing:-1.75pt;} -p.SectionTitle, li.SectionTitle, div.SectionTitle - {mso-style-name:"Section Title"; - mso-style-update:auto; - mso-style-next:Normal; - margin-top:0.0pt; - margin-right:0in; - margin-bottom:0in; - margin-left:0in; - margin-bottom:.0001pt; - line-height:11.0pt; - mso-pagination:widow-orphan; - font-size:10.0pt; - font-family:"Arial Black"; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial"; - letter-spacing:-.5pt;} -p.NoTitle, li.NoTitle, div.NoTitle - {mso-style-name:"No Title"; - mso-style-parent:"Section Title"; - margin-top:11.0pt; - margin-right:0in; - margin-bottom:0in; - margin-left:0in; - margin-bottom:.0001pt; - line-height:11.0pt; - mso-pagination:widow-orphan; - font-size:10.0pt; - font-family:"Arial Black"; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial"; - letter-spacing:-.5pt;} -objective, p.Objective, li.Objective, div.Objective, p.summary, td.summary, history, td.history, tr.history, table.history - {mso-style-name:Objective; - margin-top:12.0pt; - margin-right:0in; - margin-bottom:11.0pt; - margin-left:0in; - line-height:11.0pt; - font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial";} -p.PersonalData, li.PersonalData, div.PersonalData - {mso-style-name:"Personal Data"; - mso-style-parent:"Body Text"; - margin-top:0in; - margin-right:.75in; - margin-bottom:6.0pt; - margin-left:-.75in; - text-align:justify; - text-justify:inter-ideograph; - line-height:12.0pt; - mso-line-height-rule:exactly; - mso-pagination:widow-orphan; - font-size:11.0pt; - mso-bidi-font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial"; - font-style:italic; - mso-bidi-font-style:normal;} -p.PersonalInfo, li.PersonalInfo, div.PersonalInfo - {mso-style-name:"Personal Info"; - mso-style-parent:Achievement; - mso-style-next:Achievement; - margin-top:12.0pt; - margin-right:12.25pt; - margin-bottom:3.0pt; - margin-left:12.25pt; - text-align:justify; - text-justify:inter-ideograph; - text-indent:-12.25pt; - line-height:11.0pt; - mso-pagination:widow-orphan; - font-size:10.0pt; - font-family:Arial; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial"; - letter-spacing:-.25pt;} -p.SectionSubtitle, li.SectionSubtitle, div.SectionSubtitle - {mso-style-name:"Section Subtitle"; - mso-style-parent:"Section Title"; - mso-style-next:Normal; - margin-top:11.0pt; - margin-right:0in; - margin-bottom:0in; - margin-left:0in; - margin-bottom:.0001pt; - line-height:11.0pt; - mso-pagination:widow-orphan; - font-size:10.0pt; - font-family:"Arial Black"; - mso-fareast-font-family:Batang; - mso-bidi-font-family:"Arial"; - font-weight:bold; - mso-bidi-font-weight:normal;} -@page Section1 - {size:8.5in 11.0in; - margin:1.0in 1.25in 1.0in 1.25in; - mso-header-margin:48.25pt; - mso-footer-margin:48.25pt; - mso-title-page:yes; - mso-first-header:url("Professional%20Resume_files/header.htm") fh1; - mso-paper-source:0;} -div.Section1 - {page:Section1;} - /* List Definitions */ - @list l0 - {mso-list-id:1723291136; - mso-list-type:simple; - mso-list-template-ids:-339983110;} -@list l0:level1 - {mso-level-number-format:bullet; - mso-level-style-link:Achievement; - mso-level-text:\F0A7; - mso-level-tab-stop:.25in; - mso-level-number-position:left; - margin-top:0in; - margin-right:12.25pt; - margin-bottom:0in; - margin-left:12.25pt; - margin-bottom:.0001pt; - text-indent:-12.25pt; - font-family:Wingdings;} -ol - {margin-bottom:0in;} -ul - {margin-bottom:0in;} - /* Style Definitions */ - table.MsoNormalTable - {mso-style-name:"Table Normal"; - mso-tstyle-rowband-size:0; - mso-tstyle-colband-size:0; - mso-style-noshow:yes; - mso-style-parent:""; - mso-padding-alt:0in 5.4pt 0in 5.4pt; - mso-para-margin:0in; - mso-para-margin-bottom:.0001pt; - mso-pagination:widow-orphan; - border-width:0.0pt; - border-style:solid; - border-collapse: collapse; - font-size:10.0pt; - font-family:"Arial"} -td.SectionDescriptor, - {width: 1.0in; - vertical-align:text-top; - padding-left: 5.4pt; - padding-right: 5.4pt; - padding-top: 5.4pt; - padding-bottom: 0in;} -td.SectionContent - {width: 5.4in; - vertical-align:text-top; - padding-left: 5.4pt; - padding-right: 5.4pt; - padding-top: 5.4pt; - padding-bottom: 0in; } -td.address1cell - {vertical-align: text-top; - width:1.0in; - padding:0in 5.4pt 0in 5.4pt; - } -td.address2cell - {vertical-align: text-top; - text-width:4.5in; - padding:0in 5.4pt 0in 5.4pt; -span.skill, div.skill, td.skil - {font-family:Wingdings; - mso-fareast-font-family:Wingdings; - mso-bidi-font-family:Wingdings"; - } -table.referees { width: 80% ; } - - diff --git a/legacy-resumes/resume-1/doc/authors/index.html b/legacy-resumes/resume-1/doc/authors/index.html deleted file mode 100644 index c06c976..0000000 --- a/legacy-resumes/resume-1/doc/authors/index.html +++ /dev/null @@ -1,106 +0,0 @@ - - - - XML Resume Library Authors - - -

XML Résumé Library Authors

- -

The XML Résumé Library copyrighted, © - 2000-2002 by Sean Kelly. See the copying conditions, license, and - disclaimer. -

- -

Core Team

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Sean KellyProject Manager
Stewart EvansInformation Analyst/Designer
Bruce ChristensenDeveloper and Project Manager
Robert DubinskiDeveloper
Olivier EymereDeveloper
Rob KelleyDeveloper
Dave LeeDeveloper
Brian MayDeveloper
Paul SargentDeveloper
Mark MillerDeveloper
Nick ChalkoDeveloper
- -

Contributors

- -

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. -

- - - diff --git a/legacy-resumes/resume-1/doc/changelog/index.html b/legacy-resumes/resume-1/doc/changelog/index.html deleted file mode 100644 index 0aaaf48..0000000 --- a/legacy-resumes/resume-1/doc/changelog/index.html +++ /dev/null @@ -1,1518 +0,0 @@ - - - - XML Resume Library ChangeLog - - -

XML Résumé Library Changelog

- -

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
-	   ("&#x9;" -> " ")
-	 - 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 &copyr; to &copy;.
-
-	* /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 deleted file mode 100644 index b014565..0000000 --- a/legacy-resumes/resume-1/doc/copying/index.html +++ /dev/null @@ -1,45 +0,0 @@ - - - - XML Resume Library Copying Conditions, License, and Disclaimer - - -

XML Résumé Library Copying Conditions, License, - and Disclaimer

- -

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: -

- -
    -
  1. Redistributions of source code must retain the above copyright - notice, this list of conditions and the following disclaimer. -
    2. -
  2. Redistributions in binary form must reproduce the above - copyright notice, this list of conditions and the following - disclaimer in the documentation and/or other materials - provided with the distribution. -
    3. -
- -

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 deleted file mode 100644 index 8d3d61e..0000000 --- a/legacy-resumes/resume-1/doc/index.html +++ /dev/null @@ -1,318 +0,0 @@ - - - - XML Resume Library - - -

XML Résumé Library

- -

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. -

- -

What's Included

- -

The XML Résumé Library includes the following: -

- - - -

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:

- - - -

Requirements

- -

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. -

- -

Upgrading to version 1.4.0

- -

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
- -

Creating Résumés Using the DTD

- -

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. -

- -

Formatting Résumés

- -

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. -

- -

Creating an HTML Presentation

- -

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: -

- -

The stylesheet will turn your XML résumé into - HTML using appropriate phrasing and terminology. -

- -

Customizing the HTML Output

- -

- 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. -

- -

Creating a PDF Presentation

- -

To create a PDF presentation, follows these steps:

- -
    -
  1. Run your XSLT engine on the résumé XML file - along with one of the FO stylesheet files: - - -

    This will transform your XML file into another XML file - that defines formatting objects (usually named with a - .fo extension). -

    -
    2. -
  2. Run the formatting object output through your FO engine to - render it to PDF. -
    3. -
- -

Creating a Plain Text Presentation

- -

To create a plain text presentation, run your XSLT engine on - the résumé XML file and one of the following: -

- - - -

Automating Formatting

- -

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.

- -

Configurable Parameters

- -

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 deleted file mode 100644 index 307778b..0000000 --- a/legacy-resumes/resume-1/doc/install/index.html +++ /dev/null @@ -1,28 +0,0 @@ - - - - XML Resume Library Installation - - -

XML Résumé Library Installation

- -

The XML Résumé Library copyrighted, © - 2000-2002 by Sean Kelly. See the copying conditions, license, and - disclaimer. -

- -

Installation Instructions

- -

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 deleted file mode 100644 index a01eacc..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/appendixes.html +++ /dev/null @@ -1,4 +0,0 @@ - - - Part III. Appendixes

XMLRésuméLibrary: - User Guide

PreviousGlossary UpXML Résumé Library User Guide GNU Free Documentation LicenseNext

Appendixes

Table of Contents

A. GNU Free Documentation License
PREAMBLE
APPLICABILITY AND DEFINITIONS
VERBATIM COPYING
COPYING IN QUANTITY
MODIFICATIONS
COMBINING DOCUMENTS
COLLECTIONS OF DOCUMENTS
AGGREGATION WITH INDEPENDENT WORKS
TRANSLATION
TERMINATION
FUTURE REVISIONS OF THIS LICENSE
How to use this License for your documents
PreviousGlossary UpXML Résumé Library User Guide GNU Free Documentation LicenseNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/box-0.gif b/legacy-resumes/resume-1/doc/manual/html/box-0.gif deleted file mode 100644 index 65d30d7..0000000 Binary files a/legacy-resumes/resume-1/doc/manual/html/box-0.gif and /dev/null differ diff --git a/legacy-resumes/resume-1/doc/manual/html/box-1.gif b/legacy-resumes/resume-1/doc/manual/html/box-1.gif deleted file mode 100644 index e679f85..0000000 Binary files a/legacy-resumes/resume-1/doc/manual/html/box-1.gif and /dev/null differ diff --git a/legacy-resumes/resume-1/doc/manual/html/caret-l.gif b/legacy-resumes/resume-1/doc/manual/html/caret-l.gif deleted file mode 100644 index 80db02d..0000000 Binary files a/legacy-resumes/resume-1/doc/manual/html/caret-l.gif and /dev/null differ diff --git a/legacy-resumes/resume-1/doc/manual/html/caret-r.gif b/legacy-resumes/resume-1/doc/manual/html/caret-r.gif deleted file mode 100644 index f06f0ab..0000000 Binary files a/legacy-resumes/resume-1/doc/manual/html/caret-r.gif and /dev/null differ diff --git a/legacy-resumes/resume-1/doc/manual/html/caret-t.gif b/legacy-resumes/resume-1/doc/manual/html/caret-t.gif deleted file mode 100644 index d4cf004..0000000 Binary files a/legacy-resumes/resume-1/doc/manual/html/caret-t.gif and /dev/null differ diff --git a/legacy-resumes/resume-1/doc/manual/html/caret-u.gif b/legacy-resumes/resume-1/doc/manual/html/caret-u.gif deleted file mode 100644 index 79e6130..0000000 Binary files a/legacy-resumes/resume-1/doc/manual/html/caret-u.gif and /dev/null differ diff --git a/legacy-resumes/resume-1/doc/manual/html/cssref.html b/legacy-resumes/resume-1/doc/manual/html/cssref.html deleted file mode 100644 index f8cf89f..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/cssref.html +++ /dev/null @@ -1,112 +0,0 @@ - - - Chapter 3. CSS Class Reference

XMLRésuméLibrary: - User Guide

Previoussubjects.format UpPart II. Reference GlossaryNext

Chapter 3. CSS Class Reference

Overview

- 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. -

Overview

Table 3.1. Table of CSS Classes

ClassWhere 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é. -
Previoussubjects.format UpPart II. Reference GlossaryNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.academics.html b/legacy-resumes/resume-1/doc/manual/html/element.academics.html deleted file mode 100644 index c80c33b..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.academics.html +++ /dev/null @@ -1,34 +0,0 @@ - - - academics

XMLRésuméLibrary: - User Guide

PreviousElement Reference UpElement Reference achievementNext

Name

academics — Container for information about academic experience

Synopsis

Content Model

(degrees,note?)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The academics element contains - information about a person's academic experience. -

Parents

- academics may be contained in these - elements: - resume -

See Also

- pubs, memberships. -

Examples

<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>
PreviousElement Reference UpElement Reference achievementNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.achievement.html b/legacy-resumes/resume-1/doc/manual/html/element.achievement.html deleted file mode 100644 index f189028..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.achievement.html +++ /dev/null @@ -1,37 +0,0 @@ - - - achievement

XMLRésuméLibrary: - User Guide

Previousacademics UpElement Reference achievementsNext

Name

achievement — An accomplishment made at a job

Synopsis

Content Model

(#PCDATA|emphasis|citation|url|link)*

Attributes

NameTypeDefault
targetsCDATANone

Description

- The achievment element contains a - single accomplishment made while working at a particular job (e.g. - “increased sales by 20%”, or “improved employee - efficiency”). -

Parents

- achievement may be contained in these - elements: - achievements -

Examples

<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>
Previousacademics UpElement Reference achievementsNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.achievements.html b/legacy-resumes/resume-1/doc/manual/html/element.achievements.html deleted file mode 100644 index 7d27b81..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.achievements.html +++ /dev/null @@ -1,14 +0,0 @@ - - - achievements

XMLRésuméLibrary: - User Guide

Previousachievement UpElement Reference addressNext

Name

achievements — Container for one or more job achievements

Synopsis

Content Model

(achievement+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- achievements is a wrapper element - that contains one or more achievement elements. Achievements are - specific things that were accomplished at a job. -

Parents

- achievements may be contained in these - elements: - job -

Examples

- For examples, see achievement. -

Previousachievement UpElement Reference addressNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.address.html b/legacy-resumes/resume-1/doc/manual/html/element.address.html deleted file mode 100644 index b5691d0..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.address.html +++ /dev/null @@ -1,56 +0,0 @@ - - - address

XMLRésuméLibrary: - User Guide

Previousachievements UpElement Reference annotationNext

Name

address — A postal address

Synopsis

Content Model

(#PCDATA|street|street2|suburb|ward|city|state|province|county|prefecture|zip|postalCode|country|break)*

Attributes

NameTypeDefault
format

Enumeration:

standard
european
italian
None
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- address may be contained in these - elements: - header, referee -

Attributes

id

- A string used to uniquely identify an address. The address may - then be referred to by this identifier. -

format

- The address format. This attribute specifies the format of an - address, and overrides the global address.format - parameter for each address that it appears in. -

See Also

- address.format. -

Examples

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

Warning

- 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. -

Previousachievements UpElement Reference annotationNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.annotation.html b/legacy-resumes/resume-1/doc/manual/html/element.annotation.html deleted file mode 100644 index 46c2271..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.annotation.html +++ /dev/null @@ -1,26 +0,0 @@ - - - annotation

XMLRésuméLibrary: - User Guide

Previousaddress UpElement Reference artTitleNext

Name

annotation — Additional information about a degree

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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”). -

Parents

- annotation may be contained in these - elements: - degree -

Examples

<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>
Previousaddress UpElement Reference artTitleNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.artTitle.html b/legacy-resumes/resume-1/doc/manual/html/element.artTitle.html deleted file mode 100644 index 262a952..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.artTitle.html +++ /dev/null @@ -1,20 +0,0 @@ - - - artTitle

XMLRésuméLibrary: - User Guide

Previousannotation UpElement Reference authorNext

Name

artTitle — A title of an article or other work

Synopsis

Content Model

(#PCDATA|link)*

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- artTitle may be contained in these - elements: - pub -

See Also

- bookTitle. -

Examples

<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>
Previousannotation UpElement Reference authorNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.author.html b/legacy-resumes/resume-1/doc/manual/html/element.author.html deleted file mode 100644 index 000ee91..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.author.html +++ /dev/null @@ -1,36 +0,0 @@ - - - author

XMLRésuméLibrary: - User Guide

PreviousartTitle UpElement Reference awardNext

Name

author — An author of a publication

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
nameIDREFNone
targetsCDATANone

Description

- 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. -

Parents

- author may be contained in these - elements: - pub -

Attributes

name

- The name attribute contains - the id of a name element. -

- If an author element - specifies this attribute, it should not have any content. In - other words, there should be a single tag with a reference - (<author name="joe.smith"/>) - instead of two tags enclosing content - (<author>Joe Smith</author>). -

See Also

- name. -

Examples

<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>
PreviousartTitle UpElement Reference awardNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.award.html b/legacy-resumes/resume-1/doc/manual/html/element.award.html deleted file mode 100644 index ebd12b2..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.award.html +++ /dev/null @@ -1,24 +0,0 @@ - - - award

XMLRésuméLibrary: - User Guide

Previousauthor UpElement Reference awardsNext

Name

award — An award or other honor

Synopsis

Content Model

(title,organization?,(date|period)?,description?)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The award element describes - an award or other honor received by a person (e.g. “Nobel - Prize”, “MacArthur Fellow”). -

Parents

- award may be contained in these - elements: - awards -

Examples

<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>
Previousauthor UpElement Reference awardsNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.awards.html b/legacy-resumes/resume-1/doc/manual/html/element.awards.html deleted file mode 100644 index a0fa196..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.awards.html +++ /dev/null @@ -1,28 +0,0 @@ - - - awards

XMLRésuméLibrary: - User Guide

Previousaward UpElement Reference birthNext

Name

awards — Container for one or more awards

Synopsis

Content Model

(title?,award+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The awards element contains one or more - awards. -

Parents

- awards may be contained in these - elements: - resume -

Examples

<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>
Previousaward UpElement Reference birthNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.birth.html b/legacy-resumes/resume-1/doc/manual/html/element.birth.html deleted file mode 100644 index f5ec1b4..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.birth.html +++ /dev/null @@ -1,37 +0,0 @@ - - - birth

XMLRésuméLibrary: - User Guide

Previousawards UpElement Reference bookTitleNext

Name

birth — Container for information about a person's birth

Synopsis

Content Model

(date)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The birth element contains a single - date that specifies when a person was - born. -

Parents

- birth may be contained in these - elements: - header -

Examples

<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>
Previousawards UpElement Reference bookTitleNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.bookTitle.html b/legacy-resumes/resume-1/doc/manual/html/element.bookTitle.html deleted file mode 100644 index 92c8c85..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.bookTitle.html +++ /dev/null @@ -1,28 +0,0 @@ - - - bookTitle

XMLRésuméLibrary: - User Guide

Previousbirth UpElement Reference breakNext

Name

bookTitle — A title of a book or similar work

Synopsis

Content Model

(#PCDATA|link)*

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- bookTitle may be contained in these - elements: - pub -

See Also

- artTitle. -

Examples

<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>
Previousbirth UpElement Reference breakNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.break.html b/legacy-resumes/resume-1/doc/manual/html/element.break.html deleted file mode 100644 index 0240764..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.break.html +++ /dev/null @@ -1,21 +0,0 @@ - - - break

XMLRésuméLibrary: - User Guide

PreviousbookTitle UpElement Reference citationNext

Name

break — A linebreak

Deprecated

Synopsis

Content Model

EMPTY

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

Parents

- break may be contained in these - elements: - address -

Examples

- None. -

PreviousbookTitle UpElement Reference citationNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.citation.html b/legacy-resumes/resume-1/doc/manual/html/element.citation.html deleted file mode 100644 index fe9ef84..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.citation.html +++ /dev/null @@ -1,19 +0,0 @@ - - - citation

XMLRésuméLibrary: - User Guide

Previousbreak UpElement Reference cityNext

Name

citation — The name of a work being referenced

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The citation element marks the title - of a book, website, course, or other work. -

Parents

- citation may be contained in these - elements: - achievement, employer, institution, organization, para, project, skill -

See Also

- pub. -

Examples

<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>
Previousbreak UpElement Reference cityNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.city.html b/legacy-resumes/resume-1/doc/manual/html/element.city.html deleted file mode 100644 index 05c60a4..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.city.html +++ /dev/null @@ -1,21 +0,0 @@ - - - city

XMLRésuméLibrary: - User Guide

Previouscitation UpElement Reference clearanceNext

Name

city — The name of a city

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The city element contains a the name - of a single city or other similar municipality. -

Parents

- city may be contained in these - elements: - address, location -

Attributes

id

- A string used to uniquely identify a city. The city may - then be referred to by this identifier. -

See Also

- county, prefecture, suburb, ward. -

Examples

<address>
-  <street>3400 N. 5230 S.</street>
-  <city>Salt Lake City</city>
-  <state>UT</state>
-  <zip>84352</zip>
-</address>
Previouscitation UpElement Reference clearanceNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.clearance.html b/legacy-resumes/resume-1/doc/manual/html/element.clearance.html deleted file mode 100644 index 3a3ac44..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.clearance.html +++ /dev/null @@ -1,19 +0,0 @@ - - - clearance

XMLRésuméLibrary: - User Guide

Previouscity UpElement Reference clearancesNext

Name

clearance — A security clearance

Synopsis

Content Model

(level,organization?,(date|period)?,note?)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The clearance element contains a single - security clearance (e.g. “Top Secret”). -

Parents

- clearance may be contained in these - elements: - clearances -

Examples

<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>
Previouscity UpElement Reference clearancesNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.clearances.html b/legacy-resumes/resume-1/doc/manual/html/element.clearances.html deleted file mode 100644 index c0711ce..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.clearances.html +++ /dev/null @@ -1,20 +0,0 @@ - - - clearances

XMLRésuméLibrary: - User Guide

Previousclearance UpElement Reference companyNext

Name

clearances — One or more security clearances

Synopsis

Content Model

(title?,clearance+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The clearances element contains one or - more security clearances. It is a top-level section of a résumé. -

Parents

- clearances may be contained in these - elements: - resume -

Examples

<clearances>
-  <clearance>
-    <level>Top Secret</level>
-    <organization>NSA</organization>
-  </clearance>
-  <clearance>
-    <level>Secret</level>
-    <organization>US Navy</organization>
-  </clearance>
-</clearances>
Previousclearance UpElement Reference companyNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.company.html b/legacy-resumes/resume-1/doc/manual/html/element.company.html deleted file mode 100644 index 3679511..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.company.html +++ /dev/null @@ -1,13 +0,0 @@ - - - company

XMLRésuméLibrary: - User Guide

Previousclearances UpElement Reference contactNext

Name

company — The name of a company

Deprecated

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- This element is deprecated as of XML Résumé Library version 1.3.3. It should - not be used. -

Parents

- company may be contained in these - elements: - None -

See Also

- institution, organization. -

Examples

None.

Previousclearances UpElement Reference contactNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.contact.html b/legacy-resumes/resume-1/doc/manual/html/element.contact.html deleted file mode 100644 index b187ed9..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.contact.html +++ /dev/null @@ -1,23 +0,0 @@ - - - contact

XMLRésuméLibrary: - User Guide

Previouscompany UpElement Reference copyrightNext

Name

contact — Container for one or more methods of contacting someone

Synopsis

Content Model

(phone|fax|pager|email|url|instantMessage)*

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- contact may be contained in these - elements: - header, referee -

See Also

- address. -

Examples

<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>
Previouscompany UpElement Reference copyrightNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.copyright.html b/legacy-resumes/resume-1/doc/manual/html/element.copyright.html deleted file mode 100644 index 18b379b..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.copyright.html +++ /dev/null @@ -1,28 +0,0 @@ - - - copyright

XMLRésuméLibrary: - User Guide

Previouscontact UpElement Reference countryNext

Name

copyright — A copyright notice

Synopsis

Content Model

(year,name?,legalnotice?)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- copyright may be contained in these - elements: - resume -

Examples

<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>
Previouscontact UpElement Reference countryNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.country.html b/legacy-resumes/resume-1/doc/manual/html/element.country.html deleted file mode 100644 index 4fd1354..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.country.html +++ /dev/null @@ -1,24 +0,0 @@ - - - country

XMLRésuméLibrary: - User Guide

Previouscopyright UpElement Reference countyNext

Name

country — A country name

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The country element marks the name of - a country. -

Parents

- country may be contained in these - elements: - address, location -

Attributes

id

- A string used to uniquely identify a country. The country may - then be referred to by this identifier. -

Examples

<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>
Previouscopyright UpElement Reference countyNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.county.html b/legacy-resumes/resume-1/doc/manual/html/element.county.html deleted file mode 100644 index 1b7677b..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.county.html +++ /dev/null @@ -1,29 +0,0 @@ - - - county

XMLRésuméLibrary: - User Guide

Previouscountry UpElement Reference dateNext

Name

county — A county name

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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.) -

Parents

- county may be contained in these - elements: - address, location -

Attributes

id

- A string used to uniquely identify a county. The county may - then be referred to by this identifier. -

See Also

- state, province, prefecture. -

Examples

<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>
Previouscountry UpElement Reference dateNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.date.html b/legacy-resumes/resume-1/doc/manual/html/element.date.html deleted file mode 100644 index ba23b99..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.date.html +++ /dev/null @@ -1,32 +0,0 @@ - - - date

XMLRésuméLibrary: - User Guide

Previouscounty UpElement Reference dayOfMonthNext

Name

date — A specific instant in time

Synopsis

Content Model

(((dayOfMonth)?,month)?,year)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Note

- 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. -

Parents

- date may be contained in these - elements: - award, birth, clearance, degree, from, job, lastModified, membership, pub, to -

See Also

- period. -

Examples

<date>
-  <dayOfMonth>27</dayOfMonth>
-  <month>November</month>
-  <year>1634</year>
-</date>
<date>
-  <month>July</month>
-  <year>1457</year>
-</date>
Previouscounty UpElement Reference dayOfMonthNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.dayOfMonth.html b/legacy-resumes/resume-1/doc/manual/html/element.dayOfMonth.html deleted file mode 100644 index ce3c8d3..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.dayOfMonth.html +++ /dev/null @@ -1,14 +0,0 @@ - - - dayOfMonth

XMLRésuméLibrary: - User Guide

Previousdate UpElement Reference degreeNext

Name

dayOfMonth — An ordinal day of the month

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- Represents a specific day in a month. Its value is numeric; the first - day of the month is written 1, the fifteenth - 15, etc. -

Parents

- dayOfMonth may be contained in these - elements: - date -

Examples

- For examples, see date. -

Previousdate UpElement Reference degreeNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.degree.html b/legacy-resumes/resume-1/doc/manual/html/element.degree.html deleted file mode 100644 index bb58f8b..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.degree.html +++ /dev/null @@ -1,50 +0,0 @@ - - - degree

XMLRésuméLibrary: - User Guide

PreviousdayOfMonth UpElement Reference degreesNext

Name

degree — Container for information about a degree or similar certification

Synopsis

Content Model

(level,annotation?,major*,minor*,(date|period)?,(institution,location?)?,gpa?,subjects?,projects?)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The degree element is a container for - information about an academic degree (Bachelor of Science, Doctor of - Psychology, etc.) or other similar certification. -

Parents

- degree may be contained in these - elements: - degrees -

Attributes

id

- A string used to uniquely identify a degree. The degree may - then be referred to by this identifier. -

Examples

<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>
PreviousdayOfMonth UpElement Reference degreesNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.degrees.html b/legacy-resumes/resume-1/doc/manual/html/element.degrees.html deleted file mode 100644 index 0e23536..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.degrees.html +++ /dev/null @@ -1,20 +0,0 @@ - - - degrees

XMLRésuméLibrary: - User Guide

Previousdegree UpElement Reference descriptionNext

Name

degrees — Container for one or more degrees

Synopsis

Content Model

(degree+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The degrees element is a container - for at least one degree. -

Parents

- degrees may be contained in these - elements: - academics -

Examples

<degrees>
-  <degree>
-    <level>BA</level>
-    <major>Interstellar Basket Weaving</major>
-  </degree>
-  <degree>
-    <level>Ph.D</level>
-    <major>Aquatic Tennis Teaching</major>
-  </degree>
-</degree>
Previousdegree UpElement Reference descriptionNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.description.html b/legacy-resumes/resume-1/doc/manual/html/element.description.html deleted file mode 100644 index 0535ccc..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.description.html +++ /dev/null @@ -1,30 +0,0 @@ - - - description

XMLRésuméLibrary: - User Guide

Previousdegrees UpElement Reference docpathNext

Name

description — An explanation of something

Synopsis

Content Model

(para+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The description element specifies a - person's role, their activities, or other descriptive information. -

Parents

- description may be contained in these - elements: - award, interest, job, membership -

See Also

- projects, achievements. -

Examples

<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>
Previousdegrees UpElement Reference docpathNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.docpath.html b/legacy-resumes/resume-1/doc/manual/html/element.docpath.html deleted file mode 100644 index b8905cb..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.docpath.html +++ /dev/null @@ -1,13 +0,0 @@ - - - docpath

XMLRésuméLibrary: - User Guide

Previousdescription UpElement Reference emailNext

Name

docpath —

Deprecated

Synopsis

Content Model

(head?,node*,tail)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

- -

Parents

- docpath may be contained in these - elements: - resume -

Examples

<!-- TODO -->
Previousdescription UpElement Reference emailNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.email.html b/legacy-resumes/resume-1/doc/manual/html/element.email.html deleted file mode 100644 index dcb9d17..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.email.html +++ /dev/null @@ -1,16 +0,0 @@ - - - email

XMLRésuméLibrary: - User Guide

Previousdocpath UpElement Reference emphasisNext

Name

email — An e-mail address

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The email element specifies a single - e-mail address. -

Parents

- email may be contained in these - elements: - contact -

See Also

- fax, instantMessage, pager, url. -

Examples

<contact>
-  <email>john@johnny.bob</email>
-  <phone>555-555-1212</phone>
-</contact>
Previousdocpath UpElement Reference emphasisNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.emphasis.html b/legacy-resumes/resume-1/doc/manual/html/element.emphasis.html deleted file mode 100644 index 9c849a4..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.emphasis.html +++ /dev/null @@ -1,31 +0,0 @@ - - - emphasis

XMLRésuméLibrary: - User Guide

Previousemail UpElement Reference employerNext

Name

emphasis — An emphasized block of text

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The emphasis element is an inline - element that indicates that the text it contains should be emphasized. -

Presentation

- The presentation of text contained in this element varies depending on - the output format. -

HTML

- 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

- 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. -

XSL-FO/PDF

- Rendered as bold text. -

Parents

- emphasis may be contained in these - elements: - achievement, employer, institution, organization, para, project, skill -

Examples

<para>
-  I really, really, <emphasis>really</emphasis> want a job.
-</para>
<skill>
-  I am <emphasis>extremely</emphasis> at using rocket-powered cheese graters.
-</skill>
Previousemail UpElement Reference employerNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.employer.html b/legacy-resumes/resume-1/doc/manual/html/element.employer.html deleted file mode 100644 index 2f019f6..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.employer.html +++ /dev/null @@ -1,38 +0,0 @@ - - - employer

XMLRésuméLibrary: - User Guide

Previousemphasis UpElement Reference faxNext

Name

employer — A name of an employer

Synopsis

Content Model

(#PCDATA|emphasis|citation|url|link)*

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The employer element specifies the - name of a person, company, or other entity for whom a person works or - has worked. -

Parents

- employer may be contained in these - elements: - job -

Attributes

id

- A string used to uniquely identify an employer. The employer may - then be referred to by this identifier. -

See Also

- institution, organization. -

Examples

<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>
Previousemphasis UpElement Reference faxNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.fax.html b/legacy-resumes/resume-1/doc/manual/html/element.fax.html deleted file mode 100644 index 1d0a4c5..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.fax.html +++ /dev/null @@ -1,18 +0,0 @@ - - - fax

XMLRésuméLibrary: - User Guide

Previousemployer UpElement Reference firstnameNext

Name

fax — A fax telephone number

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
location

Enumeration:

home
work
None
targetsCDATANone

Description

- 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.) -

Parents

- fax may be contained in these - elements: - contact -

Attributes

location

- Indicates the location that the phone number connects to. This - attribute is optional. -

See Also

- email, pager, phone. -

Examples

<fax>555-555-1212</fax>
<fax location="work">(123) 456-7890</fax>
<fax location="home">345.324.2721</fax>
Previousemployer UpElement Reference firstnameNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.firstname.html b/legacy-resumes/resume-1/doc/manual/html/element.firstname.html deleted file mode 100644 index 5ef7d4f..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.firstname.html +++ /dev/null @@ -1,17 +0,0 @@ - - - firstname

XMLRésuméLibrary: - User Guide

Previousfax UpElement Reference fromNext

Name

firstname — A person's given name

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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”. -

Parents

- firstname may be contained in these - elements: - name -

See Also

- middlenames, surname. -

Examples

<name>
-  <firstname>Caroline</firstname>
-  <surname>Francisca</surname>
-</name>
Previousfax UpElement Reference fromNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.from.html b/legacy-resumes/resume-1/doc/manual/html/element.from.html deleted file mode 100644 index 881a5bd..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.from.html +++ /dev/null @@ -1,29 +0,0 @@ - - - from

XMLRésuméLibrary: - User Guide

Previousfirstname UpElement Reference gpaNext

Name

from — The beginning point in a period of time

Synopsis

Content Model

(date|present)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- from may be contained in these - elements: - period -

See Also

- to. -

Examples

<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>
Previousfirstname UpElement Reference gpaNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.gpa.html b/legacy-resumes/resume-1/doc/manual/html/element.gpa.html deleted file mode 100644 index 10a7273..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.gpa.html +++ /dev/null @@ -1,24 +0,0 @@ - - - gpa

XMLRésuméLibrary: - User Guide

Previousfrom UpElement Reference headNext

Name

gpa — Information about a grade point average

Synopsis

Content Model

(score,possible?,note?)

Attributes

NameTypeDefault
targetsCDATANone
type

Enumeration:

overall
major
overall

Description

- 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.). -

Parents

- gpa may be contained in these - elements: - degree -

Attributes

type

- 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. -

Examples

<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>
Previousfrom UpElement Reference headNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.head.html b/legacy-resumes/resume-1/doc/manual/html/element.head.html deleted file mode 100644 index f435521..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.head.html +++ /dev/null @@ -1,13 +0,0 @@ - - - head

XMLRésuméLibrary: - User Guide

Previousgpa UpElement Reference headerNext

Name

head —

Deprecated

Synopsis

Content Model

(label,uri)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

- -

Parents

- head may be contained in these - elements: - docpath -

Examples

<!-- TODO -->
Previousgpa UpElement Reference headerNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.header.html b/legacy-resumes/resume-1/doc/manual/html/element.header.html deleted file mode 100644 index 53489fc..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.header.html +++ /dev/null @@ -1,40 +0,0 @@ - - - header

XMLRésuméLibrary: - User Guide

Previoushead UpElement Reference historyNext

Name

header — Container for information about the person being described in a résumé

Synopsis

Content Model

(name,address?,birth?,contact?)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Formatting

- The header.format - parameter influences the formatting of headers in all output formats. -

Parents

- header may be contained in these - elements: - resume -

See Also

- header.format. -

Examples

<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>
Previoushead UpElement Reference historyNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.history.html b/legacy-resumes/resume-1/doc/manual/html/element.history.html deleted file mode 100644 index aeccbf6..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.history.html +++ /dev/null @@ -1,61 +0,0 @@ - - - history

XMLRésuméLibrary: - User Guide

Previousheader UpElement Reference instantMessageNext

Name

history — Container for a person's previous (and possibly current) jobs

Synopsis

Content Model

(job+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- history may be contained in these - elements: - resume -

Examples

<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>
Previousheader UpElement Reference instantMessageNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.instantMessage.html b/legacy-resumes/resume-1/doc/manual/html/element.instantMessage.html deleted file mode 100644 index 050a0c8..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.instantMessage.html +++ /dev/null @@ -1,18 +0,0 @@ - - - instantMessage

XMLRésuméLibrary: - User Guide

Previoushistory UpElement Reference institutionNext

Name

instantMessage — An instant message username or address

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
serviceCDATANone
targetsCDATANone

Description

- 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. -

Parents

- instantMessage may be contained in these - elements: - contact -

Attributes

service

- Specifies the service that the username or address is to be used - with. Acceptable values are: -

aim

AOL Instant Messenger

icq

ICQ

irc

Internet Relay Chat

jabber

Jabber

msn

MSN Messenger

yahoo

Yahoo! Messenger

-

See Also

- email. -

Examples

<instantMessage service="yahoo">joesmith</instantMessage>
<instantMessage service="aim">janedoe</instantMessage>
<instantMessage service="jabber">sammybob@jabber.com</instantMessage>
Previoushistory UpElement Reference institutionNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.institution.html b/legacy-resumes/resume-1/doc/manual/html/element.institution.html deleted file mode 100644 index 54c7e5a..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.institution.html +++ /dev/null @@ -1,21 +0,0 @@ - - - institution

XMLRésuméLibrary: - User Guide

PreviousinstantMessage UpElement Reference interestNext

Name

institution — A name of an academic institution

Synopsis

Content Model

(#PCDATA|emphasis|citation|url|link)*

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The institution element specifies the - name of a degree-awarding institution, such as a university, college, or - trade school. -

Parents

- institution may be contained in these - elements: - degree -

Attributes

id

- A string used to uniquely identify an institution. The - institution may then be referred to by this identifier. -

See Also

- organization. -

Examples

<degree>
-  <level>BA</level>
-  <major>Daisy Chain Manufacturing</major>
-  <institution>Harvard</institution>
-</degree>
PreviousinstantMessage UpElement Reference interestNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.interest.html b/legacy-resumes/resume-1/doc/manual/html/element.interest.html deleted file mode 100644 index c977662..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.interest.html +++ /dev/null @@ -1,31 +0,0 @@ - - - interest

XMLRésuméLibrary: - User Guide

Previousinstitution UpElement Reference interestsNext

Name

interest — Something a person is interested in

Synopsis

Content Model

(title,description?)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The interest element describes - something that a person is interested in. A common use for interest elements is to list hobbies. -

Formatting

- 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. -

Parents

- interest may be contained in these - elements: - interests -

See Also

- skill. -

Examples

<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. -

Previousinstitution UpElement Reference interestsNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.interests.html b/legacy-resumes/resume-1/doc/manual/html/element.interests.html deleted file mode 100644 index 312aa40..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.interests.html +++ /dev/null @@ -1,46 +0,0 @@ - - - interests

XMLRésuméLibrary: - User Guide

Previousinterest UpElement Reference jobNext

Name

interests — Container for one or more interests

Synopsis

Content Model

(title?,interest+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The interests element contains one or - more interest elements. -

Formatting

- 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. -

Parents

- interests may be contained in these - elements: - resume -

See Also

- skillarea. -

Examples

<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>
Previousinterest UpElement Reference jobNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.job.html b/legacy-resumes/resume-1/doc/manual/html/element.job.html deleted file mode 100644 index 58172bd..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.job.html +++ /dev/null @@ -1,51 +0,0 @@ - - - job

XMLRésuméLibrary: - User Guide

Previousinterests UpElement Reference jobtitleNext

Name

job — A specific employment engagement

Synopsis

Content Model

(jobtitle,employer,location?,(date|period),description?,projects?,achievements?)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The job element describes a job, - contract, or other employment engagement. -

Parents

- job may be contained in these - elements: - history -

Attributes

id

- A string used to uniquely identify a job. The job may then be - referred to by this identifier. -

Examples

<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>
Previousinterests UpElement Reference jobtitleNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.jobtitle.html b/legacy-resumes/resume-1/doc/manual/html/element.jobtitle.html deleted file mode 100644 index e2a0d48..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.jobtitle.html +++ /dev/null @@ -1,13 +0,0 @@ - - - jobtitle

XMLRésuméLibrary: - User Guide

Previousjob UpElement Reference keywordNext

Name

jobtitle — A job title

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The jobtitle element specifies the - offical title or name of the position a person held at a job. -

Parents

- jobtitle may be contained in these - elements: - job -

Examples

- For examples, see job -

Previousjob UpElement Reference keywordNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.keyword.html b/legacy-resumes/resume-1/doc/manual/html/element.keyword.html deleted file mode 100644 index 3bb523b..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.keyword.html +++ /dev/null @@ -1,21 +0,0 @@ - - - keyword

XMLRésuméLibrary: - User Guide

Previousjobtitle UpElement Reference keywordsNext

Name

keyword — A keyword to be used for résumé indexing and searching

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- keyword may be contained in these - elements: - keywords -

Examples

<keywords>
-  <keyword>forward-thinking</keyword>
-  <keyword>self-starter</keyword>
-  <keyword>independent</keyword>
-  <keyword>flexible</keyword>
-</keywords>
Previousjobtitle UpElement Reference keywordsNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.keywords.html b/legacy-resumes/resume-1/doc/manual/html/element.keywords.html deleted file mode 100644 index d01a586..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.keywords.html +++ /dev/null @@ -1,15 +0,0 @@ - - - keywords

XMLRésuméLibrary: - User Guide

Previouskeyword UpElement Reference labelNext

Name

keywords — Container for a list of keywords

Synopsis

Content Model

(keyword+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The keywords element contains one or - more keywords. These keywords are included in the HTML presentation as - <meta name="keywords" content="..."> - tags. -

Parents

- keywords may be contained in these - elements: - resume -

Examples

- For examples, see keyword. -

Previouskeyword UpElement Reference labelNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.label.html b/legacy-resumes/resume-1/doc/manual/html/element.label.html deleted file mode 100644 index 7e4c507..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.label.html +++ /dev/null @@ -1,13 +0,0 @@ - - - label

XMLRésuméLibrary: - User Guide

Previouskeywords UpElement Reference lastModifiedNext

Name

label —

Deprecated

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

- -

Parents

- label may be contained in these - elements: - head, node -

Examples

<!-- TODO -->
Previouskeywords UpElement Reference lastModifiedNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.lastModified.html b/legacy-resumes/resume-1/doc/manual/html/element.lastModified.html deleted file mode 100644 index d90d9b6..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.lastModified.html +++ /dev/null @@ -1,17 +0,0 @@ - - - lastModified

XMLRésuméLibrary: - User Guide

Previouslabel UpElement Reference legalnoticeNext

Name

lastModified — Information about when a résumé was last modified

Synopsis

Content Model

(date)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The lastModified element contains the - date that a résumé was last updated. -

Parents

- lastModified may be contained in these - elements: - resume -

Examples

<lastModified>
-  <date>
-    <dayOfMonth>4</dayOfMonth>
-    <month>July</month>
-    <year>1796</year>
-  </date>
-</lastModified>
Previouslabel UpElement Reference legalnoticeNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.legalnotice.html b/legacy-resumes/resume-1/doc/manual/html/element.legalnotice.html deleted file mode 100644 index a0de112..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.legalnotice.html +++ /dev/null @@ -1,13 +0,0 @@ - - - legalnotice

XMLRésuméLibrary: - User Guide

PreviouslastModified UpElement Reference levelNext

Name

legalnotice — A legal statement

Synopsis

Content Model

(para+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The legalnotice element contains text - that is intended to specify the legal use of a résumé. -

Parents

- legalnotice may be contained in these - elements: - copyright -

Examples

- For examples, see copyright -

PreviouslastModified UpElement Reference levelNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.level.html b/legacy-resumes/resume-1/doc/manual/html/element.level.html deleted file mode 100644 index b5ebfc1..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.level.html +++ /dev/null @@ -1,25 +0,0 @@ - - - level

XMLRésuméLibrary: - User Guide

Previouslegalnotice UpElement Reference linkNext

Name

level — A degree type

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The semantic of the title element - vary depending on which element contains it: - -

clearance

- When contained in this element, the level element specifies the level of - security clearance that a person has been granted, such as - “Top Secret” or “Restricted”. -

degree

- When contained in this element, the level element specifies a degree type, - such as “BFA” (bachelor of fine arts) or - “Ph.D” (doctor of philosophy). It typically contains - the abbreviation (“BS”) not the full spelling - (“bachelor of science”). -

-

Parents

- level may be contained in these - elements: - clearance, degree -

Examples

- For examples, see clearance and degree. -

Previouslegalnotice UpElement Reference linkNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.link.html b/legacy-resumes/resume-1/doc/manual/html/element.link.html deleted file mode 100644 index 26d0cef..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.link.html +++ /dev/null @@ -1,34 +0,0 @@ - - - link

XMLRésuméLibrary: - User Guide

Previouslevel UpElement Reference locationNext

Name

link — A titled hyperlink

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
hrefCDATANone
targetsCDATANone

Description

- The link element defines a single - hyperlink, much like HTML's a (anchor) - element. - -

Formatting

- 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. -

Parents

- link may be contained in these - elements: - achievement, artTitle, bookTitle, employer, institution, organization, para, project, publisher, skill -

Attributes

href

- The URL that the link should point to. - then be referred to by this identifier. -

See Also

- uri, url. -

Examples

<employer>
-  <link href="http://www.acme.bob/">Acme Corporation</link>
-</employer>
<para>
-  The <link href="http://xmlresume.sf.net/">XML R&eacute;sum&eacute;
-  Project</link> supplies tools that easily convert a single XML
-  r&eacute;sum&eacute; to multiple output formats.
-</employer>
Previouslevel UpElement Reference locationNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.location.html b/legacy-resumes/resume-1/doc/manual/html/element.location.html deleted file mode 100644 index edb83ea..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.location.html +++ /dev/null @@ -1,22 +0,0 @@ - - - location

XMLRésuméLibrary: - User Guide

Previouslink UpElement Reference majorNext

Name

location — A location, with city-level granularity

Synopsis

Content Model

(city?,(state|province|county)?,country?)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The location element specifies a - level location, such as “London, England”, “Seattle, - Washington”, “St. Louis, Missouri, USA”, or - “Newfoundland, Canada”. -

Parents

- location may be contained in these - elements: - degree, job, membership -

See Also

- address. -

Examples

<location>
-  <city>Los Angeles<city>
-  <state>California</state>
-  <country>USA</country>
-</location>
<location>
-  <city>Paris<city>
-  <country>France</country>
-</location>
Previouslink UpElement Reference majorNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.major.html b/legacy-resumes/resume-1/doc/manual/html/element.major.html deleted file mode 100644 index de925d9..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.major.html +++ /dev/null @@ -1,16 +0,0 @@ - - - major

XMLRésuméLibrary: - User Guide

Previouslocation UpElement Reference membershipNext

Name

major — A main course of study

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- major may be contained in these - elements: - degree -

See Also

- minor. -

Examples

- For examples, see degree. -

Previouslocation UpElement Reference membershipNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.membership.html b/legacy-resumes/resume-1/doc/manual/html/element.membership.html deleted file mode 100644 index c80190f..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.membership.html +++ /dev/null @@ -1,16 +0,0 @@ - - - membership

XMLRésuméLibrary: - User Guide

Previousmajor UpElement Reference membershipsNext

Name

membership — A professional membership

Synopsis

Content Model

(title?,(organization,location?)?,(date|period)?,description?)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The membership element contains - information about a person's membership in a professional organization. -

Parents

- membership may be contained in these - elements: - memberships -

Attributes

id

- A string used to uniquely identify a membership. The membership - may then be referred to by this identifier. -

Examples

- For examples, see memberships. -

Previousmajor UpElement Reference membershipsNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.memberships.html b/legacy-resumes/resume-1/doc/manual/html/element.memberships.html deleted file mode 100644 index 0e70a84..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.memberships.html +++ /dev/null @@ -1,32 +0,0 @@ - - - memberships

XMLRésuméLibrary: - User Guide

Previousmembership UpElement Reference middlenamesNext

Name

memberships — Container for one or more memberships

Synopsis

Content Model

(title,membership+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The memberships element contains one - or more memberships. -

Parents

- memberships may be contained in these - elements: - resume -

Examples

<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>
Previousmembership UpElement Reference middlenamesNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.middlenames.html b/legacy-resumes/resume-1/doc/manual/html/element.middlenames.html deleted file mode 100644 index 6896890..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.middlenames.html +++ /dev/null @@ -1,14 +0,0 @@ - - - middlenames

XMLRésuméLibrary: - User Guide

Previousmemberships UpElement Reference minorNext

Name

middlenames — One or more “middle” names of a person

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- middlenames may be contained in these - elements: - name -

See Also

- firstname, surname. -

Examples

<middlenames>Samione</middlenames>
<middlenames>Lu&iacute;s Garcia M&aacute;rquez</middlenames>
Previousmemberships UpElement Reference minorNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.minor.html b/legacy-resumes/resume-1/doc/manual/html/element.minor.html deleted file mode 100644 index b99086c..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.minor.html +++ /dev/null @@ -1,16 +0,0 @@ - - - minor

XMLRésuméLibrary: - User Guide

Previousmiddlenames UpElement Reference miscNext

Name

minor — A minor course of study

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- minor may be contained in these - elements: - degree -

See Also

- major. -

Examples

- For examples, see degree. -

Previousmiddlenames UpElement Reference miscNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.misc.html b/legacy-resumes/resume-1/doc/manual/html/element.misc.html deleted file mode 100644 index f433f4a..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.misc.html +++ /dev/null @@ -1,22 +0,0 @@ - - - misc

XMLRésuméLibrary: - User Guide

Previousminor UpElement Reference monthNext

Name

misc — Miscellaneous remarks

Synopsis

Content Model

(para+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The misc element contains paragraphs - of text that don't fit into any other top-level categories. -

Parents

- misc may be contained in these - elements: - resume -

Examples

<misc>
-  <para>What can't be captured on a r&eacute;sum&eacute; 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&ograve;n</citation>.
-  </para>
-</misc>
Previousminor UpElement Reference monthNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.month.html b/legacy-resumes/resume-1/doc/manual/html/element.month.html deleted file mode 100644 index dc8dbe3..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.month.html +++ /dev/null @@ -1,14 +0,0 @@ - - - month

XMLRésuméLibrary: - User Guide

Previousmisc UpElement Reference nameNext

Name

month — A month name

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The month element contains the name - of a month, such as “March” (English), “marzo” - (Spanish), or “mars” (French). -

Parents

- month may be contained in these - elements: - date, pubDate -

See Also

- dayOfMonth, year. -

Examples

<month>April</month>
Previousmisc UpElement Reference nameNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.name.html b/legacy-resumes/resume-1/doc/manual/html/element.name.html deleted file mode 100644 index 63144e9..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.name.html +++ /dev/null @@ -1,28 +0,0 @@ - - - name

XMLRésuméLibrary: - User Guide

Previousmonth UpElement Reference nodeNext

Name

name — A person's name

Synopsis

Content Model

(title?,firstname,middlenames?,surname,suffix?)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The name element contains a person's - name. -

Parents

- name may be contained in these - elements: - copyright, header, referee -

Attributes

id

- A string used to uniquely identify a name. The name may then be - referred to by this identifier. -

Examples

<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>
Previousmonth UpElement Reference nodeNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.node.html b/legacy-resumes/resume-1/doc/manual/html/element.node.html deleted file mode 100644 index c692112..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.node.html +++ /dev/null @@ -1,13 +0,0 @@ - - - node

XMLRésuméLibrary: - User Guide

Previousname UpElement Reference noteNext

Name

node —

Deprecated

Synopsis

Content Model

(label,uri)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

- -

Parents

- node may be contained in these - elements: - docpath -

Examples

<!-- TODO -->
Previousname UpElement Reference noteNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.note.html b/legacy-resumes/resume-1/doc/manual/html/element.note.html deleted file mode 100644 index ac45a1a..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.note.html +++ /dev/null @@ -1,22 +0,0 @@ - - - note

XMLRésuméLibrary: - User Guide

Previousnode UpElement Reference objectiveNext

Name

note — Additional information

Synopsis

Content Model

(para+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The note element contains additional - information about its parent element. -

Parents

- note may be contained in these - elements: - academics, clearance, gpa -

See Also

- annotation, legalnotice. -

Examples

<academics>
-  <degrees>
-    ...
-  </degrees>
-  <note>
-    <para>
-      I take education very seriously. After all, I'm in 37th grade now!
-    </para>
-  </note>
-</academics>
Previousnode UpElement Reference objectiveNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.objective.html b/legacy-resumes/resume-1/doc/manual/html/element.objective.html deleted file mode 100644 index 13e0060..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.objective.html +++ /dev/null @@ -1,20 +0,0 @@ - - - objective

XMLRésuméLibrary: - User Guide

Previousnote UpElement Reference organizationNext

Name

objective — A person's employment goal

Synopsis

Content Model

(para+)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- objective may be contained in these - elements: - resume -

Attributes

id

- A string used to uniquely identify an objective. The objective - may then be referred to by this identifier. -

Examples

<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>
Previousnote UpElement Reference organizationNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.organization.html b/legacy-resumes/resume-1/doc/manual/html/element.organization.html deleted file mode 100644 index 6f73ac9..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.organization.html +++ /dev/null @@ -1,21 +0,0 @@ - - - organization

XMLRésuméLibrary: - User Guide

Previousobjective UpElement Reference pageNumsNext

Name

organization — A name of an organization

Synopsis

Content Model

(#PCDATA|emphasis|citation|url|link)*

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The organization element contains the - name of a professional or other type of organization. -

Parents

- organization may be contained in these - elements: - award, clearance, membership, referee -

Attributes

id

- A string used to uniquely identify an organization. The - organization may then be referred to by this identifier. -

See Also

- institution. -

- --> - -

Examples

<membership>
-  <organization>Croquet Players' Association of the UK</organization>
-</membership>
Previousobjective UpElement Reference pageNumsNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.pageNums.html b/legacy-resumes/resume-1/doc/manual/html/element.pageNums.html deleted file mode 100644 index 43281bb..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.pageNums.html +++ /dev/null @@ -1,20 +0,0 @@ - - - pageNums

XMLRésuméLibrary: - User Guide

Previousorganization UpElement Reference pagerNext

Name

pageNums — One or more page numbers or ranges

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The pageNums element specifies one - or more page numbers or ranges of page numbers, and is used in citing a - publication. -

Parents

- pageNums may be contained in these - elements: - pub -

Examples

<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>
Previousorganization UpElement Reference pagerNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.pager.html b/legacy-resumes/resume-1/doc/manual/html/element.pager.html deleted file mode 100644 index 4bb6c2a..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.pager.html +++ /dev/null @@ -1,15 +0,0 @@ - - - pager

XMLRésuméLibrary: - User Guide

PreviouspageNums UpElement Reference paraNext

Name

pager — A pager telephone number

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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.) -

Parents

- pager may be contained in these - elements: - contact -

See Also

- email, fax, phone. -

Examples

<pager>456-145-4468</pager>
<pager>736.272.4673 x 235</pager>
PreviouspageNums UpElement Reference paraNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.para.html b/legacy-resumes/resume-1/doc/manual/html/element.para.html deleted file mode 100644 index 840d73f..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.para.html +++ /dev/null @@ -1,25 +0,0 @@ - - - para

XMLRésuméLibrary: - User Guide

Previouspager UpElement Reference periodNext

Name

para — A paragraph of text

Synopsis

Content Model

(#PCDATA|emphasis|citation|url|link)*

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- para may be contained in these - elements: - description, legalnotice, misc, note, objective, pub -

Examples

<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>
Previouspager UpElement Reference periodNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.period.html b/legacy-resumes/resume-1/doc/manual/html/element.period.html deleted file mode 100644 index ebb5dd3..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.period.html +++ /dev/null @@ -1,35 +0,0 @@ - - - period

XMLRésuméLibrary: - User Guide

Previouspara UpElement Reference phoneNext

Name

period — A period of time

Synopsis

Content Model

(from,to)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- period may be contained in these - elements: - award, clearance, degree, job, membership -

See Also

- element. -

Examples

<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>
Previouspara UpElement Reference phoneNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.phone.html b/legacy-resumes/resume-1/doc/manual/html/element.phone.html deleted file mode 100644 index fac79ea..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.phone.html +++ /dev/null @@ -1,34 +0,0 @@ - - - phone

XMLRésuméLibrary: - User Guide

Previousperiod UpElement Reference possibleNext

Name

phone — A voice telephone number

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
location

Enumeration:

home
work
mobile
None
targetsCDATANone

Description

- 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 -

- -

Parents

- phone may be contained in these - elements: - contact -

Attributes

location

- Indicates the location that the phone number connects to. This - attribute is optional. -

See Also

- address, email, fax, pager. -

Examples

<phone>555.555.1212</phone>
<phone location="mobile">345-262-4567</phone>
<phone location="home">(261) 345-1616</phone>

- For additional examples, see contact. -

Previousperiod UpElement Reference possibleNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.possible.html b/legacy-resumes/resume-1/doc/manual/html/element.possible.html deleted file mode 100644 index 027aa6d..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.possible.html +++ /dev/null @@ -1,16 +0,0 @@ - - - possible

XMLRésuméLibrary: - User Guide

Previousphone UpElement Reference postalCodeNext

Name

possible — The highest possible score in a GPA

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- possible may be contained in these - elements: - gpa -

See Also

- score. -

Examples

- For examples, see gpa. -

Previousphone UpElement Reference postalCodeNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.postalCode.html b/legacy-resumes/resume-1/doc/manual/html/element.postalCode.html deleted file mode 100644 index cb009cf..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.postalCode.html +++ /dev/null @@ -1,20 +0,0 @@ - - - postalCode

XMLRésuméLibrary: - User Guide

Previouspossible UpElement Reference prefectureNext

Name

postalCode — A postal code

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- postalCode may be contained in these - elements: - address -

See Also

- zip. -

Examples

A Brazilian postal code: - 

<postalCode>85070-200</postalCode>

-

A Canadian postal code: - 

<postalCode>V2B 5S8</postalCode>

-

Previouspossible UpElement Reference prefectureNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.prefecture.html b/legacy-resumes/resume-1/doc/manual/html/element.prefecture.html deleted file mode 100644 index 4111b9a..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.prefecture.html +++ /dev/null @@ -1,19 +0,0 @@ - - - prefecture

XMLRésuméLibrary: - User Guide

PreviouspostalCode UpElement Reference presentNext

Name

prefecture — A name of a prefecture or other administrative district

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- prefecture may be contained in these - elements: - address -

Attributes

id

- A string used to uniquely identify a prefecture. The prefecture - may then be referred to by this identifier. -

See Also

- city, county, state, suburb, ward. -

Examples

<prefecture>Basilius</prefecture>
PreviouspostalCode UpElement Reference presentNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.present.html b/legacy-resumes/resume-1/doc/manual/html/element.present.html deleted file mode 100644 index 39e22d0..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.present.html +++ /dev/null @@ -1,27 +0,0 @@ - - - present

XMLRésuméLibrary: - User Guide

Previousprefecture UpElement Reference projectNext

Name

present — Indicates the current time

Synopsis

Content Model

EMPTY

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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/>. -

Parents

- present may be contained in these - elements: - from, to -

See Also

- date. -

Examples

<period>
-  <from><date>
-    <month>May</month>
-    <year>1995</year>
-  </from>
-  <to>
-    <present/>
-  </to>
-</period>
Previousprefecture UpElement Reference projectNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.project.html b/legacy-resumes/resume-1/doc/manual/html/element.project.html deleted file mode 100644 index 4cbb283..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.project.html +++ /dev/null @@ -1,17 +0,0 @@ - - - project

XMLRésuméLibrary: - User Guide

Previouspresent UpElement Reference projectsNext

Name

project — Container for information about a project

Synopsis

Content Model

(#PCDATA|emphasis|citation|url|link)*

Attributes

NameTypeDefault
targetsCDATANone
titleCDATANone

Description

- The project element describes a - project that a person participated in at a job. -

Parents

- project may be contained in these - elements: - projects -

Attributes

title

- The title of the project. -

See Also

- achievement. -

Examples

- For examples, see projects. -

Previouspresent UpElement Reference projectsNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.projects.html b/legacy-resumes/resume-1/doc/manual/html/element.projects.html deleted file mode 100644 index 709aab7..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.projects.html +++ /dev/null @@ -1,17 +0,0 @@ - - - projects

XMLRésuméLibrary: - User Guide

Previousproject UpElement Reference provinceNext

Name

projects — Container for one or more projects

Synopsis

Content Model

(project+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The projects element groups together - one or more project elements. -

Parents

- projects may be contained in these - elements: - degree, job -

See Also

- achievements. -

Examples

<projects>
-  <project>Organization of Paperclips</project>
-  <project>Development of rocket booster fuel</project>
-  <project>1997 Papercut Convention</project>
-</projects>
Previousproject UpElement Reference provinceNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.province.html b/legacy-resumes/resume-1/doc/manual/html/element.province.html deleted file mode 100644 index 6955c94..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.province.html +++ /dev/null @@ -1,16 +0,0 @@ - - - province

XMLRésuméLibrary: - User Guide

Previousprojects UpElement Reference pubNext

Name

province — A name or abbreviation of a province

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The province element contains the - name or abbreviation of a single province or similar political division. -

Parents

- province may be contained in these - elements: - address, location -

Attributes

id

- A string used to uniquely identify a province. The province may - then be referred to by this identifier. -

See Also

- county, state. -

Examples

<province>Saskatchewan</province>
<province>BC</province>
Previousprojects UpElement Reference pubNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.pub.html b/legacy-resumes/resume-1/doc/manual/html/element.pub.html deleted file mode 100644 index 4a5254e..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.pub.html +++ /dev/null @@ -1,34 +0,0 @@ - - - pub

XMLRésuméLibrary: - User Guide

Previousprovince UpElement Reference pubDateNext

Name

pub — A work published by the résumé “owner”

Synopsis

Content Model

(para|(artTitle|bookTitle|author|date|pubDate|publisher|pageNums|url))*

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- pub may be contained in these - elements: - pubs -

Attributes

id

- A string used to uniquely identify a publication. The - publication may then be referred to by this identifier. -

See Also

- citation. -

Examples

Example 4. Book with multiple authors

<pub>
-  <bookTitle>Foundations of Computer Science, C Edition</bookTitle>
-  <author>Alfred V. Aho</author>
-  <author>Jeffrey D. Ullman</author>
-  <pubDate>
-    <year>1995</year>
-  </pubDate>
-  <publisher>Computer Science Press, New York</publisher>
-</pub>

Example 5. Magazine article

<pub>
-  <artTitle>Low-Fat Philly Cheese Steaks</bookTitle>
-  <bookTitle>Healthy Cooking</bookTitle>
-  <author>Joe Sixpack</author>
-  <pubDate>
-    <month>June</month>
-    <year>1999</year>
-  </pubDate>
-  <publisher>Healthy Publishing Group</publisher>
-</pub>
Previousprovince UpElement Reference pubDateNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.pubDate.html b/legacy-resumes/resume-1/doc/manual/html/element.pubDate.html deleted file mode 100644 index 518783d..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.pubDate.html +++ /dev/null @@ -1,32 +0,0 @@ - - - pubDate

XMLRésuméLibrary: - User Guide

Previouspub UpElement Reference publisherNext

Name

pubDate — The date a work was published

Deprecated

Synopsis

Content Model

(month?,year)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

Parents

- pubDate may be contained in these - elements: - pub -

See Also

- date. -

Examples

<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>
Previouspub UpElement Reference publisherNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.publisher.html b/legacy-resumes/resume-1/doc/manual/html/element.publisher.html deleted file mode 100644 index d488a03..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.publisher.html +++ /dev/null @@ -1,24 +0,0 @@ - - - publisher

XMLRésuméLibrary: - User Guide

PreviouspubDate UpElement Reference pubsNext

Name

publisher — Information about a publisher of a work

Synopsis

Content Model

(#PCDATA|link|url)*

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

Parents

- publisher may be contained in these - elements: - pub -

Examples

Example 6. Publisher name only

<pub>
-  <bookTitle>Deep Thoughts on Stuff</bookTitle>
-  <publisher>Totally Groovy Publishing, Ltd.</publisher>
-</pub>

Example 7. Publisher name and location

<pub>
-  <bookTitle>A User's Guide to Dirt</bookTitle>
-  <publisher>Mother Nature Books, Boston, Massachusetts</publisher>
-</pub>
PreviouspubDate UpElement Reference pubsNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.pubs.html b/legacy-resumes/resume-1/doc/manual/html/element.pubs.html deleted file mode 100644 index 6d49412..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.pubs.html +++ /dev/null @@ -1,21 +0,0 @@ - - - pubs

XMLRésuméLibrary: - User Guide

Previouspublisher UpElement Reference refereeNext

Name

pubs — A group of one or more publications

Synopsis

Content Model

(pub+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The pubs element groups together one - or more publications. -

Parents

- pubs may be contained in these - elements: - resume -

Examples

<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>
Previouspublisher UpElement Reference refereeNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.referee.html b/legacy-resumes/resume-1/doc/manual/html/element.referee.html deleted file mode 100644 index 3686225..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.referee.html +++ /dev/null @@ -1,33 +0,0 @@ - - - referee

XMLRésuméLibrary: - User Guide

Previouspubs UpElement Reference refereesNext

Name

referee — Someone who can provide additional information about the person the résumé describes

Synopsis

Content Model

(name,title?,organization?,address?,contact?)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Formatting

- The display of referee is influenced - by the referees.display parameter. -

Parents

- referee may be contained in these - elements: - referees -

Examples

<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. -

Previouspubs UpElement Reference refereesNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.referees.html b/legacy-resumes/resume-1/doc/manual/html/element.referees.html deleted file mode 100644 index f30e26f..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.referees.html +++ /dev/null @@ -1,27 +0,0 @@ - - - referees

XMLRésuméLibrary: - User Guide

Previousreferee UpElement Reference resultNext

Name

referees — Contains one or more referees

Synopsis

Content Model

(referee+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The referees element groups together - one or more referee elements. -

Parents

- referees may be contained in these - elements: - resume -

Examples

<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>
Previousreferee UpElement Reference resultNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.result.html b/legacy-resumes/resume-1/doc/manual/html/element.result.html deleted file mode 100644 index 314c915..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.result.html +++ /dev/null @@ -1,29 +0,0 @@ - - - result

XMLRésuméLibrary: - User Guide

Previousreferees UpElement Reference resumeNext

Name

result — An outcome of a subject

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The result element describes the - outcome or result of a subject. result often contains the letter or numeric - grade awarded for an academic class. -

Parents

- result may be contained in these - elements: - subject -

Examples

<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>
Previousreferees UpElement Reference resumeNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.resume.html b/legacy-resumes/resume-1/doc/manual/html/element.resume.html deleted file mode 100644 index 63d58f7..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.resume.html +++ /dev/null @@ -1,221 +0,0 @@ - - - resume

XMLRésuméLibrary: - User Guide

Previousresult UpElement Reference resumesNext

Name

resume — A résumé or curriculum vitae

Synopsis

Content Model

(docpath?,header?,((objective|history|academics|skillareas|skillarea|pubs|misc|referees|keywords|memberships|interests|clearances|awards))*,lastModified?,copyright?)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone
xmlnsCDATAhttp://xmlresume.sourceforge.net/resume/0.0
xmlns:xsiCDATAhttp://www.w3.org/2001/XMLSchema-instance
xsi:schemaLocationCDATANone

Description

- 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. -

Parents

- resume may be contained in these - elements: - resumes -

Attributes

id

- A string used to uniquely identify a résumé. The résumé may - then be referred to by this identifier. -

Examples

<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. -

Previousresult UpElement Reference resumesNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.resumes.html b/legacy-resumes/resume-1/doc/manual/html/element.resumes.html deleted file mode 100644 index 81be58c..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.resumes.html +++ /dev/null @@ -1,35 +0,0 @@ - - - resumes

XMLRésuméLibrary: - User Guide

Previousresume UpElement Reference scoreNext

Name

resumes — A collection of one or more résumés

Synopsis

Content Model

(resume*)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone
xmlnsCDATAhttp://xmlresume.sourceforge.net/resume/0.0
xmlns:xsiCDATAhttp://www.w3.org/2001/XMLSchema-instance
xsi:schemaLocationCDATANone

Description

- 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. -

Parents

- resumes may be contained in these - elements: - None -

Attributes

id

- A string used to uniquely identify a group of résumés. The - résumés may then be referred to by this identifier. -

Examples

<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>
Previousresume UpElement Reference scoreNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.score.html b/legacy-resumes/resume-1/doc/manual/html/element.score.html deleted file mode 100644 index 58d4c6e..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.score.html +++ /dev/null @@ -1,15 +0,0 @@ - - - score

XMLRésuméLibrary: - User Guide

Previousresumes UpElement Reference skillNext

Name

score — The score earned in a GPA

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The score element contains the GPA - score that a person has earned. -

Parents

- score may be contained in these - elements: - gpa -

See Also

- possible. -

Examples

- For examples, see gpa. -

Previousresumes UpElement Reference skillNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.skill.html b/legacy-resumes/resume-1/doc/manual/html/element.skill.html deleted file mode 100644 index da4d6ce..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.skill.html +++ /dev/null @@ -1,24 +0,0 @@ - - - skill

XMLRésuméLibrary: - User Guide

Previousscore UpElement Reference skillareaNext

Name

skill — A name and/or description of a skill

Synopsis

Content Model

(#PCDATA|emphasis|citation|url|link)*

Attributes

NameTypeDefault
idIDNone
levelCDATANone
targetsCDATANone

Description

- The skill element describes something - that a person is skilled at. -

Parents

- skill may be contained in these - elements: - skills, skillset -

Attributes

level

- The level attribute indicates - a person's level of proficiency at a skill. “Level of - proficiency” may be expressed in any manner, such as - “3 years” (three years of experience with a - particular skill), “expert”, or “7/10”. - The skills.level.display parameter - determines whether or not skill levels are displayed in formatted - output. -

See Also

- achievement, skills.format, skills.level.display. -

Examples

<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>
Previousscore UpElement Reference skillareaNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.skillarea.html b/legacy-resumes/resume-1/doc/manual/html/element.skillarea.html deleted file mode 100644 index 649e120..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.skillarea.html +++ /dev/null @@ -1,64 +0,0 @@ - - - skillarea

XMLRésuméLibrary: - User Guide

Previousskill UpElement Reference skillareasNext

Name

skillarea — A group of broadly related skill sets

Synopsis

Content Model

(title,skillset+)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Formatting

- 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. -

Parents

- skillarea may be contained in these - elements: - resume, skillareas -

Attributes

id

- A string used to uniquely identify a skill area. The skill area - may then be referred to by this identifier. -

Examples

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>
Previousskill UpElement Reference skillareasNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.skillareas.html b/legacy-resumes/resume-1/doc/manual/html/element.skillareas.html deleted file mode 100644 index c903eba..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.skillareas.html +++ /dev/null @@ -1,55 +0,0 @@ - - - skillareas

XMLRésuméLibrary: - User Guide

Previousskillarea UpElement Reference skillsNext

Name

skillareas — Group of one or more skill areas

Deprecated

Synopsis

Content Model

(skillarea+)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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é. -

Parents

- skillareas may be contained in these - elements: - resume -

Examples

<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>
Previousskillarea UpElement Reference skillsNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.skills.html b/legacy-resumes/resume-1/doc/manual/html/element.skills.html deleted file mode 100644 index 2a72059..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.skills.html +++ /dev/null @@ -1,30 +0,0 @@ - - - skills

XMLRésuméLibrary: - User Guide

Previousskillareas UpElement Reference skillsetNext

Name

skills — Group of one or more skills

Deprecated

Synopsis

Content Model

(skill+)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

Important

- 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. -

Parents

- skills may be contained in these - elements: - skillset -

Attributes

id

- A string used to uniquely identify a skills group. The group may - then be referred to by this identifier. -

See Also

- skills.format. -

Examples

<skills>
-  <skill>Leaping over tall buildings in a single bound</skill>
-  <skill>Flying</skill>
-  <skill>Quickly changing clothes</skill>
-</skill>
Previousskillareas UpElement Reference skillsetNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.skillset.html b/legacy-resumes/resume-1/doc/manual/html/element.skillset.html deleted file mode 100644 index 88bfc35..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.skillset.html +++ /dev/null @@ -1,23 +0,0 @@ - - - skillset

XMLRésuméLibrary: - User Guide

Previousskills UpElement Reference stateNext

Name

skillset — A titled group of one or more related skills

Synopsis

Content Model

(title?,(skill+|skills))

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The skillset element contains a - titled set of (usually closely) related skills. -

Formatting

- The skills.format - parameter controls the formatting of skill sets. -

Parents

- skillset may be contained in these - elements: - skillarea -

Attributes

id

- A string used to uniquely identify a skill set. The skill set - may then be referred to by this identifier. -

Examples

<skillset>
-  <title>Eating Utinsels</title>
-  <skill>Knife</skill>
-  <skill>Fork</skill>
-  <skill>Spoon</skill>
-  <skill>Soup Spoon</skill>
-</skillset>
Previousskills UpElement Reference stateNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.state.html b/legacy-resumes/resume-1/doc/manual/html/element.state.html deleted file mode 100644 index 8c5c0d8..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.state.html +++ /dev/null @@ -1,21 +0,0 @@ - - - state

XMLRésuméLibrary: - User Guide

Previousskillset UpElement Reference streetNext

Name

state — A name or abbreviation of a state

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- state may be contained in these - elements: - address, location -

Attributes

id

- A string used to uniquely identify a state name. The name may - then be referred to by this identifier. -

See Also

- province, county, prefecture. -

Examples

Example 10. State name

<state>New York</state>

Example 11. State abbreviation

<state>NY</state>
Previousskillset UpElement Reference streetNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.street.html b/legacy-resumes/resume-1/doc/manual/html/element.street.html deleted file mode 100644 index ffc8979..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.street.html +++ /dev/null @@ -1,21 +0,0 @@ - - - street

XMLRésuméLibrary: - User Guide

Previousstate UpElement Reference street2Next

Name

street — A street name, number, and other related information

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- street may be contained in these - elements: - address -

Attributes

id

- A string used to uniquely identify a street. The street may then - be referred to by this identifier. -

Examples

- For examples, see address. -

Previousstate UpElement Reference street2Next
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.street2.html b/legacy-resumes/resume-1/doc/manual/html/element.street2.html deleted file mode 100644 index fe827dc..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.street2.html +++ /dev/null @@ -1,28 +0,0 @@ - - - street2

XMLRésuméLibrary: - User Guide

Previousstreet UpElement Reference subjectNext

Name

street2 — A second line of a street address

Deprecated

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

Important

- 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. -

Parents

- street2 may be contained in these - elements: - address -

Attributes

id

- A string used to uniquely identify the second line of a street - address. The line may then be referred to by this identifier. -

See Also

- street. -

Examples

- None. -

Previousstreet UpElement Reference subjectNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.subject.html b/legacy-resumes/resume-1/doc/manual/html/element.subject.html deleted file mode 100644 index 1ffe087..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.subject.html +++ /dev/null @@ -1,23 +0,0 @@ - - - subject

XMLRésuméLibrary: - User Guide

Previousstreet2 UpElement Reference subjectsNext

Name

subject — A name of a class or topic of study

Synopsis

Content Model

(title,result)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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). -

Parents

- subject may be contained in these - elements: - subjects -

Examples

<subject>
-  <title>English</title>
-  <result>A-</result>
-</subject>
<subject>
-  <title>PE 194 Crabwalking</title>
-  <result>F</result>
-</subject>
Previousstreet2 UpElement Reference subjectsNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.subjects.html b/legacy-resumes/resume-1/doc/manual/html/element.subjects.html deleted file mode 100644 index 914471b..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.subjects.html +++ /dev/null @@ -1,22 +0,0 @@ - - - subjects

XMLRésuméLibrary: - User Guide

Previoussubject UpElement Reference suburbNext

Name

subjects — A group of one or more subjects

Synopsis

Content Model

(subject+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The subjects element contains one or - more subjects that were studied as part of - the degree represented by the parent of the - subjects. -

Parents

- subjects may be contained in these - elements: - degree -

Examples

<subjects>
-  <subject>
-    <title>Chemistry</title>
-    <result>C</result>
-  </subject>
-  <subject>
-    <title>Physics</title>
-    <result>B-</result>
-  </subject>
-</subjects>
Previoussubject UpElement Reference suburbNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.suburb.html b/legacy-resumes/resume-1/doc/manual/html/element.suburb.html deleted file mode 100644 index 1d60f36..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.suburb.html +++ /dev/null @@ -1,25 +0,0 @@ - - - suburb

XMLRésuméLibrary: - User Guide

Previoussubjects UpElement Reference suffixNext

Name

suburb — A name of a suburb

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The suburb element contains the name - of a suburb, as used by a postal service to deliver mail. -

Parents

- suburb may be contained in these - elements: - address -

Attributes

id

- A string used to uniquely identify a suburb. The suburb may then - be referred to by this identifier. -

See Also

- city, prefecture, ward. -

- --> - -

Examples

Example 12. A New Zealand Address

<address>
-  <street>236 Majoribanks Street</street>
-  <suburb>Mount Victoria</suburb>
-  <city>Wellington</city>
-  <postalCode>6001</postalCode>
-  <country>New Zealand</country>
-</address>
Previoussubjects UpElement Reference suffixNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.suffix.html b/legacy-resumes/resume-1/doc/manual/html/element.suffix.html deleted file mode 100644 index f77503c..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.suffix.html +++ /dev/null @@ -1,21 +0,0 @@ - - - suffix

XMLRésuméLibrary: - User Guide

Previoussuburb UpElement Reference surnameNext

Name

suffix — A suffix of a name, usually specifying lineage

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The suffix element contains a suffix - or suffix abbreviation that follows a name, such as “Jr.”, - “Senior”, or “III”. -

Parents

- suffix may be contained in these - elements: - name -

Examples

<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>
Previoussuburb UpElement Reference surnameNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.surname.html b/legacy-resumes/resume-1/doc/manual/html/element.surname.html deleted file mode 100644 index 966b411..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.surname.html +++ /dev/null @@ -1,13 +0,0 @@ - - - surname

XMLRésuméLibrary: - User Guide

Previoussuffix UpElement Reference tailNext

Name

surname — A family name

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The surname element contains a - person's family, or last name. -

Parents

- surname may be contained in these - elements: - name -

Examples

- For examples, see name. -

Previoussuffix UpElement Reference tailNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.tail.html b/legacy-resumes/resume-1/doc/manual/html/element.tail.html deleted file mode 100644 index 869fe99..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.tail.html +++ /dev/null @@ -1,13 +0,0 @@ - - - tail

XMLRésuméLibrary: - User Guide

Previoussurname UpElement Reference titleNext

Name

tail —

Deprecated

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

- -

Parents

- tail may be contained in these - elements: - docpath -

Examples

<!-- TODO -->
Previoussurname UpElement Reference titleNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.title.html b/legacy-resumes/resume-1/doc/manual/html/element.title.html deleted file mode 100644 index ec42e38..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.title.html +++ /dev/null @@ -1,91 +0,0 @@ - - - title

XMLRésuméLibrary: - User Guide

Previoustail UpElement Reference toNext

Name

title — A title or heading

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The title element contains a title or - heading. Its semantics vary depending on the element that contains it: - -

name

- When contained in this element, title contains a person's formal title, - such as “Dr.”, “Ms.”, or - “Professor”. -

interest

- When contained in this element, title contains the name of an interest, - such as “Cooking”, or “Politics”. -

membership, referee

- When contained in these elements, title contains the name of the - person's role or capacity withing an organization. Examples: - “Treasurer”, “Member”, “Chief - Officer of Toothpaste Policy”, “Lead - Programmer”. -

awards, interests, memberships, skillarea

- When contained in these elements, title contains a heading for that - section of a résumé. It is formatted as a top-level heading. -

Note

- The title element is optional - in awards and interests. If it is not present, the - awards.word and - interests.word parameters will be used - as the heading text in formatted résumés, respectively. -

skillset

- When contained in this element, title contains the name of a skill - category. Examples: “Teaching”, - “Computers”, “Woodworking”, - “Soap Carving”. -

subject

- When contained in this element, title contains the name of a subject. - It can be as general as “English” (a very broad - field of study), or as specific as “Eng 115 Intro to - Writing Fall 2001” (a specific university course name, - number, and date of study). -

- -

Parents

- title may be contained in these - elements: - award, awards, clearances, interest, interests, membership, memberships, name, referee, skillarea, skillset, subject -

See Also

- artTitle, bookTitle. -

Examples

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>

Example 16. subject title

<subject>
-  <title>Intro to Sociology</title>
-  <result>A-</result>
-</subject>
Previoustail UpElement Reference toNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.to.html b/legacy-resumes/resume-1/doc/manual/html/element.to.html deleted file mode 100644 index 1a6c33e..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.to.html +++ /dev/null @@ -1,16 +0,0 @@ - - - to

XMLRésuméLibrary: - User Guide

Previoustitle UpElement Reference uriNext

Name

to — The ending point in a period of time

Synopsis

Content Model

(date|present)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- to may be contained in these - elements: - period -

See Also

- from. -

Examples

- For examples, see from and period. -

Previoustitle UpElement Reference uriNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.uri.html b/legacy-resumes/resume-1/doc/manual/html/element.uri.html deleted file mode 100644 index 3730abc..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.uri.html +++ /dev/null @@ -1,13 +0,0 @@ - - - uri

XMLRésuméLibrary: - User Guide

Previousto UpElement Reference urlNext

Name

uri — A Uniform Resource Indicator

Deprecated

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

- -

Parents

- uri may be contained in these - elements: - head, node -

Examples

<!-- TODO -->
Previousto UpElement Reference urlNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.url.html b/legacy-resumes/resume-1/doc/manual/html/element.url.html deleted file mode 100644 index c6e9a42..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.url.html +++ /dev/null @@ -1,47 +0,0 @@ - - - url

XMLRésuméLibrary: - User Guide

Previousuri UpElement Reference wardNext

Name

url — A Uniform Resource Locator

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

Formatting

- 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). -

HTML

- 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. -

FO/PDF

- 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. -

Plain text

- Formatted as the value of the element. -

Parents

- url may be contained in these - elements: - achievement, contact, employer, institution, organization, para, project, pub, publisher, skill -

See Also

- link. - uri. -

Examples

<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>
Previousuri UpElement Reference wardNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.ward.html b/legacy-resumes/resume-1/doc/manual/html/element.ward.html deleted file mode 100644 index 7ab60bf..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.ward.html +++ /dev/null @@ -1,25 +0,0 @@ - - - ward

XMLRésuméLibrary: - User Guide

Previousurl UpElement Reference yearNext

Name

ward — A name of a division of a city, town, or county

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- ward may be contained in these - elements: - address -

Attributes

id

- A string used to uniquely identify a ward. The ward may then be - referred to by this identifier. -

See Also

- county, prefecture, suburb. -

Examples

<address>
-  <street>Rua Afonso Camargo, 805</street>
-  <ward>Santana</ward>
-  <city>Guarapuava</city>
-  <state>PR</state>
-  <postalCode>85070-200</postalCode>
-  <country>Brazil</country>
-</address>
Previousurl UpElement Reference yearNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.year.html b/legacy-resumes/resume-1/doc/manual/html/element.year.html deleted file mode 100644 index 0c7880f..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.year.html +++ /dev/null @@ -1,12 +0,0 @@ - - - year

XMLRésuméLibrary: - User Guide

Previousward UpElement Reference zipNext

Name

year — A year

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The year element contains a year - number, along with a possible string that identifies the date system, - such as “B.C.” or “A.D.”. -

Parents

- year may be contained in these - elements: - copyright, date, pubDate -

Examples

<year>1995</year>
<year>240 A.D.</year>
Previousward UpElement Reference zipNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/element.zip.html b/legacy-resumes/resume-1/doc/manual/html/element.zip.html deleted file mode 100644 index 3d085b2..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/element.zip.html +++ /dev/null @@ -1,22 +0,0 @@ - - - zip

XMLRésuméLibrary: - User Guide

Previousyear UpElement Reference XSL Parameter ReferenceNext

Name

zip — A zip code

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- zip may be contained in these - elements: - address -

Attributes

id

- A string used to uniquely identify a zip code. The zip code may - then be referred to by this identifier. -

See Also

- postalCode. -

Examples

- For examples, see address. -

Previousyear UpElement Reference XSL Parameter ReferenceNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/elementref.html b/legacy-resumes/resume-1/doc/manual/html/elementref.html deleted file mode 100644 index 6430cc2..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/elementref.html +++ /dev/null @@ -1,186 +0,0 @@ - - - Element Reference

XMLRésuméLibrary: - User Guide

PreviousPart II. Reference UpPart II. Reference academicsNext

Element Reference

- 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. -

Changes to the DTD

- This sections documents changes to the XML Résumé Library DTD. -

Warning

- 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. -

Version ???

  • - Changed elements: - projects - may now be included in the - degree - element. -

Version 1.5.0

  • - 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. -

Version 1.4.2

- No DTD changes. -

Version 1.4.1

Version 1.4.0

  • - New element: minor. -

  • - New element: lastModified. -

  • - New elements: awards and - award. -

  • - New elements: interests and - interest. -

  • - 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. -

Version 1.3.3

  • - 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. -

Version 1.3.2

- No DTD changes. -

Table of Contents

academics - Container for information about academic experience
achievement - An accomplishment made at a job
achievements - Container for one or more job achievements
address - A postal address
annotation - Additional information about a degree
artTitle - A title of an article or other work
author - An author of a publication
award - An award or other honor
awards - Container for one or more awards
birth - Container for information about a person's birth
bookTitle - A title of a book or similar work
break - A linebreak (Deprecated)
citation - The name of a work being referenced
city - The name of a city
clearance - A security clearance
clearances - One or more security clearances
company - The name of a company (Deprecated)
contact - Container for one or more methods of contacting someone
copyright - A copyright notice
country - A country name
county - A county name
date - A specific instant in time
dayOfMonth - An ordinal day of the month
degree - Container for information about a degree or similar certification
degrees - Container for one or more degrees
description - An explanation of something
docpath - (Deprecated)
email - An e-mail address
emphasis - An emphasized block of text
employer - A name of an employer
fax - A fax telephone number
firstname - A person's given name
from - The beginning point in a period of time
gpa - Information about a grade point average
head - (Deprecated)
header - Container for information about the person being described in a résumé
history - Container for a person's previous (and possibly current) jobs
instantMessage - An instant message username or address
institution - A name of an academic institution
interest - Something a person is interested in
interests - Container for one or more interests
job - A specific employment engagement
jobtitle - A job title
keyword - A keyword to be used for résumé indexing and searching
keywords - Container for a list of keywords
label - (Deprecated)
lastModified - Information about when a résumé was last modified
legalnotice - A legal statement
level - A degree type
link - A titled hyperlink
location - A location, with city-level granularity
major - A main course of study
membership - A professional membership
memberships - Container for one or more memberships
middlenames - One or more middle names of a person
minor - A minor course of study
misc - Miscellaneous remarks
month - A month name
name - A person's name
node - (Deprecated)
note - Additional information
objective - A person's employment goal
organization - A name of an organization
pageNums - One or more page numbers or ranges
pager - A pager telephone number
para - A paragraph of text
period - A period of time
phone - A voice telephone number
possible - The highest possible score in a GPA
postalCode - A postal code
prefecture - A name of a prefecture or other administrative district
present - Indicates the current time
project - Container for information about a project
projects - Container for one or more projects
province - A name or abbreviation of a province
pub - A work published by the résumé owner
pubDate - The date a work was published (Deprecated)
publisher - Information about a publisher of a work
pubs - A group of one or more publications
referee - Someone who can provide additional information about the person the résumé describes
referees - Contains one or more referees
result - An outcome of a subject
resume - A résumé or curriculum vitae
resumes - A collection of one or more résumés
score - The score earned in a GPA
skill - A name and/or description of a skill
skillarea - A group of broadly related skill sets
skillareas - Group of one or more skill areas (Deprecated)
skills - Group of one or more skills (Deprecated)
skillset - A titled group of one or more related skills
state - A name or abbreviation of a state
street - A street name, number, and other related information
street2 - A second line of a street address (Deprecated)
subject - A name of a class or topic of study
subjects - A group of one or more subjects
suburb - A name of a suburb
suffix - A suffix of a name, usually specifying lineage
surname - A family name
tail - (Deprecated)
title - A title or heading
to - The ending point in a period of time
uri - A Uniform Resource Indicator (Deprecated)
url - A Uniform Resource Locator
ward - A name of a division of a city, town, or county
year - A year
zip - A zip code
PreviousPart II. Reference UpPart II. Reference academicsNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/getting-started.explore.about.html b/legacy-resumes/resume-1/doc/manual/html/getting-started.explore.about.html deleted file mode 100644 index d4f2dfe..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/getting-started.explore.about.html +++ /dev/null @@ -1,11 +0,0 @@ - - - About this chapter

XMLRésuméLibrary: - User Guide

PreviousWhere to Go from Here UpExploring the Features of XML Résumé Library Part II. ReferenceNext

About this chapter

- 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>. -

PreviousWhere to Go from Here UpExploring the Features of XML Résumé Library Part II. ReferenceNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/getting-started.explore.create.html b/legacy-resumes/resume-1/doc/manual/html/getting-started.explore.create.html deleted file mode 100644 index b87ae16..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/getting-started.explore.create.html +++ /dev/null @@ -1,13 +0,0 @@ - - - Writing your first XML Résumé

XMLRésuméLibrary: - User Guide

PreviousAdvanced Features of the XML Résumé Library UpExploring the Features of XML Résumé Library Where to Go from HereNext

Writing your first XML Résumé

- 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. -

PreviousAdvanced Features of the XML Résumé Library UpExploring the Features of XML Résumé Library Where to Go from HereNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/getting-started.explore.features.html b/legacy-resumes/resume-1/doc/manual/html/getting-started.explore.features.html deleted file mode 100644 index 6d98e75..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/getting-started.explore.features.html +++ /dev/null @@ -1,134 +0,0 @@ - - - Advanced Features of the XML Résumé Library

XMLRésuméLibrary: - User Guide

PreviousExploring the Features of XML Résumé Library UpExploring the Features of XML Résumé Library Writing your first XML RésuméNext

Advanced Features of the XML Résumé Library

Filtering to target your resume

- 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. -

Customizing your résumé

- With just a few tweaks, you can dramatically change the look - of your résumés. -

Modifying the XSL Parameters

- 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. -

Note

- 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. -

Modifying the look of your HTML Résumé

- 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. -

PreviousExploring the Features of XML Résumé Library UpExploring the Features of XML Résumé Library Writing your first XML RésuméNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/getting-started.explore.html b/legacy-resumes/resume-1/doc/manual/html/getting-started.explore.html deleted file mode 100644 index b7b0293..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/getting-started.explore.html +++ /dev/null @@ -1,22 +0,0 @@ - - - Chapter 2. Exploring the Features of XML Résumé Library

XMLRésuméLibrary: - User Guide

PreviousInstalling and Configuring the Software UpPart I. Getting Started Advanced Features of the XML Résumé LibraryNext

Exploring the Features of XML Résumé Library

Peter Hutnick

Mark Miller

Edited by

Bruce Christensen

Copyright © 2002 Peter Hutnick

Formatting an example resume
Advanced Features of the XML Résumé Library
Writing your first XML Résumé
Where to Go from Here
About this chapter

- 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. -

Formatting an example resume

Converting to other formats

- 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é. -

PreviousInstalling and Configuring the Software UpPart I. Getting Started Advanced Features of the XML Résumé LibraryNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/getting-started.explore.next-steps.html b/legacy-resumes/resume-1/doc/manual/html/getting-started.explore.next-steps.html deleted file mode 100644 index 4f22112..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/getting-started.explore.next-steps.html +++ /dev/null @@ -1,20 +0,0 @@ - - - Where to Go from Here

XMLRésuméLibrary: - User Guide

PreviousWriting your first XML Résumé UpExploring the Features of XML Résumé Library About this chapterNext

Where to Go from Here

Documentation

- 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. -

Support

- 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>. -

PreviousWriting your first XML Résumé UpExploring the Features of XML Résumé Library About this chapterNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/getting-started.html b/legacy-resumes/resume-1/doc/manual/html/getting-started.html deleted file mode 100644 index 1376205..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/getting-started.html +++ /dev/null @@ -1,4 +0,0 @@ - - - Part I. Getting Started

XMLRésuméLibrary: - User Guide

PreviousIntroduction UpXML Résumé Library User Guide Setting up the XML Résumé LibraryNext

Getting Started

Table of Contents

1. Setting up the XML Résumé Library
Prerequisites
Getting the Software
Installing and Configuring the Software
2. Exploring the Features of XML Résumé Library
Formatting an example resume
Advanced Features of the XML Résumé Library
Writing your first XML Résumé
Where to Go from Here
About this chapter
PreviousIntroduction UpXML Résumé Library User Guide Setting up the XML Résumé LibraryNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/getting-started.setup.html b/legacy-resumes/resume-1/doc/manual/html/getting-started.setup.html deleted file mode 100644 index b897afc..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/getting-started.setup.html +++ /dev/null @@ -1,29 +0,0 @@ - - - Chapter 1. Setting up the XML Résumé Library

XMLRésuméLibrary: - User Guide

PreviousPart I. Getting Started UpPart I. Getting Started Getting the SoftwareNext

Setting up the XML Résumé Library

Peter Hutnick

Edited by

Bruce Christensen

Mark Miller

Copyright © 2002 Peter Hutnick

Prerequisites
Getting the Software
Installing and Configuring the Software

- 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. -

Prerequisites

Java

- 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. -

XML

- 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. -

PreviousPart I. Getting Started UpPart I. Getting Started Getting the SoftwareNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/getting-started.setup.install.html b/legacy-resumes/resume-1/doc/manual/html/getting-started.setup.install.html deleted file mode 100644 index 5911a3e..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/getting-started.setup.install.html +++ /dev/null @@ -1,86 +0,0 @@ - - - Installing and Configuring the Software

XMLRésuméLibrary: - User Guide

PreviousGetting the Software UpSetting up the XML Résumé Library Exploring the Features of XML Résumé LibraryNext

Installing and Configuring the Software

XML Résumé Library

- 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. -

Tip

You can also indicate your résumé filename on the command line - when you build your résumé, e.g.: - - 

[resume]$ make resume=myresume

-

Note

- 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">

- -

Xerces, Xalan, and FOP

- 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. -

PreviousGetting the Software UpSetting up the XML Résumé Library Exploring the Features of XML Résumé LibraryNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/getting-started.setup.software.html b/legacy-resumes/resume-1/doc/manual/html/getting-started.setup.software.html deleted file mode 100644 index 29bbd6f..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/getting-started.setup.software.html +++ /dev/null @@ -1,29 +0,0 @@ - - - Getting the Software

XMLRésuméLibrary: - User Guide

PreviousSetting up the XML Résumé Library UpSetting up the XML Résumé Library Installing and Configuring the SoftwareNext

Getting the Software

XML Résumé Library

- 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

- 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

- 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

- 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. -

PreviousSetting up the XML Résumé Library UpSetting up the XML Résumé Library Installing and Configuring the SoftwareNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/gfdl-1.html b/legacy-resumes/resume-1/doc/manual/html/gfdl-1.html deleted file mode 100644 index 966aef9..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/gfdl-1.html +++ /dev/null @@ -1,52 +0,0 @@ - - - APPLICABILITY AND DEFINITIONS

XMLRésuméLibrary: - User Guide

PreviousGNU Free Documentation License UpGNU Free Documentation License VERBATIM COPYINGNext

APPLICABILITY AND DEFINITIONS

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.

PreviousGNU Free Documentation License UpGNU Free Documentation License VERBATIM COPYINGNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/gfdl-10.html b/legacy-resumes/resume-1/doc/manual/html/gfdl-10.html deleted file mode 100644 index 2050a47..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/gfdl-10.html +++ /dev/null @@ -1,16 +0,0 @@ - - - FUTURE REVISIONS OF THIS LICENSE

XMLRésuméLibrary: - User Guide

PreviousTERMINATION UpGNU Free Documentation License How to use this License for your documentsNext

FUTURE REVISIONS OF THIS LICENSE

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.

PreviousTERMINATION UpGNU Free Documentation License How to use this License for your documentsNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/gfdl-11.html b/legacy-resumes/resume-1/doc/manual/html/gfdl-11.html deleted file mode 100644 index 7a26d07..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/gfdl-11.html +++ /dev/null @@ -1,22 +0,0 @@ - - - How to use this License for your documents

XMLRésuméLibrary: - User Guide

PreviousFUTURE REVISIONS OF THIS LICENSE UpGNU Free Documentation License 

How to use this License for your documents

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.

PreviousFUTURE REVISIONS OF THIS LICENSE UpGNU Free Documentation License 
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/gfdl-2.html b/legacy-resumes/resume-1/doc/manual/html/gfdl-2.html deleted file mode 100644 index c2c21da..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/gfdl-2.html +++ /dev/null @@ -1,14 +0,0 @@ - - - VERBATIM COPYING

XMLRésuméLibrary: - User Guide

PreviousAPPLICABILITY AND DEFINITIONS UpGNU Free Documentation License COPYING IN QUANTITYNext

VERBATIM COPYING

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.

PreviousAPPLICABILITY AND DEFINITIONS UpGNU Free Documentation License COPYING IN QUANTITYNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/gfdl-3.html b/legacy-resumes/resume-1/doc/manual/html/gfdl-3.html deleted file mode 100644 index 7b97dfd..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/gfdl-3.html +++ /dev/null @@ -1,34 +0,0 @@ - - - COPYING IN QUANTITY

XMLRésuméLibrary: - User Guide

PreviousVERBATIM COPYING UpGNU Free Documentation License MODIFICATIONSNext

COPYING IN QUANTITY

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.

PreviousVERBATIM COPYING UpGNU Free Documentation License MODIFICATIONSNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/gfdl-4.html b/legacy-resumes/resume-1/doc/manual/html/gfdl-4.html deleted file mode 100644 index cb80a35..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/gfdl-4.html +++ /dev/null @@ -1,77 +0,0 @@ - - - MODIFICATIONS

XMLRésuméLibrary: - User Guide

PreviousCOPYING IN QUANTITY UpGNU Free Documentation License COMBINING DOCUMENTSNext

MODIFICATIONS

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:

  1. 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.

  2. 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).

  3. State on the Title page - the name of the publisher of the Modified Version, as the - publisher.

  4. Preserve all the - copyright notices of the Document.

  5. Add an appropriate - copyright notice for your modifications adjacent to the other - copyright notices.

  6. 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.

  7. Preserve in that license - notice the full lists of Invariant Sections and required Cover - Texts given in the Document's license notice.

  8. Include an unaltered - copy of this License.

  9. 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.

  10. 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.

  11. 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.

  12. 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.

  13. Delete any section - entitled “Endorsements”. Such a section may not be included in - the Modified Version.

  14. 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.

PreviousCOPYING IN QUANTITY UpGNU Free Documentation License COMBINING DOCUMENTSNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/gfdl-5.html b/legacy-resumes/resume-1/doc/manual/html/gfdl-5.html deleted file mode 100644 index 4d23719..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/gfdl-5.html +++ /dev/null @@ -1,21 +0,0 @@ - - - COMBINING DOCUMENTS

XMLRésuméLibrary: - User Guide

PreviousMODIFICATIONS UpGNU Free Documentation License COLLECTIONS OF DOCUMENTSNext

COMBINING DOCUMENTS

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.”

PreviousMODIFICATIONS UpGNU Free Documentation License COLLECTIONS OF DOCUMENTSNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/gfdl-6.html b/legacy-resumes/resume-1/doc/manual/html/gfdl-6.html deleted file mode 100644 index 0f3679b..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/gfdl-6.html +++ /dev/null @@ -1,13 +0,0 @@ - - - COLLECTIONS OF DOCUMENTS

XMLRésuméLibrary: - User Guide

PreviousCOMBINING DOCUMENTS UpGNU Free Documentation License AGGREGATION WITH INDEPENDENT WORKSNext

COLLECTIONS OF DOCUMENTS

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.

PreviousCOMBINING DOCUMENTS UpGNU Free Documentation License AGGREGATION WITH INDEPENDENT WORKSNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/gfdl-7.html b/legacy-resumes/resume-1/doc/manual/html/gfdl-7.html deleted file mode 100644 index 706744e..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/gfdl-7.html +++ /dev/null @@ -1,17 +0,0 @@ - - - AGGREGATION WITH INDEPENDENT WORKS

XMLRésuméLibrary: - User Guide

PreviousCOLLECTIONS OF DOCUMENTS UpGNU Free Documentation License TRANSLATIONNext

AGGREGATION WITH INDEPENDENT WORKS

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.

PreviousCOLLECTIONS OF DOCUMENTS UpGNU Free Documentation License TRANSLATIONNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/gfdl-8.html b/legacy-resumes/resume-1/doc/manual/html/gfdl-8.html deleted file mode 100644 index 7a4283f..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/gfdl-8.html +++ /dev/null @@ -1,14 +0,0 @@ - - - TRANSLATION

XMLRésuméLibrary: - User Guide

PreviousAGGREGATION WITH INDEPENDENT WORKS UpGNU Free Documentation License TERMINATIONNext

TRANSLATION

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.

PreviousAGGREGATION WITH INDEPENDENT WORKS UpGNU Free Documentation License TERMINATIONNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/gfdl-9.html b/legacy-resumes/resume-1/doc/manual/html/gfdl-9.html deleted file mode 100644 index 55f0dcc..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/gfdl-9.html +++ /dev/null @@ -1,11 +0,0 @@ - - - TERMINATION

XMLRésuméLibrary: - User Guide

PreviousTRANSLATION UpGNU Free Documentation License FUTURE REVISIONS OF THIS LICENSENext

TERMINATION

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.

PreviousTRANSLATION UpGNU Free Documentation License FUTURE REVISIONS OF THIS LICENSENext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/gfdl.html b/legacy-resumes/resume-1/doc/manual/html/gfdl.html deleted file mode 100644 index 93ee6e0..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/gfdl.html +++ /dev/null @@ -1,24 +0,0 @@ - - - Appendix A. GNU Free Documentation License

XMLRésuméLibrary: - User Guide

PreviousPart III. Appendixes UpPart III. Appendixes APPLICABILITY AND DEFINITIONSNext

Appendix A. GNU Free Documentation License

PREAMBLE
APPLICABILITY AND DEFINITIONS
VERBATIM COPYING
COPYING IN QUANTITY
MODIFICATIONS
COMBINING DOCUMENTS
COLLECTIONS OF DOCUMENTS
AGGREGATION WITH INDEPENDENT WORKS
TRANSLATION
TERMINATION
FUTURE REVISIONS OF THIS LICENSE
How to use this License for your documents

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.

PREAMBLE

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.

PreviousPart III. Appendixes UpPart III. Appendixes APPLICABILITY AND DEFINITIONSNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/gloss.html b/legacy-resumes/resume-1/doc/manual/html/gloss.html deleted file mode 100644 index 1ec7770..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/gloss.html +++ /dev/null @@ -1,26 +0,0 @@ - - - Glossary

XMLRésuméLibrary: - User Guide

PreviousCSS Class Reference UpXML Résumé Library User Guide Part III. AppendixesNext

Glossary

attribute

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">
element

- 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. -

parent element

- The element - whose start tags and end tags surround a given element. -

child element

- Any element - positioned between the start tags and end tags of a given - element. -

PreviousCSS Class Reference UpXML Résumé Library User Guide Part III. AppendixesNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/index.html b/legacy-resumes/resume-1/doc/manual/html/index.html deleted file mode 100644 index 2fa3534..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/index.html +++ /dev/null @@ -1,13 +0,0 @@ - - - XML Résumé Library User Guide

XMLRésuméLibrary: - User Guide

   IntroductionNext

XML Résumé Library User Guide

For XML Résumé Library Version 1.5.1

Bruce Christensen

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

Introduction
What is the XML Résumé Library?
I. Getting Started
1. Setting up the XML Résumé Library
Prerequisites
Getting the Software
Installing and Configuring the Software
2. Exploring the Features of XML Résumé Library
Formatting an example resume
Advanced Features of the XML Résumé Library
Writing your first XML Résumé
Where to Go from Here
About this chapter
II. Reference
I. Element Reference
academics - Container for information about academic experience
achievement - An accomplishment made at a job
achievements - Container for one or more job achievements
address - A postal address
annotation - Additional information about a degree
artTitle - A title of an article or other work
author - An author of a publication
award - An award or other honor
awards - Container for one or more awards
birth - Container for information about a person's birth
bookTitle - A title of a book or similar work
break - A linebreak (Deprecated)
citation - The name of a work being referenced
city - The name of a city
clearance - A security clearance
clearances - One or more security clearances
company - The name of a company (Deprecated)
contact - Container for one or more methods of contacting someone
copyright - A copyright notice
country - A country name
county - A county name
date - A specific instant in time
dayOfMonth - An ordinal day of the month
degree - Container for information about a degree or similar certification
degrees - Container for one or more degrees
description - An explanation of something
docpath - (Deprecated)
email - An e-mail address
emphasis - An emphasized block of text
employer - A name of an employer
fax - A fax telephone number
firstname - A person's given name
from - The beginning point in a period of time
gpa - Information about a grade point average
head - (Deprecated)
header - Container for information about the person being described in a résumé
history - Container for a person's previous (and possibly current) jobs
instantMessage - An instant message username or address
institution - A name of an academic institution
interest - Something a person is interested in
interests - Container for one or more interests
job - A specific employment engagement
jobtitle - A job title
keyword - A keyword to be used for résumé indexing and searching
keywords - Container for a list of keywords
label - (Deprecated)
lastModified - Information about when a résumé was last modified
legalnotice - A legal statement
level - A degree type
link - A titled hyperlink
location - A location, with city-level granularity
major - A main course of study
membership - A professional membership
memberships - Container for one or more memberships
middlenames - One or more middle names of a person
minor - A minor course of study
misc - Miscellaneous remarks
month - A month name
name - A person's name
node - (Deprecated)
note - Additional information
objective - A person's employment goal
organization - A name of an organization
pageNums - One or more page numbers or ranges
pager - A pager telephone number
para - A paragraph of text
period - A period of time
phone - A voice telephone number
possible - The highest possible score in a GPA
postalCode - A postal code
prefecture - A name of a prefecture or other administrative district
present - Indicates the current time
project - Container for information about a project
projects - Container for one or more projects
province - A name or abbreviation of a province
pub - A work published by the résumé owner
pubDate - The date a work was published (Deprecated)
publisher - Information about a publisher of a work
pubs - A group of one or more publications
referee - Someone who can provide additional information about the person the résumé describes
referees - Contains one or more referees
result - An outcome of a subject
resume - A résumé or curriculum vitae
resumes - A collection of one or more résumés
score - The score earned in a GPA
skill - A name and/or description of a skill
skillarea - A group of broadly related skill sets
skillareas - Group of one or more skill areas (Deprecated)
skills - Group of one or more skills (Deprecated)
skillset - A titled group of one or more related skills
state - A name or abbreviation of a state
street - A street name, number, and other related information
street2 - A second line of a street address (Deprecated)
subject - A name of a class or topic of study
subjects - A group of one or more subjects
suburb - A name of a suburb
suffix - A suffix of a name, usually specifying lineage
surname - A family name
tail - (Deprecated)
title - A title or heading
to - The ending point in a period of time
uri - A Uniform Resource Indicator (Deprecated)
url - A Uniform Resource Locator
ward - A name of a division of a city, town, or county
year - A year
zip - A zip code
II. XSL Parameter Reference
address.format - controls default formatting of the address element
css.href - indicates the CSS stylesheet to use to format HTML output
header.format - controls formatting of the header element
interest.description.format - controls formatting of interest descriptions
referees.display - Determines whether or not referees are visible in formatted - output
skills.format - controls formatting of the skillset element
skills.level.display - Determines whether or not skill level attributes are visible in - formatted output
subjects.format - controls formatting of the subjects element
3. CSS Class Reference
Overview
Glossary
III. Appendixes
A. GNU Free Documentation License
PREAMBLE
APPLICABILITY AND DEFINITIONS
VERBATIM COPYING
COPYING IN QUANTITY
MODIFICATIONS
COMBINING DOCUMENTS
COLLECTIONS OF DOCUMENTS
AGGREGATION WITH INDEPENDENT WORKS
TRANSLATION
TERMINATION
FUTURE REVISIONS OF THIS LICENSE
How to use this License for your documents
   IntroductionNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/intro.html b/legacy-resumes/resume-1/doc/manual/html/intro.html deleted file mode 100644 index 757a9af..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/intro.html +++ /dev/null @@ -1,22 +0,0 @@ - - - Introduction

XMLRésuméLibrary: - User Guide

PreviousXML Résumé Library User Guide UpXML Résumé Library User Guide Part I. Getting StartedNext

Introduction

What is the XML Résumé Library?

What is the XML Résumé Library?

- 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. -

-

PreviousXML Résumé Library User Guide UpXML Résumé Library User Guide Part I. Getting StartedNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/manual.css b/legacy-resumes/resume-1/doc/manual/html/manual.css deleted file mode 100644 index 6683186..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/manual.css +++ /dev/null @@ -1,60 +0,0 @@ -/* ------------------------------------------------------------------------- */ -/* This part stolen from XML Resume web site's site.css */ -/* ------------------------------------------------------------------------- */ -body, p, ul, td, th, h1, h2, h3, h4, input, textarea { - font-family: Verdana, Tahoma, Arial, Helvetica, sans-serif; -} - -body, p, ul, td, th { - font-size: 90%; -} - -body { margin: 30pt 30pt 20pt 30pt } - -code, pre, tt { - font-family: Lucida Console, Courier New, Courier, monospace; - font-size: 100%; -} - -h1, h2, h3, h4 { - font-weight: bold; - color: #000066; -} -h1 { font-size: 140% } -h2 { font-size: 125% } -h3 { font-size: 110% } -h4 { font-size: 100% } - -h1.pageTitle { - margin-top: 10pt; - font-size: x-large; - font-weight: normal; - border-bottom: 1px solid black; -} -.pageTitle a { - text-decoration: none; - color: #000066; -} -/* ------------------------------------------------------------------------- */ - -/* ------------------------------------------------------------------------- */ -/* Customizations for the manual */ -/* ------------------------------------------------------------------------- */ -.note, .important, .warning, .caution, .tip { - border: 1px solid black; - padding: 0.1in; -} - -hr, .navheader { - background-color: rgb(90%, 90%, 90%); - border: 1px solid rgb(75%,75%,75%); -} - -.important {background-color: #add8e6;} /* LightBlue */ -.warning {background-color: #f08080;} /* LightCoral */ -.caution {background-color: #ffd700;} /* Gold */ -.tip {background-color: #90ee90;} /* LightGreen */ -.note {background-color: #fafad2;} /* LightGoldenrodYellow */ - -.programlisting {background-color: rgb(90%, 90%, 90%)} -.informalexample {background-color: #ffcc66} diff --git a/legacy-resumes/resume-1/doc/manual/html/param.address.format.html b/legacy-resumes/resume-1/doc/manual/html/param.address.format.html deleted file mode 100644 index 409272a..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/param.address.format.html +++ /dev/null @@ -1,50 +0,0 @@ - - - address.format

XMLRésuméLibrary: - User Guide

PreviousXSL Parameter Reference UpXSL Parameter Reference css.hrefNext

Name

address.format — controls default formatting of the address element

Applies To

- This parameter controls the formatting of the address element in all output - formats. -

Possible Values

- Possible values include standard (the default), - european, and italian. -

Note

- 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. -

standard

- Formats addresses in North American layout: - -

<street>
-<street2>
-<suburb | ward>
-<city>, <state | province | county > <zip | postalCode>
-<country>

- -

european

- Formats addresses in European layout: - -

<street>
-<street2>
-<suburb | ward>
-<zip | postalCode> <city>, <state | province | county > <country>

-

italian

- 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&eacute;ctor Garc&iacute;a Mariz&oacute;
-Reina #35, apt. 4a, e/ Gervasio y Escobar
-Ciudad de La Habana, CP 11900
-CUBA</address>

- -

PreviousXSL Parameter Reference UpXSL Parameter Reference css.hrefNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/param.css.href.html b/legacy-resumes/resume-1/doc/manual/html/param.css.href.html deleted file mode 100644 index 98dc134..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/param.css.href.html +++ /dev/null @@ -1,13 +0,0 @@ - - - css.href

XMLRésuméLibrary: - User Guide

Previousaddress.format UpXSL Parameter Reference header.formatNext

Name

css.href — indicates the CSS stylesheet to use to format HTML output

Applies To

- This parameter applies to only the HTML output format. -

Possible Values

- 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. -

Previousaddress.format UpXSL Parameter Reference header.formatNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/param.header.format.html b/legacy-resumes/resume-1/doc/manual/html/param.header.format.html deleted file mode 100644 index 4a17bc9..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/param.header.format.html +++ /dev/null @@ -1,38 +0,0 @@ - - - header.format

XMLRésuméLibrary: - User Guide

Previouscss.href UpXSL Parameter Reference interest.description.formatNext

Name

header.format — controls formatting of the header element

Applies To

- 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

- Possible values include standard (the default) and - centered. -

standard

- 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. -

centered

- 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/

Previouscss.href UpXSL Parameter Reference interest.description.formatNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/param.interest.description.format.html b/legacy-resumes/resume-1/doc/manual/html/param.interest.description.format.html deleted file mode 100644 index 738057c..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/param.interest.description.format.html +++ /dev/null @@ -1,59 +0,0 @@ - - - interest.description.format

XMLRésuméLibrary: - User Guide

Previousheader.format UpXSL Parameter Reference referees.displayNext

Name

interest.description.format — controls formatting of interest descriptions

Applies To

- This parameter controls the formatting of the description element when it is contained - in an interest. It affects all output formats. -

Possible Values

- Possible values include single-line and - block. single-line is the default. -

- The examples below demonstrate the formatting of this XML fragment: - - 

<interests>
-  <interest>
-    <title>Scuba diving</title>
-  </interest>
-  <interest>
-    <title>Flying</title>
-    <description>
-      <para>I have my pilot's license, and have logged over 1000 in-flight
-      hours.</para>
-      <para>I have also constructed my own airplane from a kit.</para>
-    </description>
-  </interest>
-</interests>

-

single-line

- This value is the default. Formats all of the para elements in the description on - the same logical line as the interest title. The title is separated - from the description by a period, and the description paragraphs are - separated from each other by - description.para.separator.text, which - defaults to an em-dash (“—”). -

- - For example, the XML above would be formatted similar to the - following: - -

Interests

  • Scuba diving

  • - Flying. I have my pilot's license, and have logged over 1000 - in-flight hours. — I have also constructed my own - airplane from a kit. -

- -

block

- Formats each of the para elements - in the description as a separate block below the interest title. -

- - For example, the XML above would be formatted similar to the - following: - -

Interests

  • 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. -

- -

Previousheader.format UpXSL Parameter Reference referees.displayNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/param.referees.display.html b/legacy-resumes/resume-1/doc/manual/html/param.referees.display.html deleted file mode 100644 index d8784ec..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/param.referees.display.html +++ /dev/null @@ -1,17 +0,0 @@ - - - referees.display

XMLRésuméLibrary: - User Guide

Previousinterest.description.format UpXSL Parameter Reference skills.formatNext

Name

referees.display — Determines whether or not referees are visible in formatted - output

Applies To

- This parameter controls the formatting of the referee - element in all output formats. -

Possible Values

- Possible values include 1 (display referees) and - 0 (display alternate text). -

1 (true)

- Referees are displayed in formatted output. -

0 (false)

- The text of the referees.hidden.phrase - parameter (default: Available upon request.) is - displayed in place of referees. -

Previousinterest.description.format UpXSL Parameter Reference skills.formatNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/param.skills.format.html b/legacy-resumes/resume-1/doc/manual/html/param.skills.format.html deleted file mode 100644 index 3f2ec7c..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/param.skills.format.html +++ /dev/null @@ -1,36 +0,0 @@ - - - skills.format

XMLRésuméLibrary: - User Guide

Previousreferees.display UpXSL Parameter Reference skills.level.displayNext

Name

skills.format — controls formatting of the skillset element

Applies To

- This parameter controls the formatting of the skillset element in all output - formats. -

Possible Values

- 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>

- -

bullet

- Formats skills as a bulleted list, one skill per line: - -

Technical Skills

Programming Languages

  • Java

  • C++

  • C

  • Perl

- -

comma

- Produces a comma-separated list on a single line: - -

Technical Skills

- Programming Languages: Java, C++, C, Perl -

-

Previousreferees.display UpXSL Parameter Reference skills.level.displayNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/param.skills.level.display.html b/legacy-resumes/resume-1/doc/manual/html/param.skills.level.display.html deleted file mode 100644 index 4cac196..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/param.skills.level.display.html +++ /dev/null @@ -1,21 +0,0 @@ - - - skills.level.display

XMLRésuméLibrary: - User Guide

Previousskills.format UpXSL Parameter Reference subjects.formatNext

Name

skills.level.display — Determines whether or not skill level attributes are visible in - formatted output

Applies To

- This parameter controls the formatting of the level attribute of skill - elements in all output formats. -

Possible Values

- Possible values include 1 (display the attribute) or - 0 (suppress the attribute). -

1 (true)

- level attributes of - skills are displayed after all of - the rest of the content of the skill. The level is displayed - surrounded by skills.level.start and - skills.level.end (parenthesis, by default). -

0 (false)

- level attributes contained in - skills are suppressed; they are - treated as if the didn't exist for formatting purposes. -

Previousskills.format UpXSL Parameter Reference subjects.formatNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/param.subjects.format.html b/legacy-resumes/resume-1/doc/manual/html/param.subjects.format.html deleted file mode 100644 index f39a59d..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/param.subjects.format.html +++ /dev/null @@ -1,37 +0,0 @@ - - - subjects.format

XMLRésuméLibrary: - User Guide

Previousskills.level.display UpXSL Parameter Reference CSS Class ReferenceNext

Name

subjects.format — controls formatting of the subjects element

Applies To

- This parameter controls the formatting of the subjects element in all output formats. -

Possible Values

- 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>

- -

comma

- Produces a comma-separated list on a single line: - -

- Subjects: English (C), Science (A), Math (B-). -

-

table

- Produces a table, with subject name in the first column and result - in the second column: -

Subjects

EnglishC
ScienceA
MathB-
Previousskills.level.display UpXSL Parameter Reference CSS Class ReferenceNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/paramref.html b/legacy-resumes/resume-1/doc/manual/html/paramref.html deleted file mode 100644 index 05935ab..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/paramref.html +++ /dev/null @@ -1,12 +0,0 @@ - - - XSL Parameter Reference

XMLRésuméLibrary: - User Guide

Previouszip UpPart II. Reference address.formatNext

XSL Parameter Reference

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
css.href - indicates the CSS stylesheet to use to format HTML output
header.format - controls formatting of the header element
interest.description.format - controls formatting of interest descriptions
referees.display - Determines whether or not referees are visible in formatted - output
skills.format - controls formatting of the skillset element
skills.level.display - Determines whether or not skill level attributes are visible in - formatted output
subjects.format - controls formatting of the subjects element
Previouszip UpPart II. Reference address.formatNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/html/ref.html b/legacy-resumes/resume-1/doc/manual/html/ref.html deleted file mode 100644 index c7628f0..0000000 --- a/legacy-resumes/resume-1/doc/manual/html/ref.html +++ /dev/null @@ -1,6 +0,0 @@ - - - Part II. Reference

XMLRésuméLibrary: - User Guide

PreviousAbout this chapter UpXML Résumé Library User Guide Element ReferenceNext

Reference

Table of Contents

I. Element Reference
academics - Container for information about academic experience
achievement - An accomplishment made at a job
achievements - Container for one or more job achievements
address - A postal address
annotation - Additional information about a degree
artTitle - A title of an article or other work
author - An author of a publication
award - An award or other honor
awards - Container for one or more awards
birth - Container for information about a person's birth
bookTitle - A title of a book or similar work
break - A linebreak (Deprecated)
citation - The name of a work being referenced
city - The name of a city
clearance - A security clearance
clearances - One or more security clearances
company - The name of a company (Deprecated)
contact - Container for one or more methods of contacting someone
copyright - A copyright notice
country - A country name
county - A county name
date - A specific instant in time
dayOfMonth - An ordinal day of the month
degree - Container for information about a degree or similar certification
degrees - Container for one or more degrees
description - An explanation of something
docpath - (Deprecated)
email - An e-mail address
emphasis - An emphasized block of text
employer - A name of an employer
fax - A fax telephone number
firstname - A person's given name
from - The beginning point in a period of time
gpa - Information about a grade point average
head - (Deprecated)
header - Container for information about the person being described in a résumé
history - Container for a person's previous (and possibly current) jobs
instantMessage - An instant message username or address
institution - A name of an academic institution
interest - Something a person is interested in
interests - Container for one or more interests
job - A specific employment engagement
jobtitle - A job title
keyword - A keyword to be used for résumé indexing and searching
keywords - Container for a list of keywords
label - (Deprecated)
lastModified - Information about when a résumé was last modified
legalnotice - A legal statement
level - A degree type
link - A titled hyperlink
location - A location, with city-level granularity
major - A main course of study
membership - A professional membership
memberships - Container for one or more memberships
middlenames - One or more middle names of a person
minor - A minor course of study
misc - Miscellaneous remarks
month - A month name
name - A person's name
node - (Deprecated)
note - Additional information
objective - A person's employment goal
organization - A name of an organization
pageNums - One or more page numbers or ranges
pager - A pager telephone number
para - A paragraph of text
period - A period of time
phone - A voice telephone number
possible - The highest possible score in a GPA
postalCode - A postal code
prefecture - A name of a prefecture or other administrative district
present - Indicates the current time
project - Container for information about a project
projects - Container for one or more projects
province - A name or abbreviation of a province
pub - A work published by the résumé owner
pubDate - The date a work was published (Deprecated)
publisher - Information about a publisher of a work
pubs - A group of one or more publications
referee - Someone who can provide additional information about the person the résumé describes
referees - Contains one or more referees
result - An outcome of a subject
resume - A résumé or curriculum vitae
resumes - A collection of one or more résumés
score - The score earned in a GPA
skill - A name and/or description of a skill
skillarea - A group of broadly related skill sets
skillareas - Group of one or more skill areas (Deprecated)
skills - Group of one or more skills (Deprecated)
skillset - A titled group of one or more related skills
state - A name or abbreviation of a state
street - A street name, number, and other related information
street2 - A second line of a street address (Deprecated)
subject - A name of a class or topic of study
subjects - A group of one or more subjects
suburb - A name of a suburb
suffix - A suffix of a name, usually specifying lineage
surname - A family name
tail - (Deprecated)
title - A title or heading
to - The ending point in a period of time
uri - A Uniform Resource Indicator (Deprecated)
url - A Uniform Resource Locator
ward - A name of a division of a city, town, or county
year - A year
zip - A zip code
II. XSL Parameter Reference
address.format - controls default formatting of the address element
css.href - indicates the CSS stylesheet to use to format HTML output
header.format - controls formatting of the header element
interest.description.format - controls formatting of interest descriptions
referees.display - Determines whether or not referees are visible in formatted - output
skills.format - controls formatting of the skillset element
skills.level.display - Determines whether or not skill level attributes are visible in - formatted output
subjects.format - controls formatting of the subjects element
3. CSS Class Reference
Overview
PreviousAbout this chapter UpXML Résumé Library User Guide Element ReferenceNext
\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/manual.css b/legacy-resumes/resume-1/doc/manual/manual.css deleted file mode 100644 index 6683186..0000000 --- a/legacy-resumes/resume-1/doc/manual/manual.css +++ /dev/null @@ -1,60 +0,0 @@ -/* ------------------------------------------------------------------------- */ -/* This part stolen from XML Resume web site's site.css */ -/* ------------------------------------------------------------------------- */ -body, p, ul, td, th, h1, h2, h3, h4, input, textarea { - font-family: Verdana, Tahoma, Arial, Helvetica, sans-serif; -} - -body, p, ul, td, th { - font-size: 90%; -} - -body { margin: 30pt 30pt 20pt 30pt } - -code, pre, tt { - font-family: Lucida Console, Courier New, Courier, monospace; - font-size: 100%; -} - -h1, h2, h3, h4 { - font-weight: bold; - color: #000066; -} -h1 { font-size: 140% } -h2 { font-size: 125% } -h3 { font-size: 110% } -h4 { font-size: 100% } - -h1.pageTitle { - margin-top: 10pt; - font-size: x-large; - font-weight: normal; - border-bottom: 1px solid black; -} -.pageTitle a { - text-decoration: none; - color: #000066; -} -/* ------------------------------------------------------------------------- */ - -/* ------------------------------------------------------------------------- */ -/* Customizations for the manual */ -/* ------------------------------------------------------------------------- */ -.note, .important, .warning, .caution, .tip { - border: 1px solid black; - padding: 0.1in; -} - -hr, .navheader { - background-color: rgb(90%, 90%, 90%); - border: 1px solid rgb(75%,75%,75%); -} - -.important {background-color: #add8e6;} /* LightBlue */ -.warning {background-color: #f08080;} /* LightCoral */ -.caution {background-color: #ffd700;} /* Gold */ -.tip {background-color: #90ee90;} /* LightGreen */ -.note {background-color: #fafad2;} /* LightGoldenrodYellow */ - -.programlisting {background-color: rgb(90%, 90%, 90%)} -.informalexample {background-color: #ffcc66} diff --git a/legacy-resumes/resume-1/doc/manual/manual.html b/legacy-resumes/resume-1/doc/manual/manual.html deleted file mode 100644 index cd87b1a..0000000 --- a/legacy-resumes/resume-1/doc/manual/manual.html +++ /dev/null @@ -1,3664 +0,0 @@ - - - XML Résumé Library User Guide

XML Résumé Library User Guide

For XML Résumé Library Version 1.5.1

Bruce Christensen

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

Introduction
What is the XML Résumé Library?
I. Getting Started
1. Setting up the XML Résumé Library
Prerequisites
Getting the Software
Installing and Configuring the Software
2. Exploring the Features of XML Résumé Library
Formatting an example resume
Advanced Features of the XML Résumé Library
Writing your first XML Résumé
Where to Go from Here
About this chapter
II. Reference
I. Element Reference
academics - Container for information about academic experience
achievement - An accomplishment made at a job
achievements - Container for one or more job achievements
address - A postal address
annotation - Additional information about a degree
artTitle - A title of an article or other work
author - An author of a publication
award - An award or other honor
awards - Container for one or more awards
birth - Container for information about a person's birth
bookTitle - A title of a book or similar work
break - A linebreak (Deprecated)
citation - The name of a work being referenced
city - The name of a city
clearance - A security clearance
clearances - One or more security clearances
company - The name of a company (Deprecated)
contact - Container for one or more methods of contacting someone
copyright - A copyright notice
country - A country name
county - A county name
date - A specific instant in time
dayOfMonth - An ordinal day of the month
degree - Container for information about a degree or similar certification
degrees - Container for one or more degrees
description - An explanation of something
docpath - (Deprecated)
email - An e-mail address
emphasis - An emphasized block of text
employer - A name of an employer
fax - A fax telephone number
firstname - A person's given name
from - The beginning point in a period of time
gpa - Information about a grade point average
head - (Deprecated)
header - Container for information about the person being described in a résumé
history - Container for a person's previous (and possibly current) jobs
instantMessage - An instant message username or address
institution - A name of an academic institution
interest - Something a person is interested in
interests - Container for one or more interests
job - A specific employment engagement
jobtitle - A job title
keyword - A keyword to be used for résumé indexing and searching
keywords - Container for a list of keywords
label - (Deprecated)
lastModified - Information about when a résumé was last modified
legalnotice - A legal statement
level - A degree type
link - A titled hyperlink
location - A location, with city-level granularity
major - A main course of study
membership - A professional membership
memberships - Container for one or more memberships
middlenames - One or more middle names of a person
minor - A minor course of study
misc - Miscellaneous remarks
month - A month name
name - A person's name
node - (Deprecated)
note - Additional information
objective - A person's employment goal
organization - A name of an organization
pageNums - One or more page numbers or ranges
pager - A pager telephone number
para - A paragraph of text
period - A period of time
phone - A voice telephone number
possible - The highest possible score in a GPA
postalCode - A postal code
prefecture - A name of a prefecture or other administrative district
present - Indicates the current time
project - Container for information about a project
projects - Container for one or more projects
province - A name or abbreviation of a province
pub - A work published by the résumé owner
pubDate - The date a work was published (Deprecated)
publisher - Information about a publisher of a work
pubs - A group of one or more publications
referee - Someone who can provide additional information about the person the résumé describes
referees - Contains one or more referees
result - An outcome of a subject
resume - A résumé or curriculum vitae
resumes - A collection of one or more résumés
score - The score earned in a GPA
skill - A name and/or description of a skill
skillarea - A group of broadly related skill sets
skillareas - Group of one or more skill areas (Deprecated)
skills - Group of one or more skills (Deprecated)
skillset - A titled group of one or more related skills
state - A name or abbreviation of a state
street - A street name, number, and other related information
street2 - A second line of a street address (Deprecated)
subject - A name of a class or topic of study
subjects - A group of one or more subjects
suburb - A name of a suburb
suffix - A suffix of a name, usually specifying lineage
surname - A family name
tail - (Deprecated)
title - A title or heading
to - The ending point in a period of time
uri - A Uniform Resource Indicator (Deprecated)
url - A Uniform Resource Locator
ward - A name of a division of a city, town, or county
year - A year
zip - A zip code
II. XSL Parameter Reference
address.format - controls default formatting of the address element
css.href - indicates the CSS stylesheet to use to format HTML output
header.format - controls formatting of the header element
interest.description.format - controls formatting of interest descriptions
referees.display - Determines whether or not referees are visible in formatted - output
skills.format - controls formatting of the skillset element
skills.level.display - Determines whether or not skill level attributes are visible in - formatted output
subjects.format - controls formatting of the subjects element
3. CSS Class Reference
Overview
Glossary
III. Appendixes
A. GNU Free Documentation License
PREAMBLE
APPLICABILITY AND DEFINITIONS
VERBATIM COPYING
COPYING IN QUANTITY
MODIFICATIONS
COMBINING DOCUMENTS
COLLECTIONS OF DOCUMENTS
AGGREGATION WITH INDEPENDENT WORKS
TRANSLATION
TERMINATION
FUTURE REVISIONS OF THIS LICENSE
How to use this License for your documents

Introduction

Table of Contents

What is the XML Résumé Library?

What is the XML Résumé Library?

- 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. -

-

Getting Started

Table of Contents

1. Setting up the XML Résumé Library
Prerequisites
Getting the Software
Installing and Configuring the Software
2. Exploring the Features of XML Résumé Library
Formatting an example resume
Advanced Features of the XML Résumé Library
Writing your first XML Résumé
Where to Go from Here
About this chapter

Setting up the XML Résumé Library

Peter Hutnick

Edited by

Bruce Christensen

Mark Miller

Copyright © 2002 Peter Hutnick

Table of Contents

Prerequisites
Getting the Software
Installing and Configuring the Software

- 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. -

Prerequisites

Java

- 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. -

XML

- 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. -

Getting the Software

XML Résumé Library

- 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

- 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

- 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

- 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. -

Installing and Configuring the Software

XML Résumé Library

- 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. -

Tip

You can also indicate your résumé filename on the command line - when you build your résumé, e.g.: - - 

[resume]$ make resume=myresume

-

Note

- 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">

- -

Xerces, Xalan, and FOP

- 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. -

Exploring the Features of XML Résumé Library

Peter Hutnick

Mark Miller

Edited by

Bruce Christensen

Copyright © 2002 Peter Hutnick

Table of Contents

Formatting an example resume
Advanced Features of the XML Résumé Library
Writing your first XML Résumé
Where to Go from Here
About this chapter

- 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. -

Formatting an example resume

Converting to other formats

- 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é. -

Advanced Features of the XML Résumé Library

Filtering to target your resume

- 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. -

Customizing your résumé

- With just a few tweaks, you can dramatically change the look - of your résumés. -

Modifying the XSL Parameters

- 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. -

Note

- 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. -

Modifying the look of your HTML Résumé

- 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. -

Writing your first XML Résumé

- 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. -

Where to Go from Here

Documentation

- 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. -

Support

- 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>. -

About this chapter

- 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>. -

Reference

Table of Contents

I. Element Reference
academics - Container for information about academic experience
achievement - An accomplishment made at a job
achievements - Container for one or more job achievements
address - A postal address
annotation - Additional information about a degree
artTitle - A title of an article or other work
author - An author of a publication
award - An award or other honor
awards - Container for one or more awards
birth - Container for information about a person's birth
bookTitle - A title of a book or similar work
break - A linebreak (Deprecated)
citation - The name of a work being referenced
city - The name of a city
clearance - A security clearance
clearances - One or more security clearances
company - The name of a company (Deprecated)
contact - Container for one or more methods of contacting someone
copyright - A copyright notice
country - A country name
county - A county name
date - A specific instant in time
dayOfMonth - An ordinal day of the month
degree - Container for information about a degree or similar certification
degrees - Container for one or more degrees
description - An explanation of something
docpath - (Deprecated)
email - An e-mail address
emphasis - An emphasized block of text
employer - A name of an employer
fax - A fax telephone number
firstname - A person's given name
from - The beginning point in a period of time
gpa - Information about a grade point average
head - (Deprecated)
header - Container for information about the person being described in a résumé
history - Container for a person's previous (and possibly current) jobs
instantMessage - An instant message username or address
institution - A name of an academic institution
interest - Something a person is interested in
interests - Container for one or more interests
job - A specific employment engagement
jobtitle - A job title
keyword - A keyword to be used for résumé indexing and searching
keywords - Container for a list of keywords
label - (Deprecated)
lastModified - Information about when a résumé was last modified
legalnotice - A legal statement
level - A degree type
link - A titled hyperlink
location - A location, with city-level granularity
major - A main course of study
membership - A professional membership
memberships - Container for one or more memberships
middlenames - One or more middle names of a person
minor - A minor course of study
misc - Miscellaneous remarks
month - A month name
name - A person's name
node - (Deprecated)
note - Additional information
objective - A person's employment goal
organization - A name of an organization
pageNums - One or more page numbers or ranges
pager - A pager telephone number
para - A paragraph of text
period - A period of time
phone - A voice telephone number
possible - The highest possible score in a GPA
postalCode - A postal code
prefecture - A name of a prefecture or other administrative district
present - Indicates the current time
project - Container for information about a project
projects - Container for one or more projects
province - A name or abbreviation of a province
pub - A work published by the résumé owner
pubDate - The date a work was published (Deprecated)
publisher - Information about a publisher of a work
pubs - A group of one or more publications
referee - Someone who can provide additional information about the person the résumé describes
referees - Contains one or more referees
result - An outcome of a subject
resume - A résumé or curriculum vitae
resumes - A collection of one or more résumés
score - The score earned in a GPA
skill - A name and/or description of a skill
skillarea - A group of broadly related skill sets
skillareas - Group of one or more skill areas (Deprecated)
skills - Group of one or more skills (Deprecated)
skillset - A titled group of one or more related skills
state - A name or abbreviation of a state
street - A street name, number, and other related information
street2 - A second line of a street address (Deprecated)
subject - A name of a class or topic of study
subjects - A group of one or more subjects
suburb - A name of a suburb
suffix - A suffix of a name, usually specifying lineage
surname - A family name
tail - (Deprecated)
title - A title or heading
to - The ending point in a period of time
uri - A Uniform Resource Indicator (Deprecated)
url - A Uniform Resource Locator
ward - A name of a division of a city, town, or county
year - A year
zip - A zip code
II. XSL Parameter Reference
address.format - controls default formatting of the address element
css.href - indicates the CSS stylesheet to use to format HTML output
header.format - controls formatting of the header element
interest.description.format - controls formatting of interest descriptions
referees.display - Determines whether or not referees are visible in formatted - output
skills.format - controls formatting of the skillset element
skills.level.display - Determines whether or not skill level attributes are visible in - formatted output
subjects.format - controls formatting of the subjects element
3. CSS Class Reference
Overview

Element Reference

- 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. -

Changes to the DTD

- This sections documents changes to the XML Résumé Library DTD. -

Warning

- 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. -

Version ???

  • - Changed elements: - projects - may now be included in the - degree - element. -

Version 1.5.0

  • - 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. -

Version 1.4.2

- No DTD changes. -

Version 1.4.1

Version 1.4.0

  • - New element: minor. -

  • - New element: lastModified. -

  • - New elements: awards and - award. -

  • - New elements: interests and - interest. -

  • - 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. -

Version 1.3.3

  • - 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. -

Version 1.3.2

- No DTD changes. -

Table of Contents

academics - Container for information about academic experience
achievement - An accomplishment made at a job
achievements - Container for one or more job achievements
address - A postal address
annotation - Additional information about a degree
artTitle - A title of an article or other work
author - An author of a publication
award - An award or other honor
awards - Container for one or more awards
birth - Container for information about a person's birth
bookTitle - A title of a book or similar work
break - A linebreak (Deprecated)
citation - The name of a work being referenced
city - The name of a city
clearance - A security clearance
clearances - One or more security clearances
company - The name of a company (Deprecated)
contact - Container for one or more methods of contacting someone
copyright - A copyright notice
country - A country name
county - A county name
date - A specific instant in time
dayOfMonth - An ordinal day of the month
degree - Container for information about a degree or similar certification
degrees - Container for one or more degrees
description - An explanation of something
docpath - (Deprecated)
email - An e-mail address
emphasis - An emphasized block of text
employer - A name of an employer
fax - A fax telephone number
firstname - A person's given name
from - The beginning point in a period of time
gpa - Information about a grade point average
head - (Deprecated)
header - Container for information about the person being described in a résumé
history - Container for a person's previous (and possibly current) jobs
instantMessage - An instant message username or address
institution - A name of an academic institution
interest - Something a person is interested in
interests - Container for one or more interests
job - A specific employment engagement
jobtitle - A job title
keyword - A keyword to be used for résumé indexing and searching
keywords - Container for a list of keywords
label - (Deprecated)
lastModified - Information about when a résumé was last modified
legalnotice - A legal statement
level - A degree type
link - A titled hyperlink
location - A location, with city-level granularity
major - A main course of study
membership - A professional membership
memberships - Container for one or more memberships
middlenames - One or more middle names of a person
minor - A minor course of study
misc - Miscellaneous remarks
month - A month name
name - A person's name
node - (Deprecated)
note - Additional information
objective - A person's employment goal
organization - A name of an organization
pageNums - One or more page numbers or ranges
pager - A pager telephone number
para - A paragraph of text
period - A period of time
phone - A voice telephone number
possible - The highest possible score in a GPA
postalCode - A postal code
prefecture - A name of a prefecture or other administrative district
present - Indicates the current time
project - Container for information about a project
projects - Container for one or more projects
province - A name or abbreviation of a province
pub - A work published by the résumé owner
pubDate - The date a work was published (Deprecated)
publisher - Information about a publisher of a work
pubs - A group of one or more publications
referee - Someone who can provide additional information about the person the résumé describes
referees - Contains one or more referees
result - An outcome of a subject
resume - A résumé or curriculum vitae
resumes - A collection of one or more résumés
score - The score earned in a GPA
skill - A name and/or description of a skill
skillarea - A group of broadly related skill sets
skillareas - Group of one or more skill areas (Deprecated)
skills - Group of one or more skills (Deprecated)
skillset - A titled group of one or more related skills
state - A name or abbreviation of a state
street - A street name, number, and other related information
street2 - A second line of a street address (Deprecated)
subject - A name of a class or topic of study
subjects - A group of one or more subjects
suburb - A name of a suburb
suffix - A suffix of a name, usually specifying lineage
surname - A family name
tail - (Deprecated)
title - A title or heading
to - The ending point in a period of time
uri - A Uniform Resource Indicator (Deprecated)
url - A Uniform Resource Locator
ward - A name of a division of a city, town, or county
year - A year
zip - A zip code

Name

academics — Container for information about academic experience

Synopsis

Content Model

(degrees,note?)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The academics element contains - information about a person's academic experience. -

Parents

- academics may be contained in these - elements: - resume -

See Also

- pubs, memberships. -

Examples

<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>

Name

achievement — An accomplishment made at a job

Synopsis

Content Model

(#PCDATA|emphasis|citation|url|link)*

Attributes

NameTypeDefault
targetsCDATANone

Description

- The achievment element contains a - single accomplishment made while working at a particular job (e.g. - “increased sales by 20%”, or “improved employee - efficiency”). -

Parents

- achievement may be contained in these - elements: - achievements -

Examples

<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>

Name

achievements — Container for one or more job achievements

Synopsis

Content Model

(achievement+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- achievements is a wrapper element - that contains one or more achievement elements. Achievements are - specific things that were accomplished at a job. -

Parents

- achievements may be contained in these - elements: - job -

Examples

- For examples, see achievement. -

Name

address — A postal address

Synopsis

Content Model

(#PCDATA|street|street2|suburb|ward|city|state|province|county|prefecture|zip|postalCode|country|break)*

Attributes

NameTypeDefault
format

Enumeration:

standard
european
italian
None
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- address may be contained in these - elements: - header, referee -

Attributes

id

- A string used to uniquely identify an address. The address may - then be referred to by this identifier. -

format

- The address format. This attribute specifies the format of an - address, and overrides the global address.format - parameter for each address that it appears in. -

See Also

- address.format. -

Examples

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

Warning

- 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. -

Name

annotation — Additional information about a degree

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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”). -

Parents

- annotation may be contained in these - elements: - degree -

Examples

<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>

Name

artTitle — A title of an article or other work

Synopsis

Content Model

(#PCDATA|link)*

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- artTitle may be contained in these - elements: - pub -

See Also

- bookTitle. -

Examples

<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>

Name

author — An author of a publication

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
nameIDREFNone
targetsCDATANone

Description

- 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. -

Parents

- author may be contained in these - elements: - pub -

Attributes

name

- The name attribute contains - the id of a name element. -

- If an author element - specifies this attribute, it should not have any content. In - other words, there should be a single tag with a reference - (<author name="joe.smith"/>) - instead of two tags enclosing content - (<author>Joe Smith</author>). -

See Also

- name. -

Examples

<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>

Name

award — An award or other honor

Synopsis

Content Model

(title,organization?,(date|period)?,description?)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The award element describes - an award or other honor received by a person (e.g. “Nobel - Prize”, “MacArthur Fellow”). -

Parents

- award may be contained in these - elements: - awards -

Examples

<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>

Name

awards — Container for one or more awards

Synopsis

Content Model

(title?,award+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The awards element contains one or more - awards. -

Parents

- awards may be contained in these - elements: - resume -

Examples

<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>

Name

birth — Container for information about a person's birth

Synopsis

Content Model

(date)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The birth element contains a single - date that specifies when a person was - born. -

Parents

- birth may be contained in these - elements: - header -

Examples

<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>

Name

bookTitle — A title of a book or similar work

Synopsis

Content Model

(#PCDATA|link)*

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- bookTitle may be contained in these - elements: - pub -

See Also

- artTitle. -

Examples

<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>

Name

break — A linebreak

Deprecated

Synopsis

Content Model

EMPTY

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

Parents

- break may be contained in these - elements: - address -

Examples

- None. -

Name

citation — The name of a work being referenced

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The citation element marks the title - of a book, website, course, or other work. -

Parents

- citation may be contained in these - elements: - achievement, employer, institution, organization, para, project, skill -

See Also

- pub. -

Examples

<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>

Name

city — The name of a city

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The city element contains a the name - of a single city or other similar municipality. -

Parents

- city may be contained in these - elements: - address, location -

Attributes

id

- A string used to uniquely identify a city. The city may - then be referred to by this identifier. -

See Also

- county, prefecture, suburb, ward. -

Examples

<address>
-  <street>3400 N. 5230 S.</street>
-  <city>Salt Lake City</city>
-  <state>UT</state>
-  <zip>84352</zip>
-</address>

Name

clearance — A security clearance

Synopsis

Content Model

(level,organization?,(date|period)?,note?)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The clearance element contains a single - security clearance (e.g. “Top Secret”). -

Parents

- clearance may be contained in these - elements: - clearances -

Examples

<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>

Name

clearances — One or more security clearances

Synopsis

Content Model

(title?,clearance+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The clearances element contains one or - more security clearances. It is a top-level section of a résumé. -

Parents

- clearances may be contained in these - elements: - resume -

Examples

<clearances>
-  <clearance>
-    <level>Top Secret</level>
-    <organization>NSA</organization>
-  </clearance>
-  <clearance>
-    <level>Secret</level>
-    <organization>US Navy</organization>
-  </clearance>
-</clearances>

Name

company — The name of a company

Deprecated

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- This element is deprecated as of XML Résumé Library version 1.3.3. It should - not be used. -

Parents

- company may be contained in these - elements: - None -

See Also

- institution, organization. -

Examples

None.

Name

contact — Container for one or more methods of contacting someone

Synopsis

Content Model

(phone|fax|pager|email|url|instantMessage)*

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- contact may be contained in these - elements: - header, referee -

See Also

- address. -

Examples

<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>

Name

copyright — A copyright notice

Synopsis

Content Model

(year,name?,legalnotice?)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- copyright may be contained in these - elements: - resume -

Examples

<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>

Name

country — A country name

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The country element marks the name of - a country. -

Parents

- country may be contained in these - elements: - address, location -

Attributes

id

- A string used to uniquely identify a country. The country may - then be referred to by this identifier. -

Examples

<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>

Name

county — A county name

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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.) -

Parents

- county may be contained in these - elements: - address, location -

Attributes

id

- A string used to uniquely identify a county. The county may - then be referred to by this identifier. -

See Also

- state, province, prefecture. -

Examples

<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>

Name

date — A specific instant in time

Synopsis

Content Model

(((dayOfMonth)?,month)?,year)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Note

- 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. -

Parents

- date may be contained in these - elements: - award, birth, clearance, degree, from, job, lastModified, membership, pub, to -

See Also

- period. -

Examples

<date>
-  <dayOfMonth>27</dayOfMonth>
-  <month>November</month>
-  <year>1634</year>
-</date>
<date>
-  <month>July</month>
-  <year>1457</year>
-</date>

Name

dayOfMonth — An ordinal day of the month

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- Represents a specific day in a month. Its value is numeric; the first - day of the month is written 1, the fifteenth - 15, etc. -

Parents

- dayOfMonth may be contained in these - elements: - date -

Examples

- For examples, see date. -

Name

degree — Container for information about a degree or similar certification

Synopsis

Content Model

(level,annotation?,major*,minor*,(date|period)?,(institution,location?)?,gpa?,subjects?,projects?)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The degree element is a container for - information about an academic degree (Bachelor of Science, Doctor of - Psychology, etc.) or other similar certification. -

Parents

- degree may be contained in these - elements: - degrees -

Attributes

id

- A string used to uniquely identify a degree. The degree may - then be referred to by this identifier. -

Examples

<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>

Name

degrees — Container for one or more degrees

Synopsis

Content Model

(degree+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The degrees element is a container - for at least one degree. -

Parents

- degrees may be contained in these - elements: - academics -

Examples

<degrees>
-  <degree>
-    <level>BA</level>
-    <major>Interstellar Basket Weaving</major>
-  </degree>
-  <degree>
-    <level>Ph.D</level>
-    <major>Aquatic Tennis Teaching</major>
-  </degree>
-</degree>

Name

description — An explanation of something

Synopsis

Content Model

(para+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The description element specifies a - person's role, their activities, or other descriptive information. -

Parents

- description may be contained in these - elements: - award, interest, job, membership -

See Also

- projects, achievements. -

Examples

<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>

Name

docpath —

Deprecated

Synopsis

Content Model

(head?,node*,tail)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

- -

Parents

- docpath may be contained in these - elements: - resume -

Examples

<!-- TODO -->

Name

email — An e-mail address

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The email element specifies a single - e-mail address. -

Parents

- email may be contained in these - elements: - contact -

See Also

- fax, instantMessage, pager, url. -

Examples

<contact>
-  <email>john@johnny.bob</email>
-  <phone>555-555-1212</phone>
-</contact>

Name

emphasis — An emphasized block of text

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The emphasis element is an inline - element that indicates that the text it contains should be emphasized. -

Presentation

- The presentation of text contained in this element varies depending on - the output format. -

HTML

- 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

- 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. -

XSL-FO/PDF

- Rendered as bold text. -

Parents

- emphasis may be contained in these - elements: - achievement, employer, institution, organization, para, project, skill -

Examples

<para>
-  I really, really, <emphasis>really</emphasis> want a job.
-</para>
<skill>
-  I am <emphasis>extremely</emphasis> at using rocket-powered cheese graters.
-</skill>

Name

employer — A name of an employer

Synopsis

Content Model

(#PCDATA|emphasis|citation|url|link)*

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The employer element specifies the - name of a person, company, or other entity for whom a person works or - has worked. -

Parents

- employer may be contained in these - elements: - job -

Attributes

id

- A string used to uniquely identify an employer. The employer may - then be referred to by this identifier. -

See Also

- institution, organization. -

Examples

<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>

Name

fax — A fax telephone number

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
location

Enumeration:

home
work
None
targetsCDATANone

Description

- 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.) -

Parents

- fax may be contained in these - elements: - contact -

Attributes

location

- Indicates the location that the phone number connects to. This - attribute is optional. -

See Also

- email, pager, phone. -

Examples

<fax>555-555-1212</fax>
<fax location="work">(123) 456-7890</fax>
<fax location="home">345.324.2721</fax>

Name

firstname — A person's given name

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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”. -

Parents

- firstname may be contained in these - elements: - name -

See Also

- middlenames, surname. -

Examples

<name>
-  <firstname>Caroline</firstname>
-  <surname>Francisca</surname>
-</name>

Name

from — The beginning point in a period of time

Synopsis

Content Model

(date|present)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- from may be contained in these - elements: - period -

See Also

- to. -

Examples

<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>

Name

gpa — Information about a grade point average

Synopsis

Content Model

(score,possible?,note?)

Attributes

NameTypeDefault
targetsCDATANone
type

Enumeration:

overall
major
overall

Description

- 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.). -

Parents

- gpa may be contained in these - elements: - degree -

Attributes

type

- 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. -

Examples

<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>

Name

head —

Deprecated

Synopsis

Content Model

(label,uri)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

- -

Parents

- head may be contained in these - elements: - docpath -

Examples

<!-- TODO -->

Name

header — Container for information about the person being described in a résumé

Synopsis

Content Model

(name,address?,birth?,contact?)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Formatting

- The header.format - parameter influences the formatting of headers in all output formats. -

Parents

- header may be contained in these - elements: - resume -

See Also

- header.format. -

Examples

<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>

Name

history — Container for a person's previous (and possibly current) jobs

Synopsis

Content Model

(job+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- history may be contained in these - elements: - resume -

Examples

<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>

Name

instantMessage — An instant message username or address

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
serviceCDATANone
targetsCDATANone

Description

- 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. -

Parents

- instantMessage may be contained in these - elements: - contact -

Attributes

service

- Specifies the service that the username or address is to be used - with. Acceptable values are: -

aim

AOL Instant Messenger

icq

ICQ

irc

Internet Relay Chat

jabber

Jabber

msn

MSN Messenger

yahoo

Yahoo! Messenger

-

See Also

- email. -

Examples

<instantMessage service="yahoo">joesmith</instantMessage>
<instantMessage service="aim">janedoe</instantMessage>
<instantMessage service="jabber">sammybob@jabber.com</instantMessage>

Name

institution — A name of an academic institution

Synopsis

Content Model

(#PCDATA|emphasis|citation|url|link)*

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The institution element specifies the - name of a degree-awarding institution, such as a university, college, or - trade school. -

Parents

- institution may be contained in these - elements: - degree -

Attributes

id

- A string used to uniquely identify an institution. The - institution may then be referred to by this identifier. -

See Also

- organization. -

Examples

<degree>
-  <level>BA</level>
-  <major>Daisy Chain Manufacturing</major>
-  <institution>Harvard</institution>
-</degree>

Name

interest — Something a person is interested in

Synopsis

Content Model

(title,description?)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The interest element describes - something that a person is interested in. A common use for interest elements is to list hobbies. -

Formatting

- 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. -

Parents

- interest may be contained in these - elements: - interests -

See Also

- skill. -

Examples

<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. -

Name

interests — Container for one or more interests

Synopsis

Content Model

(title?,interest+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The interests element contains one or - more interest elements. -

Formatting

- 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. -

Parents

- interests may be contained in these - elements: - resume -

See Also

- skillarea. -

Examples

<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>

Name

job — A specific employment engagement

Synopsis

Content Model

(jobtitle,employer,location?,(date|period),description?,projects?,achievements?)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The job element describes a job, - contract, or other employment engagement. -

Parents

- job may be contained in these - elements: - history -

Attributes

id

- A string used to uniquely identify a job. The job may then be - referred to by this identifier. -

Examples

<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>

Name

jobtitle — A job title

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The jobtitle element specifies the - offical title or name of the position a person held at a job. -

Parents

- jobtitle may be contained in these - elements: - job -

Examples

- For examples, see job -

Name

keyword — A keyword to be used for résumé indexing and searching

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- keyword may be contained in these - elements: - keywords -

Examples

<keywords>
-  <keyword>forward-thinking</keyword>
-  <keyword>self-starter</keyword>
-  <keyword>independent</keyword>
-  <keyword>flexible</keyword>
-</keywords>

Name

keywords — Container for a list of keywords

Synopsis

Content Model

(keyword+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The keywords element contains one or - more keywords. These keywords are included in the HTML presentation as - <meta name="keywords" content="..."> - tags. -

Parents

- keywords may be contained in these - elements: - resume -

Examples

- For examples, see keyword. -

Name

label —

Deprecated

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

- -

Parents

- label may be contained in these - elements: - head, node -

Examples

<!-- TODO -->

Name

lastModified — Information about when a résumé was last modified

Synopsis

Content Model

(date)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The lastModified element contains the - date that a résumé was last updated. -

Parents

- lastModified may be contained in these - elements: - resume -

Examples

<lastModified>
-  <date>
-    <dayOfMonth>4</dayOfMonth>
-    <month>July</month>
-    <year>1796</year>
-  </date>
-</lastModified>

Name

legalnotice — A legal statement

Synopsis

Content Model

(para+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The legalnotice element contains text - that is intended to specify the legal use of a résumé. -

Parents

- legalnotice may be contained in these - elements: - copyright -

Examples

- For examples, see copyright -

Name

level — A degree type

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The semantic of the title element - vary depending on which element contains it: - -

clearance

- When contained in this element, the level element specifies the level of - security clearance that a person has been granted, such as - “Top Secret” or “Restricted”. -

degree

- When contained in this element, the level element specifies a degree type, - such as “BFA” (bachelor of fine arts) or - “Ph.D” (doctor of philosophy). It typically contains - the abbreviation (“BS”) not the full spelling - (“bachelor of science”). -

-

Parents

- level may be contained in these - elements: - clearance, degree -

Examples

- For examples, see clearance and degree. -

Name

link — A titled hyperlink

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
hrefCDATANone
targetsCDATANone

Description

- The link element defines a single - hyperlink, much like HTML's a (anchor) - element. - -

Formatting

- 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. -

Parents

- link may be contained in these - elements: - achievement, artTitle, bookTitle, employer, institution, organization, para, project, publisher, skill -

Attributes

href

- The URL that the link should point to. - then be referred to by this identifier. -

See Also

- uri, url. -

Examples

<employer>
-  <link href="http://www.acme.bob/">Acme Corporation</link>
-</employer>
<para>
-  The <link href="http://xmlresume.sf.net/">XML R&eacute;sum&eacute;
-  Project</link> supplies tools that easily convert a single XML
-  r&eacute;sum&eacute; to multiple output formats.
-</employer>

Name

location — A location, with city-level granularity

Synopsis

Content Model

(city?,(state|province|county)?,country?)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The location element specifies a - level location, such as “London, England”, “Seattle, - Washington”, “St. Louis, Missouri, USA”, or - “Newfoundland, Canada”. -

Parents

- location may be contained in these - elements: - degree, job, membership -

See Also

- address. -

Examples

<location>
-  <city>Los Angeles<city>
-  <state>California</state>
-  <country>USA</country>
-</location>
<location>
-  <city>Paris<city>
-  <country>France</country>
-</location>

Name

major — A main course of study

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- major may be contained in these - elements: - degree -

See Also

- minor. -

Examples

- For examples, see degree. -

Name

membership — A professional membership

Synopsis

Content Model

(title?,(organization,location?)?,(date|period)?,description?)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The membership element contains - information about a person's membership in a professional organization. -

Parents

- membership may be contained in these - elements: - memberships -

Attributes

id

- A string used to uniquely identify a membership. The membership - may then be referred to by this identifier. -

Examples

- For examples, see memberships. -

Name

memberships — Container for one or more memberships

Synopsis

Content Model

(title,membership+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The memberships element contains one - or more memberships. -

Parents

- memberships may be contained in these - elements: - resume -

Examples

<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>

Name

middlenames — One or more “middle” names of a person

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- middlenames may be contained in these - elements: - name -

See Also

- firstname, surname. -

Examples

<middlenames>Samione</middlenames>
<middlenames>Lu&iacute;s Garcia M&aacute;rquez</middlenames>

Name

minor — A minor course of study

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- minor may be contained in these - elements: - degree -

See Also

- major. -

Examples

- For examples, see degree. -

Name

misc — Miscellaneous remarks

Synopsis

Content Model

(para+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The misc element contains paragraphs - of text that don't fit into any other top-level categories. -

Parents

- misc may be contained in these - elements: - resume -

Examples

<misc>
-  <para>What can't be captured on a r&eacute;sum&eacute; 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&ograve;n</citation>.
-  </para>
-</misc>

Name

month — A month name

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The month element contains the name - of a month, such as “March” (English), “marzo” - (Spanish), or “mars” (French). -

Parents

- month may be contained in these - elements: - date, pubDate -

See Also

- dayOfMonth, year. -

Examples

<month>April</month>

Name

name — A person's name

Synopsis

Content Model

(title?,firstname,middlenames?,surname,suffix?)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The name element contains a person's - name. -

Parents

- name may be contained in these - elements: - copyright, header, referee -

Attributes

id

- A string used to uniquely identify a name. The name may then be - referred to by this identifier. -

Examples

<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>

Name

node —

Deprecated

Synopsis

Content Model

(label,uri)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

- -

Parents

- node may be contained in these - elements: - docpath -

Examples

<!-- TODO -->

Name

note — Additional information

Synopsis

Content Model

(para+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The note element contains additional - information about its parent element. -

Parents

- note may be contained in these - elements: - academics, clearance, gpa -

See Also

- annotation, legalnotice. -

Examples

<academics>
-  <degrees>
-    ...
-  </degrees>
-  <note>
-    <para>
-      I take education very seriously. After all, I'm in 37th grade now!
-    </para>
-  </note>
-</academics>

Name

objective — A person's employment goal

Synopsis

Content Model

(para+)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- objective may be contained in these - elements: - resume -

Attributes

id

- A string used to uniquely identify an objective. The objective - may then be referred to by this identifier. -

Examples

<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>

Name

organization — A name of an organization

Synopsis

Content Model

(#PCDATA|emphasis|citation|url|link)*

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The organization element contains the - name of a professional or other type of organization. -

Parents

- organization may be contained in these - elements: - award, clearance, membership, referee -

Attributes

id

- A string used to uniquely identify an organization. The - organization may then be referred to by this identifier. -

See Also

- institution. -

- --> - -

Examples

<membership>
-  <organization>Croquet Players' Association of the UK</organization>
-</membership>

Name

pageNums — One or more page numbers or ranges

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The pageNums element specifies one - or more page numbers or ranges of page numbers, and is used in citing a - publication. -

Parents

- pageNums may be contained in these - elements: - pub -

Examples

<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>

Name

pager — A pager telephone number

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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.) -

Parents

- pager may be contained in these - elements: - contact -

See Also

- email, fax, phone. -

Examples

<pager>456-145-4468</pager>
<pager>736.272.4673 x 235</pager>

Name

para — A paragraph of text

Synopsis

Content Model

(#PCDATA|emphasis|citation|url|link)*

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- para may be contained in these - elements: - description, legalnotice, misc, note, objective, pub -

Examples

<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>

Name

period — A period of time

Synopsis

Content Model

(from,to)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- period may be contained in these - elements: - award, clearance, degree, job, membership -

See Also

- element. -

Examples

<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>

Name

phone — A voice telephone number

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
location

Enumeration:

home
work
mobile
None
targetsCDATANone

Description

- 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 -

- -

Parents

- phone may be contained in these - elements: - contact -

Attributes

location

- Indicates the location that the phone number connects to. This - attribute is optional. -

See Also

- address, email, fax, pager. -

Examples

<phone>555.555.1212</phone>
<phone location="mobile">345-262-4567</phone>
<phone location="home">(261) 345-1616</phone>

- For additional examples, see contact. -

Name

possible — The highest possible score in a GPA

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- possible may be contained in these - elements: - gpa -

See Also

- score. -

Examples

- For examples, see gpa. -

Name

postalCode — A postal code

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- postalCode may be contained in these - elements: - address -

See Also

- zip. -

Examples

A Brazilian postal code: - 

<postalCode>85070-200</postalCode>

-

A Canadian postal code: - 

<postalCode>V2B 5S8</postalCode>

-

Name

prefecture — A name of a prefecture or other administrative district

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- prefecture may be contained in these - elements: - address -

Attributes

id

- A string used to uniquely identify a prefecture. The prefecture - may then be referred to by this identifier. -

See Also

- city, county, state, suburb, ward. -

Examples

<prefecture>Basilius</prefecture>

Name

present — Indicates the current time

Synopsis

Content Model

EMPTY

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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/>. -

Parents

- present may be contained in these - elements: - from, to -

See Also

- date. -

Examples

<period>
-  <from><date>
-    <month>May</month>
-    <year>1995</year>
-  </from>
-  <to>
-    <present/>
-  </to>
-</period>

Name

project — Container for information about a project

Synopsis

Content Model

(#PCDATA|emphasis|citation|url|link)*

Attributes

NameTypeDefault
targetsCDATANone
titleCDATANone

Description

- The project element describes a - project that a person participated in at a job. -

Parents

- project may be contained in these - elements: - projects -

Attributes

title

- The title of the project. -

See Also

- achievement. -

Examples

- For examples, see projects. -

Name

projects — Container for one or more projects

Synopsis

Content Model

(project+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The projects element groups together - one or more project elements. -

Parents

- projects may be contained in these - elements: - degree, job -

See Also

- achievements. -

Examples

<projects>
-  <project>Organization of Paperclips</project>
-  <project>Development of rocket booster fuel</project>
-  <project>1997 Papercut Convention</project>
-</projects>

Name

province — A name or abbreviation of a province

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The province element contains the - name or abbreviation of a single province or similar political division. -

Parents

- province may be contained in these - elements: - address, location -

Attributes

id

- A string used to uniquely identify a province. The province may - then be referred to by this identifier. -

See Also

- county, state. -

Examples

<province>Saskatchewan</province>
<province>BC</province>

Name

pub — A work published by the résumé “owner”

Synopsis

Content Model

(para|(artTitle|bookTitle|author|date|pubDate|publisher|pageNums|url))*

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- pub may be contained in these - elements: - pubs -

Attributes

id

- A string used to uniquely identify a publication. The - publication may then be referred to by this identifier. -

See Also

- citation. -

Examples

Example 4. Book with multiple authors

<pub>
-  <bookTitle>Foundations of Computer Science, C Edition</bookTitle>
-  <author>Alfred V. Aho</author>
-  <author>Jeffrey D. Ullman</author>
-  <pubDate>
-    <year>1995</year>
-  </pubDate>
-  <publisher>Computer Science Press, New York</publisher>
-</pub>

Example 5. Magazine article

<pub>
-  <artTitle>Low-Fat Philly Cheese Steaks</bookTitle>
-  <bookTitle>Healthy Cooking</bookTitle>
-  <author>Joe Sixpack</author>
-  <pubDate>
-    <month>June</month>
-    <year>1999</year>
-  </pubDate>
-  <publisher>Healthy Publishing Group</publisher>
-</pub>

Name

pubDate — The date a work was published

Deprecated

Synopsis

Content Model

(month?,year)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

Parents

- pubDate may be contained in these - elements: - pub -

See Also

- date. -

Examples

<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>

Name

publisher — Information about a publisher of a work

Synopsis

Content Model

(#PCDATA|link|url)*

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

Parents

- publisher may be contained in these - elements: - pub -

Examples

Example 6. Publisher name only

<pub>
-  <bookTitle>Deep Thoughts on Stuff</bookTitle>
-  <publisher>Totally Groovy Publishing, Ltd.</publisher>
-</pub>

Example 7. Publisher name and location

<pub>
-  <bookTitle>A User's Guide to Dirt</bookTitle>
-  <publisher>Mother Nature Books, Boston, Massachusetts</publisher>
-</pub>

Name

pubs — A group of one or more publications

Synopsis

Content Model

(pub+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The pubs element groups together one - or more publications. -

Parents

- pubs may be contained in these - elements: - resume -

Examples

<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>

Name

referee — Someone who can provide additional information about the person the résumé describes

Synopsis

Content Model

(name,title?,organization?,address?,contact?)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Formatting

- The display of referee is influenced - by the referees.display parameter. -

Parents

- referee may be contained in these - elements: - referees -

Examples

<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. -

Name

referees — Contains one or more referees

Synopsis

Content Model

(referee+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The referees element groups together - one or more referee elements. -

Parents

- referees may be contained in these - elements: - resume -

Examples

<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>

Name

result — An outcome of a subject

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The result element describes the - outcome or result of a subject. result often contains the letter or numeric - grade awarded for an academic class. -

Parents

- result may be contained in these - elements: - subject -

Examples

<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>

Name

resume — A résumé or curriculum vitae

Synopsis

Content Model

(docpath?,header?,((objective|history|academics|skillareas|skillarea|pubs|misc|referees|keywords|memberships|interests|clearances|awards))*,lastModified?,copyright?)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone
xmlnsCDATAhttp://xmlresume.sourceforge.net/resume/0.0
xmlns:xsiCDATAhttp://www.w3.org/2001/XMLSchema-instance
xsi:schemaLocationCDATANone

Description

- 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. -

Parents

- resume may be contained in these - elements: - resumes -

Attributes

id

- A string used to uniquely identify a résumé. The résumé may - then be referred to by this identifier. -

Examples

<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. -

Name

resumes — A collection of one or more résumés

Synopsis

Content Model

(resume*)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone
xmlnsCDATAhttp://xmlresume.sourceforge.net/resume/0.0
xmlns:xsiCDATAhttp://www.w3.org/2001/XMLSchema-instance
xsi:schemaLocationCDATANone

Description

- 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. -

Parents

- resumes may be contained in these - elements: - None -

Attributes

id

- A string used to uniquely identify a group of résumés. The - résumés may then be referred to by this identifier. -

Examples

<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>

Name

score — The score earned in a GPA

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The score element contains the GPA - score that a person has earned. -

Parents

- score may be contained in these - elements: - gpa -

See Also

- possible. -

Examples

- For examples, see gpa. -

Name

skill — A name and/or description of a skill

Synopsis

Content Model

(#PCDATA|emphasis|citation|url|link)*

Attributes

NameTypeDefault
idIDNone
levelCDATANone
targetsCDATANone

Description

- The skill element describes something - that a person is skilled at. -

Parents

- skill may be contained in these - elements: - skills, skillset -

Attributes

level

- The level attribute indicates - a person's level of proficiency at a skill. “Level of - proficiency” may be expressed in any manner, such as - “3 years” (three years of experience with a - particular skill), “expert”, or “7/10”. - The skills.level.display parameter - determines whether or not skill levels are displayed in formatted - output. -

See Also

- achievement, skills.format, skills.level.display. -

Examples

<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>

Name

skillarea — A group of broadly related skill sets

Synopsis

Content Model

(title,skillset+)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Formatting

- 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. -

Parents

- skillarea may be contained in these - elements: - resume, skillareas -

Attributes

id

- A string used to uniquely identify a skill area. The skill area - may then be referred to by this identifier. -

Examples

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>

Name

skillareas — Group of one or more skill areas

Deprecated

Synopsis

Content Model

(skillarea+)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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é. -

Parents

- skillareas may be contained in these - elements: - resume -

Examples

<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>

Name

skills — Group of one or more skills

Deprecated

Synopsis

Content Model

(skill+)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

Important

- 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. -

Parents

- skills may be contained in these - elements: - skillset -

Attributes

id

- A string used to uniquely identify a skills group. The group may - then be referred to by this identifier. -

See Also

- skills.format. -

Examples

<skills>
-  <skill>Leaping over tall buildings in a single bound</skill>
-  <skill>Flying</skill>
-  <skill>Quickly changing clothes</skill>
-</skill>

Name

skillset — A titled group of one or more related skills

Synopsis

Content Model

(title?,(skill+|skills))

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The skillset element contains a - titled set of (usually closely) related skills. -

Formatting

- The skills.format - parameter controls the formatting of skill sets. -

Parents

- skillset may be contained in these - elements: - skillarea -

Attributes

id

- A string used to uniquely identify a skill set. The skill set - may then be referred to by this identifier. -

Examples

<skillset>
-  <title>Eating Utinsels</title>
-  <skill>Knife</skill>
-  <skill>Fork</skill>
-  <skill>Spoon</skill>
-  <skill>Soup Spoon</skill>
-</skillset>

Name

state — A name or abbreviation of a state

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- state may be contained in these - elements: - address, location -

Attributes

id

- A string used to uniquely identify a state name. The name may - then be referred to by this identifier. -

See Also

- province, county, prefecture. -

Examples

Example 10. State name

<state>New York</state>

Example 11. State abbreviation

<state>NY</state>

Name

street — A street name, number, and other related information

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- street may be contained in these - elements: - address -

Attributes

id

- A string used to uniquely identify a street. The street may then - be referred to by this identifier. -

Examples

- For examples, see address. -

Name

street2 — A second line of a street address

Deprecated

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

Important

- 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. -

Parents

- street2 may be contained in these - elements: - address -

Attributes

id

- A string used to uniquely identify the second line of a street - address. The line may then be referred to by this identifier. -

See Also

- street. -

Examples

- None. -

Name

subject — A name of a class or topic of study

Synopsis

Content Model

(title,result)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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). -

Parents

- subject may be contained in these - elements: - subjects -

Examples

<subject>
-  <title>English</title>
-  <result>A-</result>
-</subject>
<subject>
-  <title>PE 194 Crabwalking</title>
-  <result>F</result>
-</subject>

Name

subjects — A group of one or more subjects

Synopsis

Content Model

(subject+)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The subjects element contains one or - more subjects that were studied as part of - the degree represented by the parent of the - subjects. -

Parents

- subjects may be contained in these - elements: - degree -

Examples

<subjects>
-  <subject>
-    <title>Chemistry</title>
-    <result>C</result>
-  </subject>
-  <subject>
-    <title>Physics</title>
-    <result>B-</result>
-  </subject>
-</subjects>

Name

suburb — A name of a suburb

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- The suburb element contains the name - of a suburb, as used by a postal service to deliver mail. -

Parents

- suburb may be contained in these - elements: - address -

Attributes

id

- A string used to uniquely identify a suburb. The suburb may then - be referred to by this identifier. -

See Also

- city, prefecture, ward. -

- --> - -

Examples

Example 12. A New Zealand Address

<address>
-  <street>236 Majoribanks Street</street>
-  <suburb>Mount Victoria</suburb>
-  <city>Wellington</city>
-  <postalCode>6001</postalCode>
-  <country>New Zealand</country>
-</address>

Name

suffix — A suffix of a name, usually specifying lineage

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The suffix element contains a suffix - or suffix abbreviation that follows a name, such as “Jr.”, - “Senior”, or “III”. -

Parents

- suffix may be contained in these - elements: - name -

Examples

<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>

Name

surname — A family name

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The surname element contains a - person's family, or last name. -

Parents

- surname may be contained in these - elements: - name -

Examples

- For examples, see name. -

Name

tail —

Deprecated

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

- -

Parents

- tail may be contained in these - elements: - docpath -

Examples

<!-- TODO -->

Name

title — A title or heading

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The title element contains a title or - heading. Its semantics vary depending on the element that contains it: - -

name

- When contained in this element, title contains a person's formal title, - such as “Dr.”, “Ms.”, or - “Professor”. -

interest

- When contained in this element, title contains the name of an interest, - such as “Cooking”, or “Politics”. -

membership, referee

- When contained in these elements, title contains the name of the - person's role or capacity withing an organization. Examples: - “Treasurer”, “Member”, “Chief - Officer of Toothpaste Policy”, “Lead - Programmer”. -

awards, interests, memberships, skillarea

- When contained in these elements, title contains a heading for that - section of a résumé. It is formatted as a top-level heading. -

Note

- The title element is optional - in awards and interests. If it is not present, the - awards.word and - interests.word parameters will be used - as the heading text in formatted résumés, respectively. -

skillset

- When contained in this element, title contains the name of a skill - category. Examples: “Teaching”, - “Computers”, “Woodworking”, - “Soap Carving”. -

subject

- When contained in this element, title contains the name of a subject. - It can be as general as “English” (a very broad - field of study), or as specific as “Eng 115 Intro to - Writing Fall 2001” (a specific university course name, - number, and date of study). -

- -

Parents

- title may be contained in these - elements: - award, awards, clearances, interest, interests, membership, memberships, name, referee, skillarea, skillset, subject -

See Also

- artTitle, bookTitle. -

Examples

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>

Example 16. subject title

<subject>
-  <title>Intro to Sociology</title>
-  <result>A-</result>
-</subject>

Name

to — The ending point in a period of time

Synopsis

Content Model

(date|present)

Attributes

NameTypeDefault
targetsCDATANone

Description

- 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. -

Parents

- to may be contained in these - elements: - period -

See Also

- from. -

Examples

- For examples, see from and period. -

Name

uri — A Uniform Resource Indicator

Deprecated

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

- -

Parents

- uri may be contained in these - elements: - head, node -

Examples

<!-- TODO -->

Name

url — A Uniform Resource Locator

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

Important

- 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. -

Formatting

- 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). -

HTML

- 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. -

FO/PDF

- 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. -

Plain text

- Formatted as the value of the element. -

Parents

- url may be contained in these - elements: - achievement, contact, employer, institution, organization, para, project, pub, publisher, skill -

See Also

- link. - uri. -

Examples

<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>

Name

ward — A name of a division of a city, town, or county

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- ward may be contained in these - elements: - address -

Attributes

id

- A string used to uniquely identify a ward. The ward may then be - referred to by this identifier. -

See Also

- county, prefecture, suburb. -

Examples

<address>
-  <street>Rua Afonso Camargo, 805</street>
-  <ward>Santana</ward>
-  <city>Guarapuava</city>
-  <state>PR</state>
-  <postalCode>85070-200</postalCode>
-  <country>Brazil</country>
-</address>

Name

year — A year

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
targetsCDATANone

Description

- The year element contains a year - number, along with a possible string that identifies the date system, - such as “B.C.” or “A.D.”. -

Parents

- year may be contained in these - elements: - copyright, date, pubDate -

Examples

<year>1995</year>
<year>240 A.D.</year>

Name

zip — A zip code

Synopsis

Content Model

(#PCDATA)

Attributes

NameTypeDefault
idIDNone
targetsCDATANone

Description

- 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. -

Parents

- zip may be contained in these - elements: - address -

Attributes

id

- A string used to uniquely identify a zip code. The zip code may - then be referred to by this identifier. -

See Also

- postalCode. -

Examples

- For examples, see address. -

XSL Parameter Reference

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
css.href - indicates the CSS stylesheet to use to format HTML output
header.format - controls formatting of the header element
interest.description.format - controls formatting of interest descriptions
referees.display - Determines whether or not referees are visible in formatted - output
skills.format - controls formatting of the skillset element
skills.level.display - Determines whether or not skill level attributes are visible in - formatted output
subjects.format - controls formatting of the subjects element

Name

address.format — controls default formatting of the address element

Applies To

- This parameter controls the formatting of the address element in all output - formats. -

Possible Values

- Possible values include standard (the default), - european, and italian. -

Note

- 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. -

standard

- Formats addresses in North American layout: - -

<street>
-<street2>
-<suburb | ward>
-<city>, <state | province | county > <zip | postalCode>
-<country>

- -

european

- Formats addresses in European layout: - -

<street>
-<street2>
-<suburb | ward>
-<zip | postalCode> <city>, <state | province | county > <country>

-

italian

- 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&eacute;ctor Garc&iacute;a Mariz&oacute;
-Reina #35, apt. 4a, e/ Gervasio y Escobar
-Ciudad de La Habana, CP 11900
-CUBA</address>

- -

Name

css.href — indicates the CSS stylesheet to use to format HTML output

Applies To

- This parameter applies to only the HTML output format. -

Possible Values

- 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. -

Name

header.format — controls formatting of the header element

Applies To

- 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

- Possible values include standard (the default) and - centered. -

standard

- 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. -

centered

- 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/

Name

interest.description.format — controls formatting of interest descriptions

Applies To

- This parameter controls the formatting of the description element when it is contained - in an interest. It affects all output formats. -

Possible Values

- Possible values include single-line and - block. single-line is the default. -

- The examples below demonstrate the formatting of this XML fragment: - - 

<interests>
-  <interest>
-    <title>Scuba diving</title>
-  </interest>
-  <interest>
-    <title>Flying</title>
-    <description>
-      <para>I have my pilot's license, and have logged over 1000 in-flight
-      hours.</para>
-      <para>I have also constructed my own airplane from a kit.</para>
-    </description>
-  </interest>
-</interests>

-

single-line

- This value is the default. Formats all of the para elements in the description on - the same logical line as the interest title. The title is separated - from the description by a period, and the description paragraphs are - separated from each other by - description.para.separator.text, which - defaults to an em-dash (“—”). -

- - For example, the XML above would be formatted similar to the - following: - -

Interests

  • Scuba diving

  • - Flying. I have my pilot's license, and have logged over 1000 - in-flight hours. — I have also constructed my own - airplane from a kit. -

- -

block

- Formats each of the para elements - in the description as a separate block below the interest title. -

- - For example, the XML above would be formatted similar to the - following: - -

Interests

  • 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. -

- -

Name

referees.display — Determines whether or not referees are visible in formatted - output

Applies To

- This parameter controls the formatting of the referee - element in all output formats. -

Possible Values

- Possible values include 1 (display referees) and - 0 (display alternate text). -

1 (true)

- Referees are displayed in formatted output. -

0 (false)

- The text of the referees.hidden.phrase - parameter (default: Available upon request.) is - displayed in place of referees. -

Name

skills.format — controls formatting of the skillset element

Applies To

- This parameter controls the formatting of the skillset element in all output - formats. -

Possible Values

- 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>

- -

bullet

- Formats skills as a bulleted list, one skill per line: - -

Technical Skills

Programming Languages

  • Java

  • C++

  • C

  • Perl

- -

comma

- Produces a comma-separated list on a single line: - -

Technical Skills

- Programming Languages: Java, C++, C, Perl -

-

Name

skills.level.display — Determines whether or not skill level attributes are visible in - formatted output

Applies To

- This parameter controls the formatting of the level attribute of skill - elements in all output formats. -

Possible Values

- Possible values include 1 (display the attribute) or - 0 (suppress the attribute). -

1 (true)

- level attributes of - skills are displayed after all of - the rest of the content of the skill. The level is displayed - surrounded by skills.level.start and - skills.level.end (parenthesis, by default). -

0 (false)

- level attributes contained in - skills are suppressed; they are - treated as if the didn't exist for formatting purposes. -

Name

subjects.format — controls formatting of the subjects element

Applies To

- This parameter controls the formatting of the subjects element in all output formats. -

Possible Values

- 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>

- -

comma

- Produces a comma-separated list on a single line: - -

- Subjects: English (C), Science (A), Math (B-). -

-

table

- Produces a table, with subject name in the first column and result - in the second column: -

Subjects

EnglishC
ScienceA
MathB-

Chapter 3. CSS Class Reference

Table of Contents

Overview

- 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. -

Overview

Table 3.1. Table of CSS Classes

ClassWhere 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é. -

Glossary

attribute

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">
element

- 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. -

parent element

- The element - whose start tags and end tags surround a given element. -

child element

- Any element - positioned between the start tags and end tags of a given - element. -

Appendixes

Table of Contents

A. GNU Free Documentation License
PREAMBLE
APPLICABILITY AND DEFINITIONS
VERBATIM COPYING
COPYING IN QUANTITY
MODIFICATIONS
COMBINING DOCUMENTS
COLLECTIONS OF DOCUMENTS
AGGREGATION WITH INDEPENDENT WORKS
TRANSLATION
TERMINATION
FUTURE REVISIONS OF THIS LICENSE
How to use this License for your documents

Appendix A. GNU Free Documentation License

Table of Contents

PREAMBLE
APPLICABILITY AND DEFINITIONS
VERBATIM COPYING
COPYING IN QUANTITY
MODIFICATIONS
COMBINING DOCUMENTS
COLLECTIONS OF DOCUMENTS
AGGREGATION WITH INDEPENDENT WORKS
TRANSLATION
TERMINATION
FUTURE REVISIONS OF THIS LICENSE
How to use this License for your documents

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.

PREAMBLE

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.

APPLICABILITY AND DEFINITIONS

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.

VERBATIM COPYING

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.

COPYING IN QUANTITY

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.

MODIFICATIONS

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:

  1. 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.

  2. 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).

  3. State on the Title page - the name of the publisher of the Modified Version, as the - publisher.

  4. Preserve all the - copyright notices of the Document.

  5. Add an appropriate - copyright notice for your modifications adjacent to the other - copyright notices.

  6. 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.

  7. Preserve in that license - notice the full lists of Invariant Sections and required Cover - Texts given in the Document's license notice.

  8. Include an unaltered - copy of this License.

  9. 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.

  10. 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.

  11. 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.

  12. 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.

  13. Delete any section - entitled “Endorsements”. Such a section may not be included in - the Modified Version.

  14. 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.

COMBINING DOCUMENTS

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.”

COLLECTIONS OF DOCUMENTS

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.

AGGREGATION WITH INDEPENDENT WORKS

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

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.

TERMINATION

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.

FUTURE REVISIONS OF THIS LICENSE

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.

How to use this License for your documents

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.

\ No newline at end of file diff --git a/legacy-resumes/resume-1/doc/manual/manual.txt b/legacy-resumes/resume-1/doc/manual/manual.txt deleted file mode 100644 index 529b303..0000000 --- a/legacy-resumes/resume-1/doc/manual/manual.txt +++ /dev/null @@ -1,7015 +0,0 @@ - -XML Résumé Library User Guide - -For XML Résumé Library Version 1.5.1 - -Bruce Christensen - - 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 - - Introduction - - What is the XML Résumé Library? - - I. Getting Started - - 1. Setting up the XML Résumé Library - - Prerequisites - Getting the Software - Installing and Configuring the Software - - 2. Exploring the Features of XML Résumé Library - - Formatting an example resume - Advanced Features of the XML Résumé Library - Writing your first XML Résumé - Where to Go from Here - About this chapter - - II. Reference - - I. Element Reference - - academics - Container for information about academic - experience - - achievement - An accomplishment made at a job - achievements - Container for one or more job achievements - address - A postal address - annotation - Additional information about a degree - artTitle - A title of an article or other work - author - An author of a publication - award - An award or other honor - awards - Container for one or more awards - birth - Container for information about a person's birth - bookTitle - A title of a book or similar work - break - A linebreak (Deprecated) - citation - The name of a work being referenced - city - The name of a city - clearance - A security clearance - clearances - One or more security clearances - company - The name of a company (Deprecated) - contact - Container for one or more methods of contacting - someone - - copyright - A copyright notice - country - A country name - county - A county name - date - A specific instant in time - dayOfMonth - An ordinal day of the month - degree - Container for information about a degree or - similar certification - - degrees - Container for one or more degrees - description - An explanation of something - docpath - (Deprecated) - email - An e-mail address - emphasis - An emphasized block of text - employer - A name of an employer - fax - A fax telephone number - firstname - A person's given name - from - The beginning point in a period of time - gpa - Information about a grade point average - head - (Deprecated) - header - Container for information about the person being - described in a résumé - - history - Container for a person's previous (and possibly - current) jobs - - instantMessage - An instant message username or address - institution - A name of an academic institution - interest - Something a person is interested in - interests - Container for one or more interests - job - A specific employment engagement - jobtitle - A job title - keyword - A keyword to be used for résumé indexing and - searching - - keywords - Container for a list of keywords - label - (Deprecated) - lastModified - Information about when a résumé was last - modified - - legalnotice - A legal statement - level - A degree type - link - A titled hyperlink - location - A location, with city-level granularity - major - A main course of study - membership - A professional membership - memberships - Container for one or more memberships - middlenames - One or more middle names of a person - minor - A minor course of study - misc - Miscellaneous remarks - month - A month name - name - A person's name - node - (Deprecated) - note - Additional information - objective - A person's employment goal - organization - A name of an organization - pageNums - One or more page numbers or ranges - pager - A pager telephone number - para - A paragraph of text - period - A period of time - phone - A voice telephone number - possible - The highest possible score in a GPA - postalCode - A postal code - prefecture - A name of a prefecture or other administrative - district - - present - Indicates the current time - project - Container for information about a project - projects - Container for one or more projects - province - A name or abbreviation of a province - pub - A work published by the résumé owner - pubDate - The date a work was published (Deprecated) - publisher - Information about a publisher of a work - pubs - A group of one or more publications - referee - Someone who can provide additional information - about the person the résumé describes - - referees - Contains one or more referees - result - An outcome of a subject - resume - A résumé or curriculum vitae - resumes - A collection of one or more résumés - score - The score earned in a GPA - skill - A name and/or description of a skill - skillarea - A group of broadly related skill sets - skillareas - Group of one or more skill areas (Deprecated) - skills - Group of one or more skills (Deprecated) - skillset - A titled group of one or more related skills - state - A name or abbreviation of a state - street - A street name, number, and other related - information - - street2 - A second line of a street address (Deprecated) - subject - A name of a class or topic of study - subjects - A group of one or more subjects - suburb - A name of a suburb - suffix - A suffix of a name, usually specifying lineage - surname - A family name - tail - (Deprecated) - title - A title or heading - to - The ending point in a period of time - uri - A Uniform Resource Indicator (Deprecated) - url - A Uniform Resource Locator - ward - A name of a division of a city, town, or county - year - A year - zip - A zip code - - II. XSL Parameter Reference - - address.format - controls default formatting of the address - element - - css.href - indicates the CSS stylesheet to use to format - HTML output - - header.format - controls formatting of the header element - interest.description.format - controls formatting of - interest descriptions - - referees.display - Determines whether or not referees are - visible in formatted output - - skills.format - controls formatting of the skillset element - skills.level.display - Determines whether or not skill - level attributes are visible in formatted output - - subjects.format - controls formatting of the subjects - element - - 3. CSS Class Reference - - Overview - - Glossary - III. Appendixes - - A. GNU Free Documentation License - - PREAMBLE - APPLICABILITY AND DEFINITIONS - VERBATIM COPYING - COPYING IN QUANTITY - MODIFICATIONS - COMBINING DOCUMENTS - COLLECTIONS OF DOCUMENTS - AGGREGATION WITH INDEPENDENT WORKS - TRANSLATION - TERMINATION - FUTURE REVISIONS OF THIS LICENSE - How to use this License for your documents - -Introduction - - Table of Contents - - What is the XML Résumé Library? - -What is the XML Résumé Library? - - 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. - -Getting Started - - Table of Contents - - 1. Setting up the XML Résumé Library - - Prerequisites - Getting the Software - Installing and Configuring the Software - - 2. Exploring the Features of XML Résumé Library - - Formatting an example resume - Advanced Features of the XML Résumé Library - Writing your first XML Résumé - Where to Go from Here - About this chapter - -Setting up the XML Résumé Library - -Peter Hutnick - -Edited by - -Bruce Christensen - -Mark Miller - - Copyright © 2002 Peter Hutnick - - Table of Contents - - Prerequisites - Getting the Software - Installing and Configuring the Software - - 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. - -Prerequisites - -Java - - 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. - -XML - - 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. - -Getting the Software - -XML Résumé Library - - 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 - - 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 - - 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 - - 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. - -Installing and Configuring the Software - -XML Résumé Library - - 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. - -Tip - - You can also indicate your résumé filename on the command line when - you build your résumé, e.g.: -[resume]$ make resume=myresume - -Note - - 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: - - -Xerces, Xalan, and FOP - - 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. - -Exploring the Features of XML Résumé Library - -Peter Hutnick - -Mark Miller - -Edited by - -Bruce Christensen - - Copyright © 2002 Peter Hutnick - - Table of Contents - - Formatting an example resume - Advanced Features of the XML Résumé Library - Writing your first XML Résumé - Where to Go from Here - About this chapter - - 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. - -Formatting an example resume - -Converting to other formats - - 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é. - -Advanced Features of the XML Résumé Library - -Filtering to target your resume - - 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: - - Carpentry - Welding - Java Programming - XML - C++ - Good communicator - Gourmet Pastry Creation - Cooking for construction workers - - - 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: - - Carpentry - Welding - Java Programming - XML - C++ - Good communicator - Gourmet Pastry Creation - Cooking for construction -workers - - - 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. - -Customizing your résumé - - With just a few tweaks, you can dramatically change the look of your - résumés. - -Modifying the XSL Parameters - - 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. - -Note - - 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. - -Modifying the look of your HTML Résumé - - 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. - -Writing your first XML Résumé - - 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. - -Where to Go from Here - -Documentation - - 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. - -Support - - 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 - . - -About this chapter - - 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 . - -Reference - - Table of Contents - - I. Element Reference - - academics - Container for information about academic experience - achievement - An accomplishment made at a job - achievements - Container for one or more job achievements - address - A postal address - annotation - Additional information about a degree - artTitle - A title of an article or other work - author - An author of a publication - award - An award or other honor - awards - Container for one or more awards - birth - Container for information about a person's birth - bookTitle - A title of a book or similar work - break - A linebreak (Deprecated) - citation - The name of a work being referenced - city - The name of a city - clearance - A security clearance - clearances - One or more security clearances - company - The name of a company (Deprecated) - contact - Container for one or more methods of contacting someone - copyright - A copyright notice - country - A country name - county - A county name - date - A specific instant in time - dayOfMonth - An ordinal day of the month - degree - Container for information about a degree or similar - certification - - degrees - Container for one or more degrees - description - An explanation of something - docpath - (Deprecated) - email - An e-mail address - emphasis - An emphasized block of text - employer - A name of an employer - fax - A fax telephone number - firstname - A person's given name - from - The beginning point in a period of time - gpa - Information about a grade point average - head - (Deprecated) - header - Container for information about the person being - described in a résumé - - history - Container for a person's previous (and possibly - current) jobs - - instantMessage - An instant message username or address - institution - A name of an academic institution - interest - Something a person is interested in - interests - Container for one or more interests - job - A specific employment engagement - jobtitle - A job title - keyword - A keyword to be used for résumé indexing and searching - keywords - Container for a list of keywords - label - (Deprecated) - lastModified - Information about when a résumé was last modified - legalnotice - A legal statement - level - A degree type - link - A titled hyperlink - location - A location, with city-level granularity - major - A main course of study - membership - A professional membership - memberships - Container for one or more memberships - middlenames - One or more middle names of a person - minor - A minor course of study - misc - Miscellaneous remarks - month - A month name - name - A person's name - node - (Deprecated) - note - Additional information - objective - A person's employment goal - organization - A name of an organization - pageNums - One or more page numbers or ranges - pager - A pager telephone number - para - A paragraph of text - period - A period of time - phone - A voice telephone number - possible - The highest possible score in a GPA - postalCode - A postal code - prefecture - A name of a prefecture or other administrative - district - - present - Indicates the current time - project - Container for information about a project - projects - Container for one or more projects - province - A name or abbreviation of a province - pub - A work published by the résumé owner - pubDate - The date a work was published (Deprecated) - publisher - Information about a publisher of a work - pubs - A group of one or more publications - referee - Someone who can provide additional information about - the person the résumé describes - - referees - Contains one or more referees - result - An outcome of a subject - resume - A résumé or curriculum vitae - resumes - A collection of one or more résumés - score - The score earned in a GPA - skill - A name and/or description of a skill - skillarea - A group of broadly related skill sets - skillareas - Group of one or more skill areas (Deprecated) - skills - Group of one or more skills (Deprecated) - skillset - A titled group of one or more related skills - state - A name or abbreviation of a state - street - A street name, number, and other related information - street2 - A second line of a street address (Deprecated) - subject - A name of a class or topic of study - subjects - A group of one or more subjects - suburb - A name of a suburb - suffix - A suffix of a name, usually specifying lineage - surname - A family name - tail - (Deprecated) - title - A title or heading - to - The ending point in a period of time - uri - A Uniform Resource Indicator (Deprecated) - url - A Uniform Resource Locator - ward - A name of a division of a city, town, or county - year - A year - zip - A zip code - - II. XSL Parameter Reference - - address.format - controls default formatting of the address - element - - css.href - indicates the CSS stylesheet to use to format HTML - output - - header.format - controls formatting of the header element - interest.description.format - controls formatting of interest - descriptions - - referees.display - Determines whether or not referees are visible - in formatted output - - skills.format - controls formatting of the skillset element - skills.level.display - Determines whether or not skill level - attributes are visible in formatted output - - subjects.format - controls formatting of the subjects element - - 3. CSS Class Reference - - Overview - -Element Reference - _________________________________________________________________ - - 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. - -Changes to the DTD - - This sections documents changes to the XML Résumé Library DTD. - -Warning - - 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. - -Version ??? - - * Changed elements: projects may now be included in the degree - element. - -Version 1.5.0 - - * 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. - -Version 1.4.2 - - No DTD changes. - -Version 1.4.1 - - * New elements: clearances and clearance. - * New elements: gpa, score, and possible. - * New element: location. It may be contained in job, degree, or - membership. - * Change: name may now contain a title. - * Change: institution and organization may now contain inline - elements (emphasis, citation, url, and link). - -Version 1.4.0 - - * New element: minor. - * New element: lastModified. - * New elements: awards and award. - * New elements: interests and interest. - * 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. - -Version 1.3.3 - - * 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. - -Version 1.3.2 - - No DTD changes. - - Table of Contents - - academics - Container for information about academic experience - achievement - An accomplishment made at a job - achievements - Container for one or more job achievements - address - A postal address - annotation - Additional information about a degree - artTitle - A title of an article or other work - author - An author of a publication - award - An award or other honor - awards - Container for one or more awards - birth - Container for information about a person's birth - bookTitle - A title of a book or similar work - break - A linebreak (Deprecated) - citation - The name of a work being referenced - city - The name of a city - clearance - A security clearance - clearances - One or more security clearances - company - The name of a company (Deprecated) - contact - Container for one or more methods of contacting someone - copyright - A copyright notice - country - A country name - county - A county name - date - A specific instant in time - dayOfMonth - An ordinal day of the month - degree - Container for information about a degree or similar - certification - - degrees - Container for one or more degrees - description - An explanation of something - docpath - (Deprecated) - email - An e-mail address - emphasis - An emphasized block of text - employer - A name of an employer - fax - A fax telephone number - firstname - A person's given name - from - The beginning point in a period of time - gpa - Information about a grade point average - head - (Deprecated) - header - Container for information about the person being described in - a résumé - - history - Container for a person's previous (and possibly current) - jobs - - instantMessage - An instant message username or address - institution - A name of an academic institution - interest - Something a person is interested in - interests - Container for one or more interests - job - A specific employment engagement - jobtitle - A job title - keyword - A keyword to be used for résumé indexing and searching - keywords - Container for a list of keywords - label - (Deprecated) - lastModified - Information about when a résumé was last modified - legalnotice - A legal statement - level - A degree type - link - A titled hyperlink - location - A location, with city-level granularity - major - A main course of study - membership - A professional membership - memberships - Container for one or more memberships - middlenames - One or more middle names of a person - minor - A minor course of study - misc - Miscellaneous remarks - month - A month name - name - A person's name - node - (Deprecated) - note - Additional information - objective - A person's employment goal - organization - A name of an organization - pageNums - One or more page numbers or ranges - pager - A pager telephone number - para - A paragraph of text - period - A period of time - phone - A voice telephone number - possible - The highest possible score in a GPA - postalCode - A postal code - prefecture - A name of a prefecture or other administrative district - present - Indicates the current time - project - Container for information about a project - projects - Container for one or more projects - province - A name or abbreviation of a province - pub - A work published by the résumé owner - pubDate - The date a work was published (Deprecated) - publisher - Information about a publisher of a work - pubs - A group of one or more publications - referee - Someone who can provide additional information about the - person the résumé describes - - referees - Contains one or more referees - result - An outcome of a subject - resume - A résumé or curriculum vitae - resumes - A collection of one or more résumés - score - The score earned in a GPA - skill - A name and/or description of a skill - skillarea - A group of broadly related skill sets - skillareas - Group of one or more skill areas (Deprecated) - skills - Group of one or more skills (Deprecated) - skillset - A titled group of one or more related skills - state - A name or abbreviation of a state - street - A street name, number, and other related information - street2 - A second line of a street address (Deprecated) - subject - A name of a class or topic of study - subjects - A group of one or more subjects - suburb - A name of a suburb - suffix - A suffix of a name, usually specifying lineage - surname - A family name - tail - (Deprecated) - title - A title or heading - to - The ending point in a period of time - uri - A Uniform Resource Indicator (Deprecated) - url - A Uniform Resource Locator - ward - A name of a division of a city, town, or county - year - A year - zip - A zip code - -Name - - academics -- Container for information about academic experience - -Synopsis - -Content Model - -(degrees,note?) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The academics element contains information about a person's academic - experience. - -Parents - - academics may be contained in these elements: resume - -See Also - - pubs, memberships. - -Examples - - - - - Ph.D - Toothpick Manufacturing - Stanford University - - - - - I also have an honorary doctorate in toothpick structural analysis from - MIT. - - - - - - - - BA - Culinary Psychology - - - - _________________________________________________________________ - -Name - - achievement -- An accomplishment made at a job - -Synopsis - -Content Model - -(#PCDATA|emphasis|citation|url|link)* - -Attributes - - Name Type Default - targets CDATA None - -Description - - The achievment element contains a single accomplishment made while - working at a particular job (e.g. "increased sales by 20%", or - "improved employee efficiency"). - -Parents - - achievement may be contained in these elements: achievements - -Examples - - - Eggroll Engineer - Chineese Cuisine Systems, Inc. - - - - August - 1993 - - - - - - - - - Wrote an excellent article on shell crispiness for - the European Journal of Egg Food Engineering, - published at http://www.ejeps.org/articles/crispiness.html. - - - Decreased filling greasiness by a whopping 30%! - - - - _________________________________________________________________ - -Name - - achievements -- Container for one or more job achievements - -Synopsis - -Content Model - -(achievement+) - -Attributes - - Name Type Default - targets CDATA None - -Description - - achievements is a wrapper element that contains one or more - achievement elements. Achievements are specific things that were - accomplished at a job. - -Parents - - achievements may be contained in these elements: job - -Examples - - For examples, see achievement. - _________________________________________________________________ - -Name - - address -- A postal address - -Synopsis - -Content Model - -(#PCDATA|street|street2|suburb|ward|city|state|province|county|prefecture|zip|p -ostalCode|country|break)* - -Attributes - - Name Type Default - format - - Enumeration: - standard - european - italian - None - id ID None - targets CDATA None - -Description - - 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. - -Parents - - address may be contained in these elements: header, referee - -Attributes - - id - A string used to uniquely identify an address. The address may - then be referred to by this identifier. - - format - The address format. This attribute specifies the format of an - address, and overrides the global address.format parameter for - each address that it appears in. - -See Also - - address.format. - -Examples - - Example 1. U.S.-style address -
- 123 Pickle St. - Apt. #12 - Sourville - NX - 99999-9999 -
- - Formatted as: - - 123 Pickle St. Apt. #12 - Sourville, NX 99999-9999 - - Example 2. Italian address -
- Via Garibaldi, 23 - Sorrento - 123 456 - NA - Italy -
- - Example 3. Untagged address -
Reina #35, apt. 4a, e/ Gervasio y Escobar -Ciudad de La Habana, CP 11900 -CUBA
- - Formatted as: - - Reina #35, apt. 4a, e/ Gervasio y Escobar - Ciudad de La Habana, CP 11900 - CUBA - -Warning - - 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. - _________________________________________________________________ - -Name - - annotation -- Additional information about a degree - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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"). - -Parents - - annotation may be contained in these elements: degree - -Examples - - - BS - Street Cleaning Technology - - Graduated with highest honors. - - - - - BFA - Chalkboard Scratching Composition - - Received dean's award in 1984. - - - _________________________________________________________________ - -Name - - artTitle -- A title of an article or other work - -Synopsis - -Content Model - -(#PCDATA|link)* - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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. - -Parents - - artTitle may be contained in these elements: pub - -See Also - - bookTitle. - -Examples - - - Lion Brainwashing During the Late 20th Century - Journal of the American Feline Psychiatric Association - - - - Cucumber Pickling Process Management - Proceedings of the European Brine Process Engineers' Group - - _________________________________________________________________ - -Name - - author -- An author of a publication - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - name IDREF None - targets CDATA None - -Description - - 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. - -Parents - - author may be contained in these elements: pub - -Attributes - - name - The name attribute contains the id of a name element. - - If an author element specifies this attribute, it should not - have any content. In other words, there should be a single tag - with a reference () instead of two - tags enclosing content (Joe Smith). - -See Also - - name. - -Examples - - - Nuclear Engineering for Dummies - Edgar Neutron - - - - Shirly - Mendoza - - - Cooking Wire-Core Pretzels - - Journal of Metal-Reinforced Confections - - _________________________________________________________________ - -Name - - award -- An award or other honor - -Synopsis - -Content Model - -(title,organization?,(date|period)?,description?) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The award element describes an award or other honor received by a - person (e.g. "Nobel Prize", "MacArthur Fellow"). - -Parents - - award may be contained in these elements: awards - -Examples - - - Dean's List - ACME University - - - - Honor Roll - Littleton Middle School - - 1995 - - - Maintained a 4.0 GPA. - - - _________________________________________________________________ - -Name - - awards -- Container for one or more awards - -Synopsis - -Content Model - -(title?,award+) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The awards element contains one or more awards. - -Parents - - awards may be contained in these elements: resume - -Examples - - - Awards and Honors - - Employee of the Month - ACME, Inc. - May2002 - - - Received for exceptional customer service. - - - - - AP Scholar - College Board - 2002 - - - _________________________________________________________________ - -Name - - birth -- Container for information about a person's birth - -Synopsis - -Content Model - -(date) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The birth element contains a single date that specifies when a person - was born. - -Parents - - birth may be contained in these elements: header - -Examples - -
- - Scotty - O'Reilly - - - - 17 - March - 1931 - - -
- -
- - Josè - Luis Miguel - Domingo - - - - 23 - Mayo - 1834 - - -
- _________________________________________________________________ - -Name - - bookTitle -- A title of a book or similar work - -Synopsis - -Content Model - -(#PCDATA|link)* - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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. - -Parents - - bookTitle may be contained in these elements: pub - -See Also - - artTitle. - -Examples - - - Tropical Siberian Vacations - Boris Tzchleikovsy - - - - Children's Bedtime Stories - Jack the Axe Murderer - Caroline Black - - - - Global Commodities Market Downturn - The Economist - - June - 1992 - - - _________________________________________________________________ - -Name - - break -- A linebreak - - Deprecated - -Synopsis - -Content Model - -EMPTY - -Attributes - - Name Type Default - targets CDATA None - -Description - -Important - - 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. - -Parents - - break may be contained in these elements: address - -Examples - - None. - _________________________________________________________________ - -Name - - citation -- The name of a work being referenced - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The citation element marks the title of a book, website, course, or - other work. - -Parents - - citation may be contained in these elements: achievement, employer, - institution, organization, para, project, skill - -See Also - - pub. - -Examples - - - Increased earnings 341%, thereby landing Acme Widgets on Fortune - Magazine's Fortune 500 list. - - - - More information on the AHTM system is published in Developing - Today at http://www.dtoday.bob/tips.html. - - _________________________________________________________________ - -Name - - city -- The name of a city - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - The city element contains a the name of a single city or other similar - municipality. - -Parents - - city may be contained in these elements: address, location - -Attributes - - id - A string used to uniquely identify a city. The city may then be - referred to by this identifier. - -See Also - - county, prefecture, suburb, ward. - -Examples - -
- 3400 N. 5230 S. - Salt Lake City - UT - 84352 -
- _________________________________________________________________ - -Name - - clearance -- A security clearance - -Synopsis - -Content Model - -(level,organization?,(date|period)?,note?) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The clearance element contains a single security clearance (e.g. "Top - Secret"). - -Parents - - clearance may be contained in these elements: clearances - -Examples - - - Super-duper it-doesn't-even-exist extra secret - NATO - - - - Top Secret - CIA - 2002 - Full polygraph test performed. - - _________________________________________________________________ - -Name - - clearances -- One or more security clearances - -Synopsis - -Content Model - -(title?,clearance+) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The clearances element contains one or more security clearances. It is - a top-level section of a résumé. - -Parents - - clearances may be contained in these elements: resume - -Examples - - - - Top Secret - NSA - - - Secret - US Navy - - - _________________________________________________________________ - -Name - - company -- The name of a company - - Deprecated - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - -Important - - This element is deprecated as of XML Résumé Library version 1.3.3. It - should not be used. - -Parents - - company may be contained in these elements: None - -See Also - - institution, organization. - -Examples - - None. - _________________________________________________________________ - -Name - - contact -- Container for one or more methods of contacting someone - -Synopsis - -Content Model - -(phone|fax|pager|email|url|instantMessage)* - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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. - -Parents - - contact may be contained in these elements: header, referee - -See Also - - address. - -Examples - - - 555-555-1212 - sam.jones@xyz.bob - http://www.xyz.bob/~sam.jones/ - - - - 123-123-1234 x123 - - - - kawanza_eloma@hotmail.bob - - _________________________________________________________________ - -Name - - copyright -- A copyright notice - -Synopsis - -Content Model - -(year,name?,legalnotice?) - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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. - -Parents - - copyright may be contained in these elements: resume - -Examples - - - - 1892 - - Fluisha - Copenhagen - - - - All rights reserved. This document may not be copied or distributed - without permission. - - - - - - - 2001 - - _________________________________________________________________ - -Name - - country -- A country name - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - The country element marks the name of a country. - -Parents - - country may be contained in these elements: address, location - -Attributes - - id - A string used to uniquely identify a country. The country may - then be referred to by this identifier. - -Examples - -
- Portland - Oregon - USA -
- -
- 2621 Green Loop - Southam - Wiggleworm - S521 2GR - UK -
- _________________________________________________________________ - -Name - - county -- A county name - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - 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.) - -Parents - - county may be contained in these elements: address, location - -Attributes - - id - A string used to uniquely identify a county. The county may - then be referred to by this identifier. - -See Also - - state, province, prefecture. - -Examples - -
- North Willow - Washington - New Canada -
- -
- 1 O'Leary Place - Coby - Co. Cork - Ireland -
- _________________________________________________________________ - -Name - - date -- A specific instant in time - -Synopsis - -Content Model - -(((dayOfMonth)?,month)?,year) - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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. - -Note - - 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. - -Parents - - date may be contained in these elements: award, birth, clearance, - degree, from, job, lastModified, membership, pub, to - -See Also - - period. - -Examples - - - 27 - November - 1634 - - - - July - 1457 - - _________________________________________________________________ - -Name - - dayOfMonth -- An ordinal day of the month - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - Represents a specific day in a month. Its value is numeric; the first - day of the month is written 1, the fifteenth 15, etc. - -Parents - - dayOfMonth may be contained in these elements: date - -Examples - - For examples, see date. - _________________________________________________________________ - -Name - - degree -- Container for information about a degree or similar - certification - -Synopsis - -Content Model - -(level,annotation?,major*,minor*,(date|period)?,(institution,location?)?,gpa?,s -ubjects?,projects?) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - The degree element is a container for information about an academic - degree (Bachelor of Science, Doctor of Psychology, etc.) or other - similar certification. - -Parents - - degree may be contained in these elements: degrees - -Attributes - - id - A string used to uniquely identify a degree. The degree may - then be referred to by this identifier. - -Examples - - - Ph.D - Microbiology - Thesis on effect of hot dogs on canine amino acids - - - - BA - Toilet Paper Pattern Design - - June - 1745 - - British Design Academy - - On dean's list for duration of studies. - - - - - BS - Computer Science - English - Graphic Design - Geography - - - Compilers - A- - - - Data Structures - B - - - Classic Literature - A - - - - _________________________________________________________________ - -Name - - degrees -- Container for one or more degrees - -Synopsis - -Content Model - -(degree+) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The degrees element is a container for at least one degree. - -Parents - - degrees may be contained in these elements: academics - -Examples - - - - BA - Interstellar Basket Weaving - - - Ph.D - Aquatic Tennis Teaching - - - _________________________________________________________________ - -Name - - description -- An explanation of something - -Synopsis - -Content Model - -(para+) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The description element specifies a person's role, their activities, - or other descriptive information. - -Parents - - description may be contained in these elements: award, interest, job, - membership - -See Also - - projects, achievements. - -Examples - - - Supersonic Vacuum Technician - Joe's Vacuum Shop - - June2344 - - - - Repaired hyperdynamic microbial particle accelerators in Supersonic vacuum - models XL144 and XP2000. - - - - - Treasurer - Mars Vacuum Repair Association - - Kept books and collected membership dues. - - - _________________________________________________________________ - -Name - - docpath -- - - Deprecated - -Synopsis - -Content Model - -(head?,node*,tail) - -Attributes - - Name Type Default - targets CDATA None - -Description - -Important - - 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. - -Parents - - docpath may be contained in these elements: resume - -Examples - - - _________________________________________________________________ - -Name - - email -- An e-mail address - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The email element specifies a single e-mail address. - -Parents - - email may be contained in these elements: contact - -See Also - - fax, instantMessage, pager, url. - -Examples - - - john@johnny.bob - 555-555-1212 - - _________________________________________________________________ - -Name - - emphasis -- An emphasized block of text - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The emphasis element is an inline element that indicates that the text - it contains should be emphasized. - -Presentation - - The presentation of text contained in this element varies depending on - the output format. - - HTML - Rendered as bold (using the tag) by default. - Presentation may be overridden by creating or modifying a CSS - stylesheet that formats the emphasis class. - - Text - 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. - - XSL-FO/PDF - Rendered as bold text. - -Parents - - emphasis may be contained in these elements: achievement, employer, - institution, organization, para, project, skill - -Examples - - - I really, really, really want a job. - - - - I am extremely at using rocket-powered cheese graters. - - _________________________________________________________________ - -Name - - employer -- A name of an employer - -Synopsis - -Content Model - -(#PCDATA|emphasis|citation|url|link)* - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - The employer element specifies the name of a person, company, or other - entity for whom a person works or has worked. - -Parents - - employer may be contained in these elements: job - -Attributes - - id - A string used to uniquely identify an employer. The employer - may then be referred to by this identifier. - -See Also - - institution, organization. - -Examples - - - Angelfish Fitness Trainer - Fish Fitness Systems, Inc. - - July1998 - - - - - Helped to ensure optimum fish health by training fish on weights and - and fin and tail exercises. - - - - - - House Cleaner - Mrs. Shirlock - - July1954 - January1956 - - Dusted the blinds. That is all. - - _________________________________________________________________ - -Name - - fax -- A fax telephone number - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - location - - Enumeration: - home - work - None - targets CDATA None - -Description - - 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.) - -Parents - - fax may be contained in these elements: contact - -Attributes - - location - Indicates the location that the phone number connects to. This - attribute is optional. - -See Also - - email, pager, phone. - -Examples - -555-555-1212 - -(123) 456-7890 - -345.324.2721 - _________________________________________________________________ - -Name - - firstname -- A person's given name - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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". - -Parents - - firstname may be contained in these elements: name - -See Also - - middlenames, surname. - -Examples - - - Caroline - Francisca - - _________________________________________________________________ - -Name - - from -- The beginning point in a period of time - -Synopsis - -Content Model - -(date|present) - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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. - -Parents - - from may be contained in these elements: period - -See Also - - to. - -Examples - - - - - 26 - December - 1936 - - - - - 14 - January - 2015 - - - - _________________________________________________________________ - -Name - - gpa -- Information about a grade point average - -Synopsis - -Content Model - -(score,possible?,note?) - -Attributes - - Name Type Default - targets CDATA None - type - - Enumeration: - overall - major - overall - -Description - - 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.). - -Parents - - gpa may be contained in these elements: degree - -Attributes - - type - 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. - -Examples - - - 3.78 - 4.00 - This is on a weighted scale. - - - - 3 - - _________________________________________________________________ - -Name - - head -- - - Deprecated - -Synopsis - -Content Model - -(label,uri) - -Attributes - - Name Type Default - targets CDATA None - -Description - -Important - - 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. - -Parents - - head may be contained in these elements: docpath - -Examples - - - _________________________________________________________________ - -Name - - header -- Container for information about the person being described - in a résumé - -Synopsis - -Content Model - -(name,address?,birth?,contact?) - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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. - -Formatting - - The header.format parameter influences the formatting of headers in - all output formats. - -Parents - - header may be contained in these elements: resume - -See Also - - header.format. - -Examples - -
- - Hector - Gomez - -
- 245 San Bernadino - Los Gatos - LX - 94262 -
- - - 30 - April - 1942 - - - - 555-1212 - hector.gomez@xyz.bob - -
- _________________________________________________________________ - -Name - - history -- Container for a person's previous (and possibly current) - jobs - -Synopsis - -Content Model - -(job+) - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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. - -Parents - - history may be contained in these elements: resume - -Examples - - - - Counselor - Shrink Inc. - - August1490 - January1497 - - - - Counseled King Ferdinand and Queen Isabella. Helped to calm their fears - about their large investment in a man named Christopher Columbus. - - - When Columbus returned with gold, I was "downsized" by beheading. - - - - - Angel - Heaven - - January1497 - June2344 - - - - Saved souls. - - - - - Supersonic Vacuum Technician - Joe's Vacuum Shop - - June2344 - - - - - Allowed to return to earth to help my great-great-great-(you get the - picture)-grandson Joe with his business. - - - Repaired hyperdynamic microbial neutron particle accelerators in - Supersonic vacuum models XL144 and XP2000. - - - - - _________________________________________________________________ - -Name - - instantMessage -- An instant message username or address - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - service CDATA None - targets CDATA None - -Description - - 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. - -Parents - - instantMessage may be contained in these elements: contact - -Attributes - - service - Specifies the service that the username or address is to be - used with. Acceptable values are: - - aim - AOL Instant Messenger - - icq - ICQ - - irc - Internet Relay Chat - - jabber - Jabber - - msn - MSN Messenger - - yahoo - Yahoo! Messenger - -See Also - - email. - -Examples - -joesmith - -janedoe - -sammybob@jabber.com - _________________________________________________________________ - -Name - - institution -- A name of an academic institution - -Synopsis - -Content Model - -(#PCDATA|emphasis|citation|url|link)* - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - The institution element specifies the name of a degree-awarding - institution, such as a university, college, or trade school. - -Parents - - institution may be contained in these elements: degree - -Attributes - - id - A string used to uniquely identify an institution. The - institution may then be referred to by this identifier. - -See Also - - organization. - -Examples - - - BA - Daisy Chain Manufacturing - Harvard - - _________________________________________________________________ - -Name - - interest -- Something a person is interested in - -Synopsis - -Content Model - -(title,description?) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The interest element describes something that a person is interested - in. A common use for interest elements is to list hobbies. - -Formatting - - 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. - -Parents - - interest may be contained in these elements: interests - -See Also - - skill. - -Examples - - - Sewing - - - - Seattle Mariners - - I'm a season ticket holder. - GO MARINERS! - - - - For additional examples, see interests. - _________________________________________________________________ - -Name - - interests -- Container for one or more interests - -Synopsis - -Content Model - -(title?,interest+) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The interests element contains one or more interest elements. - -Formatting - - 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. - -Parents - - interests may be contained in these elements: resume - -See Also - - skillarea. - -Examples - - - Hobbies - - Swimming - - - Fine foods - - I do quite well in pie-eating contests. - - - - Australia - - - - - - My belly button - - - Fire ants - - - Fertilizer - - - _________________________________________________________________ - -Name - - job -- A specific employment engagement - -Synopsis - -Content Model - -(jobtitle,employer,location?,(date|period),description?,projects?,achievements? -) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - The job element describes a job, contract, or other employment - engagement. - -Parents - - job may be contained in these elements: history - -Attributes - - id - A string used to uniquely identify a job. The job may then be - referred to by this identifier. - -Examples - - - Sr. VP of Soap Suds Engineering - Proctor and Gamble - - - May - 1982 - - - June - 1988 - - - - - - Dirt - Earth - - - Januaray - 30,000 B.C. - - - - - Provided nutrients, absorbed water, and got tracked into houses. - - - - Grew a 300-ft. tree. - - - - - Took part in the construction of the construction of the Empire State - Building in New York City. (Was excavated from its basement.) - - - - _________________________________________________________________ - -Name - - jobtitle -- A job title - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The jobtitle element specifies the offical title or name of the - position a person held at a job. - -Parents - - jobtitle may be contained in these elements: job - -Examples - - For examples, see job - _________________________________________________________________ - -Name - - keyword -- A keyword to be used for résumé indexing and searching - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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. - -Parents - - keyword may be contained in these elements: keywords - -Examples - - - forward-thinking - self-starter - independent - flexible - - _________________________________________________________________ - -Name - - keywords -- Container for a list of keywords - -Synopsis - -Content Model - -(keyword+) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The keywords element contains one or more keywords. These keywords are - included in the HTML presentation as tags. - -Parents - - keywords may be contained in these elements: resume - -Examples - - For examples, see keyword. - _________________________________________________________________ - -Name - - label -- - - Deprecated - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - -Important - - 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. - -Parents - - label may be contained in these elements: head, node - -Examples - - - _________________________________________________________________ - -Name - - lastModified -- Information about when a résumé was last modified - -Synopsis - -Content Model - -(date) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The lastModified element contains the date that a résumé was last - updated. - -Parents - - lastModified may be contained in these elements: resume - -Examples - - - - 4 - July - 1796 - - - _________________________________________________________________ - -Name - - legalnotice -- A legal statement - -Synopsis - -Content Model - -(para+) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The legalnotice element contains text that is intended to specify the - legal use of a résumé. - -Parents - - legalnotice may be contained in these elements: copyright - -Examples - - For examples, see copyright - _________________________________________________________________ - -Name - - level -- A degree type - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The semantic of the title element vary depending on which element - contains it: - - clearance - When contained in this element, the level element specifies the - level of security clearance that a person has been granted, - such as "Top Secret" or "Restricted". - - degree - When contained in this element, the level element specifies a - degree type, such as "BFA" (bachelor of fine arts) or "Ph.D" - (doctor of philosophy). It typically contains the abbreviation - ("BS") not the full spelling ("bachelor of science"). - -Parents - - level may be contained in these elements: clearance, degree - -Examples - - For examples, see clearance and degree. - _________________________________________________________________ - -Name - - link -- A titled hyperlink - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - href CDATA None - targets CDATA None - -Description - - The link element defines a single hyperlink, much like HTML's a - (anchor) element. - -Formatting - - 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. - -Parents - - link may be contained in these elements: achievement, artTitle, - bookTitle, employer, institution, organization, para, project, - publisher, skill - -Attributes - - href - The URL that the link should point to. then be referred to by - this identifier. - -See Also - - uri, url. - -Examples - - - Acme Corporation - - - - The XML Résumé - Project supplies tools that easily convert a single XML - résumé to multiple output formats. - - _________________________________________________________________ - -Name - - location -- A location, with city-level granularity - -Synopsis - -Content Model - -(city?,(state|province|county)?,country?) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The location element specifies a level location, such as "London, - England", "Seattle, Washington", "St. Louis, Missouri, USA", or - "Newfoundland, Canada". - -Parents - - location may be contained in these elements: degree, job, membership - -See Also - - address. - -Examples - - - Los Angeles - California - USA - - - - Paris - France - - _________________________________________________________________ - -Name - - major -- A main course of study - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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. - -Parents - - major may be contained in these elements: degree - -See Also - - minor. - -Examples - - For examples, see degree. - _________________________________________________________________ - -Name - - membership -- A professional membership - -Synopsis - -Content Model - -(title?,(organization,location?)?,(date|period)?,description?) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - The membership element contains information about a person's - membership in a professional organization. - -Parents - - membership may be contained in these elements: memberships - -Attributes - - id - A string used to uniquely identify a membership. The membership - may then be referred to by this identifier. - -Examples - - For examples, see memberships. - _________________________________________________________________ - -Name - - memberships -- Container for one or more memberships - -Synopsis - -Content Model - -(title,membership+) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The memberships element contains one or more memberships. - -Parents - - memberships may be contained in these elements: resume - -Examples - - - Professional Memberships - - Foobar State Technology Association - - - President - Smallville Internet Developers' Group - - - September - 1998 - - - - - - Founded group and guided its growth from 4 to 150 members. - - - - - _________________________________________________________________ - -Name - - middlenames -- One or more "middle" names of a person - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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. - -Parents - - middlenames may be contained in these elements: name - -See Also - - firstname, surname. - -Examples - -Samione - -Luís Garcia Márquez - _________________________________________________________________ - -Name - - minor -- A minor course of study - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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. - -Parents - - minor may be contained in these elements: degree - -See Also - - major. - -Examples - - For examples, see degree. - _________________________________________________________________ - -Name - - misc -- Miscellaneous remarks - -Synopsis - -Content Model - -(para+) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The misc element contains paragraphs of text that don't fit into any - other top-level categories. - -Parents - - misc may be contained in these elements: resume - -Examples - - - What can't be captured on a résumé is my sheer - level of enthusiasm 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 do their best. - - I'm listed in Who's Who in American - Restaurants as well as La - Rubachòn. - - - _________________________________________________________________ - -Name - - month -- A month name - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The month element contains the name of a month, such as "March" - (English), "marzo" (Spanish), or "mars" (French). - -Parents - - month may be contained in these elements: date, pubDate - -See Also - - dayOfMonth, year. - -Examples - -April - _________________________________________________________________ - -Name - - name -- A person's name - -Synopsis - -Content Model - -(title?,firstname,middlenames?,surname,suffix?) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - The name element contains a person's name. - -Parents - - name may be contained in these elements: copyright, header, referee - -Attributes - - id - A string used to uniquely identify a name. The name may then be - referred to by this identifier. - -Examples - - - Mr. - John - Q. - Doe - - - - Joe - Sam George Bob - Flamboyzo - Jr. - - - - King - Louis - VIII - - _________________________________________________________________ - -Name - - node -- - - Deprecated - -Synopsis - -Content Model - -(label,uri) - -Attributes - - Name Type Default - targets CDATA None - -Description - -Important - - 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. - -Parents - - node may be contained in these elements: docpath - -Examples - - - _________________________________________________________________ - -Name - - note -- Additional information - -Synopsis - -Content Model - -(para+) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The note element contains additional information about its parent - element. - -Parents - - note may be contained in these elements: academics, clearance, gpa - -See Also - - annotation, legalnotice. - -Examples - - - - ... - - - - I take education very seriously. After all, I'm in 37th grade now! - - - - _________________________________________________________________ - -Name - - objective -- A person's employment goal - -Synopsis - -Content Model - -(para+) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - 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. - -Parents - - objective may be contained in these elements: resume - -Attributes - - id - A string used to uniquely identify an objective. The objective - may then be referred to by this identifier. - -Examples - - - - I seek a high-paying job in the golf playing industry. I would like at - least 20 weeks of vacation per year. - - - _________________________________________________________________ - -Name - - organization -- A name of an organization - -Synopsis - -Content Model - -(#PCDATA|emphasis|citation|url|link)* - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - The organization element contains the name of a professional or other - type of organization. - -Parents - - organization may be contained in these elements: award, clearance, - membership, referee - -Attributes - - id - A string used to uniquely identify an organization. The - organization may then be referred to by this identifier. - -See Also - - institution. - --> - -Examples - - - Croquet Players' Association of the UK - - _________________________________________________________________ - -Name - - pageNums -- One or more page numbers or ranges - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The pageNums element specifies one or more page numbers or ranges of - page numbers, and is used in citing a publication. - -Parents - - pageNums may be contained in these elements: pub - -Examples - - - Ancient Mayan Anthropology - Nature - 13-54 - - - - The New Fad: Bottle Cap Collecting - Time Magazine - 14 - - _________________________________________________________________ - -Name - - pager -- A pager telephone number - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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.) - -Parents - - pager may be contained in these elements: contact - -See Also - - email, fax, phone. - -Examples - -456-145-4468 - -736.272.4673 x 235 - _________________________________________________________________ - -Name - - para -- A paragraph of text - -Synopsis - -Content Model - -(#PCDATA|emphasis|citation|url|link)* - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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. - -Parents - - para may be contained in these elements: description, legalnotice, - misc, note, objective, pub - -Examples - - - This is a boring paragraph. - - - - I like to emphasize my words; in fact, I've written an - article on the topic. It is published on the Really - Exciting WRITING! web site at - http://www.really-exciting-writing.bob/EMPHASIS.html. - - _________________________________________________________________ - -Name - - period -- A period of time - -Synopsis - -Content Model - -(from,to) - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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. - -Parents - - period may be contained in these elements: award, clearance, degree, - job, membership - -See Also - - element. - -Examples - - - - 10 - February - 1246 - - - 19 - November - 1351 - - - - - - May - 1985 - - - - - - _________________________________________________________________ - -Name - - phone -- A voice telephone number - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - location - - Enumeration: - home - work - mobile - None - targets CDATA None - -Description - - 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 - -Parents - - phone may be contained in these elements: contact - -Attributes - - location - Indicates the location that the phone number connects to. This - attribute is optional. - -See Also - - address, email, fax, pager. - -Examples - -555.555.1212 - -345-262-4567 - -(261) 345-1616 - - For additional examples, see contact. - _________________________________________________________________ - -Name - - possible -- The highest possible score in a GPA - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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. - -Parents - - possible may be contained in these elements: gpa - -See Also - - score. - -Examples - - For examples, see gpa. - _________________________________________________________________ - -Name - - postalCode -- A postal code - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - 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. - -Parents - - postalCode may be contained in these elements: address - -See Also - - zip. - -Examples - - A Brazilian postal code: -85070-200 - - A Canadian postal code: -V2B 5S8 - _________________________________________________________________ - -Name - - prefecture -- A name of a prefecture or other administrative district - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - 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. - -Parents - - prefecture may be contained in these elements: address - -Attributes - - id - A string used to uniquely identify a prefecture. The prefecture - may then be referred to by this identifier. - -See Also - - city, county, state, suburb, ward. - -Examples - -Basilius - _________________________________________________________________ - -Name - - present -- Indicates the current time - -Synopsis - -Content Model - -EMPTY - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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 . - -Parents - - present may be contained in these elements: from, to - -See Also - - date. - -Examples - - - - May - 1995 - - - - - - _________________________________________________________________ - -Name - - project -- Container for information about a project - -Synopsis - -Content Model - -(#PCDATA|emphasis|citation|url|link)* - -Attributes - - Name Type Default - targets CDATA None - title CDATA None - -Description - - The project element describes a project that a person participated in - at a job. - -Parents - - project may be contained in these elements: projects - -Attributes - - title - The title of the project. - -See Also - - achievement. - -Examples - - For examples, see projects. - _________________________________________________________________ - -Name - - projects -- Container for one or more projects - -Synopsis - -Content Model - -(project+) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The projects element groups together one or more project elements. - -Parents - - projects may be contained in these elements: degree, job - -See Also - - achievements. - -Examples - - - Organization of Paperclips - Development of rocket booster fuel - 1997 Papercut Convention - - _________________________________________________________________ - -Name - - province -- A name or abbreviation of a province - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - The province element contains the name or abbreviation of a single - province or similar political division. - -Parents - - province may be contained in these elements: address, location - -Attributes - - id - A string used to uniquely identify a province. The province may - then be referred to by this identifier. - -See Also - - county, state. - -Examples - -Saskatchewan - -BC - _________________________________________________________________ - -Name - - pub -- A work published by the résumé "owner" - -Synopsis - -Content Model - -(para|(artTitle|bookTitle|author|date|pubDate|publisher|pageNums|url))* - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - 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. - -Parents - - pub may be contained in these elements: pubs - -Attributes - - id - A string used to uniquely identify a publication. The - publication may then be referred to by this identifier. - -See Also - - citation. - -Examples - - Example 4. Book with multiple authors - - Foundations of Computer Science, C Edition - Alfred V. Aho - Jeffrey D. Ullman - - 1995 - - Computer Science Press, New York - - - Example 5. Magazine article - - Low-Fat Philly Cheese Steaks - Healthy Cooking - Joe Sixpack - - June - 1999 - - Healthy Publishing Group - - _________________________________________________________________ - -Name - - pubDate -- The date a work was published - - Deprecated - -Synopsis - -Content Model - -(month?,year) - -Attributes - - Name Type Default - targets CDATA None - -Description - -Important - - 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. - -Parents - - pubDate may be contained in these elements: pub - -See Also - - date. - -Examples - - - How to Drink Water for Fun and Profit - - 1996 - - - - - Modern Neo-Classical Baroque Music - Journal of Classical Music - - July - 1931 - - - _________________________________________________________________ - -Name - - publisher -- Information about a publisher of a work - -Synopsis - -Content Model - -(#PCDATA|link|url)* - -Attributes - - Name Type Default - targets CDATA None - -Description - -Important - - 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. - -Parents - - publisher may be contained in these elements: pub - -Examples - - Example 6. Publisher name only - - Deep Thoughts on Stuff - Totally Groovy Publishing, Ltd. - - - Example 7. Publisher name and location - - A User's Guide to Dirt - Mother Nature Books, Boston, Massachusetts - - _________________________________________________________________ - -Name - - pubs -- A group of one or more publications - -Synopsis - -Content Model - -(pub+) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The pubs element groups together one or more publications. - -Parents - - pubs may be contained in these elements: resume - -Examples - - - - General Relativity for Idiots - Einstein - - - String Theory for Dummies - Topics in Physics - Stephen Hawking - - - _________________________________________________________________ - -Name - - referee -- Someone who can provide additional information about the - person the résumé describes - -Synopsis - -Content Model - -(name,title?,organization?,address?,contact?) - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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. - -Formatting - - The display of referee is influenced by the referees.display - parameter. - -Parents - - referee may be contained in these elements: referees - -Examples - - - Joe -
- 123 Main St. - Anytown - ST - 12345 - USA -
- - 123.456.7890 - joe@hotmail.bob - - - - For additional examples, see referees. - _________________________________________________________________ - -Name - - referees -- Contains one or more referees - -Synopsis - -Content Model - -(referee+) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The referees element groups together one or more referee elements. - -Parents - - referees may be contained in these elements: resume - -Examples - - - - Mr. Samuel J. Black - - 555.555.1212 - - - - Mom - - my_mommy@moms.bob - - - - Dad - - - _________________________________________________________________ - -Name - - result -- An outcome of a subject - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The result element describes the outcome or result of a subject. - result often contains the letter or numeric grade awarded for an - academic class. - -Parents - - result may be contained in these elements: subject - -Examples - - - - Math - A- - - - English - C - - - Science - B+ - - - Spanish - B - - - _________________________________________________________________ - -Name - - resume -- A résumé or curriculum vitae - -Synopsis - -Content Model - -(docpath?,header?,((objective|history|academics|skillareas|skillarea|pubs|misc| -referees|keywords|memberships|interests|clearances|awards))*,lastModified?,copy -right?) - -Attributes - - 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 - -Description - - 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. - -Parents - - resume may be contained in these elements: resumes - -Attributes - - id - A string used to uniquely identify a résumé. The résumé may - then be referred to by this identifier. - -Examples - - - -
- - Harry - Potter - -
- 4 Privet Drive - Little Whinging - Surrey - RO51 5NF - UK -
-
- - - To defeat Lord Voldemort once and for all, then to become an Auror - for the Ministry of Magic. - - - - Magical Skills - - Charms - Levitation - Cheering - Summoning - Banishing - - - Spells and Curses - Unlocking Spell - Patronus Spell - Stunning Spell - Disarming Spell - Reductor Curse - Impediment Curse - Imperious Curse Evasion - - - Potions - Polyjuice - Enlarging - Antidotes - - - Flying - High-speed - Wronski Feint - Steep dives - Bludger Evasion - No-hands - High-altitude - - - Languages - English - Parsel Tounge - Troll (point and grunt) - - - - Muggle Skills - - Daily Life - Telephone - Mailbox - Riding in cars - Electric lights - Hammering - - - Camping - Setting up tents - Lighting Matches - - - - - - Student - Hogwarts - - - - September - ca. 1995 - - - - - - - - - On Gryffindor House Quidditch team four years running - - - Quidditch Cup - - Youngest Seeker in a century - - Faced Lord Voldemort four times and lived. - - - - - De-gnomer - Mrs. Weasley - - - - August - ca. 1995 - - - - - August - ca. 1995 - - - - - Removed gnomes from the Weasleys' garden. - - - - - - - - Fourth Year - Wizarding - Hogwards School of Witchcraft and Wizardry - - - Transfiguration - B - - - Charms - A- - - - Defense Against the Dark Arts - A - - - Potions - D - - - Care of Magical Creature - A+ - - - Divination - B - - - - - - - - School Clubs - - Dueling Club - Trained in wizard dueling, with focus on - disarming. - - - Secretary - Society for the Protection of Elfish Workers - (S.P.E.W.) - - - - - Cho Chang - - - - - - Minerva - McGonagall - -
Hogwarts School of Witchcraft and Wizardry -Via Owl Post
- - - - Albus - Dumbledore - -
Hogwarts School of Witchcraft and Wizardry -Via Owl Post
- - - - - - For additional examples, look at the sample résumés in the examples - directory of the XML Résumé Library distribution. - _________________________________________________________________ - -Name - - resumes -- A collection of one or more résumés - -Synopsis - -Content Model - -(resume*) - -Attributes - - 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 - -Description - - 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. - -Parents - - resumes may be contained in these elements: None - -Attributes - - id - A string used to uniquely identify a group of résumés. The - résumés may then be referred to by this identifier. - -Examples - - - -
- - Bill - Gates - -
- - -
- - Steve - Jobs - -
- - - _________________________________________________________________ - -Name - - score -- The score earned in a GPA - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The score element contains the GPA score that a person has earned. - -Parents - - score may be contained in these elements: gpa - -See Also - - possible. - -Examples - - For examples, see gpa. - _________________________________________________________________ - -Name - - skill -- A name and/or description of a skill - -Synopsis - -Content Model - -(#PCDATA|emphasis|citation|url|link)* - -Attributes - - Name Type Default - id ID None - level CDATA None - targets CDATA None - -Description - - The skill element describes something that a person is skilled at. - -Parents - - skill may be contained in these elements: skills, skillset - -Attributes - - level - The level attribute indicates a person's level of proficiency - at a skill. "Level of proficiency" may be expressed in any - manner, such as "3 years" (three years of experience with a - particular skill), "expert", or "7/10". The - skills.level.display parameter determines whether or not skill - levels are displayed in formatted output. - -See Also - - achievement, skills.format, skills.level.display. - -Examples - -Singing - -Java Programming - -Eating - - - Throwing large objects - - _________________________________________________________________ - -Name - - skillarea -- A group of broadly related skill sets - -Synopsis - -Content Model - -(title,skillset+) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - 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. - -Formatting - - 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. - -Parents - - skillarea may be contained in these elements: resume, skillareas - -Attributes - - id - A string used to uniquely identify a skill area. The skill area - may then be referred to by this identifier. - -Examples - - Example 8. Broad skill area - - Skills - - - Computers - Typing (150 WPM!!) - Dropping little food crumbs in keyboards - - - - Writing - Editing - Cursive - - - - Example 9. More focused skill area - - Financial Skills - - - Investing - Stocks - Bonds - Money market accounts - Retirement accounts - - - - Bookkeeping - Amortization - Loan schedules - Book balancing - - - - Advising - Retirement investment - College investment - Philanthropy - - - _________________________________________________________________ - -Name - - skillareas -- Group of one or more skill areas - - Deprecated - -Synopsis - -Content Model - -(skillarea+) - -Attributes - - Name Type Default - targets CDATA None - -Description - -Important - - 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é. - -Parents - - skillareas may be contained in these elements: resume - -Examples - - - - Aviation - - Piloting - Biplanes - Jumbo Jets - Space Shuttle - - - Navigation - Map and charts - Instruments - Stars - - - - - Cleaning - - Tools - Rag - Sponge - Towel - - - Chemicals - Bleach - Water - Soap - - - - _________________________________________________________________ - -Name - - skills -- Group of one or more skills - - Deprecated - -Synopsis - -Content Model - -(skill+) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - -Important - - 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. - -Parents - - skills may be contained in these elements: skillset - -Attributes - - id - A string used to uniquely identify a skills group. The group - may then be referred to by this identifier. - -See Also - - skills.format. - -Examples - - - Leaping over tall buildings in a single bound - Flying - Quickly changing clothes - - _________________________________________________________________ - -Name - - skillset -- A titled group of one or more related skills - -Synopsis - -Content Model - -(title?,(skill+|skills)) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - The skillset element contains a titled set of (usually closely) - related skills. - -Formatting - - The skills.format parameter controls the formatting of skill sets. - -Parents - - skillset may be contained in these elements: skillarea - -Attributes - - id - A string used to uniquely identify a skill set. The skill set - may then be referred to by this identifier. - -Examples - - - Eating Utinsels - Knife - Fork - Spoon - Soup Spoon - - _________________________________________________________________ - -Name - - state -- A name or abbreviation of a state - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - 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. - -Parents - - state may be contained in these elements: address, location - -Attributes - - id - A string used to uniquely identify a state name. The name may - then be referred to by this identifier. - -See Also - - province, county, prefecture. - -Examples - - Example 10. State name -New York - - Example 11. State abbreviation -NY - _________________________________________________________________ - -Name - - street -- A street name, number, and other related information - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - 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. - -Parents - - street may be contained in these elements: address - -Attributes - - id - A string used to uniquely identify a street. The street may - then be referred to by this identifier. - -Examples - - For examples, see address. - _________________________________________________________________ - -Name - - street2 -- A second line of a street address - - Deprecated - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - -Important - - 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. - -Parents - - street2 may be contained in these elements: address - -Attributes - - id - A string used to uniquely identify the second line of a street - address. The line may then be referred to by this identifier. - -See Also - - street. - -Examples - - None. - _________________________________________________________________ - -Name - - subject -- A name of a class or topic of study - -Synopsis - -Content Model - -(title,result) - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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). - -Parents - - subject may be contained in these elements: subjects - -Examples - - - English - A- - - - - PE 194 Crabwalking - F - - _________________________________________________________________ - -Name - - subjects -- A group of one or more subjects - -Synopsis - -Content Model - -(subject+) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The subjects element contains one or more subjects that were studied - as part of the degree represented by the parent of the subjects. - -Parents - - subjects may be contained in these elements: degree - -Examples - - - - Chemistry - C - - - Physics - B- - - - _________________________________________________________________ - -Name - - suburb -- A name of a suburb - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - The suburb element contains the name of a suburb, as used by a postal - service to deliver mail. - -Parents - - suburb may be contained in these elements: address - -Attributes - - id - A string used to uniquely identify a suburb. The suburb may - then be referred to by this identifier. - -See Also - - city, prefecture, ward. - --> - -Examples - - Example 12. A New Zealand Address -
- 236 Majoribanks Street - Mount Victoria - Wellington - 6001 - New Zealand -
- _________________________________________________________________ - -Name - - suffix -- A suffix of a name, usually specifying lineage - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The suffix element contains a suffix or suffix abbreviation that - follows a name, such as "Jr.", "Senior", or "III". - -Parents - - suffix may be contained in these elements: name - -Examples - - - Leonard - Scott Quink - Waggenblast - IV - - - - Dolores - Sanchez - Jr. - - _________________________________________________________________ - -Name - - surname -- A family name - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The surname element contains a person's family, or last name. - -Parents - - surname may be contained in these elements: name - -Examples - - For examples, see name. - _________________________________________________________________ - -Name - - tail -- - - Deprecated - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - -Important - - 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. - -Parents - - tail may be contained in these elements: docpath - -Examples - - - _________________________________________________________________ - -Name - - title -- A title or heading - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The title element contains a title or heading. Its semantics vary - depending on the element that contains it: - - name - When contained in this element, title contains a person's - formal title, such as "Dr.", "Ms.", or "Professor". - - interest - When contained in this element, title contains the name of an - interest, such as "Cooking", or "Politics". - - membership, referee - When contained in these elements, title contains the name of - the person's role or capacity withing an organization. - Examples: "Treasurer", "Member", "Chief Officer of Toothpaste - Policy", "Lead Programmer". - - awards, interests, memberships, skillarea - When contained in these elements, title contains a heading for - that section of a résumé. It is formatted as a top-level - heading. - -Note - - The title element is optional in awards and interests. If it is - not present, the awards.word and interests.word parameters will - be used as the heading text in formatted résumés, respectively. - - skillset - When contained in this element, title contains the name of a - skill category. Examples: "Teaching", "Computers", - "Woodworking", "Soap Carving". - - subject - When contained in this element, title contains the name of a - subject. It can be as general as "English" (a very broad field - of study), or as specific as "Eng 115 Intro to Writing Fall - 2001" (a specific university course name, number, and date of - study). - -Parents - - title may be contained in these elements: award, awards, clearances, - interest, interests, membership, memberships, name, referee, - skillarea, skillset, subject - -See Also - - artTitle, bookTitle. - -Examples - - Example 13. interest title - - Fly fishing for sharks - - I once caught a 300-kg. Great White off the coase of Florida using a green - and gold-colored dragonfly that I tied. - - - - Example 14. membership and memberships titles - - Professional Memberships - - American Society of Blower-Uppers - - - Spokesperson - Smallville Demolitioneers - - - President - Willow County Pyrotechnicans' Guild - - - - Example 15. skillarea and skillset titles - - Computer Skills - - Word Processing - Microsoft Word - Corel WordPerfect - - - Programming - Perl - Python - XML - C++ - - - - Example 16. subject title - - Intro to Sociology - A- - - _________________________________________________________________ - -Name - - to -- The ending point in a period of time - -Synopsis - -Content Model - -(date|present) - -Attributes - - Name Type Default - targets CDATA None - -Description - - 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. - -Parents - - to may be contained in these elements: period - -See Also - - from. - -Examples - - For examples, see from and period. - _________________________________________________________________ - -Name - - uri -- A Uniform Resource Indicator - - Deprecated - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - -Important - - 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. - -Parents - - uri may be contained in these elements: head, node - -Examples - - - _________________________________________________________________ - -Name - - url -- A Uniform Resource Locator - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - -Important - - 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. - -Formatting - - 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). - - HTML - 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. - - FO/PDF - 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. - - Plain text - Formatted as the value of the element. - -Parents - - url may be contained in these elements: achievement, contact, - employer, institution, organization, para, project, pub, publisher, - skill - -See Also - - link. uri. - -Examples - - - The Apache XML Project web page is located at - http://xml.apache.org/. - - - - Python (see http://www.python.org/) - - _________________________________________________________________ - -Name - - ward -- A name of a division of a city, town, or county - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - 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. - -Parents - - ward may be contained in these elements: address - -Attributes - - id - A string used to uniquely identify a ward. The ward may then be - referred to by this identifier. - -See Also - - county, prefecture, suburb. - -Examples - -
- Rua Afonso Camargo, 805 - Santana - Guarapuava - PR - 85070-200 - Brazil -
- _________________________________________________________________ - -Name - - year -- A year - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - targets CDATA None - -Description - - The year element contains a year number, along with a possible string - that identifies the date system, such as "B.C." or "A.D.". - -Parents - - year may be contained in these elements: copyright, date, pubDate - -Examples - -1995 - -240 A.D. - _________________________________________________________________ - -Name - - zip -- A zip code - -Synopsis - -Content Model - -(#PCDATA) - -Attributes - - Name Type Default - id ID None - targets CDATA None - -Description - - 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. - -Parents - - zip may be contained in these elements: address - -Attributes - - id - A string used to uniquely identify a zip code. The zip code may - then be referred to by this identifier. - -See Also - - postalCode. - -Examples - - For examples, see address. - -XSL Parameter Reference - _________________________________________________________________ - - 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 - css.href - indicates the CSS stylesheet to use to format HTML output - header.format - controls formatting of the header element - interest.description.format - controls formatting of interest - descriptions - - referees.display - Determines whether or not referees are visible in - formatted output - - skills.format - controls formatting of the skillset element - skills.level.display - Determines whether or not skill level - attributes are visible in formatted output - - subjects.format - controls formatting of the subjects element - -Name - - address.format -- controls default formatting of the address element - -Applies To - - This parameter controls the formatting of the address element in all - output formats. - -Possible Values - - Possible values include standard (the default), european, and italian. - -Note - - In the examples below, means the value of XML element - , if defined. means the value of XML element - , if defined, otherwise the value of XML element , - otherwise blank. - - standard - Formats addresses in North American layout: - - - - - , - - - european - Formats addresses in European layout: - - - - - , - - italian - Formats addresses in Italian layout: - - - - () - - - 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: -
Sr. Héctor García Marizó -Reina #35, apt. 4a, e/ Gervasio y Escobar -Ciudad de La Habana, CP 11900 -CUBA
- _________________________________________________________________ - -Name - - css.href -- indicates the CSS stylesheet to use to format HTML output - -Applies To - - This parameter applies to only the HTML output format. - -Possible Values - - 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. - _________________________________________________________________ - -Name - - header.format -- controls formatting of the header element - -Applies To - - 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 - - Possible values include standard (the default) and centered. - - standard - 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. - - centered - 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/ - _________________________________________________________________ - -Name - - interest.description.format -- controls formatting of interest - descriptions - -Applies To - - This parameter controls the formatting of the description element when - it is contained in an interest. It affects all output formats. - -Possible Values - - Possible values include single-line and block. single-line is the - default. - - The examples below demonstrate the formatting of this XML fragment: - - - 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. - - - - - single-line - This value is the default. Formats all of the para elements in - the description on the same logical line as the interest title. - The title is separated from the description by a period, and - the description paragraphs are separated from each other by - description.para.separator.text, which defaults to an em-dash - ("--"). - - For example, the XML above would be formatted similar to the - following: - -Interests - - + Scuba diving - + Flying. I have my pilot's license, and have logged over 1000 - in-flight hours. -- I have also constructed my own airplane - from a kit. - - block - Formats each of the para elements in the description as a - separate block below the interest title. - - For example, the XML above would be formatted similar to the - following: - -Interests - - + 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. - _________________________________________________________________ - -Name - - referees.display -- Determines whether or not referees are visible in - formatted output - -Applies To - - This parameter controls the formatting of the referee element in all - output formats. - -Possible Values - - Possible values include 1 (display referees) and 0 (display alternate - text). - - 1 (true) - Referees are displayed in formatted output. - - 0 (false) - The text of the referees.hidden.phrase parameter (default: - Available upon request.) is displayed in place of referees. - _________________________________________________________________ - -Name - - skills.format -- controls formatting of the skillset element - -Applies To - - This parameter controls the formatting of the skillset element in all - output formats. - -Possible Values - - Possible values include bullet (the default) and comma. - - The examples below show how a like this would be rendered: - - Technical Skills - - Programming Languages - Java - C++ - C - perl - - - - bullet - Formats skills as a bulleted list, one skill per line: - -Technical Skills - -Programming Languages - - + Java - + C++ - + C - + Perl - - comma - Produces a comma-separated list on a single line: - -Technical Skills - - Programming Languages: Java, C++, C, Perl - _________________________________________________________________ - -Name - - skills.level.display -- Determines whether or not skill level - attributes are visible in formatted output - -Applies To - - This parameter controls the formatting of the level attribute of skill - elements in all output formats. - -Possible Values - - Possible values include 1 (display the attribute) or 0 (suppress the - attribute). - - 1 (true) - level attributes of skills are displayed after all of the rest - of the content of the skill. The level is displayed surrounded - by skills.level.start and skills.level.end (parenthesis, by - default). - - 0 (false) - level attributes contained in skills are suppressed; they are - treated as if the didn't exist for formatting purposes. - _________________________________________________________________ - -Name - - subjects.format -- controls formatting of the subjects element - -Applies To - - This parameter controls the formatting of the subjects element in all - output formats. - -Possible Values - - Possible values include comma (the default) and table. - - The examples below show how a section like this would be - rendered: - - - English - C - - - Science - A - - - Math - B- - - - - comma - Produces a comma-separated list on a single line: - - Subjects: English (C), Science (A), Math (B-). - - table - Produces a table, with subject name in the first column and - result in the second column: - -Subjects - - English C - Science A - Math B- - -Chapter 3. CSS Class Reference - - Table of Contents - - Overview - - 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. - -Overview - - 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é. - -Glossary - - attribute - 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: - - - - - element - An element of an XML document that defines an "object", such as - or . HTML tags are examples of elements. - Additionally, elements can have attributes. Elements have a - start (or "open") tag (e.g., ) and an end (or - "close") tag (e.g., ). - - Each element (except for the root ) has exactly one - parent element and 0 or more child elements. - - parent element - The element whose start tags and end tags surround a given - element. - - child element - Any element positioned between the start tags and end tags of a - given element. - -Appendixes - - Table of Contents - - A. GNU Free Documentation License - - PREAMBLE - APPLICABILITY AND DEFINITIONS - VERBATIM COPYING - COPYING IN QUANTITY - MODIFICATIONS - COMBINING DOCUMENTS - COLLECTIONS OF DOCUMENTS - AGGREGATION WITH INDEPENDENT WORKS - TRANSLATION - TERMINATION - FUTURE REVISIONS OF THIS LICENSE - How to use this License for your documents - -Appendix A. GNU Free Documentation License - - Table of Contents - - PREAMBLE - APPLICABILITY AND DEFINITIONS - VERBATIM COPYING - COPYING IN QUANTITY - MODIFICATIONS - COMBINING DOCUMENTS - COLLECTIONS OF DOCUMENTS - AGGREGATION WITH INDEPENDENT WORKS - TRANSLATION - TERMINATION - FUTURE REVISIONS OF THIS LICENSE - How to use this License for your documents - - 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. - -PREAMBLE - - 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. - -APPLICABILITY AND DEFINITIONS - - 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. - -VERBATIM COPYING - - 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. - -COPYING IN QUANTITY - - 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. - -MODIFICATIONS - - 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: - A. 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. - B. 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). - C. State on the Title page the name of the publisher of the Modified - Version, as the publisher. - D. Preserve all the copyright notices of the Document. - E. Add an appropriate copyright notice for your modifications - adjacent to the other copyright notices. - F. 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. - G. Preserve in that license notice the full lists of Invariant - Sections and required Cover Texts given in the Document's license - notice. - H. Include an unaltered copy of this License. - I. 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. - J. 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. - K. 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. - L. 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. - M. Delete any section entitled "Endorsements". Such a section may not - be included in the Modified Version. - N. 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. - -COMBINING DOCUMENTS - - 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." - -COLLECTIONS OF DOCUMENTS - - 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. - -AGGREGATION WITH INDEPENDENT WORKS - - 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 - - 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. - -TERMINATION - - 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. - -FUTURE REVISIONS OF THIS LICENSE - - 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. - -How to use this License for your documents - - 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. diff --git a/legacy-resumes/resume-1/doc/news/index.html b/legacy-resumes/resume-1/doc/news/index.html deleted file mode 100644 index eea4303..0000000 --- a/legacy-resumes/resume-1/doc/news/index.html +++ /dev/null @@ -1,424 +0,0 @@ - - - - XML Resume Library News - - - -

XML Résumé Library News

- -

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. -

- -

Release 1.5.1

-
    -
  • Added Ant support (build.xml) to examples
    • -
  • Default output format for referees is now 2-column
    • -
  • Fixed a bug that caused some JVM crashes while processing text output
    • -
  • Improved internationalization support
    • -
  • DTD fixed to support validation of XML files that use the "targets" attribute
    • -
  • Small CSS improvements
    • -
  • NEW: Online Resume Converter (ORC)
    • -
- -

Release 1.5.0

- -
    -
  • Added support for targeted résumés. This allows - the user to selectively filter out irrelevant elements and focus - the résumé to a particular purpose. A - demonstration of this feature is included in - example/example2.xml
    • -
  • Cascading Style Sheets (CSS) now default to being embedded - directly into the HTML output, which makes it easier to - email/transfer a résumé. Thanks to Luciano Cardoso - for the suggestion and hint.
    • -
  • Decreased the default margins to conserve space and trees - (PDF output)
    • -
  • Referees can now be listed in a 2-column table in the PDF and HTML - output. This behavior is off by default.
    • -
  • Italian, French, Spanish, and Brazilian translations have been - improved/fixed. (Thanks to Didier Cassirame, Gilles - Sadowski, Luciano Cardoso, and Miguel Coca)
    • -
  • Localization support for the fax and phone elements has been - improved. The home.word, mobile.word, and work.word params have - been replaced by phone.home.phrase, phone.mobile.phrase, and - phone.work.phrase (same applies to fax) that can support arbitrary - orderings (eg, Mobile Phone in UK, GSM in French, Cellphone in US). - Default translations for some languages may be incomplete, so please - send in translations via SourceForge's Patch Request forms. - (Bugs 624365, 629607)
    • -
  • Makefile support (in the 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)
    • -
  • The project element can now have a "title" attribute.
    • -
  • The "date" element can now be used in place of "period" for - the "membership" and "job" elements, and period can be used in - in place of date in the award and clearance tags
    • -
- -

Release 1.4.2

- -
    -
  • Fixed a bug that caused unexpected line breaks in text output (bug - 566653).
    • -
  • Decreased the default width of text output from 80 to 72 characters. - This allows them to be transmitted in most e-mail programs without - wrapping the very last part of each line.
    • -
  • Added support for comma-separated formatting of degree subjects. This - is now the default. (Thanks to Mark Miller.)
    • -
  • Comma-formatted skill lists in text output format are now terminated - with a period (feature request 575845).
    • -
  • Added a new CSS stylesheet, 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.)
    • -
- -

Release 1.4.1

- -
    -
  • The output stylesheets (us-html.xsl, - br-a4.xsl, etc.) are now in the xsl/output - directory. (They were previously in the xsl directory.
    • -
  • New elements: - <clearances> - and - <clearance>. - These elements may be used to note security clearances that you may - have. - (Feature request 556633.)
    • -
  • New elements: - <gpa>, - <score> - and - <possible>. - You can use these tags to include a GPA in a degree. - résumé. - (Feature request 560641.)
    • -
  • New element: - <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. -
    • -
  • Added Dutch language support, thanks to Andre van Dijk.
    • -
  • New CSS stylesheet: resume4.css.
    • -
- -

Release 1.4.0

- -
    -
  • New elements: - <awards> - and - <award>. - You can use these tags to include awards or other honors in a - résumé. - (Feature request 548619.)
    • -
  • New elements: - <interests> - and - <interest>. - You can use these tags to include your interests or hobbies in a - résumé. - (Feature request 504269.)
    • -
  • New elements: - <fax>, - <pager>, - and - <instantMessage> - (feature requests 485930 and 522200).
    • -
  • New element: - <minor> - (feature request 558871).
    • -
  • New element: - <lastModified> - (feature request 460165).
    • -
  • Deprecated elements: - <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).
    • -
  • Added Portuguese language support, thanks to Felipe Leme.
    • -
  • Added German language support, thanks to Jochen Hein (feature request - 522570).
    • -
  • References may now be replaced by alternate text in formatted output - with the referees.display parameter.
    • -
  • A new CSS stylesheet is included: resume3.css
    • -
  • Fixed bug 547663: only the last skill in a list of skills was - formatted when the skills.format parameter was set to - comma.
    • -
  • New chapter in the user guide: Converting an XML - Résumé to Other Formats
    • -
- -

Release 1.3.3

- -
    -
  • User guide now included!
    • -
  • Namespaces are supported and used within the stylesheets.
    • -
  • We're now compatible with the XSL-FO standard and FOP version 0.20.3.
    • -
  • New <link> element to support hyperlinks to employers.
    • -
- -

Release 1.3.2

- -

Bug fix release:

- -
    -
  • Fixed bug 509432: formatting of academic degrees exhibited - bizarre punctuation and spacing depending on what combination - of date, institution, subjects, and annotation were present. - It's clean now for all combinations. -
    • -
  • Fixed bug 513515: space for the subject name in an academic - degree is significantly wider now. -
    • -
- -

Release 1.3.1

- -

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. -

- -

Release 1.3.0

- -
    -
  • Schema Change! The - <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. -

    -
    • -
  • The <name> under a - <copyright> is now optional. If omitted, - the name will be taken from the <header>. -
    • -
  • You can specify whether HTML and plain text headings should - be standard (flush left) or centered with the - header.format parameter. -
    • -
  • You can format skill sections as bullet lists or - comma-separated lists with the skills.format - parameter. -
    • -
  • We've simplified international addresses using a setting for - the address.format parameter and also by allowing - freeform addresses. -
    • -
  • You can now list and format professional memberships on your - résumé with the <memberships> - element. -
    • -
  • You can list subjects and levels achieved under each degree - with the <subjects> element. Subjects are - formatted for print and web, but not yet for text. -
    • -
  • You can list personal references with the - <referees> element. -
    • -
  • Many elements contain unique id attributes - now. You can use the name attribute in an - <author> element to refer to a publication - author by id. -
    • -
  • You can list projects at a job with the new - <projects> element. -
    • -
  • The graduation <date> on a degree is - optional now. -
    • -
  • There's an SGML catalog file now.
    • -
  • The new XSL paramater half.space is used for a - smaller amount of space between certain types of paragraphs. -
    • -
  • The plain text formatting cleans up extra newlines when - certain parts of the resume or the titles are empty. It also - wraps long lists of items cleanly. -
    • - -
- -

Additionally, we've fixed some bugs in the XSL files.

- -

Release 1.2.4

- -

Bugs fixed:

-
    -
  • Old style US addresses in HTML were coming out - "City,State". Now there's a space after the comma: - "City, State". -
    • -
  • The <dayOfMonth> was missing a content - model; it has one now (PCDATA). -
    • -
  • <fullDate> wasn't referenced anywhere. - It's gone. -
    • -
  • The plain text stylesheet text.xsl - contained an invalid template that Xalan allowed but 4Suite - correctly disallowed. That's fixed now. -
    • -
  • The HTML output explicitly sets the character set to - UTF-8. -
    • -
  • Bullet lists in the text formatting have been greatly - improved. -
    • -
  • No more blank labels for telephone or email when there's no - telephone or email specified. -
    • -
  • The homepage URL now appears in the HTML formatting. -
    • -
-

New features:

-
    -
  • Each job in the employment history may now contain a list of - achievements, which become formatted as a bullet-list. -
    • -
  • Achievements and skills now use the same markup model as - plain paragraphs, enabling richer semantics. -
    • -
  • Real en-dashes appear in periods of employment - in the FO rendering. -
    • -
  • Hyphens in the FO rendering separating employer, job title, - and period of employment use bullets now (those hyphens looked - funny). -
    • -
  • HTML output now includes Cascading Stylesheet (CSS) "class" - attributes, enabling you to customize the HTML appearance of - your résumé. Two sample stylesheets, - resume1.css and resume2.css are in - the css directory. -
    • -
- -

Release 1.2.3

- -
    -
  • Internationalization support. The DTD and - the stylesheets support formatting international addresses - with a rich set of metadata. See the - 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! -
    • - -
  • Localization support. We've replaced - hard-coded words like "Professional Objective" and - "résumé" as well as paper sizes and margins with - configurable parameters. Driver files set these parameters - and format résumés appropriately. Support for - US English, UK English, and French are included. -
    • - -
  • Date of birth. The DTD supports a - <birth> element to record date of birth. - This element is currently not formatted. -
    • -
- -

Release 1.2.2

- -

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. -

- -

Release 1.2.1

- -
    -
  • Now compatible with FOP 1.19.0. - You can still expect to see warning messages from FOP, but - these are harmless. -
    • -
  • Acute accents now appear in the word "résumé" - in the running footer in the FO output. -
    • - -
- -

Release 1.2.0

- -

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 deleted file mode 100644 index 4315f68..0000000 --- a/legacy-resumes/resume-1/doc/todo/index.html +++ /dev/null @@ -1,47 +0,0 @@ - - - - XML Resume Library To-Do List - - -

XML Résumé Library To-Do List

- -

The XML Résumé Library copyrighted, © - 2000-2002 by Sean Kelly. See the copying conditions, license, and - disclaimer. -

- -

What To Do

- -

Below are a few suggestions. There's also a whole list of user-submitted - at feature - requests on the SourceForge project page.

- -
    -
  • It would be nice to have an xmlresume-support distribution - that includes all the necessary supporting software (fop, xalan, - xerces, etc.) for first-time users. Then it's just a simple matter - of setting a classpath and they're on their way.
    • -
  • Create/improve translations. If you don't see your favorite - language supported, please create an xsl file to do so.
    • -
  • The zip element should be renamed to postalcode deprecated (bug 632271)
    • - -
  • Implement a web-accessible, do-it-yourself - résumé generator, for those who aren't XML - savvy. -
    • - -
  • Format the date of birth, but parameterize it so that it can - be formatted depending on preference. (While it may be - traditional in some countries to include such information, I - think it might invite age discrimination in other places.) -
    • - -
  • The <present/> structure is kind of odd. -
    • -
- - - diff --git a/legacy-resumes/resume-1/dtd/catalog b/legacy-resumes/resume-1/dtd/catalog deleted file mode 100644 index 35c9483..0000000 --- a/legacy-resumes/resume-1/dtd/catalog +++ /dev/null @@ -1,44 +0,0 @@ - -- Catalog data for XML Resume Library 1.5.1 - - Copyright (c) 2000-2002 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: - - 1. Redistributions of source code must retain the above copyright - notice, this list of conditions and the following disclaimer. - - 2. Redistributions in binary form must reproduce the above - copyright notice, this list of conditions and the following - disclaimer in the documentation and/or other materials provided - with the distribution. - - 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. - -- - -OVERRIDE YES - - -- The XML Resume Library, an XML DTD (and a schema some day...) -- - -PUBLIC "-//Sean Kelly//DTD Resume 1.5.1//EN" "resume.dtd" - - -- ISO entity sets in XML format -- - -PUBLIC "ISO 8879:1986//ENTITIES Added Latin 1//EN" "iso-lat1.ent" - - -- SGML Declaration -- - -SGMLDECL "resume.dcl" diff --git a/legacy-resumes/resume-1/dtd/iso-lat1.ent b/legacy-resumes/resume-1/dtd/iso-lat1.ent deleted file mode 100644 index bd09867..0000000 --- a/legacy-resumes/resume-1/dtd/iso-lat1.ent +++ /dev/null @@ -1,105 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/dtd/resume.dcl b/legacy-resumes/resume-1/dtd/resume.dcl deleted file mode 100644 index fed2103..0000000 --- a/legacy-resumes/resume-1/dtd/resume.dcl +++ /dev/null @@ -1,179 +0,0 @@ -" - PIC "?>" - SHORTREF NONE - - NAMES - SGMLREF - - QUANTITY NONE - - ENTITIES - "amp" 38 - "lt" 60 - "gt" 62 - "quot" 34 - "apos" 39 - - FEATURES - MINIMIZE - DATATAG NO - OMITTAG NO - RANK NO - SHORTTAG - STARTTAG - EMPTY NO - UNCLOSED NO - NETENABL IMMEDNET - ENDTAG - EMPTY NO - UNCLOSED NO - ATTRIB - DEFAULT YES - OMITNAME NO - VALUE NO - EMPTYNRM YES - IMPLYDEF - ATTLIST NO - DOCTYPE NO - ELEMENT NO - ENTITY NO - NOTATION NO - LINK - SIMPLE NO - IMPLICIT NO - EXPLICIT NO - OTHER - CONCUR NO - SUBDOC NO - FORMAL NO - URN NO - KEEPRSRE YES - VALIDITY TYPE - ENTITIES - REF ANY - INTEGRAL YES - APPINFO NONE - SEEALSO "ISO 8879:1986//NOTATION - Extensible Markup Language (XML) 1.0//EN" -> diff --git a/legacy-resumes/resume-1/dtd/resume.dtd b/legacy-resumes/resume-1/dtd/resume.dtd deleted file mode 100644 index f1ca7ea..0000000 --- a/legacy-resumes/resume-1/dtd/resume.dtd +++ /dev/null @@ -1,383 +0,0 @@ - - - - - - -%ISOlat1; -]]> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/examples/addressing/Makefile b/legacy-resumes/resume-1/examples/addressing/Makefile deleted file mode 100644 index 6ee5abd..0000000 --- a/legacy-resumes/resume-1/examples/addressing/Makefile +++ /dev/null @@ -1,100 +0,0 @@ -# Makefile -# -# Makefile for resumes -# -# Copyright (c) 2000-2001 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: -# -# 1. Redistributions of source code must retain the above copyright -# notice, this list of conditions and the following disclaimer. -# 2. Redistributions in binary form must reproduce the above copyright -# notice, this list of conditions and the following disclaimer in the -# documentation and/or other materials provided with the -# distribution. -# -# 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. - -#------------------------------------------------------------------------ -# Replace this with the basename (no .xml extension) of your resume -# source file. In this example, my resume is in "example.xml", so I -# put "example" here. -# This can also be passed on the command line: "make RESUME=canada". -# -RESUME = usa -# -#------------------------------------------------------------------------ - -# uncomment these lines - and set STYLEDIR appropriately - to use a local -# installation. -#STYLEDIR=file:/usr/local/cvs/resume/src/www/xsl -#HTML_STYLE = $(STYLEDIR)/us-html.xsl -#FO_STYLE = $(STYLEDIR)/us-letter.xsl -#TXT_STYLE = $(STYLEDIR)/us-text.xsl - -# otherwise, use the published versions over the net. -HTML_STYLE = http://xmlresume.sourceforge.net/xsl/html.xsl -FO_STYLE = http://xmlresume.sourceforge.net/xsl/fo.xsl -TXT_STYLE = http://xmlresume.sourceforge.net/xsl/text.xsl - -# The Java virtual machine. If it's in your $PATH, you only need -# the first version; if it isn't you'll need to specify the full path. -JAVACMD=java -#JAVACMD=/usr/jdk1.3.0_02/bin/java - -# You may need to uncomment this and have it point to your Fop installation. -#CLASSPATH = /usr/local/Fop/lib/xalan-2.0.0.jar:/usr/local/Fop/xerces-1.2.3.jar:/usr/local/Fop/fop.jar - -# End of configurable parameters. - -.PHONY: all clean -.SUFFIXES: .html .fo .pdf .xml .xsl .txt - - -HDRFMT=-param header.format standard - -RESUMES=usa canada italy norway - -# Define the address format. Need one of these lines for each -# .xml source file. -brazil_format = european -canada_format = standard -ireland_format = standard -italy_format = italian -norway_format = european -nz_format = standard -uk_format = standard -untagged_format = standard -usa_format = standard - -all: $(RESUME).html $(RESUME).pdf $(RESUME).txt - -clean: - -rm -f $(RESUME).html $(RESUME).pdf $(RESUME).fo $(RESUME).txt *~ - - -%.html: %.xml - $(JAVACMD) -cp $(CLASSPATH) org.apache.xalan.xslt.Process -in $< -xsl $(HTML_STYLE) -out $@ $(HDRFMT) -param address.format $($*_format) - -%.txt: %.xml - $(JAVACMD) -cp $(CLASSPATH) org.apache.xalan.xslt.Process -in $< -xsl $(TXT_STYLE) -out $@ $(HDRFMT) -param address.format $($*_format) - -%.fo: %.xml - $(JAVACMD) -cp $(CLASSPATH) org.apache.xalan.xslt.Process -in $< -xsl $(FO_STYLE) -out $@ $(HDRFMT) -param address.format $($*_format) - -%.pdf: %.fo - $(JAVACMD) -cp $(CLASSPATH) org.apache.fop.apps.Fop $< $@ - diff --git a/legacy-resumes/resume-1/examples/addressing/README b/legacy-resumes/resume-1/examples/addressing/README deleted file mode 100644 index 7e8e6a3..0000000 --- a/legacy-resumes/resume-1/examples/addressing/README +++ /dev/null @@ -1,10 +0,0 @@ -This directory contains a set of minimal documents for testing the -address handling code. Each test can be built by passing the RESUME -variable to make, for example: - -make RESUME=italy - -will build italy.html, italy.txt and italy.pdf from the source file italy.xml. - -If you add additional XML test files to this directory, please be sure to -set the _format variable in the Makefile accordingly. diff --git a/legacy-resumes/resume-1/examples/addressing/brazil.xml b/legacy-resumes/resume-1/examples/addressing/brazil.xml deleted file mode 100644 index 285d2d3..0000000 --- a/legacy-resumes/resume-1/examples/addressing/brazil.xml +++ /dev/null @@ -1,45 +0,0 @@ - - - - - - - - -
- - Marina - Costa e Silva - -
- Rua Afonso Camargo, 805 - Santana - Guarapuava - PR - 85070-200 - Brazil -
-
- diff --git a/legacy-resumes/resume-1/examples/addressing/canada.xml b/legacy-resumes/resume-1/examples/addressing/canada.xml deleted file mode 100644 index 993b129..0000000 --- a/legacy-resumes/resume-1/examples/addressing/canada.xml +++ /dev/null @@ -1,33 +0,0 @@ - - - - - - - - -
- - M.J. - Arthur - -
- 1165 Rue McLean - Suite 1500 - Kamloops - BC - V2B 5S8 - Canada -
-
- diff --git a/legacy-resumes/resume-1/examples/addressing/ireland.xml b/legacy-resumes/resume-1/examples/addressing/ireland.xml deleted file mode 100644 index 52bf178..0000000 --- a/legacy-resumes/resume-1/examples/addressing/ireland.xml +++ /dev/null @@ -1,30 +0,0 @@ - - - - - - - - -
- - William - Clifton - -
- 1 O'Leary Place - Coby - Co. Cork - Ireland -
-
- diff --git a/legacy-resumes/resume-1/examples/addressing/italy.xml b/legacy-resumes/resume-1/examples/addressing/italy.xml deleted file mode 100644 index 15b5aef..0000000 --- a/legacy-resumes/resume-1/examples/addressing/italy.xml +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - -
- - Giuseppe - Verdi - -
- Via Garibaldi, 23 - Sorrento - 123 456 - NA - Italy -
-
- diff --git a/legacy-resumes/resume-1/examples/addressing/norway.xml b/legacy-resumes/resume-1/examples/addressing/norway.xml deleted file mode 100644 index e85285d..0000000 --- a/legacy-resumes/resume-1/examples/addressing/norway.xml +++ /dev/null @@ -1,30 +0,0 @@ - - - - - - - - -
- - Henrik - Ibsen - -
- POB 1181 Sentrum - Oslo - 0107 - Norway -
-
- diff --git a/legacy-resumes/resume-1/examples/addressing/nz.xml b/legacy-resumes/resume-1/examples/addressing/nz.xml deleted file mode 100644 index b8599aa..0000000 --- a/legacy-resumes/resume-1/examples/addressing/nz.xml +++ /dev/null @@ -1,32 +0,0 @@ - - - - - - - - -
- - John - Brown - -
- 236 Majoribanks Street - Mount Victoria - Wellington - 6001 - New Zealand -
-
- diff --git a/legacy-resumes/resume-1/examples/addressing/uk.xml b/legacy-resumes/resume-1/examples/addressing/uk.xml deleted file mode 100644 index f1a3cd3..0000000 --- a/legacy-resumes/resume-1/examples/addressing/uk.xml +++ /dev/null @@ -1,36 +0,0 @@ - - - - - - - - -
- - A.J. - Smith - -
- 3 High Street - Otterly - Southampton - Hants - SO31 4NG - UK -
-
- diff --git a/legacy-resumes/resume-1/examples/addressing/untagged.xml b/legacy-resumes/resume-1/examples/addressing/untagged.xml deleted file mode 100644 index fe6b903..0000000 --- a/legacy-resumes/resume-1/examples/addressing/untagged.xml +++ /dev/null @@ -1,29 +0,0 @@ - - - - - - - - -
- - Stewart - Evans - -
PO Box 1273 -Santa Cruz, CA -95061 -
-
- diff --git a/legacy-resumes/resume-1/examples/addressing/usa.xml b/legacy-resumes/resume-1/examples/addressing/usa.xml deleted file mode 100644 index f1ceb9f..0000000 --- a/legacy-resumes/resume-1/examples/addressing/usa.xml +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - - - -
- - Stewart - Evans - -
- PO Box 1273 - Santa Cruz - 95061 - CA - USA -
-
- diff --git a/legacy-resumes/resume-1/examples/build.xml b/legacy-resumes/resume-1/examples/build.xml deleted file mode 100644 index 45075fc..0000000 --- a/legacy-resumes/resume-1/examples/build.xml +++ /dev/null @@ -1,142 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/examples/example1.xml b/legacy-resumes/resume-1/examples/example1.xml deleted file mode 100644 index c732955..0000000 --- a/legacy-resumes/resume-1/examples/example1.xml +++ /dev/null @@ -1,145 +0,0 @@ - - - - - - -
- - Jo - Doe - - -
- 123 Elm #456 - Garbonzoville - NX - 99999-9999 -
- - 555.555.5555 - doe@doe.doe - http://doe.com/~doe/ - -
- - - I really, really, really, really want a - job. - - - - - - Senior Toilet Cleaner - HM Secret Service - - - - August - 1943 - - - - - - - - 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. - - - - - - - - - BA - Renaissance Bedpan Design - - February - 1631 - - Fishbaum del Schloßberg - - Graduated with lowest honors. - - - - - - - Special Skills - - Speak multiple European languages with no discernable - accent - - Able to predict earthquakes - - - - - 2009 - - So there! - - - - diff --git a/legacy-resumes/resume-1/examples/example2.xml b/legacy-resumes/resume-1/examples/example2.xml deleted file mode 100644 index 511a574..0000000 --- a/legacy-resumes/resume-1/examples/example2.xml +++ /dev/null @@ -1,387 +0,0 @@ - - - - - - -
- - Alexis - Kernighan - - -
Reina #35, apt. 4a, e/ Gervasio y Escobar -Cuidad de la Habana, CP 11900 -CUBA
- - +1-55-4362-4562 - +1-55-5252-4356 - alexis@finecooks.xyz - alexis2755263 - -
- - - To achieve my Master Chef certification and become - executive chef at a fine restaurant in the - Hawaiian islands. - - - - - Cooking Skills - - General Experience - Gastronomy - Culinary math - Nutrition - Sanitation - Culinary French - Meat identification - Wines - Restaurant Law - Brodeger's Sanitation science background - - - Culinary Skills - Braise - Sauté - Fry - Bake - Stocks - Reductions - Sauces - - - Cuisines - Seafood - American Regional - Asian - Charcuterie - Garde Manger - Pâtisserie - Modern French - - - - - Computer Skills - - Perl - J2EE - XML Parsing - - Debugging - - - - - Construction Skills - - Hammering - Drilling - Sawing - Wiring - Plunging - - - - - - - - - Electrician's Assistant - May1993 - Mike's Wiring Co. - - Rewired the city of Phoenix - Fixed my mom's living room lamp - - - - - Senior System Administrator - SysOps4Cheap.com - 1987 - - SysOps4Cheap.com was a small startup whose aim was to supply - sysadmins over the web. The business failed because the - very few sysadmins could survive the process of being overnighted - by FedEx. - - - - Ran a beowulf cluster of Commodore 64s - Used scuba tanks to keep sysadmins fresh in the mail - - - - - Sous Chef - The Four Seasons - - - - March - 1997 - - - - - - - - Created an extensive menu for our fall offerings - Revamping of Grill Area - - - Developed 13 new menu items - Prepared daily operations plan - Streamlined procedures for fresh foods - procurement - - - - Assistant Chef - Zolo - - - - April - 1993 - - - - - January - 1997 - - - - - Prepared standard daily mise en place, stocks, and - sauces. Assembled cold plates and salads. - - - - - - - Professional Societies - - Association of Aluminum Utensils - - - Grand Poobah - Stonecutters - 1934 - - - Senior Fellow - Society for Creative Cuisine - February1993 - - - As senior fellow, I was responsible for all recruiting - efforts of the organization. - - - - - - Honors and Recognition - Cooking Honor Roll - Culinary Institute of America - - January1992 - May1995 - - - - - Sysop's Choice Award for Best Cook - Usenix - May1987 - - - - - - Top Secret Cook - June1994 - - Junior Mothball Inspector - June1994 - January2004 - USMBIA - - - - - - What can't be captured on a résumé is my sheer - level of enthusiasm 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 do their best. - - - - - - - AA - Culinary Arts - - May - 1995 - - Culinary Institute of America - - - Stocks, broths, and soups - A - - - French and world sauces - A - - - French cuisine - B - - - World cuisine - A - - - Kitchen sanitation - A - - - Pastry - B - - - Culinary history - A - - - Hotel restaurant management - C - - - - - - - - - - High speed reduction of wine based sauces - - Journal of the Occidental Culinary Federation - - Charles Bell - Kassandra Kassis - 132-136 - - February - 2000 - - OCF, New York, New York - - - - - - 1998 - - Deltoid Press, http://www.deltoid.co/ - The Texas Ranger Chow Book - - - - - - Hobbies - - - Kite Flying - - Two-time Cuban national champion. - - - High-speed driving - Woodworking - - - - - - Indiana - O'Brien - - Head Chef - The Four Seasons - - 408.555.1296 - 552.762.8024 - 408.737.5375 - - - - - Web - Melgood - -
- 3090 Deltoid - Santa Yorba - CA - 95022 - USA -
- - - - - - May - 2002 - - - - diff --git a/legacy-resumes/resume-1/examples/resume.fo b/legacy-resumes/resume-1/examples/resume.fo deleted file mode 100644 index abc1aa0..0000000 --- a/legacy-resumes/resume-1/examples/resume.fo +++ /dev/null @@ -1,83 +0,0 @@ - - - - - - - - - - -Jo Doe - Résumé - page - - - - - -Jo Doe - -123 Elm #456 -Garbonzoville, NX 99999-9999 - - - -Phone: 555.555.5555 - -Email: doe@doe.doe - -URL: http://doe.com/~doe/ - - -Professional Objective -I really, really, really, really want a - job. - -Employment History - - -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. - - - -Education - - -BA in Renaissance Bedpan Design, February 1631. - Graduated with lowest honors. - -Fishbaum del Schloßberg - - -Special Skills - -Speak multiple European languages with no discernable accent, Able to predict earthquakes. - -Copyright © 2009 by Jo Doe. -So there! - - - - - diff --git a/legacy-resumes/resume-1/examples/resume.html b/legacy-resumes/resume-1/examples/resume.html deleted file mode 100644 index 7c74fa7..0000000 --- a/legacy-resumes/resume-1/examples/resume.html +++ /dev/null @@ -1,70 +0,0 @@ - -Jo Doe - Résumé

Jo Doe

123 Elm #456
Garbonzoville, NX 99999-9999

Phone: 555.555.5555
Email: doe@doe.doe
URL: http://doe.com/~doe/

Professional Objective

I really, really, really, really want a - job. -

Employment History

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. -

Education

  • BA in Renaissance Bedpan Design, February 1631. - Graduated with lowest honors. -
    Fishbaum del Schloßberg

Special Skills

Speak multiple European languages with no discernable accent, Able to predict earthquakes.

Copyright © 2009 by Jo Doe.

So there!

\ No newline at end of file diff --git a/legacy-resumes/resume-1/examples/resume.txt b/legacy-resumes/resume-1/examples/resume.txt deleted file mode 100644 index c851826..0000000 --- a/legacy-resumes/resume-1/examples/resume.txt +++ /dev/null @@ -1,51 +0,0 @@ - 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/ - - -Professional Objective: - - I really, really, really, *really* want a job. - - -Employment History: - - 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. - - -Education: - - BA in Renaissance Bedpan Design, February 1631. Graduated with - lowest honors. - Fishbaum del Schloßberg - - -Special Skills: - - Speak multiple European languages with no discernable accent, Able - to predict earthquakes. - - -Copyright © 2009 by Jo Doe. So there! diff --git a/legacy-resumes/resume-1/examples/resume.xml b/legacy-resumes/resume-1/examples/resume.xml deleted file mode 100644 index c732955..0000000 --- a/legacy-resumes/resume-1/examples/resume.xml +++ /dev/null @@ -1,145 +0,0 @@ - - - - - - -
- - Jo - Doe - - -
- 123 Elm #456 - Garbonzoville - NX - 99999-9999 -
- - 555.555.5555 - doe@doe.doe - http://doe.com/~doe/ - -
- - - I really, really, really, really want a - job. - - - - - - Senior Toilet Cleaner - HM Secret Service - - - - August - 1943 - - - - - - - - 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. - - - - - - - - - BA - Renaissance Bedpan Design - - February - 1631 - - Fishbaum del Schloßberg - - Graduated with lowest honors. - - - - - - - Special Skills - - Speak multiple European languages with no discernable - accent - - Able to predict earthquakes - - - - - 2009 - - So there! - - - - diff --git a/legacy-resumes/resume-1/java/xmlresume-filter.jar b/legacy-resumes/resume-1/java/xmlresume-filter.jar deleted file mode 100644 index 2f09456..0000000 Binary files a/legacy-resumes/resume-1/java/xmlresume-filter.jar and /dev/null differ diff --git a/legacy-resumes/resume-1/output/charlesnw-resume.fo b/legacy-resumes/resume-1/output/charlesnw-resume.fo deleted file mode 100644 index b31f951..0000000 --- a/legacy-resumes/resume-1/output/charlesnw-resume.fo +++ /dev/null @@ -1,346 +0,0 @@ - - - - - - - - - -Charles Wyble - Résumé - page - - - - - -Charles Wyble - -El Monte, CA - - - -Mobile Phone: 818.280.7059 - -Email: charles@knownelement.com - -URL: http://www.knownelement.com/ - - -Professional Objective - - 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. - -Skills Summary - -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. -Employment History - - -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. - - - - -• - - - -Automated numerous routine system administration tasks - Created numerous batch and VbScript programs to handle all aspects of Windows administration from the command line. - - - - - -• - - - -Active Directory Project for WDIG - Designed and implemented a nation wide, 3 data center, highly available Active Directory system to handle both the - PCI and non PCI servers for the Walt Disney Internet Group. - - - - - -• - - - -Windows NT to Active Directory migration - Migrated all the application servers off of Windows NT to Windows 2003 Active Directory domain controllers. - Also have experience with Windows 2008 (including Linux/Cisco/wireless - [wpa2 enterprise] authentication). Used both Centrify and Samba/Winbind/LDAP/Kerberos. - - - - - - - - -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: - - - -• - - - -Deployment of encrypted backups. - Designed/tested/documented/deployed an enterprise wide Linux backup system. - All data stored on a central server with ISCSI attached network storage. - Uses GNUPG and tar over ssh. Backups/Restores tested on a weekly basis. - - - - - -• - - - -Deployment of Oracle database infrastructure. - Deployed 2 Oracle RAC clusters, each consisting of 3 Dell 6850's. They are equipped with Qual Dual Core - Xeon's and 32 Gb of RAM, running RedHat Enterprise Linux 4.0 64bit edition. - One environment is for staging and one is for production. EMC attached. This environment is used for - Data Warehouse, Transaction Processing Software and Credit Card Clearing applications. - The hardware and software was deployed in 3 business days. - - - - - -• - - - -File Integrity Checking system for PCI compliance. - Deployment of file integrity checking across 100 UNIX servers using fully open source software. - Used integrit http://integrit.sf.net and some custom shell scripts which were submitted - back upstream for inclusion. - - - - - - - - -Linux, Windows, network and security consulting for various startups and defense contractors - -Multiple entities - -February 2005–October 2005 - - -Projects: - - - -• - - - -LAMP Deployment - Deployed a Debian Linux/Apache/MySQL/PHP system and educated the System Administration and Development - staff on configuration and use for an insurance company. - - - - - -• - - - -Corporate Linux Deployment/Migration - Provided assistance to a medium sized engineering firm with a near 100% - conversion to Linux on the desktop and server. Utilizing SUSE Professional 6.5 for desktops and Debian GNU/Linux for - servers (Email/File Server/DNS/DHCP). - - - - - -• - - - -Linux Deployment/Migration - Provided assistance to a small software development firm with a near 100% - conversion to Linux. Utilized Ubuntu Linux for desktops and Debian GNU/Linux for servers - (Email/File/LDAP/DNS/DHCP). - - - - - - - - -Linux/Windows Systems Engineer - -GSI Commerce (via acquisition of Newroads Inc) - -July 2002–February 2005 - - -Projects: - - - -• - - - -Disaster Recovery from an Informix Database failure. - Assisted in the design/testing/and execution of a disaster recovery in real time - (on-the-fly). Wrote and documented the use of several utilities that cut down the amount of time to recovery by 30 - percent. - - - - - -• - - - -Streamlined the FTP Server Configuration process. - Streamlined the system configuration and new account creation process for ProFTPD on a mission critical FTP server. - This allowed faster turn around times and freed up IT resources. - - - - - -• - - - -Deployed open-source Remote Control Software. - Deplopyed/Secured/Optimized/Maintained UltraVNC remote control software. This allowed the Infrastructure Support team to more - rapidly respond to users support requests, and by doing so increase compliance with Service Level Agreements and increase - end-user satisfaction. - - - - - -• - - - -Network Infrastructure Upgrade. - Upgraded the network from hubs to Linksys managed switches to increase network performance and usability/reliability. - No network downtime occurred in the process of the upgrade. - - - - - -• - - - -Hardware/Software Inventory Solution: - Wrote a custom software/hardware monitoring/reporting system to ensure compliance with software licensing and obtain an - accurate overview of company assets for inventory and disaster recovery purposes. Utilized WMI/Visio/Microsoft Access. - - - - - - - - - - diff --git a/legacy-resumes/resume-1/output/charlesnw-resume.html b/legacy-resumes/resume-1/output/charlesnw-resume.html deleted file mode 100644 index f9c1faf..0000000 --- a/legacy-resumes/resume-1/output/charlesnw-resume.html +++ /dev/null @@ -1,140 +0,0 @@ - -Charles Wyble - Résumé

Charles Wyble

El Monte, CA

Mobile Phone: 818.280.7059
Email: charles@knownelement.com
URL: http://www.knownelement.com/

Professional Objective

- 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. -

Skills Summary

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.

Employment History

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. -

  • Automated numerous routine system administration tasks - Created numerous batch and VbScript programs to handle all aspects of Windows administration from the command line. -
  • Active Directory Project for WDIG - Designed and implemented a nation wide, 3 data center, highly available Active Directory system to handle both the - PCI and non PCI servers for the Walt Disney Internet Group. -
  • Windows NT to Active Directory migration - Migrated all the application servers off of Windows NT to Windows 2003 Active Directory domain controllers. - Also have experience with Windows 2008 (including Linux/Cisco/wireless - [wpa2 enterprise] authentication). Used both Centrify and Samba/Winbind/LDAP/Kerberos. -

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:

  • Deployment of encrypted backups. - Designed/tested/documented/deployed an enterprise wide Linux backup system. - All data stored on a central server with ISCSI attached network storage. - Uses GNUPG and tar over ssh. Backups/Restores tested on a weekly basis. -
  • Deployment of Oracle database infrastructure. - Deployed 2 Oracle RAC clusters, each consisting of 3 Dell 6850's. They are equipped with Qual Dual Core - Xeon's and 32 Gb of RAM, running RedHat Enterprise Linux 4.0 64bit edition. - One environment is for staging and one is for production. EMC attached. This environment is used for - Data Warehouse, Transaction Processing Software and Credit Card Clearing applications. - The hardware and software was deployed in 3 business days. -
  • File Integrity Checking system for PCI compliance. - Deployment of file integrity checking across 100 UNIX servers using fully open source software. - Used integrit http://integrit.sf.net and some custom shell scripts which were submitted - back upstream for inclusion. -

Linux, Windows, network and security consulting for various startups and defense contractors
Multiple entities
February 2005-October 2005

Projects:

  • LAMP Deployment - Deployed a Debian Linux/Apache/MySQL/PHP system and educated the System Administration and Development - staff on configuration and use for an insurance company. -
  • Corporate Linux Deployment/Migration - Provided assistance to a medium sized engineering firm with a near 100% - conversion to Linux on the desktop and server. Utilizing SUSE Professional 6.5 for desktops and Debian GNU/Linux for - servers (Email/File Server/DNS/DHCP). -
  • Linux Deployment/Migration - Provided assistance to a small software development firm with a near 100% - conversion to Linux. Utilized Ubuntu Linux for desktops and Debian GNU/Linux for servers - (Email/File/LDAP/DNS/DHCP). -

Linux/Windows Systems Engineer
GSI Commerce (via acquisition of Newroads Inc)
July 2002-February 2005

Projects:

  • Disaster Recovery from an Informix Database failure. - Assisted in the design/testing/and execution of a disaster recovery in real time - (on-the-fly). Wrote and documented the use of several utilities that cut down the amount of time to recovery by 30 - percent. -
  • Streamlined the FTP Server Configuration process. - Streamlined the system configuration and new account creation process for ProFTPD on a mission critical FTP server. - This allowed faster turn around times and freed up IT resources. -
  • Deployed open-source Remote Control Software. - Deplopyed/Secured/Optimized/Maintained UltraVNC remote control software. This allowed the Infrastructure Support team to more - rapidly respond to users support requests, and by doing so increase compliance with Service Level Agreements and increase - end-user satisfaction. -
  • Network Infrastructure Upgrade. - Upgraded the network from hubs to Linksys managed switches to increase network performance and usability/reliability. - No network downtime occurred in the process of the upgrade. -
  • Hardware/Software Inventory Solution: - Wrote a custom software/hardware monitoring/reporting system to ensure compliance with software licensing and obtain an - accurate overview of company assets for inventory and disaster recovery purposes. Utilized WMI/Visio/Microsoft Access. -
\ No newline at end of file diff --git a/legacy-resumes/resume-1/output/charlesnw-resume.txt b/legacy-resumes/resume-1/output/charlesnw-resume.txt deleted file mode 100644 index f9995da..0000000 --- a/legacy-resumes/resume-1/output/charlesnw-resume.txt +++ /dev/null @@ -1,203 +0,0 @@ - Charles Wyble - Résumé - - -Contact Information: - -Charles Wyble -El Monte, CA - -Mobile Phone: 818.280.7059 -Email: charles@knownelement.com -URL: http://www.knownelement.com/ - - -Professional Objective: - - 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. - - -Skills Summary: - - 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. - - -Employment History: - - 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. - - Projects: - * *Automated numerous routine system administration tasks* Created - numerous batch and VbScript programs to handle all aspects of - Windows administration from the command line. - * *Active Directory Project for WDIG* Designed and implemented a - nation wide, 3 data center, highly available Active Directory - system to handle both the PCI and non PCI servers for the Walt - Disney Internet Group. - * *Windows NT to Active Directory migration* Migrated all the - application servers off of Windows NT to Windows 2003 Active - Directory domain controllers. Also have experience with Windows - 2008 (including Linux/Cisco/wireless [wpa2 enterprise] - authentication). Used both Centrify and - Samba/Winbind/LDAP/Kerberos. - - - 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: - * *Deployment of encrypted backups.* - Designed/tested/documented/deployed an enterprise wide Linux - backup system. All data stored on a central server with ISCSI - attached network storage. Uses GNUPG and tar over ssh. - Backups/Restores tested on a weekly basis. - * *Deployment of Oracle database infrastructure.* Deployed 2 Oracle - RAC clusters, each consisting of 3 Dell 6850's. They are equipped - with Qual Dual Core Xeon's and 32 Gb of RAM, running RedHat - Enterprise Linux 4.0 64bit edition. One environment is for staging - and one is for production. EMC attached. This environment is used - for Data Warehouse, Transaction Processing Software and Credit - Card Clearing applications. The hardware and software was deployed - in 3 business days. - * *File Integrity Checking system for PCI compliance.* Deployment of - file integrity checking across 100 UNIX servers using fully open - source software. Used integrit http://integrit.sf.net and some - custom shell scripts which were submitted back upstream for - inclusion. - - - Linux, Windows, network and security consulting for various startups and defense contractors - Multiple entities - February 2005-October 2005 - - Projects: - * *LAMP Deployment * Deployed a Debian Linux/Apache/MySQL/PHP system - and educated the System Administration and Development staff on - configuration and use for an insurance company. - * *Corporate Linux Deployment/Migration* Provided assistance to a - medium sized engineering firm with a near 100% conversion to Linux - on the desktop and server. Utilizing SUSE Professional 6.5 for - desktops and Debian GNU/Linux for servers (Email/File - Server/DNS/DHCP). - * *Linux Deployment/Migration* Provided assistance to a small - software development firm with a near 100% conversion to Linux. - Utilized Ubuntu Linux for desktops and Debian GNU/Linux for - servers (Email/File/LDAP/DNS/DHCP). - - - Linux/Windows Systems Engineer - GSI Commerce (via acquisition of Newroads Inc) - July 2002-February 2005 - - Projects: - * *Disaster Recovery from an Informix Database failure.* Assisted in - the design/testing/and execution of a disaster recovery in real - time (on-the-fly). Wrote and documented the use of several - utilities that cut down the amount of time to recovery by 30 - percent. - * *Streamlined the FTP Server Configuration process.* Streamlined - the system configuration and new account creation process for - ProFTPD on a mission critical FTP server. This allowed faster turn - around times and freed up IT resources. - * *Deployed open-source Remote Control Software.* - Deplopyed/Secured/Optimized/Maintained UltraVNC remote control - software. This allowed the Infrastructure Support team to more - rapidly respond to users support requests, and by doing so - increase compliance with Service Level Agreements and increase - end-user satisfaction. - * *Network Infrastructure Upgrade.* Upgraded the network from hubs - to Linksys managed switches to increase network performance and - usability/reliability. No network downtime occurred in the process - of the upgrade. - * *Hardware/Software Inventory Solution*: Wrote a custom - software/hardware monitoring/reporting system to ensure compliance - with software licensing and obtain an accurate overview of company - assets for inventory and disaster recovery purposes. Utilized - WMI/Visio/Microsoft Access. - diff --git a/legacy-resumes/resume-1/xsl/country/br.xsl b/legacy-resumes/resume-1/xsl/country/br.xsl deleted file mode 100644 index 2e88049..0000000 --- a/legacy-resumes/resume-1/xsl/country/br.xsl +++ /dev/null @@ -1,110 +0,0 @@ - - - - - - - Curriculum Vitae - página - - Dados para Contato - Objetivo Profissional - - Experiência Profissional - Formação Acadêmica - Publicações - Interesses - Autorizações - Prèmios - Diversos - - em - - e - - Copyright © - - por - - presente data - Realizações: - Projetos: - - - minoritário - minoritários - Referências - - Média Geral - - Média Principal - - de um total de - - - Disponível sob pedido. - Última modificaçõ - - Telefone - Fax - Pager - Endereço Eletrônico - URL - - - - Residencial - Comercial - Celular - Residencial - Comercial - - - - AIM - ICQ - IRC - Jabber - MSN Messenger - Yahoo! Messenger - - - - european - - diff --git a/legacy-resumes/resume-1/xsl/country/de.xsl b/legacy-resumes/resume-1/xsl/country/de.xsl deleted file mode 100644 index a6fa60c..0000000 --- a/legacy-resumes/resume-1/xsl/country/de.xsl +++ /dev/null @@ -1,100 +0,0 @@ - - - - - - - Lebenslauf - Seite - Personalien - Ziele - Ausgeübte Tätigkeiten - Akademische Ausbildung - Veröffentlichungen - Interessen - Leumundszeugnis - Preise - - Verschiedenes - in - und - Copyright © - - Gegenwart - Erreichte Ziele: - Projekte: - - Nebenfach - Nebenfächer - Referenzen - - Notendurchschnitt - - Notendurchschnitt der Hauptfächer - - von - - - Referenzen werden gerne auf Anfrage genannt. - Letzte Aktualisierung: - - Telefon - Fax - Privat - Geschäft - Mobil - Privat - Geschäft - - Pager - Email - URL - - - - - AIM - ICQ - IRC - Jabber - MSN Messenger - Yahoo! Messenger - - - - - european - - diff --git a/legacy-resumes/resume-1/xsl/country/es.xsl b/legacy-resumes/resume-1/xsl/country/es.xsl deleted file mode 100644 index 5ff1e83..0000000 --- a/legacy-resumes/resume-1/xsl/country/es.xsl +++ /dev/null @@ -1,88 +0,0 @@ - - - - - - - Curriculum Vitae - página - Información de contacto - Objetivo - Experiencia - Formación - Publicaciones - Otros - en - Copyright © - por - Actualidad - - Teléfono - Fax - - del Trabajo - Móvil - - del Trabajo - - Email - URL - Logros: - Proyectos: - - - european - - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - - diff --git a/legacy-resumes/resume-1/xsl/country/fr.xsl b/legacy-resumes/resume-1/xsl/country/fr.xsl deleted file mode 100644 index 68d2872..0000000 --- a/legacy-resumes/resume-1/xsl/country/fr.xsl +++ /dev/null @@ -1,93 +0,0 @@ - - - - - - - - - Curriculum Vitae - page - Information de Contact - Objectif professionnel - Expérience professionnelle - Formation - Publications - Divers - en - Copyright © - par - présent - - Téléphone - Facsimile - GSM - privé - privé - - Courrier électronique - URL - Réalisations: - Projets: - Références - Récompenses - - - - european - - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - - diff --git a/legacy-resumes/resume-1/xsl/country/it.xsl b/legacy-resumes/resume-1/xsl/country/it.xsl deleted file mode 100644 index 7e11a07..0000000 --- a/legacy-resumes/resume-1/xsl/country/it.xsl +++ /dev/null @@ -1,86 +0,0 @@ - - - - - - - Curriculum Vitae - page - Contatti - Obiettivo - Esperienze Professionali - Istruzione - Documenti - Varie - in - Copyright © - di - presente - Telefono - in casa - Email - URL - Conseguimenti - Progetti - Riferimenti - - - italian - - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - - diff --git a/legacy-resumes/resume-1/xsl/country/nl.xsl b/legacy-resumes/resume-1/xsl/country/nl.xsl deleted file mode 100644 index f058eb3..0000000 --- a/legacy-resumes/resume-1/xsl/country/nl.xsl +++ /dev/null @@ -1,88 +0,0 @@ - - - - - - - Curriculum Vitae - bladzijde - Contactinformatie - Profesionele Doelstelling - Werkervaring - Studies - Publicaties - Overigen - in - Copyright © - door - heden - Telefoon - E-mail - URL - Prestaties: - Projecten: - Referenties - - - - european - - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - - diff --git a/legacy-resumes/resume-1/xsl/country/propogate-params.sh b/legacy-resumes/resume-1/xsl/country/propogate-params.sh deleted file mode 100644 index a75f04e..0000000 --- a/legacy-resumes/resume-1/xsl/country/propogate-params.sh +++ /dev/null @@ -1,47 +0,0 @@ -#!/bin/sh - -SOURCE=us.xsl - -# propogate-translations.sh -# By Mark Miller, though he is not proud of it. -# -# This is a quick and VERY DIRTY way to add any new params defined -# in us.xsl (or $SOURCE) to the rest of the country.xsl stylesheets -# with a \"TRANSLATION NEEDED\" message. It also checks for outdated -# params existing in other country.xsl files but not in $SOURCE -# -# IMPORTANT: After running this script, you must manually edit each -# .xsl file and make sure that all the xsl:param tags are INSIDE the -# tags. This script does NOT do that for you. -# -# WARNING: This script is by no means fool-proof, and only included -# to make life slightly easier for developers. Please manually edit -# each .xsl file after running to be sure that the script has not -# screwed anything up. " - -echo "======== Checking Files for outdated params..." -for country in `ls -1 *.xsl`; do - for param in `grep '.*\<\/xsl:param\>/$1/g`; - do - exists=`grep -c $param $SOURCE` - if [ "0" = $exists ]; then - echo "Param $param in file $country does not exist in $SOURCE." - fi - done -done - -echo "======== Adding params in $SOURCE to other files as necessary..." -for country in `ls -1 *.xsl`; do - for param in `grep '.*\<\/xsl:param\>/$1/g`; - do - translated=`grep -c $param $country` - if [ "0" = $translated ]; - then - echo "Adding param $param to $country" - echo " TRANSLATION NEEDED" >> $country - fi - done -done -echo "Done." diff --git a/legacy-resumes/resume-1/xsl/country/uk.xsl b/legacy-resumes/resume-1/xsl/country/uk.xsl deleted file mode 100644 index abd474e..0000000 --- a/legacy-resumes/resume-1/xsl/country/uk.xsl +++ /dev/null @@ -1,86 +0,0 @@ - - - - - - - - - CV - Telephone - Referees - - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - TRANSLATION NEEDED - - diff --git a/legacy-resumes/resume-1/xsl/country/us.xsl b/legacy-resumes/resume-1/xsl/country/us.xsl deleted file mode 100644 index ef17c47..0000000 --- a/legacy-resumes/resume-1/xsl/country/us.xsl +++ /dev/null @@ -1,103 +0,0 @@ - - - - - - - Résumé - page - - Contact Information - Professional Objective - - Employment History - Education - Publications - Interests - Security Clearances - Awards - Miscellany - - in - - and - - Copyright © - - by - - Present - Achievements: - Projects: - - minor - minors - References - - Overall GPA - - GPA in Major - - out of - - - Available upon request. - Last modified - - Phone - Fax - Home - Work - Mobile - Home - Work - - Pager - Email - URL - - - - AIM - ICQ - IRC - Jabber - MSN Messenger - Yahoo! Messenger - - diff --git a/legacy-resumes/resume-1/xsl/format/fo.xsl b/legacy-resumes/resume-1/xsl/format/fo.xsl deleted file mode 100644 index 3328fda..0000000 --- a/legacy-resumes/resume-1/xsl/format/fo.xsl +++ /dev/null @@ -1,1142 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Heading Not Defined - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - , - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ( - ) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - : - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - , - - - - . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - : - - - - - - - - - - . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - , - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - , - - - - , - - - - . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - , - - , - - - - - - - - - - - - - - - - - - - - - . - - - - - - - - - - - - - - - - - - - - . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - – - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - , - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - , - - - - - - - - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/format/html.xsl b/legacy-resumes/resume-1/xsl/format/html.xsl deleted file mode 100644 index f871a0f..0000000 --- a/legacy-resumes/resume-1/xsl/format/html.xsl +++ /dev/null @@ -1,964 +0,0 @@ - - - - - - - - - - - HEADING NOT DEFINED -

- - - -

- - - - - - <xsl:apply-templates select="r:resume/r:header/r:name"/> - <xsl:text> - </xsl:text> - <xsl:value-of select="$resume.word"/> - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - - - - - - - - - - , - - - - - -
-

- -

- - -
- - - - - - - -
-

- -

- - -
- - - - -

- -

- - - - - - : - -
- - - - - - : - -
- - - - : - -
- - - - : - - - -
- - - - : - - - -
- - - - - - : - -
- - - -

- -

- - -

- - - - - - - - - - - - -
- - - -
- - - -
- - - - , - - - - - - - -
- - -

- - -

- - - - - - - - - - - - -
- - - -
- - - -
- - - - - - - -
- - - -
- - -

- - -

- - -
- - - -
- - - - - - - - ( - - ) - - -
- - -

- - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - - - - -

- -
- - -
- -

- - jobDescription - - -
-

- -

- -
- - -
-

- -

- -
- - - - - - - - - - - - - - - - - - -
    - -
- - - - -
  • - - - - - - - -
    • -     - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
      - -
    • - -
      • -       -
    -     - - - - - - - - - - - - -
      - -
    - -     - - - - - - - - -
  • - - - - - - - - - - - - , - - - - . - - - -
    - - -     - - - -
    • -     - - -

    - - - - - - - - - - - : - - - - - - - . - - -

    -     - - -

    - -

    - - - - - - - - - -
    - - - -
    -     - - - -

    - - - - - - -

    -     - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

    - - - - - - - - - - - - - - - - - -

    -     - -

    - -

    - -
      - -
    -     - - -
      - -
    -     -     -     -     - - - - - - - - - - - - -
  • - - -
    • -     - - - - - - - - - - - - - - - - - -
      - -
    -     - - -
  • - -
    • -     - - - - - - - -
      - -
    -     - - - -
  • - -
    - - - -
    -     - - - -
    -     - - -
    -     - - membershipDescription - -
    • -     - - - - - - - - - - -
      - -
    -     - - - -
  • - - - - - - . - - -
    • -     - - - - - interestDescription - - - - - - - - - - - -
      - -
    -     - - -
  • - - - - - , - - - - , - - - - . - - -
    • -     - - - - - - - - - -
      - -
    -     - - -
  • - - - - - , - - - - , - - - -
    • -     - - - - - - - - - - - -

    - - - - . -

    -     - - -
    - - - - - - - - - - - - - . - -
    -     - - -

    - -

    -     - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    -     - -
    - -
    -     -     -     - -

    - -

    -     -     -     - - -
    -
    - - -
    - - - , - - -
    -     -
    -
    -
    -
    -     - - - - -
    - - -
    - - - , - - -
    -     -
    -
    - - - -     - - - - - block - description - - - - - - - - - - - - - -
    - -
    -     -     -     -     diff --git a/legacy-resumes/resume-1/xsl/format/text.xsl b/legacy-resumes/resume-1/xsl/format/text.xsl deleted file mode 100644 index 6802732..0000000 --- a/legacy-resumes/resume-1/xsl/format/text.xsl +++ /dev/null @@ -1,1135 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - : - - - - - - - - - : - - - - - - : - - - - - - : - - - - - - : - - - - - - - - - : - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - , - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ( - - ) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - block - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - , - - - - . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - : - - - - - - - - - - . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 - - - - - - - - - - - - - - - - - - - - - - - - 0 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - , - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - , - - - - , - - - - . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - , - - , - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . - - - - - - - - - - - - - - - - - - - - - - - . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - , - - - - - - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/lib/address.xsl b/legacy-resumes/resume-1/xsl/lib/address.xsl deleted file mode 100644 index b458976..0000000 --- a/legacy-resumes/resume-1/xsl/lib/address.xsl +++ /dev/null @@ -1,133 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/lib/common.xsl b/legacy-resumes/resume-1/xsl/lib/common.xsl deleted file mode 100644 index c33c035..0000000 --- a/legacy-resumes/resume-1/xsl/lib/common.xsl +++ /dev/null @@ -1,317 +0,0 @@ - - - - - - - - - - - - - - - - - NO DEFAULT TITLE DEFINED - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ***** WARNING: Unknown phone location: ' - - ' (inserting literally into output) - - - - - - - - - - - - - - - - - - - - - ***** WARNING: Unknown fax location: ' - - ' (inserting literally into output) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ***** WARNING: Unknown instantMessage service: ' - - ' (inserting literally into output) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - , - - - - , - - - - - - - - - - - - - - - ( - - - - ( - - - - - - - - - - - - - - , - - - - , - - - - - - - ) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - , - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/lib/deprecated.xsl b/legacy-resumes/resume-1/xsl/lib/deprecated.xsl deleted file mode 100644 index 0a2aaef..0000000 --- a/legacy-resumes/resume-1/xsl/lib/deprecated.xsl +++ /dev/null @@ -1,137 +0,0 @@ - - - - - - - - - - - - WARNING: break deprecated - The break element is deprecated as of version 1.3.3 of the XML Resume - Library. It will be removed in a future version. It is recommended that - you remove all break elements. - You can use "make 13x-140" to fix this problem. - - - - - - - WARNING: company deprecated - The company element is deprecated as of version 1.3.3 of the XML Resume - Library. It will be removed in a future version. It is recommended that - you remove all company elements. - You can use "make 13x-140" to fix this problem. - - - - - - - WARNING: street2 deprecated - The street2 element is deprecated as of version 1.3.3 of the XML Resume - Library. It will be removed in a future version. It is recommended that - you convert all street2 elements to street elements. - You can use "make 13x-140" to fix this problem. - - - - - - - - WARNING: skillareas deprecated - The skillareas element is deprecated as of version 1.4.0 of the XML - Resume Library. It will be removed in a future version. It is - recommended that you remove all skillareas elements. skillarea elements - may now be direct children of resume. - You can use "make 13x-140" to fix this problem. - - - - - - - WARNING: skills deprecated - The skills element is deprecated as of version 1.4.0 of the XML Resume - Library. It will be removed in a future version. It is recommended that - you remove all skills elements. skill elements may now be direct - children of skillset. - You can use "make 13x-140" to fix this problem. - - - - - - - - - - - - - - - - - - WARNING: pubDate deprecated - The pubDate element is deprecated as of version 1.4.0 of the XML Resume - Library. It will be removed in a future version. It is recommended that - you replace pubDate elements with date elements. - You can use "make 13x-140" to fix this problem. - - - - - - - WARNING: docpath, head, node, tail, label, and uri deprecated - The docpath, head, node, tail, label, and uri elements are deprecated as - of version 1.4.0 of the XML Resume Library. They will be removed in a - future version. It is recommended that you remove all of these elements. - You can use "make 13x-140" to fix this problem. - - - - - diff --git a/legacy-resumes/resume-1/xsl/lib/pub.xsl b/legacy-resumes/resume-1/xsl/lib/pub.xsl deleted file mode 100644 index 3d4505d..0000000 --- a/legacy-resumes/resume-1/xsl/lib/pub.xsl +++ /dev/null @@ -1,135 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - " - - " - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/lib/string.xsl b/legacy-resumes/resume-1/xsl/lib/string.xsl deleted file mode 100644 index ec5f834..0000000 --- a/legacy-resumes/resume-1/xsl/lib/string.xsl +++ /dev/null @@ -1,168 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -1 - - - - - - - - - - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/lib/textlayout.xsl b/legacy-resumes/resume-1/xsl/lib/textlayout.xsl deleted file mode 100644 index 4924273..0000000 --- a/legacy-resumes/resume-1/xsl/lib/textlayout.xsl +++ /dev/null @@ -1,365 +0,0 @@ - - - - - - - - - - - - - - - - - : - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/misc/124-130.xsl b/legacy-resumes/resume-1/xsl/misc/124-130.xsl deleted file mode 100644 index 06d9c2e..0000000 --- a/legacy-resumes/resume-1/xsl/misc/124-130.xsl +++ /dev/null @@ -1,51 +0,0 @@ - - - - - - - - - - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/misc/13x-140.xsl b/legacy-resumes/resume-1/xsl/misc/13x-140.xsl deleted file mode 100644 index bc6f07f..0000000 --- a/legacy-resumes/resume-1/xsl/misc/13x-140.xsl +++ /dev/null @@ -1,88 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/misc/default.xsl b/legacy-resumes/resume-1/xsl/misc/default.xsl deleted file mode 100644 index 682eee7..0000000 --- a/legacy-resumes/resume-1/xsl/misc/default.xsl +++ /dev/null @@ -1,276 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    -   - <? ?> -
    -     - - - - - ="" - - - - - - -
    -   - -
    -     - - - -
    - <!-- -
    -   --> -
    -     - - - -
    - <![CDATA[ -
    -   ]]> -
    -     - - - -
    -   - < /> -
    -     - - - - - -
    -   < - ></> -
    -     - - - -
    -
    - <>
    -
    -
     </>
    -
    -     - -     diff --git a/legacy-resumes/resume-1/xsl/misc/html_contemporary.xsl b/legacy-resumes/resume-1/xsl/misc/html_contemporary.xsl deleted file mode 100644 index ca85072..0000000 --- a/legacy-resumes/resume-1/xsl/misc/html_contemporary.xsl +++ /dev/null @@ -1,690 +0,0 @@ - - - - - - - - - - - - - - <xsl:apply-templates select="resume/header/name/firstname"/> - <xsl:text> </xsl:text> - <xsl:apply-templates select="resume/header/name/surname"/> - <xsl:text> - </xsl:text> - <xsl:value-of select="$resume.word"/> - - - - - - - - - - - - -
    - -
    - - -     - - - - - - - - - - - - , - - - - - -
    - - - - - -
    - - - - - - mailto: - - -
    -     - - -
    -     -
    -
    - -
    - - - -
    -     - - - - - -
    -

    - -

    - -
    - - : -
    -     - - : - mailto: - - -
    -     - - : - - - - -
    -     - - - - - - - - - - - - - - - - - - - - - - -
    - - -
    -     - - -
    -     - - - , - - - - - - - -
    - -     -     - - - - - - - - - - - - -
    - - -
    -     - - -
    -     - - - - - - -
    - -     - -
    - -     -     - - -
    - - -
    -     - - - - - - - ( - - ) - - -
    - -     -     - - - - - - - - - - - -
    - - - -     - - - -     -     - - - - - - - -
    -

    - - Objective -

    -     		-

    - -

    -
    -     - - - - - - - -
    -

    - - Experience -

    -     		-

    - -

    -
    -     - - - - - - - -
    -

    - - Education -

    -     		-

    - - -

    -
    -     - -

    - -

    - -     - -
    - -
    -     - -
    - - - - - - -
    -
    - -
    -
    -
    - §
    -
    - - - - - - - - - - - -
    -
    -
    - §
    -
    - - - -
    -     - - - - - - - - - -
    - - - - - -
    -     - - - -
    - -
    - -
    - -
    - -     -
    - -
    - - - - - - - - - -     - - -
      - -
    • - -
      • -       -
    -     - -
    - - -
    -     - - - - - - - - - - - -
    - §
    -
    - -
    -
    -     -

    - - - - - - -

    - -

    - -     - - - -

    - - -

    -     - - - - -     -     - -
    - - : -
    -     - -

    - -

    -     - - -
    - - - , - - -
    -     - - -
      - -
    • - -
      • -       -
    -     - - -

    - -

    -
      - -
    -     - - -
  • - -
    • -     - - -

    - -

    - -     - - -
    -

    - - - - - - - - - - - - - . This document uses - - http://xmlresume.sourceforge.net - XMLResume - -

    -
    -     - - - - - - - - - - - - - - - - -

    - -

    -     - - - - - - - - - - - - - - - - - - - - - -

    - -

    - -     - -

    - -

    -

    - -
    - - - : -
    -     - - : - mailto: - - -
    -     - - : - - - - -

    -     - - -
    - -
    -     - - - - - - - -
    -

    - -

    -     		-

    - -

    -
    -     - - - -
    - -
    -
    -     - -
    - -
    -     - - -
    -     - -     -     diff --git a/legacy-resumes/resume-1/xsl/misc/html_professional.xsl b/legacy-resumes/resume-1/xsl/misc/html_professional.xsl deleted file mode 100644 index beb99aa..0000000 --- a/legacy-resumes/resume-1/xsl/misc/html_professional.xsl +++ /dev/null @@ -1,688 +0,0 @@ - - - - - - - - - - - - - - <xsl:apply-templates select="resume/header/name/firstname"/> - <xsl:text> </xsl:text> - <xsl:apply-templates select="resume/header/name/surname"/> - <xsl:text> - </xsl:text> - <xsl:value-of select="$resume.word"/> - - - - - - - - - - - - -
    - -
    - - -     - - - - - - - - - - - - , - - - - - -
    - - - - - -
    - - - - - - mailto: - - -
    -     - - -
    -     -
    -
    - -
    -
    - - - -
    -
    -     - - - - - -
    -

    - -

    - -
    - - : -
    -     - - : - mailto: - - -
    -     - - : - - - - -
    -     - - - - - - - - - - - - - - - - - - - - - - -
    - - -
    -     - - -
    -     - - - , - - - - - - - -
    - -     -     - - - - - - - - - - - - -
    - - -
    -     - - -
    -     - - - - - - -
    - -     - -
    - -     -     - - -
    - - -
    -     - - - - - - - ( - - ) - - -
    - -     -     - - - - - - - - - - - -
    - - - -     - - - -     -     - - - - - - - -
    -

    - -

    -     		-

    - -

    -
    -     - - - - - - - -
    -

    - -

    -     		-

    - -

    -
    -     - - - - - - - -
    -

    - -

    -     		-

    - - -

    -
    -     - -

    - -

    - -     - -
    - -
    -     - -
    - - - - - - -
    - - -
    -
    - - § - - - - - - - - - - - - - - -
    - - § - - - - - - -
    -     - - - - - - - - - -
    - - - - - -
    -     - - - -
    - -
    - -
    - -
    -     -
    - -
    - - - - - - - - - -     - - -
      - -
    • - -
      • -       -
    -     - -
    - - -
    -     - - - - - - - - - - - - - § - - -
    -     -     -     -

    - - - - - - -

    - -

    - -     - - - -

    - - -

    -     - - - - -     -     - - - - : - - - -

    - -

    -     - - - - - - , - - - - - - -
      - -
    • - -
      • -       -
    -     - - -

    - -

    -
      - -
    -     - - -
  • - -
    • -     - - -

    - -

    - -     - - -
    -

    - - - - - - - - - - - - - . This document uses - - http://xmlresume.sourceforge.net - XMLResume - -

    -
    -     - - - - - - - - - - - - - - - - -

    - -

    -     - - - - - - - - - - - - - - - - - - - - - -

    - -

    - -     - -

    - -

    -

    - -
    - - - : -
    -     - - : - mailto: - - -
    -     - - : - - - - -

    -     - - -
    - -
    -     - - - - - - - -
    -

    - -

    -     		-

    - -

    -
    -     - - - - - - -
    -     - - - - -
    -     - - -
    -     - -     -     diff --git a/legacy-resumes/resume-1/xsl/misc/normalize-whitespace.xsl b/legacy-resumes/resume-1/xsl/misc/normalize-whitespace.xsl deleted file mode 100644 index f92ac8f..0000000 --- a/legacy-resumes/resume-1/xsl/misc/normalize-whitespace.xsl +++ /dev/null @@ -1,130 +0,0 @@ - - - - - - - - - - - - - -Element - - - - - - - - -Text: '' - - - - - - - - - - - - - - - Preceding sibling: '' - Output leading space - - - - - - Content: '' - - - - - - - - - - - - - - - Following sibling: '' - Output trailing space - - - - Preceding siblings: - - #/: '' - - - (Text) - - - (Element) - - - (Unknown node type) - - - - - Following siblings: - - #/: '' - - - (Text) - - - (Element) - - - (Unknown node type) - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/br-a4.xsl b/legacy-resumes/resume-1/xsl/output/br-a4.xsl deleted file mode 100644 index bf6c916..0000000 --- a/legacy-resumes/resume-1/xsl/output/br-a4.xsl +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/br-html.xsl b/legacy-resumes/resume-1/xsl/output/br-html.xsl deleted file mode 100644 index ca991af..0000000 --- a/legacy-resumes/resume-1/xsl/output/br-html.xsl +++ /dev/null @@ -1,42 +0,0 @@ - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/br-text.xsl b/legacy-resumes/resume-1/xsl/output/br-text.xsl deleted file mode 100644 index 4a12d33..0000000 --- a/legacy-resumes/resume-1/xsl/output/br-text.xsl +++ /dev/null @@ -1,42 +0,0 @@ - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/de-a4.xsl b/legacy-resumes/resume-1/xsl/output/de-a4.xsl deleted file mode 100644 index 652a4b0..0000000 --- a/legacy-resumes/resume-1/xsl/output/de-a4.xsl +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/de-html.xsl b/legacy-resumes/resume-1/xsl/output/de-html.xsl deleted file mode 100644 index 2fe7418..0000000 --- a/legacy-resumes/resume-1/xsl/output/de-html.xsl +++ /dev/null @@ -1,42 +0,0 @@ - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/de-text.xsl b/legacy-resumes/resume-1/xsl/output/de-text.xsl deleted file mode 100644 index b01b335..0000000 --- a/legacy-resumes/resume-1/xsl/output/de-text.xsl +++ /dev/null @@ -1,42 +0,0 @@ - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/fr-a4.xsl b/legacy-resumes/resume-1/xsl/output/fr-a4.xsl deleted file mode 100644 index 91f1ea4..0000000 --- a/legacy-resumes/resume-1/xsl/output/fr-a4.xsl +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/fr-html.xsl b/legacy-resumes/resume-1/xsl/output/fr-html.xsl deleted file mode 100644 index 8f57339..0000000 --- a/legacy-resumes/resume-1/xsl/output/fr-html.xsl +++ /dev/null @@ -1,42 +0,0 @@ - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/fr-text.xsl b/legacy-resumes/resume-1/xsl/output/fr-text.xsl deleted file mode 100644 index 2985283..0000000 --- a/legacy-resumes/resume-1/xsl/output/fr-text.xsl +++ /dev/null @@ -1,42 +0,0 @@ - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/it-a4.xsl b/legacy-resumes/resume-1/xsl/output/it-a4.xsl deleted file mode 100644 index 71ce886..0000000 --- a/legacy-resumes/resume-1/xsl/output/it-a4.xsl +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/it-html.xsl b/legacy-resumes/resume-1/xsl/output/it-html.xsl deleted file mode 100644 index 85f752c..0000000 --- a/legacy-resumes/resume-1/xsl/output/it-html.xsl +++ /dev/null @@ -1,42 +0,0 @@ - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/it-text.xsl b/legacy-resumes/resume-1/xsl/output/it-text.xsl deleted file mode 100644 index 9884b42..0000000 --- a/legacy-resumes/resume-1/xsl/output/it-text.xsl +++ /dev/null @@ -1,42 +0,0 @@ - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/nl-a4.xsl b/legacy-resumes/resume-1/xsl/output/nl-a4.xsl deleted file mode 100644 index 53e8016..0000000 --- a/legacy-resumes/resume-1/xsl/output/nl-a4.xsl +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/nl-html.xsl b/legacy-resumes/resume-1/xsl/output/nl-html.xsl deleted file mode 100644 index 094cbca..0000000 --- a/legacy-resumes/resume-1/xsl/output/nl-html.xsl +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/nl-text.xsl b/legacy-resumes/resume-1/xsl/output/nl-text.xsl deleted file mode 100644 index 4d35644..0000000 --- a/legacy-resumes/resume-1/xsl/output/nl-text.xsl +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/uk-a4.xsl b/legacy-resumes/resume-1/xsl/output/uk-a4.xsl deleted file mode 100644 index 4837789..0000000 --- a/legacy-resumes/resume-1/xsl/output/uk-a4.xsl +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/uk-html.xsl b/legacy-resumes/resume-1/xsl/output/uk-html.xsl deleted file mode 100644 index 6bed94d..0000000 --- a/legacy-resumes/resume-1/xsl/output/uk-html.xsl +++ /dev/null @@ -1,42 +0,0 @@ - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/uk-text.xsl b/legacy-resumes/resume-1/xsl/output/uk-text.xsl deleted file mode 100644 index c88c863..0000000 --- a/legacy-resumes/resume-1/xsl/output/uk-text.xsl +++ /dev/null @@ -1,42 +0,0 @@ - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/us-html.xsl b/legacy-resumes/resume-1/xsl/output/us-html.xsl deleted file mode 100644 index ab692c9..0000000 --- a/legacy-resumes/resume-1/xsl/output/us-html.xsl +++ /dev/null @@ -1,46 +0,0 @@ - - - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/us-letter.xsl b/legacy-resumes/resume-1/xsl/output/us-letter.xsl deleted file mode 100644 index 1e80f52..0000000 --- a/legacy-resumes/resume-1/xsl/output/us-letter.xsl +++ /dev/null @@ -1,46 +0,0 @@ - - - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/output/us-text.xsl b/legacy-resumes/resume-1/xsl/output/us-text.xsl deleted file mode 100644 index c4bcf5f..0000000 --- a/legacy-resumes/resume-1/xsl/output/us-text.xsl +++ /dev/null @@ -1,45 +0,0 @@ - - - - - - - - - - - - diff --git a/legacy-resumes/resume-1/xsl/paper/a4.xsl b/legacy-resumes/resume-1/xsl/paper/a4.xsl deleted file mode 100644 index 5872477..0000000 --- a/legacy-resumes/resume-1/xsl/paper/a4.xsl +++ /dev/null @@ -1,69 +0,0 @@ - - - - - - - - - - 297mm - 210mm - 20mm - 20mm - 20mm - 20mm - 20mm - 0mm - - - 50mm - - - diff --git a/legacy-resumes/resume-1/xsl/paper/letter.xsl b/legacy-resumes/resume-1/xsl/paper/letter.xsl deleted file mode 100644 index c1db1c6..0000000 --- a/legacy-resumes/resume-1/xsl/paper/letter.xsl +++ /dev/null @@ -1,75 +0,0 @@ - - - - - - - - - - - 11in - 8.5in - - - 0.75in - 0.6in - 0.6in - 0.6in - - - .5in - - - 0in - - - 1.65in - - - diff --git a/legacy-resumes/resume-1/xsl/params.xsl b/legacy-resumes/resume-1/xsl/params.xsl deleted file mode 100644 index f52239d..0000000 --- a/legacy-resumes/resume-1/xsl/params.xsl +++ /dev/null @@ -1,236 +0,0 @@ - - - - - - - - - - - - - - comma - - - 1 - - - - - 1 - - - - compact - - - - standard - - - - - single-line - - - - - - standard - - - - - - : - - - - , - - - - . - - - ( - ) - - - Subjects - - - - - comma - - - , - - - . - - - 1 - - - - ( - ) - - - ( - ) - - - - - — - - - , - - - . - - - - - - ../../css/compact.css - - - - - 1 - - - - - * - - - * - * - - - 72 - - - 4 - - - - - rule - 1pt - - - 0.750em - - - - - 0.4em - - - • - - 1.0em - - normal - bold - - - italic - - 10pt - serif - - 8pt - serif - - 10pt - sans-serif - bold - none - thin - - - 8pt - - bold - italic - monospace - - normal - bold - - - normal - bold - - italic - normal - - italic - normal - - italic - normal - - - italic - normal - - italic - normal - - italic - normal - - italic - normal - - - italic - normal - - diff --git a/legacy-resumes/resume.xml b/legacy-resumes/resume.xml deleted file mode 100644 index 9d1883c..0000000 --- a/legacy-resumes/resume.xml +++ /dev/null @@ -1,321 +0,0 @@ - - - - - - -
    - - Mr - Charles - Nathaniel - Wyble - - -
    - 1350 Victoria Ave Suite 116 - Oxnard - CA - 93035 -
    - - - 818-280-7059 - 805-984-9983 - charles@thewybles.com - http://www.thewybles.com/~charles - -
    - - - - - - To obtain a Linux system administration position with your organization. - - - - - Skills Summary - - A Linux system administrator with a detailed knowledge of Linux in a wide variety of industries and environments. - - - - A superb communicator who will thoroughly and efficiently handle any situation requiring communication with clarity and - conciseness. - - - - A frequent speaker/writer on a wide variety of I.T and open source matters, as well as a frequent contributer to open source - projects. - - - - System and Network Administration Skills - - UNIX Administration - Debian (stable/testing/unstable) - Mandrake - SUSE - Red Hat Enterprise Linux (3/4) - Shell scripting/automation (bash/python/tcl/php/awk/sed) - - - - Linux Server Applications - Apache 1/2 - Postfix/Qmail And Cyrus/Courier - OpenLdap/Samba - IpTables/Snort/Nessus/Nmap - Webmin - Courier/Cyrus - Proftpd - - - - Storage Administration - EMC Clarion (cx400 and cx700) - Equal Logic - Promise ISCSI - - - - Server Hardware - Dell 26/28/6850 - Hp NetServer - Custom built/whitebox - - - - Networking - Cabling (backbone/serial/desktop/fiber) - Routers (Cisco/Linksys/Dlink) - Load balancing (Cisco/Webmux) - Switches (Cisco Catalyst/Linksys) - - - - - - - - I have founded two open source projects, and participated in many more by writing code/documentation and providing user/developer - support. - - - - - The Chicago Project - - This project produced code and documentation to assist developers working with the Microsoft excel and compound - document/structured storage file formats on non Microsoft platforms. I am the project manager and lead developer - for this project which is now in maintenance mode. (http://chicago.sourceforge.net) - - - - - The Open Source Microsoft Exchange Replacement Platform - - The goal of this project is to produce code and documentation that will provide a fully open source - drop in replacement for Microsoft Exchange. I am the project manager, and founder. - I work closely with the lead developer and a worldwide team of programmers, documenters, and beta testers. - (http://www.thewybles.com/~charles/oser) - - - - - - - - - - Senior Linux System Administrator - Electronic Clearing House (http://www.echo-inc.com) - - October2006 - June2006 - - - - - - Senior Linux administrator for a 24x7 transaction processing/ecommerce/ - financial services environment. Responsibilities include: Working closely - with the network administration and infrastructure design teams. Ensuring continuous - uptime of multiple high visibility/high impact/high value envrironments including: - - - - - A 1TB MySQL database. - - - - A 300 GB Oracle database. - - - - A 1.5 GB Oracle Data warehouse. - - - - A 4,000 store LAMP based ecommerce system. - - - - - - - Deployment of encrypted backups - - Designed/tested/documented/deployed an enterprise wide Linux backup system. - All data stored on a central server with ISCSI attached network storage. - Uses GNUPG and tar over ssh. Backups/Restores tested on a weekly basis. - - - - - Deployment of core database infrastructure. - - Deployed 2 Oracle RAC clusters, each consisting of 3 Dell 6850's. They are equipped with Qual Dual Core - Xeon's and 32 Gb of RAM, running RedHat Enterprise Linux 4.0 64bit edition. - One environment is for staging and one is for production. EMC attached. This environment is used for - our Data Warehouse, our Transaction Processing Software and our Credit Card Clearing application. It is a - fundamental infrastructure component. The hardware and software was deployed in 3 business days. - - - - - File Integrity Checking - - Deployment of file integrity checking across 100 UNIX servers using fully open source software. - Used integrit http://integrit.sf.net and some custom shell scripts which were submitted - back upstream for inclusion. - - - - - - - - - Consultant - - February2005 - September2005 - - - - - - LAMP Deployment: Deployed a Debian Linux/Apache/MySQL/PHP system and educated the System Administration and Development - staff on configuration and use for an insurance company located in Burbank CA. - - - - - - Corporate Linux Deployment/Migration: Providing on going assistance to a medium sized business with a 100% conversion to - Linux on the Desktop as well as server. Utilizing SUSE Professional 6.5 for desktops and Debian GNU/Linux for - multiple production mission critical servers (Email/File Server/DNS/DHCP). This is for a manufacturing company in - Sylmar CA. - - - - - - Linux Deployment/Migration: Providing on going assistance to a small software development firm with a 100% - conversion to Linux. Utilizing Ubuntu Linux for desktops and Debian GNU/Linux for - servers (Email/File/LDAP/DNS/DHCP). February 2004-Present - - - - - - - - - - Junior System Administrator - Newroads http://www.newroads.com - - March2002 - February2005 - - - - - Disaster Recovery from an Informix Database Failure - - Assisted in the design/testing/and execution of a disaster recovery in real time - (on-the-fly). Wrote and documented the use of several utilities that cut down the amount of time to recovery by 30 - percent. - - - - - Streamlined the FTP Server Configuration process - - Streamlined the system configuration and new account creation process for ProFTPD on a mission critical FTP server. - This allowed faster turn around times and freed up I.T. resources. (1 month project) - - - - - Deployed open-source Remote Control Software - - Deplopyed/Secured/Optimized/Maintained UltraVNC remote control software. This allowed the Infrastructure Support team to more - rapidly respond to users support requests, and by doing so increase compliance with Service Level Agreements and increase - end-user satisfaction. (2 month project) - - - - - Network Infrastructure Upgrade - - Upgraded the network from hubs to Linksys managed switches to increase network performance and usability/reliability. - No network downtime occurred in the process of the upgrade (1 week project) - - - - - Hardware/Software Inventory Solution - - Wrote a custom software/hardware monitoring/reporting system to ensure compliance with software licensing and obtain an - accurate overview of company assets for inventory and disaster recovery purposes. (2 month project) - - - - - - - - - - - - Classes/Courses - - Course 319: Technical Writing A Comprehensive Hands On Introduction - Learning Tree International - May 2004 - - This course showed the entire process of developing clear concise effective technical writing in less time, that meets the needs - of the audience. - - - - - Course 364: Introduction to Internetworking Switches And Routers - Learning Tree International - October2004 - - This workshop presented a conceptual overview of networking fundemntals and technology. - - - - - -     diff --git a/legacy-resumes/resume/bio b/legacy-resumes/resume/bio deleted file mode 100644 index 8c5886b..0000000 --- a/legacy-resumes/resume/bio +++ /dev/null @@ -1 +0,0 @@ -Charles Wyble is an experienced technologist and entrepreneur. He has 15+ years of experience ranging from mom/pop to fortune 500 (Disney,Fox,DOD) diff --git a/legacy-resumes/resume/resume.txt b/legacy-resumes/resume/resume.txt deleted file mode 100644 index 4352397..0000000 --- a/legacy-resumes/resume/resume.txt +++ /dev/null @@ -1,20 +0,0 @@ - -2002 to 2005 Accretive Commerce (accquired by e-bay) -2007 to 2008 Walt Disney Internet Group - -HostGator.com - Global Site Reliability Engineer - March 2011 to September 2012 - Automated over 90% of daily common customer requests - Handled training, mentoring, quality checks and overall team improvement for junior and mid level admins - Worked with the security desk to facillitate 24/7 restores of compromised sites - - -TippingPoint - Linux System Engineer - October 2012 to present - Rundeck - Slack - Automation - 3x growth - Spin out to TrendMicro - Core information assets - SVN/GIT - Confluence - diff --git a/CurrentResume/non-cv/@ReachableCEO/Resume/Non-CV/Projects.md b/non-cv/@ReachableCEO/Resume/Non-CV/Projects.md similarity index 100% rename from CurrentResume/non-cv/@ReachableCEO/Resume/Non-CV/Projects.md rename to non-cv/@ReachableCEO/Resume/Non-CV/Projects.md diff --git a/CurrentResume/non-cv/@ReachableCEO/Resume/Non-CV/Work-History.md b/non-cv/@ReachableCEO/Resume/Non-CV/Work-History.md similarity index 100% rename from CurrentResume/non-cv/@ReachableCEO/Resume/Non-CV/Work-History.md rename to non-cv/@ReachableCEO/Resume/Non-CV/Work-History.md diff --git a/CurrentResume/non-cv/build.sh b/non-cv/build.sh similarity index 100% rename from CurrentResume/non-cv/build.sh rename to non-cv/build.sh diff --git a/CurrentResume/non-cv/output/intermediate/CharlesNWybleShortResume.md b/non-cv/output/intermediate/CharlesNWybleShortResume.md similarity index 100% rename from CurrentResume/non-cv/output/intermediate/CharlesNWybleShortResume.md rename to non-cv/output/intermediate/CharlesNWybleShortResume.md