drewp for 2005 April 6 (entry 0)

< tmrs and mapping
Screenwriter John August uses python >

[Trackback URL for this entry] 2005-04-06T20:22:03 What's wrong with resume formats:

Everyone seems to have an HTML resume, and maybe pdf/msword/text versions too. A few people are generating these from a single source, which is obviously what we all would like to do. Also, many of us would appreciate being able to dynamically create resumes with various amounts and types of data selected from our complete pool of bio and work history.

Imagine an actor who is also doing clerical work to pay the bills. He will have two extremely different resumes for the two types of jobs he applies for, but they will share some data (contact info; perhaps the 3 most prestigious jobs in the other field than the one the resume is being generated for).

Imagine a web contractor who works hard and takes a lot of small contracts- she should probably post a summary resume that lists only selected past contracts, but that selection changes every time a new job gets added. Perhaps the selection is based on age (always list all jobs in the last year, but only the best jobs older than 5 years), or based on "similarity" to the prospective job. When she's pitching an "online store for custom garments", the resume program can produce a resume that has the interesting relevant past jobs. It might be wrong, in which case she can add hints to the data to make that resume come out better.

http://internetalchemy.org/2005/04/refactoring-bio-with-einstein-part-1-first-steps got me thinking about this issue again.

http://captsolo.net/semweb/resume/cv.rdfs is the first resume vocab for RDF that I found, and it looks limiting to me.


[Main]

Unless otherwise noted, all content licensed by Drew Perttula
under a Creative Commons License.