Best Practices for Managing Large, Complex XML Schemas (XSDs)

[Frus2000]

I'm working on a project that involves a rather large and complex set of XML Schema Definitions (XSDs). We're talking about dozens of interdependent schema files, with a mix of

Code: Select all

xs:import

and

Code: Select all

xs:include

directives, spanning multiple namespaces. It's becoming a bit of a challenge to manage, especially when making updates or trying to track dependencies.
What are your preferred strategies for structuring your XSD files on disk? Do you use a flat structure, a deep directory hierarchy, or something in between?
When you need to make changes to a core schema, how do you ensure backward compatibility and minimize ripple effects across dependent schemas? Are there any specific tools or methodologies you use beyond just basic validation?
I'm trying to avoid a scenario where a small change in one file breaks half a dozen others in unexpected ways. Any insights, war stories, or recommended resources would be greatly appreciated!

[tavy]

Hello,

I think the best way to handle large structures of XML Schemas is to use Oxygen's main files support. You can read more about this in our user guide:
https://www.oxygenxml.com/doc/versions/ ... ntext.html

If you define the main XSD file in your project, then you will have correct validation of the modules, content completion in the context of the main modules, and you can use searching and refactoring actions to search for components or make changes in the XSD modules.

Oxygen also provides helper views, such as the Component Dependencies view, which allows you to see the dependencies for a selected component, or the Referenced/Dependent Resources view, which displays the hierarchy or dependencies for resources included in an XML Schema.

Here is a video demo where the main file support is explained: https://youtu.be/zZiuM9Fyfrg?si=6ftHufmE7Pt5TliR&t=1955

Best Regards,
Octavian