lindenb

lindenb: Tshirt

2008-06-12T18:40:54.0012Z

Hey, I'd love to send you a Freebase tshirt in thanks for your contributions here. Could you send me your tshirt size and postal address to kirrily@metaweb.com

Thanks!

Ethnicity: Ethnicity ?

2008-05-23T07:31:01.0005Z

'French people', 'European', etc... this is not Ethnicity this is nationality. In genetics, only a few items are used 'Caucasian', 'African', 'Asian' ... and even here, that doesn't mean much things.

Scientist: Scientist reciprocation

2008-04-15T04:21:54.0007Z

I can't think of a way to do this with data modeling, but it would be nice if your "Worked with" property was automatically populated with co-authors and other topics having similar professional connections.

lindenb: Person created for you

2008-03-13T14:32:54.0000Z

The person-related properties you had were: gender, profession, and software developer software type.

Freebase makes a distinction between people and the user accounts used by those people. For one thing, a person might have multiple accounts; for another, user accounts are used by the system to track changes to data, write quotas, and things like that. Also, only a user (or administrator) can alter a user, while anyone can alter a person; the person is just another kind of community data, like the city in which you live or the school which you attended. (As Kirrily discussed on our mailing lists, we are considering drawing a distinction between public (or “notable,” as Wikipedia calls it) people and other people, and moving some more sensitive properties away from ordinary people for privacy reasons.)

lindenb: Person created for you

2008-03-13T09:19:17.0000Z

OK, I saw http://www.freebase.com/view/guid/9202a8c04000641f8000000007629113

thank you, but what "bunch of person-related properties associated with your (this) user" are you talking about ? Why should I have a distinct instance of person *and* my freebase user profile ?

lindenb: Person created for you

2008-03-06T22:42:28.0012Z

Hi, Pierre. You had a bunch of person-related properties associated with your (this) user. I created a discrete Person instance to represent you as a person, distinct from a user account, and moved those properties over there. Please take a look at see that they’re correct. Thanks.

lindenb: Featured user

2008-03-03T06:45:36.0003Z

Hi Deepak, It's 7H00 here,so it's time to go to bed for you :-)

lindenb: Featured user

2008-03-03T06:21:53.0012Z

Way cool :)

Scientist: Scientist reciprocation

2008-03-01T09:38:44.0000Z

OK, it works fine now ! :-)

Thank you very much

Scientist: Scientist reciprocation

2008-02-29T22:19:57.0007Z

Pierre, the properties used there aren’t reciprocated. You have a Teacher type with a “Student” property, which is reciprocated by the “Teacher” property on Student. Those work correctly. However, you also have “Teacher” and “Student” properties on Scientist, which are not reciprocated; that’s what you used to connect Oughtred and Wren.

Instead, type Wren as a Student, and then mark Oughtred as his teacher. Meanwhile, hide the “Student” and “Teacher” properties on Scientist to avoid confusion.

Scientist: Scientist reciprocation

2008-02-29T20:39:52.0007Z

Thank you, that was a very useful information ! :-)

However, I'm still missing someting : when I added William Oughtred as the teacher of Christopher Wren, when I go to the page of Oughtred, I could not find Wren as a student :-(

Scientist: Scientist reciprocation

2008-02-28T05:06:22.0005Z

This is an interesting tag with useful properties. However, I suggest you reciprocate the advisor, student and opponent properties. You can do this by creating an Advisor type and a Student type. Next, add a Student property to the Advisor type and list the Student type as the expected type. Click the link to go to the Student type's schema and name the suggested Advisor property at the bottom of the page to complete the reciprocation. Next, change the expected types of the student and advisor properties from Person to the Student and Advisor types. You will need to remove the existing links or delete the properties and rebuild them before this can be done. The result will be that when you fill in an advisor for a student topic, then that topic will automatically be linked as a student to the advisor's topic. Opponent is more difficult because it is a circular link that calls itself. You will need to build an Opponent CVT to make that reciprocation work.