[uf-discuss] Google Code microformat?

2008-11-22 Thread Samuel Richter
Please excuse me if this is not the appropriate mailing list or if this has already been discussed (the archives have no search feature.) It seems that Google Code is using some sort of microformat in their project feeds. I happened to look at the Atom source for a given project's update feed

[uf-discuss] Google Code microformat?

2008-11-22 Thread Toby A Inkster
If you're talking about their use of class=ot-logmessage etc, then no, that isn't a Microformat[1]. It looks to me like the reason those particular classes are present in the project updates Atom feed is that the feed is generated by the same code that generates the project updates HTML

[uf-discuss] hCard slowing adoption of microformats?

2008-11-22 Thread Samuel Richter
I read some blog posts this morning on microformats and a common concern (and I feel a legitimate one) is the scraping of hCard's from web sites for future generations of spammers. I believe that fear, if left unaddressed, will kill the microformat effort. Has there been any discussion of this?

Re: [uf-discuss] rel=byme

2008-11-22 Thread Martin McEvoy
Martin Atkins wrote: Martin McEvoy wrote: On your homepage: a rev=made href=http://somesite.com/;Some Website/a [snip] The last thing I may add to all that is @rev is depreciated in Microformats and HTML5, but if you mark up your pages in XHTML or HTML4 you are still good to go Per

Re: [uf-discuss] Google Code microformat?

2008-11-22 Thread Samuel Richter
It seems to me that both hAtom and hDOAP present limitations of a sort when it comes to providing feeds for software updates. On the one hand with hAtom, you have a generic microformat with no way of identifying any content beyond it merely being feed content and with hDOAP, you have no mechanism

Re: [uf-discuss] hCard slowing adoption of microformats?

2008-11-22 Thread André Luís
Samuel, Yes, it's a recurring concern, however, microformats don't deal with authorization. That's stuff for other protocols (openid, oauth). What they do is markup existing data, stuff that you're already publishing. Now, you can establish a scenario where public hcards only markup a small

Re: [uf-discuss] Google Code microformat?

2008-11-22 Thread David Janes
On Sat, Nov 22, 2008 at 9:09 AM, Samuel Richter [EMAIL PROTECTED] wrote: It seems to me that both hAtom and hDOAP present limitations of a sort when it comes to providing feeds for software updates. On the one hand with hAtom, you have a generic microformat with no way of identifying any

Re: [uf-discuss] hCard slowing adoption of microformats?

2008-11-22 Thread Martin McEvoy
Hello Samuel Samuel Richter wrote: I read some blog posts this morning on microformats and a common concern (and I feel a legitimate one) is the scraping of hCard's from web sites for future generations of spammers. I believe that fear, if left unaddressed, will kill the microformat effort.

Re: [uf-discuss] hCard slowing adoption of microformats?

2008-11-22 Thread Martin McEvoy
Martin McEvoy wrote: Hello Samuel Samuel Richter wrote: I read some blog posts this morning on microformats and a common concern (and I feel a legitimate one) is the scraping of hCard's from web sites for future generations of spammers. I believe that fear, if left unaddressed, will kill the

Re: [uf-discuss] Google Code microformat?

2008-11-22 Thread Scott Reynen
On [Nov 22], at [ Nov 22] 7:09 , Samuel Richter wrote: It seems to me that both hAtom and hDOAP present limitations of a sort when it comes to providing feeds for software updates. On the one hand with hAtom, you have a generic microformat with no way of identifying any content beyond it