[Data-modeling] Migration of types to soccer commons

[Jeff Prucher]

If you don't change the key (or just add an additional key via MQL write),
changing the name of the property shouldn't break anything. I think making
it "Roster" rather than current roster is a good idea, though.
 
Jeff


  _____  

From: data-modeling-bounces at freebase.com
[mailto:data-modeling-bounces at freebase.com] On Behalf Of Iain Sproat
Sent: Thursday, July 09, 2009 4:06 PM
To: Freebase data modeling mailing list
Subject: Re: [Data-modeling] Migration of types to soccer commons


The soccer commons <http://schemas.freebaseapps.com/domain?id=/soccer>  is
now upgraded - I left out the 'squad' and 'competition season' subsets from
the migration as I wasn't too happy with them at the moment. 

I'd like to propose a breaking change - I'd like to rename 'Current Roster'
to 'Roster' on /soccer/football_team
<http://www.freebase.com/type/schema/soccer/football_team>  as it's now
time-mediated.


Bug reports and feature requests greatly appreciated - either here on the
soccer commons discussions.

Iain



On Thu, Jul 9, 2009 at 10:30 PM, Iain Sproat <iainsproat at gmail.com> wrote:


I'm about to replicate the types and properties currently in draft in the
football association
<http://schemas.freebaseapps.com/domain?id=/base/associationfootball>  base
into the soccer <http://schemas.freebaseapps.com/domain?id=/soccer>
commons.  This will only be the addition of types and properties, so I think
should* not break any existing apps.

There's been some discussion at
http://www.freebase.com/discuss/threads/guid/9202a8c04000641f800000000c5a708
b
 
<http://www.freebase.com/discuss/threads/guid/9202a8c04000641f800000000c5a70
8b> I'd appreciate any further comments.

*shout if you've an app that uses the soccer commons and think otherwise.


Iain


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freebase.com/pipermail/data-modeling/attachments/20090710/b9ca12a3/attachment.htm