Design for Bug # 1897542

What user need will be met by this feature?

Users needn't worry about their topic ids conflicting with other's. Duplicated topicIDs betwwen different dita files are handled automated by Chunk module.

What is the technical design for the change?

@chunk attribute in <topicref> has seven different values, according to the specification only the vaule of to-content need to be considered. "to-content" chunk several dita files or topics in to one certain file, if there are duplicated topicIDs, they should be changed. <topicref> can be nested, and each nested <topicref> can have its own @chunk, in this situation the nested <topicref> are chunked into its own file, not conflict with the ancestors,  fortunately we can use the same idea to process the problem of duplicated topicIDs.

What sections of the toolkit will be impacted by the change?

ChunkModule.java and Constants.java are impacted by this change.

See also

none