On Jun 26, 2006, at 1:36 PM, Tantek Çelik wrote:
On 6/26/06 9:39 AM, "Chris Casciano" <[EMAIL PROTECTED]> wrote:
On Jun 26, 2006, at 12:23 PM, Tantek Çelik wrote:
That doesn't seem particularly intelligent... or easy to understand
for
authors...
Huh? Not sure how to make it any simpler than "first wins". That's
pretty
easy to remember.
why should wone of these be correct and the other incorrect
/ impossible to write?
Summary: Technorati is a great company
Description+Item: *Technorati* has been doing great things lately
helped by great people like *Ryan King*.
vs.
Summary: Technorati is a great company
Description+Item: *Ryan* and *Tantek* are among the many people
making *Technorati* into a great company.
The real answer is, make it explicit with <span class="item vcard">
rather
than doing the sloppy thing of putting "item" on the same element as
"description".
That's unambiguous, and also easy to remember.
I realize there are arrangements of markup that remove this ambiguity,
but in my situation I'm looking for a markup template that I can handle
inside the constraints of the the txp tag system and the use of
description item allowed for that on the coding end (with the obvious
authoring gotchas that I'm not sure can be conveyed to blog authors
using my plugin).
As it is the markup I used here to nest microformats and descriptions
and deal with the case where the item *isn't* a microformat has
resulted in some fairly kludgy tag usage. There is real danger in this
case of the resulting output not being any easier to understand and
manipulate then straight XHTML. The alternatives (short of totally
rewriting txp's "tag builder", tightly restricting what data is allowed
to describe an "item", or going the "structured blogging" plugin
direction and not allowing reviews to be part of posts, but have their
own UI completely) aren't prettier IMO.
Its part a textpattern specific (or more importantly my code specific)
issue, but its also a general concern when it comes to how to build
intelligent microformat editors where something fairly typical arises
like the following...
hReview contains
reviewer hCard
event hCalendar contains location hCard
And have that same UI and storage mechanism also allow for an hreview
of a web page with nothing but a url..
*wonders how far all this flattery will get him*
Heh. Your well written code has gotten you much farther. ;)
Tantek
you haven't seen....
;)
--
[ Chris Casciano ]
[ [EMAIL PROTECTED] ] [ http://placenamehere.com ]
_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss
