Calling it a standardness rule seems... uncomfortable. It seems too high, in that a standard is something generally reached by consensus. I think it should be referred to as a convention, which denotes both that it is commonly adhered to, but deviation is not a significant issue.
Would there be any point in changing the naming from "standardness rules" to "conventions"? "Standardness rules" seems easier to conflate with "consensus rules" which is the most common source of confusion I've seen.
That’s fair. Instead of referring to transactions that fail Bitcoin Core’s mempool policy as non-standard, we should really be talking about "transactions that are [not] accepted by Bitcoin Core’s mempool policy defaults". It’s a bit of a mouthful, though.
re: #972228
Would there be any point in changing the naming from "standardness rules" to "conventions"? "Standardness rules" seems easier to conflate with "consensus rules" which is the most common source of confusion I've seen.