* Case Number: a20100919.1
  * Status: closed
  * Claimants: Bernd N
  * Respondents: CAcert
  * iCM: UlrichSchroeter
  * Case Manager: BernhardFröhlich
  * Arbitrator: UlrichSchroeter
  * Date of arbitration start: 2010-09-22
  * Date of ruling: 2010-09-23
  * Case closed: 2010-09-24
  * Complaint: Name change after Marriage w/ Assurance

  * Relief: To change the Name as requested

Before: Arbitrator UlrichSchroeter (A), Respondent: CAcert (R), Claimant: Bernd N (C), Case: a20100919.1


== History Log ==
 . 2010-09-19 (issue.c.o) case [s20100919.35]
 . 2010-09-21 (iCM): added to wiki, request for CM / A
 . 2010-09-21 (A): I'll take care about this case
 . 2010-09-21 (CM): I'll take care about this case
 . 2010-09-22 (A): Initmailing sent to (C)
 . 2010-09-22 (C): accepts CCA / DRP under this arbitration
 . 2010-09-22 (A): contacting 4 Assurers who assured (C) at SFD to confirm name change request
 . 2010-09-22 (AS2): confirms name change
 . 2010-09-22 (A): name change request includes an Umlaut. So my question to (C) is, if he prefers the name w/ Umlaut or w/o Umlaut, transliterated in his online account
 . 2010-09-22 (C): prefers name w/o Umlaut, transliterated
 . 2010-09-23 (AS1): confirms name change

== Discovery ==
 * 4 Assurers assured (C) at [[events/SoftwareFreedomDayHamburg100918|Software Freedom Day Hamburg]]
 || Assurer# || Assurer name || replied || confirms req ||
 || AS1      || Martin G     ||  {+}    ||  {+}         ||
 || AS2      || Sven U       ||  {+}    ||  {+}         ||
 || AS3      || Rolf W       ||         ||              ||
 || AS4      || Michael B    ||         ||              ||
  * 2 Assurers confirmed name change after marriage as requested by (C)

 * PracticeOnNames rules for names after marriage
  * The hyphen connects two lastnames (after marriage)
   {{{
sample: Mr Mustermann married Mrs Nix geb. Beispiel

    * Male  : Mustermann
    * Female: Mustermann geb. Beispiel
    * Female: Mustermann-Beispiel geb. Beispiel
    * Female: Beispiel-Mustermann geb. Beipiel
    * Female: Nix-Mustermann geb. Beispiel
    * Female: Mustermann-Nix geb. Beispiel

O r
    * Female: Beispiel
    * Male  : Beispiel geb. Mustermann
    * Male  : Beispiel-Mustermann geb. Mustermann
    * Male  : Mustermann-Beispiel geb. Mustermann
Source: http://www.hanau.de/lebeninhanau/familie/standesamt/eheschliessung/artikel/00827/
Date: 2009-10-16
}}}

 * Assurers short rule (from [[AssuranceHandbook2|Assurance Handbook]])
  {{{
  For names or name parts:
  * in general: its allowed to reduce information, but it is prohibited to add informations
}}}
  * sample 1 (Male) : Mustermann-Beispiel geb. Mustermann
  * sample 2 (Male)  : Mustermann-Beispiel
  * so sample 2 is allowed

 * User requested name change that includes an Umlaut
  {{{
  * AP 2.2. Multiple Names and variations

In order to handle the contradictions in the above general standard, a Member may record multiple Names or multiple variations of a Name in her CAcert online Account. Examples of variations include married names, variations of initials of first or middle names, abbreviations of a first name, different language or country variations, and transliterations of characters in a name. 
}}}
  * (C) has been asked which variant he will prefer
  * (C) answer was to use his name w/o Umlaut in online account, so transliterated

 * Certificates issued after 2009-11-08 (date when CPS became draft) needs to be checked
  * The certs problem on Name changes
   * The [[http://www.cacert.org/policy/CertificationPracticeStatement.php|CPS]] comes to draft at Status: DRAFT p20091108
   * The user issued probably client certificates, with the not yet corrected name in the account
   * [[http://www.cacert.org/policy/CertificationPracticeStatement.php|CPS]] 3.1.1. Types of names - Client Certificates. The Subscriber Naming consists of:
    * CN= The common name takes its value from one of: 
     * For individual Members, a Name of the Subscriber, as Assured under AP.

== Ruling ==
 * I hereby rule, that the name in the users account should be changed to the name as requested, by using the transliterated Umlaut (AP 2.2, [[AssuranceHandbook2|Assurance Handbook]], PracticeOnNames)
 * Transliteration of Umlaut doesn't conflict with the confirmations received nor with future assurances (AP 2.2)
 * Client cert problem (CPS)
  * A client certificate may include the name from before marriage. Following the short rule "in general: its allowed to reduce information, but it is prohibited to add informations". After name change the client cert has less informations available as in users online account. So here there is no conflict. AP 2.2 example of variations include married names
  * no revocation of client certs is required

Frankfurt/Main, 2010-09-23

== Execution ==
 * 2010-09-23 (A): ruling sent to (C), (CM), (Support)
 * 2010-09-23 (A): Support, please change (C)'s lastname in account as requested with transliteration of Umlaut
 . 2010-09-23 (AS3): confirms name change
 . 2010-09-23 (AS4): confirms name change
 . 2010-09-24 (Support): Name change req has been executed [s20100923.2]
 . 2010-09-24 (A): Thanks to Assurers and (C), case closed

== Similiar Cases ==
|| [[Arbitrations/a20091111.1|a20091111.1]] || [[Arbitrations/a20091111.1|Member requests name change after marriage]] ||
|| [[Arbitrations/a20100825.1|a20100825.1]] || [[Arbitrations/a20100825.1|Name Change Request after marriage]] ||

----
 . CategoryArbitration
 . CategoryArbCaseAccountDataNameModificationsRequested