Consider DITA-OT project file contexts in "Validate and Check for Completeness"
Posted: Sun Nov 13, 2022 3:09 am
Our writers make heavy use of content reuse and profiling conditions. Consider the following example:
Note that
Validate and Check for Completeness has options to consider DITAVAL profiling via condition sets, associated transformation scenarios, and manually specified DITAVAL conditions. All our DITA-OT project files are in the Main Files list. This enhancement request is to provide a way to also consider the DITA-OT project file contexts that apply:
Our DITA-OT project files capture all of the profiling condition configurations that our maps are published in. (And importantly, they capture this by construction because they *are* the files used for publishing!)
When a writer updates or restructures content in a map, this would allow them to ensure valid content in all publishing contexts that reach the customer. This request is already filed under issue ID EXM-47753.
Note that
- The Product variable has multiple definitions, but only one is active at a time.
- The warehouse topic has a reference to a "featureC" topic that is not used in this book.
Validate and Check for Completeness has options to consider DITAVAL profiling via condition sets, associated transformation scenarios, and manually specified DITAVAL conditions. All our DITA-OT project files are in the Main Files list. This enhancement request is to provide a way to also consider the DITA-OT project file contexts that apply:
Our DITA-OT project files capture all of the profiling condition configurations that our maps are published in. (And importantly, they capture this by construction because they *are* the files used for publishing!)
When a writer updates or restructures content in a map, this would allow them to ensure valid content in all publishing contexts that reach the customer. This request is already filed under issue ID EXM-47753.