[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Dangers of De Facto (WAS RE: Dangers of Subsetting?)
Let me give you an example of why "de facto" may not be good enough. Here are two statements from a real Request for Proposal: "Solutions that use Internet technology will be considered." Followed later in the same document by: "The ... plan for (a named agency) provides for a deployment that allows for the improvement of departmental systems and for access to the Internet. The planned direction for information system provides for an architectural plan as defined by the following elements: o Open Systems (ISO/OSI) standards " See the problem. We can't even mention the use of XML in a response to this. The W3C isn't anywhere in this considered a standards org. No, we can't explain it to them either. This is formal contracting, not and RFI (request of information). They did this deliberately. We can mention ISO HTML (not W3C XHTML or HTML). Do we like it? Heck no. We provide XML for lots of good reasons, but not to this customer. De facto is fine for developing technology but too often, not for selling it. Len Bullard clbullar@i... http://www.mp3.com/LenBullard Ekam sat.h, Vipraah bahudhaa vadanti. Daamyata. Datta. Dayadhvam.h -----Original Message----- From: Rob Lugt [mailto:roblugt@e...] I believe that XML 1.0 needs to be treated as a de-facto standard.
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|