Well I think you have got it wrong. The author tries to explain with the CD example that in OOPS, you have data and the code that processe the data together (fileds and methods in a class) equating this with the example you have a CD and a designated CD player. As opposed to SOA you have generic form of data and the code i.e. a CD (data) that can be played on any player (code).
When I create my CD class, I have CD related data and methods operating on that data. Essentially, I am not binding my CD to a Player!!! I am just exposing an interface for CD players to use!!!
SO IT SEEMS, YOU MISSED THE POINT OF O-O Programming!!! OOPS rightly teaches the Generalization-Specialization mechanism of software development which is in essence the basis for SOA!!!