1. Suppose a web page has multiple geo Microformats. The Operator
Find a Google Map currently allows only a mashup of one geo
Microformat at a time with Google Maps.
I would like an option that
would display all the geo Microformats simultaneously. For example, a
web page that shows the
Hello Michael,
I think Mozilla Corporation (the main backers of Firefox) have a
special relation with Google.
So, it's probably not so much of an issue.
See ya
On 5/2/07, Michael MD [EMAIL PROTECTED] wrote:
1. Suppose a web page has multiple geo Microformats. The Operator
Find a Google
In message [EMAIL PROTECTED], Tantek Çelik
[EMAIL PROTECTED] writes
AndyMabbett and Gazza, apologies for the inconvenience of the temporary
blocking. Thanks very much for your patience. Blocks have been
removed.
You appear to have not received; to have overlooked; or to have
deliberately
In message
[EMAIL PROTECTED], Mike
Kaply [EMAIL PROTECTED] writes
Thanks Roger, I really want feedback like this!
On 5/1/07, Costello, Roger L. [EMAIL PROTECTED] wrote:
Hey Mike,
Here's my wish list for Operator:
1. Suppose a web page has multiple geo Microformats. The Operator
Find a
On 5/1/07, Andy Mabbett [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Dan Champion [EMAIL PROTECTED]
writes
If the aim is to retain the data in the body, yet render it invisible
to all users, including those of assistive technologies, what about
using a comment as the data container:
Ben Buchanan wrote:
Hi Jeremy,
I'd be interested in hearing other arguments for or against
this idea.
I think it's a humans vs. machines issue. To my mind, the
ABBR element is there to provide additional information to
the user (the human). In this case, it's being used to add a
Hello, all! I'm writing to let µF folks know about this upcoming event.
Some of you have already received personal invitations, but I wanted to
send a broadcast for all the people I don't know personally.
RecentChangesCamp is the international unconference for wiki developers,
users, theorists
M. Jackson Wilkinson wrote:
If a patent were granted, then the holders could approach users of the
now-patented process and hold them accountable for royalties and
licensing fees. All of a sudden, anyone from Microsoft to your small
business can be threatened with, at minimum, a long legal
Hi Folks,
I have written a short wiki article describing how an information
design may evolve from custom XML tags, to XHTML tags, to XHTML +
Microformats:
http://www.xfront-wiki.com/wiki/index.php?title=Alternative_Information
_Designs
Comments are welcome.
/Roger
On 5/2/07, Costello, Roger L. [EMAIL PROTECTED] wrote:
Hi Folks,
I have written a short wiki article describing how an information
design may evolve from custom XML tags, to XHTML tags, to XHTML +
Microformats:
http://www.xfront-wiki.com/wiki/index.php?title=Alternative_Information
_Designs
Two of my recent edits, soon reverted by Tantek, were to remove a red
link, under the heading see also to from:
http://microformats.org/wiki/show-formats
and from:
http://microformats.org/wiki/showroll-brainstorming
The red link was to:
/microshow
and had existed
Andy Mabbett wrote:
/video-metadata-models
/microshow
That's incredibly strange - both of these links appear under the
Related and See Also sections of those pages. Should red-link items
be placed under each of those sections? There isn't anything at the end
of the links to relate to or see?
With all of the discussion about iso dates being unreadable and that an
iso date isn't necessarily required when someone enters a date (i.e.
saying 24th June doesn't translate into a single date, neither does
'thursday'). Shouldn't the focus be on trying to standardise date
formats rather than
Tim Parkin wrote:
With all of the discussion about iso dates being unreadable and
that an
iso date isn't necessarily required when someone enters a date (i.e.
saying 24th June doesn't translate into a single date, neither does
'thursday'). Shouldn't the focus be on trying to standardise date
From: James Craig [EMAIL PROTECTED]
To: Microformats Discuss microformats-discuss@microformats.org
Sent: Thursday, May 03, 2007 8:56 AM
Subject: Re: [uf-discuss] human readable date parsing
Tim Parkin wrote:
With all of the discussion about iso dates being unreadable and that an
iso date
Paul Wilkins wrote:
What if the value class was to be used with a hidden class. Then they
would serve their purpose, they wouldn't interfere with existing styles
and could be interpreted correctly.
.hidden {display: hidden}
Then the human-readable and machine-readable can be mashed
James Craig wrote:
Tim Parkin wrote:
With all of the discussion about iso dates being unreadable and that an
iso date isn't necessarily required when someone enters a date (i.e.
saying 24th June doesn't translate into a single date, neither does
'thursday'). Shouldn't the focus be on trying
James Craig wrote:
Tim Parkin wrote:
[...] Shouldn't the focus be on trying to standardise date
formats rather than trying to hide the iso date? If we can get a parser
to recognise 'human readable' dates (which *is* possible, if not totally
easy, http://labix.org/python-dateutil for a python
So, I started this response thinking How does a full-string timestamp /not/
disambiguate a March 2 date in the following?
My answer is: by not being human-readable :) The example in the
original post shows the problem:
abbr class=dtstart title=20070312T1700-06
March 12, 2007 at 5 PM, Central
19 matches
Mail list logo
