[Data-modeling] deceased organism cause of death

[Faye Li]

Another vote for JG's suggestion. The distinction between what affects 
humans and what affects other organisms is not an artificial or 
arbitrary one and needs to be upheld. For example, many values of 
/people/cause_of_death are currently co-typed as /medicine/disease; 
we're been trying hard to keep human and animal diseases separate and 
animal diseases out of the Medicine domain.

-- Faye


Jeff Prucher wrote:
> I like JG's suggestion.  Delegation won't work in this case because the
> source type of the delegated property is always added to any topics that use
> the delegated property, which means that deceased people would also be typed
> as deceased organisms.
>
> Jeff
>
>   
>> -----Original Message-----
>> From: data-modeling-bounces at freebase.com 
>> [mailto:data-modeling-bounces at freebase.com] On Behalf Of Warren Harris
>> Sent: Tuesday, July 22, 2008 7:03 PM
>> To: Freebase data modeling mailing list
>> Subject: Re: [Data-modeling] deceased organism cause of death
>>
>> Would this be a case for delegated properties? We could have 
>> a general /biology/deceased_organism/cause_of_death, and a 
>> delegated / people/cause_of_death. Overkill -- probably, and 
>> would allow lumping and splitting. (Plus throw in a 
>> deceased_person with included type deceased_organism for good 
>> measure.)
>>
>> Warren
>>
>>
>> On Jul 22, 2008, at 6:37 PM, John Giannandrea wrote:
>>
>>     
>>> The cause_of_death could be moved to /biology if we wanted 
>>>       
>> to conflate
>>     
>>> them.
>>>
>>> But then you would be saying that the  reciprocal property 
>>>       
>> 'People Who
>>     
>>> Died This Way' should be generalized to 'organisms who died 
>>>       
>> this way'
>>     
>>> and that seems too general to be as useful.
>>>
>>> The question boils down to whether its more valuable to know in
>>> general that some people and some horses died of a heart attack, or
>>> keep these in two separate semantic buckets and if you want to know
>>> that you have to look in two places.    Lumping vs. splitting.
>>>
>>> In this case Id propose splitting, keeping the distinction between
>>> deceased_organism and deceased_person.   This will also 
>>>       
>> have the nice
>>     
>>> property that when looking at a cause of death you will see two
>>> classes of the afflicted.
>>>
>>> -jg
>>>
>>> Alexander Marks wrote:
>>>       
>>>> Apart from it being strange to expect something in the /person
>>>> domain, is there a good reason why /biology/deceased_organism/
>>>> cause_of_death shouldn't expect /people/cause_of_death? In other
>>>> words, is it important to distinguish between human and non-human
>>>> causes of death?
>>>>         
>>> _______________________________________________
>>> 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
>
>