On 4/26/07, Andy Mabbett [EMAIL PROTECTED] wrote:
That's a point-of view, but not a definitive fact. Who says it's not a
microformat? With what authority?
Microformats are the things that are following the process on microformats.org.
The authority presumably comes from whoever made up the
On Thu, Apr 26, 2007 at 07:40:01PM -0500, Scott Reynen wrote:
On Apr 26, 2007, at 5:54 PM, Dr. Ernie Prabhakar wrote:
I realize you may not like that distinction, and we may or may not
have any ability to enforce that, but I think it is only reasonable
for us to attempt to enforce
Keith Grennan wrote:
I agree. I really hope microformat won't turn into just another
term for semantic HTML. Clear communication is difficult enough
already without additional ambiguity.
I think it already has.
It's like Adobe trying to control how people use the word 'photoshop'.
It
Hi,
I was inspired to write an article about why microformats are cool and
important. Feel free to take a look.
http://nearlyfree.org/microformats-sip-sea-water
...there are 14 billion websites, but like the scattered builders of the
tower of Babel, these sites are all speaking different
-- Forwarded message --
From: Manu Sporny [EMAIL PROTECTED]
Date: Apr 27, 2007 3:42 PM
Subject: Re: [uf-new] Legal implications of using Microformats
To: For discussion of new microformats. [EMAIL PROTECTED]
Brian, to answer your question -
(from
Brian Suda wrote:
--- if you can give-us any other information, who exactly the company
is, etc and any other information from the legal team we can attempt
to work around these problems or debunk the FUD.
Our company is Digital Bazaar, Inc. we provide digital content delivery
services (buying
Hi everyone,
Have you seen this post over on the WaSP blog?
http://www.webstandards.org/2007/04/27/haccessibility/
It's a well-reasoned and calm look at the problems caused by the abbr
pattern in today's screenreaders (though some of the comments are a
little less calm). Rather than just
This is another response to the WaSP post about screen reader issues
with the abbr pattern:
http://www.webstandards.org/2007/04/27/haccessibility/
As I pointed out in a comment on the post, their example uses the
condensed form of the datetime, e.g.:
title=20070312T17
This currently
Jeremy wrote:
The simplest solution is to simply expand the pattern to allow the
same usage of class and title on elements other than abbr (span is
specifically mentioned but this would potentially apply to any element).
.
I'd be interested in hearing other arguments for or against
Hi Jeremy,
On Apr 27, 2007, at 9:49 AM, Jeremy Keith wrote:
However, the datetime can also be written with dashes and colons
like this:
title=2007-03-12T17:00:00
http://microformats.org/wiki/datetime-design-pattern
Would everyone agree that, for the sake of screen reader users, we
should
On 4/27/07 10:47 AM, Dr. Ernie Prabhakar [EMAIL PROTECTED]
wrote:
Hi Jeremy,
On Apr 27, 2007, at 9:49 AM, Jeremy Keith wrote:
However, the datetime can also be written with dashes and colons
like this:
title=2007-03-12T17:00:00
http://microformats.org/wiki/datetime-design-pattern
On 4/27/07 10:18 AM, John Beales [EMAIL PROTECTED] wrote:
Jeremy wrote:
The simplest solution is to simply expand the pattern to allow the
same usage of class and title on elements other than abbr (span is
specifically mentioned but this would potentially apply to any element).
.
Hi Jeremy,
Putting hyphens/dashes in between the integers sounds like a good idea
to me. I do that for most file names that need a date, so personally
I'm on board.
I'd be really interested in seeing if this does have an impact on the
screen readers output at some point.
It's definitely worth
In message [EMAIL PROTECTED], Dr. Ernie
Prabhakar [EMAIL PROTECTED] writes
That's a point-of view, but not a definitive fact. Who says it's
not a microformat? With what authority?
Um, is there any authority you *would* accept for that usage?
It doesn't matter what I do, or would, accept; it's
On 4/27/07 11:11 AM, David Mead [EMAIL PROTECTED] wrote:
Putting hyphens/dashes in between the integers sounds like a good idea
to me. I do that for most file names that need a date, so personally
I'm on board.
I'd be really interested in seeing if this does have an impact on the
screen
In message [EMAIL PROTECTED], Tantek Çelik
[EMAIL PROTECTED] writes
b) This still conforms with all the relevant W3C recommendations
ISO8601 is an ISO standard, not W3C.
I rather suspect that this was a reference to the WCAG-WAI
recommendations, not to any date-related format.
--
Andy
Hi Andy,
On Apr 27, 2007, at 11:21 AM, Andy Mabbett wrote:
In message [EMAIL PROTECTED], Dr. Ernie
Prabhakar [EMAIL PROTECTED] writes
That's a point-of view, but not a definitive fact. Who says it's
not a microformat? With what authority?
Um, is there any authority you *would* accept for
In message
[EMAIL PROTECTED], Brian
Suda [EMAIL PROTECTED] writes
It's not about whether they are behind the times or not - the really big
problem in the ambiguous copyright and patent statements, compounded by
the prevention of making derivative works, etc.
--- is this a REAL problem, or do
In message [EMAIL PROTECTED], Dr. Ernie
Prabhakar [EMAIL PROTECTED] writes
On Apr 27, 2007, at 11:21 AM, Andy Mabbett wrote:
In message [EMAIL PROTECTED], Dr. Ernie
Prabhakar [EMAIL PROTECTED] writes
That's a point-of view, but not a definitive fact. Who says it's
not a microformat? With
In message [EMAIL PROTECTED], Tantek Çelik
[EMAIL PROTECTED] writes
Even more so, we should evangelize browsers that have plugins and
extensions for microformats.
And most of all, browsers that have built-in support for microformats.
Other than FireFox, what browsers do? Are there any moves to
In message [EMAIL PROTECTED], Jeremy
Keith [EMAIL PROTECTED] writes
title=20070312T17
[...]
can also be written with dashes and colons like this:
title=2007-03-12T17:00:00
Would everyone agree that, for the sake of screen reader users, we
should update the wiki to strongly encourage this
Both upcoming and eventful do not have dashes in their dates.
They will need to be evangelized.
Mike
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
If anyone is interested in helping define the user interface for
microformat in Firefox 3 and Operator, we're trying to have a
discussion at:
https://labs.mozilla.com/forum/index.php/topic,77.0.html
I'm open to any and all opinions/suggestions.
Thanks
Mike Kaply
Mike Kaply wrote:
Both upcoming and eventful do not have dashes in their dates.
They will need to be evangelized.
Mike
Wikevent.org's got it right
http://wikevent.org/en/Joan_Armatrading_2007_5_7 we don't need
evangelising ;-)
Spike
___
In message
[EMAIL PROTECTED], Ciaran
McNulty [EMAIL PROTECTED] writes
On a side-note, the issue of what to do with user-entered names where
one isn't sure of the formatting is one I've also had issues with and
could do with some attention - for now hCard is only going to be
useful in applications
[EMAIL PROTECTED] wrote:
Jeremy wrote:
The simplest solution is to simply expand the pattern to allow the
same usage of class and title on elements other than abbr (span is
specifically mentioned but this would potentially apply to any
element). . I'd be interested in hearing other
Webadmin - Tenbus wrote:
Mike Kaply wrote:
Both upcoming and eventful do not have dashes in their dates.
They will need to be evangelized.
Mike
Wikevent.org's got it right
http://wikevent.org/en/Joan_Armatrading_2007_5_7 we don't need
evangelising ;-)
Spike
Ditto for Revish -
Hello Mike,
Is this going to be replacing XUL, XBL, etc etc?
See ya
On 4/27/07, Mike Kaply [EMAIL PROTECTED] wrote:
If anyone is interested in helping define the user interface for
microformat in Firefox 3 and Operator, we're trying to have a
discussion at:
Dr. Ernie Prabhakar wrote:
title=2007-03-12T17:00:00
Can you confirm that:
a) This will in fact solve the screen reader problem
It will not. Though I agree with Jeremy and Tantek that this solution
is slightly better than the current recommendation. It is still far
from accessible.
Dan Champion wrote:
Webadmin - Tenbus wrote:
Mike Kaply wrote:
Both upcoming and eventful do not have dashes in their dates.
They will need to be evangelized.
Wikevent.org's got it right http://wikevent.org/en/
Joan_Armatrading_2007_5_7 we don't need evangelising ;-)
Ditto for Revish -
In message [EMAIL PROTECTED], James Craig
[EMAIL PROTECTED] writes
You guys are missing the point. Do you talk that way?
Is anyone gonna be in thirty point three. Dash ninety-seven point
seventy-five anytime soon? I should be there at two thousand seven six
nine tee fifteen thirty zero zero
Bringing, for discussion, a proposal from the WaSP ATF co-lead in
response to today's article.
http://www.webstandards.org/2007/04/27/haccessibility/#comment-57820
Patrick Lauke wrote:
so, looking at some “harmonisation” ideas then, what i would
suggest a way forward may be:
1) heavily
32 matches
Mail list logo
