Extra warnings reported when project using key scopes and branch filtering is published

We are using branch filtering and key scopes, I’m attaching a small project:

http://www.oxygenxml.com/forum/files/mobilePhoneBrochure.zip

The published content is correct but the publish process issues warnings like:

   [gen-list] [DOTJ045I][INFO] The key "model" is defined more than once in the same map file. The  reference href="null" is ignored.
   [gen-list] [DOTJ045I][INFO] The key "image" is defined more than once in the same map file. The reference href="image/Syncro_x2000_black.png" is ignored.
  [gen-list] [DOTJ045I][INFO] The key "description" is defined more than once in the same map file. The reference href="null" is ignored.

and:

  [branch-filter] file:/C:/Users/radu_coravu/Desktop/to%20upload/mobilePhoneBrochure/phoneDetails.ditamap:5:46: [DOTJ065W][WARN] Branch filter generated topic topics/specifcations.dita used more than once. Renaming topics/specifcations.dita to topics/specifcations-1.dita.
  [branch-filter] file:/C:/Users/radu_coravu/Desktop/to%20upload/mobilePhoneBrochure/phoneDetails.ditamap:6:55: [DOTJ065W][WARN] Branch filter generated topic topics/colors-and-accessories.dita used more than once. Renaming topics/colors-and-accessories.dita to topics/colors-and-accessories-1.dita.

The first set of messages received in the gen-list stage seems incorrect. The “model” key for example is defined twice but in different key scopes:

<map>
 <title>Mobile Phone Brochure</title>
 <topicref href="phoneOverview.dita" keyscope="X1000Scope">
  <keydef keys="model">
   <topicmeta><keywords><keyword>X1000</keyword>        </keywords>       </topicmeta>
  </keydef>
  ......
 </topicref>
 <topicref href="phoneOverview.dita" keyscope="X2000Scope">
  <keydef keys="model">
   <topicmeta>        <keywords>         <keyword>X2000</keyword>        </keywords>      </topicmeta>
  </keydef>
  ......
 </topicref>
</map>

The second set of messages I think is not necessary. The feature works as it should, it renames topics in various context. So I don’t think it should advertise this as a warning. It should probably report nothing in this case.

[raducoravu]

+1 Another one of our users is properly using keys with key scopes and receives errors like this one:

         [gen-list] [DOTJ045I][INFO] The key "keyName" is defined more than once in the same map file. The reference href="null" is ignored.

In my opinion this information message could be removed completely. Even if the end user is not using key scopes, there is no problem when you have the same duplicate key, the specs tells precisely what should happen in these cases.

My problem is that there are other information messages which are important and indicate problems like this one:

            [DOTJ048I] Unable to find key definition for key reference "key_name" in scope "scope_name. The href attribute may be used as fallback if it exists

so I cannot advice the end user to just ignore all information messages.

[raducoravu]

Here we go: https://github.com/dita-ot/dita-ot/issues/2857