Are you suggesting a content model like element xenoData { att.global.attributes http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation/ws/P5/Guidelines-web/..., att.global.rendition.attributes http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation/ws/P5/Guidelines-web/..., att.global.linking.attributes http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation/ws/P5/Guidelines-web/..., att.global.analytic.attributes http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation/ws/P5/Guidelines-web/..., att.global.facs.attributes http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation/ws/P5/Guidelines-web/..., att.global.change.attributes http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation/ws/P5/Guidelines-web/..., att.global.responsibility.attributes http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation/ws/P5/Guidelines-web/..., att.declarable.attributes http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation/ws/P5/Guidelines-web/..., att.typed.attributes http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation/ws/P5/Guidelines-web/..., desc?, text | macro.anyXML http://teijenkins.hcmc.uvic.ca/job/TEIP5-Documentation/ws/P5/Guidelines-web/...* } Lou? I'd be ok with that, actually. I'll point out too that it has @type and @subtype already, so there are ways to characterize it.