RE: [xml-dev] Proper way to use redefine in an hierarchichal set of schemas

["Michael Kay" <mike@saxonica.com>]

xmlschema-dev is a better place for such questions.

 

The spec says that xsd:redefine is pervasive: i.e. if anyone redefines X, then everyone gets the redefined version. It's not very clear how this is supposed to work in practice, but I would think a likely strategy is that as soon as someone starts using the schema e.g. for validation, then further modifications to it using xs:redefine are blocked.

 

In practice the results are likely to vary between implementations. The Saxon schema processor still has more work to do in this area: you can get into inconsistent states for example by importing a schema into an XSLT stylesheet and then using a redefined version of the same schema for validating the instance document.

 

Michael Kay

http://www.saxonica.com/

---

From: Marty Burns [mailto:burnsmarty@comcast.net]
Sent: 06 May 2005 13:20
To: xml-dev@lists.xml.org
Subject: [xml-dev] Proper way to use redefine in an hierarchichal set of schemas

All,

 

I am looking for guidance on how to redefine a primitive complex type which is defined in a schema that is imported into several other schemas. The instance document references as master schema that imports the other namespaces and definitions in the hierarchy.

 

If I point an instance document at a schema that imports the document schema after importing a schema redefining the base types, I receive an error saying can’t redefine because base schema is already redefined or imported.

 

Any ideas?

 

Thanks,

Marty Burns