 |
 |
 |
Good day,
We would like to announce a new type of mapping that we have implemented
in xsd (http://codesynthesis.com/products/xsd/).
Instead of providing a conventional DOM-like in-memory data structure,
it offers an event-driven SAX-like parser templates that application
developers can extend to build their own in-memory representations or
perform immediate processing. This should be especially useful in the
following cases:
* Data types for the in-memory representation may already be defined.
It is therefore desirable to use these data types instead of the
ones provided by the mapping.
* The construction of the in-memory representation may not be necessary
or possible. For example, the entire XML instance document could be
too large to fit in memory or the processing needs to be carried out
as soon as parts of the document become available (streaming).
You can view a short guide to our implementation of this mapping here:
http://codesynthesis.com/projects/xsd/documentation/cxx/parser/quick-guide/
We believe it is the only mapping of this kind and would appreciate
any comments you might have.
thanks,
-boris
|
 | 



|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |