One problem with this idea is the difficulty of parsing. (I know that
as per microformats principles, the needs of implementors come third,
after the needs of users and the needs of publishers - but the needs
of implementors do still need to be taken into account!) It would
mean that all microformats tools would have to include a full CSS-
parsing ability. Otherwise they might pick up false positives from
things like:
<span style="background:url("http://example.com/-uf-
content:'2008'")"
(Yes, this is a contrived example!) And you may end up in a situation
where publishers start using the following and expecting it to work:
<style type="text/css">
#event1 .dtstart { -uf-content: '2008-01-01' }
</style>
Then you end up with parsers needing to follow all rel=stylesheet
links, @import rules, etc.
--
Toby A Inkster
<mailto:[EMAIL PROTECTED]>
<http://tobyinkster.co.uk>
_______________________________________________
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
