Below are the new features of TOGAF 9. The bolded text is what was provided by the Open Group. The regular text is my commentary on it.
Modular structure – I am a firm believer that enterprise processes are modular pieces that should be orchestrated based on the specific set of concerns. It is good to see that TOGAF feels the same way.
Promotes greater usability & encourages incremental adoption – This is somewhat lofty and subject largely to implementation details. I do agree that the guidance provided does promote reusability. This is reinforced with the first bullet on the modular structure.
Supports evolutionary release management -
Content framework – This is a significant step in the right direction. The content framework provides architects with a map of information that is needed. From what I have seen so far there isn’t a great amount of detail here. But I am sure there is more to come.
Extended guidance on using TOGAF – The TOGAF book was expanded greatly with new guidance that extends the base concepts of TOGAF and supports new features.
Explicit consideration of architectural styles – In the guidance there are linkages between the TOGAF ADM and Service Oriented Architecture (SOA). I am hoping that this isn’t a tight coupling. If you are interested in my thoughts on architectural styles I wrote a post on this not too long ago. See the post What is an Architecture Style?  
SOA and Security – This could be interesting. But only if done right. The Open Group needs to be careful at balancing out too much in the developer details (what OASIS & W3C provides) and high level / nebulous guidance (Analyst firms) that isn’t actionable. What could be of great value is if the Open Group embarked on true architectural patterns and styles that would aid SOA and EA architects on choosing the right architectural strategies.
Further detail added to the Architecture Development Method (ADM)