[Openid-specs-fapi] "SHALL" vs. "MUST"

[Preibisch, Sascha H]

Thanks Brian and Mike!

I checked RFC https://www.ietf.org/rfc/rfc2119.txt, and, as Mike said, according to that MUST and SHALL are exactly the same.

My feeling tells me though they are understood as you said, Brian.

With that it is just important to always reference the RFC 2119 when using the terms:

1. MUST   This word, or the terms "REQUIRED" or "SHALL", mean that the
   definition is an absolute requirement of the specification.

Now I feel better.

Thanks,
Sascha

From: Brian Costello <BCostello at yodlee.com<mailto:BCostello at yodlee.com>>
Date: Tuesday, December 6, 2016 at 4:03 PM
To: Sascha Preibisch <sascha.preibisch at ca.com<mailto:sascha.preibisch at ca.com>>, Financial API Working Group List <openid-specs-fapi at lists.openid.net<mailto:openid-specs-fapi at lists.openid.net>>
Subject: RE: "SHALL" vs. "MUST"

I ran this by a couple of contract lawyers I trust.

They use "shall" to create ambiguity because it can mean "may" or "will". "Must" has no ambiguity. It also connects with rights and responsibilities. "Must" is a responsibility and "shall" is a right, which is why there can be ambiguity. One doesn't have to do the "shall" thing, even if there a right to do so.

It also really hinges on jurisdiction and how they have interpreted shall.

Brian

-----Original Message-----
From: Openid-specs-fapi [mailto:openid-specs-fapi-bounces at lists.openid.net] On Behalf Of Preibisch, Sascha H via Openid-specs-fapi
Sent: Tuesday, December 06, 2016 9:01 AM
To: Financial API Working Group List <openid-specs-fapi at lists.openid.net<mailto:openid-specs-fapi at lists.openid.net>>
Subject: [Openid-specs-fapi] "SHALL" vs. "MUST"

Hi all!

I just had a chat with a colleague and he said:

- you know Sascha, I hate to read 'shall' in specifications. I then never know if a product supports it

So my question is: what is the reason for using "shall" instead of "must"?

Thanks,
Sascha

_______________________________________________
Openid-specs-fapi mailing list
Openid-specs-fapi at lists.openid.net<mailto:Openid-specs-fapi at lists.openid.net>
http://lists.openid.net/mailman/listinfo/openid-specs-fapi<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openid.net_mailman_listinfo_openid-2Dspecs-2Dfapi&d=DgMFaQ&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=BjnOFeRZMwPBZLm00SguJm4i4lt0O13oAeF-9EZheL8&m=jsWdFoc0l_lJMPweb2dik0s8M-1MnT4F3vAzp5SsIiM&s=YlghwUkJu2X9LGnogWwdMxvQM9--tj0VrL67OgvX7B4&e=>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-fapi/attachments/20161207/ab88f0ca/attachment-0001.html>