Another XML Team introduction – Stan Kitsis

Hi everyone. I have recently joined the Microsoft XML team as a Program Manager focusing on XML Tools. As such, I am open to all feedback you might have regarding the new XML Editor (VS 2005) and any other XML tools that you would like to see in the future. My pre-Microsoft life includes 8 years of enterprise software development experience with a company called Comshare - an ISV that was specializing in developing corporate performance management applications (Comshare was acquired by Geac in 2003, at which time my career with the company came to an end). I have an MBA from the University of Michigan and an undergraduate degree in Computer Science from Case Western Reserve University. I cannot really compete with professional achievements of people like Michael Champion, Dare Obasanjo, Mark Fussell and Michael Rys. Instead, I thought I'd tell you what I do outside of work. While the list is not big, it includes finishing several marathons and triathlons as well as winning a section of the World Open Chess Championship. I also consume dark chocolate in large quantities 🙂

Well, that's it for now. Wish you all a Happy New Year

Comments (2)
  1. Kent Tegels says:

    Hi Stan,

    Something things we need, IMHO, XML tool-wise:

    a. An XPath Evaulator over the current document that displays the selected nodes in a grid. See XMLSpy 3.x+.

    b. Right-click on a node and get its basic XPath

    c. An XQuery builder (you’d be nice and share that with the Yukon folks, I’m sure…)

    d. A visual Annotated Schema/FOR XML builder

    e. Different styles of schema-by-inference

    BTW, Once you start down the Dark Chocolate path, forever dominate your life it will…

  2. My 5cents:

    I want to be able to extend with managed UITypeEditors and TypeConverters the XML editor. Invent a namespace like the Dataset guys did, and allow extending a schema by adding those attribute, i.e.:

    <xs:element name="connectionString" design:editor="MyNs.MyUITypeEditor, MyAsm">


    And for a converter:

    <xs:element name="connectionString" design:converter="MyNs.MyTypeConverter, MyAsm">


    The behavior of editor/converters should be the same as in the property browser. That way, I can hook with potentially powerful UIs into the XML editing process.

    The value returned from either a TypeConverter or an UITypeEditor should be an XPathNavigator, from which you should be able to get the XML for insertion in the file.

Comments are closed.

Skip to main content