You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a fair amount of brittle book keeping required to track the location of schemas and resolve them at run-time. An alternative approach involves embedding the schemas into the source (e.g. xxd -i schema.xsd), then at run-time passing those buffers to the xml validator.
Is that a feature that may be valuable to the broader community? If so, is it a feature that replaces the existing schema path machinery, or, does that path based machinery enable a valuable use case that I'm ignorant to? If so, it probably makes sense to maintain the existing schema paths for backwards compatibility.
The text was updated successfully, but these errors were encountered:
Yes, the schema-path machinery is a bit complicated; I like the idea of embedding a schema! But this probably needs to get run through "the process" (although I'm not sure exactly what that might be) as an enhancement.
This probably isn't possible in a standard way unless/until std::embed/#embed is accepted.
There's a fair amount of brittle book keeping required to track the location of schemas and resolve them at run-time. An alternative approach involves embedding the schemas into the source (e.g.
xxd -i schema.xsd
), then at run-time passing those buffers to the xml validator.Is that a feature that may be valuable to the broader community?
If so, is it a feature that replaces the existing schema path machinery, or, does that path based machinery enable a valuable use case that I'm ignorant to?If so, it probably makes sense to maintain the existing schema paths for backwards compatibility.The text was updated successfully, but these errors were encountered: