I could be inclined to go with this. If APP collections feeds and subscription feeds were completely separate entities, it wouldn't be so much of a problem, but as my own implementation of the spec demonstrates, there will be times in with the collection feed and subscription feed are one and the same. Looking at our implementation and the semantics of Feed History, I realize that we can't implement it precisely because of this issue.
Care to write up a pace? - James Andreas Sewe wrote: >[snip] > Hence I urge you to change the directionality of "next"/"previous" > within the APP. > > Regards, > > Andreas Sewe > >
