Xml schema versioning strategy

Xml schema versioning strategy

Posted: gater Date: 05.07.2017
xml schema versioning strategy

I often have to design XML schemas for different XML-bases import routines. It is clear that XML schemas will evolve over time or they could contain bugs to be fixed, so it is important to capture the schema's version and to have some mechanism to bind against a specific version.

The schema upgraded and should be considered as preferable but an old one should be also supported.

Versioning XML Schemas – Subbu Allamaraju

When fixing a bug I fix it in the same namespace but if I'm about to upgrade a schema then I need to create a new namespace but with upgrade month added:. This is such a difficult subject that it's not even funny, and one that I have spent years providing consultancy support for.

There are many best practices out there, but a most of them do not work in all situations. For example, many advocate the use of "xsd: By posting your answer, you agree to the privacy policy and terms of service.

By subscribing, you agree to the privacy policy and terms of service. Stack Overflow Questions Developer Jobs Documentation beta Tags Users. Sign up or log in to customize your list.

XML Schema Versioning Use Cases

Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us.

Log In Sign Up. Join the Stack Overflow Community. Stack Overflow is a community of 7.

Schema Versioning Strategy - eBay Trading API

Join them; it only takes a minute: What are the best practices for versioning XML schemas? Currently I have two scenarios: The bug is found within the schema and all schema instances must comply with the fixed version. Finally I came up with storing version information within the namespace of schema: Lott k 56 Regent 4, 3 22 Here are some tips for you if you're getting started: Do not put a minor version number, micro version number, date, or anything else of the sort, into your namespace.

xml schema versioning strategy

Every time you change the namespace, you will break all processing applications. Do put a "version" attribute in the XML instance document.

That will enable a processing application or a version adapter service to figure out what it is processing. Do specify a policy of what constitutes a backwards compatible change, for example: Christian 51 1 1.

Sign up or log in StackExchange. Sign up using Facebook. Sign up using Email and Password.

xml schema versioning strategy

Post as a guest Name. In it, you'll get: The week's top questions and answers Important community announcements Questions that need answers. Stack Overflow works best with JavaScript enabled.

Sooo, maybe we should just put information about version in comment? MathOverflow Mathematics Cross Validated stats Theoretical Computer Science Physics Chemistry Biology Computer Science Philosophy more 3. Meta Stack Exchange Stack Apps Area 51 Stack Overflow Talent.

Rating 4,7 stars - 976 reviews
inserted by FC2 system