Does the constraint mechanism allow removal of core elements?

If you wanted to omit <data> and all of its specializations you would have a harder task because you've have to override every parameter from commonElements or other modules that include %%data.elements.incl;, which is a much larger set.
Cheers, E. ---- Eliot Kimber, Owner Contrext, LLC http://contrext.com On 10/14/15, 2:55 PM, "Eliot Kimber" < on behalf of > wrote:
>What you show is the correct way to do it: simply omit the base type from
>the integration parameter entity, leaving only specializations. >
>This case is covered in the spec. Note that even though the constraint is
>implemented directly in the shell, it's still a constraint and needs to be
>declared on @domains. >
>Cheers, >
>E. > >----
>Eliot Kimber, Owner
>Contrext, LLC
> http://contrext.com > > > >
>On 10/14/15, 10:41 AM, "Bob Thomas" < on behalf
>of > wrote: > >>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 () or Skype >>Time zone: Mountain (GMT-7) >> >> >> >> >> >> >> > > > >

---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail. Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > >