It looks like some of the Beverage properties are duplicating what should be associated with Consumer_product and Alcoholic_beverage. <br><br>I would describe Beverage with very generic properties. For example, <span class="producttitle">"Jack Daniel's Whiskey Single Barrel 94@</span>
<span class="bottlesize">750ML" would be a Consumer_product linked to "Jack Daniel's Whiskey Single Barrel 94" that is linked to Whiskey, which is co-typed with Beverage and Alcoholic_beverage. <br>
<br>Similarly, "Milk" would be typed with Beverage. I could see "Skim milk" as a topic of a "Milk type" enumerated type or go the route of adding properties to a Milk_product type that could be co-typed within Cheese and used to describe "Mozzarella cheese".<br>
<br>Another route would be to develop the schema so that the consumer product "Fresh Mozzarella" would be typed with Consumer_product and include a link to a Cheese CVT that includes properties such as Cheese_type, Milk_source (e.g., cow, goat), etc.<br>
<br>Somehow I went from Beverage and Whiskey to Cheese... <br><br>-Ed<br><br></span><div class="gmail_quote">On Fri, Jun 6, 2008 at 7:40 PM, Jeff Prucher <<a href="mailto:jeff@metaweb.com">jeff@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;">There are bunch of types for various beverages in the food domain, some of<br>
which could use a little fixing up. (Most of these were also made by me --<br>
mea culpa!)<br>
<br>
1) Beverage <<a href="http://www.freebase.com/tools/schema/food/beverage" target="_blank">http://www.freebase.com/tools/schema/food/beverage</a>>. I'm<br>
wondering if this type is even necessary. The instances are a mix of general<br>
beverage varieties ("Cocktail") and specific varieties ("Newcastle Brown<br>
Ale"), so at the very least this should be normalized and cleaned up. And<br>
both them "manufacturer" and "place of origin" properties seem redundant<br>
with some of the more fully-fleshed out beverage schemas, like beer and<br>
wine. And the "color" property is probably pointless.<br>
<br>
<br>
2) Whisky: This has a similar problem as beverage, in that the instances<br>
include both distilleries and products. I think that a simple fix would be<br>
to add a "distillery" property (and type), and reserve the "whisky" type for<br>
the specific whiskys (similar to the beer/brewery relationship). There's<br>
probably a lot more that could be done with whiskies, but for now I'd just<br>
like to clean up the current model.<br>
<br>
What do you all think?<br>
<br>
Jeff Prucher<br>
<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>
</blockquote></div><br>