dita — archive

Does the constraint mechanism allow removal of core elements?

From: Robert Anderson <[email protected]>
To: [email protected]
Date: Wed, 14 Oct 2015 17:01:00 -0000

Hi Bob, I think this is what you are looking for: http://docs.oasis-open.org/dita/dita/v1.3/cos01/part3-all-inclusive/archSpec/base/example-contraints-replace-base-element-w-domain-extensions.html Basically, just do what you've done, but also define a constraint token that goes in @domains. I don't think that the DTD syntax will allow you to remove <data> when you don't also have domain specializations of <data>, but fortunately you've got those here. Robert D Anderson IBM Authoring Tools Development Chief Architect, DITA Open Toolkit ( http://www.dita-ot.org/ ) Bob Thomas ---10/14/2015 10:41:47---I am putting together authoring DTDs for DITA topics. One of the things that I would like to do is t From: Bob Thomas <[email protected]> To: dita <[email protected]> Date: 10/14/2015 10:41 Subject: [dita] Does the constraint mechanism allow removal of core elements? Sent by: <[email protected]> I am putting together authoring DTDs for DITA topics. One of the things that I would like to do is to constrain away elements that are meant for architectural extension rather than for authoring. For example, it would be nice to remove <data>. The DTD mechanics for incorporating this into the content model are straightforward: Out-of-the-box: <!ENTITY % data "data %ut-d-data_option; "> Constrained: <!ENTITY % data "%ut-d-data_option; "> Is there a way in DITA 1.3 to declare this as a constraint? I suspect that there isn't. If that's the case, then I claim that there should be a way to declare this because it is a reasonable thing to do. -- Bob Thomas +1 720 201 8260 Skype: bob.thomas.colorado Instant messaging: Gmail chat ( [email protected] ) or Skype Time zone: Mountain (GMT-7)