My understanding is that ditabase allows all topics defined within the technicalContent package, plus the generic topic from base, to be aggregated into a single XML instance. Since the technicalContent package has constrained the shell DTD for task (task.dtd), then the shell DTD for ditabase ought to apply same constraint. Otherwise, ditabase becomes more than a way to aggregate topics from the technicalContent package.
Having ditabase do more than facilitating aggregation for technicalContent topics may be desirable in some applications. But, in such cases the onus would be on the application implementer to reconfigure the ditabase shell DTD to suit their needs. Such reconfiguration could easily include the removal or replacement of strictTaskbodyConstraint.mod from
ditabase.dtd.
Bob Thomas
;)
+1 720 201 8260