[Data-modeling] Types for subjects
Jeff Prucher
jeff at metaweb.com
Wed Jul 8 20:40:56 UTC 2009
> -----Original Message-----
> From: data-modeling-bounces at freebase.com
> [mailto:data-modeling-bounces at freebase.com] On Behalf Of John
> Giannandrea
> Sent: Tuesday, July 07, 2009 4:48 PM
> To: Freebase data modeling mailing list
> Subject: Re: [Data-modeling] Types for subjects
>
>
> Jeff Prucher wrote:
> > How would this work? Practically any topic is a potential
> subject, so
> > I can see the appeal of using /common/topic there, but how would
> > incoming properties work? Either there'd need to be two
> properties on
> > / common/topic
> > -- "subjects" and "subject of" (a phylogeny pattern), or
> there'd have
> > to be a single "subject-having thing" type to connect to it. Or is
> > there another way?
>
> I think two properties on /common/topic could make sense, and
> one could always delegate that property to /film/film and the
> like if only certain contexts should display it.
OK, this is a really fascinating idea. I'm interested in how it could best
be implemented. The "subject of" property seems pretty straightforward --
just a new property that would appear on all topics. The "subjects"
property, though, is intriguing. It sounds like you're suggesting it could
be hidden on /common/topic, and only used as a delegated property? (I just
checked, and you can, indeed, delegate a non-hidden property from a hidden
one.)
Jeff
More information about the Data-modeling
mailing list