[xsd-users] Hybrid between XSD and XSD/e - parsing serialisation approach from XSD/e, but feature set and interface of XSD

[Vladimir.Michl at barclayscapital.com]

Hi Boris,

Thank you for your suggestions. At the moment there is need to use XML as format, but get it as quick as possible.

Following features are missing for me from XSD/e:
 - when validation is switched off, there is really not validation at all. XSDe provides at least some so invalid objects are not constructed. This is mainly about extensibility, being able to add new fields without need to recompile all receivers.
 - any and anyAttribute are ignored
 - IDREF no static typing available.
 - optional attributes should be returned as optional type rather then need to ask using XXX_present function.
 - function naming - would have preferred to have java naming available.

Regards

Vladimir

--
Vladimir Michl
Global Technology - FX Cash (BARX, DEVON)
Barclays Capital, 5 The South Colonnade, E14 4BB 
Tel: +44 20313 46373

-----Original Message-----
From: Boris Kolpackov [mailto:boris at codesynthesis.com] 
Sent: 16 June 2011 10:18
To: Michl, Vladimir: IT (LDN)
Cc: xsd-users at codesynthesis.com
Subject: Re: [xsd-users] Hybrid between XSD and XSD/e - parsing serialisation approach from XSD/e, but feature set and interface of XSD

Hi Vladimir,

Vladimir.Michl at barclayscapital.com <Vladimir.Michl at barclayscapital.com> writes:

> What makes XSD slow is that transformation to DOM and then to C++ objects.
> XSD/e on the other side does not have all the features I would require.
> 
> Is there any way to pick best of both from XSD and XSD/e? E.g. The 
> parsing/serialisation approach from XSD/e, but feature set and 
> interface from XSD?

No, unfortunately there is no easy way combine the two.

C++/Hybrid in XSD/e is pretty similar conceptually to C++/Tree in XSD,
especially if C++ exceptions and STL are enabled in XSD/e. What are
the specific features of XSD that are missing in XSD/e and that you
need?

Also, you may want to consider using the binary representation of
the object model. For example, you can use it internally in your
application and export to XML only if/when needed for compatibility
with third party systems. Another alternative would be to have a
"fat" format where both the binary and XML representations are present.
Binary parsing/serialization is about an order of magnitude faster
than XML parsing/serialization. For more information see section
5.2, "Binary Serialization" in the C++/Tree Mapping User Manual:

http://www.codesynthesis.com/projects/xsd/documentation/cxx/tree/manual/#5.2

Boris
_______________________________________________

This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays. Any views or opinions presented are solely those of the author and do not necessarily represent those of Barclays. This e-mail is subject to terms available at the following link: www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the foregoing.  Barclays Capital is the investment banking division of Barclays Bank PLC, a company registered in England (number 1026167) with its registered office at 1 Churchill Place, London, E14 5HP.  This email may relate to or be sent from other members of the Barclays Group.
_______________________________________________