Why standardization is necessary

TalkBack 1 of 25:

Next »

• Thread View
• Flat View

Standards first

A few items. While providing functionality above and beyond a standard is nice, the main complaint is that many people are picking and choosing what parts of a standard to implement instead of tackling the entire standard before implementing extras.

You Xerces versus JAXP example is a bit strange. First off, it is not the DOM standard that is to be blamed for this. The DOM standard is what allows different programs (in this case XML parsers) to interface with XML documents. This doesn't control all the methods that Xerces and JAXP happen to expose. Either they aren't really standards compliant or the function that you were using wasn't in the standard.

The main point of standards versus standardization is competition/replaceability. If everyone is working toward the standard then more tool-kits (dare I say "ecosystem") will be available for use. Instead, if you standardize on one tool-kit's implementation then you're stuck.

Posted by: Robert Crocker   Posted on: 02/10/06 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• Virtualization: Architectural Considerations And Other Evaluation Criteria VMware Of the many approaches to x86 systems virtualization available in the ... Download Now
• The True Costs of Virtual Server Solutions VMware In an economic environment that is repeatedly heralding the message "do ... Download Now
• VMware Infrastructure: A Guide to Bottom-Line Benefits VMware Frustrated by the costs of maintain ever larger data centers?or building ... Download Now