-crest: Difference between revisions

From SCA Heraldry Wiki
Jump to navigation Jump to search
No edit summary
(No difference)

Revision as of 15:25, 14 July 2018

From Pelican: No More SCA-Compatibility

On the May 2008 Cover Letter, we ruled: > Therefore, as of the May 2009 decisions meetings, we declare that no new name elements or name patterns will be ruled SCA-compatible, that all names previously ruled SCA-compatible are no longer SCA-compatible and that in order for them to be registered, documentation meeting the same standards as for non-SCA-compatible names will be required. This ruling went into effect with this, the May 2009 Pelican meeting. [[1]]


Compiled Name Precedents:

[[2]]

François la Flamme 2001.11 [crest and keep//] The element //crest// falls into the same category as //keep//. In both cases, we do not have evidence of that element used in a formal place name in period, though we have evidence of each as a geographical element. Bardsley (p. 216 s.n. Crest) dates both //Rogerus del Crest// and //Johannes del Crest// to 1379. Bardsley (p. 441 s.n. Keep) dates //William atte Kep// to 18 Edw. I, //Roger Kep// to I Edw. III, and //Richard atte Kippe to I Edw. III. Reaney & Wilson (p. 261 s.n. Keep) dates Thomas ate Kepe to 1327 and Roger de Kepe to 1332.


Keep// has long been used as part of SCA branch names. The most recent registration is //Crossrode Keep, Shire of// (registered November 1999 via Ansteorra). This element is effectively regarded as SCA compatible as an element in an English place name. Given the forms in which it has been registered, spellings of the element //Keep// are registerable both as a separate element (such as //Crossrode Keep//), and as the final element in a compound place name (such as //Northkeep//). Registerable spellings include //Keep and any alternate spellings which may be documented to period (including those listed above).

Similarly, there has been enough interest in the element crest//, including as recently as 1999, to rule it SCA compatible in an English place name. Unlike //keep//, //crest// is not registerable as a separate element. So, //Ravencrest// is a registerable placename, though //Ravenwood Crest//, for example, is not. [Tristan Ravencrest, 11/01, A-Æthelmearc] ||