Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.2: Replace "non-falsifiable" with a more accurate term #332

Closed
MarkLodato opened this issue Mar 23, 2022 · 5 comments
Closed

0.2: Replace "non-falsifiable" with a more accurate term #332

MarkLodato opened this issue Mar 23, 2022 · 5 comments
Labels
duplicate This issue or pull request already exists slsa 3 Applies to a SLSA 3 requirement

Comments

@MarkLodato
Copy link
Member

The term non-falsifiable is used incorrectly in the SLSA requirements. "Falsifiable" means that a theory can be proved false though some test, which is actually a good thing. What we actually mean is "non-forgeable," though perhaps there is an even better term. Any suggestions? (Note: This is also somewhat related to #261.)

I suggest that we wait until v0.2 to change the term, since doing so will break existing references.

@MarkLodato MarkLodato added the slsa 3 Applies to a SLSA 3 requirement label Mar 23, 2022
@MarkLodato MarkLodato added this to the v0.2 milestone Mar 23, 2022
@MarkLodato
Copy link
Member Author

Once it's decided to change, we could add a note to v0.1 noting this misuse of the term.

@david-a-wheeler
Copy link
Member

For 0.1 we can add a note, but for version 0.2 let's definitely switch to the correct term :-).

@david-a-wheeler
Copy link
Member

The scientific meaning of falsifiable is "capable of being disproved through experiment". The meaning intended here is "incapable of being undetectably false", which is a plausible meaning of the word but isn't what will come to mind to many.

Perhaps "non-forgeable" or "verifiable" are better terms?

@trishankatdatadog
Copy link
Member

Thoughts @cedricvanrompay-datadog?

@MarkLodato
Copy link
Member Author

Let's merge this into #306 so that we have a single "terminology" issue rather than one per term.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists slsa 3 Applies to a SLSA 3 requirement
Projects
None yet
Development

No branches or pull requests

3 participants