From: Francois Lafortune [EMAIL PROTECTED]
On 7-Nov-07, at 12:36 AM, Tantek Çelik wrote:
Then follow-up with reading POSH resources:
http://microformats.org/wiki/posh
I read that, I find the word semantic ambiguous in some contexts,
just as tabular data may be ambiguous to some.
In
One more change I'm considering for Operator.
Removing support for an adr by itself in the UI.
Basically the problem is that unlike just about other microformat
(except geo), there's really nothing good to display for adr in the UI
(the address just looks silly). And because I try so hard to
Sorry, forgot the reference link:
http://microformats.org/wiki/hresume#Experience
~ Tim
tjameswhite.com'http://www.tjameswhite.com;tjameswhite.com
- Original Message
From: Tim White [EMAIL PROTECTED]
To: Microformats Discuss microformats-discuss@microformats.org
Sent: Thursday,
I was doing some research on the hResume page and noticed that the include
pattern hadn't been updated.
I've gone ahead and updated the page to reflect the updates to the include
pattern.
I have added a note with reference to the include-pattern and added an example
above the object example.
[EMAIL PROTECTED] wrote:
From: Katrina [EMAIL PROTECTED]
The quote from RFC 2426 refers to 'the' locality and 'the' extended
address, which to me, sounds like exactly one.
Is it legitimate to have multiple localities or extended addresses?
My bad there, sorry for the confusion Katrina.
One more change I'm considering for Operator.
Removing support for an adr by itself in the UI.
Basically the problem is that unlike just about other microformat
(except geo), there's really nothing good to display for adr in the UI
(the address just looks silly). And because I try so hard to
