[Data-modeling] [Developers] /architecture schema changes

[brendan]

I just crawled for non-uniques in the data and came up with just a  
handful which I corrected.  I found two more properties I'd like to  
mark unique:

/architecture/structure/destruction_date
/architecture/structure/construction_cost

and /architecture/house/height_meters didn't actually exist, so  
scratch that one.

I'll wait a day or two before changing the schema.  This is a pretty  
safe change if, indeed, there were anyone out there running queries  
against this data. The only significant schema change is removing the  
building/height_meters property, but that has long been a hidden  
property anyhow.

Brendan

On Apr 15, 2008, at 2:31 PM, brendan wrote:

> 1. properties that should be marked unique properties
>
> /architecture/structure/height_meters
> /architecture/structure/construction_started (date)
> /architecture/structure/closed (date)
> /architecture/building/floors
> /architecture/building/floor_space_square_meters
> /architecture/skyscraper/height_with_antenna_spire_meters
>
> Currently, these are *not* set to be unique in the schema, which
> doesn't make much sense and prohibits doing a mql sort (which would be
> a nice thing to do)
>
> 2. to be removed
>   /architecture/house/height_meters
>   /architecture/building/height_meters
> both are functionally redundant (with /architecture/structure/
> height_meters)
>
> I will make these changes pretty soon (and do some related minor data
> updates). I don't know of anyone who would be affected by this change.
> If you are chime in...
>
> thanks,
>
> Brendan
> _______________________________________________
> Developers mailing list
> Developers at freebase.com
> http://lists.freebase.com/mailman/listinfo/developers