All tags can now have a class, but you have to declare it in the ini file. The "class" is a bit misleading here, it is more general than a css class style.
So you need to define the classes in the ini file, then create a template where you use this class (and add it to the override.ini.append). In your template you can do many things with the class value. The straight forward thing is to associate it with a css class style, but you are not limited to that. You can also modify the template for the xml element and use a switch to do whatever you want based on its value.
It is a little misleading. Since the doco mentions that the class is let through to the template as {$classification} maybe the tag should be called 'classification' instead of 'class'.
I've opted for the custom tag approach. All i needed was a way of applying some css to a paragraph. None of the current tags supported by ezxml tackle this.
Was there a reason to exclude the <p> tag from ezxml?
I know paragraphs are there by default but i can't use another tag as it carries some form of formatting with it (<strong><em> etc). I could use <table> but it is overkill just to wrap some text up and would confuse users building with it.