From mail at tobyinkster.co.uk Thu Mar 18 01:38:24 2010
From: mail at tobyinkster.co.uk (Toby Inkster)
Date: Thu Mar 18 01:38:36 2010
Subject: [uf-new] hResume issue: embedding hCard for job title leads to
ambiguities.
Message-ID: <1268905104.29519.24.camel@ophelia2.g5n.co.uk>
I quickly documented this issue on the wiki yesterday:
http://microformats.org/wiki/hresume-issues#issue-20100317
While porting/testing my hResume parser, I ran into an issue. It is
suggested that to mark up job titles, roles, etc within hResume
experiences, an hCard should be embedded into the experience. I'm going
to call this the "JThC" (Job Title hCard), just because I'd like a term
to unambiguously refer to it.
With the experience already being an hCalendar event, there are several
places an hCard could already legitimately be embedded within it - e.g.
class="location vcard". So the issue is that there's not really any way
to differentiate between the JThC versus other hCards within the
experience.
There seem to be three possible ways of disambiguating - two that
involve spec changes, and one that doesn't but I think would be less
reliable and harder to implement.
1. The JThC should be given class="contact" within the hCalendar event.
The CONTACT property is defined in RFC 2445 (iCalendar) as:
Purpose: The property is used to represent contact information or
alternately a reference to contact information associated with the
calendar component.
So an hResume experience would look something like:
May 2005 -
June 2008 -
Senior Vice-President
CompuGlobalHyperMeganet
This industry moves so fast it's really hard to tell.
2. Same dealy, but defining a new hResume-specific property rather than
reusing hCalendar's contact property. e.g.
May 2005 -
June 2008 -
Senior Vice-President
CompuGlobalHyperMeganet
This industry moves so fast it's really hard to tell.
3. This is the option which requires no spec changes. We simply specify
that the JThC is the first hCard within the experience which is not also
a location/attendee/organizer/contact(?) hCard.
May 2005 -
June 2008 -
Senior Vice-President
CompuGlobalHyperMeganet
This industry moves so fast it's really hard to tell.
--
Toby A Inkster
From info at csarven.ca Thu Mar 18 02:58:29 2010
From: info at csarven.ca (Sarven Capadisli)
Date: Thu Mar 18 02:58:38 2010
Subject: [uf-new] hResume issue: embedding hCard for job title leads to
ambiguities.
In-Reply-To: <1268905104.29519.24.camel@ophelia2.g5n.co.uk>
References: <1268905104.29519.24.camel@ophelia2.g5n.co.uk>
Message-ID: <1268909909.2925.22.camel@csarven-laptop>
On Thu, 2010-03-18 at 09:38 +0000, Toby Inkster wrote:
> I quickly documented this issue on the wiki yesterday:
>
> http://microformats.org/wiki/hresume-issues#issue-20100317
>
> While porting/testing my hResume parser, I ran into an issue. It is
> suggested that to mark up job titles, roles, etc within hResume
> experiences, an hCard should be embedded into the experience. I'm going
> to call this the "JThC" (Job Title hCard), just because I'd like a term
> to unambiguously refer to it.
>
> With the experience already being an hCalendar event, there are several
> places an hCard could already legitimately be embedded within it - e.g.
> class="location vcard". So the issue is that there's not really any way
> to differentiate between the JThC versus other hCards within the
> experience.
What do you think about:
The hCard with class="location vcard" could legitimately contain
rel="contact". This may give that distinction.
-Sarven
From mail at tobyinkster.co.uk Thu Mar 18 06:59:27 2010
From: mail at tobyinkster.co.uk (Toby Inkster)
Date: Thu Mar 18 06:59:35 2010
Subject: [uf-new] hResume issue: embedding hCard for job title leads to
ambiguities.
In-Reply-To: <1268909909.2925.22.camel@csarven-laptop>
References: <1268905104.29519.24.camel@ophelia2.g5n.co.uk>
<1268909909.2925.22.camel@csarven-laptop>
Message-ID: <1268924367.29519.34.camel@ophelia2.g5n.co.uk>
On Thu, 2010-03-18 at 11:58 +0100, Sarven Capadisli wrote:
> The hCard with class="location vcard" could legitimately contain
> rel="contact". This may give that distinction.
The definition of rel=contact is:
Someone you know how to get in touch with.
Which seems like it's only intended when linking to a page that
represents a person - not an organisation or place. Though perhaps
Tantek (as co-author of the XFN profile) could clarify that.
Either way, this is only useful for hCards that contain a link, which
not all do.
--
Toby A Inkster
From mail at tobyinkster.co.uk Thu Mar 25 07:51:57 2010
From: mail at tobyinkster.co.uk (Toby Inkster)
Date: Thu Mar 25 08:00:30 2010
Subject: [uf-new] hRecipe issue - value and type
Message-ID: <1269532317.1205.66.camel@ophelia2.g5n.co.uk>
See .
The suggested way of using 'value' and 'type' within hRecipe is strange,
and quite different from hCard. This is especially problematic for
'value' because of its role in value excerpting.
My suggestion, and how I plan on implementing hRecipe in
HTML::Microformats is to parse class="ingredients" and class="nutrition"
as simple strings with no subproperties, using class="value" for value
excerpting in a manner consistent with other microformats.
--
Toby A Inkster