: How to tag distinct options/entities without giving any an implicit priority or suggested order? An example of the problem in an aggravated form surrounds the controversy of France changing ‘mother’

Vote Up Vote Down

Full names and arbitrary names are good solutions to the question you asked. To address the question behind the one you asked -- the implicit "superiority" in ordering -- write examples that don't start with the first unit. For example, I might describe a database with nodes A, B, and C, and then talk through an example where B acts as the initiator in processing a query. Who says it has to be A? The names are arbitrary, after all, so don't start all your examples with the first name in your ordered set. (For that matter, why not have nodes K, L, and M?) If you have users Alice and Bob and Carol and Dan, try having Dan or Carol be the first ones to act in a scenario.

There is value in having sequential names in some kinds of diagrams and examples, like that database cluster (where there might be way more than three nodes). Don't make your documentation less usable by talking about nodes 12, 37, 42, and 139 instead of 1-4 or A-D. But you don't always need meaningful names and you don't always need to match "first in the sequence" with "first in the example or sequence of actions".

(0)

Vote Up Vote Down

I don't think most readers would assume that the order in which you list things implies a priority. If you're going to give a list, it has to be in SOME order. If you said, "I work with three guys: Al, George, and Fred", I think few would assume that this means that Al is better or more important than George and Fred.

That said, if you're concerned that readers may make such an assumption, just add a sentence saying the order is not significant. I see this every now and then, a writer will say, "The members of the group, in no particular order, are ..."

(0)

Vote Up Vote Down

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.

(0)

Vote Up Vote Down

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.

(0)