i'm quite frankly very excited about xpath and .net2. but i'm not sure how far MS has gone to actually support xpath2 in .net 2.0. has anyone got any idea about those two?
i read that xquery has been dropped entirely; it being a subset of xpath, i couldn't quite believe that, especially since sql2005 will have a new datatype of XML, which can be queried into very nicely (apparently), to retrieve fragments, single elements or
entire trees.
again, have you guys any insights on this?
thanks a lot.
-
Follow
Oops, something didn't work.
Sign In to be begin to follow this thread
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.Getting "follow" information
Start following this thread
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.Removing your "follow"
Setting up your "follow"
Did you know you can
sign up for email notifications?
-
hardball
Let's Go
-
littleguru
<3 Seattle
I think that dropping XQuery 1.0 in .NET 2.0 was a big mistake.
Perhaps they dropped it because it is still a working draft and no official standard. -
Sven Groot
Don't worry... I'm a doctor.
They did drop it because it's still a Working Draft, and imho they made the right decision. Although XQuery is a great technology, history has shown that implementing a working draft is not good when you need to provide backwards compatibility later on. Just look at the mess with the XSL-WD implementation vs. the real XSLT implementation that came later.
-
draza
Bring It On
If memory serves me correctly...
- they dropped XQuery support as the standard is not yet finalized and won't be in the time frame of Visual Studio 2005
- however, they kept a subset of it that most likely won't change and implemented it in the SQL Server 2005
- what they (Microsoft) most likely dropped in general - not just for 2.0 - (if I understood correctly) is XPath 2.0 in favor of XQuery because the syntax of XQuery is supposedly a lot more natural to the majority of developers
Personally, I have had bad experiences with Microsoft's earlier attempts to implement not-yet-finalized specification (XML Data Reduced, anyone?) so I'm glad that they decided to wait for the final spec this time.
-
W3bbo
Work hard; increase production; prevent accidents, and be happy.
But what about CSS2.1 and IE7?
The CSS2.1 spec won't be finalised until after (or around) IE7's release. Although most of the standard is stable, I don't think this should be an excuse not to support it. After all, all the other browsers out there do. -
Sven Groot
Don't worry... I'm a doctor.
W3bbo wrote:After all, all the other browsers out there do.
If one lemming jumps of the cliff... -
littleguru
<3 Seattle
Sven Groot wrote:They did drop it because it's still a Working Draft, and imho they made the right decision. Although XQuery is a great technology, history has shown that implementing a working draft is not good when you need to provide backwards compatibility later on. Just look at the mess with the XSL-WD implementation vs. the real XSLT implementation that came later.
You are right! -
Tyler Brown
Bullets change governments far surer than votes.
Sven Groot wrote:If one lemming jumps of the cliff...
Then the other lemmings should follow, otherwise people will more than likely make it known that the little lemming should have jumped.
-
PaoloM
Hypermediocrity
I would refuse to implement any standard that is not finalized and ratified. People are going to (I need to watch my language) anyways, so why bother?W3bbo wrote:But what about CSS2.1 and IE7?The CSS2.1 spec won't be finalised until after (or around) IE7's release. Although most of the standard is stable, I don't think this should be an excuse not to support it. After all, all the other browsers out there do. -
PaoloM wrote:
I would refuse to implement any standard that is not finalized and ratified. People are going to (I need to watch my language) anyways, so why bother?
W3bbo wrote: But what about CSS2.1 and IE7?The CSS2.1 spec won't be finalised until after (or around) IE7's release. Although most of the standard is stable, I don't think this should be an excuse not to support it. After all, all the other browsers out there do.
Agreed. And on a somewhat related mater, I hate the W3C. I now declare my manifesto, I will use b, i, u, and center tags forever!
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.