Please explain how the release-management domain should be processed

[Stefan Eike <stefan.eike@mailbox.org>]

Hi,

I've created a DITA-OT plugin that automatically generates lists or tables from the release-management domain elements. The code can be found on GitHub, the usage is explained in the docs. I'm not sure, whether I implemented this correctly.

The plugin picks the changes from the <change-item> elements. And it determines the book release dates from the <created> and <revised> elements that are allowed in the <critdates> element. The bookmap also has a <bookchangehistory> element, but, as I understand it, this is more to reflect the workflow and not the release dates. Is this and my implementation correct?

Further on, there is an <amendments> element in the <bookmap>, that could be used as a placeholder for the actual change lists or tables. Should this element be used for this purpose? And why is this element only allowed in the <backmatter> and not in the <frontmatter>? Currently, the plugin triggers the creation of te change lists or tables when a <booklist type="change-historylist"/> is used. Would it be possible to allow <amendments> also in the <frontmatter> or could you add a new <change-historylist> element to the <frontmatter> and <backmatter> for this?

Thanks and best regards,

Stefan