To avoid confusion with XMDP profiles, we should choose a more
specific name, such as user-profile-examples, or user-bio-examples,
etc.
-brian
On 9/3/06, Chris Messina [EMAIL PROTECTED] wrote:
A long time ago we discussed the need for a user-profile microformat.
Clearly this would be a
While I take your point that profiles vs xmdp profiles I confusing,
the notion of a profile can also apply to groups or teams... So
user-profiles would be too specific.
Perhaps we should do more research and see if this effort requires two
separate formats for groups and individuals.
Chris
On
How about public-profiles?
Regards, etc...
David
On 9/4/06, Chris Messina [EMAIL PROTECTED] wrote:
While I take your point that profiles vs xmdp profiles I confusing,
the notion of a profile can also apply to groups or teams... So
user-profiles would be too specific.
Perhaps we should do more
Brian's suggestion is a good one, user-profiles.
Chris, consider solving the specific problem (principle #1) of user-profiles
rather than expanding it to include groups.
In addition, I very much recommend figuring out ways to just stick with
hCard to represent aspects of the profile, rather than
Well, let's do some research and see what we come up with.
I agree that user-profiles are the originating domain, but how does
this relate to something like hResume?
I guess maintaining hcard as a simple format for sending data relating
to someone's *contact* info is important to me... whereas
