Parsing microformats

Update: This code is now contained in Microformats.js.

One of the things I’ve run into with Operator is learning how to parse microformats correctly. Instead of keeping the knowledge I’ve found to myself, I’ve decided to work with Andy Mitchell and create a generic cross browser microformat parser in JavaScript, tentatively called ufParser. That’s the reason I’ve been so quiet.

The parser allows for the creation of definition files for microformats, so that new microformats can be added to the parser easily. So far I have all of the Operator microformats done (hCard, hCalendar, hReview, hResume, geo, xFolk, rel-tag) and I have done XFN.

We’re also investigating the potential to create more generic actions as well (but I’ll maintain compatibility with old style Operator actions).

The next version of Operator will definitely use the new parser, so there might be some regressions here and there. Hopefully we’ll get them solved quickly

Stay tuned. I’m hoping to have something in the next week or so.

Please note: I reserve the right to delete comments that are offensive or off-topic.

Leave a Reply

Your email address will not be published. Required fields are marked *

14 thoughts on “Parsing microformats

  1. ufParser sounds really great.. Operator is sounding more and more like something that should go into firefox 3.. keep up the great work

  2. Seems like this concept has a lot of potential, once people know to put microformats in their web pages.

    Question: Export Contact tries to export to Outlook, which I don’t have installed. Is there a way to make it export to Mozilla Thunderbird?

  3. Mike, really a great tool. I’m thinking about integrating Microformats into the OpenLaszlo project. A Microformat parser running inside OpenLaszlo and exporting Microformats while a Flash movie or DHTML/AJAX app is running into the DOM.

    I’ve two questions on that:

    1) How does Operator register changes in the DOM tree structure? Would I need to explicitly signal Operator that there are new Microformats to pick up, if I generate them after the first parsing of the DOM?

    2) Do you have any idea under what license the ufparser is going to be published? Any chance that the piece will be open source?

    Thanks, keep up the excellent work.


  4. Craig:

    It sounds like your system is configured to use outlook by default for vCards.

    Bring up any folder (like My Documents) and select Tools->Folder Options.

    Click on File Types.

    Scroll down in Registered File Types and select VCF. Then select Change to change it to Thunderbird.

    I’ll be changing this in the next release to bring up the traditional Open/Save As dialog vs sending it directly to the OS, so this change will be easier (determined by the browser)

  5. Raju:

    1) You would need to signal Operator to pick up the new microformats and right now there is no way to do that. I’ll put that on my list for the next release. It will probably be an event you produce that operator picks up.

    2) ufParser will be open source. Not sure of license right now. Operator is trilicensed, but ufParser might be something different depending on my lawyers.


  6. Roger:

    class and status are both parsed in the next version (what services they will be passed to is a different story)

    I’m aware of the recurring issue and I am working on it.