Derrick Lyndon Pallas wrote:
Wow! I didn't expect to hear about mfo again until September. Maybe its
time has come! A real-world parser: ~D
I hadn't heard of mfo, but the use case,
"E.g. you might put a <span class="vcard mfo"> deep inside a <span
class="vevent">, and not want the categories/tags of the hCard
accidentally parsed into the hCalendar event."
...is pretty well motivated from an RDFy/SemWeb perspective, since we're
all about mixing vocabs. The mfo sketch suggests progress towards having
it be clearer which entity some properties are being attached to,
without each parser needing hardcoded knowledge of each and every
vocabulary. Cool stuff!
cheers,
dan
Scott Reynen wrote:
This is why we need mfo [1]. What typically happens when we see a
problem like this is we use sub-optimal markup to avoid the problem
before it actually occurs in real-world publishing. I think this is a
mistake. Instead, I suggest we use markup that makes sense, and
address this kind of parsing problem if/when it actually comes up in
practice, e.g. by applying mfo in parsers.
[1] http://microformats.org/wiki/mfo
_______________________________________________
microformats-new mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-new
_______________________________________________
microformats-new mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-new
