From: Mike R. <mik...@gm...> - 2005-09-27 15:51:24
|
On 9/27/05, Owen Rogers <exo...@gm...> wrote: > i'm also curious as to why people might choose > netreflector over the default xml serialisation support in the .net > framework. I'm going to jump in here. Joe Walnes has had great success with the XStream project as a new (simple) way of thinking about (de)serializing XML. I think there's an opportunity to do the same kind of thing with NetReflector (noting that there is already an XStream .NET although I don't know what its status is. > i agree; however, unfortunately the format of the xml that > netreflector can parse does not lend itself well to generating > schemas. eg. netreflector doesn't distinguish between attributes and > simple elements, and it uses attributes (such as type) to support > polymorphic types. Would it be possible to define a 'canonical' format for NetReflector XML ? That way people could at least use a generated schema for intellisense. I'm not suggesting that NetReflector itself validates XML using the schema since it itself should allow something less stringent. > but i'm worried about the configuration > changes that this might entail > and how this could affect our userbase How hard would it be to write some XSL to convert for them.? I'm not an XSL expert so don't really know myself |