Product brand is a pretty elegant solution. However, I'm having a little trouble conceptualizing how to use the type for a product such as a cell phone that may be produced by one company but sold and marketed by multiple middle men under the umbrellas of different brands.
<br><br>-Ed<br><br><div class="gmail_quote">On Jan 7, 2008 2:24 AM, Robert Cook <<a href="mailto:robert@metaweb.com">robert@metaweb.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Topic granularity for products is a very interesting topic. People<br>would like to think of the topics "Coke", "Diet Coke", "Diet Coke 1<br>liter bottle" all as type "product" in different circumstances. This
<br>could be handled by a "phylogeny" containment pattern, where the<br>product type pointed to more specific versions of the product, just as<br>the "location" type points to other contained locations.
<br><br>I like the "edible product" idea, although I suspect there might be a<br>more elegant name ;-) The "beer" type could benefit from your<br>suggested properties:<br><br><a href="http://www.freebase.com/view/schema/food/beer" target="_blank">
http://www.freebase.com/view/schema/food/beer</a><br><br>Also, ASINs, Netflix IDs, ISBNs and UPC codes are exactly the kind of<br>"foreign keys" we would like to get into Freebase. If anybody has<br>access to such keys, we will help get them loaded.
<br><font color="#888888"><br>R<br></font><div><div></div><div class="Wj3C7c"><br>On Jan 6, 2008, at 11:04 PM, Daniel E. Renfer wrote:<br><br>> I know this adds another layer to the data, but you might want to go<br>> even further and break it down to the types or brands of a product
<br>> and the instances or editions of that brand.<br>><br>> For instance:<br>><br>> <The Coca-Cola Bottling Corporation> produces <Coca-Cola><br>> <Coca-Cola> has an edition <Coca-Cola 20 oz. Bottle>
<br>> <Coca-Cola> has an edition <Coca-Cola 2 ltr. Bottle><br>><br>> <The Coca-Cola Bottling Corporation> produces <Diet Coke><br>><br>> You could then break it down to regional variance in ingredients,
<br>> weight, nutritional value, (although this would be a property of the<br>> co-type, Edible Products) etc.<br>><br>> I don't know how this would fly for most people, but what about a<br>> property to record the ASIN (The key in Amazon's database) of the
<br>> item as well.<br>><br>> Ed Laurent wrote:<br>>> I guess it's growing on me and Shawn's definition helps quite a bit<br>>> except I would replace "organization" with "person, company, or
<br>>> other organization". My concern is that the product <-> producer<br>>> concepts are so general that they should be well thought out and<br>>> modeled as generally as possible so that they support all relevant
<br>>> co-types now and in the future. For example, are UPC, weight/<br>>> volume, and cost universal properties of a product? Coca-cola for<br>>> example has different combinations of ingredients depending on
<br>>> where it is sold. Similarly, my motorcycle model has a different<br>>> gear ratio when sold in Japan compared to the U.S. Maybe these<br>>> versions have different UPCs but their differences in weight/volume
<br>>> are insignificant and you might be able to sell each version for<br>>> the same price. I don't know how many topics in Freebase can/will<br>>> be considered products but it's probably a bunch. Any problems
<br>>> later on could have big implications.<br>>> -Ed<br>>> On Jan 7, 2008 12:19 AM, Shawn Simister <<a href="mailto:narphorium@gmail.com">narphorium@gmail.com</a> <mailto:<a href="mailto:narphorium@gmail.com">
narphorium@gmail.com</a><br>>> >> wrote:<br>>> I would define a Product as a tangible object which is sold by an<br>>> organization under a specific brand name. Therefore corn or people<br>>> are not products but Corn Flakes and People Magazine are. I know
<br>>> that there are more general definitions of products, but I think<br>>> they could be accommodated by additional types like Commercial<br>>> Service, Commodity etc.<br>>> Shawn<br>
>> Ed Laurent wrote:<br>>>> The "Products producer" type with a "Products produced" property<br>>>> sounds pretty good to me. The "Product" type a little less so.
<br>>>> Would every tangible topic (including people) need to be typed as<br>>>> a product? What defines a product that separates it from other<br>>>> tangible topics? I agree that this kind of type could be very
<br>>>> useful and there should be reciprocation between product and<br>>>> producer but I'm not excited about this approach to doing it.<br>>>><br>>>> -Ed<br>>>><br>
>>> P.S. This conversation is probably more relevant to the Data<br>>>> Modeling list so I'm cc'ing it.<br>>>><br>>>><br>>>> On Jan 6, 2008 10:05 PM, Daniel E. Renfer <
<a href="mailto:duck@kronkltd.net">duck@kronkltd.net</a><br>>>> <mailto:<a href="mailto:duck@kronkltd.net">duck@kronkltd.net</a>>> wrote:<br>>>><br>>>> It would probably make sense to have some sort of "products
<br>>>> producer"<br>>>> co-type. The producers would have a "products produced" link<br>>>> to the<br>>>> "producer" field of the corresponding "product" type.
<br>>>><br>>>> Not every company produces products, and there are some<br>>>> products that<br>>>> are produced by groups other than companies.<br>>>><br>>>> Other than that, it sounds like great information to track.
<br>>>><br>>>> Kavitha Srinivas wrote:<br>>>> > For companies, is there any interest in linking companies<br>>>> to<br>>>> their<br>>>> > major products (
e.g., Pfizer to its key pharma products) as<br>>>> listed in<br>>>> > Wikipedia? I don't mind adding it, but there is no<br>>>> appropriate slot<br>>>> > to add it.
<br>>>> > Key products seems to be important information for a<br>>>> company.<br>>>> > Thanks!<br>>>> > Kavitha<br>>>> > _______________________________________________
<br>>>> > Developers mailing list<br>>>> > <a href="mailto:Developers@freebase.com">Developers@freebase.com</a> <mailto:<a href="mailto:Developers@freebase.com">Developers@freebase.com
</a>><br>>>> > <a href="http://lists.freebase.com/mailman/listinfo/developers" target="_blank">http://lists.freebase.com/mailman/listinfo/developers</a><br>>>><br>>>><br>>>> _______________________________________________
<br>>>> Developers mailing list<br>>>> <a href="mailto:Developers@freebase.com">Developers@freebase.com</a> <mailto:<a href="mailto:Developers@freebase.com">Developers@freebase.com</a>>
<br>>>> <a href="http://lists.freebase.com/mailman/listinfo/developers" target="_blank">http://lists.freebase.com/mailman/listinfo/developers</a><br>>>><br>>>><br>>>><br>>>> ------------------------------------------------------------------------
<br>>>><br>>>> _______________________________________________<br>>>> Data-modeling mailing list<br>>>> <a href="mailto:Data-modeling@freebase.com">Data-modeling@freebase.com</a>
<mailto:<a href="mailto:Data-modeling@freebase.com">Data-modeling@freebase.com</a>><br>>>> <a href="http://lists.freebase.com/mailman/listinfo/data-modeling" target="_blank">http://lists.freebase.com/mailman/listinfo/data-modeling
</a><br>>>><br>>> _______________________________________________<br>>> Data-modeling mailing list<br>>> <a href="mailto:Data-modeling@freebase.com">Data-modeling@freebase.com</a> <mailto:
<a href="mailto:Data-modeling@freebase.com">Data-modeling@freebase.com</a>><br>>> <a href="http://lists.freebase.com/mailman/listinfo/data-modeling" target="_blank">http://lists.freebase.com/mailman/listinfo/data-modeling
</a><br>>> ------------------------------------------------------------------------<br>>> _______________________________________________<br>>> Data-modeling mailing list<br>>> <a href="mailto:Data-modeling@freebase.com">
Data-modeling@freebase.com</a><br>>> <a href="http://lists.freebase.com/mailman/listinfo/data-modeling" target="_blank">http://lists.freebase.com/mailman/listinfo/data-modeling</a><br>><br>> _______________________________________________
<br>> Data-modeling mailing list<br>> <a href="mailto:Data-modeling@freebase.com">Data-modeling@freebase.com</a><br>> <a href="http://lists.freebase.com/mailman/listinfo/data-modeling" target="_blank">http://lists.freebase.com/mailman/listinfo/data-modeling
</a><br><br>_______________________________________________<br>Data-modeling mailing list<br><a href="mailto:Data-modeling@freebase.com">Data-modeling@freebase.com</a><br><a href="http://lists.freebase.com/mailman/listinfo/data-modeling" target="_blank">
http://lists.freebase.com/mailman/listinfo/data-modeling</a><br></div></div></blockquote></div><br>