Society for Creative Anachronism
College of Arms
For the November 2021 meetings, printed January 8, 2022
To all the College of Arms and all others who may read this missive, from Emma Laurel, Elisabetta Pelican, and Oddr Wreath, greetings.
We are pleased to announce the selection of Ragna stórráđa Úlfsdóttir, Rouge Scarpe Herald for the kingdom of the Middle, as successor to the office of Quarterstaff, with a transition happening over the next few months as items requiring a pend for redraw are identified.
We wish to take this moment to thank Cormac Mór and congratulate him for his success in defining the office of Quarterstaff, which has been of great benefit to our submitters. We look forward to seeing what he does next.
This month, we considered whether or not the bynames Bond and Pond were too similar in sound and appearance to allow them to be clear under PN3C3. The decision to consider these sounds in conflict was based on how we create the sounds of consonants, as reflected in the International Phonetic Alphabet, or IPA. More information on IPA can be found here: http://dialectblog.com/the-international-phonetic-alphabet/ipa-consonants/. IPA groups sounds by the way that we create them in the mouth (consonant position) and the type of sound that is created (manner of articulation). This tool should help to demonstrate why some sounds are too similar to register, even when they visually look different, and why the exception to SENA PN3C3 exists.
Many of the standard articles that we use for Arabic names rely on particular transliterations systems, some relatively casual (not distingushing long and short vowels or emphatic consonants from their non-emphatic equivalents) and others relatively complete and scholarly. Most, however, do not clearly show the way the article al- 'the' is pronounced before the "sun consonants" in classical Arabic. For these consonants, the l assimilates to the following sound, so that in the name al-Zahra' the article is pronounced \az\ even though it is written al- in many transliteration systems.
For more information about how the particle al behaves when it is followed by a sun or a moon consonant in Classical Arabic, please reference this excellent guide by Sara al-Garnatiyya, Beacon Principal Herald: https://sarasartsandsciences.wordpress.com/2021/12/12/classical-arabic-grammar-diatrical-marks-the-definite-article-sun-letters-and-moon-letters/. We encourage people to consider transliterations that include that pronunciation information but remind remind submitters and heralds alike that any standard transliteration of non-Roman letters is acceptable, as long as the whole name is consistent, per SENA Appendix D.
Palimpsest's August 12th proposal to add a standard letter to Appendix D for groups to grant permission to conflict for an augmentation is accepted. Note that permission to conflict is not required if the badge being used for the augmentation is designated as a "standard augmentation" in the O&A. The updated version of Appendix D will be available at http://heraldry.sca.org/admin.html shortly.
As proposed in Palimpsest's August 12th Rules Letter, SENA A2B2c is revised. The new wording is:
c. Constructed Monsters: There is a pattern of creating monsters by combining elements from different animals and monsters known in period. Thus, a new monster that follows these patterns of combining identifiable elements from different animals and monsters is registerable. Items which can be constructed using this rule are registerable, even if it recreates a monster which is a wholly post-period invention.
For example, there is a pattern of combining the top half of quadrupeds with a fish tail to make a creature, as in a heraldic sea-horse. This pattern can be used to create an unattested sea-camel.
The insert/delete version of that wording is:
c. Constructed Monsters: There is a pattern of creating monsters by combining elements from different animals and monsters
known in period. Thus, a new monster that follows these patterns of combining identifiable elements from different animals and monsters is registerable. Items which can be constructed using this rule are registerable, even if it recreates ain heraldrymonster which isnamed heraldica wholly post-period inventiondemonstrated to be.in real-world heraldryFor example, there is a pattern of combining the top half of quadrupeds with a fish tail to make a creature, as in a heraldic sea-horse. This pattern can be used to create an unattested sea-camel.
The description of Appendix A in SENA PN2B is updated as proposed in Palimpsest's August 12th Rules Letter. The examples are unchanged and are not included here. The new wording is:
B. Name Phrase Requirements: A registerable personal name must be made up of at least two name phrases: a given name and at least one byname (which may appear to be a second given name). While it is easy to document individuals who are identified only with a single given name, we do not allow the registration of single element personal names. Individuals may use those names, but may not register them.
Each name phrase must be grammatically correct for its position in a name. In some languages, spelling changes are used to indicate aspects of relationships in bynames.
Capitalization should be consistent with the language of the name phrase. Some patterns for capitalization that do not require further documentation can be found in Appendix A.
The insert/delete version:
B. Name Phrase Requirements: A registerable personal name must be made up of at least two name phrases: a given name and at least one byname (which may appear to be a second given name). While it is easy to document individuals who are identified only with a single given name, we do not allow the registration of single element personal names. Individuals may use those names, but may not register them.
Each name phrase must be grammatically correct for its position in a name. In some languages, spelling changes are used to indicate aspects of relationships in bynames.
Capitalization should be consistent with the language of the name phrase. Some patterns for capitalization
that do not require further documentation can be found in Appendix A.in important European languages
With a modification to the example, the proposal on Palimpsest's August 12th Rules Letter to modify SENA PN2C to update the description of Appendix A and to treat name phrases submitted under the Legal Name Allowance as gender neutral is accepted. No changes are made to PN2C1 or PN2C2. The revised wording is:
C. Name Requirements: A name submission must be consistent with the standards laid out in this section for temporal and geographical compatibility. The position of each name phrase in the overall name must be shown to be appropriate for that type of name phrase in its language and cultural tradition. Patterns for name grammar in some languages can be found in Appendix A. Any pattern found there does not need further documentation; a reference to Appendix A will be sufficient. Other patterns require documentation.
For example, there is evidence for names in Spanish with two bynames in certain patterns. One pattern is a patronymic byname followed by a placename, as in Ruy Diaz de Bivar. That would justify Juan Perez de Madrid, but would not support the registration of Juan de Madrid Perez.
Note that name phrases submitted under the legal name allowance are considered gender neutral.
For example, a submitter whose legal given name is Avery could register either Avery mac Briain or Avery inghean Bhriain (regardless of their gender) as a culturally mixed name under PN2C2d. Likewise, a person with the legal name of Dancia could register either Dancia filia William or Dancia filius William and a person with the legal given name of Jayden could register Jayden Hakonsdottir or Jayden Hakonsson regardless of their gender.
For example, a person with the legal name Inga Finnbogadóttir could register William Finnbogadóttir regardless of their gender. This applies even if the byname is a literal matronymic rather than an inherited surname.
In addition, the name as a whole must follow a period pattern for personal names. Any name must follow the pattern described in one of the two sections below.
The insert/delete version:
C. Name Requirements: A name submission must be consistent with the standards laid out in this section for temporal and geographical compatibility. The position of each name phrase in the overall name must be shown to be appropriate for that type of name phrase in its language and cultural tradition.
Patterns for name grammar inSome psome languages can be found in Appendix A. Any pattern found there does not need further documentation; a reference to Appendix A will be sufficient. Other patterns require documentation.important EuropeanFor example, there is evidence for names in Spanish with two bynames in certain patterns. One pattern is a patronymic byname followed by a placename, as in Ruy Diaz de Bivar. That would justify Juan Perez de Madrid, but would not support the registration of Juan de Madrid Perez.
Note that name phrases submitted under the legal name allowance are considered gender neutral.
For example, a submitter whose legal given name is Avery could register either Avery mac Briain or Avery inghean Bhriain (regardless of their gender) as a culturally mixed name under PN2C2d. Likewise, a person with the legal name of Dancia could register either Dancia filia William or Dancia filius William and a person with the legal given name of Jayden could register Jayden Hakonsdottir or Jayden Hakonsson regardless of their gender.
For example, a person with the legal name Inga Finnbogadóttir could register William Finnbogadóttir regardless of their gender. This applies even if the byname is a literal matronymic rather than an inherited surname.
In addition, the name as a whole must follow a period pattern for personal names. Any name must follow the pattern described in one of the two sections below.
As proposed in Palimpsest's August 12th Rules Letter, SENA Appendix D is updated to add acceptable transliterations in Old English. The letters đ (edh) and ţ (thorn) are generally interchangeable in Old English. Both may be transcribed as th or d; this need not be consistent in the same name.
We wish to thank Gunnv{o,}r Orle for her research on this issue.
The updated version of Appendix D will be available at http://heraldry.sca.org/sena.html shortly.
SENA Appendix A is updated, as proposed in Palimpsest's August 12th Rules Letter, to add double descriptive bynames as a pattern in Old Norse that does not need further documentation.
The updated version of Appendix A will be available at http://heraldry.sca.org/sena.html shortly.
Based on Palimpsest's August 11th Rules Letter, SENA PN1B2g - Existing Registration Allowance is updated to expand the list of "close relative" to match precedent and to address how potentially offensive name elements are handled under the Existing Registration Allowance. It is also updated to allow changes required for gender as necessary when the registered name is a relationship name (e.g. changing -dottir to -son) or a descriptive, locative, or other type of byname that changes based on gender. The new wording is below. Due to the extensive revisions of this section, an insert/delete version of the wording is not included.
g. The Existing Registration Allowance (ERA): In a new personal name submission, an individual may use name phrases already registered to them or a close legal relative (such as parent, spouse, child, sibling, aunt/uncle, etc.), even if that name phrase would no longer be allowed under the current rules. To do this, the submitter must demonstrate the relationship through legal documents or through attestation of relationship from the individual whose name is already registered. Wording for an attestation can be found in Appendix D of the Administrative Handbook. Note that a letter of permission to presume/claim relationship (found in the same appendix) may also be needed. See the December 2019 Cover Letter for a discussion on which letter is needed when.
For example, given a registered Arwen Gandalfsdottir, the existing registration allowance applies to the name phrases Arwen, Gandalfsdottir, and Arwen Gandalfsdottir. For example, in Ciar ingen Donnchaid meic Con Duib the name phrases are Ciar, ingen Donnchaid, Ciar ingen Donnchaid, meic Con Duib, and Ciar ingen Donnchaid meic Con Duib. For a registered Skalla-Brandr, Skalla is a pre-pended byname and is a name phrase. The other name phrases that can be registered under the existing registration allowance are Brandr and Skalla-Brandr.
Only the exact, actual name phrase from the registered form may be used, not variants, patterns, etc. except:
1. In cases where the existing registered element is being used in a relational byname (e.g., patronymic/matronymic, multi-generational, spousal, brother/sister, etc.): The registered element may only be modified as necessary to construct the byname. The relationship being claimed under this exception must match the legal relationship of the parties involved and must be documented as described above.
For example, a daughter of a registered Hrafn wishes to register the Demotic Egyptian given name with a patronymic byname, Djehutyiirdis Hrafnsson. This is allowed as a legal parent/child relationship exists; the genders of the names registered/being registered do not matter. However, if the person submitting the new name was instead Hrafn's brother, Sedjemniykhnum Hrafnsson could not be registered, as a legal parent/child relationship does not exist between them.
2. In cases where the submitter wishes to change the gender of an existing registered element: The registered element may be any element (e.g., descriptive byname, locative byname, or patronymic/matronymic) that changes to match the gender of the given name. The submitter's legal gender does not matter.
For example, in the name Tofi Durinsson Durinsson is a gendered name element (patronymic). If the submitter wished to register Tofa (a feminine given name) the existing registration allowance would allow the registration of Tofa Durinsdottir.
In some cases, particularly with relationship bynames, there may be multiple ways to form the byname based on the above exceptions. See Appendix O, Existing Registration Allowance and Bynames, for guidance in this process.
The use of the existing registration allowance does not allow the submitter to evade new style problems (as discussed in PN.2 below). It only allows the submitter to keep style problems that already exist with the registered name. Also, documentation under this allowance does not exempt a name or name phrase from conflict or presumption rules, unless that rules violation is itself part of the existing registration in question. A name element that is considered offensive under PN5B may only be registered to the original owner under the existing registration allowance, not to close legal relatives, though names that increase offense may still be returned on a case-by-case basis.
In support of the changes to PN1B2g shown above, SENA Appendix O is being created. This appendix will not be added to SENA until PN5B is approved by the Board of Directors. For that reason, the entire text of the appendix is included below.
The existing registration allowance (ERA), including the required documentation, is defined in PN1B2g. This appendix provides some examples and guidance for creating gendered bynames, that is, names that must change in order to match the gender of the given name, and relationship bynames. This list is not exhaustive nor exclusive; it is meant to provide guidelines for using the ERA. Names submitted under the exceptions to PN1B2g will be decided on a case-by-case basis.
1. Unmarked Relationship Bynames
In languages with unmarked patronymics/matronymics, a registered given name can be used without change to indicate a parent/child relation.
For example, English uses unmarked patronymics. Therefore a registered Arabic Da'ud can be used with a submitted Thomas to form Thomas Da'ud. As no changes are required to the name, Da'ud can be legally related in any way to Thomas, not just his father, as neither exception under PN1B2g is required.
2. Latin Relational Bynames
In Latin, relational bynames (particularly patronymics/matronymics) in many cultures can be found in period where the given name is treated as indeclinable. That is, the name doesn't change to show genitive case. In cases where there are no examples of how the name was treated in Latin (period or post-period), it may be treated as indeclinable.
For example, a young woman's father has a Japanese persona, and his registered given name is Tokihiro. She's not quite sure where she wants to eventually land in the SCA and chooses the name Anna in Latin because it works across multiple cultures. As we don't have example of Tokihiro in Latin, it may be treated as indeclinable and her name registered as Anna filia Tokihiro. Similarly, if Tokihiro's brother and nephew decide to register Johannes and Georgius respectively while denoting their relationship to Tokihiro they could register Johannes frater Tokihiro and Georgius nepos Tokihiro.
3. Relationship Bynames in Original Language
There are a number of names that were previously registerable but have become unregistrable, or only registrable in a different language, as our knowledge has improved. These names can be registered following the grammar of the language they were considered when registered assuming that they are compatible with the new name being registered.
For example, pre-2009 a gentleman registered the given name Ian with the Middle Irish byname mac Gadhra. The Ian element has been since redocumented as a grey period English masculine given name through FamilySearch records. His daughter, however, wants to register a multi-generational Gaelic name and be Oébfinn ingen Iain mhic Gadhra. Treating the element Ian as Gaelic rather than English means it would be in the genitive case but not lenite, and the modification of grammar for the multigenerational byname (mac to mhic) would be permitted using the exception in PN1B2g.
For example, suppose the daughter of a woman named Eowyn wants to register the name Elizabeth and mark herself in English as Eowyn's daughter. The submitter does not want to use an unmarked matronymic, even though Elizabeth Eowyn would be permitted. Because the submitter intends to have an English name, and Eowyn was registered as an Old English name, Eowyn can be treated as English and we would therefore register Elizabeth Eowynsdohter.
4. Relationship Bynames in Different Languages
Registered names are considered neutral in time and place; therefore, relationship bynames can be formed in one language from a name registered based on a different language. In many cases it is possible to simply add the appropriate marker to the registered name to create the relationship byname.
For example, a woman wishes to include the registered name of her husband Cedric in her name but wants to be Taisiia as her persona is Russian. As Wickenden's A Dictionary of Period Russian Names tells us that one way a spousal byname in Russian would have been formed is by adding -skaia to the given name, an option for her would be Taisiia Cedricskaia. She could not, however, register Taisiia Cedricskona, as that spousal byname construction is Old Norse (and neither Taisiia nor Cedric is Old Norse).
For example, Lórien has a son who wants to go by the Old Norse name Flosi and wants to be known as Lórien's son. Since Lórien is not an Old Norse name the matronymic may be created by adding -s, so the name can be registered as Flosi Lóriensson. Similarly, in 1979 we registered the given name Strider. Say his hypothetical wife finally wants to register her name, and she wants to be Inga, wife of Strider. She could register Inga Striderskona, using the attested construction for a spousal byname in Old Norse.
For example, the mother of someone with the registered name of Olaff wishes to be known by the Arabic name Maryam and as the mother of Olaff. Following the examples in Da'ud ibn Auda's Period Arabic Names and Naming Practice she may construct the name using the kunya pattern umm <child's name> which would result in the name Umm Olaff Maryam ("the mother of Olaff, Maryam").
For example, Welsh has a pattern of ap <given name> or verch <given name>. Thus the daughter of a registered Da'ud who wishes the Welsh given name Jenett may regiester Jenett verch Da'ud.
5. Gender Change in the Same Language
a. If a submitter has a gendered byname (a byname that must or may change to match the given name) registered and changes the gender of their registered name, they may change the gender of the byname following the normal rules of the language even if the name is no longer registerable.
For example, say someone registered the name Tofi Durinsson when such things were permissible, and now they wish to change their registered name to Tofa Durinsdottir. ERA allows them to keep the element Durin in a Norse name despite its redocumentation as a French literary name and simply modify the remainder of the name to match the now feminine given name.
b. If a submitter wishes to register a gendered byname through the ERA and the language sometimes marks the gender of a byname and sometimes doesn't, they may register either version.
For example, a hypothetical Marie la broderresse ("the embroiderer") wishes to use the byname via ERA with the Arabic Da'ud. The masculine form of the byname is le brodeeur, allowing the registration of Da'ud le brodeeur. If a hypothetical Jean le brodeeur wished to register the given name Áine they may register either Áine le brodeeur or Áine la broderresse, using ERA to combine a Gaelic given name with a French byname (a combination not normally allowed).
On November 13, 2021, at Stellar University of Northshield, Katerinka Polaris did elevate Bridget ni Cathasaigh to the rank of Herald Extraordinary for her long-standing and exemplary work with the tournament heralds of the kingdom.
Shortly after, Katerinka Lvovicha took her well-earned rest from Principal Herald of Northshield. Ysolt Pais de cuer is her successor as Polaris. Thank you both for your service!
On December 11, 2021, at Solstice Court in the Barony of Loch Salaan, Conchobhar mac Michil, outgoing Golden Wing Principal Herald of Artemisia, did elevate Fiametta de Travestere to the rank of Herald Extraordinary. Aside from being Golden Crown Herald many times, she has been instrumental in setting up and streamlining kingdom and baronial virtual events. At the same court, Conchobhar stepped down as Golden Wing and Karl Braden von Sobernheim stepped up as successor. Thank you both!
Also on December 11, at Magna Faire Court in the Barony of Iron Mountain in the kingdom of Meridies, Adelaide Colette de Monferrer was inducted into the Order of the Velvet Owl, the grant-level Meridies order for arts and sciences, for her onomastic and ceremonies research.
And finally on December 11, at the Yule Toy Tournament in the kingdom of Atlantia, Their Majesties Eckehard and Jane inducted Catherine Ambrose, former Ibis Herald, into the Order of the Golden Dolphin, the grant-level Atlantia order for service.
Please send information about happenings to major heralds and major happenings to all heralds to Laurel, so that it can be published here.
Letters of Intent, Comment, Response, Correction, et cetera are to be posted to the OSCAR online system. No paper copies need be sent. All submission forms plus documentation, including petitions, must be posted to the OSCAR online system. While black-and-white emblazons must be included in the Letter of Intent, only colored armory forms need to be posted in the forms area.
Cheques or money orders for submissions, payable to "SCA Inc.-College of Arms" are to be sent to Trent Le Clair, 928 Frazier Dr, Walla Walla WA 99362
Send roster changes and corrections to Laurel. College of Arms members may also request a copy of the current roster from Laurel.
For a paper copy of a LoAR, please contact Laurel, at the address above. The cost for one LoAR is $3. Please make all checks or money orders payable to "SCA Inc.-College of Arms". The electronic copy of the LoAR is available free of charge. To subscribe to the mailings of the electronic copy, please see the bottom of http://heraldry.sca.org/heraldry/lists.html#lists for more instructions.
For all administrative matters, please contact Laurel.
Items listed below in square brackets have not been scheduled yet. For information about future scheduling, please review the status table located on the Web at http://oscar.sca.org/index.php?action=137.
The November Laurel decisions were made at the Pelican meeting held on Sunday, November 14, 2021 and the Wreath meeting held on Saturday, November 6, 2021. These meetings considered the following letters of intent: Trimaris (01 Aug, 2021), Middle (02 Aug, 2021), Calontir (05 Aug, 2021), Laurel LoPaD (10 Aug, 2021), An Tir (11 Aug, 2021), Palimpsest Rules Letter (11 Aug, 2021), Artemisia (12 Aug, 2021), Palimpsest Rules Letter (12 Aug, 2021), Avacal (19 Aug, 2021), Ealdormere (24 Aug, 2021), Lochac (25 Aug, 2021), Atlantia (26 Aug, 2021), Outlands (28 Aug, 2021), Ansteorra (31 Aug, 2021), Caid (31 Aug, 2021), Drachenwald (31 Aug, 2021), Laurel LoPaD (20 Sep, 2021) (redraws). All commentary, responses, and rebuttals should have been entered into OSCAR by Sunday, October 31, 2021.
The December Laurel decisions were made at the Pelican meeting held on Sunday, December 12, 2021 and the Wreath meeting held on Saturday, December 4, 2021. These meetings considered the following letters of intent: Ćthelmearc (02 Sep, 2021), Calontir (02 Sep, 2021), Meridies (08 Sep, 2021), An Tir (11 Sep, 2021), Middle (11 Sep, 2021), Laurel LoPaD (12 Sep, 2021), Ćthelmearc (19 Sep, 2021), Ealdormere (24 Sep, 2021), Caid (27 Sep, 2021), Atlantia (28 Sep, 2021), Avacal (28 Sep, 2021), Lochac (29 Sep, 2021), Atenveldt (30 Sep, 2021), Drachenwald (30 Sep, 2021), West (30 Sep, 2021), Laurel LoPaD (25 Oct, 2021) (redraws). All commentary, responses, and rebuttals should have been entered into OSCAR by Tuesday, November 30, 2021.
The January Laurel decisions will be made at the Pelican meeting held on Saturday, January 23, 2021 and the Wreath meeting held on Friday, January 22, 2021. These meetings will consider the following letters of intent: Atlantia (04 Oct, 2021), Calontir (04 Oct, 2021), Meridies (07 Oct, 2021), An Tir (10 Oct, 2021), Artemisia (15 Oct, 2021), Middle (17 Oct, 2021), Avacal (22 Oct, 2021), Laurel LoPaD (23 Oct, 2021), Ansteorra (24 Oct, 2021), Ealdormere (24 Oct, 2021), East (24 Oct, 2021), Lochac (25 Oct, 2021), Atenveldt (26 Oct, 2021), Outlands (27 Oct, 2021), Caid (30 Oct, 2021), Caid (31 Oct, 2021), Drachenwald (31 Oct, 2021), Northshield (31 Oct, 2021), Laurel LoPaD (14 Nov, 2021) (redraws). All commentary, responses, and rebuttals should have been entered into OSCAR by Friday, December 31, 2021.
Not all letters of intent may be considered when they are originally scheduled on this cover letter. The date of posting of the LoI, date of receipt of the Laurel packet, or other factors may delay consideration of certain letters of intent. Additionally, some letters of intent received may not have been scheduled because the administrative requirements (receipt of the forms packet, receipt of the necessary fees, et cetera) have not yet been met.
REMINDER: Until all administrative requirements are met, the letter may not be scheduled.
Pray know that I remain,
In service,
Emma de Fetherstan
Laurel Queen of Arms
Created at 2022-01-08T15:49:54