[Data-modeling] the commons / non distinction is a farce

[Kirrily Robert]

On Jun 29, 2009, at 11:20 AM, Stefano Mazzocchi wrote:
>
> Say it were and you were in charge of making it happen: how would  
> you do
> it?
>
> I'm not defensive, I'm honestly curious.


This was what I was going to ask too :)  We've talked about this a LOT  
internally and it's actually an extremely hard problem (or at least we  
find it to be so).  We would really welcome suggestions for the design  
of a more collaborative way of doing schema that doesn't break things  
for app developers.  Even just a workflow of "I'm a schema developer,  
here's what I would like to do, step by step" would help.

Meanwhile, there are some things we can do to help with the main  
annoyances, I think.  The email notification system that just came  
live is a help as it allows us to contact schema admins more easily.   
There's a new Freebase Suggest in the works which I hope will make it  
easier to distinguish between multiple types with the same name.  Acre  
code search is likely to be increasingly useful for seeing just how  
many people are using a certain schema in their apps (it won't catch  
non-Acre apps, but as the number of apps grows, it will at least give  
us *some* idea.)

K.

-- 
Kirrily Robert
Freebase Community Director
kirrily at metaweb.com
http://freebase.com/