[uf-discuss] xdmp profiles not enough for parsing?

brian suda brian.suda at gmail.com
Wed Nov 16 07:44:40 PST 2005

Phil Dawes wrote:

> Hi Microformats list,
> When coding up my python microformats parser, one of the problems I
> encountered was getting the parser to interpret the structure
> correctly (see [1]). In order to overcome this my parser currently
> hardcodes the elements that can have sub-elements in an internal data
> structure.
> (e.g. for hCard: 'adr', 'geo' and 'n' can have subelements).
> I've just noticed that xdmp profiles don't carry this information, and
> was wondering if this scuppers the general idea of parsing
> microformats from their profiles?
> (or am I missing something)

XMDP doesn't do alot of things, it doesn't do any sort of Typing either.
In hCard DTSTART is an ISO date. That is something that is NOT encoded
in XMDP as something that is machine readable.

This leads back to a discussion a few weeks ago about a universal, or
general Microformat parser. The general consensus was that it would be
very difficult because of many of these restrictions.


More information about the microformats-discuss mailing list