The following is taken from the LyX wiki on semantic markup:
What is the difference between "noun" and "small caps" or "emphasized" and "italic"?
The concepts of "noun" and "emphasized" draw on the idea of "semantic markup" (as opposed to traditional "static" or "physical markup"). Semantic markup means that you do not mark a text element in a definite way ("this is italic" or "this uses small caps"), but you mark it as a semantic element ("this is a noun, i.e. a person name" or "this is to be emphasized").
How this really looks in the output can be (re-)decided at any time later, or it is determined by specific classes differently (so "emphasized" might mean "italic" in one class and "bold" in another). This has many practical advantages. If your publisher tells you "Please do not mark person names with small caps, but use italics" or "Please do not mark person names at all", you do not have to change any person name in your document, but simply change the definition of "noun", e.g. (to have no marking at all): \renewcommand*\noun[1]{#1}
The LyX philosophy is to encourage semantic markup. This is why the "semantic" elements are put prominently on the LyX toolbar.
Of course, the idea would be to have much more of such semantic elements. However, they have not yet been implemented in a proper way. Some elements are provided as "character styles" which can be accessed via "modules". Check out the "Logical Markup" module or the "Linguistics" module (the latter with semantic elements such as "Expression", "Concept", "Meaning"). But this is a different implementation in terms of the user interface, and those "insets" behave differently. A proper and unified semantic markup UI is yet a desideratum.
Taking the above into consider, LyX promotes a way of consistent typography whereby you specify the same thing using the same markup and can update it to your liking at any given time rather than (what is commonly referred to as) hard-coding things one way or another.
A practical example of this (using pure LaTeX) using your reference to nouns:
\documentclass{article}
\newcommand{\noun}[1]{\textsc{#1}}% Original formatting of nouns
\begin{document}
\noun{Jack} and \noun{Joe Bloggs} went up the hill \par
to fetch a pail of water. \par
\noun{Jack} fell down and broke his crown, \par
And \noun{Joe Bloggs} came tumbling after.
\end{document}
This input yields the output

If there is a change of heart and you wish to adapt the setting of nouns, you merely have to change the way \nouns are interpreted, without changing anything else in your document. So, by adding \renewcommand{\noun}[1]{\textsf{#1}} to your LaTeX preamble in LyX, the output after compilation changes to:

...or to \renewcommand{\noun}[1]{\MakeUppercase{#1}}:

...or to \renewcommand{\noun}[1]{\textit{#1}}:

The use-case should be obvious. (La)TeX's macro programming allows for this and it should be used. As such, in the interest of consistency throughout your document, mark Joe Bloggs as a "noun" wherever you see it:
"If I was writing an article about, say, the life of Joe Bloggs, should I set his name in noun case? Even in the title?"
Yes.
"If I list Jane Bloggs in my acknowledgements, should I set her name in noun case?"
Yes.
"Where else should I use noun case?"
Wherever you feel things should be consistent with nouns (whatever your definition of a nou; a person's name, for example).
Note that you would be able to change the meaning of \noun mid-document (even though it might not promote the same consistency). However, it's best to define the same things in the same way exactly for that reason.
-lyx, +typogaphy) accordingly, which should increase the chance to attract the typography experts to your question. – Daniel Jun 01 '13 at 07:49I used the LyX tag because I was under the impression that the noun style is a LyX feature.
– Pitarou Jun 02 '13 at 09:31