Collected Precedents of the S.C.A.:
Rules for Submission (RfS) Cites


Name Precedents: Rules for Submission (RfS) Cites

Laurel: Date: (year.month.date) Precedent:
 
RfS I.3 "Inappropriate Claims"
François la Flamme 2002.08 [Damosels of Astolat] No documentation was presented and none was found that Damosels of Astolat meets the requirements set down in RfS III.2.b.iv which states:

Household names must follow the patterns of period names of organized groups of people. Possible models include Scottish clans (Clan Stewart), ruling dynasties (House of Anjou), professional guilds (Bakers Guild of Augsburg, Worshipful Company of Coopers), military units (The White Company), and inns (House of the White Hart).

With regards to this submission, no evidence was found that Damosels is a reasonable designator for an organized group of people. Additionally, Astolat was documented only as a placename from Mallory's Le Morte d'Arthur. No support was provided and none was found that a placename only documented from literature is appropriate in a household name.

Additionally, were these issues addressed, the combination Damosels of Astolat violates RfS I.3, Inappropriate Claims, which states, "No name or armory will be registered which claims for the submitter powers, status, or relationships that do not exist." Bright Leaf explains:

As the documentation provided notes, Astolat appears in Malory's Le Morte d'Arthur. Elaine le Blanke, who seduces Launcelot, is known as the Fair Maiden of Astolat (which is the origin of Tennyson's Maiden of Shallot). The term damosel (spelled damesell in my edition of Malory) is used frequently in addressing young women in Le Morte d'Arthur. The combination of this form of address with the unique place name Astolat makes me think that the members of this household are claiming a connection to the Arthurian legend.

The combination of elements in the submitted Damosels of Astolat, all of which were documented in the submission only from Arthurian legend incidently, implies identity with the Arthurian character and so is not registerable. [Celestine Albret de Morat, 08/2002, R-Meridies]

 
RfS III.1 "Compatible Naming Style and Grammar - Name Grammar and Syntax"
François la Flamme 2004.01 This name is being returned for a combination of issues.

Briana is a literary feminine given found in Spanish and English in late period (see the Cover Letter for the December 2001 LoAR for details). Bronwen is an SCA-compatible Welsh feminine given name. Regarding Du Bois, the LoI stated:

Du Bois is found in "French Surnames from Paris, 1421, 1423 & 1438" by Aryanhwy merch Catmael (http://www.ellipsis.cx/~liana/names/paris1423surnames.html), with this spelling dated to 1421 and 1423.

In fact, the spelling dated to 1421 and 1423 in that source is du Bois not Du Bois.

Therefore, this name has one weirdness for an element (Bronwen) that is SCA compatible. Additionally, this name (at best) combines Welsh, English, and French in a single name. The LoI did not address whether such a combination complies with RfS III.1, which states in part, "Each name as a whole should be compatible with the culture of a single time and place". At best, such a combination is a weirdness. Alternatively, it is not registerable. Regardless, this name has one weirdness for use of the SCA-compatible element and at least one weirdness for the lingual combination, and is, therefore, not registerable.

As the submitter allowed no major changes, we were unable to drop the element Bronwen and register her name as Briana du Bois. [Briana Bronwen Du Bois, 01/2004, R-Outlands]

François la Flamme 2003.10 Submitted as Kathelyne Fraser of Loch Dubh, the submitter requested authenticity for 15th C Scottish and allowed any changes. [...]

The byname of Loch Dubh mixes the English of with the Gaelic words Loch and Dubh, thereby violating RfS III.1.a, which requires linguistic consistency within a name phrase.

Johnston lists dates a number of placenames in Scotland that include the elements Loch and Dubh, including (p. 240 s.n. Lochbuie) Lochbuy dated to 1549 and (p. 218 s.n. Kilduff) Rossdoy dated to 1595. From these examples, Lochdoy is a reasonable 16th C Scots form of this placename. We have changed the byname to the completely Scots form of Lochdoy in order to register this name. [Katherine Fraser of Lochdoy, 10/2003, A-Artemisia]

François la Flamme 2003.08 This name combines an Anglicized Irish feminine given name with a Romany placename. However, no evidence was provided showing that Anglicized Irish and Romany were spoken in the same location in the same time period. Lacking such evidence, this lingual mix is not registerable as it does not meet RfS III.1, which states in part "As a rule of thumb, languages should be used together only if there was substantial contact between the cultures that spoke those languages [...] Each name as a whole should be compatible with the culture of a single time and place." Lacking evidence that Anglicized Irish speakers and Romany speakers had substantial contact in period, this combination is not registerable. [Ena Weshen-eskey gav, 08/2003 LoAR, R-Atenveldt]
François la Flamme 2003.08 Submitted as Pierre von Vorman RaKogscy de Saint Germain, there were a number of issues with this name. [...]

As submitted, this combined French (Pierre and de Saint Germain), German (von Vorman), and Hungarian (RaKogscy) in a single name. Lacking evidence that there was a time and place that these three languages would have been spoken at the same time, this combination violates RfS III.1, which states in part, "Each name as a whole should be compatible with the culture of a single time and place." [...]

Lacking support for the form RaKogscy, and lacking evidence that French, German, and Hungarian would plausibly be combined in a name in period, we have dropped this element in order to register this name. [Pierre Vorman de Saint Germain, 08/2003 LoAR, A-Meridies]

François la Flamme 2003.04 This name is being returned for combining a Welsh given name with a Hungarian descriptive byname. al-Jamal addressed the documentation for Welsh-Hungarian contact provided in the LoI:

The closest to real documentation for a combination Welsh/Hungarian name that the LoI comes is a statement about the plausibility of an assumption "that there was, at least one, Welshman who went on Crusade to Jerusalem amongst the plethora of English" or "that there was, at least one, Welshman who went on Pilgrimage to the Holy Land ... most likely via Hungary", and alluding to the presence of the Benedictine Order in both the British Isles and in Hungary (without taking into consideration at all the likely or even possible nationality of its members). RfS III.1. states that: "As a rule of thumb, languages should be used together only if there was substantial contact between the cultures that spoke those languages...." (Emphasis added) Assumptions, even without arguing their plausibility, are not evidence of "substantial contact".

Lacking evidence that Welsh and Hungarian cultures had substantial contact, this name is not registerable. [Aneirin Nevetség(es), 04/2003 LoAR, R-Trimaris]

François la Flamme 2002.07 Dorothea was submitted under the Legal Name Allowance as it is the submitter's legal given name. Elements of a submitter's legal name are registerable under the Legal Name Allowance. However, if the other elements in the name, when combined with the element from the submitter's legal name, produce a combination that is excessively obtrusive, the name may be returned per the precedent:

While we allow real-world name elements in SCA names without further documentation, this is restricted to cases where "such elements are not excessively obtrusive." Combining a Gaelic Irish given name with what appears to be a non-European surname falls afoul of this restriction. [Ciarmhac Sayenga, 07/00, R-Æthelmearc]

Dorothea is documentable as a German given name and a late period English given name. Either way, this submission combines three languages. There was considerable discussion about the registerability of a name with this lingual combination. A name combining three languages is registerable, so long as the lingual mix complies with RfS III.1, which states:

Names should generally combine elements that are all from a single linguistic culture, but a name may be registered that combines languages. As a rule of thumb, languages should be used together only if there was substantial contact between the cultures that spoke those languages, and a name should not combine more than three languages. Each name as a whole should be compatible with the culture of a single time and place.

So, the question is whether a mix of English, Italian, and French or a mix of German, Italian, and French is plausible for "the culture of a single time and place". Neither of these combinations have been demonstrated to fulfill this requirement. Lacking such documentation, these combinations are not registerable.

However, because Dorothea was submitted under the Legal Name Allowance, the question becomes whether combining Dorothea in an otherwise Italian and French name is excessively obtrusive. Given that the Italian name Doratea is documented to 1427 in Arval Benicouer's article "Feminine Given Names from the Online Catasto of Florence of 1427" (http://www.s-gabriel.org/names/arval/catasto/), the inclusion of Dorothea is not excessively obtrusive and this combination is registerable. [Dorothea Micola d'Isigny, 07/2002, A-Atenveldt]

François la Flamme 2002.03 Submitted as Nastas'ia Rosenzweig, this name mixes Russian and German, which was ruled registerable, though a weirdness, in the August 2001 LoAR (s.n. Tatiana Heinemann). RfS III.1 states that "Each name as a whole should be compatible with the culture of a single time and place". Therefore, we have modified the given name to a transliteration that is consistent with German orthography. [Nastasiia Rosenzweig, 03/2002, A-Atlantia]
Da'ud ibn Auda (2nd tenure, 2nd year) 1994.12 An English given name plus a locative surname plus a Scots Gaelic patronym from a Norse given does not follow the naming practices or models of either English or Gaelic. (See RfS III.1., "Name Grammar and Syntax - All names must be grammatically correct for period names and follow documented patterns.") (Da'ud ibn Auda, LoAR December 1994, p. 12)
Da'ud ibn Auda (2nd tenure, 2nd year) 1994.12 The combination of German forename and Gaelic byname needs justification, at the very least. None of the commenters noted any German/Gaelic interaction in period (see, e.g., RfS III.1., "As a rule of thumb, languages should be used together only if there was substantial contact between the cultures that spoke those languages." (Da'ud ibn Auda, LoAR December 1994, p. 10)
Da'ud ibn Auda (2nd tenure, 2nd year) 1994.09 The name combines in a single phrase two different languages (Norse and Gaelic), and thus falls afoul of RfS III.1. Name Grammar and Syntax ("Names should generally combine elements that are all from a single linguistic culture") and III.1.a., Linguistic Consistency ("Each phrase must be grammatically correct according to the usage of a single language"). (Da'ud ibn Auda, LoAR September 1994, p. 17)
 
RfS III.1.a "Compatible Naming Style and Grammar - Name Grammar and Syntax - Linguistic Consistency"
Shauna of Carrick Point 2004.05 Listed on the LoI as Alric æt Mæidesstana, the preposition was submitted as of but changed to æt in kingdom in the belief that æt was the Old English equivalent of the modern English of. As the Old English preposition meaning of is of, we have returned this name to the originally submitted form. [Alric of Mæidesstana, 05/04, A-Aethelmearc]
Shauna of Carrick Point 2004.05 Submitted as Erika of Öland, this name has two problems. [...]

The byname combines the English preposition of with a Swedish locative. RfS III.1.a states "In the case of place names and other name elements frequently used in English in their original form, an English article or preposition may be used." However, as English does not use umlauts, Öland cannot be a form used in English. Therefore, we have changed the preposition to the Swedish av to make the byname phrase linguistically consistent. [Eericka av Öland, 05/04, A-East]

Shauna of Carrick Point 2004.05 The element al-Mãkdukht had several problems. First, al-Jamal states that Mãhdukht is a transcription error for M{a-}hdukht The name M{a-}hdukht is a Persian name; combining it with the Arabic al mixes Persian and Arabic in a single name phrase, in violation of RfS III.1.a. The byname al-Zarqá has a transcription error as well; the correct form is al-Zarqa'. In order to register the name, we have dropped the problematic elements and corrected the transcription of the remaining parts, giving M{a-}dukht al-Zarqa'. [M{a-}hdukht al-Zarqa',05/04, A-Trimaris]
Shauna of Carrick Point 2004.04 Finally, the name combines a German preposition with a Lithuanian name in the same name phrase. The Rule for Submission III.1.a says "Each phrase must be grammatically correct according to the usage of a single language." Barring documentation that Risna is a German form of this place name, these two words cannot be combined in a name phrase. A better alternative would be to use an appropriate Lithuanian form for the locative byname. However, since we do not know the appropriate form for the place name, we are unable to suggest its byname form. [Katherne von Risna, 04/04, R-Lochac]
François la Flamme 2004.03 The byname inghean Domnaill combines the Early Modern Gaelic (c. 1200 to c. 1700) form inghean with the Middle Gaelic (c. 900 to c. 1200) form Domnaill and, so, violates RfS III.1.a, which requires linguistic consistency within a name phrase. The form ingen Domnaill is a fully Old Gaelic (c. 700 to c. 900) and Middle Gaelic (c. 900 to c. 1200) form. The form inghean Domhnaill is a fully Early Modern Gaelic (c. 1200 to c. 1700) form. [Cyneswith a bíth inghean Domnaill, 03/2004, R-Calontir]
François la Flamme 2004.03 Submitted as Shire of Bull Pytt, the submission mixed the Old English pytt with the late period English Bull. This combination is not registerable, as it violates RfS III.1.a, which require linguistic consistency within a name phrase (such as a placename). Siren was able to suggest possible registerable forms:

There are several placenames based on <Bul-> 'bull' or perhaps derived from a personal name <Bulla>, including <Bulebrige> c. 1200 (s.n. Bulbridge), <Bulecampe> DB (s.n. Bulcamp), Bulecote DB and 1236 (s.n. Bulcote), and <Bulemere> 1178 (s.n. Bulmer). The spelling <pytt> is unfortunately Old English, not Middle English. Most forms of placenames based on OE <pytt> turn out as <-pet>, but <Pytte> is dated to II DM (s.n. Pett). That may support a c. 1066 <Bulepytte>. Short of that, a hypothetical late period <Bull Pitte> is probably justifiable. There is a placename <Pitt>, spelled <Pette> in 1286 and <Putte> in 1316 (Ekwall s.n. Pitt). R&W (s.n. Pitt) date spellings with <-e->, <-u-> and <-i->. Examples of the last include <Thomas de la Pitte> 1225, <Gilbert atte Pitte> 1294, and <Richard Pyts> 1395. R&W (s.n. Bull) date <William Bull> to t. Henry III. So a place named <Pitte> on the estate of the Bull family might come to be known as <Bull Pitte>.

As Bull Pitte is the closest plausible Middle English form to the submitted Bull Pytt, we have changed the submitted name to that form to register it. [Bull Pitte, Shire of, 03/2004, A-Calontir]

François la Flamme 2004.03 Sudentor was submitted as Middle English with the documentation:

Ekwall notes under Dunster a form Dunstore dated 1138. Under Haytor is noted Eofede torr dated 1323, both of which reference an entry torr, an Old English word meaning "High rock, peak, hill". Under Siddington appears Sudendune, dated to the Domesday book of 1066.

The Middle English Dictionary (Kurath and Kuhn, 1954) under tor notes a placename Torbiri dated 1271 and Blaketorre dated 1296.

However, there are a couple of issues with the proposed form Sudentor. First, the example of Sudendune dated to the Domesday Book is Old English (or a Latinized form of an Old English placename). It is not Middle English.

Second, the cited examples of Dunstore and Eofede torr support -tore as the second element in a dithematic placename and torr as the second word in a two element placename. Neither supports -tor as a Middle English deuterotheme (second half) of a dithematic (two-element, one-word) placename.

As a result, the submitted form Sudentor is actually a mix of Old English and Middle English. RfS III.1.a requires linguistic consistency within a name phrase. Therefore, this name must be changed to a fully Old English or a fully Middle English form in order to be registerable.

Ekwall (s.n. Siddington) dates the form Sudingdone to 1286, showing Suding- as a Middle English form of the earlier Suden-. Therefore, a fully Middle English form of this name would be Sudingtore.

Ekwall (s.n. Dunster) dates the form Torre to the Domesday Book. Therefore, Sudentorre would be a form of this name consistent for the language of the Domesday Book (mainly Latinized Old English).

Of these two forms, Sudentorre is closer than Sudingtore in sound and appearance to the submitted Sudentor. As the submitters allow minor changes, we have changed this name to the form Sudentorre in order to register this name. [Sudentorre, Canton of, 03/2004, A-Atlantia]

François la Flamme 2004.03 The byname ap Erwin does not violate RfS III.1.a, which requires lingual consistency. Though ap was documented as Welsh and Erwin was documented as English, evidence has been found of late period Welsh using English names in bynames that include ap or ferch. This issue has previously been addressed by the precedent:

Found on the LoI as Myfanwy ferch Gerallt, it was originally submitted as Myfanwy ap Gerald, and changed in kingdom because it was felt that the use of ap or ferch needed a Welsh name. However, late period Welsh used ap and ferch with English names, so we have restored the patronymic to the originally submitted form. (LoAR November 1998, p. 4).

As a result, the byname ap Erwin is registerable as a Welsh byname that incorporates an English name, which follows documented period practice. [Rhydderch ap Erwin, 03/2004, A-Æthelmearc]

François la Flamme 2004.03 Submitted as Tuathal O'hAirt, the byname combined the Anglicized Irish O' with the Gaelic hAirt and, so, violated RfS III.1.a, which requires linguistic consistency within a name phrase. As the submitter allows minor changes, we have changed this byname to the fully Gaelic form Ó hAirt in order to register this name. [Tuathal Ó hAirt, 03/2004, A-Atlantia]
François la Flamme 2004.03 There were several issues with the submitted byname O'Muirnea{c.}áin.

The spelling O'Muirnea{c.}áin combined the Anglicized Irish O' with an otherwise Gaelic name, violating RfS III.1.a, which requires linguistic consistency within a name phrase.

This byname was documented from Woulfe (p. 622), which lists the header Ó Muirnea{c.}áin where the notation {c.} represents a c with a "dot" over it. The "dot" over a letter in Gaelic is called a punctum delens. When Gaelic is being represented using the Roman alphabet, letters with the punctum delens are rendered with an appended h; thus, c with a punctum delens becomes ch in standard transliteration. For registration purposes, we use this standard transliteration method.

This entry in Woulfe lists the Anglicized Irish form O Murnyghan to temp. Elizabeth I-James I. The College was unable to find any evidence that this name was used earlier. Therefore, Ó Muirneacháin must be considered a 16th C byname.

Precedent requires that when a Gaelic byname is used, it agree in gender with the given name, since bynames were used literally in Gaelic. Since Ó Muirneacháin is a masculine form, it cannot be registered with a feminine given name. The corresponding feminine form is inghean uí Mhuirneacháin [Muireann O'Muirnea{c.}áin, 03/2004, R-An Tir]

François la Flamme 2004.02 Submitted as Artúr Ó Láegaire, the byname Ó Láegaire combined the Early Modern Gaelic (c. 1200 to c. 1700) Ó with Láegaire, which is an Old Irish (c. 700 to c. 900) or Middle Irish (c. 900 to c. 1200) form. As a result, this byname violated RfS III.1.a, which requires linguistic consistency within a name phrase. We have changed this byname to the fully Old Irish form hua Láegaire in order to register this name. [Artúr hua Láegaire, 02/2004, A-Atlantia]
François la Flamme 2004.02 Submitted as Séamus O'MaoLiriain, the submitter requested authenticity for "1560's Ireland/Scotland (lowlands)" and allowed any changes.

The submitted byname combines the Anglicized Irish O' in an otherwise Gaelic byname. As such, it violates RfS III.1.a, which requires linguistic consistency within a name phrase. Additionally, the submitted documentation supported Ó Maoilriain as a modern Gaelic form of this name, rather than O' MaoLiriain. The Annals of the Four Masters were written in 1632-1636 and, for the most part, use spellings appropriate for 16th C Ireland. In the Annals of the Four Masters, vol. 5, (http://www.ucc.ie/celt/published/G100005E/), entry M1585.8 includes the name Conchobhar na Moinge, mac Uilliam Chaoích, mic Diarmata Uí Mhaoil Riain tigherna Uaitne Uí Mhaoil Riain (the underlined e represents the "long e" character in Gaelic, which is sometimes rendered as ea and sometimes as e in Roman characters, depending upon the word). Based on this example, we have changed the byname to Ó Maoil Riain in order to meet the submitter's request for authenticity. [Séamus Ó Maoil Riain, 02/2004, A-Atlantia]

François la Flamme 2004.02 Submitted as Wolfgang Grothe zu Verron, Verron was documented by the submitter and by the College only as a French place name. As such, the phrase zu Verron combines the German zu with a French place name and, so, violates RfS III.1.a, which requires linguistic consistency within a name phrase. We have changed this byname to the fully French form de Verron in order to register this name. [Wolfgang Grothe de Verron, 02/2004, A-Outlands]
François la Flamme 2004.02 The submitter requested authenticity for 9th to 10th C Irish. The submitted byname ingen Dochartaigh combines the Middle Irish (c. 900 to c. 1200) ingen with the Early Modern Irish (c. 1200 to c. 1700) Dochartaigh and, so, violates RfS III.1.a, which requires linguistic consistency within a name phrase. A fully Middle Irish Gaelic form of this byname would be ingen Docartaig. A fully Early Modern Irish Gaelic form of this byname would be inghean Dochartaigh.

The submitter's name form has the "no minor changes" box checked (though the "no major changes" box is unchecked). A common problem with the current form is that it is not uncommon for submitters to interpret the major and minor changes boxes as a "pick one" setup, where checking the minor changes box also implies that major changes are not allowed. Therefore, in cases where the forms are marked in this manner, we interpret the changes allowed as "no changes".

Regardless, the changes necessary to modify the byname to a registerable form are minor changes, which the submitter does not allow. [Nem ingen Dochartaigh, 02/2004, R-Atlantia]

François la Flamme 2004.01 Submitted as Padraig Ó Taidc, the submitter allowed minor changes to the byname only. The submitted byname Ó Taidc combines Ó, which is an Early Modern Irish Gaelic (c. 1200 to c. 1700) form, with Taidc, which is a Middle Irish Gaelic (c. 900 to c. 1200) form. As a result, this byname violated RfS III.1.a, which requires linguistic consistency within a name phrase. We have changed this byname to the fully Early Modern Irish Gaelic form Ó Taidg in order to register this name. [John de Duglas, 01/2004, A-East]
François la Flamme 2004.01 Submitted as Wulfwyn atte Maeldun, the documentation showed the placename as Mældun, not Maeldun. We have made this correction.

This name combined the Middle English atte with the Old English placename Mældun and, so, violated RfS III.1.a, which requires linguistic consistency within a name phrase. We have changed atte to the Old English æt in order to make the byname fully Old English and register this name. [Wulfwyn æt Mældun, 01/2004, A-Ansteorra]

François la Flamme 2004.01 Listed on the LoI as Milissent  Heathwait, this name was submitted as Milissent du Heathwait. The article du was removed at Kingdom as none of the documented examples of this byname contained an article.

An additional problem with the submitted byname du Heathwait was that it combined the French du 'of the' with Heathwait, which was documented as the modern English form of a location in England. The combination of French and English in a single name phrase violates RfS III.1.a, which requires linguistic consistency within a name phrase.

No evidence was found that an Hea- spelling of this placename is plausible in period. A number of forms of this placename were found dated to period, including in Ekwall (s.n. Heathwaite), which dates the form Haithwait to c. 1175. We have changed this byname to the English form de Haithwait in order to resolve these issues and to make this name sound more like the submitted form (as the submitter indicated that sound was most important). [Milissent de Haithwait, 01/2004, A-East]

François la Flamme 2003.12 The byname Reinarskona combines the Danish masculine given name Reinar with the Old Norse kona 'wife'. While Danish and Old Norse are related languages, they are not the same language. Therefore, the byname Reinarskona violates RfS III.1.a, which requires linguistic consistency within a name phrase. As the submitter allows major changes, we have dropped this element in order to register this name. [Ellisif þunnkárr, 12/2003, A-West]
François la Flamme 2003.12 Submitted as Hubert d'Aquae mortuae, the submitter requested authenticity for 13th C France (southern) and allowed all changes. The LoI provided documentation for the byname d'Aquae mortuae:

Aigués-Mortes: Dauzat, Noms de Lieux page 5 header Aiguebelette gives Aigue-Mortes and a 13th century form of the name Aquae mortuae 1248. It means a place with stagnant water.

Unfortunately, the submitted byname d'Aquae mortuae is violates RfS III.1.a, which requires linguistic consistency within a name phrase. Metron Ariston explains:

The byname mixes French orthography and Latin. If you are going to use the Latin form of the place name, you need to use the Latin preposition and the appropriate ablative form: de Aquis Mortuis. The French form would be d'Aigue Mortes. Either would work with Hubert, but you have to choose French or Latin for the phrase.

In order to meet the submitter's request for authenticity, we have modified this byname based on the dated example provided in the LoI, changing only the cases of the words as recommended by Metron Ariston. [Hubert de Aquis mortuis, 12/2003, A-Ansteorra]

François la Flamme 2003.11 Submitted as Gunnarr of Iorvik, the submitted byname of Iorvik combined the English of and the Norse Iorvik and, so, violated RfS III.1.a, which requires linguistic consistency within a name phrase. The fully Old Norse form of this byname would be í Iórvík. Old Norse names are registerable with accents used or omitted consistently. We have changed this byname to the fully Old Norse form (with accents omitted) in order to register this name. [Gunnarr i Iorvik, 11/2003, A-Meridies]
François la Flamme 2003.11 Submitted as Fj{o,}rleif Rúnólfswyf, the submitted byname Rúnólfswyf combines the Old Norse Rúnólfs- with the English -wyf and so violates RfS III.1.a, which requires linguistic consistency within a name phrase. The Norse word for 'wife' used in bynames is kona, as in �orvé, Végauts kona, found in Lindorm Eriksson's "The Bynames of the Viking Age Runic Inscriptions" (http://www.s-gabriel.org/names/lindorm/runicbynames/). In this case, the two elements are separate words, but in transcriptions, bynames that express relationship often take this form. In other sources, they are written as a single word. Therefore, this would be acceptable either as Rúnólfskona or Rúnólfs kona. As the former is closer to her submitted name, we have made that change. [Fj{o,}rleif Rúnólfskona, 11/2003, A-Meridies]
François la Flamme 2003.10 Listed on the LoI as Pedrog Sylvrbeard, this name was submitted as Pedrog ap Sylvrbeard and was changed at Kingdom because the submitted byname combined the Welsh ap and the English Sylvrbeard in a single name phrase and, so, violated RfS III.1.a, which requires linguistic consistency within a name phrase. The submitter requested authenticity for 10th C "Welch/Norse [sic]" and allowed any changes.

Sylvrbeard was submitted as a constructed English byname. However, no support was provided for either the spelling Sylvr- or -beard in period. All of the period examples of bynames including forms of the elements 'silver' and 'beard' found by the College had the 'silver' element spelled as Silver- or Sylver- and the 'beard' element spelled as -berd. Lacking evidence that Sylvrbeard is a plausible form in period, we have changed the byname to the form Sylverberd in order to register this name. [Pedrog Sylverberd, 10/2003, A-Ansteorra] [Pedrog Sylverberd, 10/2003, A-An Tir]

François la Flamme 2003.10 Submitted as Stella of Lundeia, the submitter requested authenticity for the 12th to 14th C and allowed minor changes. The byname of Lundeia combined the English of with the Latin Lundeia and, so, violated RfS III.1.a, which requires linguistic consistency within a name phrase.

Ekwall (p. 307 s.n. Lundy Island) dates the Latin form Lundeia to 1189 and the English form Lunday to 1281. Reaney & Wilson (p. 288 s.n. Lundy) dates Walter de Lundy to 1305 and John of Lundy to 1499. Based on this information, a fully Latin form of this byname would be de Lundeia. Fully English forms of this byname would be of Lunday, de Lunday, of Lundy, and de Lundy.

Of these forms, the last two English forms, of Lundy and de Lundy, would best match the time period in which Stella was found. (The submitter's documentation shows Stella as dated to 1379.) As the submitter only allows minor changes, and changing the language of a name phrase is a major change, we were unable to change the Latin Lundeia to an English form in order to match the time period for Stella. Changing the language of a particle, such as of, is a minor change rather than a major since the particle is not the substantive part of the byname. Therefore, we have changed the byname to the completely Latin form de Lundeia in order to register this name. [Stella de Lundeia, 10/2003, A-Ansteorra] [Stella de Lundeia, 10/2003, A-Ansteorra]

François la Flamme 2003.10 Submitted as Cáelainn ingen uí Raghailligh, the byname ingen uí Raghailligh combined the Middle Irish (c. 900 to c. 1200) ingen uí with Raghailligh which is an Early Modern Irish Gaelic (c. 1200 to c. 1700) form. Combining these languages in the byname ingen uí Raghailligh violates RfS III.1.a, which requires linguistic consistency within a name phrase. We have changed this byname to the fully Early Modern Irish Gaelic form inghean uí Raghailligh in order to register this name. [Cáelainn inghean uí Raghailligh, 10/2003, A-Ansteorra]
François la Flamme 2003.09 Submitted as Elena neyn Duhile, the submitter requested authenticity for 13th C Scots and allowed all changes.

Scots, a language closely related to English, was spoken in the lowlands and towns of Scotland by the end of our period. The earliest surviving records written in Scots date from c. 1375. Lacking any evidence that Scots was used in the 13th C, it is not possible to make this name authentic for "13th C Scots".

The submitted byname neyn Duhile combined the Scots neyn with Duhile, found in Black (s.n. MacDoual), which states: "Fergus McDuhile in Wigton was juror on inquest at Berwick, 1296, and in the same year as Fergus MacDowilt rendered homage." Given the date, time, and location of the inquest cited by Black, this record was most likely written in Latin or Anglo-Norman French. The Scots form neyn would not be found in a Latin or Anglo-Norman French document, or in any 13th C document. Lacking evidence that any form McDuhile is a Scots form, the byname neyn Duhile combines Scots with either Anglo-Norman French or Latin, and so violates RfS III.1.a, which requires linguistic consistency within a name phrase. Without evidence of a Scots form of McDuhile, we are unable to hypothesize a feminine Scots form of this byname.

However, the vast majority of Scottish records that survive from the period desired by the submitter are written in Latin. These records provide enough information to construct a fully Latin form of the submitted name that is appropriate for 13th C Scotland. Black (p. 6 s.n. Achmuty) dates Elena la Suchis to 1296. Typical Latin construction for a woman's name may be seen in the name Muriella filia Coneval, which Black (pp. 620-621 s.n. Muriel) dates to 1284. Black (s.n. MacDoual) shows that this name corresponds to the modern Scottish Gaelic MacDh�ghaill 'son of Dougal'. This origin can be seen in Dugalli, the Latin byname form corresponding to the submitted Duhile, which is found in the seal for a man who lived in 1296 which reads S' Will' f' Dugalli (Black, p. 217 s.n. Dougalson).

Based on this information, a fully Latin form of the submitted name, appropriate for 13th C Scotland, would be Elena filia Dugalli and would most likely belong to a woman of Scoto-Norman descent. [Elena filia Dugalli, 09/2003 LoAR, A-Trimaris]

François la Flamme 2003.08 [Household name Gwely Caradoc] Listed on the LoI as Clann Caradoc, this name was submitted as Clan Caradoc. The LoI stated that "The submitters note that 'If Clan is unacceptable, please change to correct Welsh designator.'"

RfS III.1.a requires linguistic consistency in a name phrase. As a household name is a single name phrase, the entire household name must be in a single language.

As Caradoc is Welsh, it may not be used with Clann, which is Gaelic, or with Clan, which is Scots or Anglicized Irish. Harpy provided information regarding a word in Welsh that has a close meaning to clan:

In my research, the type of name that seems to correspond best to the Gaelic "clan", in the sense of a group of closely-related individuals with mutual legal and economic obligations, uses the element "gwely", which literally means "bed", but in this context means "a group of closely-related individuals who hold land in common (also the land held by such a group)". These group/place names are normally constructed as "gwely <personal name of common ancestor>" where the ancestor may be identified by a given name or a full personal name or much more rarely by some other descriptor.

Some examples of this type of name from the mid 14th century rental in the Black Book of St. Davids include:

gwele Cradoc ap Duryn~
gwele Ieuan ap Kediuor
gwele Gwylbrid'
gwele redwyth'

Harpy explained that the form gwele found in the examples below is a non-standard spelling used in this source, and that the standard spelling for this time period would be gwely. She also provided the correct form of this household name using Gwely as a designator:

Gwely Caradoc (the near descendents of Caradoc who hold land in common, also the land they hold)

As the submitters allow any changes, we have changed this household name to Gwely Caradoc as recommended by Harpy to make this name completely Welsh in order to register this name. [Mat of Forth Castle and Adekin Caradoc, 08/2003 LoAR, A-Caid]

François la Flamme 2003.08 Submitted as Caitilín ingen Aodha, the submitter requested authenticity for Irish and allowed any changes. The submitted byname ingen Aodha combined the Middle Irish (c. 900 to c. 1200) particle ingen with the Early Modern Irish (c. 1200 to c. 1700) Aodha and so violated RfS III.1.a, which requires linguistic consistency within a name phrase. We have changed this byname to the fully Early Modern Irish form inghean Aodha, which is appropriate for use with the given name Caitilín, in order to meet the submitter's request for authenticity and to register this name. [Caitilín inghean Aodha, 08/2003 LoAR, A-Calontir]
François la Flamme 2003.07 [Household name MacLeod Keep] [...] Additionally, in the submitted household name MacLeod Keep, Keep is solely English and MacLeod is Scots. While Scots is a language closely related to English, they are not actually the same language. Therefore, the submitted MacLeod Keep violates RfS III.1.a, which requires linguistic consistency within a name phrase.

Changing the household designator from Keep to Clan (i.e. Clan MacLeod) would resolve the linguistic consistency issue, but does not resolve the presumption issue with Clan MacLeod. The submitter may clear this conflict by adding an element that explicitly indicates that this household name is not the real-world Clan MacLeod. For example, Clan MacLeod of [a Scottish placename] would be registerable so long as the placename specified was not associated with the mundane Clan MacLeod. [Simon MacLeod, 07/2003 LoAR, R-Meridies]

François la Flamme 2003.07 The byname D'Navarre is not correctly constructed. The article de only elides (contracts to d') before words that begin with vowels. While there are a few examples of this practice in Spanish in period, the normal practice is for de to remain unchanged in locative bynames. Additionally, Navarre is an English form of this placename. The Spanish form of this placename may be seen in the locative byname de Navarra which is listed in Juliana de Luna's article "Spanish Names from the Late 15th Century" (http://www.s-gabriel.org/names/juliana/isabella/locative.html). [Acacia D'Navarre, 07/2003 LoAR, R-Lochac]
François la Flamme 2003.07 Listed on the LoI as Angus O'Coildáin, this name was submitted as Angus O'Coileáin. We have corrected the typographical error in the byname. The byname O'Coileáin uses the Anglicized Irish O' in this Gaelic byname and so violates RfS III.1.a, which requires linguistic consistency in a name phrase. We have changed this byname to a fully Gaelic form in order to register this name. A fully Gaelic forms of this name would be Aonghus Ó Coileáin. As the submitter did not request authenticity, we have only made the changes necessary in order to register this name. [Angus Ó Coileáin, 07/2003 LoAR, A-Atlantia]
François la Flamme 2003.07 Prague is the English name for this city. The German form is Prag (per Brechenmacher, p. 197 s.n. Prager). Therefore, the submitted byname von Prague combines German and English in a single name phrase and so violates RfS III.1.a, which requires linguistic consistency within a name phrase. The completely German form of this byname would be von Prag. The completely English form of this byname would be of Prague. Bahlow (p. 421 s.n. Prager) also dates Karel der Prager to 1272 and Herman Prager to 1362, showing forms of Prager 'person from Prague' in and near the submitter's desired time period. [Amalie von Prag, 07/2003 LoAR, A-Lochac]
François la Flamme 2003.07 Submitted as Bjorn Krom von Hakenberg, Hakenberg was documented as a Danish rendering of a German placename found in Knudsen, Kirstensen, and Hornby, Danmarks Gamle Personnavne (column 400, s.n. Hakenberg), which dates Hans Haghenberch to 1429, Bernd Hakenbergh to 1464, Bernd Hakenbergs to 1468 (the source notes the byname is in genitive case in this example), Bernt Hackenberg to 1470, and Bernd Hakenberg to 1481. This submission noted von as an attempt at a Danish word for 'of/from' and requested help in correcting this element. The particle von is German while Hakenberg is documented as Danish. As a result, the byname von Hakenberg violates RfS III.1.a, which requires linguistic consistency in a name phrase, and so is not registerable. As all of the Danish examples of bynames referring to Hakenberg do not use a particle, we have registered this byname without a particle in order to follow the standard Danish usage for this name. [Bjorn Krom Hakenberg, 07/2003 LoAR, A-Atenveldt]
François la Flamme 2003.07 The byname of 'Akka violates RfS III.1.a, which requires linguistic consistency in a name phrase. The byname of 'Akka combines the English of with the Arabic 'Akka in a case where the common English form of this placename, Acre, is different from the form of this placename in the original language. RfS III.1.a says in part:

In the case of place names and other name elements frequently used in English in their original form, an English article or preposition may be used. For example, of Aachen might be used instead of the purely German von Aachen.

Recent precedent discusses this issue:

Some placenames do not appear in English in their original form. For example, the German city of Köln appears in English as Cologne. Therefore, bynames referring to this location would be von Köln or of Cologne. The byname of Köln mixes English and German and so is not registerable because Köln is not the form that this placename takes in English. [Nathaniel Constantine von Laubach, 12/2002, A-Atenveldt]

In the case of this submission, 'Akka is an Arabic form of this placename. In English, it is rendered Acre. This name would be registerable as Katherine of Acre. As the submitter allows no changes, we were unable to make this change in order to register this name. [Katherine of 'Akka, 07/2003 LoAR, R-Atenveldt]

François la Flamme 2003.06 The submitted byname nic an Ghabhann combines nic, which is a Scots (a language closely related to English) rendering of the Gaelic inghean mhic, with an Ghabhann, which is Gaelic. This combination of Scots and Gaelic in a single name phrase violates RfS III.1.a, which requires linguistic consistency in a single name phrase. Forms of this byname appropriate for Early Modern Gaelic (c. 1200 to c. 1700) are inghean mhic an Ghabhann and inghean mhic an Ghobhann. [Broinninn nic an Ghabhann, 06/2003 LoAR, R-Caid]
François la Flamme 2003.06 Listed on the LoI as Gwineth Llyn  Lloyd, this name was submitted as Gwineth Llyn Brith. The LoI noted that the constructed placename was intended to mean 'Gray Pond'. Kingdom found that brith more usually means 'speckled', rather than 'gray', and so forwarded the name using llwyd 'gray' which appears more frequently in placenames.

Unfortunately, the hypothecized Llyn Lloyd combines Welsh and English in a single name phrase (in this case, the placename Llyn Lloyd) and, so, violates RfS III.1.a. Metron Ariston explains:

The locative is analogous to the actual Llyndu, but needs a bit of grammatical work since Lloyd is an anglicized form. The actual Welsh word for grey is in fact Llwyd, as noted in the documentation on the letter of Intent. And, following usual place name formation, the two elements would coalesce into something like Llynllwyd.

We have changed the locative byname to use the form of this placename suggested by Metron Ariston in order to place the entire byname in a single language and to make its construction follow period examples. [Gwineth Llynllwyd, 06/2003 LoAR, A-Ealdormere]

François la Flamme 2003.03 As submitted, this name combined the Old English Eald- 'old' with Nortwalde 'north forest', which is a form dated to the Domesday Book. The forms of placenames found in the Domesday Book have to be interpreted with care, as this document shows the transition from Old English to Middle English. As it turns out, the Old English Eald- had shifted to the Middle English (Anglo-Norman) form Alde- by the time of the Domesday Book. Therefore, the submitted Ealdnortwalde combined the Old English Eald- with the Middle English Nortwalde in a single word and so violated RfS III.1.a, which requires linguistic consistency in a name phrase. [Ealdnor�wuda, Canton of, 03/2003, A-Middle]
François la Flamme 2003.02 The byname ingen Mathghamhain combined the Middle Irish (c. 900 to c. 1200) ingen with the Early Modern Irish (c. 1200 to c. 1700) Mathghamhain, and so violated RfS III.1.a, which requires linguistic consistency in a name phrase. Additionally, Mathghamhain is a nominative form, not a genitive form as required by Gaelic grammar in a byname. The fully Middle Irish form of this name is Medb ingen Mathgamna. The fully Early Modern Irish form of this name is Meadhbh inghean Mhathghamhna. As the Early Modern Irish form is the closer of these to the originally submitted form of this name, we have changed this name to that form in order to register this name. [Meadbh inghean Mhathghamhna, 02/2003 LoAR, A-Caid]
François la Flamme 2003.02 [Order name Ordre du Meritum Martialis] This name is being returned for violation of RfS III.1.a, which requires linguistic consistency in a name phrase. In this case Ordre du is French and Meritum Martialis is Latin. As the submitters allow no changes, we were unable to change this name to a registerable form.

This name was intended to mean 'Order of Martial Merit'. Metron Ariston provided information regarding correctly constructed Latin and French forms of this order name:

Note that meritum does NOT come from the French merite, as stated on the Letter of Intent. The French form is derived from the well-documented classical Latin word meritum. An all-Latin form would be Ordo Meriti Martialis though Ordre Meriti Martialis would probably also work. An appropriate all-French form would be Ordre du M�rite Martial.

[Havre de Glace, Barony of, 02/2003 LoAR, R-East]
François la Flamme 2003.01 Submitted as Ùna inghen ui Griffin, the submitter requested authenticity for Irish and allowed any changes. Her forms indicated that the meaning 'Una, daughter of Clan Griffin' was most important to her. The submitted byname inghen ui Griffin combined the Gaelic inghen ui with the English or Anglicized Irish Griffin, and so violated RfS III.1.a, which requires linguistic consistency within a name phrase. Additionally, Gaelic names are registerable if accents are used or omitted consistently. We have changed this to the fully Early Modern Gaelic (c. 1200 to c. 1700) form Ùna inghean uí Ghríobhtha in order to meet the submitter's request for authenticity and to register this name. [Ùna inghean uí Ghríobhtha, 01/2003 LoAR, A-Calontir]
François la Flamme 2003.01 Listed on the LoI as Máirgrég ingen Dubhghaill, this name was submitted as Máirgreg ingen Dubgall and changed at Kingdom to add the second accent to the given name to match documented forms and to correct the grammar in the byname. However, the modified form of the byname is in violation of RfS III.1.a, which requires linguistic consistency in a name phrase, because it combines ingen, which is a Middle Irish Gaelic (c. 900 to c. 1200) form, with Dubhghaill, which is an Early Modern Irish Gaelic (c. 1200 to c. 1700) form. A fully Middle Irish form of this byname is ingen Dubgaill, which is only one character different from the originally submitted form. We have changed the byname to this form in order to register this name. A fully Early Modern Irish form of this name would be Máirghréad inghean Dubhghaill. [Máirgrég ingen Dubgaill, 01/2003 LoAR, A-Caid]
François la Flamme 2003.01 As submitted, the byname ben mhic Fhearghuis 'wife of [a man whose byname is] mac Fearghuis' combined the Middle Gaelic (c. 900 to c. 1200) ben with the Early Modern Gaelic (c. 1200 to c. 1700) mhic Fhearghuis and, so, violated RfS III.1.a which requires linguistic consistency in a name phrase. We have changed the byname to the completely Early Modern Gaelic form bean mhic Fhearghuis in order to meet the submitter's request for authenticity and to register this name. [Afraig bean mhic Fhearghuis, 01/2003 LoAR, A-East]
François la Flamme 2003.01 Submitted as Brighid Mhor inghean uí Fhlaithbertaig, the submitter requested authenticity for 10th C Ireland and allowed any changes. As submitted, this name mixes Middle Irish (c. 900 to c. 1200) and Early Modern Irish (c. 1200 to c. 1700). In particular, the byname inghean uí Fhlaithbertaig combines the Early Modern Irish inghean uí with the Middle Irish Fhlaithbertaig, and so violates RfS III.1.a, which requires linguistic consistency in a name phrase. The fully Middle Irish form of this name would be Brigit Mór ingen huí Fhlaithbertaig. We have changed the name to this form in order to meet the submitter's request for authenticity. [Brigit Mór ingen huí Fhlaithbertaig, 01/2003 LoAR, A-Caid]
François la Flamme 2003.01 Submitted as Leofwine av Sumersaeton, the submitter requested authenticity for 1056 Anglo-Saxon England and allowed minor changes. As submitted, this byname combines the modern Swedish av with the Old English Sumersaeton and so violates RfS III.1.a, which requires linguistic consistency in a name element. We have changed the particle from the Swedish av to the Old English of to resolve this problem.

Old English grammar requires that, in personal names having the form [given name] of [placename], the placename be in the dative case. The documented Sumersæton (found in Ekwall, p. 430 s.n. Somerset) is a nominative form. The dative form of this placename is Sumersætum. We have made this correction in order to register this name and to meet the submitter's request for authenticity. [Leofwine of Sumersætum, 01/2003 LoAR, A-Ansteorra]

François la Flamme 2003.01 Submitted as Michael de Safita, Safita is the name of a castle and a nearby town in Syria. No evidence was found that Safita is in a language that uses de. RfS III.1.a requires that a name phrase use a single language. Lacking evidence that de Safita is in a single language, we have changed the byname to of Safita. RfS III.1.a also states that "[i]n the case of place names and other name elements frequently used in English in their original form, an English article or preposition may be used. For example, of Aachen might be used instead of the purely German von Aachen." As Safita appears in English in this form, of Safita is registerable under this allowance in RfS III.1.a. We have, therefore, changed the byname to of Safita in order to register the name. [Michael of Safita, 01/2003 LoAR, A-Calontir]
François la Flamme 2003.01 Submitted as Thorgrim van de K�benhavn, the submitter requested authenticity for Danish and allowed any changes. The submitted byname van de K�benhavn combines van de, which appears in both Dutch and Low German, with K�benhavn, which is modern Danish. Because of this mix, this byname violates RfS III.1.a, which requires linguistic consistency in a name phrase. Metron Ariston provided information about period Danish forms of this name:

K�benhavn is the official modern Danish name for the city according to the official list of Danish place names published by the University of Copenhagen (K�benhavns Universitet) at levende.kms.dk/su/h-l.pdf. However, histories of the city at www.aok.dk/E/G/CPHDK/0000/03/86/ and www.danbbs.dk/~erikoest/cph_info.htm#CopenhagenCityHistory indicate the city was originally known in the medieval period as either simply Havn or later in medieval Danish as K�bmannehavn (Merchant's Harbor). The current name is an obvious derivation of the latter form.

From this information, af Havn and af K�bmannehavn are period Danish forms of this byname. As the latter is closer to the submitted form, we have changed the byname to this form in order to register this name and to meet the submitter's request for authenticity. [Thorgrim af K�bmannehavn, 01/2003 LoAR, A-Outlands]

François la Flamme 2003.01 [Name change from Thorvaldr Gángl�re Vakkerfjell] There are multiple problems with the byname í Vakkerfjelli.

Vakkerfjell, the basis for the byname í Vakkerfjelli, was documented only as the name of a shire in the West Kingdom (registered May 1983). There are some limitations upon registerability of SCA branch names in a personal name:

[O]nly the actual registered form of an SCA branch name is automatically registerable as part of a personal name. [...] Given the lack of documentation standards in earlier years - particularly for SCA branch names - there is no reason to assume that a registered branch name is documentable even in the language it is registered in. [Roberto Raimondo de la Montana de Trueno, LoAR June 1998, R-Atenveldt]

The submitted byname í Vakkerfjelli does not use the actual registered spelling of this SCA branch name. Rather it uses a gramatically inflected form of the placename. Therefore, the allowance for automatic registerability of an SCA branch name in a personal name does not come into play. Instead, the byname í Vakkerfjelli is subject to the same requirements of any constructed byname.

In this case, the file for Vakkerfjell shows it to have been submitted as meaning 'Beautiful Mountain' in Norwegian, using only a modern dictionary for documentation. Therefore, this is an example of the situation described in the above precedent - that, from the documentation in the file, we cannot assume that Vakkerfjell is a properly constructed period Norwegian placename.

The submitted byname í Vakkerfjelli was documented as an Old Norse construction. Therefore, the byname í Vakkerfjelli violates RfS III.1.a, which requires linguistic consistency in a name phrase, because it attempts to form an Old Norse locative byname from a hypothetical Norwegian placename. [Thórvaldr í Vakkerfjelli Thórólfsson, 01/2003 LoAR, R-Outlands]

François la Flamme 2003.01 Submitted as Seán Ó Súilleabháin Beer, Ó Súilleabháin Beer is a single compound clan name that denotes a particular branch of the O'Sullivan family. The submitted form combines the Gaelic Ó Súilleabháin with the Anglicized Irish Beer, and so violates RfS III.1.a which requires linguistic consistency in a name phrase. We have changed this byname to the fully Gaelic form Ó Súilleabháin Beirre, found in entry M1580.19 of the "Annals of the Four Masters", vol. 5, (http://www.ucc.ie/celt/online/G100005E/), in order to register this name and to meet the submitter's request that the byname be translated entirely into Gaelic. [Seán Ó Súilleabháin Beirre, 01/2003 LoAR, A-East]
François la Flamme 2002.12 Submitted as Senán O'Faolan, the submitter requested authenticity for Irish and allowed minor changes. The form O'Faolan combines the Anglicized Irish O' with the Gaelic given name Faolan. This combination is not registerable because it violates RfS III.1.a, which requires linguistic consistency in a name phrase. The closest fully Irish Gaelic form of this byname to the submitted form is the Early Modern Gaelic (c. 1200 to c. 1700) form Ó Faoláin. [Senán Ó Fáeláin, 12/2002, A-Atenveldt]
François la Flamme 2002.12 Submitted as Jean d'Esledes, the LoI stated that the submitter requested "an authentic French/Burgundian name meaning 'John of Leeds' accurate for the Hundred Year War time period". The time period of the Hundred Years War begins in the early/mid 14th C and ends in the early 15th C. Esledes was documented as dating to the Domesday Book (which means either 1066 or 1086) in Ekwall (p. 293 s.n. Leeds). Presumably, the form Esledes is, therefore, Old English or Latin. Regardless, combining it with the French d' violates RfS III.1.a, which requires linguistic consistency in a name phrase. This form is also around 250-350 years too early for the submitter's requested time period. Reaney & Wilson (p. 275 s.n. Leeds) dates Hugh de Leedes to 1285. We have changed the byname to this form to partially meet the submitter's request for authenticity. As we were unable to find a French form of the byname, we were unable to make this name completely authentic for the submitter's requested culture. [Jean de Leedes, 12/2002, A-West]
François la Flamme 2002.12 Submitted as Nathaniel Constantine of Laibach, [...]

None of these sources are included in "Books That Do Not Require Photocopies to Laurel", Appendix H of the CoA Administrative Handbook. Lacking these photocopies, we did not have an opportunity to evaluate these sources and so these references may not be considered for documentation.

Additionally, the article cited from the newadvent.org website only documents that the diocese specified was founded in the 15th C. There is no indication that Laibach was the name of that diocese at that time. Lacking evidence that Laibach is a plausible period placename in German, it is not registerable. Nebuly provided additional information regarding the byname of Laibach:

[...] of is an English preposition; and Laibach is the modern German name for the Slovenian capital. [...] [T]he submitted form of Laibach mixes two languages in the same phrase (RfS III.1.a). However, I cannot find evidence that Laibach is a period spelling for the city of Ljubljana. Blaznik (who has published a big book of pre-1500 Slovene toponyms) does not cover this part of Slovenia. Simon de Kéza recorded the town's name in Latin as Leopah when he wrote the Gesta Hungarorum circa 1285. Blaeu (p. 111) records the name as Laubach or Lubiana in his Grand Atlas. Bynames from Bahlow and Brechenmacher agree with the spelling Laubach, and we might want to change the submission to that spelling, since there does not seem to be evidence for the submitted Laibach before modern times.

RfS III.1.a says in part:

In the case of place names and other name elements frequently used in English in their original form, an English article or preposition may be used. For example, of Aachen might be used instead of the purely German von Aachen.

Laibach does not meet this requirement. Some placenames do not appear in English in their original form. For example, the German city of Köln appears in English as Cologne. Therefore, bynames referring to this location would be von Köln or of Cologne. The byname of Köln mixes English and German and so is not registerable because Köln is not the form that this placename takes in English. In the case of this submission, Laibach is a modern German name for Ljubljana (Webster's Geographical Dictionary, s.n. Ljubljana). In English, this location is known as Ljubljana, not Laibach. So, of Laibach is not registerable.

We have changed this byname to von Laubach in order to register this name. [Nathaniel Constantine von Laubach, 12/2002, A-Atenveldt]

François la Flamme 2002.11 The submitted byname O'Morda is a combination of the Anglicized Irish O' and the Gaelic Morda and so violates RfS III.1.a, which requires linguistic consistency within a name phrase. As the submitter requested authenticity, we have changed this byname to the fully Gaelic form hua Mordha based on "The Annals of Ulster", entry U1026.6, which lists Aimhirgin H. Mordha, ri Loigsi (H. is a scribal abbreviation for hua, which later became Ua and finally Ó). [Conallán hua Mordha, 11/2002, A-Atenveldt]
François la Flamme 2002.11 Submitted as Seamus O'Dubhda, O'Dubhda mixes the Anglicized Irish O' with the Gaelic Dubhda and so violates RfS III.1.a, which requires linguistic consistency within a name element. We have changed this element to the fully Gaelic form Ó Dubhda in order to register this name. Since accents must be used or omitted consistently within a Gaelic name, and no accent was included on the submitted form of the given name, we have left the accents out of this name. A fully Gaelic form that includes accents would be Séamus Ó Dubhda. [Seamus O Dubhda, 11/2002, A-Ansteorra]
François la Flamme 2002.11 The phrase ingen Fhaolain violates RfS III.1.a (which requires linguistic consistency in a name phrase) because it combines the particle ingen, which is an Old Irish Gaelic (c. 700 to c. 900) and Middle Irish Gaelic (c. 900 to c. 1200) form, with Fhaolain, which is an Early Modern Irish Gaelic (c. 1200 to c. 1700) form. We have changed the particle ingen to the Early Modern Irish Gaelic form inghean to resolve this issue. [Máirghréad inghean Fhaoláin, 11/2002, A-An Tir]
François la Flamme 2002.10 The byname von Aschehyrst violates RfS III.1.a, which requires linguistic consistency in a name element. Aschehyrst, the name of the submitter's group, is English, while the particle von is German. A similar case is shown in the precedent:

Submitted as Ulrich von Rudivale, we have changed the [von] to of since the rules require that prepositions must agree in language with the following noun, and Rudivale, which is the client's home group, is English. (Jaelle of Armida, LoAR July 1996, p. 13)

As the submitter allows no changes, we cannot change von to of and register his name. However, as the submitter allows a holding name, we have formed his holding name, Karl of Aschehyrst, according to the standard format of using the name of his branch, in order to permit registration of his armory. By having Karl of Aschehyrst as a holding name, rather than an (undesired) name change, we can register the device, which would otherwise have to be returned. [Karl von Aschehyrst, 10/2002, R-East]

François la Flamme 2002.10 Submitted as Stowe on the Wald, Canton of, this name combined the Middle English Stowe on the with the Old English Wald. As a placename is a single name phrase, the submitted form was in violation of RfS III.1.a, which requires linguistic consistency in a name element. Mills (s.n. Stow, Stowe) dates Stowe on the Olde to 1574. Speed's The Counties of Britain (p. 83, map of Gloucestershire, map dated to 1610) lists Stowe on y(e) wowld ("(e)" represents a superscript 'e'). We have changed Wald to Wowld to make the entire name Middle English in order to register the name. [Stowe on the Wowld, Canton of, 10/2002, A-Lochac]
François la Flamme 2002.10 O'Céileachair combines the Anglicized Irish O' with the Irish Gaelic Céileachair. (The forms definitely show an apostrophe rather than an accent on the O.) RfS III.1.a requires linguistic consistency within a name element. As the submitter allows no changes, we were unable to change this to the fully Gaelic Ó Céileachair in order to register this name. [Daniel O'Céileachair, 10/2002, R-Ansteorra]
François la Flamme 2002.10 [...] by combining the Romanian Stefán with the Hungarian -ne, the element Stefánne violates RfS III.1.a, which requires linguistic consistency within a name phrase. [Fehér Stefánne de la Afumati, 10/2002, R-Middle]
François la Flamme 2002.09 Submitted as Sadb inghean Constance, the submitter requested authenticity for Irish. The byname inghean Constance combined the Gaelic particle inghean with the English feminine given name Constance. Since RfS III.1.a requires linguistic consistency within a name phrase, such as inghean Constance, this byname is not registerable. We have dropped the particle inghean in order to register this name as an Irish feminine given name and an English matronymic byname. Lacking evidence that the name Constance was used in Ireland, we were unable to make this name authentic for the submitter's desired culture. [Sadb Constance, 09/2002 LoAR, A-Calontir]
François la Flamme 2002.09 Submitted as Iain mac Caradoc, the submitter requested authenticity for 15th C Scots and allowed any changes. Iain is a Gaelic masculine given name, ruled SCA compatible in April 1997. However, no evidence has yet been found that it was used in period. The submitted byname mac Caradoc combined the Scots or Anglicized Irish particle mac with the Welsh name Caradoc. RfS III.1.a requires linguistic consistency in a single name phrase. Therefore, the phrase mac Caradoc is in violation of this rule and is not registerable. No examples were found of any form of Caradoc in either Gaelic or Scots (a language closely related to English). Therefore, we have changed the byname to the form Cradoc, which is a plausible form based on the examples of Philip Craddoc dated to 1205 and Robert Cradock dated to 1301, both in England, in Reaney & Wilson (p. 114 s.n. Craddock). Morgan & Morgan (p. 67 s.n. Caradog) explain that the change in this name from Caradoc to Cradoc forms is due to an accent shift in early Welsh. Use of an element that is only SCA compatible (Iain in this case) counts as a weirdness. Combining English and Gaelic in a single name is also a weirdness. To avoid having two weirdnesses in this name, which would cause the return of this name, we have changed the given name to the form Ian, which is also SCA compatible. Since Ian is Scots, and mixing Scots and English in a single name carries no weirdness for the lingual mix, Ian Cradoc is a registerable form of the submitted name. [Ian Cradoc, 09/2002 LoAR, A-Atenveldt]
François la Flamme 2002.08 As submitted, the byname Haroldsson used the English name Harold in an Old Norse patronymic form. As such, it violated RfS III.1.a, which requires linguistic consistency in a single name element. Heralds attending the decision meeting at Pennsic found the byname Harolds�n dated to 1424 in Sveriges Medeltida Personnamn (vol. 11, column 118, s.n. Harald). This is the closest form found to the submitted byname. We have changed the byname to this form in order to register this name. Argent Snail noted that "Lind dates Axel in this spelling to 1366, while Sveriges Medeltida Personnamn dates this spelling of Axel to 1397 and 1398." So, Axel Harolds�n is a fine name for late 14th C or early 15th C Swedish. [Axel Harolds�n, 08/2002, A-Calontir]
François la Flamme 2002.08 Submitted as Morgan MacOwain of Staghold, MacOwain combined the Scots (a language closely related to English) or Gaelic Mac with Welsh Owain. This is in violation of RfS III.1.a, which requires linguistic consistency in a name phrase. As the submitter allows minor changes, we have dropped Mac in order to register this name. [Morgan Owain of Staghold, 08/2002, A-Atenveldt]
François la Flamme 2002.07 Submitted as Desiree of Colecestra, the submitter requested authenticity for 12th C England in the region of Essex. As the form Colecestra is a Latin form, we have changed the byname to the completely Latin form de Colecestra to meet the submitter's request for authenticity and to comply with RfS III.1.a, which requires linguistic consistency in a single name phrase. [Desiree de Colecestra, 07/2002, A-An Tir]
François la Flamme 2002.07 The submitted name mixes Arabic and Indian languages within name phrases, which is prohibited under RfS III.1.a, which requires linguistic consistency within a name element. Humayun was documented as the "name of a Mughal ruler of northern India, 1515-1556". al-Jamal notes that "technically the name is not truly 'Arabic', in that Humayun may be Mughal, a form of Mongol, rather than Arabic." The byname bint Humayun therefore combines the Arabic bint, meaning 'daughter', with the non-Arabic name Humayun. There is also some question whether the name Humayun was in common use. If it is unique to this ruler, then use of this name in a byname is presumptuous and is cause for return. In order to be registerable, this phrase needs to rendered in a single language and Humayun needs to be shown to be a name that is not unique to this ruler.

The byname al Delhi combines the Arabic element al with the Indian placename Delhi. In order to be registerable, this phrase needs to be rendered in a single language and put in a proper locative byname form. al-Jamal explains:

Al Delhi is neither proper grammar nor the correct gender. As it stands, her father is claiming to be Delhi. If locatives are formed in Mughal India according to Arabic rules of grammar, something I cannot confirm, I would expect the masculine form from someone from Delhi to be al-Delhiwayyi, and the feminine form to be al-Delhiwayyia.

The form that locative bynames take in Mughal would need to be documented as matching those in Arabic, or Delhi would need to be documented as an Arabic form of this placename, for the forms mentioned by al-Jamal to be registerable. [Masala bint Humayun al Delhi, 07/2002, R-Atenveldt]

François la Flamme 2002.07 The element Kathoum, used in the byname ibn Kathoum, was submitted as the father's legal given name. The Legal Name Allowance only applies to elements of the submitter's own name. At the same time as this submission, the submitter's father submitted an Arabic name using Kathoum as his given name via the Legal Name Allowance. (That submission is returned this month for other issues.) The Grandfather Clause allows elements of immediate family members to be used in the same manner and exactly the same spelling as in the registered name regardless of the current registerability of that element, so long as no new violations of the Rules for Submissions exist in the new name that did not exist in the registered name. In Arabic, given names used in a patronymic byname have the same case as given names used in given name positions, so the spelling of Kathoum used in a patronymic byname would not change from the spelling Kathoum used as a given name. Therefore, if the submitter's father registers Kathoum as the given name in his SCA name, the submitter may register ibn Kathoum as an Arabic byname in his SCA name. Since Kathoum is a modern Arabic masculine given name, the byname ibn Kathoum complies with RfS III.1.a, which requires linguistic consistency in a byname. [Rami Hussein ibn Kathoum, 07/2002, R-Atenveldt]
François la Flamme 2002.06 The byname macSeyfang is in violation of RfS III.1.a, which requires linguistic consistency in a single name phrase. It combines mac, which can be viewed as Gaelic, Anglicized Irish, or Scots, with Seyfang, which is a German byname. Removing mac from the byname would not make this name registerable since the earliest date provided for Seyfang was 1864. Lacking evidence that Seyfang is a period name, it is not registerable. [Brian macSeyfang, 06/2002, R-Atenveldt]
François la Flamme 2002.05 [Caisín ingen Annaidh] The submitted byname ingen Annaidh combines ingen, which is an Old Irish Gaelic (c. 700 to c. 900) and Middle Irish Gaelic (c. 900 to c. 1200) form, with Annaidh, which is an Early Modern Irish Gaelic (c. 1200 to c. 1700) form. This combination violates RfS III.1.a, which requires linguistic consistency within a single name phrase. A fully Old Irish/Middle Irish form would be ingen Annaid. A fully Early Modern Irish form would be inghean Annaidh. The LoI noted that the byname was originally submitted as Mac Annaidh and the only change allowed by the submitter was changing Mac to ingen. As the submitter allows no other changes, we were unable to modify the byname in order to register this name. [Fujiwara no Aoi, 05/2002, R-East]
François la Flamme 2002.05 The byname verch Bertram does not violate RfS III.1.a, which requires lingual consistency. Though verch was documented as Welsh and Bertram was documented as English, evidence has been found of late period Welsh using English names in bynames that include ap or ferch. This issue has previously been addressed by the precedent:

Found on the LoI as Myfanwy ferch Gerallt, it was originally submitted as Myfanwy ap Gerald, and changed in kingdom because it was felt that the use of ap or ferch needed a Welsh name. However, late period Welsh used ap and ferch with English names, so we have restored the patronymic to the originally submitted form. (LoAR November 1998, p. 4).

Since verch is a 16th C form of ferch, the byname verch Bertram is registerable as a Welsh byname that incorporates an English name, which follows documented period practice. [Gwladyse verch Bertram, 05/2002, A-Outlands]

François la Flamme 2002.04 Submitted as Colleen inghean Phátraic, the submitter requested authenticity for "Celtic Irish/Scottish" and allowed minor changes. As the submitted byname inghean Phátraic combines the Early Modern Irish (c. 1200 to c. 1700) inghean with the Middle Irish (c. 900 to c. 1200) Phátraic, it violates RfS III.1.a, which requires linguistic consistency within a name phase. A standard Middle Irish form of this byname would be ingen Phátraic. A standard Early Modern Irish form would be inghean Phádraig. Another option for an Early Modern Irish form is found in the Annals of the Four Masters, vol. 5 (http://www.ucc.ie/celt/online/G100005E/), which lists Tomas, mac Pattraicc, mic Oiliuéir Ploingcéd tighearna Luchcmaigh in entry M1578.15. This entry shows Pattraicc used as a given name in a family of Anglo-Norman descent. In a feminine byname, this form of Pattraicc would be lenited to become Phattraicc. [...] [Colleen inghean Phattraicc, 04/2002, A-Artemisia]
François la Flamme 2002.04 Submitted as Helga Idadóttir, the byname combined the German Ida with the Old Norse -dóttir. This violates RfS III.1.a, which requires linguistic consistency within a name phrase. Lacking evidence that the name Ida was used in Old Norse, the constructed Idadóttir is not registerable.

The LoI stated "the submitter will accept a German form similar to Helga Idas dohtir if she must." Bahlow (p. 272 s.n. It(t)ensohn) gives this as a matronymic meaning 'son of Frau Itta (Ida)' and dates Arnold Ittensun to 1300 and Hertel Idenson to 1375. The parallel 'daughter' forms would be Ittendohtir and Idendohtir. Given the example of Henneke Katerinen son dated to 1336 in Bahlow (p. 288 s.n. Katharina), Itten dohtir and Iden dohtir are reasonable forms as well. As Iden dohtir is the closest of these forms to the alternate form Idas dohtir listed on the LoI, we have changed the byname to this form in order to register her name. [Helga Iden dohtir, 04/2002, A-Caid]

François la Flamme 2002.04 The byname Ingridsdottir combines Ingrid (documented as Norwegian from E. H. Lind, Norsk-Isl�ndska Dopnamn fr�n Medeltiden, col. 639 s.n. Ingiri�r, which dates Ingridh to 1430 and Ingerid to 1461), and -dottir (documented as Swedish in Sveriges Medeltida Personamen (vol. IV, column 543), which lists Cecelia Ingadottir). By the 15th century, Norweigian and Swedish had diverged and were different, though related, languages. Therefore, the constructed Ingridsdottir violates RfS III.1.a by combining Norwegian and Swedish in a single name phrase. Lindorm Eriksson's article "Swedish Feminine Names from ca. 1300" (http://www.s-gabriel.org/names/lindorm/swedish1300female.html) lists the form Ingrid and includes the names Helena Ormsdotyr uxor Johannis Ingason and Ingeborg filia Tunædotir domina. Sveriges Medeltida Personamen (vol. III, column 636, s.n. Elena) dates Elena Anundadottir to 1312. From these examples, Ingridsdotir and Ingridadotir are plausible Swedish forms of this byname close to the originally submitted Ingriddotir. We have changed the byname to the first of these in order to register the name. [Karen Ingridsdotir, 04/2002, A-Middle]
François la Flamme 2002.04 Listed on the LoI as Cera ingen Taidhg, this name was submitted as Cera ingen Tadc and changed at kingdom to put Tadc into a documented genitive form. Tadc is an Old Irish Gaelic (c. 700 to c. 900) and Middle Irish Gaelic (c. 900 to c. 1200) form of the name that became Tadhg in Early Modern Irish Gaelic (c. 1200 to c. 1700). Taidhg is the genitive form of Tadhg. The genitive form of Tadc is Taidc. As ingen, meaning 'daughter', is an Old Irish or Middle Irish form, the accompanying patronym must be an Old Irish or Middle Irish form in order to comply with RfS III.1.a, which requires lingual consistency in a name phrase. Therefore, we have changed the byname to ingen Taidc. Since 'T' does not lenite if the previous word ended in 'n', the byname form Taidc is the appropriate form following ingen. [Cera ingen Taidc, 04/2002, A-Caid]
François la Flamme 2002.03 Listed on the LoI as Seóan Ó Donndubáin, this name was submitted as Seóan O'Donndun and changed at kingdom, since the byname mixed Gaelic and Anglicized Irish and RfS III.1.a requires lingual consistency in a single name phrase. Also, the byname was not in the genitive. The submitter requested authenticity for Irish language/culture and allowed any changes. Ó is an Early Modern Gaelic (c. 1200 to c. 1700) spelling. Donndubáin is a Middle Gaelic (c. 900 to c. 1200) spelling. Therefore, we have changed the byname to a consistently Early Modern Gaelic form to comply with RfS III.1.a and to meet the submitter's request for authenticity. [Seóan Ó Donndubháin, 03/2002, A-Æthelmearc]
François la Flamme 2002.03 Submitted as Cortlandt  Keep, Shire of, this mixed the Dutch Cortlandt with the English Keep in a placename. As a placename is a single name phrase, this combination is in violation of RfS III.1.a, which requires linguistic consistency within a single name phrase. The LoI noted that "If the mix is acceptable, the group would prefer the submitted spelling. Otherwise, they would prefer that the second element be changed to a Dutch term equivalent to 'keep'. No one in Æthelmearc was able to find an appropriate term." The Dutch word for a castle or keep is slot. Cortlandtslot and Slot Cortlandt are proper Dutch forms of this name. As Cortlandtslot is the closer of these two in sound and appearance to the submitted Cortlandt Keep, we have changed the name to that form. [Cortlandtslot, Shire of, 03/2002, A-Æthelmearc]
François la Flamme 2002.02 The name was registered as Caitilín Fhionn inghean Fhionn. Further examination of the documentation shows that it was correct as submitted, Caitilín Fhionn inghean Fhinn. [Caitilín Fhionn inghean Fhinn, 02/02 Errata Letter, A-Atlantia]
François la Flamme 2002.02 Additionally, if support was found for Nasrin as a place name in Persian, it would not be registerable in the form al-Nasriniyya, since it uses Arabic construction. RfS III.1.a requires linguistic consistency in a name phrase. For al-Nasriniyya to be registerable, Nasrin needs to be documented as a place name in Arabic. [Khalila al-Nasiriniyya, 02/02, R-Caid]
François la Flamme 2002.02 RfS III.1.a requires lingual consistency within a name phrase. A place name is a single name phrase. As Avallon is documented as a French placename and Keep is English, Avallon Keep violates this requirement. [Avallon Keep, Canton of¸ 02/02, R-Lochac]
François la Flamme 2002.01 Submitted as Gerhart von Cynnabar, RfS III.1.a requires lingual consistency within a name phrase. The branch name Cynnabar was documented as English when the name was registered in 1983. ...Use of von in conjunction with an SCA group name that is English has previously been ruled unregisterable:
[Ulrich of Rudivale] Submitted as Ulrich von Rudivale, we have changed the [von] to of since the rules require that prepositions must agree in language with the following noun, and Rudivale, which is the client's home group, is English. (Jaelle of Armida, LoAR July 1996, p. 13)
This submission has the same problem. Therefore, the submitted von Cynnabar is in violation of the linguistic consistency requirement in RfS III.1.a for mixing German and English in a single name phrase. As the submitter allows minor changes, we have changed the particle von to of in order to register this name.

This submission raised considerable discussion about the languages of particles that have been registered with group names in the past. Of particular note was discussion regarding the following precedent:
[Robert de Cynnabar] Cynnabar is the registered name of an SCA group. Since de was the most common medieval documentary locative preposition in both England and France, the two places where Robert is most likely to be found, we allow him to register the name of an SCA group with it. This was first done with the 11/92 registration of Robert de Cleftlands. (02/97)
It was asserted that since de has been registered in conjunction with Cynnabar at that time, von should also be registerable as well. However, in the cases of both Robert de Cynnabar and Robert de Cleftlands, the group names are English. Since there is considerable documentation for use of the particle de in documents written in English, both of the bynames de Cynnabar and de Cleftlands comply with RfS III.1.a and are in a single language, i.e., English. In the recent registration of Lucas de Caid (October 2001), Caid is an acronym and is therefore not documentable in any language. For branch names registered long ago that are not documentable to any particular language (as is the case with Caid), we will treat them as part of the Society's official language, which is English. Therefore, the byname de Caid is treated as an all-English byname and complies with RfS III.1.a. [Gerhart of Cynnabar, 01/02, A-Caid]
François la Flamme 2002.01 Eplaheimr was submitted as a constructed name for a Viking-era farm meaning 'world of apples'. RfS III.1.a requires name phrases to be constructed of a single language. Eplaheimr does not meet this requirement, since eple is stated to be Norwegian and heimr is Old Norse. Just as we would not register a place name mixing Old English and Middle English in a single name phrase, a mix of Old Norse and Norwegian is not registerable in a single name phrase. [Ságadís Duncansdaughter and Sigmundr Hákonsson, 01/02, R-Drachenwald]
François la Flamme 2001.12 Submitted as Caitilín Fhionn inghean Fhinn, the byname inghean Fhinn combined the Early Modern Gaelic (post-1200) inghean with the Middle Gaelic (pre-1200) Fhinn. This combination violates RfS III.1.a, which requires lingual consistency in a single name phrase. We have changed the byname to a completely Early Modern Gaelic form to resolve this problem. [Caitilín Fhionn inghean Fhionn, 12/01, A-Atlantia] [overturned in the 02/2002 Errata Letter]
François la Flamme 2001.12 [RfS III.1.a] Submitted as Síthmaith nic Aoidh, the byname combined the Scots particle nic with the Gaelic Aoidh. This combination violates RfS III.1.a, which requires lingual consistency within a single name phrase. The LoI noted that, "She specifically desires the very late 'nic' form to match her persona from late Elizabethan Ireland," though she did not have a request for authenticity. Unfortunately, we have no evidence that nic was used in the names of Irish women in Ireland, though there is plently of evidence for use of the particle in the Scots language in Scotland. Therefore, we have changed the byname to the all Gaelic form inghean mhic Aoidh in order to register this name. [Síthmaith inghean mhic Aoidh, 12/01, A-Atlantia]
François la Flamme 2001.12 [RfS III.1.a] Submitted as Amber Roriksdottír, Amber is grandfathered to the submitter. Roriksdottír combined the Danish Rorik with the Old Norse -dóttir (with the accent misplaced). Such a mix is a violation of RfS III.1.a which requires lingual consistency in a name prase. Therefore, the byname is registerable as the completely Danish Roriksdatter or the completely Old Norse Hr�reksdóttir. From examples of bynames listed in E. H. Lind, Norsk-isländska dopnamn ock fingerade namn från medeltiden (columns 594-595 s.n. Hrórek) the form Roreksstadir would be registerable as medieval Norse. As the submitter allowed minor changes, we have registered this name in the Danish form Roriksdatter since it is the closest form to the submitted Roriksdottír. [Amber Roriksdatter, 12/01, A-Atlantia]
François la Flamme 2001.11 [RfS III.1.a] Submitted as Úna ingen Ranald, the submitter requested authenticity for 12th to 13th C Scottish Gaelic and allowed any changes. Ranald is a Scots language form. (Scots is a language similar to English.) The corresponding name in Gaelic is Ragnall. [Úna ingen Ragnaill, 11/01, A-East]
François la Flamme 2001.11 [RfS III.1.a] Submitted as Doireann ingen Chearbhaill, the submitter requested authenticity for 12th to 14th C (no culture specified) and allowed any changes. The particle ingen is a Middle Irish (pre-1200) spelling. Chearbhaill is an Early Modern Irish (post-1200) spelling. There is enough difference between Middle Irish and Early Modern Irish that they count as different languages for our purposes. So ingen Chearbhaill violates RfS III.1.a since it combines elements from two different languages. [Doireann inghean Chearbhaill, 11/01, A-An Tir]
François la Flamme 2001.10 [RfS III.1.a] The particle was not used in Gaelic in period. The pre-1200 form is ingen uí and the post-1200 form is inghean uí. We have changed the particle to be linguistically consistent (as required by RfS III.1.a) with Líadnáin which is a pre-1200 spelling. [Ceara ingen uí Líadnáin, 10/01, A-Atlantia]
François la Flamme 2001.10 [RfS III.1.a] Submitted as Séamus O' Tadhgáin, O' is an Anglicized form while Ó is a Gaelic form. Per RfS III.1.a, mixing languages is prohibited in a single name phrase. We have therefore changed O' to the Gaelic Ó. [Séamus Ó Tadhgáin, 10/01, A-Artemisia]
François la Flamme 2001.10 [RfS III.1.a] Submitted as Diederic van Flandres, the support for van Flandres is from an Academy of Saint Gabriel letter (client #1295). Nebuly was one of the contributors to this letter and has found a mistake in how the notation in that source was originally interpreted. As such, van Flandres is a combination of two languages which violates RfS III.1.a, and so is not registerable. Nebuly writes:
The byname van Flandres is problematic since van is a Dutch preposition while Flandres is a French spelling. Under RfS III.1.a. this should be returned for mixing two languages in a single phrase. The simplest way to correct this is to make the byname entirely French as de Flandres. The most likely Dutch form is Vlaminck, with no preposition (Luana de Grood, 1594).
Additionally, evidence has been found of the singular Flandre in French bynames rather than the plural Flandres. Changing van Flandres to de Flandre is a smaller change than changing van Flandres to Vlaminck. Since the submitter did not note any preferences on his forms regarding language/culture, we have made the smaller change in order to register this name. [Diederic de Flandre, 10/01, A-Æthelmearc]
François la Flamme 2001.10 [RfS III.1.a] Submitted as Derdriu de Dubhglas, the byname combined the Gaelic Dubhglas with the non-Gaelic de in a single name phrase. This violates RfS III.1.a, which requires linguistic consistency in a single name phrase. We have changed the byname to a completely Scots form to resolve this issue. [Derdriu de Duglas, 10/01, A-Trimaris]
François la Flamme 2001.10 [RfS III.1.a] [Saint Vladimir] ... the element Saint is English and the element Vladimir is Russian. RfS III.1.a requires all elements in a single name phrase to be from the same language. A placename is a single name phrase. Therefore, Saint Vladimir is in violation of this rule. An exact parallel exists with the precedent:
[Registering �vatý Sebesta, College of.] Submitted as College of Saint Sebesta, RfS III.1.a. requires that each phrase must be grammatically correct according to the usage of a single language. We have translated "saint" to the Czech form, as well as adding the correct "inverted caret" over the S in Sebesta (it is pronounced "Shebesta"). [6/94, p.9]
According to Paul Wickenden, the Russian form of Saint is Sankt. In period, a location named for Saint Vladimir in Russia would have simply have been named Vladimir. In fact, there are three locations with this name. Sankt Petrburg (Saint Petersburg) was intentionally named to follow European practices. Furthermore, it was so named in 1703, so even if it followed Russian naming practices, this example is outside our period. Given this information, we would have dropped Saint to follow documented practices in Russian, but the group allows no major changes. Major changes normally include language changes, which would prevent changing Saint to Sankt. However, the consensus at the decision meeting was that changing Saint to Sankt was more like changing the language of a particle in a personal name (which is normally viewed as a minor change) rather than changing the language of a substantial element (which is a major change). Therefore, we have changed Saint to Sankt in order to register the name. It was felt that the name construction was plausible enough to register. However, given that we have no concrete examples of this construction in Russian in period, it is a weirdness. [Sankt Vladimir, College of, 10/01, A-Atenveldt]
François la Flamme 2001.09 [RfS III.1.a] Submitted as Roise ni Ruaidhri, the particle ni is an Anglicized form of inghean uí. As RfS III.1.a requires all elements of a name phrase (the byname ni Ruaidhri in this case) to be in a single language, we have changed the particle to the Gaelic form. [Roise inghean ui Ruaidhri, 09/01, A-Calontir]
François la Flamme 2001.09 [RfS III.1.a] Submitted as Marie Suzanne von Westphalia, the byname combines a German particle with the English form of a place name (the German spelling is Westphalen). As RfS III.1.a requires all elements of a name phrase (the byname von Westphalia in this case) to be in a single language, this byname needed to be changed to either the all German form von Westphalen or the all English form of Westphalia. [Marie Suzanne of Westphalia, 09/01, A-Calontir]
François la Flamme 2001.09 [RfS III.1.a] Submitted as Áengus Ó Dubhghaill Grey Wolf, this name had several problems.

The greatest problem was regarding the construction of Ó Dubhghaill Grey Wolf. No documentation was provided that this was a reasonable construction. Ó Dubhghaill Grey Wolf may seem to be two name phrases, Ó Dubhghaill and Grey Wolf, but it is actually a compound byname. Irish Gaelic uses the structure Ó byname + another byname to refer to a particular family, usually as part of a chiefly title. For example, the names Ó Conchobhair Donn, Ó Conchobhair Ruadh, and Ó Conchobhair Sligeach are all designations for heads of branches of the O'Connors (Woulfe, p. 477 s.n. Ó Conchobhair Donn).

As a compound byname, Ó Dubhghaill Grey Wolf falls under RfS III.1.a and must consist of a single language. As submitted, this name phrase mixes Irish Gaelic and English. As we have no evidence that 'color + animal' is a reasonable byname in Irish Gaelic, we cannot translate Grey Wolf into Gaelic. The simplest fix is to put Grey Wolf before the patronymic, making it a descriptive byname referring to Áengus. [Áengus Greywolf Ó Dubhghaill, 09/01, A-Caid]
François la Flamme 2001.08 [RfS III.1.a] Submitted as Swanesdæl, this element violates RfS III.1.a since it combines the Middle English Swanes- with the Old English -dæl, combining two incompatible elements in the same placename. [Edith of Swanesdale, 08/01, A-West]
François la Flamme 2001.08 [RfS III.1.a] Submitted as Kaaren Håkonsdóttir. ... As the submitted form combined Old Norse and 15th C Swedish, it violated RfS III.1.a by mixing languages. To clear this problem, we have changed the patronymic to the 15th C Swedish form Håkonsdotter as that is closer to the submitted byname than the Old Norse form Hákonardóttir. [Kaaren Håkonsdotter, 08/01, A-West]
François la Flamme 2001.08 [RfS III.1.a] In our period, the particle nic was not used in Gaelic. The period Gaelic equivalent was inghean mhic. RfS III.1.a requires that all elements in a name phrase be in one language. We have made the change in the particle to comply with this rule. Note: As the patronym (Criomhthainn) begins with a "C" and the preceeding particle (mhic) ends with a "c", the patronym does not lenite. [Muirenn inghean mhic Criomhthainn, 08/01, A-Caid]
Elsbeth Anne Roth 2000.08 Submitted as Muirenn ingen Darragh, the byname mixed Anglicized and Gaelic spelling. As Bordure put it,

Woulfe (p. 494 s.n. Ó Dara) lists Darragh as a modern Anglicized form of the name. As such, using it with ingen violates RfS III.1.a, "Each phrase must be grammatically correct according to the usage of a single language." [Muirenn ingen Dara, 08/00, A-Atlantia]
Jaelle of Armida 1997.08 [Caíntigern of Ainsley] This combines Gaelic and English orthography in the same name. An argument was made that the lingua angelica rule should apply to topographic bynames. If "Ainsley" is a reasonable place name in English, the result is as registerable as, say "Caítigern of Dublin", would be. Unfortunately, the lingua angelica rule does not work that way. The relevant passage in the rules comes at the end of RfS III.1.a (Linguistic Consistency): `In the case of place names and other name elements frequently used in English in their original form, an English article or preposition may be used. For example, of Aachen might be used instead of the purely German von Aachen.' This submission does not meet that standard. (Jaelle of Armida, LoAR August 1997, p. 16)
Jaelle of Armida 1997.04 [returning Ziegfried Gunter von Wieselburg. Household name for Haus Godwiesel.] This is being returned for violating RfS III.1, by combining two different languages, the of Middle English god and the German Wiesel in the same word. Moreover, the existence of Middle English bynames of a particular type is no guarantee that bynames of that type existed in German as well. (Jaelle of Armida, LoAR April 1997, p. 24)
Da'ud ibn Auda (2nd tenure, 2nd year) 1994.11 RfS III.1.a. requires that "Each phrase must be grammatically correct according to the usage of a single language." Here we have a Welsh patronymic particle (merch) combined into a single phrase with an Anglicized variant of an Old Irish surname (Ó Donndugháin), which itself appears to be from a compound meaning "brown Dubhán". The combination is unlikely in the extreme, and it does not follow "the usage of a single language" as required by the RfS. (Da'ud ibn Auda, LoAR November 1994, p. 14)
Da'ud ibn Auda (2nd tenure, 2nd year) 1994.09 The name combines in a single phrase two different languages (Norse and Gaelic), and thus falls afoul of RfS III.1. Name Grammar and Syntax ("Names should generally combine elements that are all from a single linguistic culture") and III.1.a., Linguistic Consistency ("Each phrase must be grammatically correct according to the usage of a single language"). (Da'ud ibn Auda, LoAR September 1994, p. 17)
 
RfS III.2.a "Personal Names - A personal name must contain a given name and at least one byname ... "
François la Flamme 2004.02 Submitted as Bessenyei Rozsa, Rozsa was documented from Kalman's The World of Names. Kalman should be used with care since, as Nebuly explains, "he never provides dates and modernizes all spellings". Whenever possible, better documentation should be used.

Nebuly provided information regarding the elements of this name:

The element Bessenyei is documented to 1576 in Kázmér and is a locative byname meaning "from Besnye". The spelling of the given name Rozsa is demonstrably post-period, since the ZS diphthong is a post-period innovation in Hungarian.

I have not found the name Rozsa (in any spelling) used as a given name in period Hungarian, but we may be able to justify it in another spelling. Kázmér has examples of its use as a byname (s.n. Rózsa); specifically, he has Rosa dated 1573 and Rossa dated 1592. He identifies the byname as a metronym, and although there may be another interpretation, the use of Rosa and Rossa as a given name in neighboring Italy (Arval) support Kázmér's interpretation. The name should be changed to Bessenyei Rosa or Bessenyei Rossa for registration.

As Rossa is the closer of the two forms found by Nebuly to the submitted Rosza, we have changed the name to use this form in order to register this name. [Bessenyei Rossa, 02/2004, A-Atlantia]

François la Flamme 2004.02 This name is being returned for lack of a given name as required by RfS III.2.a, "Personal Names", which states in part that "A personal name must contain a given name and at least one byname".

Teofilia was submitted as a given name as stated in the LoI:

Teofilia is dated to before 1607 by Zofia Teofilia Danilowicz, mother of Jan Sobieski III, b 1607 (<http://www.geocities.com/a_gulinski/poczela.htm>)

This website is a genealogy website. Genealogy sources often standardize and/or modernize names. While this practice aids in presentation of a genealogist's research, it is not useful for our purposes. Nebuly provided significant commentary regarding the person mentioned in this webside, and regarding the name Teofilia in general:

Although it may be true that Zofia Teofilia Danilowicz appears as the mother of Jan III Sobieski on the cited web page, I doubt that this is a period form for her name, especially since it is grammatically incorrect for Polish. I have examined the web site and find that it is a purported genealogy of the Guli{n'}ski family, with information indiscriminately pulled from a wide array of sources. Spellings of names on the site are heavily modernized, and information is often unreliable. For example, Jan III Sobieksi's father, Jakub Sobieski, had four sons (Stone, p136), but the Guli{n'}ski site lists only three sons. We do not generally regard genealogical sources as sufficient for documentation, and given the mistakes and modernization of names, the site should be regarded with extreme suspicion.

It was unclear to me whether the cited individual had two given names and a patronym, or a single given name and compound patronym. That is, the name might mean "Zofia, daughter of Teofil Danilowicz." The element Teofilia would thus be the masculine given name Teofil in its genitive form. Some digging into the genealogy of Jan III revealed that his maternal grandfather was Stefan {Z.}ó{l/}kiewski (Stone p236). This at least rules out the possibility that Teofilia was a patronymic.

However, it still seemed unlikely that Teofilia was a second given name. Knab (s.n. Teofila) says that it was a "more popular name in the 17th century [than today]," but does not say when the name was introduced. I suspect that its use and popularity originated with Jan III's wife Zofia. Imitation of popular royalty and saints is a hallmark of Polish naming practice. However, double given names are extremely rare in period Polish and when they do occur in Slavic languages, one name is Christian and the other is a Slavic use name. Since both Zofia and Teofilia are Christian given names, this makes it doubly unlikely that we here have an example of a double given name.

I believe I have the answer as to the origin and meaning of Teofilia in the cited name. My clue came when I noticed that the wife of Jan III was Marie Casimira d'Arquien, a French-born woman who moved to Poland at a young age to serve as a lady-in-waiting to Queen Louise Marie, wife of King Jan Kazimierz (Stone, p162). Now since Jan III's wife Marie was French, there is zero possibility that the Polish name element Casimira came to her from her birth heritage. What I do know is that King Jan Kazimierz and his queen Louise Marie built a favorable political faction around themselves by marrying off the queen's "nieces" (highly favored ladies-in-waiting). It seems likely that Jan III's wife was called Casimira because of her status in the royal court, and public use of the name would have strengthened political ties to the royalty. That is, the only logical reason for the intrusion of Casimira into an otherwise French name is to show political allegiance in the nobility. My best guess is the name Zofia Teofilia Danilowicz exemplifies another such case of political allegiance to a noble named Teofil. This would make the name inappropriate as a feminine given name, though it could still be used as a nickname in a three element Polish name.

In addition, the birthdate information given for Zofia in the LoI is incorrect. She did not give birth to Jan III Sobieski in 1607, but rather she herself was born in that year. She married Jakub in 1627 and gave birth to the future Jan III in 1629. This means that even if Teofilia had been a second given name, it is quite firmly post-1600.

Based on this information, Teofilia is only documented as a second element in a feminine name, most likely as a byname of allegiance of the type described by Nebuly. Lacking clear evidence of Teofilia used as a feminine given name, it is not registerable in that position. As a result, the submitted name has no given name and is, therefore, not registerable.

At this time, we only have evidence of use of bynames of allegiance (such as Casimira in the name of Marie Casimira d'Arquien, b. 1641) from sometime in the mid to late 17th C. If evidence can be found that the use of bynames of allegiance were a practice in Poland during period, then Teofilia would be registerable as the second element in a three element feminine name. For example, if the submitter added a feminine given name then this name would be registerable as [feminine given name] Teofilia Karaszkiewicza. [Teofilia Karaszkiewicza, 02/2004, R-Atlantia]

François la Flamme 2003.09 No documentation was presented and none was found that Langry was used as a given name in period. Lacking such evidence, the submitted name Langry de Cluny has no given name and, so, violates RfS III.2.a, which states in part "A personal name must contain a given name and at least one byname".

The documentation provided for Langry on the LoI was the statement: "Langry is dated to 1080 in Hopkins, Knights (39)." The source referred to in this statement is Andrea Hopkins, Knights (p. 39), which states, "[T]here is a record of one lord, Langry Gros, giving a mansus (a piece of land capable of supporting a household of people) to the great Abbey of Cluny in 1080 in exchange for a suite of mail."

Many modern history books modernize names. Additionally, historical figures are often referred to simply by their bynames (Mortimer, Hotspur, Percy, etc.). In the case of Langry Gros cited in Hopkins, we cannot tell from the context whether Langry is a given name or one of a pair of bynames. Therefore, we must examine other information about Langry to determine if it is plausible as a given name and whether the form Langry is a solely modern form. Metron Ariston found information about the name Langry online:

There is some significant doubt as to whether Langry is in fact a given name, though it is found as a byname in France. One of the larger on-line French onomastic dictionaries has this to say at www.jtosti.com/noms/l3.htm: "Le nom est porté dans la Seine-et-Marne et dans l'Aube. Variante: Langris (apparue au XIXe siècle). La finale -y semble indiquer qu'il s'agit d'un toponyme (nom de lieu) renvoyant à un ancien village. L'origine pourrait �tre semblable à celle de Langres (ville et plateau de la Haute-Marne), qui évoque le peuple gaulois des Lingones. A noter dans l'Ouest des hameaux appelés (la) Langrie. Il faut cependant remarquer que, dans le village de Saint-Léger (77), le nom Langry appara�t comme une déformation de Landry (voir ce nom), à moins que ce ne soit l'inverse (les membres d'une m�me famille sont appelés sur les actes du XVIIIe siècle tant�t Landry, tant�t Langry)." This would appear to indicate that at least some francophones consider it a locative byname rather than a patronymic one.

Lacking evidence that Langry in the cited Langry Gros is a period given name, we must assume it is a byname based on the evidence found by the College of Langry used solely as a byname in period. As such, the submitted name Langry de Cluny has no given name and must be returned. [Langry de Cluny, 09/2003 LoAR, R-Middle]

François la Flamme 2003.04 Serin was documented as a descriptive byname "from the agreeable song of a bird", not as a given name. Lacking evidence that it was used as a given name, it is not registerable as a given name.

In the byname le Rapp, Rapp was documented as a patronymic byname. No documentation was presented and none was found to support the addition of le to Rapp in this byname. Lacking such evidence, the byname le Rapp is not registerable. [Serin le Rapp Scheurer, 04/2003 LoAR, R-Ansteorra]

François la Flamme 2003.01 This name is being returned because it contains no given name. Liath is a Gaelic descriptive byname meaning 'gray'. No evidence was presented and none was found that it was used as a given name in period. Lacking such evidence, Liath is not registerable as a given name. [Liath of Argyll, 01/2003 LoAR, R-Calontir]
François la Flamme 2002.10 This name is being returned for multiple issues. Regarding the submitter's wishes, the LoI stated that the submitter intended the name to mean "the white-haired wife of Stefan of the Afumati family." Also, the LoI said that, "The client wants a name authentic to 15th century Romania/Hungary and cares most about having a name from that language/culture."

The first issue with this name is that there is no given name in this name, and so it violates RfS III.2.a, which requires at least one given name and at least one byname in a personal name. Second, by combining the Romanian Stefán with the Hungarian -ne, the element Stefánne violates RfS III.1.a, which requires linguistic consistency within a name phrase. Third, the number of bynames may be an issue depending upon whether the submitter wishes Romanian or Hungarian. No documentation has been presented, and none was found, that a Hungarian name would contain more than one byname. Lacking such evidence, multiple bynames are not registerable in Hungarian.

Since the LoI provided this information to the College, the College had the opportunity to research options for the submitter. Nebuly provided information regarding issues with this name and options that the submitter may wish to consider:

The three biggest problems are that (1) it mixes Hungarian and Romanian elements even within individual phrases of the name (RfS III.1.a), (2) undocumentaed[sic] use of a three element name from Hungary (my research through thousands of period names has never turned up even one case with more than one given and one byname, for more see my article Hungarian Names 101), and (3) lack of a given name (required by RfS III.2.a).

[...]

The period Hungarian form of Stephen is Istvan or Istwan, and Fehér Istwanne would be a fine documentary form for a period Hungarian woman. However, it would mean "wife of white-haired Stephen", and could not be registered in the SCA because it still would lack a given name.

To construct a registerable Hungarian name, the submitter would need to choose a feminine given name, such as Orsolya (there is a list of all the period women's names I've been able to find in Hungarian Feminine Names), and she could then be Feher Orsolya. Alternatively, the submitter could find a period Romanian given name and be [name] de la Afumatsi. Either way, this is a drastic change requiring the addition of a wholly new name element, and the submission would best be returned so that the submitter can select one.

[Fehér Stefánne de la Afumati, 10/2002, R-Middle]
François la Flamme 2002.09 This name is being returned for lack of a given name by the precedent:

While Aurich is found in Bahlow's Deutsches Nameslexikon, it is as a place name, not a given name, leaving the submitter with no given name. Since a given name is required, we are returning it for lack of a given name. [Aurich Greim, 06/99].

If the submitter is interesed in the sound of Aurich, he may wish to consider the name "Erich, a German masculine given name dated to the 13th, 14th, and 15th centuries in multiple examples on p. 123 of Bahlow (s.n. Erich)", suggested by Bright Leaf. [Aurich Rivenhall, 09/2002 LoAR, R-Caid]

 
RfS III.2.b.ii "Non-Personal Names - Names of Orders and Awards"
François la Flamme 2003.12 [Order name Order of the Serpent's Torque] No documentation was presented and none was found that the pattern [animal/creature]+[possession or adornment] is a plausible construction for an order name in period. Lacking such evidence, this order name violates RfS III.2.b.ii, which requires that "Names of orders and awards must follow the patterns of the names of period orders and awards", and must be returned. [An Crosaire, Barony of, 12/2003, R-Trimaris]
François la Flamme 2003.12 [Order name Ordre de la Plume de l'ange rouge] No documentation was presented and none was found that a name meaning 'Order of the Feather of the Red Angel' is a plausible order name in period. The submission cited a number of period order names, most of which do not in any way support this submission. The Wing of St. Michael is the only period order name cited in this submission that in any way parallels the construction of the submitted order name. However, it is not a true parallel. al-Jamal explains:

An angel is not a monster or a beast; the only "parts" that come close in the examples cited are the Wing of St. Michael. St. Michael is a very specific personage, with equally specific attributes (archangel, and so on); what is submitted is closer in spirit to "the seraphim's left foot" than St. Michael's wing, and I find nothing in the examples presented to adequately support this submission.

Lacking evidence that the submitted order name complies with RfS III.2.b.ii, which requires that "Names of orders and awards must follow the patterns of the names of period orders and awards", this name is not registerable. [An Crosaire, Barony of, 12/2003, R-Trimaris]

François la Flamme 2002.09 [Order name Order of the Silver Muse] No documentation was provided for either the elements of this order name or for the construction of this order name. RfS III.2.b.ii, Names of Orders and Awards, states:

Names of orders and awards must follow the patterns of the names of period orders and awards.

These are often the names of saints; others are similar to sign names (see RfS III.2.a.iii). Some examples are: the Order of Saint Michael, the Order of Saint Maurice and Saint Lazarus, the Brethren of the Sword, the Order of the Garter, La Toison dOr (the Order of the Golden Fleece), the Order of the Golden Rose, the Order of the Star, the Order of the Swan, La Orden de la Jara (the Knights of the Tankard), the Order of Lilies.

RfS III.2.a.ii says that some order names were "similar to sign names". In those cases, both sign names and order names are formed using names of heraldic charges. To follow the pattern of an order name based on a heraldic charge, the charge in question must either be (1) documented as a period heraldic charge, or (2) must have been ruled to be registerable as a charge within the S.C.A. No evidence was presented of a muse as a period heraldic charge and there has not yet been one registered as a heraldic charge within the S.C.A. Therefore, muse is not available for use in an order name whose name references a heraldic charge.

Lacking evidence that the elements of this order name are period and that the construction of this order name follows period naming patterns for orders and awards, this name is not registerable. [Mists, Principality of the, 09/2002 LoAR, R-West]

 
RfS III.2.b.iv "Non-Personal Names - Household Names"
François la Flamme 2004.02 [Household name Consortium Turrium No evidence was presented, nor could any be found that Consortium was a term used to refer to a group of people in period, or that Consortium Turrium follows a period naming pattern for an organized group of people in period. Lacking such evidence, this household name does not meet RfS III.2.b.iv, which states that "Household names must follow the patterns of period names of organized groups of people." Therefore, this household name cannot be registered.

In addition, the submitter may wish to know that the the submitted construction does not mean 'Consortium of the Tower' which he indicated was his desired meaning. The form that would have that meaning would be Consortium Turris. The submitted form means 'Consortium of the Towers'. [Kevin of Thornbury, 02/2004, R-Atlantia]

François la Flamme 2002.08 [Damosels of Astolat] No documentation was presented and none was found that Damosels of Astolat meets the requirements set down in RfS III.2.b.iv which states:

Household names must follow the patterns of period names of organized groups of people. Possible models include Scottish clans (Clan Stewart), ruling dynasties (House of Anjou), professional guilds (Bakers Guild of Augsburg, Worshipful Company of Coopers), military units (The White Company), and inns (House of the White Hart).

With regards to this submission, no evidence was found that Damosels is a reasonable designator for an organized group of people. Additionally, Astolat was documented only as a placename from Mallory's Le Morte d'Arthur. No support was provided and none was found that a placename only documented from literature is appropriate in a household name.

Additionally, were these issues addressed, the combination Damosels of Astolat violates RfS I.3, Inappropriate Claims, which states, "No name or armory will be registered which claims for the submitter powers, status, or relationships that do not exist." Bright Leaf explains:

As the documentation provided notes, Astolat appears in Malory's Le Morte d'Arthur. Elaine le Blanke, who seduces Launcelot, is known as the Fair Maiden of Astolat (which is the origin of Tennyson's Maiden of Shallot). The term damosel (spelled damesell in my edition of Malory) is used frequently in addressing young women in Le Morte d'Arthur. The combination of this form of address with the unique place name Astolat makes me think that the members of this household are claiming a connection to the Arthurian legend.

The combination of elements in the submitted Damosels of Astolat, all of which were documented in the submission only from Arthurian legend incidently, implies identity with the Arthurian character and so is not registerable. [Celestine Albret de Morat, 08/2002, R-Meridies]

 
RfS V.1.a.ii.a "Name Conflict - Personal Names - Difference of Name Phrases - Bynames - Bynames of Relationship"
(see also Conflict - Bynames)
François la Flamme 2001.08 [Aaron Christoferson vs. Aaron Christopher] RfS V.1.a.ii.a says, "Two bynames of relationship are significantly different if the natures of the relationships or the objects of the relationships are significantly different." As the bynames Christoferson and Christopher both mean "son of Christopher", these names are in conflict. [Aaron Christoferson of the Osprey, 08/01, A-Meridies]
 
RfS V.1.c "Name Conflict - Personal Names - Historical Personal Names"
François la Flamme 2001.08 This name is being returned for conflict with Edward the Black Prince, son of Edward III who was created Earl of Chester in 1333, Duke of Cornwall in 1337, and Prince of Wales in 1343 (Cambridge Biographical Encyclopedia s. n. Edward the Black Prince).

RfS V.1.c reads,
Protected historical personal names are protected in all of the forms in which they commonly appear. Charlemagne, which becomes Carolus Magnus in Latin and Karl der Grosse in German, is protected in all three forms.
Longstanding precedent says that Edward Duke of Cornwall would conflict with Edward of Cornwall. Thus the question that has to be answered is whether the prince was known as Edward Duke of Cornwall. If so, this submission is in conflict with him. If not, this submission is not in conflict with him. ...

As he was created Duke of Cornwall in 1337 and Prince of Wales in 1343, there is a six year period where his primary title was Duke of Cornwall. During this time, it is reasonable to assume that he was commonly known as Edward, Duke of Cornwall. As such, this submission is in conflict with him and must be returned. [Edward of Cornwall, 08/01, R-Atenveldt]
 
RfS VI.3 "Presumptuous Names - Names Claiming Specific Relationships" (see also Presumptuous)
François la Flamme 2002.02 [RfS VI.3] There was some question whether this name conflicts with Caspar, one of the three Magi, since Withycombe (s.n. Jasper) says that "Jasper is the usual English form of Gaspar or Caspar, which was the traditional name of one of the Three Kings (Gaspar, Melchior, Balthasar) into whom medieval legend transformed the 'wise men' who came to Bethlehem to worship the infant Christ." RfS V.3 "Names Claiming Specific Relationships" states "Names that unmistakably imply identity with or close relationship to a protected person or literary character will generally not be registered ... In some cases a unique name, surname, or epithet is so closely related to an individual that its use alone can imply relationship to that individual." The question is whether this name unmistakably implies identity with Caspar. Jasper is dated to 1370 in Withycombe (p. 173 s.n. Jasper) as an English given name. Wiseman is listed in Reaney & Wilson (p. 497 s.n. Wiseman). This entry dates the spellings Wisman to 1154 and Wyseman to 1471. Neither Jasper nor Wiseman are unique to the member of the Magi and so do not imply identity with him when used on their own. Therefore, this name is clear of the restriction in RfS V.3.

The question now becomes whether the submission conflicts with Caspar as a submission of Henry England would conflict with any of the kings of England named Henry. Though the group is routinely referred to as the Magi, The Three Kings, or The Three Wise Men, the individuals are not referred to as Caspar the Wise Man or Caspar Magus. Therefore, the submitted name does not conflict with a form of Caspar's name and this submission is registerable. [Jasper Wiseman, 02/02, A-Atlantia] (Editor's note: RfS section number was typoed in this ruling. It should be VI.3 rather than V.3.)
 
RfS VI.1 "Presumptuous Names - Names Claiming Rank" (see Presumptuous)
 
RfS VI.2 "Presumptuous Names - Names Claiming Powers" (see Presumptuous: Surnames/Bynames that indicate Powers)
 
RfS VI.3 "Presumptuous Names - Names Claiming Specific Relationships" (see Presumptuous: Names that imply identity with an already registered name or a protected individual and Presumptuous: Names that imply a relationship with an already registered name or a protected individual or location)