<!-- This is a work in progress (i.e. NOT A COMPLETED EXAMPLE!)           -->

<!--                                                                         
	                                                                     
     This is an extreme example of the possible power of rezML. This single  
     document can be used to generate the following:                         
	1) A single resume                                                   
	2) A list of applicants for a single job                             
	3) A list of applicants by job (i.e. multiple jobs)                  
	4) A single job                                                      
	5) A single joblist (i.e. grouping of jobs)                          
	6) Multiple joblists (could even do it by company or recruiter)      
	7) A list of companies that a single applicant applied for*          
	8) A list of jobs that a single applicant applied for (could even do 
	   it by company or recruiter)*                                      
	9) A contact list of applicants (or a mail merge, ect...)            
	10) Could do all sorts of nifty things with multiple transactions    
	    (like database adds, updates, deletes, etc...)                   
	11) A single applicant with multiple resumes for different jobs      
	                                                                     
     Note: most uses of rezML do not require this level of complexity!       
	                                                                     
     * only if single resume used.                                           
	                                                                     
                                                                          -->

<rezml>


<!--  type='master' suggested use:                                           
      Use to indicate authoritative source                                -->

   <transaction ID='rezml1' timestamp='20010806162900' type='update'>
      <job-ref job-id='j1' />
      <job-ref job-id='j2' />
      <job-ref job-id='j3' />
      <job-ref job-id='j4' />
   </transaction>

   <resume ID='r1' type='master' active='y' confidential='n'>
   
      <title></title>

      <objective></objective>

      
      <preferences>
<!-- two weeks, etc... -->
         <available></available>
         <job-type>permanent</job-type>
         <job-type>contract</job-type>
         <job-type>full-time</job-type>
         <description></description>
         <relocate>yes</relocate>
         <location>San Francisco</location>
      </preferences>

      <work-status country-code='us'>I am authorized to work in this country for any employer.</work-status>
      <url type='homepage'>http://</url>

      <url type='portfolio'>http://</url>
      
<!--  type='resume' suggested use: URL where latest version of this resume   
can be found. The idea is that resumes instances will get stale over time -->
      <url type='resume'>http://</url>

      <apply>
         <job-ref job-id='j1' />
         <job-ref job-id='j2' />
         <job-ref job-id='j3' />
         <job-ref job-id='j4' />
      </apply>

      <applicant>
         <full-name>
            <prefix>Mr.</prefix>
            <first-name>John</first-name>
            <preferred-name>Pete</preferred-name>
            <middle-name>Peter</middle-name>
            <surname>Leth-Nissen</surname>
            <suffix>Jr.</suffix>
         </full-name>
         <contact>
            <phone type='home'>
               <country-code />
               <area-code>912</area-code>
               <number>238-3536</number>
               <extension type='pin'>4356</extension>
            </phone>
         </contact>
         <email type='home'>wjsearch@yahoo.com</email>
      </applicant>

      <employment-history>
         <employer />
         <title />
         <period />
         <description>
         <li></li>
         </description>      
      </employment-history>
      
<!--  May generalize this node - still thinking about it-->
      <memberships>
         <membership type='professional'>
            <name></name>
            <period></period>
            <title>member</title>
            <organization>Institute of Electrical and Electronics Engineers (IEEE)</organization>
            <description></description>
         </membership>
      </memberships>

<!--  May generalize this node - still thinking about it-->
      <projects>
         <project type='internet'>
            <name>DEturbo</name>
            <period></period>
            <title></title>
            <organization></organization>
            <description>Open source collaboration tool for IRC. Message management, file sharing, text editing, and personalization</description>
         </project>
      </projects>
      
      <education>
      </education>

<!--  May generalize this node - still thinking about it-->
      <publications>
         <publication>
         </publication>
      </publications>

      
      <skill-list>
         <title>Markup Languages</title>
         <skill last-used='1999' years-used='10' level='10'>XML</skill>
      </skill-list>
      
<!--  Really don't like this node but after reviewing listing services I added it.-->
      <keywords>
         <keyword>
         </keyword>
      </keywords>
      
      <references>
         <reference>
         </reference>
      </references>

   </resume>

   <job ID='j1' type='external' active='y'>
   </job>

   <job-list ID='jl1' type='master'>
      <job-ref job-id='j1' />
      <job-ref job-id='j2' />
      <job-ref job-id='j3' />
      <job-ref job-id='j4' />
   </job-list>

   <employer ID='e2'>
   </employer>

   <recruiter ID='rc1'>
   </recruiter>

   <listing-service ID='l1'>
   </listing-service>

</rezml>