Elegant. On Sat, Nov 22, 2008 at 9:44 AM, André Luís <[EMAIL PROTECTED]> wrote: > 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 amount of information (fn, url, country...) but, if on your > website you have a social network, you can reveal more data to your > friends. ie, if one of your friends is logged in and visits your > profile, your data is far more detailed: (fn, email, full address, > date of birth, etc). > > Or you can use a whitelist of openids that can access your full details. > > The point is... microformats allow you to represent data in > recognizable fashion. How you decide how many information to publish, > is out of the scope of microformats. > > At least, this is how I see it and how it's been discussed here > before. Please, correct me, anyone, if I'm wrong. > > Cheers, > André Luís > > On Sat, Nov 22, 2008 at 2:13 PM, Samuel Richter <[EMAIL PROTECTED]> 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. Has there been >> any discussion of this? >> _______________________________________________ >> microformats-discuss mailing list >> [email protected] >> http://microformats.org/mailman/listinfo/microformats-discuss >> > > _______________________________________________ > microformats-discuss mailing list > [email protected] > http://microformats.org/mailman/listinfo/microformats-discuss >
_______________________________________________ microformats-discuss mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-discuss
