 |
|
|
Is anyone aware of an advanced XML(/XSD) editor that has refactoring
features aka. the ones known for ex. Java. They could be:
* refactoring logical layout. Between the diffent forms: Russian Doll,
Salami slice, Garden of Eden etc.
* refactoring physical layout. From schema modules to a flattend schema.
* namespaces. Changing prefix's over several modules, and or namespaces
URI's.
* naming. Element, attribute and types.
I am aware that some of these could be done by using some sort of 'replace',
but I often work with several schema modules with the same namespace. Also
XSL could/can do the job, but I would love to see it integrated in an
Editor, ex. as a plugin for Eclipse.
Also I would like to know of any tools for doing a logical comparison om
XSD's, like a XSD-diff, to be used in analysing diffent version of the same
schema.
---
Brian Nielsen
IT-Strategic Division
bni@i... <mailto:bni@i...>
33 379 134 (direkte)
25 67 07 45 (mobil)
National IT and Telecom Agency
Holsteinsgade 63
DK-2100 København Ø
Telf. +45 35 45 00 00
Fax. +45 35 45 00 10
<http://www.itst.dk>
itst@i... <mailto:itst@i...>
|
|
| |
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.
| |
| |
|
|
|
