[Data-modeling] [Developers] Modeling question

[Ed Laurent]

The "Products producer" type with a "Products produced" property sounds
pretty good to me. The "Product" type a little less so. Would every tangible
topic (including people) need to be typed as a product? What defines a
product that separates it from other tangible topics? I agree that this kind
of type could be very useful and there should be reciprocation between
product and producer but I'm not excited about this approach to doing it.

-Ed

P.S. This conversation is probably more relevant to the Data Modeling list
so I'm cc'ing it.


On Jan 6, 2008 10:05 PM, Daniel E. Renfer <duck at kronkltd.net> wrote:

> It would probably make sense to have some sort of "products producer"
> co-type. The producers would have a "products produced" link to the
> "producer" field of the corresponding "product" type.
>
> Not every company produces products, and there are some products that
> are produced by groups other than companies.
>
> Other than that, it sounds like great information to track.
>
> Kavitha Srinivas wrote:
> > For companies, is there any interest in linking companies to their
> > major products (e.g., Pfizer to its key pharma products) as listed in
> > Wikipedia?  I don't mind adding it, but there is no appropriate slot
> > to add it.
> > Key products seems to be important information for a company.
> > Thanks!
> > Kavitha
> > _______________________________________________
> > Developers mailing list
> > Developers at freebase.com
> > http://lists.freebase.com/mailman/listinfo/developers
>
>
> _______________________________________________
> Developers mailing list
> Developers at freebase.com
> http://lists.freebase.com/mailman/listinfo/developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freebase.com/pipermail/data-modeling/attachments/20080106/c757ea16/attachment-0001.htm