* Case Number: a20090908.1 * Status: closed * Claimants: Lambert Hofstra * Respondents: Pieter van Beek * Case Manager: UlrichSchroeter * Arbitrator: UlrichSchroeter * Date of arbitration start: 2009/09/08 * Date of ruling: 2009/10/21 * Case closed: 2009/11/11 * Complaint: incorrect first name {{{ Dear support, I'd like to file a dispute. I tried to assure member Pieter van Beek on June 15 2009 and noticed he has an incorrect first name recorded. In his account his first name is "Pieter", but his drivers license states his first name as "Petrus" Regards, Lambert }}} * Relief: TBD Before: Arbitrator Ulrich Schroeter (A). Respondent: Pieter van Beek (R) Claimant: Lambert Hofstra (C) Case: a20090908.1 1. 2009-09-08 (CM): requests for CCA / DRP ack to Claimant and Respondent 2. 2009-09-08 (CM): (R) accepts CCA / DRP 3. 2009-09-08 (A): I'll take care about that also as Arbitrator {{{ When I first created an account at CACert.org, I mistakenly entered "Pieter" as my first name. While this is indeed my common first name in daily life, officially my first name is "Petrus". At an ATA meeting with Lambert in the Netherlands, I found out that this was against CACert policies. So, there's no "dispute" in the normal sense: I fully agree with Lambert, and kindly ask you that my first name in the database be changed into "Petrus" instead of "Pieter". The reason I'm not simply creating a new account with correct data is that have already been asserted, am an assurer, and already assured several other people. Best regards, Pieter (Petrus) van Beek }}} == Discovery == * there was no malfeasance alleged or found * (R) Pieter (Petrus) has agreed the name change * (C, R) the dispute was filed by the Assurer but also agreed by the the person owning the account in question himself * this dispute is the result of learning at an ATE * (A) I've tried to request for confirmation about the givenname for about 1 or 2 more experienced assurers/co-auditors on this ATE * (A) running 1 week with requests and a 2nd week with daily reminders with request for confirmation doesn't give any confirmation results * (A) One addtl. assurer can remember about this case and also about the Givenname "Petrus" that he had seen in his drivers license but can't find the CAP form (!) * the full name Petrus van Beek was verified by a "senior experienced assurer" _and_ also "arbitrator" (Lambert Hofstra) at an ATE * 2 addtl. untidily assurers can no longer be the blockage of this arbitration case. * The request for confirmation was related about the discovery for arbitration case Arbitrations/a20090621.2 * two senior experienced Assurers have verified the requested name in the account * these 2 assurances would bring the Account up above 50 points according to AP * I have no doubts, that the Givenname for Pieter is Petrus, but according to AP i need an addtl. confirmation from an assurance so i came here to following intermediate Ruling: == Intermediate Ruling == I hereby order that - one of the "senior experienced assurer" (see CC party) have to contact Pieter (Petrus) van Beek to get an addtl. 2nd assurance under the CARS [1] program as a VIP assurance [2] The assurance should have to be done upto end of this month (31.10.2009). The assurer have to report to me directly with a reliable statement (see CARS) that Pieter (Petrus) van Beek full name is written in one of his ID documents as Petrus van Beek [1] CARS (short: CAcert Assurer Reliable Statement): see https://svn.cacert.org/CAcert/Assurance/Minutes/20090517MiniTOP.html - Reliable Statement [2] VIP assurance: see https://wiki.cacert.org/VipAssurance == Ruling == . 2009-10-21 (A): rcvd mails from 4 assurers, that states, that Peter's name in his ID documents is Petrus J.A. van Beek Due to these facts I order the accounts name to be changed without the removal of any assurance or experience points. The claimant is requested to revoke currently valid certificates, however this is not an order and is left to the discretion of the claimant. {{{ The certificates are not revoked mandatorily, because * the CPS only requires the name to be assured under Assurance Policy, which it was. * the Assurance Policy itself only requires that the Name, E-Mail and secondary distinguishing feature be known, which they are. * the current PracticeOnNames would suggest that the current account name is actually valid according to current policies and practices. }}} == Execution == . 2009-10-21 (A) (C) and (R) has been notified of the ruling by E-Mail . 2009-10-21 (A) support@c.o has been requested to change the account by E-Mail as requested . 2009-11-11 (A) notification from support: change done, was also sent to involved parties . 2009-11-11 (A) case closed. == Similar Cases == . [[Arbitrations/a20070921.1|a20070921.1]] [[Arbitrations/a20070921.1|mismatch issued name and name on passport]] . [[Arbitrations/a20071023.1|a20071023.1]] [[Arbitrations/a20071023.1|mismatch issued name and name on CAP form]] . [[Arbitrations/a20080604.1|a20080604.1]] [[Arbitrations/a20080604.1|change assured 35 p name to name as on ID]] . [[Arbitrations/a20090618.4|a20090618.4]] [[Arbitrations/a20090618.4|User registered under nickname ]] . [[Arbitrations/a20090621.1|a20090621.1]] [[Arbitrations/a20090621.1|User not registered under full first name]] . [[Arbitrations/a20090828.1|a20090828.1]] [[Arbitrations/a20090828.1|request for name change]] . [[Arbitrations/a20090621.2|a20090621.2]] [[Arbitrations/a20090621.2|User not registered under full names ]] ---- . CategoryArbitration . CategoryArbCaseAccountDataNameMismatch