Cheese and crackers that's a good question!!<br><br>No properties come to mind besides those that refer to texture, color and taste but I'm not sure how those should be modeled. Beverage should probably be co-typed with a generic Liquid type if you don't mind that kind of overkill. <br>
<br>-Ed<br><br><div class="gmail_quote">On Mon, Jun 9, 2008 at 6:52 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;">
<div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2">Do you think that "beverage" should have any properties at
all, or should it just be a bucket to stick classes of things you can drink
(e.g., whiskey, milk, water, fruit juice)?</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2">Jeff</font></span></div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2"></font></span> </div>
<div dir="ltr" align="left"><span><font color="#0000ff" face="Arial" size="2">PS -- Mmmm. Whiskey cheese.
<a href="http://www.cheesesupply.com/product_info.php/products_id/270" target="_blank">http://www.cheesesupply.com/product_info.php/products_id/270</a></font></span></div><br>
<blockquote style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div dir="ltr" align="left" lang="en-us">
<hr>
<font face="Tahoma" size="2"><b>From:</b> <a href="mailto:data-modeling-bounces@freebase.com" target="_blank">data-modeling-bounces@freebase.com</a>
[mailto:<a href="mailto:data-modeling-bounces@freebase.com" target="_blank">data-modeling-bounces@freebase.com</a>] <b>On Behalf Of </b>Ed
Laurent<br><b>Sent:</b> Sunday, June 08, 2008 12:48 AM<br><b>To:</b> Freebase
data modeling mailing list<br><b>Subject:</b> Re: [Data-modeling] Tweaks to
the food domain<br></font><br></div><div><div></div><div class="Wj3C7c">
<div></div>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>"Jack Daniel's Whiskey Single Barrel 94@</span> <span>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" target="_blank">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" target="_blank">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></div></div></blockquote></div>
<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></blockquote></div><br>