[Data-modeling] Products schema test run

[Kirrily Robert]

I figure when someone comes to us with a comprehensive database of  
dental care products, their packaging and flavours, etc, then we can  
worry about it -- probably by creating a Dental Hygiene base.

K.

On Dec 23, 2008, at 3:51 PM, Jeff Prucher wrote:

> I think this basically works, although the problem you mentioned  
> with food
> products is going to occur in a lot of places. Crest toothpaste is  
> such an
> example -- it comes in a dizzying combination of flavors and  
> treatments,
> each of which comes in a wide variety of sizes and packages. Should  
> each
> combination of stuff be its own product line, so that that you can  
> easily
> find all the available Crest Cool Mint Gel with Tartar Control  
> sizes? Or,
> since there is so much variety, should there be no product line  
> below Crest
> Toothpaste, and just have a slew of products?
>
> Jeff
>
>> -----Original Message-----
>> From: data-modeling-bounces at freebase.com
>> [mailto:data-modeling-bounces at freebase.com] On Behalf Of
>> Kirrily Robert
>> Sent: Tuesday, December 23, 2008 2:15 PM
>> To: Freebase data modeling mailing list
>> Subject: [Data-modeling] Products schema test run
>>
>> Me and Robert and some others were talking about this in the
>> office and we all reached some kind of consensus (at least
>> between that small
>> group) in the end.  Here's what we came up with:
>> http://products.sandbox.freebase.com/
>>
>> I've added a handful of different kinds of producers,
>> brands/product lines, and products to the domain so you can
>> see some different
>> examples:
>>
>> * Coca Cola company -- one producer, hierarchy of brands
>> * Apple Inc -- one producer, numerous brands, product lines,
>> and products
>> * Ikea -- producer with numerous lines (eg. Billy, Ivar,
>> Leksvik) -- see Leksvik for examples
>> * Threadless -- producer with no product lines, just products
>> * Procter and Gamble -- Crest and Charmin product lines
>> * GMC -- Chevrolet and Saturn brands
>>
>> The idea is that this isn't perfect, but it provides a rough
>> outline for most areas, and if one area has a lot of existing
>> data and a better understood structure (as, for example, we have with
>> automobiles) then we can reflect that in a specific domain (eg.
>> Automotive).  This is a pattern we already have in Sports,
>> where we have forked off more specific domains for eg.
>> Basketball, to handle specific details that vary on a per-sport  
>> basis.
>>
>> One area we've definitely realised will need additional work
>> is Food Products, especially as regards packaging in
>> different sizes and so forth.  So please keep in mind that
>> this would happen in a "Food Product" co-type.  See
>> alexander's Breakfast Cereal base for a schema we're
>> considering for Food Products.
>>
>> K.
>>
>> --
>> Kirrily Robert
>> Freebase Community Director
>> kirrily at metaweb.com
>> http://freebase.com/
>>
>>
>>
>>
>> _______________________________________________
>> Data-modeling mailing list
>> Data-modeling at freebase.com
>> http://lists.freebase.com/mailman/listinfo/data-modeling
>>
>
> _______________________________________________
> Data-modeling mailing list
> Data-modeling at freebase.com
> http://lists.freebase.com/mailman/listinfo/data-modeling

-- 
Kirrily Robert
Freebase Community Director
kirrily at metaweb.com
http://freebase.com/