Hi:
I am working on our government web site and am working towards
implementing the hCard microformat for our contact pages. However, I am
having a bit of difficulty with phone numbers.
To verify my work, I installed the Tails Export extension for Firefox
but when I export to Microsoft Outlook
I was able to get phone numbers to export into Outlook by specifying a
type and value. I have updated your example as follows:
div class=vcardspan class=fnJim McAuley/span, span
class=telspan class=value705-670-5855/span (span
class=typeWork/span)/span, a class=email
href=mailto:[EMAIL
On Jun 15, 2007, at 8:15 AM, Dougal Campbell wrote:
Okay, so I started a new job recently.
The web site and service has a lot to do with SEO. But despite
that, the
HTML is a mess of table-based layout and tag soup. I'm hoping I can
change that in time, but it won't happen quickly. But one
On Jun 20, 2007, at 11:41 AM, Rickards, Julian (NDM) wrote:
Hi:
I am working on our government web site and am working towards
implementing the hCard microformat for our contact pages. However,
I am
having a bit of difficulty with phone numbers.
To verify my work, I installed the Tails
Your suggestion seems to agree with what Ryan wrote moments before you
that type must be specified. However, given that all of the numbers
are work (voice) numbers and everyone in my work group shares a common
fax number, it seemed redundant to write span class=typeWork/span
for each person.
It
On Jun 20, 2007, at 1:57 PM, Rickards, Julian (NDM) wrote:
However, given that all of the numbers
are work (voice) numbers and everyone in my work group shares a common
fax number, it seemed redundant to write span class=typeWork/
span
for each person.
You can use the include pattern to
- Original Message -
From: Scott Reynen [EMAIL PROTECTED]
You can use the include pattern to remove some of this redundancy:
http://microformats.org/wiki/include-pattern
E.g.:
pStaff span class=type id=work-typework/span phone
numbers:/p
...
div class=vcard
p class=fnPerson One/p
p
In message [EMAIL PROTECTED], Scott
Reynen [EMAIL PROTECTED] recommended:
a href=#work-title class=include/a
I thought we'd decided that empty anchor tag-pairs were bad, from an
accessibility PoV?
--
Andy Mabbett
___
microformats-discuss mailing
From: Andy Mabbett [EMAIL PROTECTED]
I thought we'd decided that empty anchor tag-pairs were bad, from an
accessibility PoV?
Is the object tag to be used instead for the include pattern?
--
Paul Wilkins
___
microformats-discuss mailing list
Paul Wilkins wrote:
From: Andy Mabbett [EMAIL PROTECTED]
I thought we'd decided that empty anchor tag-pairs were bad, from
an accessibility PoV?
Is the object tag to be used instead for the include pattern?
The object include pattern has some performance problems, it would
be best to
From: James Craig [EMAIL PROTECTED]
Paul Wilkins wrote:
Is the object tag to be used instead for the include pattern?
The object include pattern has some performance problems, it would be
best to use the anchor include pattern but include some text indicated
the marker that was being
James Craig wrote:
Paul Wilkins wrote:
From: Andy Mabbett [EMAIL PROTECTED]
I thought we'd decided that empty anchor tag-pairs were bad, from
an accessibility PoV?
Is the object tag to be used instead for the include pattern?
The object include pattern has some performance problems, it
Is the object tag to be used instead for the include pattern?
given the complexity it adds to non-browser-based parsers I'm wondering if
include-pattern is too much trouble to bother with
___
microformats-discuss mailing list
13 matches
Mail list logo
