Comment 1 for bug 1853

I agree with your rationale, but disagree with your conclusion.

First, there are places where a distinct title is useful. For example (if we follow source package naming) we could have name="firebird" displayname="FireBird" and title="FireBird Database" (as opposed to browser). I find it often useful to use the title to clarify the name a bit. For example displayname="Osiris" does not tell you much, but title="Osiris - Host Integrity Monitor" can really help reading long lists like in <https://launchpad.net/products?text=network>.

Also, in my understanding, the one item that's not well defined is _title_. Displayname is very clearly meant to be the actual name of the project, with proper capitalisation, while name is constrained by url policies. An example could be name="texmacs" displayname="TeXmacs". The capitalised X in the middle of the word is part of the proper name of the project, or name="gnulinux" title="GNU/Linux".

I think title and displayname are both useful, but the help text could be very much improved. From a data input perspective the one that's easy to explain and understand is displayname.

The help text should be fixed to make sense. That's true for most Registry input forms anyway.