it would make sense to add the xcri-cap to the api as its essentially the same thing so no need for its own controller
add controller functions to generate the xcri-cap feed
add a function to our API model to retrieve and format a programme for the xcri-cap feed
we dont need this anymore since we're grabbing the xcri feed via the API
add a function to be able to trim ids from individual field names
modify xcri-cap URL so that its under the api too
a lot of formatting to the xcri-cap views, mostly to get it to validate
cope with four digit ids
update the tests to reflect changes made
test edge cases
fix some more validator issues with the famous <![CDATA[...]]>
html_entity_decode seems to be causing some character issues on the server, i've removed it
move the cache from the output cache directory so that it doesnt have to re-generate each time the output caches are cleared
if we don't have a cache, then 404, instead of generating the feed from scratch
turn the xcri-cap generating function into a controller action so we can route to it directly
Merge pull request #280 from unikent/feature/xcri-cap

the XCRI-CAP!!!