We intend to propose a method for, given an API element, ranking the threads linked with it based on the quality and confidence of the content of the threads, aiming to select the best threads for documenting that API element.
These factors need to be considered when using the content of threads for documenting API elements.
So Jive customers can search, browse, and link to SharePoint repositories and content from wherever they happen to be working in Jive, including groups, discussion threads, documents, and blogs.
This may impose warnings concerning the use of the thread content for documenting these API elements, as the need of documenting API elements together or preprocessing the thread content to filter relevant content for specific API elements.
In this sense, we define what is relevant for documenting: a thread is relevant for documenting an API element if it contains any relevant content for a specific type of documentation of that API element.
I wanted to explore mine and other women's individuality while still documenting the thread that tied our visual identities together".
Table 15 presents the results regarding the proportion of occurrence of API element that the analyzed threads are relevant for documenting such.
Table 15 Proportion of occurrence of API element which threads are relevant for documenting such, for both APIs and both types of discussion API Discussion type Relevant for documenting Swing how-to-do-it 94.35 debug-corrective 40.71 Android how-to-do-it 86.82 debug-corrective 23.89.
So, even if a given thread were not considered relevant for documenting that element, it does not mean that there is no other thread relevant for such element.
To perform that quantification, for each API element mentioned in the threads of our sample, we searched for at least one occurrence in a thread that was considered relevant for documenting it.
