Cart
[Home] [By Thread] [By Date] [Recent Entries]
I get the A product usually but only after asking questions say on XML-Dev. As you say, education. The harder problem for example in schema products was figuring out if the content was valid or invalid and the tool did or did not support the feature. We have to expect tool churning and understand it holds back work. For Thralls, the adoption curve includes the learning curve, but until we can get into the reliable product curve we don't have a business. What keeps me awake at night isn't XML. It is applications of XML. Len http://www.mp3.com/LenBullard Ekam sat.h, Vipraah bahudhaa vadanti. Daamyata. Datta. Dayadhvam.h -----Original Message----- From: Nicolas LEHUEN [mailto:nicolas.lehuen@u...] The problem is when you have a developer that produces malformed content, then compares development tool A and development tool B to decide which one he'll buy. Development tool A, being more strict, rejects the developer's content. Development tool B does not. So the developer buys the B product. This is a phenomenon that keeps marketers and product managers awake at night. Maybe the solution is to educate the developer himself ?
|
