SENA, Non-Personal Names Part 1, Content
WARNING: Do not cite this page as a reference. This page is on this wikispace only to make the content of SENA "searchable" and easier to find. If you think you find the information you seek here, go to the official home of SENA on the SCA Laurel Website to confirm the reference. [[1]]
NPN.1. Non-Personal Names Content http:heraldry.sca.org/sena.html#NPN1 #NPN1AA. Definitions: Non-personal names consist of two parts: the designator and the substantive phrase. A designator is the word or group of words that describe what kind of non-personal name it is, such as House//, //Barony// or //Order. The substantive element is the part of the name that is specific to the item being submitted. That is, it specifies which household, branch, etc. is being referred to. The preposition and article which often link the designator and substantive element are for the most part treated as part of neither, but in general should match the designator in language. For example, in the name Barony of Carolingia//, //Barony// is the designator and //Carolingia// the substantive element. In the name //Black Lion Principal Herald//, //Principal Herald// is the designator and //Black Lion// the substantive element. In the name //the honurable Ordre of the Gartier//, //the honurable Ordre// is the designator and //Gartier// the substantive element. In the name //Hous of Julyane Huxster//, //Hous// is the designator and //Julyane Huxster is the substantive element. In each case, the preposition and article that may link them are part of neither one. #NPN1BB. Designators: The designators which may be used are determined by the type of non-personal name submission. In general, if the lingua Anglica// form of a designator is used, the prepositions and articles which join the designator to the substantive element will also take the //lingua Anglica// form. //Lingua Anglica// allows English translations of certain elements; it is discussed in greater detail in C.2.c below. > #NPN1B11. Branch Designators: The designators for branches (local SCA groups) are fixed by the Governing Documents. The list may be found in Appendix E of this document. These designators are considered to be compatible with any place name construction. This is true whether or not period forms can be found with such a designator. Shires are not limited to the forms of English shires, nor baronies to the kinds of names found for baronies in period. In addition, each type of branch may be registered with other designators suitable for that branch type. A college may be named following the pattern of medieval colleges. These designators may take the lingua Anglica// form, using the form //Designator of X regardless of the language of the substantive phrase. Alternately, a translation for the appropriate type of branch may be proposed. A list of translations that have been registered can be found in Appendix E. > In general, changes of status for a branch, such as changing from shire to barony, do not need to be submitted. The Laurel office does not track those changes in status (that being a duty of the Seneschal and Board of Directors). However, it will acknowledge them when a new submission is made. The exception is when a branch wants the approval of a new alternate form of the branch designator, such as a non-English form. Such approval requires Laurel approval, but is an administrative action (which does not require fees) and does not delay the change in status. > As discussed in [[2]], we only allow non-personal names from locations beyond Europe when the entity in question could have traveled to Europe. As branches could not have so traveled, designators for branch names may only be in languages used in medieval and Renaissance Europe. > #NPN1B22. Order and Award Designators: The designators for order names must follow a documented pattern for medieval order names. The standard designators are Order// and //Award//. Any pattern suitable for one such designator is suitable for the other. These designators may take the //lingua Anglica// form, using the forms above regardless of the language of the substantive phrase. Alternately, they may take the language of the substantive element. A list of some translations of these designators is listed in Appendix E; any other designators should be documented. In general, designators which are used for household and association names cannot be used for orders and awards; however, those which were used in period to refer to multiple kinds of groups of people, including both those that we would call households and those that we would call orders, such as //company, may be used for either. > For example, either Order of the Levrier// or //Ordre du Levrier// is registerable for the meaning 'order of the hound', but //Order du Levrier// and //Ordre of the Levrier are not; in each one, the preposition and article do not match the language of the designator. > For example, Company of the Levrier// is registerable as a household name or as an award or order name as //Company// was used in period for military groups, guilds, and knightly orders. However, //House of the Levrier// would only be registerable as a household name, as //House was not a term used for orders or awards. > [section updated per November 2013 Cover Letter] > #NPN1B33. Household and Association Names: The designators for household names must be documented as a form describing a group of people in a particular culture. It must be compatible with the substantive element in terms of content and style. There is no standard designator which is considered compatible with all types of names for groups of people. > Several kinds of groups of people have served as models for household names. They include a noble household, a military unit, a guild, a group of people associated with an inn or tenement house, a university or school (noting that the word college is reserved for branches), clans, and an organized group of musicians or actors. Designators may be registered in the original language or may take the lingua Anglica// form. Suitable substantive elements (like simple descriptions) may take the //lingua Anglica// form as well. In general, designators which are used within the SCA for orders and awards cannot be used for household and association names; however, other than "Order", those which were used to refer to multiple kinds of groups of people, including both those that we would call households and those that we would call orders, such as //company, may be used for either. > For example, either Compagnia di Santa Lucia// or //Company of Santa Lucia// is registerable for the meaning 'company of Saint Lucia, but //Company di Santa Lucia// and//Compagnia of Santa Lucia are not; in each one, the preposition and article do not match the language of the designator. > For example, Compagnia di Santa Lucia// is registerable as a household name or as an order name as //Compagnia// was used in period for military groups, guilds, and knightly orders. However, //Order of Santa Lucia is registerable as an award or order name, but not a household name. >> [section updated per November 2013 Cover Letter] > #NPN1B44. Heraldic Titles: The designators for heraldic titles must follow a documented pattern for heraldic titles. The standard terms for heraldic titles for kingdoms and local branches are Herald// and //Pursuivant//. Any pattern suitable for one such designator is suitable for the other. These designators may take the //lingua Anglica// form, using the forms above regardless of the language of the substantive phrase, or they may take the language of the substantive element. The designator //Principal Herald// is restricted to the chief herald of a kingdom. The designator //King/Queen/Sovereign of Arms is restricted to the Laurel office. In general, changes of designator, for example from pursuivant to herald, do not need to be submitted to the Laurel office; if submitted, they are administrative actions, which do not require fees. > For example, a heraldic title based on the German placename Funffprun// could be //Funffprun Herold// or //Funffprun Herald//, as //Herold// is found as a German term for heralds, but it could not be //Funffprun Herault//, as //Herault is a French term for heralds. > As discussed in [[3]], we do not register heraldic titles in languages from cultures that did not use heraldic titles. This applies to both the designator and the substantive elements of such heraldic titles. #NPN1CC. Standards for Designators and Substantive Elements: To be registerable, those designators whose form is not fixed in NPN.1.B above (including those with modifiers, such as //Noble Order) must meet the standards laid out below. All substantive elements must also meet the standards laid out below. #NPN1C11. Single Time and Place: A substantive element must follow the rules of grammar and structure for a single time and place. It may not mix languages unless that mixing of languages within a name phrase is attested. For example, the attested English heraldic title Rougecrosse Pursuivant is partially French and partially English, but this does not necessarily mean that all French and English words may be so combined. #NPN1C22. Sources of Designators and Substantive Elements: We allow registerable name phrases to be created in a variety of ways. A designator is a name phrase. A substantive element is a name phrase. Those designators that are discussed in [[4]] above do not need to be justified under the terms of this section. #NPN1C2aa. Attested Name Phrases: Name phrases may be attested to period as a complete name phrase. A single example of an attested name phrase clearly dated to period is sufficient to demonstrate its use. Minor spelling variants are allowed when those spelling variants can be demonstrated to be compatible with the spelling conventions of the time and place of the attested name. For example, in Renaissance Scots, the letters i// and //y// are regularly interchangeable. So, a name attested as //Armyltoun// could also be registered as //Armiltoun//. The letters //k// and //q//, on the other hand, are not interchangeable in Renaissance Scots. So, a name attested as //Kintyre// does not justify the spelling //Qintyre. #NPN1C2bb. Constructed Name Phrases: Name phrases may be constructed from attested period name elements. This requires demonstrating that the combination follows a period pattern. We generally require at least three examples to consider something a pattern. This is because a single name phrase can appear to follow a pattern that it does not actually follow. For example, the German placename element –katz does not derive from the name of the animal but from the name of a river. Thus, this element cannot be combined with an element that is incompatible with a river name. All of the elements and patterns for a constructed name phrase must come from a single time and place. We do not allow constructed name phrases that are created by using patterns from one time and place with elements from another time and place. Some examples of constructed names are: >>> #NPN1C2b11. New Placenames Constructed from Attested Elements: New placenames can be constructed from attested placename elements following an attested pattern. >>> For example, the attested English place names Oxford//, //Swinford// and //Hartford// indicate a pattern of kinds of large hooved animals with -//ford//. Therefore, this pattern would support a similar name like //Sheepford//. This pattern would not, however, support constructing //Bookford// or //Duckford//, since neither //books// nor //ducks are large hooved animals. >>> For example, there is a pattern of adding family names to existing placenames in English. Following this pattern, the attested family name Peverel// can be added to the attested placename //Bercroft// to construct the compound placename //Bercroft Peverel. >>> #NPN1C2b22. New Heraldic Titles Constructed from Attested Elements: New heraldic titles can be constructed by using attested elements in attested patterns for a given time and place. >>> For example, attested English titles include Blaunche Sanglier Pursuivant// and //Rouge Dragon Pursuivant//. These can justify //Rouge Sanglier Pursuivant// and //Blaunche Dragon Pursuivant//. They can also justify the use of other animals or heraldic monsters, like //Rouge Griffin// //Pursuivant// or //Blanche Leopard Pursuivant. #NPN1C2cc. Lingua Anglica// Allowance: We also allow the registration of translations of attested and constructed household names, heraldic titles, and order names into standard modern English, which we call the //lingua Anglica rule. We allow this because the meanings of these names would have been clear to the speakers of these languages, but may be unclear to modern speakers. The translation must be a literal, plausible and complete translation. Under no circumstances will translations of the meanings of given names or placenames be registerable under this rule. For example, Blanche Sanglier Pursuivant// can be translated as //White Boar Pursuivant//, but not //White Sanglier Pursuivant//, //Snowy Boar Pursuivant//, or //White Piggy Pursuivant. For example, the Spanish byname de Castilla// may be translated as //of Castile//. The Arabic byname //al-Dimashqi// may be translated as //of Damascus// or //the Damascene//. However, while //Cairo// is derived from a word which means "the victorious", its //lingua Anglica// form is //of Cairo//, not //of The Victorious, as "The Victorious" is a translation of the meaning. #NPN1C2dd. Borrowed Names: Name phrases may be borrowed from secular literature, from the Bible or other religious literature, or from the names of saints. Name phrases may also be constructed from name elements borrowed from those types of source. To borrow a name phrase or element, the following conditions must be met: >>> #NPN1C2d11. Linguistically Appropriate Form: The name phrase must be shown to be a form by which the entity was known in that time and place. Generally this means finding it in the literature of that time (so a Renaissance Italian Bible, or an English publication of an Arthurian romance). In the case of a saint's name, evidence for their veneration through the naming of churches is generally sufficient. Only the form of the name used in that culture is permitted under this allowance. >>> For example, the Greek mythological object known in English as the Golden Fleece// was known to the medieval French as the //Toison d'Or//. It is //Toison d'Or// that was borrowed for the name of the period Burgundian order. Similarly, the saint known in her lifetime as //Æthelthryth// was venerated by late period English people as //Audrey//. //Audrey// is the form allowed in late period English context to create a name like the //College of Saint Audrey. >>> #NPN1C2d22. Pattern of Borrowing Names: The culture must be shown to have a pattern of using name phrases from that type of source. Demonstrating such a pattern requires at least three independent examples of normal entities using such name phrases in the target time and place. >>> The demonstrated pattern must address the type of name phrase. Evidence of the use of the given names of saints does not demonstrate the use of the bynames of saints. The demonstrated pattern must also address the type of character or entity. The use of a non-personal name derived from the given name of a major character in a source does not demonstrate the use of a non-personal name derived from the given name of a minor character. >>> For example, there is a pattern of using the given names of major Arthurian characters in medieval England. This would justify a non-personal name derived from the name Bedivere// even if it were not attested. However, it would not justify a non-personal name derived from the name of a minor Arthurian character like //Gwinas, who is only mentioned once. It would also not justify a non-personal name derived from a Biblical name. As there is no similar pattern of borrowing in Gaelic, a non-personal name derived from the Gaelic form of an Arthurian character cannot be registered under this allowance. #NPN1C2ee. Legal Name Allowance: Name phrases from an individual submitter's legal names may be used. To do this, the submitter must demonstrate the name phrase on a legal document, such as a birth certificate, driver's license, or the like. Only the full name and the nature of the document must be visible. Identification numbers and the like may be obscured. Religious names (Hebrew names, confirmation names) are also considered legal names. With appropriate evidence, they can be used under this allowance. A personal name can be used in the construction of a household name. Surnames are used to construct household names, on the pattern of Surname Hall//. Personal names can be used in the construction of heraldic titles. Surnames are used to construct heraldic titles on the pattern of //Surname Herald. For example, someone whose legal surname is Smylie// could register //Smylie Hall under the legal name allowance. The name phrase must be used in precisely the way that it is spelled on the legal document. As some legal documents obscure capitalization (by using all capitals) or omit punctuation (and markings like accents), such changes may be allowed on a case by case basis. Name phrases must be used in their entirety, including any prepositions and articles. Non-personal names based on nicknames which do not appear on legal documents cannot be registered. For example, the legal surname Westwick// justifies //Westwick Herald//, but not //Westwyck Herald// or //Westwik Herald//. The legal surname //von Volvorth// justifies //von Volvorth Hall//, not //Volvorth Hall// or //de Volvorth Hall//, even though the expected form in a period construction would drop the preposition //von. #NPN1C2ff. Branch Name Allowance: Name phrases may be created from the registered forms of SCA branches. Only the exact registered form of the branch name may be used, in the lingua Anglica// form "//of Branchname". Translated forms will not be registered under this allowance. For example, we would allow the forms of the East// or //of Fontaine dans Sable//, as these are the expected //lingua Anglica// forms. However, this would not allow //von Osten// as a German translation of "of the East", even if the rest of the submission was in German. Similarly, it would not allow //de la Fontaine dans Sable// as a fully French version of "of Fontaine dans Sable", even though the branch name is French. That is, we would allow //Ordre du Levrier of Fontaine dans Sable// or //Order of the Levrier of Fontaine dans Sable//, but we would not allow //Ordre du Levrier de la Fontaine dans Sable// under this rule, as this is not the //lingua Anglica// form of the branch name, even though it matches the intended origin of the submission. If //Fontaine dans Sable// can also documented as an attested or constructed French name, //de Fontaine dans Sable// could be used in forming a fully French order name; however that would not be through the use of the branch name allowance. For example, we would not allow //of the Midrealm//, as this is not the registered form of the //Kingdom of the Middle. #NPN1C2gg. The Grandfather Clause: Name phrases from a name registered to an individual or branch may be used in a new non-personal name submission by that individual or branch, even if the name phrase is no longer registerable under the rules. The use of the grandfather clause does not allow the submitter to evade new style problems (as discussed in NPN.2 below). It only allows the submitter a pass on style problems that already exist with the registered name. Documentation under the grandfather clause does not exempt a name from conflict, presumption, or offense rules, unless that rules violation is itself grandfathered. The element used may be the entire substantive element, the designator, or part of the substantive element. Only the exact, actual name phrase from the registered form may be used, not variants, patterns, etc. with the exception of submissions of branch heraldic titles and order names. A name phrase from a registered name of an individual may also be registered by a close legal relative (such as parent, spouse, child, sibling, etc.). 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. Branches may register new heraldic titles and order names based on patterns used in their existing heraldic titles or order names. To use the grandfather clause, the new submission must be similar in content to the existing pattern. For example, if a branch had registered an order name Crimson Sleeve//, they could use that to modify a new, similar object such as //Crimson Glove//. However, they could not register //Crimson Bowl//, as a bowl is not the same type of object as a sleeve. Likewise, the owner of //Diamond Herald// and //Ruby Herald// could use the grandfather clause to register //Order of the Saphire//. The owner could not register //Order of the Diamond Ring// or //Order of the Gold, because the pattern of registered items is limited to precious stones, not jewelry or precious items in general. Branches may also utilize the grandfather clause to register non-personal names incorporating name phrases from the registered names of individuals closely associated with the branch. This generally means a resident of the branch or an active supporter. The permission of the individual or their heraldic heir is required for this use. Only the whole, exact, actual name phrase from the registered form may be used, not variants or patterns. Under no circumstances will this privilege be extended to use names or to other unregistered names.