W3C Releases Drafts For DOM L2 And More
TobiasSodergren writes "People at W3C seem to have had a busy Friday, according to their website.
They have released no less than 4 working drafts
(Web Ontology Language (OWL) Guide,
the QA Working group - Introduction,
Process and Operational Guidelines,
Specification Guidelines)
and 2 proposed recommendations:
XML-Signature XPath Filter 2.0
and HTML DOM 2.
Does the this mean that one can expect browsers to behave in a predictable manner when
playing around with HTML documents? Hope is the last thing to leave optimistic people, right?"
doesn't matter how many standard that w3c sets, MS is never going to follow them. They'll just set their own standards, and those will become the de facto standards... its rough, but its the ways it is...
www.punkmafia.com
"I am insane, and you are my insanity"
--Bruce Willis, 12 Monkeys
Does the this mean that one can expect browsers to behave in a predictable manner
When there was 1 standard (HTML), browsers didn't behave predictably.
Now there are more, there is more scope for implemetations to have their quirks, not less.
Standards are large and complicated descriptions of expected behaviour. Each implementor may have a slightly different interpretation. Different implementations will have their strengths and weaknesses which make different parts of the standard easier or harder to implement fully and/or correctly. There may even be reasons why an implementor may choose to ignore part of a standard (perhaps it is difficult and he believes that users don't want or need that functionality yet).
Unfortunately, standards are an ideal to aim for, not a description of reality.
Shock horror! Browser released in 1996 fails to support latest web standards!
If you want to bash Netscape, aim at Netscape 6 or 7 (both of which have superb standards compliance thanks to the Mozilla project). Netscape 4 simply isn't relevant any more, and hasn't been for several years. It's only big companies and institutions who don't want the hassle of upgrading their site-wide PCs that are keeping it alive, and with any luck even they will give it up soon.
MSDN clearly marks out which functions are standard to and which version of HTML/DOM they are complying to.
Mozilla is almost de-facto compliant because that's the only thing they have to work from and they don't have an agenda like interoperation with MS Office/Front Page.
Standards compliance does work, it's the lazy/inept authors of web pages that are to blame for faulty product resulting from an ad-hoc approach to web page development.
Then again, like the saying goes: "A bad workman always blames his tools..."
Height: 38U, Weight: 0 Newtons, Eyes: #0000FF, OS: Gray Matter 1.0 (Alpha)