. '''To CAcert.org''' '''[[Brain#CAcert.org_Education_&_Training| Education & Training]]''' - '''To CAcert.org Education & Training''' '''[[Brain/EducationTraining| Overview]]''' . '''To [[http://www.cacert.org/policy/AssurancePolicy.php|Assurance Policy]]''' - '''To [[AssuranceHandbook2| Assurance Handbook]]''' [[PracticeOnNames/CZ|česky]] | '''english''' ---- == Practice on Names == Currently this is an interpretation based on the Assurance Policy at http://www.cacert.org/policy/AssurancePolicy.php#2.1 to specify more clearly how to match names found in official ID documents with names stored in CAcert accounts. It is intended to be a bit on the safe side and might be more restrictive as the policy itself. Also the interpretation concentrates on "western names". Though some thought has been given to other regions, it might be not suited well to special situations. If you encounter such a situation, feel free to explain it on the [[mailto:cacert-education@lists.cacert.org|Education mailing list]]. ''Non-policy Notes:'' * ''--(This probably belongs in the Assurance Policy.)--'' * ''--(This needs a linkage from Assurance Handbook that clearly explains what are the rules, how much we can rely on this document. I.e., either this document is acceptable and approved practice in Names variations as per AP, or it is ... not!)--'' * ''--(There were some discussions on -policy about this during April which should be considered first. [samj])--'' * ''There needs to be a linking into the CPS on how the Names are used.'' * ''This document is now part and included in the Assurance Handbook'' === General Standard === It is preferred that the name used in the account can be matched exactly to the name as written in at least one government-issued Identity document. For several reasons some deviations of this preferred standard are accepted. <> === Basic, Simple, Strict Rules === 1. '''We assure only names, that we can find in at least one ID document.''' {{{#!wiki red/solid '''We assure only names, that we can find in at least one ID document.''' }}} 1. '''Its allowed to reduce information, but its prohibited to add information.''' (The data of the ID documents does not have to be used completely, that is not all given names have to be used and names may be abbreviated under certain circumstances.) {{{#!wiki red/solid '''Its allowed to reduce information, but its prohibited to add information.''' }}} 1. '''Always document missing names on the CAP.''' (A person may have multiple names as long as they are verifiable with official ID documents) {{{#!wiki red/solid '''Document missing names on the CAP.''' }}} 1. '''Transliterations are accepted''' because of technical reasons (8bit to 7bit conversions) {{{#!wiki red/solid '''Transliterations are accepted''' }}} 1. We use '''Case-Insensitive''' {{{#!wiki red/solid '''Case-Insensitive''' }}} ==== Clarifications ==== * It is always preferred to have the name(s) in the account exactly like the name(s) in the ID documents. * Translations of names (Matthew <-> Matthias) are not accepted (Reason: it is too complicated to verify translations) * Initials of first and middle names are depreciated but accepted (Reason: Rule #2, but this may be open for discussion. Maybe at least one given name should be used completely?) * Middle names and academic titles may be omitted (Reason: Rule #2) * Diacritical marks (accents and similar things) may be omitted (Reason: Rule #4) * If transliteration is used it has to be used on the whole name, result must be 7-bit ASCII (Reason: Otherwise technical reasons are not plausible) * In general names are handled case insensitively. If usage of different cases is very unusual or could indicate abuse, a dispute should be filed to clarify the specific case. ==== Examples ==== Allowed Variations || '''Name(s) in ID doc''' || '''Name(s) in CAcert account''' || '''Remarks''' || || Bärbel Renate Fröhlich || Bärbel Renate Fröhlich || preferred variant || || Bärbel Renate Fröhlich || Renate Bärbel Fröhlich || ordering of given names is arbitrary || || || Baerbel Renate Froehlich || Transliteration || || || Bärbel Fröhlich || middle name omitted || || || Renate Fröhlich || first name omitted || || || Bärbel R. Fröhlich || acceptable since two name parts (including the family name) are complete || || Dr. Bärbel Fröhlich || Bärbel Fröhlich || like middle names, academic titles may be omitted || || Κάρολος Παπούλιας || Κάρολος Παπούλιας || preferred variant || || || Karolos Papoulias || Transliterated according to ISO 843 || || Κωνσταντίνος Καραμανλής || Konstantinos Karamanlis || ISO 843, diacritical marks omitted || || Борис Николаевич Ельцин || Boris Eltsin || According to [[AcceptableDocuments/Russia|AcceptableDocuments]] this would be the "official" translation in the passport. Note that if the translated/transcribed name is contained in a ID document this translation should be preferred to manual transliteration using ISO or other rules. || || Anis Mohamed Youssef Ferchichi, artist name Bushido || Bushido || if an artist name is included in official ID documents it may be used in a CAcert account. || || || Anis Mohamed Youssef Ferchichi || of course the "official" name may also be used || || Peter de Vries || Peter de Vries || where: 'Peter' is the given name and 'de Vries' is the last name (preferred variant); see also Dutch usage of [[http://en.wikipedia.org/wiki/Tussenvoegsel|Tussenvoegsels]]; there exists no lists in the CAcert system that needs special name ordering; see also [[Arbitrations/a20090618.9|a20090618.9]] on how to entering [[http://en.wikipedia.org/wiki/Tussenvoegsel|Tussenvoegsels]] into the system || || Paulus de Vries || Paul de Vries || known NL country variation (read below). Requirement: citizen of the Netherlands || || Hans-Peter Fröhlich || Hans Fröhlich || It is allowed but deprecated for german people. See the chapter on "[[#HyphenRule|Hyphen Rule]]" below. || Forbidden variants || '''Name(s) in ID doc''' || '''Name(s) in CAcert account''' || '''Remarks''' || || Bärbel Fröhlich || Bärbel Froehlich || either transliteration everywhere or nowhere || || Bärbel Froehlich || Bärbel Fröhlich || transliteration works only one way || || Bärbel Fröhlich || Bärbel Renate Fröhlich || Middle name is not in ID documents || || Bärbel Fröhlich || Bärbel F. || Family name must not be abbreviated. Even if all names are given names, like for example in Indonesia, at least two names must be included without abbreviations (if present). || || || Fröhlich || If there is a given name in the docs at least one has to be used. || || Bärbel Fröhlich || Dr. Bärbel Fröhlich || Academic titles, like middle names, have to be contained in at least one ID document to be assured || || Bärbel Renate Fröhlich || B. R. Fröhlich || At least one given name must be used completely. || || Борис Ельцин || Boris Jelzin || not transliterated but transcribed (translated phonetically) || || William Gates || Bill Gates || Though a usual nickname it is not acceptable, since it cannot be found on any document. || || Matthias Beckett || Matthew Beckett || No translation of names || Note: If ID documents for other alphabets also contain the name(s) in Latin characters, like many passports do, these would be acceptable even if not conforming to ISO transliteration rules, because they are contained in official documents. <> ===== Practice on Suffix ===== see [[http://en.wikipedia.org/wiki/Suffix_%28name%29|Wikipedia Suffix (name)]] Suffixes are often a problem and leads into arbitrations, as suffixes mostly not added into ID docs. But this isn't noticed onto the join form :( Despite the fact there is a link on the join form, most suffixes cannot be accepted, 'cause they are not listed in any ID docs. So the simple rule here is: prevent adding suffixes and only accept suffixes you may find in at least one ID doc. If you find a suffix in the online account, ask the assuree, to correct his name in the online account or if once received assurance points, ask Assuree to file a dispute. * read also: ''Potential precedent case: [[Arbitrations/a20110119.1|a20110119.1]]'' (... to process name change requests which are transitions satisfying the requirements of PracticeOnNames.) <> === Relaxed Rules === The relaxed rules follows the general strategy as defined at [[Assurance/PracticeOnIdChecking#CCA-AP-requirement|PracticeOnIDChecking - CCA/AP requirements]] {{{ Hence, the Assurance Statement goes some distance to detune or soften the need for pure identity documents ... as long as we can reliably get the guy to Arbitration, the precise Name and Documents matter less. }}} ==== Top Down Procedure to handle Strict and Relaxed Rules ==== . {{attachment:ProcessNames3.png|Top Down Procedure to handle Strict and Relaxed Rules|align="center"}} || 1. || First check on Strict Rules || Can case be handled under Strict Rules? || Pass, otherwise continue 2. || || 2. || Second, check on Relaxed Rules || Can case be handled under Relaxed Rules? || Pass, otherwise continue 3. || || 3. || File Dispute || Bring case before an Arbitrator || Await ruling || ==== Relaxed Rules: Extended Assurers task ==== All cases that ends with '''Not Passed''' have to be passed to Arbitration or to the Assurance team for a review. Follow the simple rule: document all Names you've read an ID doc, and all names of all the ID docs you've get presented (e.g. use backside of the CAP form) {{{#!wiki red/solid One of the requirement to allow relaxed rules is the quality in documentation by the assurers. In case of an arbitration, the Arbitrator can request required infos from the Assurer. If documentation is missing or is incomplete, the Assurer and CAcert has a problem. }}} <> === Hyphen Rule === For the purposes of checking the Name against PoN, a hyphen in given names is to be treated as '''OPTIONAL'''. The reasons for this are detailed in the Arbitration Precedents Case [[Arbitrations/a20100302.1|a20100302.1]]. ---- --(Since, in contrary to other countries, German custom and practice considers the hyphen as an essential part which connects two given names to one single name, German members are advised to use names in their account accordingly.)-- --(But since it is not possible for Assurers to verify every aspect of name customs it is considered acceptable to leave out the hyphen and treat two hyphenated names as different names if the member insists on it.)-- --(So acceptable variants are:)-- ## || '''Name(s) in ID doc''' || '''Name(s) in CAcert account''' || '''Remarks''' || ## ||<|5> Hans-Peter Meier || Hans-Peter Meier || Preferred variant! || ## || Hans Peter Meier || deprecated but allowed if the member insists || ## || Hans Meier || deprecated but allowed if the member insists || ## || Peter Meier || deprecated but allowed if the member insists || ## || Peter Hans Meier || deprecated but allowed if the member insists || ## '''Note:''' When insisting on one of those deprecated variants a German member might violate German regulations, and might be liable for that (please consult a lawyer to find out if this indeed is the case). CAcert can not enforce every aspects of national laws and customs. --('''Note:''' CAcert can not and will not enforce every aspects of national laws and customs. )-- ---- . (from [[Arbitrations/a20100302.1|a20100302.1]]) Further I rule, to add this sample into the PracticeOnNames as a default rule, to make the usage of hyphen in Givennames optional: {{{ For the purposes of checking the Name against PoN, a hyphen in given names is to be treated as optional. Although under some codes of law and naming customs the hyphen is considered non-optional, it is optional under common-law tradition (cacert's family of law), and our global community has many customs. These influences push us to be more inclusive than restrictive in naming practices. }}} Principle regarding Assurance Statement is: {{{ a) select the law under which Assuree / Assurer agrees to check the name local law or common law b) dependent on the law, the Assurer has to give his Assurance Statement Assurer has to accept Assuree's decision but Assurer gives his Assurance Statement. In mind, that the full name as seen in users IdDoxs is documented onto the CAP form, it doesn't causes to decrease Assurance points as it fulfills the requirements for AP and Arbitration if the Assurer has confidence into the members identity. }}} So acceptable variants are: || '''Name(s) in ID doc''' || '''Name(s) in CAcert account''' || '''Remarks''' || ||<|5> Hans-Peter Meier || Hans-Peter Meier || Preferred variant! || || Hans Peter Meier || optional (allowed) variant || || Hans Meier || optional (allowed) variant || || Peter Meier || optional (allowed) variant || || Peter Hans Meier || optional (allowed) variant || '''Note:''' CAcert can not and will not enforce every aspects of national laws and customs. === Country variations === Note the Arbitration precedent set in [[http://wiki.cacert.org/Arbitrations/a20120115.2 | a20120115.2]] allows for most, if not all, of the known country variations listed below - however that listing is retained as it contains useful reference material for those from outside the countries concerned. {{{#!wiki yellow/solid Based on the more general case made by the Assurance Officer with the introduction of "Relaxed Rules" for assurance, I also rule that any assurer can legitimately assure a person where the name on the assuree's account does not tally exactly with their ID Documentation '''provided that the following conditions are met''' 1. the assurer documents exactly the names that were seen on the assuree's ID documents 1. the assurer is convinced that the Account name, the assuree and the documentation all relate to the same individual and that the Account name is reasonable with respect to the assuree's name ''(If the names are vastly different and particularly if the account name is that of a well-known person, alarm bells should ring in the assurer's mind!)'' 1. that the Risks/Liabilities/Obligations are disclosed to and understood by the assuree 1. the assurer is satisfied that the assuree accepts the CCA 1. the assurer is convinced that the assuree can be brought into arbitration if needed. If these conditions are not met, there is the fallback option of filing a dispute for arbitration. According to AP 2.2. Multiple Names and variations, I've set this case as a precedent under "different country variations" for Assurers }}} regarding [[http://www.cacert.org/policy/AssurancePolicy.php#2.2._Multiple_Names_and_variations|AP 2.2. Multiple Names and variations]] The Known Country Variations section gives advice to the Assurers, how they can handle Names according to the descriptions given in each individual section Known Country Variations: * NL * [[http://en.wikipedia.org/wiki/Tussenvoegsel|Tussenvoegsels]] * [[Arbitrations/a20090618.12|a20090618.12]] Abbreviations on given names are allowed under the given circumstances (read ruling of case a20090618.12) advanced by ruling [[Arbitrations/a20091128.2|a20091128.2]] * [[http://www.meertens.knaw.nl/voornamen/vnb/|Nederlandse Voornamen Databank]] {{{#!wiki note * To the Assurers: . Starting 2009 with the ATE's Assurers learned to allow only such names in Account that match the ID docs (strictly). However, as the name rules are in flux, the Dutch "roepnaam" problem hasn't been investigated deeply before the first dispute filings started. Since the ruling of precedents case [[Arbitrations/a20090618.12|a20090618.12]] new infos received the Assurance Officer and also the Arbitrators about an existing '''[[http://www.meertens.knaw.nl/voornamen/vnb/|Nederlandse Voornamen Databank]]'''. So on any doubt also international Assurers can check Dutch common short name variations against the name found in the ID doc. But consider, this rule is '''no''' clearance for general [[http://en.wikipedia.org/wiki/Nickname|Nicknames]]. Like me, my given name is Ulrich. This is every time a problem for people from Anglo-American culture to speak, so I moved to the "Rufname" or "roepnaam": Uli. This is to read as a [[http://en.wikipedia.org/wiki/Nickname|Nickname]], because a. it doesn't follow the Dutch common short name variation (country variation, that is allowed under AP 2.2), from the [[http://www.meertens.knaw.nl/voornamen/vnb/|Nederlandse Voornamen Databank]]: Ulrich relates to Oldrik a. I'm not a citizen from the Netherlands, so the Dutch country variation doesn't apply }}} * '''ij''' vs. '''y''' ([[http://en.wikipedia.org/wiki/Digraph_(orthography)|digraph]]) - '''Y''' is a known common substitution in the dutch language for '''IJ''' (see references [[https://wiki.familysearch.org/en/Netherlands_Language_and_Languages#LANGUAGE_CHARACTERISTICS|Netherlands Language and Languages (Alphabetical Order)]] and [[http://en.wikipedia.org/wiki/IJ_(digraph)]]) (added 2011-02-07 by AO). . Definition: In the Dutch language, the letter combination ij is considered a single letter. It has the same value as y, and it is usually alphabetized as if it were a y. . (see also: [[http://www.indonesianhistory.info/pages/place-name-spelling-issues.html|Indonesian place name spelling issues]]) * BE * As Belgium is bilingual you have to decide whether you are dealing with a Flemish firstname "roepnaam" then see the Netherland country variations. If you are dealing with French first names see the French country variations. <
>''Please contact Assurance Officer if you have further details so we can update these infos.'' * China * ''Personal names in Chinese culture follow a number of conventions different from those of personal names in Western cultures. Most noticeably, a Chinese name is written with the family name first and the given name next, therefore "John-Paul Smith" as a Chinese name would be "Smith John-Paul". For instance, the basketball player Yao Ming should be addressed as "Mr. Yao", not "Mr. Ming".'' * To prevent missusage, a Chinese name has to be entered into the online system as defined: * Givenname(s) into the Givenname and/or Middlenames field(s) * Lastname / Surname into the Lastname field * Please mark on your CAP form, which Name part is the Givenname and which Name part is the Lastname as read in an ID doc * The resulting Names line has to be read: Givenname(s) Lastname * If this doesn't happen in the online form, you cannot finish the Assurance, and the Assuree has to correct his name in the Online Account * By transferring the Assurance from the CAP form to the Online form, and you read the names switched around, ask the Assuree to correct his name in his Online account or file a dispute for name correction (Givenname / Lastname switched around case) * Further readings about Chinese names: [[http://en.wikipedia.org/wiki/Chinese_name]] * Spain * [[http://en.wikipedia.org/wiki/Spanish_naming_customs#Naming_system_in_Spain|Naming System in Spain]] (also covers hyphenations) * [[http://en.wikipedia.org/wiki/Spanish_naming_customs#Nominal_conjunctions|Nominal conjunctions]] are optional. Nominal conjunctions are for better identification of surnames from other name parts. ID docs probably drops nominal conjunctions. * The particle “de” (from) * The particle “y” (and) (also i, e) * Though Spanish people generally have two surnames, one surname (generally the paternal) is sufficient. Portuguese people have up to four surnames, here again one is sufficient. * FR * In French culture, the fullname is often written {{{ LASTNAME, Givenname1, Givenname2, .., GivennameN }}} * To prevent missusage, a French name has to be entered into the online system as defined: * Givenname(s) into the Givenname and/or Middlenames field(s) * Lastname / Surname into the Lastname field * The resulting Names line has to be read: Givenname(s) Lastname * If this doesn't happen in the online form, you cannot finish the Assurance, and the Assuree has to correct his name in the Online Account * If a name is written as LASTNAME, Givenname on the CAP form, the Givenname and Lastname part are identifiable as this is a known definition on writing names. * But this format is prohibited in the Online form * By transferring the Assurance from the CAP form to the Online form, and you read the LASTNAME, Givenname variant, ask the Assuree to correct his name in his Online account or file a dispute for name correction (Givenname / Lastname switched around case) * GR * Deliberations on Greek givenname variations can be found under [[Arbitrations/a20091231.2|a20091231.2]] * So there is a known list (may be incomplete) of common Greek givenname variations that are optional a. Γεώργιος/Γιώργος -> Geōrgios/George * [[http://el.wikipedia.org/wiki/%CE%93%CE%B5%CF%8E%CF%81%CE%B3%CE%B9%CE%BF%CF%82_%28%CF%8C%CE%BD%CE%BF%CE%BC%CE%B1%29|Greek version of Wikipedia: Geōrgios/George]] a. Ιωάννης/Γιάννης -> Ioannis/Giannis/John * [[http://el.wikipedia.org/wiki/%CE%99%CF%89%CE%AC%CE%BD%CE%BD%CE%B7%CF%82_%28%CF%8C%CE%BD%CE%BF%CE%BC%CE%B1%29|Greek version of Wikipedia: Ioannis/Giannis/John]] * [[http://en.wikipedia.org/wiki/John_%28given_name%29]] a. Μιχαήλ/Μιχάλης -> Michael/Michalis * [[http://el.wikipedia.org/wiki/%CE%9C%CE%B9%CF%87%CE%B1%CE%AE%CE%BB|Greek version of Wikipedia: Michael/Michalis]] * [[http://en.wikipedia.org/wiki/Michael]] a. Ηρακλής -> Iraklis/Hercules a. Θεόδωρος -> Theodoros/Theodore * [[http://en.wikipedia.org/wiki/Theodore_%28name%29]] a. Αλέξανδρος -> Alexandros/Alexander * [[http://en.wikipedia.org/wiki/Alexander]] * and I am sure there are many more examples...Γεώργιος and Ιωάννης are the two most common greek male names though. a. Νικόλαος -> Nikolaos/Nicholas/Nikolas * [[http://en.wikipedia.org/wiki/Nicholas]] * Indonesia * [[http://en.wikipedia.org/wiki/Indonesian_names]] * There are a couple of Indonesian name variations known. However [[http://en.wikipedia.org/wiki/Mononym#Countries_where_mononyms_are_normal|mononyms]] cannot be entered into the online system yet, as the system requires givenname + lastname to be entered and prevents mononyms (givenname or lastname only) * This issue is currently WIP in Software-Assessment and Policy Group * Please contact Assurance team until this problem is solved for further directions ## . ''[[Iang]]: what does this all mean? "Known Country Variations" ? As an Assurer, I want to know if it is acceptable to treat the "de" as optional, and I want to know if the hyphen in the German name is optional. As an Arbitrator, I want to know if this is approved practice by the AO, so when a dispute comes in, this can be (generically) ruled.'' ## . ''[[u60]]: the 'de' thing under Nominal conjunctions is "optional". The hyphen thing in Germany is not optional. It cannot be abbreviated from Hans-Dieter to Hans as its '''one''' name, but maybe in NL or Spain. But there are other rules regarding Abbreviations on 2nd or 3rd given names/middle names. This isn't covered by this rule'' ''(by the time of writing the below referenced arbitration case [[Arbitrations/a20100302.1|a20100302.1]] had not been ruled, so it reflects previous practice, that is now replaced by the precedent ruling under [[Arbitrations/a20100302.1|a20100302.1]])'' ## . ''[[BernhardFröhlich]]: [[Arbitrations/a20100302.1|a20100302.1]] explicitly states in the ruling that the hyphen is optional for a (seemingly) German member. Therefore I have modified the parts on the hyphen rule (except Uli's comment above) which were explicitly contradicting before.'' === Discussion === ==== CPS / CN ==== This discussion is about Assurance: matching ID documents with the names recorded in a CAcert account. What it is not about, or is less about, is what Name (if any) goes into the CN of certificates. We will need a linking statement in the CPS that states how the names are used. Something like: * Any Name assured to 50 points by the Assurance process may be issued in the CN of a member's certificate * Assurance Policy may provide methods for variations for Names in the CN, such as transliterations and short forms. Just a suggestion. ==== Irish Country Variation ==== * 3 potential variants for one name 1. O'Reilly 1. O Reilly 1. OReilly * source: [[http://restrictedview.blogspot.com/2008/04/oreilly-factor.html|The OReilly Factor]] ==== English Language short forms of names ==== Applies to UK, US, AU, NZ, CA and possibly others<
> There is a whole set of commonly used and standard "short forms" of English forenames. Examples include "Bill" for "William" and "Dick" for "Richard". (see [[http://en.wiktionary.org/wiki/Appendix:English_given_names]] and [[http://www2.elc.polyu.edu.hk/CILL/namesmatching.htm]].) These names are often used by an individual in preference to their formal names (eg "Bill Gates". At least one example is currently awaiting arbiration and a past arbitration has ruled that short forms of names are allowable under AP 2.2 [[https://wiki.cacert.org/Arbitrations/a20090618.12 | a20090618.2 ]] <
><
>I believe that it is worth adding a (non-exclusive) list of names and associated short forms that are allowable under relaxed rules for name matching purposes. Currently the example "Bill Gates" for "William Gates" is specifically not allowed under "Strict" rules but it is not clear whether this would (or should!) be allowable under "relaxed" rules x^1^)- I personally believe that it should be allowable but (particularly for people who are not native English speakers) clarification would help! [[Community/HomePagesMembers/AlexRobertson | Alex Robertson]] * u60 - x^1^) read "Top Down Procedure to handle Strict and Relaxed Rules" ==== Advantages and Disadvantages ==== From former discussion about Relaxed or Strict Rules || Ruleset || '''Advantages:''' || '''Disadvantages:''' || || Strict ||<^> * supports possible objective of exporting identity documents to net<
> * supports possible objective of asserting a "r.i.g.h.t" to a name ||<^> * Does not reflect current practice, therefore:<
> * handling of legacy accounts has to be defined<
> * problem to educate existing assurers, because it is stricter than some government-standard practices (e.g., Germany)<
> * Many problems in details have to be addressed || || Ruleset || '''Advantages:''' || '''Disadvantages:''' || || Relaxed ||<^> * supports possible objective of helping members to use certs ||<^> * Simplifies creation of multiple assured accounts for the same user<
> * Assurers have to be educated about "official CAcert" rules of transliteration<
> * Rules are more complicated (at least at first glance...) || ==== Further readings ==== http://en.wikipedia.org/wiki/Transliteration http://en.wikipedia.org/wiki/List_of_personal_naming_conventions and http://en.wikipedia.org/wiki/Family_name for some background about personal names. [[Arbitrations/a20090618.12|Arbitration Case a20090618.12]]: An example of an accepted country variation. ---- . CategoryAssurance