Lists Home |
Date Index |
- To: Rick Jelliffe <firstname.lastname@example.org>
- Subject: Re: [xml-dev] Restrictions on existence of attributes?
- From: Michael Champion <email@example.com>
- Date: Mon, 03 Jul 2006 00:36:19 -0700
- Cc: firstname.lastname@example.org
- In-reply-to: <44A77AB7.email@example.com>
- References: <7C80003DF5F4D640840D0D37250C143E01A1035F@RED-MSG-70.redmond.corp.microsoft.com> <44A303FA.firstname.lastname@example.org> <44A34133.email@example.com> <44A37EC7.firstname.lastname@example.org> <44A49A67.email@example.com> <44A4DCEB.firstname.lastname@example.org> <7C80003DF5F4D640840D0D37250C143E2327D7@RED-MSG-70.redmond.corp.microsoft.com> <44A77AB7.email@example.com>
- User-agent: Thunderbird 126.96.36.199 (Windows/20060516)
Rick Jelliffe wrote:
> Stan Kitsis wrote:
>> In my experience API-level support is an order (or two) of magnitude
>> more expensive than delivering UI apps. First of all, the testing
>> costs are much higher. Second (and way more significant), once we
>> realease an API, we will have to support it for 10 years or so - and
>> this is extremely expensive.
> I hadn't heard that applications with User Interfaces were so cheap
> and easy to deliver.
Note that Stan stressed the second point, that Microsoft shipped APIs
have to be supported more or less forever, so the up front test costs
are enormous. If we're talking about RNG, I can very easily see the
costs in the multiple millions of dollars -- for test case writing,
implementation on .NET and native platforms,stress testing, performance
tuning, extensive security scrutiny, integration with the rest of the
stack, documentation for mainstream audiences, and so on. Reasonable
people inside and outside MS disagree on whether this is an appropriate
commitment to quality / security / customer value or process overkill,
but it's the world that Stan and I live in. For better or worse, that
cost has to be balanced against both the actual customer benefit from
supporting yet another XML technology, and the opportunity cost of not
investing the resources in something that people really are clamoring for.
> And I think customers would respond positively to MS and other
> vendors supporting ISO Schematron, because it both fills a common and
> constant need and because it increasingly is being adopted in
> government and industry standards. Schematron is moving from being the
> secret weapon of system developers, such as freight companies and
> legal publishers, to being the way that organizations and consortia
> who are serious about interoperability specify executable constraints
> with user-focused diagnostics.
I agree with all these points. I encourage people who hit the wall
with XSD in the Microsoft environment to try out Schematron constraints,
use the reference XSLT implementation, and see if that works for them.