T
Tony Lavinio
Dear comp.text.xml community,
Microsoft recently announced that they are dropping XQuery from
their next release of the .NET Framework, 2.0 (Whidbey). Since
Microsoft ships .NET Framework only every 3 or so years, cutting
XQuery from Whidbey means that the next opportunity for XQuery
to find its way into .NET Framework won't be until around 2009,
and even then it's far from a sure thing. That's why it's so
important that the community of XQuery developers makes XQuery a
priority for Microsoft.
Stylus Studio believes that XQuery's has broader applicability
then just an XML querying language but is also an important
mid-tier data integration and Web service enabling technology,
and therefore should not be dropped from the Microsoft .NET 2.0
Framework. Many Microsoft MVP's agree and Stylus Studio is
asking for any developer who shares this vision and to sign the
petition online at: http://www.stylusstudio.com/xqueryforall/
Microsoft recently announced that they are dropping XQuery from
their next release of the .NET Framework, 2.0 (Whidbey). Since
Microsoft ships .NET Framework only every 3 or so years, cutting
XQuery from Whidbey means that the next opportunity for XQuery
to find its way into .NET Framework won't be until around 2009,
and even then it's far from a sure thing. That's why it's so
important that the community of XQuery developers makes XQuery a
priority for Microsoft.
Stylus Studio believes that XQuery's has broader applicability
then just an XML querying language but is also an important
mid-tier data integration and Web service enabling technology,
and therefore should not be dropped from the Microsoft .NET 2.0
Framework. Many Microsoft MVP's agree and Stylus Studio is
asking for any developer who shares this vision and to sign the
petition online at: http://www.stylusstudio.com/xqueryforall/