Re: [uf-discuss] Re: Possible alternative methods for include
On Fri, 2008-02-08 at 15:21 +, Martin McEvoy wrote: eg: we could use class data as a container for what we want to include. span class=vcard span class=data span class=fnFoo/span /span a class=email href=mailto:[EMAIL PROTECTED]email [EMAIL PROTECTED]/a /span The above example was not very clear was it?, so a proposal can be found here: http://microformats.org/wiki/include-pattern-strawman#Use_a_Class_Create_method Thanks Martin McEvoy ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
[uf-discuss] microformats and privacy
What is the response to the privacy argument? As a carefree technophile I'm happy publishing personal info on the web. But when you're trying to convince a major social network to add semantics that makes their users personal information easier to harvest and possibly abuse. Is there any answer? http://www.flickr.com/groups/flickrideas/discuss/72157603869809336/ ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] A further possible solution to the abbr accessibility issue
On 2/8/08, Andy Mabbett [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], Andy Mabbett [EMAIL PROTECTED] writes Early in December, I made the following suggestion, but in a separate, and unclearly-titled thread. I'm reposting it here, in a new thread, in the hope that it will warrant discussion: [prefix changed to data] span class=dtstart title=data:20070912T16:03:00+01:00 4.03pm /span A further advantage of this method has just occurred to me; it could use plain-language *and* machine values in one title, thus: span class=dtstart title=we start at three minutes past four - data: 2007-09-12T16:03:00+01:00 4.03pm /span and we could even exempt parentheses: span class=dtstart title=we start at three minutes past 4 (data: 2007-09-12T16:03:00+01:00) 4.03pm /span -- Andy Mabbett I wonder if this will be heavy for the parsers when both plain-language *and* machine values are mixed i.e., knowing the scope of the regex to differentiate between the two. -Sarven ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] microformats and privacy
Obviously doesn't publish any information to the web that you want private. For example facebook asks you for your phone number... so it can show it to others... but you don't have to give it that info! Microformats will help expose the information you are willing to put out there. (If you want something private... then don't give it out.) -- Charles Iliya Krempeaux, B.Sc. http://ChangeLog.ca/ Motorsport Videos http://TireBiterZ.com/ Vlog Razor... Vlogging News... http://vlograzor.com/ On Feb 9, 2008 10:22 AM, Thom Shannon [EMAIL PROTECTED] wrote: What is the response to the privacy argument? As a carefree technophile I'm happy publishing personal info on the web. But when you're trying to convince a major social network to add semantics that makes their users personal information easier to harvest and possibly abuse. Is there any answer? http://www.flickr.com/groups/flickrideas/discuss/72157603869809336/ ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
[uf-discuss] hKit and include-pattern scope
Isn't the importation of data from external resources using hKit face similar issues as in include-pattern? re: http://microformats.org/wiki?title=include-pattern-faqdiff=0oldid=25623 -Sarven ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] microformats and privacy
Thom Shannon wrote: What is the response to the privacy argument? As a carefree technophile I'm happy publishing personal info on the web. But when you're trying to convince a major social network to add semantics that makes their users personal information easier to harvest and possibly abuse. Is there any answer? Thom, Last year, I brought up the idea of something I named hprivacy and presented a very primitive hprivacy html proxy filter prototype with three groups: pro, family, friends and public. See http://microformats.org/discuss/mail/microformats-discuss/2007-April/009264.html This is a tiny prototype that is not integrated with a tagged social graph, so for now, I simulate the filtering by passing the group in the URL. But you'll get the idea. Some links have moved: http://lebleu.org/projects/hprivacy/index.php (what the public sees) http://lebleu.org/projects/hprivacy/index.php?group=family (what a family member would see) http://lebleu.org/projects/hprivacy/index.php?group=friends http://lebleu.org/projects/hprivacy/index.php?group=pro See the markup: http://lebleu.org/projects/hprivacy/hcard.html (obviously, in real implementation, this would be pulled from a non-public folder) There didn't seem to be much interest on this list. Maybe because it's not so much about data formats and/or because it's about marking up content that is not public to anyone (microformats seems to have a bias toward public content). Let me know what you think. Also, someone helped me design a cool logo: http://hprivacy.org Guillaume ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
[uf-discuss] A further possible solution to the abbr accessibility issue
In message [EMAIL PROTECTED], Sarven Capadisli [EMAIL PROTECTED] writes A further advantage of this method has just occurred to me; it could use plain-language *and* machine values in one title, thus: span class=dtstart title=we start at three minutes past four - data: 2007-09-12T16:03:00+01:00 4.03pm /span and we could even exempt parentheses: span class=dtstart title=we start at three minutes past 4 (data: 2007-09-12T16:03:00+01:00) 4.03pm /span I wonder if this will be heavy for the parsers when both plain-language *and* machine values are mixed i.e., knowing the scope of the regex to differentiate between the two. 'Everything after data: excluding leading white space and a trailing close-parenthesis, if any' shouldn't be to difficult to code. -- Andy Mabbett ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
