[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Declarative XML Processing with XQuery


declarative serialization



>From: "Bullard, Claude L (Len)" <len.bullard@i...>
>To: 'Michael Champion' <michael.champion@h...>, 
>xml-dev@l...
>Subject: RE:  Declarative XML Processing with XQuery
>Date: Wed, 9 Nov 2005 10:44:34 -0600
>
>As we used to say, "way cool", or just, frikkin wow.

This was basically the bait that got me to sell my soul to the Dark Side :-) 
(Although nobody talked about what is now called LINQ/XLinq at my interview, 
I could read the tea leaves that somethin' frickkin wow was in the works)

>
>I may have missed it but what does this do with mixed content models?

There are axes that let you iterate over content in a way that sees the 
markup, and those that let you just see the content.
>
>The evolution of the schema-aware features will be fun to watch. I want
>to see that work with the big beasties like GJXML which attempt to
>use naming conventions to force object-orientation.

Thanks for the suggested use case.  Any tool that can help cage that kind of 
beast is bound to generate some interest.

>
>This will make some of our developers quite happy although it is terrifying
>to
>think about how much technology we are about to throw away..

Hmm, like what?   So far the internal developer experience, and my 
experience trying to balance the DOM and XLinq story at PDC, has not 
indicated that very many people look back longingly at the XML technologies 
of the previous centrury :-)  MS does need to have a clear story on how 
XLinq trees can be converted back/forth to DOM trees, how XSLT can be used 
on XLinq trees, etc.  No plans or promises, but I do want to hear about real 
scenarios where we might cause developer pain as people move to or mix/match 
XLinq with other XML technologies.

>
>What will XLinq/DLinq do with XML Binary?  (had to put a troll in
>but actually important to the sensor web community).

That's a serialization, XLinq is a data model.  XLinq shouldn't care whether 
the bits on the wire are XML 1.0, some proprietary binary XML thingie, or an 
eventual EXI standard.  But thanks for the reminder, I'lll try to make sure 
that there's a pluggable reader/writer architecture planned for XLinq (as 
well as SAX/DOM).
>
>I'd like to see an overview of this fit into a web services
>scenario.  I posted a reply to a CNet news article that provides
>an example:  the domain/query aware application (Kris Kringle
>for Windows Movie Maker).

I agree that's an important scenario, do you have a pointer to your C|Net 
reply?

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.