Re: [uf-discuss] Fwd: Twitter Is Now Even More Geeky

[Ben Buchanan]

> And for the really geeky, we have a surprise: Twitter now fully
> supports microformats. Now that is pretty geektastic.
How 'bout that!  But what does that mean?


Hmm, well it looks like all the are now hCards and the streams are
hAtom. Nothing else is jumping out from a quick glance - can anyone
spot anything more?

--
--- 
--- The future has arrived; it's just not
--- evenly distributed. - William Gibson
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

Re: [uf-discuss] a[name] as machine data?

[James Craig]

Ryan King wrote:


a[name has restrictions that input[name] does not have.


...snip...


1. http://www.w3.org/TR/html401/struct/links.html#h-12.2.1


Note and removed. Thanks!
http://microformats.org/wiki/assistive-technology-abbr- 
results#Markup_Possibilities


James

___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

[uf-discuss] Fwd: Twitter Is Now Even More Geeky

[Ernest Prabhakar]

How 'bout that!  But what does that mean?

Begin forwarded message:


And for the really geeky, we have a surprise: Twitter now fully
supports microformats. Now that is pretty geektastic.

Happy Twittering!
-Biz Stone and the Twitter Team
http://twitter.com/biz


___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

Re: [uf-discuss] a[name] as machine data?

[Ryan King]

On May 10, 2007, at 4:45 PM, James Craig wrote:


Ryan King wrote:


James Craig wrote:

Haven't thought too much about this, but are there any obvious  
gotchas to using an anchor element with name attribute as a  
potential replacement for the abbr-design-pattern?


I believe a[name] and @id need to be unique across an entire page.  
This would make it impossible to have two events with the the same  
dtstart, dtend or dtstamp on the same page. I think that makes it  
unworkable.


Only ID has that restriction. Radio buttons, for example, require  
elements have unique IDs but the same NAME.


a[name has restrictions that input[name] does not have.

Per [1], @id's and a[name] are collectively known as "anchor names"  
and must be unique, as they share the same name space. A relevant  
snippet:


The id and name attributes share the same name space. This means  
that they cannot both define an anchor with the same name in the  
same document. It is permissible to use both attributes to specify  
an element's unique identifier for the following elements: A,  
APPLET, FORM, FRAME, IFRAME, IMG, and MAP. When both attributes are  
used on a single element, their values must be identical.


-ryan

1. http://www.w3.org/TR/html401/struct/links.html#h-12.2.1
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

Re: [uf-discuss] a[name] as machine data?

[James Craig]

Ryan King wrote:


James Craig wrote:

Haven't thought too much about this, but are there any obvious  
gotchas to using an anchor element with name attribute as a  
potential replacement for the abbr-design-pattern?


I believe a[name] and @id need to be unique across an entire page.  
This would make it impossible to have two events with the the same  
dtstart, dtend or dtstamp on the same page. I think that makes it  
unworkable.


Only ID has that restriction. Radio buttons, for example, require  
elements have unique IDs but the same NAME.


James

___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

Re: [uf-discuss] a[name] as machine data?

[Ryan King]

On May 10, 2007, at 3:23 PM, James Craig wrote:


Just a thought:

Haven't thought too much about this, but are there any obvious  
gotchas to using an anchor element with name attribute as a  
potential replacement for the abbr-design-pattern?


I believe a[name] and @id need to be unique across an entire page.  
This would make it impossible to have two events with the the same  
dtstart, dtend or dtstamp on the same page. I think that makes it  
unworkable.


-ryan


___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

[uf-discuss] GRDDL (Microformats->Semantic Web) call for comments

[Harry Halpin]

Hey everyone,

Has anyone here heard of GRDDL? It's a simple method of converting
microformats to RDF, the basic data format of the Semantic Web, and then
one can use the Semantic Web toolset to do some interesting things like
merge microformat-based data from different sources and then query the
"mashed-up" microformat data.  GRDDL allows one to link a transformation
to RDF (either from the document directly or the profile URI) to some
micro-format enabled data. The technique also works with plain-vanilla
XML documents. I think with GRDDL, we get both additional value from
microformats and the Semantic Web.

I'm the chair of the W3C GRDDL WG, and I want for people who are
active in the microformat community to give us comments on our
specification. We would highly value your comments on any of the
following docs:

1) GRDDL specification, which is for implementers and power-users, and
as such is formally written.
This document is a Candidate Recommendation, so we'd like comments
within the month:

http://www.w3.org/2004/01/rdxh/spec

2) GRDDL Primer, which is for end-users and is supposed to be
easy-to-read and informal:

http://www.w3.org/2001/sw/grddl-wg/doc29/primer.html

3) The specification has test-cases and a test-harness (we have
implementations in Python, C, and Java), a Last Call Working Draft:

http://www.w3.org/2001/sw/grddl-wg/td/grddl-tests

4) Use-case scenarios:

http://www.w3.org/2001/sw/grddl-wg/doc43/scenario-gallery.htm

  thanks!

-- 
-harry

Harry Halpin,  University of Edinburgh 
http://www.ibiblio.org/hhalpin 6B522426

___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

[uf-discuss] a[name] as machine data?

[James Craig]

Just a thought:

Haven't thought too much about this, but are there any obvious  
gotchas to using an anchor element with name attribute as a potential  
replacement for the abbr-design-pattern? The only things I can  
foresee are the plus sign (+) in pre-UTC time zones and the semicolon  
(;) in GEO. Those could both be escaped though, perhaps as  
underscores. It wouldn't leave as much room for growth as a full  
CDATA attribute, but may be able to


July 13th
Austin

http://www.w3.org/TR/html4/types.html#type-cdata
...NAME tokens must begin with a letter ([A-Za-z]) and may be  
followed by any number of letters, digits ([0-9]), hyphens ("-"),  
underscores ("_"), colons (":"), and periods (".").


Anyway, kick it back here if there is something obvious I'm missing.  
I'm certainly not proposing it as the best solution yet, but I have  
added it to the wiki and don't want to waste time with an AT test  
case if I don't have to.


http://microformats.org/wiki/assistive-technology-abbr- 
results#Markup_Possibilities


Cheers,
James

___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

Re: [uf-discuss] User Interface for Firefox/Operator

[Scott Reynen]

On May 10, 2007, at 2:46 PM, Mike Kaply wrote:


If someone creates a web page that takes hcalendars and generates a
timeline, I'll be more than happy to write an action for it...


This appears to do that:

http://suda.co.uk/projects/microformats/hcalendar/

Peace,
Scott

___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

Re: [uf-discuss] User Interface for Firefox/Operator

[Mike Kaply]

If someone creates a web page that takes hcalendars and generates a
timeline, I'll be more than happy to write an action for it...

On 5/10/07, Costello, Roger L. <[EMAIL PROTECTED]> wrote:


Hey Mike,

I'd like to add another item to my wish list for Operator:

Mashup a web page containing events (hCalendar) with the Timeline
widget[1].

[1] http://simile.mit.edu/timeline/

/Roger

-Original Message-
From: Costello, Roger L.
Sent: Tuesday, May 01, 2007 11:12 AM
To: Microformats Discuss
Subject: RE: [uf-discuss] User Interface for Firefox/Operator

Hey Mike,

Here's my "wish list" for Operator:

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 route of an airplane may have a geo Microformat
for each waypoint.  I would like to be able to view on Google Maps all
the waypoints simultaneously.

2. Suppose the geo Microformat is part of an hCard.  The "Find a Google
Map" currently only shows the lat/lon values on the Google Map.  It
would be nice if Operator would scoop up some of the other information
in the hCard, such as name and address, and display it on the Google
Map.

3. An XHTML document is an XML document.  Operator recognizes
Microformats in XHTML XML documents, but not other XML documents.  For
example, here is an XML document that has an embedded hCard:



Waldorf-Astoria

301 Park Ave.
New York
NY
10022



I would like to see Operator able to recognize Microformats in any XML
document, not just XHTML XML documents.

/Roger

___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss


___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

Re: [uf-discuss] uF Tools for Internet Explorer?

[Andy Mabbett]

In message
<[EMAIL PROTECTED]>, Brian
Suda <[EMAIL PROTECTED]> writes

>the microformats wiki has a list of existing bookmarklets

>http://microformats.org/wiki/bookmarklets

They would be better on a non-wiki page, formatted like those on:



so that they can be dragged to a browser's toolbar or folder.

-- 
Andy Mabbett
*  Say "NO!" to compulsory ID Cards:  
*  Free Our Data:  
*  Are you using Microformats, yet:  ?
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

RE: [uf-discuss] User Interface for Firefox/Operator

[Costello, Roger L.]

 
Hey Mike,

I'd like to add another item to my wish list for Operator:

Mashup a web page containing events (hCalendar) with the Timeline
widget[1].

[1] http://simile.mit.edu/timeline/

/Roger

-Original Message-
From: Costello, Roger L. 
Sent: Tuesday, May 01, 2007 11:12 AM
To: Microformats Discuss
Subject: RE: [uf-discuss] User Interface for Firefox/Operator

Hey Mike,

Here's my "wish list" for Operator:

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 route of an airplane may have a geo Microformat
for each waypoint.  I would like to be able to view on Google Maps all
the waypoints simultaneously.

2. Suppose the geo Microformat is part of an hCard.  The "Find a Google
Map" currently only shows the lat/lon values on the Google Map.  It
would be nice if Operator would scoop up some of the other information
in the hCard, such as name and address, and display it on the Google
Map.

3. An XHTML document is an XML document.  Operator recognizes
Microformats in XHTML XML documents, but not other XML documents.  For
example, here is an XML document that has an embedded hCard:



Waldorf-Astoria

301 Park Ave.
New York
NY
10022



I would like to see Operator able to recognize Microformats in any XML
document, not just XHTML XML documents.

/Roger

___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

Re: [uf-discuss] My experience creating an hcard 'me card'

[Brian Suda]

On 5/10/07, Keith Grennan <[EMAIL PROTECTED]> wrote:

However, if I gave someone a link to one of my blog entries, it would be
harder for them to know that this card was authoritative for that entry
- but I don't have as much of a problem with that.


--- this is where the rel="me" can help to consolidate identity.[1]


My only sticky point now is sharing my photo - the Technorati contacts
service doesn't fetch the hcard photo, and neither does my mac's Address
Book.app.  Fetching the photo and inlining it in the vcard, albeit to
compensate for the limitations of desktop apps, would be a nice feature
for an hcard-to-vcard service.


This is correct, this is a limitation of desktop apps they do not
derefference the URL to find the image. There is away around this by
using the DATA URI to encode, but there are drawbacks because IE7
doesn't support the DATA URI.[2]

I have been experimenting with the DATA URI and CSS on my own site:
http://suda.co.uk/contact/

the resulting hcard has the PHOTO base64 encoded
http://feeds.technorati.com/contact/http://suda.co.uk/contact

PHOTO;ENCODING=b;TYPE=png:iVBORw0KGgoNSUhEUgAAADIyCAM..

To hide the image from IE6/7 i am using the not() operator which is
not suported to show it to advanced browsers which also support the
DATA URI.

#gravatar img.photo { display:none }
#gravatar>img.photo:not([border]) { display:block }

I hope this helps.
-brian

[1] - http://www.gmpg.org/xfn/and/
[2] - http://microformats.org/wiki/hcard-parsing

--
brian suda
http://suda.co.uk
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss

[uf-discuss] My experience creating an hcard 'me card'

[Keith Grennan]

Hi,

I just added hcard to my homepage [1], with a link to convert it to
vcard uing the Technorati contacts service [2].

I did a little test and confirmed that the contacts service follows the
fragment identifier in the URL (#me)- which is awesome because even if I
have multiple hcards on the page, the contacts service will only decode
the 'me card', which is what I wanted.  Yay!

I also wanted to indicate somehow that this card is the authoritative
card for my homepage - the simplest way to do this was to make the url
component of the vcard equal to the homepage url (which is of course
what you'd expect).

After reading a previous related discussion [3], I played with using
rel=self to further indicate that this hcard is authoritative, but by
the definition of rel=self, this usage would only be correct if the url
also contained the fragment pointing to the hcard.  But if I make my
vcard url contain a fragment, then people clicking this link would be
partially scrolled down the page when arriving.  Really, rel=self
indicates more the canonical location of the hcard itself, rather than
the fact that it is authoritative for the page.

Given that, I think that having an hcard contain a url equal to the
homepage URL is good enough - if I just gave someone my homepage URL,
they could deduce which hcard on the page is authoritative for that URL,
because it contains a link to that URL.

However, if I gave someone a link to one of my blog entries, it would be
harder for them to know that this card was authoritative for that entry
- but I don't have as much of a problem with that.

Just thought that I would share this experience - I haven't seen
discussion around indicating that an hcard is authoritative for a
webpage via this simple method, so I thought people might find it
interesting.

My only sticky point now is sharing my photo - the Technorati contacts
service doesn't fetch the hcard photo, and neither does my mac's Address
Book.app.  Fetching the photo and inlining it in the vcard, albeit to
compensate for the limitations of desktop apps, would be a nice feature
for an hcard-to-vcard service.

Cheers,
Keith

[1] http://nearlyfree.org/blog/keith

[2] 
http://feeds.technorati.com/contacts/http%3A%2F%2Fnearlyfree.org%2Fblog%2Fkeith%23me

[3] http://microformats.org/wiki/hcard-issues#Canonical.2FAuthoritative_Hcard
___
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss