On Fri, May 13, 2005 at 12:40:26PM -0700, Boris Mann wrote:
On 13-May-05, at 11:08 AM, neil@civicspacelabs.org wrote:
On Fri, May 13, 2005 at 09:11:27AM +0200, Dries Buytaert wrote: FOAF really didn't have an ideal solution to this. Chris Messina had some strong criticism for it:
# The FOAF module has the worst possible UI I've ever seen. It doesn't # help you get started, it begins with a dirth of stupid fields that # don't allow you to fix the problem of associating the fields with # contact fields. Why doesn't the software do the association for you?! # # This module is ONE BIG DEAD END! http://civicspacelabs.org/home/node/6939
Excellent criticism...with no suggestions on how to fix this.
We (Bryght) ship profile + FOAF pre-configured, so it "just works". It is "solved" by a mapping interface between defined profile fields and the standard set of FOAFnet fields. Of course, core Drupal ships with profile empty, which means it takes a while to configure. I think we had discussed this a while back...shipping profile with a set of pre-defined, standard fields.
This is an excellent way to make these modules work together. With location module we have a consistent place for locative data which is more dependable than the profile module. -Neil