In .NET 3.5 the System.Xml.Linq assembly was introduced, adding a new set of classes for constructing XML, as well as extensions for querying XML using LINQ. The term LINQ To XML was coined and has since referred to both aforementioned tasks. While the name LINQ To XML makes perfect sense for the act of writing a LINQ statement against an XML source, the name has little application for the act of building an XML tree using the new API. For the sake of explicitness, I’d like to see a name that could be given to the group of “X Classes” within the System.Xml.Linq namespace (aka the XSpace) that could eliminate any ambiguity when differentiating between it and the actual use of LINQ To XML.
I was pondering over the name XPI (XML programming interface). It seems to make sense on a few different levels:
- It is indeed a programming interface for XML…
- Every class within the API is prefixed with “X”, hence it isn’t an API but rather an XPI…
- It’s an acronym and we all know that we need more of those…
This probably isn’t the best name in the world, but it certainly has a nice ring to it…
- “So I was out the other night, minding my own business, and all of a sudden this dude gets up in my grill questioning my XPI skills and I was like what?!?!”
- “I knew I liked the girl after she admitted her fixation with 80’s hair metal, but it wasn’t until she told me she was into XPI that I realized I loved her!!!”
- “I’ll take .NET 3.5 XML programming interfaces for 300 hundred Alex” - Contestant
“This XML programming interface was introduced in .NET 3.5 and is pretty freakin sweet.” - Alex
“What is XPI Alex?” - Apparently cool contestant
Need I say more? If you don’t believe me, don’t take my word for it…
