Hi Tom,

Happy to see your interest in configuring Draft Space (and probably Review Space). Let me first highlight that with Collective Spaces, we aim for a high out of the box behavior. By taking a bit more control, we actually minimize customization touchpoints, in turn less configuration makes upgrades easier which comes with examples as yours.

So BehaviorConfig.xml is the only customization we allow, and is mostly catered to cover typical OASIS DITA specialization. I assume you found https://docs.sdl.com/806356/811981/sdl-tridion-docs-14-sp3/collective-spaces---------------behaviorconfig-xml  already. Layout changes like “Step 1” becoming “1.” Is not scope for change. Remember that these changes complicate product development progress (more permutations), and in turn also your upgrade (maintain customizations is effort and has a potential risk as well).

We consider it a great feature that “note” permutations like yours are transparently picked up from the OASIS DITA schema – as an alternative I would like to suggest DITA Constraints.

For the wider audience, sessions 3 and 4 mentioned on https://community.sdl.com/product-groups/sdl-tridion/tridion-docs/b/weblog/posts/sdl-tridion-docs-architectural-runway-txs2020 titled “TXS 2020 Day 2: Designing a Domain-Specific-Language - YouTube” and “TXS 2020 Day 2: Partner Presentation - Fonto - YouTube” highlight parts of the route we took so far.

Best wishes,
Dave

Thanks Dave,

I appreciate the details and the (as usual) speedy and well-informed response. You mentioned briefly "DITA Constraints." We may be open to making changes to the schemas to restrict what happens in Draft Space (as opposed to the DTDs which we might not change). I'm specifically interested in controls for Draft Space. Can you explain what you mean by "DITA Constraints" and how those would help me control what happens in Draft Space?

Best regards,

Tom

Thanks Dave,

I appreciate the details and the (as usual) speedy and well-informed response. You mentioned briefly "DITA Constraints." We may be open to making changes to the schemas to restrict what happens in Draft Space (as opposed to the DTDs which we might not change). I'm specifically interested in controls for Draft Space. Can you explain what you mean by "DITA Constraints" and how those would help me control what happens in Draft Space?

Best regards,

Tom