DITA IDs not unique - consequences?

rkusterer

20-12-2019

Hi all,

we are using AEM DITA with the XML plugin. DITA expects unique topic IDs (https://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/id.htmlhttps://docs.oasis-open.org/dita/v1.0/archspec/id.html), is there any info in which situations AEM uses these IDs? Nothing prevents users from copying topics, and copies have non-unique IDs (AEM only generates IDs when creating topics).

 

As long as the copied topics are not referenced in the same DITAmap, the non-unique IDs have not caused an issue. 

 

Then I was looking at incoming and outgoing links in the topic properties. Let’s say topic A contains a link to topic B, and I duplicate A. If I now look at incoming links for B, only A1 is listed but A2 is not. Can anyone confirm that? Will that happen for every copy, because A1and A2 have the same ID? That’s one example where IDs are used, are there any others we should be aware of? Copying topics doesn't break anything, but it will cause confusion later if someone relies on the topic properties for link info. 

Accepted Solutions (0)

Answers (0)