Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

MSXML Future Roadmap ?

4 views
Skip to first unread message

Daniel Bowen

unread,
Feb 3, 2003, 4:20:13 PM2/3/03
to
SQL Server Development Team [MSFT] wrote:
> Vikram,
>
> Here are the planned future MSXML releases.
>
> MSXML3sp4 will come out with Windows Server 2003
> MSXML3sp5 will be part Yukon
> MSXML4sp2 will come out spring 2003
> MSXML50 is part of Office 11.
> MSXML60 will be part of Longhorn slated for 2004
>
> Our plan is to phase out the native development and you should plan on
> switching to .Net Framework as MSXML60 will be the last version of MSXMLs.
>
> Thanks,
> Umut Alev
...
>>Can anyone from Microsoft let us know if Microsoft plans to continue
>>update the MSXML software in future ?


I was about to ask the same question. Thanks for the response!

Its disappointing to hear that MSXML60 will be the last. A real-time
application that I'm involved with is actually using MSXML, and will
likely never be using the .Net framework. MSXML has always performed
very well, and is very well designed.

I have a couple of questions.

Will a beta of MSXML50 be included with the Office 11 beta (or
separately near the same time)?

Would it be possible to share any goals for MSXML50 (or MSXML60)?

DOM Level 2 has been a recommendation for sometime, but unfortunately,
MSXML 4 didn't have full DOM Level 2 support (even though MSXML 4 was
released a year after DOM L2 was a recommendation). Will we see it in
MSXML50?

DOM Level 3 is close to being a recommendation. Will there be DOM Level
3 related things in MSXML50? (I'm especially interested in DOM Level 3
Validation).

How soon before the release of MSXML50 would DOM Level 3 have to be a
recommendation for MSXML50 to implement it? XSLT 2.0? XPath 2.0? XML
Schema 1.1? XML 1.1?

Thanks!
-Daniel

SQL Server Development Team [MSFT]

unread,
Feb 5, 2003, 2:23:24 PM2/5/03
to
see my comments inline
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.
"Daniel Bowen" <dbow...@no.spam.com> wrote in message
news:e4jI#n8yCHA.640@TK2MSFTNGP12...

> SQL Server Development Team [MSFT] wrote:
> > Vikram,
> >
> > Here are the planned future MSXML releases.
> >
> > MSXML3sp4 will come out with Windows Server 2003
> > MSXML3sp5 will be part Yukon
> > MSXML4sp2 will come out spring 2003
> > MSXML50 is part of Office 11.
> > MSXML60 will be part of Longhorn slated for 2004
> >
> > Our plan is to phase out the native development and you should plan on
> > switching to .Net Framework as MSXML60 will be the last version of
MSXMLs.
> >
> > Thanks,
> > Umut Alev
> ...
> >>Can anyone from Microsoft let us know if Microsoft plans to continue
> >>update the MSXML software in future ?
>
>
> I was about to ask the same question. Thanks for the response!
>
> Its disappointing to hear that MSXML60 will be the last. A real-time
> application that I'm involved with is actually using MSXML, and will
> likely never be using the .Net framework. MSXML has always performed
> very well, and is very well designed.
[umut] I am pleased to here that you like MSXML but on the other hand .Net
Framework is the future and in time their perf will be better also. If there
is continued customer demand for native xml support then we may reconsider
our decision for future MSXML releases.

>
> I have a couple of questions.
>
> Will a beta of MSXML50 be included with the Office 11 beta (or
> separately near the same time)?

[umut] MSXML50 will ship with Office 11 nowhere else. So MSXML50 will be
part of Office 11 Beta.

>
> Would it be possible to share any goals for MSXML50 (or MSXML60)?

[umut] MSXML50 and MSXML60 are improvements on MSXML40. MSXML50/60 have
better validation engine, inline-schemas, XML Digitial Signatures support,
lots of bug fixes. Also MSXML60 will have XSD errata fixes.

>
> DOM Level 2 has been a recommendation for sometime, but unfortunately,
> MSXML 4 didn't have full DOM Level 2 support (even though MSXML 4 was
> released a year after DOM L2 was a recommendation). Will we see it in
> MSXML50?

[umut] Nope, no changes to DOM. It is still the same and DOM L2 will not be
implemented.

>
> DOM Level 3 is close to being a recommendation. Will there be DOM Level
> 3 related things in MSXML50? (I'm especially interested in DOM Level 3
> Validation).

[umut] Samething DOM Level updates. Sorry.

>
> How soon before the release of MSXML50 would DOM Level 3 have to be a
> recommendation for MSXML50 to implement it? XSLT 2.0? XPath 2.0? XML
> Schema 1.1? XML 1.1?

[umut] Again MSXML has no plans to implement new features: XSLT 2.0, XPath
2.0. For XML 1.1 and XSD 1.1 we are still thinking about it.

>
> Thanks!
> -Daniel
>


Daniel Bowen

unread,
Feb 5, 2003, 8:01:13 PM2/5/03
to
Thank you very much for the feedback! See my comments inline


> [umut] I am pleased to here that you like MSXML but on the other hand .Net
> Framework is the future and in time their perf will be better also. If there
> is continued customer demand for native xml support then we may reconsider
> our decision for future MSXML releases.

I guess it was bound to happen :-( I'm not sure how you will measure
customer demand, or what it would take to reconsider.

> [umut] MSXML50 will ship with Office 11 nowhere else. So MSXML50 will be
> part of Office 11 Beta.

So will MSXML50 *not* be a stand-alone deliverable/download like MSXML
has always been? Will it *not* be redistributable? Is it a beta of
MSXML50 that comes with Office 11 Beta, or is it an RTM/RTW version of
MSXML50?

> [umut] MSXML50 and MSXML60 are improvements on MSXML40. MSXML50/60 have
> better validation engine, inline-schemas, XML Digitial Signatures support,
> lots of bug fixes. Also MSXML60 will have XSD errata fixes.

Thanks. I'll probably think of lot's more later, but here's 2 quick
questions:
1. Will there be anything to help validate proposed changes to a DOM
without modifying the DOM and validating the whole DOM? Such as
"canAppendChild", "canInsertBefore", "canSetAttribute"?
2. Will you be able to load using the res: protocol with "NewParser" set
to true (i.e., will it handle asynchronous download)?


>>DOM Level 2 has been a recommendation for sometime, but unfortunately,
>>MSXML 4 didn't have full DOM Level 2 support (even though MSXML 4 was
>>released a year after DOM L2 was a recommendation). Will we see it in
>>MSXML50?
>
> [umut] Nope, no changes to DOM. It is still the same and DOM L2 will not be
> implemented.
>
>
>>DOM Level 3 is close to being a recommendation. Will there be DOM Level
>>3 related things in MSXML50? (I'm especially interested in DOM Level 3
>>Validation).
>
>
> [umut] Samething DOM Level updates. Sorry.

...


> [umut] Again MSXML has no plans to implement new features: XSLT 2.0, XPath
> 2.0. For XML 1.1 and XSD 1.1 we are still thinking about it.

That's quite depressing, but I guess that's the way it is. I've been
telling others to just wait for the next release of MSXML for things
like this (especially DOM support), but now it seems that hope is in vain.

I've been using and advocating the use of MSXML since 1999. I waited
patiently for MSXML 3.0. I looked forward with anticipation to MSXML
4.0. It's sad to see MSXML being marginalized for the future.


Thanks for the feedback. I appreciate your response.

-Daniel

0 new messages