It would be great if each call could have 2 additional items to assist with caching data.  There are a number of tables 
that we should cache and not pound the FRC Event API for.  For example, nearly all of the Season data (Season Summary, 
Event Listing, District Listing, and Team Listing) should update far less frequently than other data.  

1) For each table, there should be a unique identifier passed.  For example, in the Event Awards call there is an Award 
ID.  Matching up IDs and making updates appropriately will reduce overhead.  Currently, if you want to create a unique 
ID for Event Schedule, you would generally need the following columns:  season, event, tournamentLevel, and matchNumber.
  You could create a primary key set based on this data.  However, having a unique, numerical identifier will make it 
much faster!  Also, if we had an ID, then related tables, like Team, would be easier to establish relationships with.  
Obviously if there is a subset of data (like Teams) associated with a match, it would be great to have a single table of
 teams to relate that to.  With the current set of data, we have to make some assumptions and try to match up the data. 
 Team Number can be used as a unique identifier generally.

2)  For each call, it would be great if you could simply ask for changes after a specific date/time.  For example, 
rather than having to refresh the full Event Listing, it would be great if you could pass in a date/time and get back 
just the items that were added or updated since that time. 

Does this make sense?  I know I am late to the party for 2016, but if the above could be considered for 2017, that would
 be awesome!