Thanks for the article.
-Mike Schinkel
http://www.mikeschinkel.com/blogs/
http://www.welldesignedurls.org/
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andy
Mabbett
Sent: Saturday, November 25, 2006 10:39 AM
To: Microformats Discuss
Subject:
Hi Folks,
I am when using Brian Suda's xhtml2kml.xsl tool to create a KML file
from an hCard. Then I display the KML on Google Earth.
What is the best practice for wrapping hCard data with geo, which will
result in the most informative rendering on Google Earth? Let me
explain what I mean.
Hi all
I am adding hcard to a page and wondered if there was a pattern for defining
the rss feed for an individual.
It seems like there would already be something simple, i.e. class=rss or
rel=rss. I didnt see anything.
Do you have a suggestion?
Thanks
Ted Drake
Yahoo! Tech - Tech Made
In message [EMAIL PROTECTED],
Costello, Roger L. [EMAIL PROTECTED] writes
I am when using Brian Suda's xhtml2kml.xsl tool to create a KML file
from an hCard. Then I display the KML on Google Earth.
What is the best practice for wrapping hCard data with geo, which will
result in the most
On Nov 20, 2006, at 10:08 AM, Ben Ward wrote:
One thing I would request though is that the results listing also
be marked up with hCard, since that would enable use of existing
Microformats browser tools to transfer hCards from the results into
desktop address books and so forth.
If you
On Nov 25, 2006, at 11:19 AM, Ryan Cannon wrote:
Is it perhaps useful to talk about implied vcards? The rule could
be similar to:
If a an element with class=vcard does not have any hCard class
names, imply the entire content as an fn field, and attempt to
apply the implied n
On Nov 27, 2006, at 6:55 AM, Ryan Cannon wrote:
It would seem that the rule still applies: [EMAIL PROTECTED] would
be both the FN and Nickname fields. Perhaps parsing could key on
the protocol: mailto would imply an
EMAIL;TYPE=Internet
and http(s) would imply a URL. Any other protocols
On Nov 30, 2006, at 1:24 PM, Ryan King wrote:
On Nov 27, 2006, at 6:55 AM, Ryan Cannon wrote:
It would seem that the rule still applies: [EMAIL PROTECTED]
would be both the FN and Nickname fields. Perhaps parsing could
key on the protocol: mailto would imply an
EMAIL;TYPE=Internet
and
Hi, I can't tell from the ending of the most recent trail of emails
about the citation uf whether a consensus was reached about encoding
page values and ranges, or if everyone just got tired after 51 emails.
There was some evidence of research that I think ought to be put on
the
Based on the existence of a URL in the examples listed at the end of
this email, I propose modifying the working straw format at
http://microformats.org/wiki/citation-brainstorming#Brian.27s_Straw_format
to include a URL field, denoting the URL to a copy of the work
available online (often a PDF,
On 11/30/06, Michael McCracken [EMAIL PROTECTED] wrote:
I also suggest that in the case of identifiers like a DOI or ISBN
which can be represented as a parameter in a link to doi.org or some
other resolver, that the format encourage using a URL field for those
identifiers and not include
On 11/30/06, Bruce D'Arcus [EMAIL PROTECTED] wrote:
On 11/30/06, Michael McCracken [EMAIL PROTECTED] wrote:
I also suggest that in the case of identifiers like a DOI or ISBN
which can be represented as a parameter in a link to doi.org or some
other resolver, that the format encourage using a
12 matches
Mail list logo
