I've been thinking about hResume, and I have two thoughts on it:
First, I don't think having multiple hCard representations of the
same person is the best way to organize the data. I think it would
make more sense to make the entire hResume an hCard, since it's all
representing the same person. This poses the problem of vCard not
allowing multiple ORG and ROLE attributes, but I think this was a
mistake in vCard, and was another mistake to adopt from vCard to
hCard. I say this because I don't know a single person who doesn't
have multiple roles in multiple organizations right now, not even
accounting for history.
My other thought is that I think the general hResume conceptual model
for dates should be more like hAtom's.
hAtom: feed contains entries with date attributes
hResume: resume contains dates which contain contact information
I think conceptually, the dates in hResume are attributes of the
contact information, just as they are attributes of the entries in
hAtom. The contact information holds meaning without the dates, but
the dates don't mean anything outside the context of the contact
information. If we intend to assert a date of relevance for hCards,
I think that information should be contained *within* the hCard.
Peace,
Scott
_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss
