I think you can safely omit XML since it has become so ubiquitous you can see it everywhere from configuration files up to the new Word document format. Very hard to get by without getting involved in it in one way or another.
More to your question. After you've been in a field for a while you just know what technologies do come together to form an entire stack or ecosystem. You also know which ones form the basic foundation, which are for advanced classes and which are really cool.
If we take an example of a C# developer:
BASIC: C# goodies, .NET class library, ASP.NET WebForms, Visual Studio, SQL Server
ADVANCED: ASP.NET MVC, jQuery, Entity Framework, nUnit, TFS
TOP: Resharper, nHibernate, IoC, integration testing, application and database performance tuning etc.
Depending on a position and its specific requirements, you omit the obvious which is implied and put the stuff above the defined niveau to distinguish yourself from the others.
Basically it's about understanding the abstraction level of your imaginary opponent and adjusting to it. If an opening speaks about ORM tools, testing and integration, your mentioning of XML would seem like a strange joke.
Listing everything is probably a bad strategy since it could trigger a thought this guy is clueless about priorities or desperate to get any job.
I find it also useful to mention the years I dealt with one or the other technologies. For instance I clearly indicate when I stopped using C++ and moved to applied development so that the folks though can see my background in it but avoid extensive questioning on it.