[Data-modeling] Astronomy: CelestialObjects andNaturalSatellites

[Ed Laurent]

The employment option that Dan mentioned on another thread is also something
to consider. A professional baseball player is an employee of the team and
has a job that is one or more team positions. Naming is really the only
sticky point (see my feature request for property pseudonyms). Sport could
be linked through a professional athlete co-type.

-Ed

On Sun, May 4, 2008 at 12:57 AM, Ed Laurent <spatial.db at gmail.com> wrote:

> That's where a more generic "Professional athlete" type could come in. A
> "Sport" property on it could be reciprocated with a "Players" property on
> the sport. "Position" would be a little trickier but might work using
> disambiguation.
>
> -Ed
>
>
> On Sun, May 4, 2008 at 12:40 AM, Jeff Thompson <jeff at thefirst.org> wrote:
>
> > Ed Laurent wrote:
> > > I don't think the name "Type" has much to do with it. Baseball and
> > > Basketball player aren't bad names if they contain properties that are
> > > universal to all baseball or basketball players and no one else. I
> > would
> > > personally create a more generic "Professional sports player" type
> > > co-typed with "Team member" and the "Baseball player" type. It's
> > > properties like "Current team" on a very specific type (i.e., Baseball
> > > player) that tend to cause these conflicts.
> >
> > The problem is that, while Babe Ruth is typed as Baseball Player,
> > http://www.freebase.com/view/en/babe_ruth
> > there is no property which connects him to Baseball
> > http://www.freebase.com/view/guid/9202a8c04000641f800000000000a21e
> >
> > This means that you cannot do even a simple query like
> > "people born in Baltimore before 1900 and the sport they play".
> >
> > _______________________________________________
> > Data-modeling mailing list
> > Data-modeling at freebase.com
> > http://lists.freebase.com/mailman/listinfo/data-modeling
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freebase.com/pipermail/data-modeling/attachments/20080504/1c0f4bcc/attachment.htm