Clarity strategy for dealing with outdated Facebook.xsd

Feb 8, 2009 at 3:22 PM
Edited Feb 8, 2009 at 3:25 PM
On Friday a number of important API changes http://developers.facebook.com/news.php?blog=1&story=193
were made that do not appear to be reflected in the already outdated Facebook.xsd (http://www.google.com/search?q=facebook.xsd).

This is a question for the Clarity guys, is there a strategy to deal with the lack of updates to this .xsd? Without them the API will remain static which isn't a whole lot better than where the v1.7 toolkit ended up. Do any of you have connections with Facebook to prompt them to update this file so that the FDT can deal with API changes?

Thanks
-Steve
http://www.stevetrefethen.com/blog/
Facebook Starter Kit: http://www.stevetrefethen.com/wiki/Facebook%20application%20development%20in%20ASP.NET.ashx
Developer
Feb 8, 2009 at 7:45 PM
We don't have any more connections than any other user has, at least to my knowledge, so we don't really have any special way of putting pressure on the FB team. We have no "in" with them; we just decided one day a while back that making a .NET-based toolkit for the Facebook API would be a good idea, and we made it.

That said, there are a couple of different things that can be done about this issue. Facebook hosts a community bug tracker, and we've used that a few times to have them solve some problems with varying degrees of success. Either way, though, making sure the issue is listed on their bug tracker with plenty of detail is by far the best way to get any issues with the Platform solved.

Until that point, the best we can do is modify our own copy of the .xsd (I believe it's distributed with the source) with a few custom changes to reflect the current state of the API. Here at Clarity, we don't have anyone who is currently dedicated to updating the FDT, so patches from the community are always welcome.
Feb 9, 2009 at 3:11 AM
I figured as much. I do know a few people at FB so I'll see if I can find anything out. I've posted to the FB forums under API so feel free to chime in and add your "me too" comment!

I don't know if you can affect this at all but would it be possible to move the link back to my starter kit to the main FDT page? I get zero hits from the secondary page it was moved to here on codeplex whereas I get a dozen or more hits a day from the seemingly defunct Facebook.NET page where it's listed on the main page. I've put quite a bit of time and effort into making FDT more beginner friendly with my Starter Kit and would sure appreciate it.

Thanks,
-Steve