Some additional information that may spur some thoughts on this overlooked topic...
As a concrete example I have this in one C# doc-comment:
/// The <see cref="SyntaxHighlightingTextBox.EnableHighlighting"/> property ...
The class containing that doc-comment inherits from SyntaxHighlightingTextBox so it is a valid reference. However, the code for SyntaxHighlightingTextBox comes from a separate DLL which is
not included in the documentation generation. In the final generated HTML that line renders as:
The EnableHighlighting() property
with the property name emboldened and an erroneous set of parentheses attached--a bug in the XSLT perhaps...? For completeness, I should state that when the property reference resolves to a valid link elsewhere in the documentation tree, then the formatting
is correct, without the extraneous parentheses.