"ID" or "Id" in the user interface

Question

The QA manager I work for has just told me that there is an error in my desktop application because it uses the "Agent Identifier" as the login prompt, when it should be "Operator ID". Her argument is that “Eid” refers to Freud’s ego-part “psychic apparatus” and is not semantically correct.

Now, as an anal engineer (AE), of course, I had to find an Id vs ID, and from my cursory investigations (google) it seems that the ID is as often used for Freud’s ego as Id.

Therefore, I argue that Id is an abbreviated version of "Identifier", more correct, or at least more frequently used, than an ID, which usually indicates a two-word abbreviation.

I could just change the user interface, but then I would not continue my profession as AE, so I was wondering if there are any best practices or links for these kinds of things that I could use to support my arguments? Remember that this question is about the user interface, not the source code, where abbreviations and registers are a completely different branch of philosophy.

Answer 1

According to Merriam-Webster , the abbreviation is "ID". If it were the correct abbreviation, it would have to be an "Identifier". with a period.

Answer 2

Personally, I use "Id". The compiler doesn't care, but my eyes. Compare:

GetIDByWhatever <-- looks terrible GetIdByWhatever <-- oh so pretty! 

Aesthetics is more important than grammar when it comes to code, always. (Update: after 4 years, I no longer agree with this statement)

Answer 3

"D" is not worth anything, so I always considered it an abbreviation, not an abbreviation, and therefore I also use "Id" and not "ID".

I do not know about your arguments qa - words can have more than one meaning - this is not uncommon in English :)

But it looks like regular use is actually an “ ID ” (right or wrong: P), which is probably the format your users expected.

Answer 4

Interestingly, many believe that Eid should be a way. I feel that “ID” is appropriate because it hints at how we pronounce it — ID Also, when I read “Id” in the current sentence, I sometimes have to go back and read it again to make sure it isn’t typo for "is" or "it".

Answer 5

The QA line of reasoning is stupid. Many English words have several meanings. Lead, Lead, Lead (metal, front or connector).

I would just try to match the capitalization used elsewhere in the application.

Answer 6

As a UAUA (Ultra-Analytical Usability Analyst), use ID instead of Id.

Visually, it is more recognizable in English. Grammatically, “Eid” is a word (rhyming with “squid”) and Freud's definition above. We never verbally asked to show "id", but "ID". I'D. fine, but passe, as periods mean a few words.

So.

Just use the id, ok?

OK

Answer 7

So, as a technical writer, this is a problem that arises for me quite regularly when other people are considered, be it programmers, BAs or other authors. As a rule, id refers to the ego, as others told me in front of me, and the accepted abbreviation for identification is an identifier, just because many people do not know or do not understand the rule, this does not mean that they are correct (sorry for being stupid) , mind you rules for punctuation and writing are pretty much almost as volatile as mod!

However, nobody seemed to ask if your company has a standard? At the end of the day, if your company has a style guide and they have covered this topic in this guide, you should follow the guide. If this is not covered, then can I suggest that you raise the problem with the person who leads the leadership and include all interested parties in the conversation. Consistency is key. If the company you work for doesn't have a style guide, maybe it's time to start it!

Hope this helps ...

Answer 8

How would you say it if you read aloud? I would say two letters. ID is correct, similar to similar abbreviations such as television. (No dots, please, because the letters are not worth it.)

When I deal with such abbreviations, I like to format them in small tables, but this is just a personal taste. Capitals, anyway.

(But I will probably continue to use Id in the code itself.)

Answer 9

The user interface and code are very different animals ...

"ID" is the correct answer for the user interface.

In code, consistency is your friend. Whether you want it or not, go with what you already have elsewhere in the code. If this is not the case, then read and make a decision, or chat with the team and devise a way so that everyone can agree. Consistency makes life easier.

Answer 10

as a short version of the identifier, I would use Id. Also, ID is fancy when you have features like

 getUserIDByName() 

Numerous capitals in domains are quite problematic with CamelCase, as they can create ambiguities and, therefore, dishonesty in your interfaces and names

Answer 11

I think it depends on how we write. We do not pronounce "this", but "ay-di." Id-ID is a spell with two sounds, that's why people make D in a cap so as not to think that id is a "word". It is more like a symbol symbol. I like "ID" only because it is nicer.

Answer 12

I prefer the identifier because when it is used with other 2-letter text, it does not become a single all-caps word

Photovoltaic systems ... PVID (single word or 2?) PvId (much more clear).

Answer 13

Each of us has a bit of OcD!

Anyway, the Google style guide says this:

"ID: not Id or id, except for string literals or enumerations. In some cases, it is better to specify as an identifier or identification."

I go with that.

Microsoft is more vague as far as I could find.

Answer 14

ID = Idaho! Id = Freud! Let the OCD begin!