On 03/23/2011 07:23 PM, Tyrin Avery wrote: > > I’m using XMLMind Professional 4.8 > > > > When I try to retransclude a reference that I’ve had in the doc for > over a year I get the following error: > > > > Inclusion Error > > file:/C:/DemandwareStudio/workspace/documentation/branches/maintenance.2.11.1/doc/DITA/source/ditamap/SiteDevelopment/Supporteddatatypes.dita::: > cannot fetch included nodes: the list of domains of the referenced > document "(topic reference) (topic hi-d) (topic ut-d) (topic indexing-d) > (topic hazard-d) (topic abbrev-d) (topic pr-d) (topic sw-d) (topic > ui-d)" must be equal or must be a subset of the list of domains of the > referencing document "(topic concept) (topic hi-d) (topic ut-d) (topic > indexing-d) (topic hazard-d) (topic abbrev-d) (topic pr-d) (topic sw-d) > (topic ui-d)" >
In plain English, this means: you cannot include in a <concept> topic, a <table> element coming from a <reference> topic. > file:/C:/DemandwareStudio/workspace/documentation/branches/maintenance.2.11.1/doc/DITA/source/ditamap/SiteDevelopment/Supporteddatatypes.dita::: > document not fully processed after 3 iterations > > > > This error doesn’t make any sense. The only difference in constraints > between the two topics is that one is a concept and one is a reference > type. They both use the <table> element. I’ve checked the DITA 1.2 spec, > and as far as I can tell, this should be allowed. Please tell us where you see this. We have very carefully implemented the following part of the spec: Excerpts from http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/constraintsGeneralize.html#constraintsGeneralize --- Conref compatibility with constraints To determine compatibility between two document instances, a conref processor can check the @domains attribute to confirm that * The referencing document has a superset of the vocabulary modules in the referenced document. * For each vocabulary module in the referenced document, the referencing document qualifies the common module with a subset of the constraints in the referenced document. Some examples ... --- > At the very least, I’d expect this to be backward-compatible, Yes, this used to work with XMLmind XML Editor v4.7/DITA 1.1 because the DITA 1.1 DTD specified just the following domains for both <concept> and <reference>: --- (topic hi-d) (topic ut-d) (topic indexing-d) (topic pr-d) (topic sw-d) (topic ui-d) --- But now DITA 1.2 specifies different, more complex, domains for <concept> and <reference>. > since this is an old conref and > hasn’t changed. I’m pretty sure this is a bug in XMLMind. I'm sorry but this is *unfortunately* not a bug in XMLmind XML Editor. We would really like this to be a bug, because this part of the spec (checking domains instead of leveraging the DTD or schema) indeed does not make sense. Because we have expected this to happen, we have implemented a way to bypass this check. You'll have to add the following system property to the script used to start XMLmind XML Editor (bin/xxe Unix shell script OR bin/xxe.bat OR bin/xxe.jstart if you use bin/xxe.exe): -DXXE_LENIENT_CONREF=1 (We forgot to document this system property.) -- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
