Skip to Content.
Sympa Menu

cacert-policy - Re: [CAcert-Policy] CPS bugs. Vote please. Colosing date of votes21 October 12pm UTC

Subject: Policy-Discussion

List archive

Re: [CAcert-Policy] CPS bugs. Vote please. Colosing date of votes21 October 12pm UTC


Chronological Thread 
  • From: "Sam Johnston" <samj AT samj.net>
  • To: Policy-Discussion <cacert-policy AT lists.cacert.org>
  • Subject: Re: [CAcert-Policy] CPS bugs. Vote please. Colosing date of votes21 October 12pm UTC
  • Date: Mon, 20 Oct 2008 11:01:57 +0800
  • List-archive: <https://lists.cacert.org/cgi-bin/mailman/private/cacert-policy>
  • List-id: Policy-Discussion <cacert-policy.lists.cacert.org>

2008/10/17 Tomáš Trnka <TomTrnka AT seznam.cz>

I would like "validated" a bit more (and even more thinking about automated
checking)...What do the others think?

Validation in this context is the process of validating the chain of trust - it has nothing to do with verifying the information contained therein. On the other hand there is 'Extended Validation'.

The Mozilla CA Certificate Policy uses wording like 'We consider verification of certificate signing requests to be acceptable if it'
 
> P,S.: evaluated is derived from value. However it does not mean assigning
> value. The preposition e or ex means to extract. So evaluate actually means
> to extract value. That is why I think it may not be a bad term to use after
> all.

Probably correct...However - I don't know why exactly - I still tend to
have "evaluated" connected with a bit different meaning than "checked"
or "verified"...

Agreed, evaluated makes no sense in this context. We evaluate formulas, not IDs... 'I must evaluate your ID' makes no sense whatsoever, especially when you could just say 'I must verify your ID'.

Sam




Archive powered by MHonArc 2.6.16.

Top of Page