Comments on Eduardo Jezierski: SMS Applications and Microformats - lots of work t...

oops, I made the same mistake again .. should have...

2008-04-23T22:33:27.822-07:00

oops, I made the same mistake again .. should have said "I was talking only about nanoformats here"

Thanks Ade! I like the approach and we'd have to t...

2008-04-21T15:44:49.285-07:00

Thanks Ade! I like the approach and we'd have to try it out. One challenge is the training required and the statelessness of people under stress. Worth experimenting...

Mikel - I realized but since I heard this issue twice in the context of discussions about SMS apps I thought it would be good to raise that dialog. Agree that we could have more pervasive use of microformats on HTML (and KML) views as long as it doesn't make the UI look like a telegram!

Thanks Eduardo, great contribution -- simple keyst...

2008-04-21T15:38:10.642-07:00

Thanks Eduardo, great contribution -- simple keystroke count is the crucial factor here, and nanoformats have so far not taken that into account.

And just a minor clarification -- I was talking only about microformats here; microformats are simple standards for including machine readable data to HTML.

A couple of interesting optimizations spring to mi...

2008-04-21T15:12:21.310-07:00

A couple of interesting optimizations spring to mind:

Context-specific funneling - How about allowing users to use only the decimal and do some smart interpretation of subsequent locations based on likely/possible velocities and or terrain. First message is:

L:121.234, 12.234

Then:
L:678,124 => L:121.678, 12.124

And:
L:678,987 => L:121.678, 11.987

Cuts down on the number of key strokes quite a bit.

This would also potentially reduce the number of mis-typed locations by eliminating or flagging impossible position deltas. For example; a new location that implies you moved 400mi in half an hour.