Just a thought, prompted by this Russell Beattie post -
http://www.russellbeattie.com/notebook/1008914.html
I don't think (m)any of the the blog engines offer styling that will
work well on mobile devices. Could be a good inroad for hAtom: use
this profile, get handheld support for free (via Zen
Thanks for all of your comments.
My current take is this:
- I will be continuing to develop this format using suggested route.
- I will be following this group and contributing if approriate (I
think microformats is a good solution to a real problem).
- I will ask this group periodically for
I think this is yet another issue tied to a Citation microformat.
When you are adding an image or description of a work of art on a web
site, you are more often than not citing an actual document hanging
in a museum somewhere else in the world. This shares everything with
a citation
On 3/23/06, Brian Suda [EMAIL PROTECTED] wrote:
In the same vein as classification of plants, we might want to explore
making a simple microformat that mimics the classification system of
the taxonomy of organizims. Kingdom-Phylum-...Family-Species. That
way additional microformats (such as
Hi all,
While reading yet another design tutorial for Web 2.0 sties:
http://snyke.net/blog/2006/03/25/site-design-using-prototype/
I ran across the Behaviour JavaScript library:
http://bennolan.com/behaviour/
Using CSS selectors to apply JavaScript behaviors
I'm not sure I understand it
Anyone seen this?
MicroID is a new Identity layer to the web and Microformats that
allows anyone to simply claim verifiable ownership over their own
pages and content hosted anywhere. The technology is radically simple
and capable of empowering new and unique meta services with only minor
effort.
Perhaps Danny can shed some light on his proposal?
On 3/27/06, Chris Casciano [EMAIL PROTECTED] wrote:
On Mar 27, 2006, at 3:39 PM, Chris Messina wrote:
On 3/27/06, Chris Casciano [EMAIL PROTECTED] wrote:
I guess I'm not clear where microformats (including hAtom or not)
would
serve
IN RFC 2426 (vCard) it saws in the overview:
The [MIME-DIR (RFC 2425)] document defines a MIME Content-Type for holding
different kinds of directory information. The directory information
can be based on any of a number of directory schemas. This document
defines a [MIME-DIR (RFC 2425)]
On 3/27/06, David Weekly [EMAIL PROTECTED] wrote:
Take: We're meeting at Gordon Biersch at 10:30 tomorrow - be there!
Change to: We're meeting at
[Event: Gordon Biersch at 10:30 tomorrow] - be there!
Well, we'd have to rewrite tomorrow to a date when the original
submitter posted.
This is an interesting idea. Here are the key elements to Russell
Beattie's proposal (I think) as it relates to hAtom:
I have to say I’m getting more and more convinced that this is the
direction that the mobile web is going to go. No recoding markup, no
“separate and always unequal” access
Boy, once Doc gets a hold of something... I was going to send out a
little note here asking for some feedback, but it's gone full circle
already :)
Anyway, MicroID isn't exactly a microformat all by itself but it can
be expressed in conjunction with one. It's really just an opaque but
I must be missing something obvious, because it seems apparant to me
that this doesn't buy you anything. You take a person's email and
website, and generate a long hex number based on the two. This
identifies them uniquely, sure--but anybody who knows your email
address can generate the exact
On Mar 27, 2006, at 3:40 PM, jer wrote:
Boy, once Doc gets a hold of something... I was going to send out a
little note here asking for some feedback, but it's gone full circle
already :)
Anyway, MicroID isn't exactly a microformat all by itself but it can
be expressed in conjunction with
Yep, I tend to agree with Holly. It seems that the process for verifying
your identity is identical to the process of creating an identical
forgery.
Also, I've mentioned this before regarding i-tags, using the class attribute
to store information seems like a bad idea in general and violates a
On Mar 27, 2006, at 7:46 PM, Chris Messina wrote:
Another example of using hAtom could come from the devices
themselves... Imagine using a service proxy between the website you
want and your handheld:
originating website -- proxy -- handheld
While you could use RSS for this, hell, why not
Yep, I tend to agree with Holly. It seems that the process for
verifying
your identity is identical to the process of creating an identical
forgery.
What I need to learn how to say better (and put in a FAQ) is
something like MicroIDs are not to be validated until a user makes a
claim and
As your model is spoofable if I know your email, I'm not sure what
this gains for you over showing the ID or email directly in the
moderated system.
So that you don't *have* to be public, so the identifier can be
private if you want it to, so that your account on that other system
isn't
17 matches
Mail list logo
