Here is a little bit of extra information. When I made the xml_archive I considered a number of options. I settled on the simplest implemenation which I thought would be considered acceptable. I also tried to use map xml features such as object id tags to analogous concepts that the serialization library required. This has worked out pretty well in that not too many people have complained that its not enough. I did consider have the serialization library generate a compatible schema when the archive is saved. This might be useful for browsing the archive. I didn't do this, but it's still an interesting idea. I could be implemented by making an new xml_oarchive, by deriving from the existing one or by making a whole new arechive - xml_oschema. Good luck. Robert Ramey "Joseph Fradley" <joe.fradley@fradeng.com> wrote in message news:f7907c850802130934r6e2eff6bm22f37710b324547a@mail.gmail.com... Robert, Fair enough, I'll see if I can make something useful in the amount of time I have. Joe I don't. I guess its up to you. Robert Ramey Joseph Fradley wrote: > Hello, > > I've seen a few postings on how a XSD generating archiver would be > written and a posting for a google code project on it. But I can't > seem to find any implementations. > > Does anybody know of any implementations? > > Joe ------------------------------------------------------------------------------ _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users