[uf-discuss] RE: microformats for groups and group memberships?

[Jim Dalton]

I think that's great Chris. It's an elegant solution that I didn't even
think of.

I wonder whether nesting of hcards is allowed by the hcard standard though?
Would be nice if it was. You could map an entire company out with that
method, even down to individual departments or multiple locations.

Sincerely,

Jim Dalton
Production Director
ERE Media, Inc.
580 Broadway
Suite 304
New York, NY 10012

Phone: (212) 671-1181, ext. 802
Mobile: (917) 226-5631

jim at ere.net
http://www.ere.net
 

> -----Original Message-----
> From: Chris Messina [mailto:chris.messina at gmail.com] 
> Sent: Friday, August 11, 2006 9:35 PM
> To: jim at ere.net
> Cc: Microformats Discuss
> Subject: Re: [uf-discuss] RE: microformats for groups and 
> group memberships?
> 
> On 8/11/06, Jim Dalton <jim at ere.net> wrote:
> >
> > An example that pops into my head is any page where there 
> would be mulitple
> > membership lists on a single page. For example, a list of 
> attendees (in
> > hcard of course) to a conference, organized by company (in 
> its own hcard),
> > allowing the contact information in the company to be related to the
> > employeees without having to repeat it.
> 
> There's no reason why you couldn't do this and infer a relationship:
> 
> <div class="vcard">
> <h2 class="fn org">Foo Co.</h2>
> 
> <h3>Member Listing</h3>
> <ul class="xoxo">
> <li class="vcard"><a href="http://mulettesgalore.com" class="fn url"
> rev="founder moderator member">Joe Bob</a></li>
> </ul>
> </div>
> 
> So basically you could contain the member hcards within the group's
> "master" hcard... *I think*.
> 
> Does that make sense?
> 
> Chris
> 
> > > -----Original Message-----
> > > From: Chris Messina [mailto:chris.messina at gmail.com]
> > > Sent: Friday, August 11, 2006 5:26 PM
> > > To: jim at ere.net; Microformats Discuss
> > > Subject: Re: [uf-discuss] RE: microformats for groups and
> > > group memberships?
> > >
> > > On 8/11/06, Jim Dalton <jim at ere.net> wrote:
> > >
> > > > One thing I noticed on the examples I was looking at and
> > > posted (aside from
> > > > almost zero semantic markup) was that member lists often
> > > exist in a location
> > > > separate from the main "group" page. frequently, with long
> > > lists of members,
> > > > the member lists can be spread across multiple pages, often
> > > with different
> > > > URIs then the original group page.
> > >
> > > This is where you have to look at what the representation of the
> > > group's URI is... which goes to the concept of authority in
> > > microformats -- The One True Issue.
> > >
> > > Heh. I'm so clever.
> > >
> > > But anyway, the concept of XFN resides on the notion that 
> everyone you
> > > know has some kind of URI -- typically in the form of a 
> URL. (this is
> > > why OpenID and XFN are best buddies).
> > >
> > > So if the group has a URL, then we can do some *things* to show
> > > relationships... on a member's blog they might do this to express
> > > membership:
> > >
> > > <a href="http://mygroupliveshere.com" rev="founder moderator
> > > member">Joe Bob</a>
> > >
> > > At mygroupliveshere.com you might see a member listing, 
> reciprocating
> > > the relationship (a weak claim):
> > >
> > > <ul class="xoxo">
> > >   <li><a href="http://mulettesgalore.com" rel="founder moderator
> > > member">Joe Bob</a></li>
> > > </ul>
> > >
> > > Now, that's how XFN plays a role.
> > >
> > > You might be able to use something on the group homepage 
> like hAtom to
> > > contain an hcard to denote the group name and 
> description... And in
> > > within the hcard entry, you could list the members using XFN. How
> > > you'd handle paginated member lists, I'm not sure, but 
> I'm guessing
> > > that you could stem the URL so that all XFN members under 
> a certain
> > > URL stem could be presumed to be members, like on Flickr:
> > >
> > > http://flickr.com/groups/microformats/members
> > >
> > > or Ma.gnolia:
> > >
> > > http://ma.gnolia.com/groups/microformats/people
> > >
> > > Just some extemporaneous brainstorming.
> > >
> > > Chris
> > >
> 
>