JD_Toims - 6:05 pm on Aug 23, 2013 (gmt 0)
Personally, I think in this type of situation I might let the pagination be indexed rather than trying to associate the separate pages all with one URL and then use pushState() to change the URL displayed to the corresponding fragment of the main page so any links or bookmarks take visitors there rather than the pagination.
So, basically I'm saying I think I'd consider:
1.) Paginate and let the SEs index the separate pages.
2.) Set up all paginated pages to "lazy load" the next and previous content so if a visitor "landed in the middle" of a set of pages they could still have the same experience they would have if they navigated to that content via the "main page".
3.) "Mask" the paginated URL as the main URL with a corresponding "identifier" using pushState() [EG /the-section/the-info/27 would show as /the-section/the-info#27] so visitors land on the correct location next time they visit or if they link, etc.
4.) Make sure I used rel=prev, rel=next and rel=start on the pagination.
5.) I might even run rel=canonical href=http://www.example.com/the-section/the-info#27 on the http://www.example.com/the-section/the-info/27 locations in one section to test and see what the SEs did with it.