<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"
  >
  


  <author ><name>Freebase Staff</name>
<uri>http://www.freebase.com/view/user/domain_administrator</uri>
</author>



<generator uri="http://www.freebase.com/" >Freebase Atom Feed Generator</generator>


<id>http://www.freebase.com/view/sports</id>

<link href="http://www.freebase.com/feed/discuss/all/sports" rel="self"  />





<title>Freebase: Discussion about Sports</title>

<updated>2010-01-04T12:00:31Z</updated>

<entry >
      <author ><name>jeff</name>
<uri>http://www.freebase.com/view/user/jeff</uri>
</author>

    
    <content type="html">&lt;p&gt;I prefer the CVT version as well. We could just hide/deprecate the old start/end date properties.  None of the sport-specific types have career date properties, so we wouldn't have to refactor any of those. &lt;/p&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f8000000013175ad5</id>

    <link title="Pro Athlete: Sports played?" href="http://www.freebase.com/view/guid/9202a8c04000641f8000000013175ad5" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >I prefer the CVT version as well. We could just hide/deprecate the old start/end date properties. ...</summary>

    <title>Pro Athlete: Sports played?</title>

    <updated>2009-12-30T20:22:56.0005Z</updated>

</entry>
<entry >
      <author ><name>faye</name>
<uri>http://www.freebase.com/view/user/faye</uri>
</author>

    
    <content type="html">&lt;p&gt;+1 for CVT with career start &amp;amp; end dates.&lt;/p&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f8000000013119f0f</id>

    <link title="Pro Athlete: Sports played?" href="http://www.freebase.com/view/guid/9202a8c04000641f8000000013119f0f" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >+1 for CVT with career start &amp;amp; end dates. </summary>

    <title>Pro Athlete: Sports played?</title>

    <updated>2009-12-28T22:58:31.0013Z</updated>

</entry>
<entry >
      <author ><name>tfmorris</name>
<uri>http://www.freebase.com/view/user/tfmorris</uri>
</author>

    
    <content type="html">&lt;p&gt;If you implemented your second suggestion, you wouldn't need the first, since the Sport would be specified in the CVT, right?  That seems like the more powerful solution, since it would allow you to construct queries like &quot;show me all people who were playing professional basketball in 1982.&quot;  Does it have implications for any of the sport-specific types (ie do they have start/end career dates)?&lt;/p&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f8000000013117772</id>

    <link title="Pro Athlete: Sports played?" href="http://www.freebase.com/view/guid/9202a8c04000641f8000000013117772" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >If you implemented your second suggestion, you wouldn't need the first, since the Sport would be...</summary>

    <title>Pro Athlete: Sports played?</title>

    <updated>2009-12-28T18:19:25.0001Z</updated>

</entry>
<entry >
      <author ><name>jeff</name>
<uri>http://www.freebase.com/view/user/jeff</uri>
</author>

    
    <content type="html">&lt;div&gt;&lt;p&gt;What do people think about a &quot;Sports played professionally&quot; property on this type?  I think it would be useful for a couple reasons.  One is that we don't (and won't any time soon, if ever) have as many sport-specific &quot;Sport Player&quot; as there are professional sports, so we can't rely on co-types to tell us what any given pro athlete's sport is. The other is that, even if we did have a complete set of Sport Player types, lots of pro athletes have played other sports non-professionally (e.g. in college or post-retirement), which are legitimate uses of those types, so co-types will never be a reliable guide to a pro athlete's professional sport(s).&lt;/p&gt;
&lt;p&gt;For extra points, we could refactor the Start/End of career dates into a CVT with Sport, so that multisport pro athletes could have different start and end dates for different sports.&lt;/p&gt;
&lt;p&gt;Thoughts?&lt;/p&gt;&lt;/div&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f8000000013115eac</id>

    <link title="Pro Athlete: Sports played?" href="http://www.freebase.com/view/guid/9202a8c04000641f8000000013115eac" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >What do people think about a &quot;Sports played professionally&quot; property on this type? I think it...</summary>

    <title>Pro Athlete: Sports played?</title>

    <updated>2009-12-28T16:38:32.0005Z</updated>

</entry>
<entry >
      <author ><name>jeff</name>
<uri>http://www.freebase.com/view/user/jeff</uri>
</author>

    
    <content type="html">&lt;p&gt;I agree -- adding a CVT to the relationship between any team and any league(s) would be a much better way to model this. I'll create a JIRA task for the proposal (&lt;a href=&quot;https://bugs.freebase.com/browse/DA-1020&quot;&gt;DA-1020&lt;/a&gt;).  This would be a major change, so we'll have to run it past the mailing lists.&lt;/p&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f80000000130d7c5e</id>

    <link title="Sports Association: Team/League association not dated" href="http://www.freebase.com/view/guid/9202a8c04000641f80000000130d7c5e" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >I agree -- adding a CVT to the relationship between any team and any league(s) would be a much...</summary>

    <title>Sports Association: Team/League association not dated</title>

    <updated>2009-12-22T19:17:33.0006Z</updated>

</entry>
<entry >
      <author ><name>hangy</name>
<uri>http://www.freebase.com/view/user/hangy</uri>
</author>

    
    <content type="html">&lt;div&gt;&lt;p&gt;I don't get why the &lt;a href=&quot;/view/sports/sports_league&quot;&gt;Sports Association&lt;/a&gt; type suggests that a sports team is a member of a league and that does not change. If it would change, all historical data of a league participation would be gone once the Freebase topic is brought up-to-date, and I don't think that's a good idea. :)&lt;/p&gt;
&lt;p&gt;The way the &lt;a href=&quot;/view/soccer/football_league_participation&quot;&gt;Football League Participation&lt;/a&gt; and &lt;a href=&quot;/view/soccer/football_league_season&quot;&gt;Football League Season&lt;/a&gt; are modeled makes much more sense - to me - which is why I originally modelled &lt;a href=&quot;/view/base/handball/handball_league_season&quot;&gt;Handball League Season&lt;/a&gt; and &lt;a href=&quot;/view/base/handball/handball_league_participation&quot;&gt;Handball League Participation&lt;/a&gt; after those types.&lt;/p&gt;
&lt;p&gt;Even though these custom built types for each sport seem to work relatively well right now, it seems to me that it our data would be better for a lot of things if there was a generic &quot;Sports League Participation&quot; type in the commons and if the &lt;a href=&quot;/view/sports/sports_league_season&quot;&gt;Sports League Season&lt;/a&gt; refered to the sports league and the participating teams somehow.&lt;/p&gt;
&lt;p&gt;I would really like to see the sports commons a bit more flexible than they ae right now. The sports leagues that I know of have some relegation and promotion to higher leagues etc., so a team's place in a league is not ever set in stone. :)&lt;/p&gt;&lt;/div&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f80000000130d0670</id>

    <link title="Sports Association: Team/League association not dated" href="http://www.freebase.com/view/guid/9202a8c04000641f80000000130d0670" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >I don't get why the Sports Association type suggests that a sports team is a member of a league and...</summary>

    <title>Sports Association: Team/League association not dated</title>

    <updated>2009-12-22T10:39:10.0006Z</updated>

</entry>
</feed>
