Fhyujk

An example of the problem in an aggravated form surrounds the controversy of France changing ‘mother’ and ‘father’ to ‘parent 1’ and ‘parent 2’ in official paperwork - where the controversy suggests the new standard implies one parent is 'secondary' and the designation may induce completely unnecessary family conflicts.

In technical writing this may happen also; we have two or more completely independent identical units/objects/devices, which need to communicate. Any of them may initiate the communication, and this will assign them specific roles, but before the conditions occur, they are perfectly equivalent and so suggesting any order, priority, sequence etc would be misguiding - but we still need to distinguish them; assign them some designations when describing the situation. Marking them "Unit A, B, C"; "1, 2, 3"; "X, Y, Z", "Alpha, Beta, Gamma" this all is a specific sequence. I might try using symbols, 'unit @, unit *, unit %' but I believe this by itself would be rather confusing, never mind not yielding itself for verbal communication.

Can you suggest a convenient set/system of identifiers to use e.g. in technical writing or legal documents, that doesn't imply any order or priority of the options, but still allows to reference them uniquely?

I think you may be overthinking the issue.

In technical writing when you name three entities with elements of a specific subset, the ordering of the specific subset doesn't come into play unless it is specifically stated. There are plenty of examples where the common "A,B,C", or "X,Y,Z" are used without underlying assumptions of "who come firsts" or "who is more important". Luckily enough, technical writing is somewhat shielded from those kind of controversies.

Answering your question, though, you could try:

• Assign full names to your entities. This is often done in telecommunications examples or in cryptography (Alice and Bob, exchanging messages...). If you don't like inventing name, you could use the Nato Phonetic alphabet. To be sure, following an alphabetic convention won't free you of an underlying order. Another drawback of this soluton is that full names are not concise; if you have a lot of entities to name, you'll see your text fill up with Alices and Bobs.




• Use a color coding. Your entities can become Red, Green and Blue. This is somewhat assimilable to the alphabet, since you can easily shorten those to RGB. Yet, if you pick your names from colours, nobody will be able to claim that you are making assumptions about who's more important.

Assign them a cycling index "number" upon discovery. Use an arbitrarily large sequence, orders of magnitude larger than needed.

To further the concept of an oversized indexing system, letters are sometimes combined with numbers. Perhaps hexidecimal with an advancing cycle larger than 1

Parent L7KQ6 verses Parent Z3M19 sounds suitably dystopian.