The rabbit hole on names goes deep [1]. Lots of other fun rabbit holes. [2] For how to model physical objects like those cables, go see how Grainger does it as

The rabbit hole on names goes deep [1]. Lots of other fun rabbit holes. [2] For how to model physical objects like those cables, go see how Grainger does it as a working practical model. To really handle names properly, you need more context than the name in the presentation layer that many schemas take their modeling from can obtain. Government health care or similar widely-adopted encoding is sometimes Good Enough. If you want non-lossy exactitude however, then that's a much bigger scope (I'd be investigating a first-pass classifier with contextual hints taken from various geolocations, age, etc., that implies soliciting the name comes after what you normally solicit for input, and refining from there). Password reset; this is why vendors like Okta exist to abstract authN away for us, and auth0 for authZ. Then there is the rabbit hole of what this abstraction leads to... [1] https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-... [2] https://github.com/kdeldycke/awesome-falsehood https://github.com/kdeldycke/awesome-falsehood