I love how the OIDC standard is littered with “authentication identity token code id cookie identifier” and many subtle variations of homonyms in slightly different combinations and orders.

I’m sure someone thought it all made perfect sense.

Probably someone who never confuses “empathy” and “sympathy” while also carefully distinguishing between “should” and “ought”.

▲

theasisa 4 hours ago | parent [-]

> Probably someone who never confuses “empathy” and “sympathy” while also carefully distinguishing between “should” and “ought”.

What do you mean by this?

▲

throwaway1058 4 hours ago | parent | next [-]

I feel "ought" is stronger and is something that is expected of you, but English is not my native language.

"You should drink more water"

"You ought to help your sick mother"

▲

da_chicken 3 hours ago | parent | next [-]

I'm a native speaker and I agree. "Ought" can connote an obligation or responsibility of some sort. "Should" is used more often when the outcome is out of any control. It might only be the speaker's belief.

But there is significant overlap.

▲

rzzzt 2 hours ago | parent | prev [-]

That's when you turn to the RFC2119 all-caps requirement levels!

	▲	intrasight 41 minutes ago \| parent \| next [-]
		SHALL vs SHOULD
	▲	actionfromafar an hour ago \| parent \| prev [-]
		You really OUGHT to.

▲

perching_aix 4 hours ago | parent | prev [-]

Not sure what's giving you a pause there?

▲

happytoexplain 3 hours ago | parent [-]

It's going over my head, too. I don't understand what the implication of the sentence is in context.

▲

hilariously an hour ago | parent [-]

Someone who is incredibly pedantic and also specific about their word use, who doesn't have a problem with four different descriptions because they all elide to the same thing. ie someone who should have more sympathy AND empathy even if they can disambiguate the terms (for their audience.)

	▲	ButlerianJihad an hour ago \| parent [-]
		> Someone who is incredibly pedantic > they all elide to the same thing I see what you did there: https://en.wiktionary.org/wiki/elide#Usage_notes Current article title: Authorization terminology is a mess: Let's fix it That being said, GP mentions OIDC Connect, which is indeed a standard using jargon, just like the IETF uses jargon, and when a standard uses or invents jargon, it makes an effort to define that terminology, and also delineate when it's being used. https://openid.net/specs/openid-connect-core-1_0.html#Termin... If someone believes that standards and specifications are written by pedantic people who are precious about the definitions of words, they may also be likely to fire their attorney during a court case, because that attorney just refuses to use plain English in the courtroom.