Hi Alistair, The documentation is wrong. Use the <content src="" /> attribute.
16 months ago, I gave a pretty clear description of this exact issue at http://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=2356#c4. It took me an hour our two to reason it out and explain it as clearly as I could. Ten months later, Vic closed it with a status 'Obsolete' and a comment "This is something that we will fix in a future version of the API." Five months later still, and there is no new version of the API. In fact, there's not even any public information about what the API will *do* (although Vic's made a pretty rude offer to everyone in an email thread (except for me) to join him in a little tete-a-tete on Google+). If you enjoy being abused, you could file a new issue about it using this URL: http://code.google.com/a/google.com/p/apps-api-issues/issues/entry But they haven't bothered to respond to any of the other issues raised in the last year ... why would they pay any attention to yours? You could vote for http://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=2516as kind of pathetic protest. Issues these days are more in the vein of rally cries rather than an actual conversation. The following dialog simply does not exist in Spreadsheet API land: user: "hey, I found a bug", google: "thank you for reporting that, it's clearly a bug, we will schedule to fix it soon", user: "no worries, glad to help", google (a week or two later): "we're in the process of pushing out a new release, it fixes this bug, let us know how it works out for you" user: "awesome, yes it solves my problem, you can close this issue" google: "users first, that's our motto. consider it closed. be sure to let us know if you find anything else the matter" I don't know why that conversation doesn't exist. It exists for the Calendar API. The Spreadsheet API is more like: user: "hey, I found a bug" --static-- user: "did you see that bug I raised? I put a lot of time into it" --static-- user: "are you guys really there?" --static-- user: "oh well, didn't need the stupid thing fixed anyway" --static-- --static-- --static-- google: "this bug is old now, and we are closing it because it is irrelevant to our undisclosed plans for this product" user (intensely frustrated): "'product' is a bit strong! like I cared these last 9 months anyhow! what makes you think people even use this?" I think they genuinely don't understand that conversation A is the important conversation to be having with your user base. cheers, David. On Wed, Jan 18, 2012 at 1:57 PM, Alistair <[email protected]> wrote: > In the section on retrieving a worksheet-based > feed<http://code.google.com/apis/spreadsheets/data/3.0/developers_guide.html#RetrievingWorksheetFeeds> > of > the developers (protocol) guide, it says that each spreadsheet entry will > have a <link> with rel=" > http://schemas.google.com/spreadsheets/2006#worksheetsfeed"; whose href > should be used to "GET" the worksheet-based feed. > > In all the spreadsheet-based feeds I've tried, and in their own example in > the documentation, there is no such link (try searching the page for it!). > There is a <content> tag whose src attribute looks like a worksheet-based > feed Uri. > > Am I missing something or is the documentation wrong? >
