ADE doesn't use CFI's per se for storing annotations and reading positions - but it's really close: instead of specifying the spine item by xpath it does it by name, however the rest of the ADE location is an xpath in CFI style. So if you have the .opf file for the book, it is a trivial transformation between ADE style locations and a CFI.
Note1: the reason for the two styles is that the ADE method predates, and informed, the CFI spec.
Note2: this also means that most RMSDK based readers will be using the same location strings at least internally for positioning, although there may be no file system way of getting those locations.
Note3: RMSDK 9.3.1 also added direct support for CFIs, if the vendor chooses to use it.
Last edited by Jim Lester; 10-28-2012 at 11:56 AM.