Support for xs:redefine

[dyedgreen]

I think a schema which redefines an existing schema using xs:redefine is currently not supported.

A simple sample schema might look something like this:

<xs:schema
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns="foo"
    targetNamespace="foo"
    elementFormDefault="qualified"
    attributeFormDefault="unqualified"
>
	<xs:redefine schemaLocation="initial_schema.xsd">
		<xs:simpleType name="bar">
			<xs:restriction base="bar">
				<xs:enumeration value="80">
					<xs:annotation>
						<xs:documentation>…</xs:documentation>
					</xs:annotation>
				</xs:enumeration>
			</xs:restriction>
		</xs:simpleType>
    …
    </xs:redefine>
</xs:schema>

Would there be interest in supporting this (and if so are outside PRs welcome for features like this)?

[Bergmann89]

Hey @dyedgreen

I think a schema which redefines an existing schema using xs:redefine is currently not supported.

Correct - there hasn’t been a use case for it until now.

Would there be interest in supporting this (and if so are outside PRs welcome for features like this)?

Absolutely. Contributions are also welcome if you’re up for creating a PR. Let’s just clarify upfront who will take it on to avoid any confusion later. It should be fairly straightforward to extend the existing interpreter logic to generate the appropriate type from the xs:redefine content and overwrite the existing definitions. So what do you think, would you give it a try?

[dyedgreen]

I'm happy to give it a try (although I might not get to it until next week)

[dyedgreen]

Related question: what's the general plan for releasing a new version to crates.io?

I'd be keen to get a new release after adding support for this so I can consume the updated version via crates.io rather than having to depend on a GitHub rev. 😅

[Bergmann89]

The new release was originally planned for this week. I kept delaying it because new improvements and fixes kept coming in. I'm still finishing another task, and once that’s done, I’d like to ship the release. If you’re really quick, we can still include it, but I also don’t see any issue with publishing another release by the end of December once your PR is ready :)