Regarding whether REST is going to replace SOAP:
I think it depends on who you ask. There seem to be a lot of people that prefer to see things in black and white, i.e. either REST or SOAP.
Personally, I have a more gray view on things. :-)
I think that SOAP was originally hyped as being able to solve all sorts of problems. Now that some time has passed, people have understood that this is not the case.
...and long comes the next hype, REST.
I think that there are some areas to which RESTful solutions are better suited and there are other areas in which using more traditional, SOAP based, web services is a better choice. REST has definitely taken a "market share" from SOAP, but I think this is only healthy, since I suspect that share is better served by applying RESTful solutions.
Regarding practical examples of web services: Do you mean situations in which web service solutions can be applied?
If this is the case, then have a look at Amazon and the web services they make available.
Other possible examples are: Credit card services, hotel booking services etc etc.
Today, SOAP is many things, from a syntax to a framework, from an RPC protocol to an abstract, one-way messaging environment. It is difficult to make unequivocal statements about what SOAP is or what it allows. Given this, we cannot even say with confidence whether SOAP and REST are in competition.
William Butler Yeats: All life is a preparation for something that probably will never happen. Unless you make it happen.