User Administrator http://www.freebase.com:80/view/user/user_administrator Freebase Atom Feed Generator http://www.freebase.com:80/view/user/szaijan 2008-09-08T19:03:04Z szaijan http://www.freebase.com:80/view/user/szaijan <p>Hi Dan, <br /> <br /> I need to use my own type for Fantasy Football positions for a couple of reasons. <br /> <br /> 1. Each league will have a different number of sets of positions to choose from, and they may or may not map to a position on the /american_football/football_position type. For example, there are Team Quarterbacks, Team Kickers, and Defensive Units that are FF positions, but not American Football positions. In addition, you have two Quarterback positions which can only be distinguished by ID, since there is no offense or defense property. Also, some leagues use Wide Receiver and Tight Ends as distinct positions, while others may use Receiver as a combination of the two. In any case, the Football Position needs to be distinct from the Fantasy Football position. <br /> <br /> 2. When enumerating types in scripts, I want to be able to control what returns in queries. I can do that with a private type, but not a public type. <br /> <br /> As for teams, NFL_Team uses your /american_football/football_team as its type and is definitely redundant with the /football_roster_position/team field. As I mentioned however, redundancy has cause problems with writing to and reading from this subfield and so I added it to my type for simplicity. At this point, it could be eliminated. <br /> <br /> As for stats, my only source is TheHuddle.com, as we discussed, and only for projections. Ideally, the Statistic fields would get populated by an XML pull from NFL.com and the projections would be an aggregate of moderated community submissions. I have no knowledge of an XML feed of NFL stats, but would love to locate one. The structure of your source data will likely dictate the actual stats you'd track, and thus structure of the Statistic instances I'd use to record the data, but they'd certainly map to NFL Week, NFL Season, and Player. You'd also want to keep a record of Opponent and Stadium where the stats were compiled. <br /> <br /> As for the aggregation of community projections, that's a worthy project in itself and outside my project's current scope.</p> http://www.freebase.com:80/view/guid/9202a8c04000641f8000000005b87f5d

Hi Dan, I need to use my own type for Fantasy Football positions for a couple of reasons. 1. Each...

2007-08-22T21:31:40.0012Z danm http://www.freebase.com:80/view/user/danm <p>still trying to get my head around what you're doing here -- you're thinking that fantasy football rosters would be good to store in Freebase? Interesting. Can't say we really anticipated it being used for that kind of data.<br /> <br /> Re your schemas - wondering why you're inputing player's teams in your own type when the current team and position field already exists on the football player type? It appears that much of this data is redundant?<br /> <br /> Also, if you're defining and loading historical stats - i'd like to work with you on the best way to model that - its pretty complicated to get right. What is your source for data? Thanks,<br /> Dan (danm)</p> http://www.freebase.com:80/view/guid/9202a8c04000641f8000000005b7acac

still trying to get my head around what you're doing here -- you're thinking that fantasy football...

2007-08-20T05:06:56.0004Z