Re: [uf-discuss] Optimus — microformats parser
In message [EMAIL PROTECTED], Dmitry Baranovskiy [EMAIL PROTECTED] writes I wrote f parser Whatever character you have before that f isn't 7-bit Usenet compliant. -- Andy Mabbett ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Optimus — microformats parser
On 9/20/07, Andy Mabbett [EMAIL PROTECTED] wrote: Whatever character you have before that f isn't 7-bit Usenet compliant. Is this list available on Usenet? -Ciaran McNulty ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Optimus microformats parser
The Greek letter mu, if I'm not mistaken :) Jim Original Message: - From: Thom Shannon [EMAIL PROTECTED] Date: Thu, 20 Sep 2007 11:25:38 +0100 To: microformats-discuss@microformats.org Subject: Re: [uf-discuss] Optimus microformats parser Whatever character you have before that f isn't 7-bit Usenet compliant. i'd imagine it was a micro symbol :) ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss mail2web.com Enhanced email for the mobile individual based on Microsoft® Exchange - http://link.mail2web.com/Personal/EnhancedEmail ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Optimus — microformats parser
On 20/09/2007, Ciaran McNulty [EMAIL PROTECTED] wrote: On 9/20/07, Andy Mabbett [EMAIL PROTECTED] wrote: Whatever character you have before that f isn't 7-bit Usenet compliant. Is this list available on Usenet? well, what you do is, you blast all possible 8 bit sequences through usenet, and the ones that come out alive... that's your list. ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Optimus — microformats parser
On 9/20/07, Philip Tellis [EMAIL PROTECTED] wrote: well, what you do is, you blast all possible 8 bit sequences through usenet, and the ones that come out alive... that's your list. Is this mailing list available on Usenet? -Ciaran McNulty ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: Re: [uf-discuss] Optimus — microformats parser
In message [EMAIL PROTECTED], Ciaran McNulty [EMAIL PROTECTED] writes On 9/20/07, Andy Mabbett [EMAIL PROTECTED] wrote: Whatever character you have before that f isn't 7-bit Usenet compliant. Is this list available on Usenet? Ack, of course not - I have it configured as a pseudo-newsgroup in my combined news mail client. Sorry. Nonetheless, the character is not rendering properly, here, at least - though it does render properly at: http://microformats.org/discuss/mail/microformats-discuss/2007-September/010710.html -- Andy Mabbett ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
RE: [uf-discuss] Optimus - microformats parser
Is that a bug? The parsing rules at http://microformats.org/wiki/hcard-parsing seem pretty unambiguous: For all properties, when the element for a property is: * abbr title: use the value of the 'title' attribute. If there is no 'title' attribute then use the contents of the element. So am I right in understanding that a parser should always ignore the contents of abbr? In which case, do the parsing rules need revisiting? Jim Original Message: - From: Andy Mabbett [EMAIL PROTECTED] Date: Thu, 20 Sep 2007 13:16:26 +0100 To: microformats-discuss@microformats.org Subject: [uf-discuss] Optimus - microformats parser I've found a bug :-( For: http://www.westmidlandbirdclub.com/birmingham/indoor.htm Optimus is rendering the postal code in: span class=postal-code abbr class=geo title=52.4703;-1.9239 B15 3AF /abbr /span as: postal-code52.4703;-1.9239/postal-code and likewise where that postal code is part of an hCalendar's location. -- Andy Mabbett ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss myhosting.com - Premium Microsoft® Windows® and Linux web and application hosting - http://link.myhosting.com/myhosting ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Optimus - microformats parser
On 20/09/2007, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: So am I right in understanding that a parser should always ignore the contents of abbr? In which case, do the parsing rules need revisiting? except that in this case, the postal-code element is not abbr, but span, and it has no title. ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Optimus microformats parser
On 9/20/07 4:47 AM, Andy Mabbett [EMAIL PROTECTED] wrote: Ack, of course not - I have it configured as a pseudo-newsgroup in my combined news mail client. Sorry. Nonetheless, the character is not rendering properly, here, at least - though it does render properly at: http://microformats.org/discuss/mail/microformats-discuss/2007-September/0107 10.html Consider checking the UTF-8 compliance of your combined news mail client, as Dmitry Baranovskiy's message headers properly stated: Content-Type: text/plain; charset=UTF-8 And then simply included the UTF-8 mu (or micro symbol) character inline in the message. Thanks, Tantek P.S. Well done Dmitry Baranovskiy! I'm still playing with Optimus a bunch more before following up with specific feedback. ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Optimus — microformats parser
Hi Dmitry On 9/19/07, Dmitry Baranovskiy [EMAIL PROTECTED] wrote: Hello everyone, Inspired by Brian's X2V[1] and Drew's presentation Can Your Website be Your API?[2] I wrote µf parser that transforms any microformatted web page to XML or JSON. It could be used as an API to any web site with microformats. I hope now we could see some µf based mashups. Brilliant. I started along a similar road [1] but didn't cover nearly as much ground, more just a proof of concept. I'll definately be having a play soon. I note you've made all the XML/XSL files available for download. Under what licence are these available? I'd love to be able to use them in commercial projects if it comes to that. Gareth [1] http://morethanseven.net/posts/working-example-of-microformats-as-an-api/ Characteristics at glance: Supported formats: hCalendar, hCard, hAtom, hResume, hReview, xFolkentry, adr, geo, xfn, votelinks, rel-nofollow, rel-tag, rel-license Output formats: XML, JSON, JSON-P URL:http://microformatique.com/optimus/ Query parameters: uri — URI of the resource format — output format (xml or json, default is xml) [optional] function — name of call back function for JSON [optional] filter — space separated names of microformats (default is vevent vcard hfeed hresume hreview xfolkentry adr geo xfn votelinks rel-nofollow rel-tag rel-license) [optional] Examples: http://microformatique.com/optimus/?uri=http://ma.gnolia.com/people/drewm/tags/microformats http://microformatique.com/optimus/?uri=http://corkd.com/wine/view/1122format=json http://microformatique.com/optimus/?uri=http://johnfallsopp.comformat=jsonfunction=Back I happy to hear any feedback, good (on-list) or bad (off-list) :) 1. http://suda.co.uk/projects/X2V/ 2. http://allinthehead.com/retro/301/can-your-website-be-your-api -- Best regards, Dmitry Baranovskiy http://dmitry.baranovskiy.com ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss -- Gareth Rushgrove garethrushgrove.com morethanseven.net refreshnewcastle.org ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Optimus — microformats parser
On 9/18/07, Dmitry Baranovskiy [EMAIL PROTECTED] wrote: Hello everyone, Inspired by Brian's X2V[1] and Drew's presentation Can Your Website be Your API?[2] I wrote µf parser that transforms any microformatted web page to XML or JSON. It could be used as an API to any web site with microformats. I hope now we could see some µf based mashups. Characteristics at glance: Supported formats: hCalendar, hCard, hAtom, hResume, hReview, xFolkentry, adr, geo, xfn, votelinks, rel-nofollow, rel-tag, rel-license Output formats: XML, JSON, JSON-P URL:http://microformatique.com/optimus/ Query parameters: uri — URI of the resource format — output format (xml or json, default is xml) [optional] function — name of call back function for JSON [optional] filter — space separated names of microformats (default is vevent vcard hfeed hresume hreview xfolkentry adr geo xfn votelinks rel-nofollow rel-tag rel-license) [optional] Examples: Wow, this looks great. Now I now what I'll be doing on lunch break :) :DG ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
Re: [uf-discuss] Optimus — microformats parser
I think I speak for all when I say: friggin' awesome work!! Thanks for showing off the xml and xsl as well. Great things will come out of this, I'm sure. One thing though.. while testing this url: http://andr3.net/blog/post/102 the rel-tag's didn't show up under /microformats/rel-tag. Only under /microformats/xfolkentry/tag. Is this the expected behavior? I don't even know if I'm using xfolk correctly, because it's not literally a list of my bookmarks, but a list of bookmarkable entries... but it raised a doubt that has been discussed in the past. Shouldn't the tags show up BOTH under the xfolkentry and also as rel-tag? If someone has reached a final decision on this, I'd be thankful if someone could point me to it and sorry. Cheers, André Luís On 9/19/07, Dimitri Glazkov [EMAIL PROTECTED] wrote: On 9/18/07, Dmitry Baranovskiy [EMAIL PROTECTED] wrote: Hello everyone, Inspired by Brian's X2V[1] and Drew's presentation Can Your Website be Your API?[2] I wrote µf parser that transforms any microformatted web page to XML or JSON. It could be used as an API to any web site with microformats. I hope now we could see some µf based mashups. Characteristics at glance: Supported formats: hCalendar, hCard, hAtom, hResume, hReview, xFolkentry, adr, geo, xfn, votelinks, rel-nofollow, rel-tag, rel-license Output formats: XML, JSON, JSON-P URL:http://microformatique.com/optimus/ Query parameters: uri — URI of the resource format — output format (xml or json, default is xml) [optional] function — name of call back function for JSON [optional] filter — space separated names of microformats (default is vevent vcard hfeed hresume hreview xfolkentry adr geo xfn votelinks rel-nofollow rel-tag rel-license) [optional] Examples: Wow, this looks great. Now I now what I'll be doing on lunch break :) :DG ___ 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] Optimus — microformats parser
Thanks everyone for warm words. Your positive feedback is the best donation you could make to the developer. :) André: It was a bug with elemental µfs. I fixed it. Gareth: There is rel-licence µf on the page :) Just at the bottom. But beware: it is only gamma version. :) I am still waiting for feedback of elders. -- Best regards, Dmitry Baranovskiy http://dmitry.baranovskiy.com ___ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
