[Data-modeling] modeling a mediator with an included type

[Ed Laurent]

Did my email not come through again? This seems to happen often on this
list. Here it is again:

>From Mon, May 25, 2009 at 5:27 PM

You probably want to use CVTs for roommates. I created some schema in a
Celeb sandbox base and added you as an admin. Not really sure what the Heat,
Interest, and Source info are about but I grouped them together into another
CVT to show you how that can be done too.
http://celeb.sandbox-freebase.com/type/schema/base/celeb/celeb

-Ed

P.S. I checked and the base is still on sandbox


On Tue, May 26, 2009 at 1:21 PM, Jeff Prucher <jeff at metaweb.com> wrote:

>  The Freebase client doesn't display disambiguators for included types.
> However, if you delegated the properties from the common type onto the CVT,
> it should work fine.
>
> To do this, edit the lived_with CVT; add a property for "heat"; select the
> "use a property from another type" option, and select the "heat" property
> from the common type.  If you make it a disambiguator, it should show up
> just like any other CVT property.
>
> jeff
>
>  ------------------------------
> *From:* data-modeling-bounces at freebase.com [mailto:
> data-modeling-bounces at freebase.com] *On Behalf Of *Jack Alves
> *Sent:* Monday, May 25, 2009 1:41 PM
> *To:* data-modeling at freebase.com
> *Subject:* [Data-modeling] modeling a mediator with an included type
>
>
> I'm trying to model special schema for celebrities. I tried a few things
> but it isn't obvious how I accomplish what we need to do.
>
> The special aspect of what I'm trying to do is that I want all types
> (topics and mediators) in this domain to include a common type with
> properties heat, interest, and source. These are for relevance and for a
> source (a web link that "verifies" the assertion).
>
> A person would be typed celeb. A property of celeb is lived_with. I thought
> I would make lived_with a CVT with disambiguated properties for the people,
> dates, and the included common type with heat, interest, and  source. But
> when I do this I can't use freebase.com to edit the common properties
> (heat, interest, source). So I tried making lived_with a topic. I get an
> error entering the property if I don't include a name for the topic, and the
> common properties don't display. Seems like it would be really sloppy to
> give names to the mediator properties like lived_with.
>
> I need to figure out what will work quickly because we are in the middle of
> development and are deciding if freebase will work as an alternative to our
> current database.
>
> We need to use freebase.com for editing. We don't necessarily need
> freebase.com to display common properties on a celeb property like
> lived_with. It would be okay if we had to navigate into a lived_with
> mediator to edit common properties. It would also be okay if freebase.comdisplayed the guid as a name.
>
> I created a types is a test domain/base,
>
> /base/celeb/celeb
> /base/celeb/lived_with - w/ properties participant, start date, end date,
> and included type common
> /base/celeb/common - w/ properties heat, interest, source
>
>
> Any suggestions for modelling this? I would be happy to send the existing
> full schema if someone wants to help model it. There are a bunch of types:
> wears, vacations, canoodled, dated, bought, shops at, endorsements...
>
> Jack Alves
> 510 604-3609
>
>
> _______________________________________________
> Data-modeling mailing list
> Data-modeling at freebase.com
> http://lists.freebase.com/mailman/listinfo/data-modeling
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freebase.com/pipermail/data-modeling/attachments/20090526/0fe3a2fc/attachment.htm