Good idea... IF UML knowledge is a UML requirement.
I find when conducting job interviews that it is better to know what concepts you wish to talk about, but to also be flexible. For instance, perhaps the person I am interviewing does not know UML, but understands OOP very well. With rigid questions, all I will find out is that s/he knows OOP, but can't draw a UML diagram.
If I am more flexible in my discussion with them, I might ask more questions about their knowledge of OOP principles, and perhaps find that they were a contributing developer for a PEAR project. At that point, if he doesn't know UML, I'd still hire him, and simply request that he get up to speed on UML diagrams. Your questionaire is nice, but it doesn't allow for such flexibility.
I don't believe interviews should be like tests. I believe they should be a means to really get to know the person, find out how they interact with others, what their passions are, what their depth of knowledge is in their areas of expertise, etc. The best answer I could get from an interviewee is "I don't know it well, but I know where to find the answer. If they offer a training class, I'd be happy to take it and become more proficient."
But that's just me. Everyone has different ways of interviewing, and different needs to be met.