[uf-discuss] Current state of grouping proposal

[Xavier Badosa]

> I think the grouping mechanism can be accomplished with XOXO,

XOXO as it is now (or as I understand it) is based on list elements
(ol ul dl), and these are not suited for "grouping" purposes, not in
my sense at least: maybe I should say "classing" instead of "grouping"
because in my meaning the idea of inheritance is important.

List elements don't allow to associate data to the group itself. In my
previous example,

>> <div class="hset">
>>   <h1 class="item"><a href="IMDB_URI" class="fn url">The Godfather
>>   II</a></h1> <div class="hreview">
>>      <blockquote class="description">The best!</blockquote>
>>      <p class="reviewer vcard"><em class="fn">Some guy</em></p>
>>   </div>
>>   <div class="hreview">
>>      <blockquote class="description">Soooooo good!</blockquote>
>>      <p class="reviewer vcard"><em class="fn">Enthusiastic
>>      girl</em></p>
>>   </div>

"item" is associated with the group ("hset"), telling implicitly the
machine that it must be replicated for every member ("hreview") of the
"group" (or "class"). It's a sort of include-pattern mechanism that
happens to follow the principle of adapting to current behaviors in
the publication of reviews on webpages. I think you can't do that with
XOXO.

X.

On Wed, Jul 2, 2008 at 10:24 PM, Bob Jonkman <bjonkman at sobac.com> wrote:
> I think the grouping mechanism can be accomplished with XOXO,
> http://microformats.org/wiki/xoxo
>
> --Bob.
>
>>>> 1 Jul 2008 18:08  Xavier Badosa <microformats-
> discuss at microformats.org>  >>>
>
>> I'm a little confused about the current state of the grouping
>> proposal. I'm not sure even if the uf-community is working on a
>> general solution (a microformat for grouping any sort of items) (+1
>> vote) or a particular solution for some of the existing microformats
>> (0 votes).
>>
>> I think some sort of grouping is needed in hReview if we want to
>> follow the principle of adapting to current behaviors and usage
>> patterns. Usually, webpages include more than one review for a single
>> item. To solve this, hReview forces us:
>>
>> 1) to repeat an unnecessary hidden item for every hreview (this
>> somehow violates the hidden (meta)data principle);
>>
>> or
>>
>> 2) to use the include-pattern (empty anchor, accessibility issues).
>>
>> A grouping mechanism could come to the rescue. Something like:
>>
>> <div class="hset">
>>   <h1 class="item"><a href="IMDB_URI" class="fn url">The Godfather
>>   II</a></h1> <div class="hreview">
>>      <blockquote class="description">The best!</blockquote>
>>      <p class="reviewer vcard"><em class="fn">Some guy</em></p>
>>   </div>
>>   <div class="hreview">
>>      <blockquote class="description">Soooooo good!</blockquote>
>>      <p class="reviewer vcard"><em class="fn">Enthusiastic
>>      girl</em></p>
>>   </div>
>> </div>
>>
>> could be interpreted by a parser that the same item should be
>> associated with every hreview. In fact, a grouping microformat would
>> be an alternative (easy to parse) include-pattern mechanism.
>>
>> X.
>
>
> -- -- -- --
> Bob Jonkman <bjonkman at sobac.com>         http://sobac.com/sobac/
> SOBAC Microcomputer Services              Voice: +1-519-669-0388
> 6 James Street, Elmira ON  Canada  N3B 1L5  Cel: +1-519-635-9413
> Software   ---   Office & Business Automation   ---   Consulting
>
>
> _______________________________________________
> microformats-discuss mailing list
> microformats-discuss at microformats.org
> http://microformats.org/mailman/listinfo/microformats-discuss
>