Skip to main content

Cliff Schmidt

Cliff Schmidt manages standards and open source strategy for BEA's WebLogic Workshop product. Through the Java Community Process and other standards organizations, he ensures that the Workshop product complies with existing standards and advances future standards. He has also participated in standards working groups at OASIS and the World Wide Web Consortium, such as the XML Schema Working Group. In addition to working with standards organizations, he is responsible for BEA's relationship with open source communities, including code contributions and ongoing developer involvement. Prior to working at BEA, he managed the XML standards strategy for Microsoft's MSXML, SQLXML, and .NET XML products. He has been working in the software industry since 1987, with the exception of serving six years as a submarine officer for the US Navy.

 

cliff's blog

The Warm and Fuzzy JavaOne

Posted by cliff on June 29, 2005 at 3:15 AM PDT

"Every person here is special." -- John Gage, Chief Researcher of the Science Office, Sun Micrososystems



"Java Loves You!" -- oversized walking coffee mug outside convention center



Aside from the nice warm fuzzy feelings from these and other statements made during the first day at JavaOne, Sun also announced that they have made up with IBM.

Apache Beehive, XMLBeans and Open Source Strategy

Posted by cliff on September 17, 2004 at 1:36 AM PDT

So I've learned that I'm not so good at keeping a blog going, which is surprising since, in person, I can ramble on quite a bit: see an example of my rambling in a recent interview for TheServerSide linked from http://www.theserverside.com/news/thread.tss?thread_id=28806.

What do Customers Mean by "Standards"? (the 6 W's of Standards)

Posted by cliff on August 12, 2003 at 3:05 AM PDT

When an ISV tries to sell a new piece of software, they are likely to be asked whether the product is based on "standards". I'd like to explore what qualifies as a standard in a customer's mind. To do this, I'll answer the Who, What, Where, When, Why, and How of standards as concisely as possible (although, not in that order).