Editing Existing Registration Allowance, Grandfather Clause
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
'''WARNING: Do not cite this page as a reference. This page is on this | '''WARNING: Do not cite this page as a reference. This page is on this wikispace only to make the content "searchable" and easier to find. If you find the information you seek here, go to the original sources as linked below to verify the information and use them for your documentation.''' | ||
''<span style="background-color: #eef3f6; color: #222222; font-family: monospace;">Revised {$revisiondate}.</span>'' | |||
---- | |||
=Glossary of Terms: Grandfather Clause= | ===Glossary of Terms: Grandfather Clause=== | ||
The popular name given to the guarantee in Corpora that, once registered, a name or piece of armory remains registered unless the owner requests its release, regardless of changes in the Rules for Submissions and standards applied to submissions after that time. | The popular name given to the guarantee in Corpora that, once registered, a name or piece of armory remains registered unless the owner requests its release, regardless of changes in the Rules for Submissions and standards applied to submissions after that time. | ||
The term Grandfather Clause is also sometimes applied to the provisions that allow a submitter to use elements that they have previously registered in new name or armory submissions, even if those elements are no longer acceptable under the current Rules for Submissions. On a case by case basis, this allowance has been extended to the submitter's immediate legal family. These provisions are stated in Rules for Submissions II.5. and VII.8; a sample letter documenting the right to extend the Grandfather Clause can be found in the Cover Letter for the October 2002 LoAR. | The term Grandfather Clause is also sometimes applied to the provisions that allow a submitter to use elements that they have previously registered in new name or armory submissions, even if those elements are no longer acceptable under the current Rules for Submissions. On a case by case basis, this allowance has been extended to the submitter's immediate legal family. These provisions are stated in Rules for Submissions II.5. and VII.8; a sample letter documenting the right to extend the Grandfather Clause can be found in the Cover Letter for the October 2002 LoAR. | ||
http://heraldry.sca.org/coagloss.html | [[http://heraldry.sca.org/coagloss.html]] | ||
---- | |||
=SENA, Personal Names Part 1, Content := | ===[[scaheraldry/SENA, Personal Names Part 1, Content|SENA, Personal Names Part 1, Content]] :=== | ||
g. The Grandfather Clause: In a new personal name submission, an individual may use name phrases already registered to them, even if that name phrase would no longer be allowed under the current rules. Only the exact, actual name phrase from the registered form may be used, not variants, patterns, etc. The use of the grandfather clause does not allow the submitter to evade new style problems (as discussed in [[http://heraldry.sca.org/laurel/sena.html#PN2B|PN.2]] below). It only allows the submitter to keep style problems that already exist with the registered name. | g. The Grandfather Clause: In a new personal name submission, an individual may use name phrases already registered to them, even if that name phrase would no longer be allowed under the current rules. Only the exact, actual name phrase from the registered form may be used, not variants, patterns, etc. The use of the grandfather clause does not allow the submitter to evade new style problems (as discussed in [[http://heraldry.sca.org/laurel/sena.html#PN2B|PN.2]] below). It only allows the submitter to keep style problems that already exist with the registered name. | ||
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. Documentation under the grandfather clause does not exempt a name or name phrase from conflict, presumption, or offense rules, unless that rules violation is itself grandfathered. | 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. Documentation under the grandfather clause does not exempt a name or name phrase from conflict, presumption, or offense rules, unless that rules violation is itself grandfathered. | ||
---- | |||
=SENA, Non-Personal Names Part 1, Content]] := | ===[[scaheraldry/SENA, Non-Personal Names Part 1, Content|SENA, Non-Personal Names Part 1, Content]] :=== | ||
g. 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. | g. 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. | 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. | ||
Line 20: | Line 24: | ||
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. | 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. | ||
---- | ---- | ||
=SENA, Armory Part 2, Content= | ===[[scaheraldry/SENA, Armory Part 2, Content|SENA, Armory Part 2, Content]] :=== | ||
3. Grandfather Clause: Armorial elements which are registered to an individual may be used in a new submission by that individual, even if they are no longer allowed under the rules. Only the exact, actual elements which are registered may be used, not variants or patterns. The use of the grandfather clause does not allow the submitter to evade new style problems (as discussed in [[http:''heraldry.sca.org/laurel/sena.html#A1|A.1]] through [[http:''heraldry.sca.org/laurel/sena.html#A3|A.3]]). It only allows the submitter to evade style problems that already exist with their registered armory. | |||
3. Grandfather Clause: Armorial elements which are registered to an individual may be used in a new submission by that individual, even if they are no longer allowed under the rules. Only the exact, actual elements which are registered may be used, not variants or patterns. The use of the grandfather clause does not allow the submitter to evade new style problems (as discussed in [http: | |||
An armorial element from a registered piece of armory 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 armory is already registered. | An armorial element from a registered piece of armory 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 armory is already registered. | ||
Documentation under the grandfather clause does not exempt a design from conflict, presumption, or offense rules, unless that rules violation is itself grandfathered. | Documentation under the grandfather clause does not exempt a design from conflict, presumption, or offense rules, unless that rules violation is itself grandfathered. | ||
= | ---- | ||
===Letter Documenting Legal Relationship for Grandfather Clause=== | |||
I, [Legal name], known in the SCA as [Society name], do attest that [Legal name of submitter], known in the SCA as [Society name of submitter], is my legal [father/mother/wife/husband/son/daughter/brother/sister]. I understand that this letter cannot be withdrawn once [Legal name of submitter]'s name or device is registered. | I, [Legal name], known in the SCA as [Society name], do attest that [Legal name of submitter], known in the SCA as [Society name of submitter], is my legal [father/mother/wife/husband/son/daughter/brother/sister]. I understand that this letter cannot be withdrawn once [Legal name of submitter]'s name or device is registered. | ||
[Date] [Signature of [Legal name]] | [Date] [Signature of [Legal name]] | ||
(from the Administrative Handbook, Appendix D - Suggested Standard [[Form Letters]] | (from the Administrative Handbook, Appendix D - Suggested Standard [[scaheraldry/Form Letters|Form Letters]] ) | ||
---- | |||
===Precedents:=== | |||
Precedents of the SCA College of Arms - [[http://heraldry.sca.org/laurel/precedents.html]] | |||
Morsulus Heralds Website - [[http://www.morsulus.org/]] (to search the LoARs and Precedents) | |||
Restatement Wiki - [[http://yehudaheraldry.com/restatement/index.php?title=Main_Page]] (restatements of Precedents) | |||
'''''Use the above links to be sure any precedents listed below haven't been superseded by newer precedents.''''' | '''''Use the above links to be sure any precedents listed below haven't been superseded by newer precedents.''''' | ||
'''Collected Name Precedents on the Grandfather Clause:''' | '''Collected Name Precedents on the Grandfather Clause:''' | ||
http://heraldry.sca.org/precedents/CompiledNamePrecedents/GrandfatherClause.html | [[http://heraldry.sca.org/precedents/CompiledNamePrecedents/GrandfatherClause.html]] | ||
==Collected Armory Precedents:== | ====<span style="background-color: #ffffff;">'''<u>Collected Armory Precedents:</u>'''</span>==== | ||
'''<span style="background-color: #ffffff;">Tenure of Elisabeth de Rossignol (May 2005 - July 2008)</span>'''<span style="background-color: #ffffff; font-family: 'Times New Roman'; font-size: medium;"> - </span><span style="font-family: 'Times New Roman'; font-size: medium;">[[http://heraldry.sca.org/precedents/elisabeth/armory.html#GRANDFATHER|GRANDFATHER CLAUSE]]</span> | '''<span style="background-color: #ffffff;">Tenure of Elisabeth de Rossignol (May 2005 - July 2008)</span>'''<span style="background-color: #ffffff; font-family: 'Times New Roman'; font-size: medium;"> - </span><span style="font-family: 'Times New Roman'; font-size: medium;">[[http://heraldry.sca.org/precedents/elisabeth/armory.html#GRANDFATHER|GRANDFATHER CLAUSE]]</span> | ||
'''<span style="background-color: #ffffff;">The 2nd Tenure of François la Flamme (October 2004 - May 2005) - </span>'''<span style="font-family: 'Times New Roman'; font-size: medium;">[[http://www.ellipsis.cx/~liana/sca/armoryprec.html#GRANDFATHER|GRANDFATHER CLAUSE]]</span> | '''<span style="background-color: #ffffff;">The 2nd Tenure of François la Flamme (October 2004 - May 2005) - </span>'''<span style="font-family: 'Times New Roman'; font-size: medium;">[[http://www.ellipsis.cx/~liana/sca/armoryprec.html#GRANDFATHER|GRANDFATHER CLAUSE]]</span> |