Kingdom of Atenveldt
Heraldic Submissions Page
(administered by the Brickbat Herald)
|
Atenveldt Submissions (excerpted from the S.C.A. College of Arms' Letters of Acceptance and Return)
ATENVELDT REGISTRATIONS by the College of Arms, March 2002: Ahlrich von dem Türlin. Name and device. Gules, two chevrons argent each charged with three water bougets sable. Alan of Atenveldt. Holding name and device (see RETURNS for name). Per bend azure and purpure, a bend dancetty Or between a lit candle in a flat candleholder and a basket argent. Submitted under the name Tiarnán del Sarto. Aron the Falcon. Device. Argent, a bend sinister bretessed vert between an eagle displayed and an arrowhead inverted azure. Atenveldt, Kingdom of. Badge for the Brewers' Guild. (Fieldless) A wooden tankard proper charged with a sun in splendor Or all within and conjoined to an annulet azure. A number of commenters noted that there was some overlap between the tankard and the annulet. Overlap between a charge and the charge to which it is conjoined may be reason for return. In the full-sized colored emblazon the degree of overlap is negligible, so this may be accepted. Atenveldt, Kingdom of. Badge for the Office of Regalia. (Fieldless) A wooden chest proper charged with a sun in splendor Or. Brighid ní Sheachnasaigh. Device. Per pale argent and sable, three escarbuncles counterchanged. Nice arms! Cadogan map Cado. Name change from Cadogan map Cado Blaidd (see RETURNS for device). His previous name, Cadogan map Cado Blaidd, is released. Caterina Amiranda della Quercia. Household name House Flagon and Dragon and badge (see RETURNS for second badge). Azure, three tankards and on a chief argent a dragon passant sable. Ceara inghean Chárthaigh. Name. Submitted as Ceara MacCárthaigh, the submitter requested authenticity for Irish. This name combined a feminine given name with a masculine form of a byname. As bynames were literal in Gaelic, this combination has not been registerable for some time. We have changed the byname to a feminine form in order to register this name. Cecily d'Abernon. Name. Coilean Mac Caiside. Name. Conall mac Rónáin. Name. Dagun Karababagai. Name (see RETURNS for device). Damian of Ered Sûl. Holding name and device (see RETURNS for name). Per bend gules and argent, two rapiers in saltire argent and a caravel proper sailed Or. The ship, like most ships, has sails which are roughly half the charge. The ship, therefore, is equally divided of a color (the dark brown wood proper of the hull) and a metal (the Or of the sails). RfS VIII.2.a.ii provides that "Good contrast exists between ... an element equally divided of a color and a metal, and any other element as long as identifiability is maintained." The ship is acceptably identifiable, and therefore, has good contrast with its underlying field. Submitted under the name Damian Blackthorne. Darius Xavier Drake. Device. Sable, a skull Or and on a chief triangular argent two roses in saltire gules slipped and leaved vert. Dmitrii Ivanovich Rostovskii. Name (see RETURNS for device). Dolcina da Laurito. Name and device. Purpure, two elephant trunks issuant from the flanks argent. Dorothea Micola d'Isigny. Name (see RETURNS for device). 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. Eibhilin ni Mhaghnuis. Badge. Vert, a boot and a bordure embattled Or. Elizabeth de Rose. Name and device. Azure, a pale argent between two roses slipped and leaved Or. Submitted as Ealusaid Rose, the submitter requested authenticity for "mid to late 15th century" and allowed any changes. The submitted form mixes Gaelic and Scots (a language closely related to English) in a single name. In period, this name would have been written all in Gaelic or all in Scots depending upon the language of the document in which the name was recorded. Black (p. 773 s.n. Tod) dates Elizabeth Tode to 1467, and (p. 699 s.n. Rose) Andrew de Rose to 1440. We have changed the name to a completely Scots form to meet the submitter's request for authenticity. Eric the Hun of Alta. Name. The LoI supported the submitted phrase the Hun by documenting the Old Norse term húnar: According to the Compact Oxford English Dictionary, the ON term is Húnar, and they are referred to in written literature c. 900 A.D. Therefore, the Hun is a Lingua Anglica form of húnar. Eiríkr húnar would be a fully Old Norse form of the first two elements in this name. Eva le Fayre. Name and device. Per pale gules and purpure, two Great Danes couchant regardant respectant Or. Fintán Mac Con. Name and device. Per bend sinister vert and gules, a bend sinister argent between a wolf rampant Or and a flame argent. Genevieve Gabrielle Plubel d'Avon. Device. Purpure, a unicorn doubly queued rampant regardant argent armed and gorged of a collar Or within a bordure Or semy of bunches of grapes purpure slipped and leaved vert. Gerold the Bald. Name. The submitter requested authenticity for 11th C German but allowed no changes. As the submitter's request for authenticity was not mentioned in the LoI, the College did not have the opportunity to comment on an appropriate form of this name in 11th C German that we would have included here as a courtesy to the submitter. Igor of Throckmorton. Device. Gules, three lightning bolts in pile Or and in base a gauntlet aversant argent. Ívarr bjarnherðar. Name. Submitted as Ivarr Bearshoulders, the LoI noted that the submitter "would gladly accept [the byname] being translated into Old Norse, Icelandic or Norwegian". Multiple members of the College found bynames using elements meaning 'bear' and 'shoulders' in Old Norse, along with descriptive bynames that support a byname meaning 'bear-shoulders' as being plausible in Old Norse. Therefore, we have changed the byname to the form bjarnherðar as suggested by the College. We have also added the accent to the Í in the given name, as accents should be used when ð is used in the name. James MacCoag. Name. Submitted as James MacCuagh, the submitter requested authenticity (by checking the language/culture box), but did not specify a language or culture. Presumably his desired culture is Irish based on the submitted documentation. MacCuagh is a Modern Gaelic (c. 1700 to present) form. In period, the name took Mac Dh- forms such as Mac Dhabhóc. An authentic name in period would have been written all in Gaelic or all in Anglicized Irish depending upon the language of the document that the name appeared in. A fully Gaelic form of this name would be Séamus Mac Dhabhóc or Séamas Mac Dhabhóc. Woulfe (p. 347 s.n. Mac Dhabhóc) dates the Anglicized forms M'Cawque, M'Cavoke, M'Cavog, M'Coag, and M'Coke to temp. Elizabeth I-James I. Therefore, a fully Anglicized Irish form of this name would combine James with one of these forms. Of these forms, M'Coag is the closest to the submitted form. Examples have been found of Anglicized Irish bynames using Mac- and Mc-. Therefore, MacCoag and McCoag are logical variations of the documented M'Coag. Therefore, we have changed the byname to MacCoag to meet the submitter's request for authenticity. Johann Hieronymus von Leipzig. Name. Kedivor Tal ap Cadugon. Badge. (Fieldless) A tyger passant argent enflamed azure. Kharra Unegen. Name and device. Sable, a chevron between a label dovetailed throughout and a horse's head couped contourny argent. Note: The wording on the LoI was not explicitly clear that Unegen means 'fox'. Inadequate summarization of submitted documentation on the LoI has been, and continues to be, a reason for return. In this case, the documentation was provided, just not clearly. Submission heralds, please make sure to clearly summarize all submitted documentation in the LoI. A peculiarity of SCA blazon is that the standard label is throughout by default, but the dovetailed label is couped by default. The blazon in this submission label is both dovetailed and throughout, and both these details must be blazoned. Lazarus Artifex. Badge. Per pale Or and azure, a phoenix and a bordure counterchanged. Maredudd of Atenveldt. Holding name and device (see RETURNS for name). Argent, a holly leaf bendwise sinister vert between two needles bendwise sinister sable. Submitted under the name Maredudd Gryffydd. Marguérite de Toulouse. Name change from Rose of the Forest (see PENDS for device change). Her previous name, Rose of the Forest, is released. Masala of Atenveldt. Holding name and device (see RETURNS for name). Purpure mullety of six points, a decrescent argent. Submitted under the name Masala bint Humayun al Delhi. Masala of Atenveldt. Badge. Purpure, a fess Or overall a decrescent argent. Nicolete la Rossa. Name. Submitted as Nicolete La Rossa, the submitter requested authenticity for French. We have put la in lowercase to match documented forms. Rhodri ap Gruffudd. Badge. (Fieldless) A cross formy per pale argent and gules. Rhodri Longshanks. Badge. Per fess azure and gules all ermined argent, two billets in fess Or. His previous badge, Per fess azure and gules, in fess two billets Or within ermine spots sans nombre in annulo argent, is released. Rhys Ravenscroft. Device. Per bend sinister gules and sable, a bend sinister erminois between two horses' heads couped respectant Or. Rose Blackthorne. Device. Argent, a bend sinister engrailed sable between a cat couchant gardant and a rose gules. Sibilla of Atenveldt. Name and device. Sable, two chevrons inverted argent each charged with three water bougets gules. Steffan von Hessen. Name (see RETURNS for device). Submitted as Stefhan von Hessen, the submitter requested authenticity for "German of the Holy Roman Empire about 1550." No documentation was provided and none was found that Stefhan is a plausible period variant of this name. To meet the submitter's request for authenticity, we have changed the given name to the form Steffan, which is dated to 1508 in Talan Gwynek's article "Medieval German Given Names From Silesia" (http://www.s-gabriel.org/names/talan/bahlow/). Twin Moons, Barony of. Order name L'Ordine della Luna Crescente and badge. Azure, a pall inverted bretessed between two increscents argent. ATENVELDT RETURNS by the College of Arms, March 2002: Ana ní Muireáin. Name. The byname ní Muireáin was submitted as a matronymic byname in Irish Gaelic. The registerability of matronymic bynames in Gaelic has fluctuated over time. Currently, only a few rare examples of matronymics have been found in Irish Gaelic, only two of which include a reference to a mother's given name. In both of these examples, the mother's given name and the father's given name are included in the person's byname. Additionally, all of the examples known at this time date from after 1200. This date is important because of the changes in which given names were popular, partially due to the Anglo-Norman influence which was growing at that time. Given the rarity of matronymics, and the narrow time and cultural frame in which they occur, they have been ruled registerable (though a weirdness), so long as they match the time and cultural frame in which the few known examples appear. Specifically, that results in two restrictions: - The matronymic byname must be in Irish Gaelic. - The mother's given name used in the matronymic byname must be documented as having been used after 1200. Regarding the submitted byname, Muireann is listed in Ó Corráin & Maguire (s.n. Muirenn) and in Woulfe (s.n. Muireann), and is a form consistent with Early Modern Gaelic (c. 1200 to c. 1700) and Modern Gaelic (c. 1700 to present) spelling conventions. However, the only dated examples of this name that have been found in period date to the 7th to 10th centuries. Lacking evidence that any form of Muireann was used after 1200, it is not registerable in a matronymic byname. Additionally, the particle ní was not used in Gaelic in period. The pre-1200 form was ingen uí and the post-1200 form was inghean uí. The few examples of matronymics in Gaelic are literal. No evidence has been found of clan names (including those using forms of ua/Ó) referring to a female ancestor. Therefore, the particle inghean is registerable in a matronymic construction, while inghean uí is not. If evidence were found of Muireann being used after 1200, then this byname would be registerable using inghean and with Muireann put into the genitive case and lenited. Cadogan map Cado. Device. Sable, on a plate a wolf statant gules and on a chief argent three flames gules. The device conflicts with Cartismandua Natione Veniconum, Sable, on a plate a hedgehog statant gules, on a chief argent three hedgehogs statant gules. This armory does not qualify for RfS X.4.j.ii because it is not a simple case as defined by the subsections of that rule: both the primary and peripheral charges are themselves charged. Therefore there is no difference for changing the type only of either of the two groups of tertiary charges: the tertiary group consisting of the charge on the plate or the tertiary group consisting of the charges on the chief. Caterina Amiranda della Quercia. Badge. (Fieldless) A tankard argent. Conflict with Giles MacManus, registered in the Atlantian section of this LoAR, Per bend sinister sable and gules, a tankard argent. There is only one CD, for fieldlessness. The cover letter for the March 1993 LoAR (dated 8 May 1993) stated: At their April 93 meeting, the Board of Directors decided to accept my recommendation on how to prevent SCA members from being disadvantaged by non-members during the heraldic submission process. Corpora explicitly forbids us to consider the membership status of an armory's owner, once the armory is registered; the Board agreed that the only time a member's submission could be returned for conflict by a non-member's armory is when the two were considered at the same Laurel meeting. Beginning immediately, therefore, if two submissions at the same meeting are deemed to conflict, we will give preference to the submission from the paid member. If both submitters are (or aren't) paid members, then the first received takes priority, as before. This gives an advantage to members' submissions, without requiring anyone to check every submitter's membership status. Laurel need only call the Registrar, on those rare occasions when membership becomes important; this happens seldom enough to impose no undue burden on Laurel, the Registrar, or the College. This policy has not been rescinded. It has been upheld a number of times since: Since both submissions were from the same month, we followed the strictures from the Board which meant that we had to determine the membership status of the two submitters, since if one was a member and one was not, the member would get priority (LoAR September 1996). According to the registry, both submitters were members in August 2001, and thus priority is determined by the date on the LoI (LoAR August 2001). Wreath therefore telephoned the registry. The registry indicated that Giles MacManus's membership was current at the time of the Wreath meeting, and that Caterina had not been a member since March 2000. Since the armory of a member takes precedence over armory of non-members, Giles's armory takes precedence. Cosimo Orsini. Name and device. Argent, on a bend vert between two brown bears statant proper three fleurs-de-lys Or. The submission was withdrawn on the July 2002 Atenveldt Letter of Intent. Dagun Karababagai. Device. Gules, on a bend sable fimbriated between two bear's paw prints argent a comet inverted headed of a roundel Or charged on the head with a torteau. This must be returned for charging a tertiary charge. RfS VIII.1.c.ii, Layer Limit, states "All charges should be placed either directly on the field or entirely on other charges that lie on the field." Here, the roundel lies on the comet, which does not lie on the field. There were some other concerns about the artwork. Pawprints do not show this degree of disarticulation in nature: generally the 'toes' may be separated from the 'pads' but there is no separation between the joints of the toes in the pawprint. This emblazon shows too many separate pieces of the toes to be a pawprint. Charges should be drawn either in a period heraldic stylization (where available) or in a recognizable naturalistic style. Since pawprints are not found in period heraldry, it is all the more important that they be drawn recognizably. Some commenters felt that heading a comet of a roundel, rather than a mullet or an estoile, might be an additional problem with this armory. However, given the different period depictions of comets, a comet headed of a roundel is a reasonable variant. Damian Blackthorne. Name. This name conflicts with Damon Blackthorn (registered February 1992). The differences between the sound and appearance of the given names is insufficient. His armory has been registered under the holding name Damian of Ered Sûl. Dmitrii Ivanovich Rostovskii. Device. Ermine, on a pile gules a demi-sun issuant from base Or. A demi-sun is a semi-circular charge. If a demi-sun is drawn from the bottom of a pile, it should subtend an arc of a circle. This charge subtends an arc of some tall thin oval and is not clearly recognizable as a demi-sun: it's too elongated. (It's so difficult to describe an unusual shape in words. The best I can do here is "an ice cream cone with some small sun rays issuant from the top of the ice cream scoop".) The rays of the charge are too short to allow this charge to be reblazoned as rays of the sun issuant from base (as can be seen in Parker's A Glossary of Terms used in Heraldry under Ray). Because this charge cannot be blazoned, it must be returned for redrawing. It is not clear whether a demi-sun can be correctly drawn issuant from base on a charge as narrow at the base as a pile. On resubmission, the submitter should be careful to avoid conflict with Emrys Montgomery, Barry azure and Or, on a pile gules fimbriated argent a sun in his splendor Or. Dorothea Micola d'Isigny. Device. Gules, a castle and on a point pointed Or three pellets two and one. As drawn, this is neither a point pointed nor a per chevron field. This must therefore be returned for redrawing. A point pointed should go less than halfway up the shield. A per chevron field should balance the top and bottom halves of the field. Farisa Ramia Hameedah bint Kathoum. Name. This name is being returned for multiple issues. Farisa, which the submitter intended to mean 'horsewoman', is the feminine form of Faris, which is listed as an Arabic form of Knight in "The List of Alternate Titles as approved by the College of Arms" (http://www.sca.org/heraldry/titles.html). Therefore, Farisa (like Knight) is a restricted title and may not be registered as part of an SCA name. The element Ramia was documented on the LoI as follows: "The Arabic word rama/ramy means 'to shoot' or 'to fire' (pp. 360-361, A Dictionary of Modern Written Arabic, Arabic-English, Hans Wehr, McDonald and Evans Ltd., London, reprinted 1980); the submitter's husband was raised and educated in Iraq, and Arabic is his first language." Unfortunately, knowledge of a modern language does not necessarily imply a knowledge of the same language in period. As a result, a simple statement by a native speaker has not been sufficient documentation for a number of years. One precedent that outlines the issue is: Most of us wouldn't trust the average English-speaker to get Early Modern English correct (witness the number of people who have trouble understanding Shakespeare!); anything earlier is even more unlikely. And there is no reason to believe that English is peculiar in this. We have no more cause to trust a modern German speaker's knowledge of Middle High German than to trust a modern English speaker's knowledge of Middle English. Native speakers of English submitting English names frequently 'know' that they are correct -- even when they are altogether wrong. Without sufficient information with which to judge the reliability of the source, or the background and training of the speaker, we cannot assume any special knowledge about period naming practice or grammar. When the documentation boils down to "because I said so", it cannot be accepted on its face. [6/94c, p.3] Lacking documentation that Ramia would have been used in an Arabic byname in period, it is not registerable. The element Kathoum, used in the byname bint 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 bint Kathoum as an Arabic byname in her SCA name. Since Kathoum is a modern Arabic masculine given name, the byname bint Kathoum complies with RfS III.1.a, which requires linguistic consistency in a byname. An additional issue is that this name uses inconsistent transliteration. Al-Jamal wrote: Okay, first off, either drop the final "h" from Hameedah (which we can't do if she's applying the legal name allowance, which only permits the exact legal name) or add it to Farisa and Ramia. "Submitted as Khadijah bint Mika'il al-Zarqa, it combines two different forms of transliteration. We have changed the spelling of the byname to make the entire name consistent." (Elsbeth Anne Roth, LoAR September 2000, p. 12) al-Jamal provided commentary regarding another issue with this name: Finally, the name is not constructed as names were in period. Hameedah bint Kathoum al-Ramiah (were all of the elements documented) would be the expected period form; Hameedah al-Ramiah bint Kathoum (the same caveat) might also be registrable. But the submitted form is unlike period names (or modern, so far as I can see) in structure and grammar. Lacking evidence that a byname would precede a given name in this manner in a period Arabic name, this construction is not registerable. Hawk's Rest, Shire of. Badge. Or, on a tower pean a hawk's head erased Or. Conflict with Torrin the Wanderer, Or, on a tower per pale gules and azure, a compass star Or. There is one CD for changing the tincture of the tower but nothing for changing the type only of tertiary charge by RfS X.4.j.ii, because a charged tower will not qualify for this rule. According to X.4.j.ii, "A charge is suitable for the purposes of this rule if (a) it it simple enough in outline to be voided, and (b) it is correctly drawn with an interior substantial enough to display easily recognizable charges." Towers are not simple enough in outline to be voided. In addition, the badge may not be accepted for administrative reasons. The name of the branch was returned in April 2002, so the badge must be returned for lack of a name to which to register it in any case. Maredudd Gryffydd. Name. This name conflicts with King Maredudd ap Gruffydd (d. 1155), son of King Gruffydd ap Rhys, who retook most of the Welsh kingdom of Deheubarth from the Normans. Though Maredudd does not have his own entry in the online Encyclopedia Britannica, we protect rulers of countries who do not have their own entries in general encyclopedias. This practice was demonstrated with the return of the name Gruffydd ap Gwineth, which was judged as conflicting with Gruffudd, King of Gwynedd to 1137 (December 1997 LoAR). Just as Gruffudd does not have his own entry in a general encyclopedia, yet is protected, so Maredudd is also protected. His armory has been registered under the holding name Maredudd of Atenveldt. Masala bint Humayun al Delhi. Name. 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. Her armory has been registered under the holding name Masala of Atenveldt. Mu'Alim Rami Kathoum ibn Abdul Majeed. Name and device. Per fess vert and sable, on a fess argent between the Arabic words "Allah Akbar" Or and a scimitar fesswise argent a bow sable. This name is being returned for multiple issues. Mu'alim, which the submitter intended to mean 'teacher', is listed as an Arabic form of Master, in the form Mu'allim, in "The List of Alternate Titles as approved by the College of Arms" (http://www.sca.org/heraldry/titles.html). al-Jamal explains: Mu'allim is a restricted title, the Arabic equivalent of master. (That it also has the connotation of "teacher" was a bonus to those of us who researched the Arabic alternate titles list.) Therefore, Mu'Alim (like Master) is a restricted title and may not be registered as part of an SCA name. The element Rami was documented on the LoI as follows: "The Arabic word rama/ramy means 'to shoot' or 'to fire' (pp. 360-361, A Dictionary of Modern Written Arabic, Arabic-English, Hans Wehr, McDonald and Evans Ltd., London, reprinted 1980); I am trusting the submitter on this, as he was raised and educated in Iraq, and Arabic is his first language." Unfortunately, knowledge of a modern language does not necessarily imply a knowledge of the same language in period. As a result, a simple statement by a native speaker has not been sufficient documentation for a number of years. One precedent that outlines the issue is: Most of us wouldn't trust the average English-speaker to get Early Modern English correct (witness the number of people who have trouble understanding Shakespeare!); anything earlier is even more unlikely. And there is no reason to believe that English is peculiar in this. We have no more cause to trust a modern German speaker's knowledge of Middle High German than to trust a modern English speaker's knowledge of Middle English. Native speakers of English submitting English names frequently 'know' that they are correct -- even when they are altogether wrong. Without sufficient information with which to judge the reliability of the source, or the background and training of the speaker, we cannot assume any special knowledge about period naming practice or grammar. When the documentation boils down to "because I said so", it cannot be accepted on its face. [6/94c, p.3] Lacking documentation that Rami would have been used in an Arabic byname in period, it is not registerable. al-Jamal provided commentary regarding other issues with this name: Abdul Majeed is more usually transliterated 'Abd al-Majid. Finally, the name is not constructed as names were in period. Kathoum ibn 'Abd al-Majid al-Rami (assuming that rami can be documented) would be the expected form. The submitted form is unlike period names (or modern, so far as I can see) in structure and grammar. Lacking evidence that a byname would precede a given name in this manner in a period Arabic name, this construction is not registerable. As the submitter does not allow major changes, we were unable to drop the problematic elements in order to register this name. The words "Allah Akbar" in the device are not written in a standard Arabic form: a diacritical marking is misplaced. For examples of this phrase, see http://www.islaam.org/Taqwaa/taqwaa.html or http://members.lycos.co.uk/islaam/. Because we do not know what the altered writing means, it has the potential to either be nonsensical or offensive. The phrase "Allah Akbar" means roughly "God is Most Great". The phrase is acceptable if spelled correctly. Mu'Alimah Ramia Jameela Ghafoor. Name. This name is being returned for multiple issues. Mu'allimah, which the submitter intended to mean 'teacher', is listed in the form Mu'allima (an alternate transliteration) as an Arabic form of Mistress in "The List of Alternate Titles as approved by the College of Arms" (http://www.sca.org/heraldry/titles.html). al-Jamal explains: Mu'allima is a restricted title, the feminine Arabic equivalent of mistress. (That it also has the connotation of "teacher" was a bonus to those of us who researched the Arabic alternate titles list.) Therefore, Mu'allimah (like Mistress) is a restricted title and may not be registered as part of an SCA name. The element Ramia was documented on the LoI as follows: "The Arabic word rama/ramy means 'to shoot' or 'to fire' (pp. 360-361, A Dictionary of Modern Written Arabic, Arabic-English, Hans Wehr, McDonald and Evans Ltd., London, reprinted 1980); the submitter's husband was raised and educated in Iraq, and Arabic is his first language." Unfortunately, knowledge of a modern language does not necessarily imply a knowledge of the same language in period. As a result, a simple statement by a native speaker has not been sufficient documentation for a number of years. One precedent that outlines the issue is: Most of us wouldn't trust the average English-speaker to get Early Modern English correct (witness the number of people who have trouble understanding Shakespeare!); anything earlier is even more unlikely. And there is no reason to believe that English is peculiar in this. We have no more cause to trust a modern German speaker's knowledge of Middle High German than to trust a modern English speaker's knowledge of Middle English. Native speakers of English submitting English names frequently 'know' that they are correct -- even when they are altogether wrong. Without sufficient information with which to judge the reliability of the source, or the background and training of the speaker, we cannot assume any special knowledge about period naming practice or grammar. When the documentation boils down to "because I said so", it cannot be accepted on its face. [6/94c, p.3] Lacking documentation that Ramia would have been used in an Arabic byname in period, it is not registerable. No documentation was provided in the LoI for the element Ghafoor and the College found none. Lacking documentation that this element is plausible as part of a period name, it is not registerable. Padraig Dillon of Liaththor. Device. Sable, a maunch fracted in pale and issuant from base a demi-sun argent. The maunch fracted is not identifiable. It appears to be two slightly different styles of maunches addorsed rather than a single fracted charge. Rami Hussein ibn Kathoum. Name. The element Rami was documented on the LoI as follows: "The Arabic word rama/ramy means 'to shoot' or 'to fire' (pp. 360-361, A Dictionary of Modern Written Arabic, Arabic-English, Hans Wehr, McDonald and Evans Ltd., London, reprinted 1980); I am trusting the submitter's father, as he was raised and educated in Iraq, and Arabic is his first language." Unfortunately, knowledge of a modern language does not necessarily imply a knowledge of the same language in period. As a result, a simple statement by a native speaker has not been sufficient documentation for a number of years. One precedent that outlines the issue is: Most of us wouldn't trust the average English-speaker to get Early Modern English correct (witness the number of people who have trouble understanding Shakespeare!); anything earlier is even more unlikely. And there is no reason to believe that English is peculiar in this. We have no more cause to trust a modern German speaker's knowledge of Middle High German than to trust a modern English speaker's knowledge of Middle English. Native speakers of English submitting English names frequently 'know' that they are correct -- even when they are altogether wrong. Without sufficient information with which to judge the reliability of the source, or the background and training of the speaker, we cannot assume any special knowledge about period naming practice or grammar. When the documentation boils down to "because I said so", it cannot be accepted on its face. [6/94c, p.3] Lacking documentation that Rami would have been used in an Arabic byname in period, it is not registerable. 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. al-Jamal provided commentary regarding other issues with this name: Finally, the name is not constructed as names were in period. Hussein ibn Kathoum al-Rami (were all of the elements documented) would be the expected period form; Hussein al-Rami ibn Kathoum (with the same caveat) might also be registrable. But the submitted form is unlike period names (or modern, so far as I can see) in structure and grammar. Lacking evidence that a byname would precede a given name in this manner in a period Arabic name, this construction is not registerable. Rami Muhammad ibn Kathoum. Name. The element Rami was documented on the LoI as follows: "The Arabic word rama/ramy means 'to shoot' or 'to fire' (pp. 360-361, A Dictionary of Modern Written Arabic, Arabic-English, Hans Wehr, McDonald and Evans Ltd., London, reprinted 1980); I am trusting the submitter's father, as he was raised and educated in Iraq, and Arabic is his first language." Unfortunately, knowledge of a modern language does not necessarily imply a knowledge of the same language in period. As a result, a simple statement by a native speaker has not been sufficient documentation for a number of years. One precedent that outlines the issue is: Most of us wouldn't trust the average English-speaker to get Early Modern English correct (witness the number of people who have trouble understanding Shakespeare!); anything earlier is even more unlikely. And there is no reason to believe that English is peculiar in this. We have no more cause to trust a modern German speaker's knowledge of Middle High German than to trust a modern English speaker's knowledge of Middle English. Native speakers of English submitting English names frequently 'know' that they are correct -- even when they are altogether wrong. Without sufficient information with which to judge the reliability of the source, or the background and training of the speaker, we cannot assume any special knowledge about period naming practice or grammar. When the documentation boils down to "because I said so", it cannot be accepted on its face. [6/94c, p.3] Lacking documentation that Rami would have been used in an Arabic byname in period, it is not registerable. 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. al-Jamal provided commentary regarding other issues with this name: Finally, the name is not constructed as names were in period. Muhammad ibn Kathoum al-Rami (were all of the elements documented) would be the expected period form; Muhammad al-Rami ibn Kathoum (with the same caveat) might also be registrable. But the submitted form is unlike period names (or modern, so far as I can see) in structure and grammar. Lacking evidence that a byname would precede a given name in this manner in a period Arabic name, this construction is not registerable. Romanus de Castelyn. Name. The submitted byname de Castelyn combines the locative particle de 'of' with the occupational byname Castelyn, which is not a plausible combination. Metron Ariston explains: Actually, the listing for Castellan in Reaney and Wilson has two etymologies cited with rather different orthographies listed. The one which contains Walter Castelyn is occupational from the Old French chastelain and the earlier forms have the article le not a preposition. The forms with the preposition derive from Castellion in France: William de castellon, Hugo de Castelliun and Robert de Chastellun. As the submitter allowed no changes, we were unable to either drop de and register the byname simply as Castelyn or change the spelling of Castelyn to a documented locative form. Steffan von Hessen. Device. Or goutty de sang, a pall inverted engrailed between two eagles displayed heads to sinister sable and a rose gules. The gouttes are too numerous and too small to be identifiable. There was a significant discrepancy between the emblazon on the forms and the mini-emblazon on the Letter of Intent. There are approximately 130 gouttes on the form, and approximately 40 gouttes on the mini-emblazon. Forty charges is a large number to have on the field compared to the standard period depiction of a group of strewn charges (which often has as few as ten charges on the field). As long as the charges in a group of strewn charges maintain their identifiability, they are acceptable regardless of the exact number of charges in the emblazon. Most commenters noted the typographical error in the blazon that made the field Gules goutty de sang. Because the field was not blazoned correctly, the College could not perform correct conflict research on this submission. Theodericus Lucem Quaeror. Name. The submitter requested authenticity for 6th to 7th C Central Europe. No evidence was presented and none was found that a byname meaning 'light seeker' would have been applied to a person in period. Metron Ariston found evidence of a Latin word, lucipetus, with this meaning: To my great surprise, there is actually a Latin word for "light seeking" and, what is more, it occurs in a work that would be familiar to educated men for most of our period, the Etymologies or Origines of Isidore of Seville (560-636). It even has an antonym (lucifugus). Mind you, the term is applied to a fly by Isidore who was dealing with the natural world at that point [...] As we have no evidence that lucipetus, or a different phrase meaning 'light seeker', would have been used to describe a human in period, a byname with this meaning is not registerable. If evidence were found that a byname with this meaning would have been been used to describe a human in period, then Theodericus Lucipetus would be a registerable form of this name. Tiarnán del Sarto. Name. This name combines the Irish Gaelic Tiarnán with the Italian del Sarto. Mixing Anglicized Irish and Italian in a single name was ruled unregisterable in April 2000. As mixing Irish Gaelic and Italian in a single name is less likely than mixing Anglicized Irish and Italian, this combination is similarly unregisterable. Additionally, Tiarnán is a Modern Irish Gaelic (c. 1700 to present) form, and so is not registerable. Registerable forms include the Middle Irish (c. 900 to c. 1200) Tigernán and the Early Modern Gaelic (c. 1200-c. 1700) Tighearnán found in Ó Corráin and Maguire (s.n. Tigernán). His armory has been registered under the holding name Alan of Atenveldt. Tieg ap Gwylym. Device. Sable, a rabbit sejant erect affronty paly argent and azure on a chief argent two fleurs-de-lys azure. The identifiability of the rabbit is unacceptably compromised by the combination of the unusual sejant erect affronty posture and the paly tincture of the rabbit. While there is period armory depicting animals in multiply divided tinctures such as barry and checky, the period animals so tinctured are in their most identifiable postures. Sejant erect affronty is not such a posture. In addition, period examples of sejant erect affronty, such as the crest of Scotland, are generally drawn with the forepaws displayed. Such a rendition is more identifiable than the depiction in this emblazon, where the forepaws lie entirely on the rabbit's body. THE FOLLOWING HAVE BEEN PENDED UNTIL THE JANUARY 2003 LAUREL MEETING Marguérite de Toulouse. Device change. Argent, on a bend sinister vert an ivy vine throughout argent in dexter chief a butterfly sable. The tincture of the ivy vine was omitted in the letter of intent, leading the College to surmise that it was sable. This must be pended for further research. If this submission passes, the submitter will release her currently held device, Per chevron engrailed argent and azure, a castle sable and four fish naiant contourny Or. |
This page is best viewed with a minimum of 800 x 600 resolution, and 16 million colors.