DDSIRTP23 — Remove the concept of Topic Kinds (With Key vs. No Key)

This distinction is important for DDS, but not relevant for RTPS. There are places where RTPS deals with the Key as an independent unit of data (KeyFlag, etc.), but those are not relevant to the TopicKind_t which seems to be an artifact of an older version of the specification. The current protocol as written in this specification works the same way for both With Key and No Key topics. This issue seeks to remove the Topic Kind concept entirely from the specification.
1. Section: 8.2.1.2, Table 8.2
Page: 14
Change: remove the table row for TopicKind_t
2. Section: 8.2.1.3, Figure 8.2
Page: 16
Change: remove the topicKind attribute in Endpoint
3. Section: 8.2.5, Figure 8.5
Page: 21
Change: remove the topicKind attribute in Endpoint
4. Section: 8.2.6, Table 8.9
Page: 23
Change: remove the table row for TopicKind_t
5. Section: 8.2.9.1, Figure 8.6
Page: 25
Change: remove the if() statements for W::topicKind
6. Section: 8.2.9.1.3-4
Page: 26-27
Change: remove the if() statements for the_rtps_writer.topicKind and the paragraphs “This operation has no effect if the topicKind==NO_KEY).”
7. Section: 8.3.3, Figure 8.8
Page: 31
Change: remove NoKeyData and NoKeyDataFrag
8. Section: 8.3.7, Bullets 1-2,4
Page: 43
Change: remove the text “(NO_KEY Reader/Writer or WITH_KEY Reader/Writer)”
9. Section: 8.3.7.2
Page: 47
Change: remove the text “(NO_KEY or WITH_KEY)”
10. Section: 8.3.7.3
Page: 49
Change: remove the text “(NO_KEY or WITH_KEY)”
11. Section: 8.3.7.2, 3rd Bullet
Page: 63
Change: remove the text referring to “keyed topics”
12. Section: 8.4.4
Page: 69-70
Change: remove all references to topicKind, WITH_KEY, NO_KEY, etc.
13. Section: 8.4.7.1, Figure 8.15
Page: 72
Change: remove the topicKind attribute in Endpoint
14. Section: 8.4.8.1
Page: 83
Change: remove “WITH_KEY”
15. Section: 8.4.8.1, Figure 8.16
Page: 84
Change: remove “WITH_KEY”

16. Section: 8.4.8.2
Page: 85
Change: remove “WITH_KEY” and “NO_KEY”
17. Section: 8.4.8.2, Figure 8.17
Page: 86
Change: remove “WITH_KEY”
18. Section: 8.4.9.1
Page: 90
Change: remove “WITH_KEY” and “NO_KEY”
19. Section: 8.4.9.1, Figure 8.18
Page: 90
Change: remove “WITH_KEY”
20. Section: 8.4.9.2
Page: 93
Change: remove “WITH_KEY” and “NO_KEY”
21. Section: 8.4.9.2, Figure 8.19
Page: 94
Change: remove “WITH_KEY”

22. Section: 8.4.10.1, Figure 8.21
Page: 102
Change: remove the topicKind attribute in Endpoint

23. Section: 8.4.11.1
Page: 109
Change: remove “WITH_KEY” and “NO_KEY”
24. Section: 8.4.11.1, Figure 8.22
Page: 110
Change: remove “WITH_KEY”

25. Section: 8.4.12.1
Page: 111
Change: remove “WITH_KEY” and “NO_KEY”
26. Section: 8.4.12.1, Figure 8.23
Page: 111
Change: remove “WITH_KEY”

27. Section: 8.4.12.2
Page: 113
Change: remove “WITH_KEY” and “NO_KEY”

28. Section: 8.4.12.3, Figure 8.25
Page: 117
Change: remove “NOKEYDATA” alternative

29. Section: 8.5.3.3, Tables 8.74 and 8.75
Page: 129
Change: remove topicKind rows from both tables

30. Section: 9.3.2, Table 9.4
Page: 155
Change: remove the “TopicKind_t” row

Limit the use of TopicKind to the places where it matters

The protocol works the same whether or not a Topic is keyed; the distinction was therefore unnecessary in many places and was removed.