[
Lists Home |
Date Index |
Thread Index
]
No one is blaming Microsoft. I am saying "it is your
problem". I am not saying "go your own way", and
yes, being the gorilla, you will always be perceived
with fear and loathing. That came with success.
Don't let that part bother you.
You belong to the W3C. Many of us don't.
We use your products. You chose the W3C to design
your specifications. Namespaces are hard to apply
and painful to learn. What to do?
If the answer is, "you'll have to read the specs and
understand namespaces completely, or .Net won't
work properly", it is pretty obviously a problem,
because they are not only hard to understand,
the specs are inconsistent and contradictory.
If reading the specs isn't required, and the
tools don't reveal the problems or just die with
an anonymous error message, then when the
software refuses to work as expected, the user
blames Microsoft.
It's not your fault. It is your problem. Big diff.
You wanted to know if this was mere philosophy.
It isn't. It's complexity. Tools are made
to handle complexity. So one approach to your
problem will be to hide that complexity beneath
the tools. Selecting to be a member of the W3C
means you accept that responsibility.
I think Amy gave you almost a cookbook list
of the kinds of problems that have to be solved
or hidden.
len
-----Original Message-----
From: Dare Obasanjo [mailto:dareo@microsoft.com]
I'm not sure I understand where you got the notion that I expect our users to read specs. My response quoting the XML infoset REC was part of making an argument that our users aren't the target audience of the REC.
As for the rest of your post and another of your mails, you imply that Microsoft should be going it's own way instead of following the W3C recommendations. Unfortunately, we do not have that luxury as an industry leader. I can just imagine the flak that'll come down when the "Microsoft To Ignore W3C And Go All Proprietary For XML" headlines start to circle the 'net.
We participate in the working groups and we try to encourage them to come up with solutions that satisfy our users. Sometimes they do, and sometimes they don't. However we do not control the W3C or the working groups we sit on regardless of how comforting it is to blame the complexity of W3C XML Schema (for example) on Microsoft[0]
[0] http://www.kuro5hin.org/story/2002/8/16/121422/461#aaronxsd
|
