[Data-modeling] Types for subjects

[Jeff Prucher]

It looks like we're going to go forward with this proposal. Because the
properties on /common/topic have to handled specially by the client, it will
take some time to fully implement. 

Jeff

> -----Original Message-----
> From: data-modeling-bounces at freebase.com 
> [mailto:data-modeling-bounces at freebase.com] On Behalf Of Faye Harris
> Sent: Thursday, July 09, 2009 6:36 PM
> To: Freebase data modeling mailing list
> Subject: Re: [Data-modeling] Types for subjects
> 
> +1
> 
> This would make it much easier to enter and parse data on 
> topics like /en/world_war_ii, which has the following 
> subject-related types:
> 
> - book subject
> - literary genre
> - computer game genre
> - computer game subject
> - tv genre
> - film subject
> - art subject
> - media genre
> - speech topic
> - nobel subject area
> - exhibition subject
> - taxonomy subject
> 
> It may be worthwhile to examine how "foo subject" and "foo 
> genre", sometimes overlapping, are being used or misused.
> 
> -- Faye
> 
> 
> John Giannandra wrote:
> > yes, that is exactly what I was suggesting.
> >
> > there could be times when the 'subjects' property might 
> make sense to display too, but we can figure that our later 
> once we see how much of this data we actually have.  For 
> example imagine a 'books about this topic' property which is 
> delegated from /common/topic/subjects or whatever...
> >
> > -jg
> >
> >   
> >> ... It sounds like you're suggesting it could be hidden on 
> /common/topic, and only used as a delegated property?
> >>     
> > _______________________________________________
> > Data-modeling mailing list
> > Data-modeling at freebase.com
> > http://lists.freebase.com/mailman/listinfo/data-modeling
> >
> >   
> 
> _______________________________________________
> Data-modeling mailing list
> Data-modeling at freebase.com
> http://lists.freebase.com/mailman/listinfo/data-modeling
>