[Data-modeling] /location/location/area not unique

[Jeff Prucher]

The odd case here is /book/pagination/numbered_pages, which is already a
property on a CVT, and really is meant to be non-unique: Some books, usually
bibles and omnibuses, have multiple paginations within the body of the book.
But this is a pretty unusual case.  (And that LEAID property really oughtta
be a machine-readable string.)

WRT area, the thing we should probably do for now is decide that it's for
current area, and punt the issue of conflicing datasources for now, like we
have with all the other unique numeric values thus far.

Jeff

> -----Original Message-----
> From: data-modeling-bounces at freebase.com 
> [mailto:data-modeling-bounces at freebase.com] On Behalf Of 
> Praveen Paritosh
> Sent: Friday, September 19, 2008 12:47 PM
> To: Freebase data modeling mailing list
> Subject: Re: [Data-modeling] /location/location/area not unique
> 
> 
> Claim: Numeric properties should always be unique. 
> 
> Below is a list of all floats and ints in Freebase that can 
> have multiple values. It seems that in every case, they 
> should be modeled as CVTs, for example, if a star has 
> multiple masses, they are refering to diffferent estimates or 
> a book has multiple paginations with different numbered 
> pages, they are refering to editions or prints of books. How 
> often we need this modeling simplification? The claim is 
> intentionally exaggerated, maybe there are valid cases of 
> multiple numeric values -- examples? 
> 
> 
> /type/float:
> 
> ['/astronomy/star/mass_m', '/astronomy/star/radius', 
> '/user/ptomblin/default_domain/aerodrome/pattern_altitude_mete
> rs', 
> '/user/benstiglitz/default_domain/portable_media_player/capaci
> ty', '/user/brendan/musician_products/speaker_cabinet/ohms', 
> '/astronomy/comet/epoch', 
> '/user/spatialed/bird_codes/sampling_design/area', 
> '/user/spatialed/bird_codes/sampling_design/width', 
> '/user/spatialed/bird_codes/sampling_design/length', 
> '/user/spatialed/bird_codes/sampling_design/radius', 
> '/user/spatialed/bird_codes/sampling_design/survey_time_per_vi
> sit', 
> '/user/mrmasterbastard/default_domain/electric_car/full_charge
> _time', '/user/akatenev/weapons/gun/weight', 
> '/user/metapsyche/exoplanetology/exoplanet/mass_jupiter', 
> '/astronomy/orbital_relationship/inclination', 
> '/guid/9202a8c04000641f8000000008c17404', 
> '/user/kesava/indian_railways_base/indian_railways_train/avera
> ge_speed', 
> '/user/kesava/indian_railways_base/indian_railways_train/dista
> nce_covered', '/user/mikeshwe/cyclocross_bikes/crankset
>  /crank_arm_length', '/user/jdouglas/view/location/area', 
> '/user/tom000/default_domain/portable_media_player/memory_size']
> 
> /type/int:
> 
> ['/book/pagination/numbered_pages', 
> '/user/xavier/default_domain/revision/number', 
> '/biology/genomic_locus/end_base', 
> '/biology/genomic_locus/start_base', 
> '/government/us_president/presidency_number', 
> '/user/spatialed/bird_codes/sampling_design/number_of_breeding
> _visits', 
> '/user/spatialed/bird_codes/sampling_design/number_of_observer
> s_per_site', 
> '/user/mindstream/default_domain/rating/ratingcount', 
> '/user/indexxml/default_domain/aaa/try', 
> '/user/drakecaiman/default_domain/computer_game_release/number
> _of_discs', '/user/barak/social_dance/dance_style/counts', 
> '/user/kesava/indian_railways_base/indian_railways_train/trave
> l_time_in_mins', 
> '/user/mikeshwe/cyclocross_bikes/crankset/chainring_teeth', 
> '/education/school_district/leaid', 
> '/user/biocode/computer_hardware_components/case/internal_5_25
> _bay', 
> '/user/biocode/computer_hardware_components/case/external_5_25
> _bay', 
> '/user/biocode/computer_hardware_components/case/internal_3_5_
bay', '/user/biocode/computer_hardware_components/c
>  ase/external_3_5_bay', 
> '/user/mr_kav/default_domain/customer/num', 
> '/user/wf/shape_note_singing/tunebook_tune/page_number']
> 
> 
> 
> 
> ----- Original Message -----
> From: "Alexander Marks" <al at metaweb.com>
> To: "Freebase data modeling mailing list" <data-modeling at freebase.com>
> Sent: Friday, September 19, 2008 12:14:48 PM (GMT-0800) 
> America/Los_Angeles
> Subject: Re: [Data-modeling] /location/location/area not unique
> 
> Both of those things require a migration to a CVT, don't they?
> 
> ----- Original Message -----
> From: "Jeff Prucher" <jeff at metaweb.com>
> To: "Freebase data modeling mailing list" <data-modeling at freebase.com>
> Sent: Friday, September 19, 2008 9:42:07 AM (GMT-0800) 
> America/Los_Angeles
> Subject: Re: [Data-modeling] /location/location/area not unique
> 
> Hmmm.  I can think of two reasons for it not to be unique, 
> one of which would require a change in the model. The first 
> is that different sources will give you different values. The 
> second is everybody's favorite anwser to any sort of 
> modelling question: It could be date-mediated! 
> 
> Jeff
> 
> > -----Original Message-----
> > From: data-modeling-bounces at freebase.com
> > [mailto:data-modeling-bounces at freebase.com] On Behalf Of Alexander 
> > Marks
> > Sent: Thursday, September 18, 2008 5:24 PM
> > To: Freebase data modeling mailing list
> > Subject: [Data-modeling] /location/location/area not unique
> > 
> > Shouldn't /location/location/area be unique?
> > 
> > Al
> > 
> > _______________________________________________
> > 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
> 
> _______________________________________________
> 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
>