- From: David Chadwick <d.w.chadwick@kent.ac.uk>
- Date: Sun, 22 May 2016 14:28:41 +0100
- To: public-credentials@w3.org
On 22/05/2016 13:26, Timothy Holborn wrote: > What about version control and therein; 'get latest'... I dont think this is needed when have an issuing time and expiry time. You can tell from the former which is the latest credential regards David > > On Sun, 22 May 2016 at 22:01 Victoriano Giralt <victoriano@uma.es > <mailto:victoriano@uma.es>> wrote: > > On 21/05/16 20:44, David Chadwick wrote: > > You are mixing up the attribute/claim, date of birth (or similar) > which > > lasts forever, and the credential, which is a cryptographic digital > > representation of it. This has to have an expiry time due to the > > inherent weakness of the crypto. > > You are very right, David, it is possibly me being thick because of the > cabin pressure. I should read threads twice before responding from a > plane :-) You already noted that in the thread, and you are right, > signatures should be refreshed because of crypto. > > > regards > > double those ;-) > > -- > Victoriano Giralt CIO > University of Malaga > +34952131415 SPAIN > ================================================================== > Note: signature.asc is the electronic signature of present message > A: Yes. > > Q: Are you sure ? > >> A: Because it reverses the logical flow of conversation. > >>> Q: Why is top posting annoying in email ? >
Received on Sunday, 22 May 2016 13:29:14 UTC