The
Rules For Submissions for Names and How to Avoid the Common Problems
We define names to include given names, surnames, by names and place names. We need to ensure that we maintain our standards for period content and style. So, we will define some of the concepts so we reduce the issues.
Documented Names
Often, we find this to be the easily way to get a submission passed. But there are some tricks to this.
Given names, surnames and by names should be used like they were in the period sources. Sometimes our client wants to use a surname name as given name. This is not acceptable for period style. However, we can get around this by suggesting they find an acceptable given name and just go by their last name. In some cultures today or in the military, we only refer to people by the last name. This gets them what they want to be called but gets it through the system.
Also, the variants and diminutives used must also be similar in period style. Depending on the culture, some spelling may be different and could be substituted for the current name. For example, Arwyn is an acceptable variant of Arwen because the change of the "e" to a "y" was common and Master Talon cited several examples for my submission. If a spelling variant is used but you can't document to a period name, then provide examples of the spelling changed used in that culture. The easiest is to find copies of the naming practice and provide them as supporting documentation.
Finally, names should be associated with people or places. Because people name other things, their horse, dog, sword, etc, a client's name submission should be a name associated with people. However, you can be from place as a locative by-name. Hence, the period naming convention of "Arwyn of Leicester", Nichola Bracton of Leicester, would be accepted.
Overall, the rule is to match the types properly. Given names as given names; surnames as surnames; bynames as bynames. Otherwise, the submission may be returned.
Constructed Names
Constructed names come from someone's desire to use standard naming practices from a particular region. Norse, Irish, Saxon names come to mind where the construction is dependent family concepts like Bjorn who would have a son with a last name Bjornsson. . We still need examples of the name construction and the components that used were also documented. Then the name will be easily shown to be an acceptable name construction. Provide a couple of examples of the name construction to ensure that the construction is not considered to be "weird". "Weirdness" increases the chance of the submission being returned and should be minimized to one or two at the most.
Invented Names
If the name elements have been created with naming construction practices, you can sometimes document an invented name. But now we are trending into the more obscure submissions and we should get some help on this. Ask again to the submitter why they need the name that way and if the spelling is important. If the pronunciation or meaning is what is important, you may be able to find a better documented or constructed name. If the client still wants the name, then get help with some the Senior name heralds for further assistance. Invented names have some of the lowest acceptance rates but still can be done if the documentation and/or support can be shown. But again, confirm with the client that they want this level of risk.
Legal Names
A submitter may use elements of their legal name but not all of it. But this allowance comes with a restriction, only the legal names can be used and not their variants. For example, my surname is Mortenson (legally). Even though my grandfather's real name was Mortensen and would be more Danish, I can't use Mortensen without documentation. I can however use Mortenson and provide my birth certificate as proof of documentation.
Like we stated before, given names shall be used as given names. Surnames as surnames. So, I can be Arwyn Mortenson of Leicester but not Mortenson Arwyn of Leicester. Because I haven't provided documentation for Mortenson was used as a given name, I can't submit it this way.
Part III - Compatible Naming Style and Grammar
Name Grammar and Syntax
We now need to ensure that the naming style and grammar stays consistent with our period of study within the SCA. We also need to ensure that the grammar makes sense for the language being used. The best way is to keep it simple by only using one language from one culture but you may have a name that combines languages. Biggest struggle is when the name has too many "weirdness" and hence becomes incompatible with the scope and period of the SCA. Also, the submitter may have a requirement for authenticity.
Simple one-language names allows for not only a high acceptance rate but also if the submitter requires authenticity. When someone starts down the two-language road, ask him or her why they want to. If we go back to the "persona story", then remind them that they make change their persona several times over the years or decades in the SCA. Also ask them which parent they see the most and who would have most likely named them (if their persona is that detailed). But if they continue, the rule of thumb is two languages can work together if there was substantial contact between those cultures. Don't try combining more than three languages (with four there is a potential of 6 weirdnesses) because it becomes very unlikely that all would be found in one name.
Also, each phrase must be grammatically correct according to the usage of a single language. This includes the concept that "trillium" would not have fires and that a trillium can't have a dream. Laurel has a long list of precedents about these available on the Laurel web page. Use the precedents to explain how Laurel has previously returned incorrect grammar. Most of the time, we can fix it with a simple correction; otherwise, the client should be educated on why his or her submission may be returned.
Naming Style
Our names should be compatible with a culture of a single time and place even if constructed with two languages. We all are from some single point in space and time and should be consistent to the naming practices of that place. We have two types of names: Personal names and Non-personal names.
Personal names are given to a single person and must contain a given name and at least one byname. These components make up a name phrase. A byname is added so a person can be more easily recognized or identified. In period, names contain more than three name phrases but a rule of thumb is no more than four name phrase. A documentable exception is Arabic whose naming practice shows the lineage from father to son over several generations. Often people have their given name or the name that they are called with the SCA and often struggle with a byname to allow the submission to continue. Here are some simple examples of byname types and how you can work with the submitter to find something that matches them:
1. A byname with a relationship, like a patronymic or metronymic. Daughter, son, brother of XXX. Depending upon the language/culture the name construction will be different. Find out more if they want some ties either to their persona or their peer if applicable. Maybe, they are second generation SCAdian and now want something from their "real" parents. Maybe not. Maybe from their SCA created family.
2. A byname could be a second given name. This is where you can use their mundane name if applicable or a second name they like.
3. A byname could be locative. Being from somewhere could be part of the submitter's persona and could be included. Placenames can either period locations and/or SCA created group names. However, SCA group names often do not allow the submitter to have an authentic name. If this is a desire, steer them away from group names. Locative bynames may also include sign names such as inn sings etc. But we don't often see these in period but they can be used.
4. A byname could describe their occupation, status or office. Occupations can work well with the submitter's interests but status and offices may not. Cooper, Baker, Smith, etc are examples of occupations whereas Reve, Parson, Freman, indicate status or offices. Watch for requests for status above their current SCA station. A person cannot be considered Baron as part of their name unless they are one.
5. A byname could be a nickname to describe one of their aptitudes. "Lionhearted", "The Quite", and "The Red" are examples of this type. Look for suggestions from their current nicknames and see if any in or out of the SCA can work towards this. Something could come up in the discussion that could work really well.
6. A byname could be a sentence, oath or phrase name. Look for period examples of this. Although by-names are popular here in Ealdormere, I don't see this option used very often.
Non-Personal names include branch names, names of orders and awards, heraldric titles and household names. In all cases, they should follow the patterns similar to those used in period. Look for documented examples and work from there. Household names tend to cause issues with people because we don't do the initial research when they are formed. Work with the submitter to find a good example that fits the flavour of what their household represents. For all other non-personal names, work with the Senior Heralds because they are not done often enough.
Part IV - Offensive Names
As we discussed in the general principles, we need to support the image of the SCA both within the Society but to the outside world. More often than not, the name may be considered offensive without the submitter knowing. Several offensive names include:
1. Vulgar Names such as bathroom or toilet humour. If it might be offensive to your grandmother or your children, it probably fits into this category. This affects a large section of both the Society and general outside world.
2. Religious Terminology could mock others beliefs which again reduces the enjoyment of a section of the SCA but also will cause a poor image to the general population.
3. Stereotypical Names degrade ethnic, racial or sexual orientation backgrounds of people. We don't use this in general population because it's consistent highly inappropriate.
4. Offensive Political Terminology may offend people of a race, religion or ethnic background.
If the client is unaware, explain the issue of the name. If they insist on it, ask why they want it. Maybe beyond the "inappropriate" humour we can find a story that could make a better byname. Hopefully, we can a better byname that both the submitter but also our Society can accept.
Part V - Name Conflict
Conflict by its own definition causes people to get defensive. Here we are talking about that one person's name closely resembles someone else. Although we have thousands maybe millions of "John Smith" around the world, we like to keep the confusion level down. Our name can be similar in both written and verbal form. But some simple tricks allow us to submit names that are different from those already protected.
We need to try to make the names "significantly different" from those already protected. We do this by having the name significantly different in both sound and appearance. If not, we assume for conflict checking that the names are equivalent. Don't get hung up on diminutives and variants. If the name sound and looks different, then it is probably "significantly different". If not, start questioning if it's the same.
Personal Names and Their Conflict Issues
Given names only have to be "significantly different". However, for bynames, we have additional requirements and potential pitfalls:
1. Punctuation does not make it significantly different. For example: John Smith's son would conflict with John Smithson. Also, John the Smith would conflict with John Smith.
2. Similar relationships make it not significantly different. A daughter or son of the same person are not significantly different. Hey, how many of us have been called our sibling's name? Same deal here. There is no significant difference because the relationship is the same. However, being from a household would make this different because of the number of people potentially involved.
3. Locative bynames don't have to be different places - that's just the easy way to handle it. However, watch out for ones that mean the same. For example: "John Ealdormann" would conflict with "John of Ealdormere" because in both cases we are talking a John from Ealdormere.
The easiest way to check for conflict is to see if you would meet one person with one name and not confuse them with another. Here are some examples:
1. If their given names are different, no conflict. For example: John Martin Smith would be a different person from David Martin Smith. Both could be called Martin but their full names are different - so we assume that would be.
2. If the full name has a different number of name phrases, no conflict. For example: John Martin Smith would not conflict with either John Martin or John Smith because of the number of names.
3. The order of the name may not make a significant different. The order change must make the meaning different. Check to see if the names describe the same person. If so, we may have a conflict.
4. Just adding a locative, may not solve your problem. The addition of a name phrase need to make the name different. For example: John Martin Smith will conflict with John Martin Smith of Ealdormere. The two people may be the Same. But "Arwyn of Leicester" would not conflict with Arwen of Aethlemarc. Because we would be from two locations.
In all cases, if you find a conflict, work with the submitter to find out what's important. Is the Given name? Is the Locative Byname? What about the relationship? Don't forget to remind people that we all don't use our whole name "official" here in the SCA or in the outside world. We often go by our nicknames, short forms, middle name and even by our last name. Don't allow them "hung" up on adding or taking away something from the name but look and ask for what's most important.
Finally, there's a real catch with "historical names". If the name could have been written in a different language locally, then all language variations are protected. Ask them why they want to be a famous person and work with the traits of that historical icon and develop the client's traits with the same vigour.
Non-Personal Names and their Conflict Issues
The most common misconception happens with distinguishing between a designator or name of a branch within the Society and a descriptive element. We define a designator or name of a branch to indicate the position and/or location. The branch name type can change as the group changes. Ie. A basic local group can be called a shire, college, canton or stronghold depending upon their status. All of these are the same. But that same group can become a barony, principality or kingdom depending on their population size and acceptance by the board. All of these would represent the same location. Hence, the names are not considered to be significantly different from one another. For example: The Canton of Westbellford would conflict with the Barony of Wesbelford. Our group type is not included and we are left with just the name that sounds and looks the same. Therefore the "descriptive" element would be the same.
But also, the group's name type conflicts with other designators such as herald or house. Awards or Orders are also included. Therefore, in our example, House Westbellford and the Wesbelford herald would conflict as well with the groups listed above. All of these describe for the most part a group of people. So, therefore, the group could be confused as being the same.
However, a simple addition of a descriptive element would make the conflict go away. For example, the White Wolf Fion would not conflict with the Red Wolf Fion because the description would be different. But watch that the grammar or order doesn't make it the same. For example, the Red and White Wolf Fion would conflict with the White and Red Wolf Fion because the order of red and white doesn't change the concept. The meaning is still the same.
Finally, watch for modifiers. Modifiers add to the noun to describe further information but don't change the overall meaning. For example, the Award of the Scarlet Banner would conflict with House Flying Scarlet Banner because flying further describes what the banner is doing. They could be the same banner.
Remember the trick here is to think if it would describe the same people with the same meaning. If so, then probably the name would conflict. When in doubt, still send it through the system but warn the submitter of a potential issue.
Part VI- Presumptuous Names
As part of the General Principles, a name can't claim a status or power that the submitter doesn't have. Again, go back the basics. Would that confuse you if someone were claiming to be a Duke when they never sat the throne. Also, the name would reduce fun or the enjoyment for those who did get the accolade of their title. Our Kingdom or the Society recognized them for it and we should ensure that no one get confused.
Presumptuous Name problems include:
1. Names that claim a rank cause issues because we also include derived title names. Also, small stronghold owned solely by a family indicates wealth or position that the person doesn't have. So, we normally can claim castles or a connection to a royal house. If there is examples of other "non-royalty" of that period, then we can use the name. If you can confuse a connection to a famous family or a rank, then you have a problem.
2. Names that claim powers. Names from mythologies, legends, sagas, etc can cause issues with powers that name comes with. Again, if you can confuse the person also with beings that are non-human, we have a problem.
3. Names that claim a specific relationship. We can't claim a relationship to someone specific outside the society without reasonable proof. For example, some of us may want to be related to Donald Trump to get the money but the claim would not be valid. Same thing with names already protected.
4. Names that give confusions as well to orders and/or peerages within and outside the SCA. For example, the House of the Pelican and Laurel would not conflict but would confuse people to believe that only a person with a Pelican and Laurel may join. But if this household was not, the members could be confused to be members of those peerages.
Presumptuous name problem normally arise from a person wanting something important or if they weren't aware of the problem. Ask them if there is something about that person or place which could be converted into a byname. Also, have them look at the heraldry for some clues, to find something that represents more them instead of the protected name.
In conclusion:
In general, name issues can be resolved by looking at if the new name creates a new person who is different from anyone else. If it does, we normally don't have a problem. But it does explain some of the problems. Also remember that new names should enhance the enjoyment of the game for everyone and should be in good taste.
Go Back to Part I