Middle Kingdom - Internal Letter of Acceptances & Returns – July 2002
This is the July 2002 Middle Kingdom Letter of Acceptances and Returns for Escutcheon’s and Keythong’s May Letters. Unless otherwise noted, all clients will accept changes. {Comments in braces {} were removed from the Letter of Intent sent to Laurel and the College of Arms. Names, devices, or badges in braces have been returned or pended; general comments or replies to commentary are also placed in braces. Thanks to AElfreda aet AEthelwealda, Mikhail of Lubelska, Aryanhwy merch Catmael, Pendar the Bard, Shauna of Carrick Point, Athenais Bryennissa, Knut, Ettiene le Couteau des Roches, Kevin Ambrozijwski, Phebe Bonadeci, Dunstan Bramblette, and Jaelle of Armida for their commentary this month.}
{While I appreciate all the commentary that I receive, I am a little surprised at a number of statements about what we “do” or “don’t do” in SCA heraldry. Many of these statements in this month’s letter are in fact false and it would be good to refrain from such hearsay in the future. If you have preferences that differ from those in use, feel free to note your differences, but avoid claims about what is and is not “correct” practice unless you are absolutely certain. Thanks!!}
Please note that my email address is goldschp@mailbag.com. While I can still check goldschp@yahoo.com, I don’t do so very often.
1) Ashby Turley. Device Resubmission. Purpure semy-de-lys, two sea dogs rampant Or.
{Name reg’d 6/00}
The original device, Per bend sinister wavy purpure and vert, two wolves statant Or, was pended for further comment on the February 2001 LoAR, to be decided upon in the August 2001 LoAR. On that LoAR, it was returned for conflict with Katherine Goodpasture (Per fess and per pale embattled erminois and gules, in bend sinister two talbots passant Or) [reg’d 1/90]. This redesign clears that conflict, and seems to be clear of any other. The Society doesn’t use French blazonry terms, and the “in fess” seems to be needless. Suggested reblazon: Purpure semy-de-lys, two sea dogs Or.
Device Commentary
Pendar: Blazon-fu: Purpure semy-de-lys, two seadogs Or. Sea dogs do get a CD for type from other dogs, but it is not a substantial difference in type. [a wolf vs a seadog] There is a CD between the two critters, but not substantial difference. (Llyr ap morgwn, 3/98 p. 22). No conflicts found.
Ettiene, et al.: OK
Knut: Clear, including beast-dog
Athenais: The original device, Per bend sinister wavy purpure and vert, two wolves statant Or, was pended for further comment on the February 2001 LoAR, to be decided upon in the August 2001 LoAR. On that LoAR, it was returned for conflict with Katherine Goodpasture, Per fess and per pale embattled erminois and gules, in bend sinister two talbots passant Or. The submitter’s name was registered 06/00 via the Middle. This redesign clears that conflict, and seems to be clear of any other. The Society doesn’t use French blazonry terms, and the “in fess” seems to be needless. Suggested reblazon: Purpure semy-de-lys, two sea dogs Or.
Aryanhwy: Her previous device submission was pended on the 02/01 LoAR until the 08/01 LoAR, where it was returned. Note that the sea-dogs are rampant.
2) Ashby Turley. New Badge. Purpure, two sea dogs rampant and in base a fleur-de-lys Or.
{Name reg’d 2/00}
Badge Commentary
Pendar: The fleur is not equivalent size with the seadogs, so Blazon-Fu: Purpure, two seadogs and in base a fleur-de-lys Or. If they were equivalent size would could have blazoned this Purpure, two seadogs and a fleur-de-lys Or. No conflicts found, but it is virtually identical to her device. I don't see the point. Toyota
Ettiene, et al.: OK
Knut: Single CD from device submission above for number of secondary group. Presumed permission to conflict. Otherwise clear.
Athenais: This also appears to be clear of conflict. The “in fess” in the blazon seems to be needless, and generally the position of the charge comes first. Suggested reblazon: Purpure, two sea dogs and in base a fleur-de-lys Or.
Aryanhwy: Note that the sea-dogs are rampant.
3) Berach mac Arailt Oicc. Name and Device Resubmission. Barry azure and agent, three gouttes d’Or.
{We pended this last month and the client agreed to take the changes so we are sending it up}
The client’s previous submission (Bearaich O’Harald-o) was returned by Laurel on 11/00 for various problems, and included the note: “we would have registered it if the submitter had allowed us to make major changes. Since he did not, we are unwilling to change the name so radically from the submitted form.” Laurel at the time suggested that Berach mac Arailt Oicc might be an acceptable name. The client has reluctantly agreed to the change.
The form of the byname given in Woulfe is O'Harold. This is an Anglicized spelling; Woulfe gives Ó hArailt as the Gaelic form. However, it is undated, and the Anglicized form is dated to the very end of our period. Based on examples in the Annals of Tigernach, mac Arailt Oicc would seem a reasonable early form of the byname.
Bearac (can also be spelled Bearach) is found in Woulfe (172, s.n. Bearac), which notes that it was “the name of a celebrate Connacht saint of the 6th century.” Therefore, it should work as an Irish Gaelic given name. Indeed, Ó Corráin & Maguire (31, s.n. Berach) they mention a number of saints by this name, and note that “The O Hanlys continued to use Berach as a family personal name but in the nineteenth century they anglicized it Barry.” Berach would be the appropriate early period form, with Bearach being later-period. Given the documentation found in the Laurel return, Berach mac Arailt Oicc (“Berach, son of Harald the young”) should work.
{*) Berok Silfrson. New Name and Device. Sable, a bear’s paw print argent.
{The name has multiple problems. The given name is largely undocumented (persona stories are not generally considered relevent to documenting a name and should be avoided). Contrary to what was asserted, there is no such word as “berok” in the Russian language (period or modern). The Russian word for bear is “medved” (literally, “honey gatherer”) and has been so since antiquity. Even with my fairly formidable library on Russian dialects, we are not aware of any regional variant like this. The client is advised to study my article on Russian zoological names if he wishes to learn more about this subject (http://goldschp.freeservers.com/zoonames.html). If he has documentation to support this variant, it should be provided in the resubmission.
The byname also has problems. Patronymics are formed from the father’s given name, not a nickname. Geirr Bassi has “silfri,” meaning “silver” as a nickname (p. 27, col. 1). The closest-sounding given name is “Silvester,” (p. 14, col. 2). If the submitter is most interested in the sound of the name, “Bárekr silfri” (both elements found in Geirr Bassi) would be the likeliest.
The device is being returned with the name but would have been returned regardless. It conflicts with at least three registered devices: Griffin Pollard le Bere (Per saltire azure and sable, a paw print argent) [reg’d 6/97] There is no difference counted between different types of pawprints, so there is only one here for the field.
Nicholas Wolfmar (Gyronny of six issuant from base gules and Or, a wolf's paw print argent) [reg’d 2/88] has a similar problem.
Matsudaira Kentarou Toshiyori (Sable, semy of bear's paw prints argent) [reg’d 12/00] has only one difference – the number of paw prints.
To clear these conflicts, the client will probably need to consider some fairly major changes, ranging from adding an ordinary or additional charges to a complete redesign.}
Name Commentary
Pendar: Name: The "sound" may be most important to the client, but if he is pronouncing the "r" then he is mispronouncing it. According to Geirr Bassi the "r" at the end is a glottal stop which does not get pronounced. Page 33: "Although the devoicing after h may be ignored, the devoicing of the final r is important. The difficulty is aggravated by the fact that a final r should not be pronounced as a syllable of its own. In other words, the Old Norse names Auðr, B{o,}rkr, Gestr, Hallr, Leifr, Þorðr, etc., are all monosyllabic." I could not find "Berok" used as a given name by a person in period in any of my resources. The closest forms were Barak (Commander) in Paul Wickendon's book of Russian names, and Bárekr on page 8 of Geirr Bassi. The latter would work best with the rest of the name. "silfri", meaning "silver" is found as a nickname on page 27 of Geirr Bassi. According to the Formation of Patronymics section of Geirr Bassi on page 18, a man's name ending in "-i" such as "Snorri" would become "-a" in the patronymic form, so "Snorri" becomes "Snorrason", "silfri" would become "silfrason". "Berok Silfrson" is not registerable as it was submitted due to lack of documentation, but could easily be registered using references to Geirr Bassi as "Bárekr silfrason".
Ettiene, et al.: No name docs for Berok. Silfri found in Gerri-Bassi p. 27
Athenais: There is no documentation for this name, as a persona story is not documentation. The name of a type of bear can’t be used as a given name unless the submitter can show that it was used that way in period. Geirr Bassi shows “Bárekr” (p. 8, col. 1), which is the closest-sounding name I was able to find. If he would rather the name mean “bear,” then “Bj{o,}rn” would be appropriate. Patronymics are formed from the father’s given name, not a nickname. Geirr Bassi has “silfri,” meaning “silver” as a nickname (p. 27, col. 1). The closest-sounding given name is “Silvester,” (p. 14, col. 2) which doesn’t match any of the examples shown in the patronymic formation section; it could become “Silvesterson,” “Silvestesson,” or “Silvestsson.” If the submitter is most interested in the sound of the name, “Bárekr Silvesterson” (or some form of the patronymic) or “Bárekr silfri” would be the likeliest. If he’s most interested in the meaning, it would be either “Bj{o,}rn silfri” or “Bj{o,}rn Silvesterson” (or some form of the patronymic).
Aryanhwy: This name is undocumented as stands (and ungrammatical as well). So does he want a Russian name or a Norse name? In Paul's dictionary there is a [Barokh] 1470, [Baroch] 1237, [Baroch'] 1202, as well as [Beroi] 1470, but these are the closest Russian names I can find. On the Norse side of things, Geirr Bassi lists [Ba/rekr] as a given name, and [silfri] as a byname meaning “silver.” Device Commentary
Pendar: Conflicts with Nicholas Wolfmar (2/88 Outlands): Gyronny of six issuant from base gules and Or, a wolf's paw print argent. and Griffin Pollard le Bere (6/97 Trimaris): Per saltire azure and sable, a paw print argent. There is no significant difference between a wolf's paw print and a bear's paw print, especially as this one is drawn. [a pawprint vs a cat's pawprint] ...we do not grant difference between types of pawprint. (Radbot Gunter, 10/94 p. 13) That leaves only 1 CD for changes to the field. And with Matsudaira Kentarou Toshiyori (12/00 Atlantia): Sable, semy of bear's paw prints argent. 1 CD for number of charges.
Aelfreda, et al: Conflicts with the following two devices, with only 1 CD for field. Per prior precedent, there is no difference for the type of paw print.
From: Precedents of THE PRECEDENTS OF MASTER DA'UD IBN AUDA Decisions from the second year of his second tenure; covering the period July, 1994 to June, 1996 Pawprint [a pawprint vs a cat's pawprint] ...we do not grant difference between types of pawprint. (Radbot Gunter, 10/94 p. 13)
Griffin Pollard le Bere (reg 6/97) "Per saltire azure and sable, a paw print argent." And Nicholas Wolfmar (reg 2/88) "Gyronny of six issuant from base gules and Or, a wolf's paw print argent." There is also a conflict with the following device, with 1 CD for number of pawprints. Matsudaira Kentarou Toshiyori (reg 12/00) "Sable, semy of bear's paw prints argent."
Knut: [a pawprint vs a cat's pawprint] ...we do not grant difference between types of pawprint. (Radbot Gunter, 10/94 p. 13) Precedents - Da'ud 2.2 under Pawprint
Nicholas Wolfmar - The following device associated with this name was registered in February of 1988 (via the Outlands): Gyronny of six issuant from base gules and Or, a wolf's paw print argent. CD for field, No CD for type of paw print. Conflict
Matsudaira Kentarou Toshiyori The following badge associated with this name was registered in
December of 2000 (via Atlantia): Sable, semy of bear's paw prints argent. CD for number of primary group. Conflict
Athenais: The device is in conflict with Griffin Pollard le Bere, Per saltire azure and sable, a paw print argent, registered 06/97 via Trimaris. There is only one CD for the change to the field.
Aryanhwy: This conflicts with Griffin Pollard le Bere (reg. 06/97 via Trimaris): "Per saltire azure and sable, a paw print argent." There is not a CD between different types of pawprints, so there is only one here for the field. It also conflicts with Matsudaira Kentarou Toshiyori (reg. 12/00 via Atlantia), "Sable, semy of bear's paw prints argent," with one CD for number.
4) Brice Colquhoun for Fellowship of the Oaken Blade. New Household Name {and Badge.
(Fieldless) In cross conjoined in center four rapiers proper, and in saltire stems conjoined in center four oak leaves gules .}
{Name reg’d 4/98}
The elements of this name can all be documented in the OED. Fellowship is defined as “a guild, corporation, company” and dated 1515 (2nd ed, 5: 819). It has been used in this context in period. A quote regarding the fellowship of porters is dated to 1560. Oaken is “made of the wood oak” and dated to 1390 (ibid, 10: 627). For blade, “the blade being the essential part of such weapons etc. is often put for the whole, esp. in poetry and literary language” and dated to c1325 (ibid, 2: 254).
The use of bladed weapons in house names is supported by O’Brien “English Sign Names” (http://www.s-gabriel.org/names/mari/inn) which has “sword” dated to 1480. While it is unlikely that an oaken blade would be very useful beyond a practice weapon, the naming practice is found in period (albeit not necessarily in English). Wickenden (193) has Lubianaia Sablia, which is a nickname that translates to “bast sabre.” At worst, it is a single weirdness.
The client will NOT accept MAJOR or MINOR changes.
{The badge is being returned. RfS VIII.5 Fieldless Style says "Fieldless armory must form a self-contained design. A fieldless design must have all its elements conjoined, like the three feathers issuing from a crown used by the Heir Apparent to the throne of England. Since there is no field in such a design, it may not use charges that rely on the edges of the field to define their shape, such as bordures and orles, nor to cut off their ends, such as ordinaries or charges throughout." The charges here are not conjoined, and therefore this must be returned.}
Name Commentary
Pendar: The designator "Fellowship" has been registered for SCA household names before: Fellowship of the Footprint (3/86 Caid), Fellowship of the Grimflaed (10/84 East), Fellowship of the White Bear (11/79 West). A quick check in the OED confirms that it has been used in this context in period. 7. A guild, corporation, company. Now rare, "Fellowship of Porters" see 11.b. The quote regarding the fellowship of
porters was dated to 1560. Also in the OED under "Oaken" we find 1. Made of the wood of the oak. The face of heom is playn, and hard, Al so hit weore an oken bord. 1390. While I don't believe that the Fellowship of the Oaken Blade is period, it should be registerable.
Knut: Fellowship - a guild, corporation, company. dated 1515 OED 2nd ed. vol 5 pg 819 Fellowship (7) This seems to be a valid household designator. Oaken - made of the wood oak. dated 1390 OED 2nd ed. vol 10 pg 627 Oaken (1) Blade - The blade being the essential part of such weapons etc. is often put for the whole, esp. in poetry and literary language. Dated c1325 OED 2nd ed. vol 2 pg 254 Blade (7) This seems to me to be an acceptable order name based on a tangible object.
Athenais: With no documentation given for the household name, it should be returned. I don’t see how “Fellowship of the Oaken Blade” follows known period naming practices, unless the submitter can justify it as an inn sign name.
Aryanhwy: His name was registered 04/98 via the Middle. I cannot help with documenting the household name. It does not follow any of the acceptable period models, discussed in RfS III.2.b.iv Household Names: "Household names must follow the patterns of period names of organized groups of people. Possible models include Scottish clans (Clan Stewart), ruling dynasties (House of Anjou), professional guilds (Bakers Guild of Augsburg , Worshipful Company of Coopers), military units (The White Company), and inns (House of the White Hart)." Additionally, I cannot think of any reasonable way to describe a sword as "oaken," as one that was literally oaken would be useless.
Badge Commentary
Pendar: Badge: The blades are not conjoined. All elements of fieldless badges must be conjoined as per RfS VIII.5. The badge is returnable for this reason. Even if the field were reblazoned as argent, making it: "Argent, four swords in cross points to center proper between four oak leaves in saltire base to center gules." you would end up with argent blades on an argent field, violating RfS VIII.2, Armorial Contrast.
Ettiene, et al.: Doesn’t look like a rapier.
Aelfreda, et al: The charges are not conjoinned, which is required for a fieldless badge. Return for redrawing.
Knut: These charges are not conjoined. The swords should be drawn more boldly. (Fieldless) In cross four rapiers tips to center proper, and in saltire four oak leaves stems to center gules all conjoined is clear. Return for violation of RfS VIII.5
Athenais: The badge does not show any conjoined charges, but rather a group of separate charges, which hasn’t been allowed for fieldless badges for quite some time. The badge needs to be returned for a redraw if the submitter actually wants the charges to be conjoined, or returned for the submitter to pick a field if he wants the non-conjoined charges. The submitter’s name and device, Per bend sinister vert and azure, a wolf sejant ululant and a tree couped Or, were registered 04/98 via the Middle.
Aryanhwy: Household badge: This also needs to be returned for redesign. RfS VIII.5 Fieldless Style says "Fieldless armory must form a self-contained design. A fieldless design must have all its elements conjoined, like the three feathers issuing from a crown used by the Heir Apparent to the throne of England. Since there is no field in such a design, it may not use charges that rely on the edges of the field to define their shape, such as bordures and orles, nor to cut off their ends, such as ordinaries or charges throughout." The charges here are not conjoined, and therefore this must be returned.
{*) Cicilia inghean Ui Campbell. New Name.
The name has problems of inconsistent orthography. One internal commentator, citing Black, suggested the byname “Cíle inghean an Caimbeuil,” but the client does not allow major changes. In order to register the name, all of the elements will need to be Scots or Irish (not the current mixture of the two). However, since changing the language of any of the elements has been prohibited by the client, we cannot fix this and are returning it. In the grand scheme of things, the client might be just as well off with Cicilia Campbell (citing the Modern Name Allowance for the byname if necessary).}
Name Commentary
Ettiene, et al.: inghean is an Irish Gaelic name element. Is it also a Scots Gaelic name element?
Athenais: The given name is documented from the article “A List of Feminine Personal Names Found in Scottish Records,” by Brian M. Scott (Talan Gwynek). “Inghean Vi” isn’t documented at all. According to “Quick and Easy Gaelic Names,” by Sharon L. Krossa (http://www.medievalscotland.org/scotnames/quickgaelicbynames/), the way to indicate an Irish clan affiliation byname for women is to use “inghean uí.” It also states, “This style of Gaelic name & clan affiliation byname is appropriate in Ireland (but not Scotland) from the 10th century, but only becomes common from about the 11th century.” The name would be much better off by dropping “inghean vi” altogether.
“Campbell” is the header spelling from Black, p. 129. It dates that spelling to 1282 and 1390.
Aryanhwy: This name combines Gaelic and Scots orthography in the same phrase; while mixed Gaelic-anglicized names are currently allowable, each phrase must be wholly in one language. Let's see what we can't do to help this.
'Cicilia' is a fine Scots name. The byname is slightly problematic in that 'Campbell' was not originally a given name, but a nickname, from the Gaelic'caimbeul' “wry, crooked mouth” (Black s.n. Campbell). Black says that “the earliest individual of the name Campbell in record is Gillespic Cambel…in 1263.” There is also a 'Nicholas Cambell' 1294, 'Duncan Campbell' 1390, and 'Cambal' 1545, 'Cambale' 1375, 'Cambele' 1432, 'Cambelle' 1424, 'Camble' 1513, 'Camille' 1451, 'Cammell' 1473, 'Campbele' 1481, 'Campbill' 1617. 'Cicilia Campbell' would be a fine Scots name.
It’s not sure in what (if any) form the Scottish Gaels adopted 'Cicilia'. According to OCM s.n. Si/le, 5) Dragano da Monte. New Name.
Both the given name and the byname are in Mittleman and Scott, “Fourteenth Century Venetian Personal Names” (http://www.s-gabriel.org/names/arval/venice14/venice14given.html ). The client will NOT accept MAJOR changes and cares most about meaning (“dragon of the mountain”) in 14th century Italian culture.
Name Commentary
Ettiene, et al.: OK
Athenais: The name looks perfectly good for 14th century Italian, although by that time, any “meaning” to the names would probably have been lost.
Aryanhwy: The name is fine (more than that, it is excellent), but it does not mean "Dragon of the mountain." It means "Dragano of the hill/mountain."
6) Edyth Miller. New Name.
Edyth is dated to 1332 in Scott, “Feminine Given Names in a A Dictionary of English Surnames” (93). Miller is in Bardsley, Dictionary of English and Welsh Surnames (532, 533) and dated to 1572. Reaney and Wilson (310) dates Miller to 1327. The client will NOT accept MAJOR changes.
Name Commentary
Ettiene, et al.: OK
Athenais: Good English name!
Aryanhwy: Name: Lovely name!
7) Eiríkr häggvandi Ivarrson. Device Resubmission.
Per fess dovetailed gules and sable, an axe fesswise and a bull’s head cabossed Or.
{Name submitted on the 1/02 MK LoI}
Device Commentary
Pendar: No conflicts found.
Ettiene, et al.: Esct. is correct. Blazon should be: Per fess dovetailed gules and sable, an axe fesswise head to dexter and a bull’s head cabossed Or.
Knut: The per fess is slightly enhanced but, due to space filling considerations, reasonable.
Gaston de Clermont -- The following device associated with this name was registered in June
of 1995 (via the East): Per fess dovetailed gules and sable, a griffin passant and a crescent
argent. Since this exact field has been registered under the current rules and several other gules and sable fields with a complex line have been registered since, the contrast between the gules and sable is probably
enough to allow the complex line. Clear.
Athenais: I agree that the blazon should be Per fess dovetailed gules and sable, an axe fesswise head to dexter and a bull’s head cabossed Or. This looks clear of conflict. It would be useful to know when the name was submitted.
Aryanhwy: Blazon fu: "Per fess dovetailed gules and sable, an axe fesswise and a bull's head cabossed Or." (Head to dexter is default for axes fesswise). The client's previous submission, "Per fess dovetailed gules and sable, a lambsplitter and a bull's head cabossed counterchanged," was returned by Rouge Scarpe 01/02, for problems of contrast and lack of documentation for lambsplitters in period armory.
This submission has cleared both those problems. The client's name was forwarded to Laurel in the form *) Flame, Barony of the. New Badge.
(Fieldless) On a flame Or a gout de sang.
{Name reg’d 2/83}
{This is being returned for the inherent non-identifiability of an enflamed gout and a conflict. There is a standing precendent from Master Da’ud (written in 1994) that states: "The gout is unrecognizable as such on the flames, appearing to be a part of the flames rather than a separate charge." Because the gout is not identifiable, a conflict arises with William of Sark (Sable, a flame proper) which has only one difference (the change of the field).}
{To Pendar and Athenais: It can be spelled “gout” or “goutte” and is spelled both ways by the SCA – in fact it is spelled both ways in Pendar’s commentary.}
Badge Commentary
Pendar: That's spelled "goutte", not "gout". Can be returned via the precedent: [... on three flames Or three gouts azure.] Gouttes on flames are inherently unidentifiable. "The gout is unrecognizable as such on the flames, appearing to be a part of the flames rather than a separate charge." (Da'ud ibn Auda, LoAR August 1994, p. 16) [Cassandra Zoë Paganel, 08/99, R-Caid]
Ettiene, et al.: lovely
Knut: I believe that there is an identifiability problem with this submission. If the charges were anything other than flames and/or gouts or the tinctures anything other than gules and Or there would be no problem. Unfortunately, this combination appears to be an artistic variation of the banned "a flame gules fimbriated Or" depiction of a flame proper. As such, it would also conflict with the following: William of Sark -- Either the name or the following device associated it (or both) were registered in January of 1973:Sable, a flame proper.
Athenais: This looks almost like “on a flame Or, another gules.” It may conflict visually with William of Sark, Sable, a flame proper, registered 01/73, depending on how exactly his flame is drawn. The charge is actually a goutte de sang. Suggested reblazon: (Fieldless) On a flame Or a goutte de sang. The barony’s name and device were registered 02/83 via the Middle.
Aryanhwy: Badge: This should have been listed under "Flame, Barony of the" in the LoI. Their name was registered 02/83 via the Middle.
8) Flame, Barony of the. New Badge.
Sable estencely Or, a flamberge gules hilted and enflamed Or.
{Name reg’d 2/83}
The depiction of the flamberge enflamed appears in several pieces of armory registered to this group and should be considered grandfathered to them.
Badge Commentary
Pendar: A semy of sparks is, by definition, blazoned "estencely", so Blazon-Fu: Sable estencely Or, a flamberge gules hilted and enflamed Or. It looks like this flaming blade is a common motif among this group's armory. If it is always drawn this way, then the depiction is grandfathered to them. I found no conflicts.
Ettiene, et al.: lovely
Knut: [returning two boar spears in saltire surmounted by another palewise argent enflamed sable] The "enflaming" here is not, but is rather "a sheaf of three spears-shaped flame" charged with a sheaf of three
spears. This is much too complex for a flame to be. It's identifiability suffers sufficiently that it becomes next to impossible to identify it as a flame. (Picture it without the spears on it; they tend to give it better definition.) The flames here act only as a very complex fimbriation, which has been previously disallowed. (Red Spears, Barony of, 5/95 p. 14) Precedents - Da'ud 2.2 under Flames and Enflamed
Flame, Barony of the -- The following device associated with this name was registered in February of 1983 (via the Middle): Sable, a wavy-bladed sword gules, hilted and the blade enflamed, in base a laurel wreath Or. The following badge associated with this name was registered in October of 1994 (via the Middle): Athenais: It’s worth noting that this badge draws from the barony’s registered device, Sable, a wavybladed sword gules, hilted and the blade enflamed, in base a laurel wreath Or. Only the blade is actually enflamed. While “semé of sparks” is fine, this is normally called “estencely.” Suggested reblazon: Sable, estencely Or, a flamberge gules hilted and the blade enflamed Or.
Aryanhwy: Badge: This should have been listed under "Flame, Barony of the" in the LoI. Their name was registered 02/83 via the Middle.
9) Grietje Crynes. New Device.
Argent, between two bendlets sinister azure a waterlily pad gules.
(Name reg’d 1/01)
{This was returned last month for lack of a registered name, but Ary found the name docs (thanks!) so we are sending it to Laurel}
*) Hamish mór Dubh nan Cath. New Name and Device.
Per chevron azure and Or, 3 crescents 1 and 2, Or and in base a lion rampant gules.
{The name is being returned because the given name cannot be registered. Hamish appears on Laurel’s list of names that cannot currently be registered in the SCA (http://www.sca.org//heraldry/laurel/names/returned-names.html). The precedent in which this decision was made states: "Hamish is not a name. It is a phonetic rendering of the Gaelic name Seumas in the vocative case, and only became misconsidered a given name by mistake by non-Gaelic speakers in post-period times. It is no more a given than would be the possessive James'. If the submitter would consider the given Seumas, this would work." (November, 1991). No documentation was provided for the given name that would indicate sufficient reason to attempt to overturn this precedent.
The device is being returned with the name but otherwise does not appear to have any significant problems.}
Name Commentary
Ettiene, et al.: Name OK.
Athenais: Unfortunately, “Hamish” “seems to be a bastard Scottish form developed from the vocative” of “Séamus,” and is thus not registerable (Ó Corráin & Maguire, p. 163, header “Séamus”). I don’t think that using two nicknames is normal for Scots Gaelic; according to “Quick and Easy Gaelic Names,” by Sharon L Krossa (http://www.medievalscotland.org/scotnames/quickgaelicbynames/), “The standard way to form a name using a descriptive adjective byname for men is: Aryanhwy: Name: Okay…[Hamish] is not even listed in Black.
Device Commentary
Pendar: These crescents are awfully shallow. Possibly returnably so. There is no need to specify that the lion is in base as he is part of the primary charge group. Blazon-fu: Per chevron azure and Or, three crescents two and one Or and a lion gules. Lions are rampant by default. Similar concept to but clear of Conall Ó Ríoghbhardáin (1/00 Ansteorra): Per chevron azure and argent, three crescents argent and a natural leopard rampant sable spotted argent. 1 CD for changes to the field, 1 CD for tincture of the crescents, 1 CD for tincture of the cat. and Alasdair MacKenzie (7/00 Atlantia): Per chevron azure and Or, two swords in saltire Or and a lion rampant gules. 1 CD for number, 1 CD for type. No conflicts found.
Ettiene, et al.: This is color on color. Pt VIII 1a.
Knut: There is an identifiability problem with these "crescents". A properly drawn crescent would have the top of the three shown arcs removed and possibly one added halfway between the other two. These look like a perspective drawing of convex discs with a bite taken out. Clear for the properly drawn blazon. Return for violating RfS VII.7.a
Athenais: The Society usually spells out numbers, rather than using numerals. Since “rampant” is the default posture for a lion, that may be dropped from the blazon, as can “in base,” since the lion cannot be on the azure section of the field. Suggested reblazon: Per chevron azure and Or, three crescents one and two Or and a lion gules. This looks clear of conflict.
10) Julianna de Pardieu. New Device.
Purpure semy-de-lys, a unicorn rampant argent.
{Name reg. 9/99}
The client will be instructed to draw the fleurs-de-lys larger.
{Athenais: The Society uses all sorts of terms and you will find both semé and semy throughout the O&A.}
Device Commentary
Pendar: There are a lot more fleurs on the field than there needs to be and they are poorly drawn, in some cases they resemble mullets. Neither of those is likely to get the device returned. No conflicts found.
Ettiene, et al.: One hopes the larger version is better drawn.
Knut: The fleurs-de-lys are somewhat difficult to see. They should be fewer and bolder. Clear.
Athenais: Normally, the Society doesn’t use French blazonry terms, and as “rampant” is the default posture for a unicorn, it may be dropped from the blazon. Suggested reblazon: Purpure semy-de-lys, a unicorn argent. This looks clear of conflict.
Aryanhwy: Her previous device, identical to this, was returned in 03/02 by Rouge Scarpe for problems of identifiability. This resubmission addresses some of the problems, but the fleurs-de-lys are still hard to recognize, and the hooves of the unicorn are not clearly cloven. I'm hesitant to recommend returning for redrawing again, but it reality, it really needs it.
11) Marie Boleyn. New Device.
Purpure, a maiden, arms upraised, vested Or and on a chief argent a daschund statant sable.
{Name registered 11/98}
Device Commentary
Angharad: “Dancer maiden is not a recognized charge and needs to be more explicitly described (a Moorish dancer? A Saracen dancer?), (In fact how would a European herald have any way of knowing what an Islamic woman in harem attire might look like?!?! not to mention offending the daylights out of sharia law) plus the blazon still does not describe her position (affronty arms upraised?) or attire. Several commenters noted a “dancer” in Von Volborth’s “Heraldry, Customs, Rules, and Styles” p 193 except that this example is not a charge but a crest and furthermore is noted as the muse Terpischore and the arms date from 1937! All in all this does not feel at all like period heraldry more like “filk” heraldry]
Pendar: While I agree that this isn't likely to be registered as a "dancer maiden", it can be registered as a "maiden arms upraised Or" as in Elfwyn of the Silvermoon (4/92 Atlantia): Argent, a maiden statant affronty, arms upraised proper, vested and crined on a chief triangular sable, a decrescent argent. with the way she is dressed left to artistic license. The dog is a "dachshund", not a "daschund", as in Maximillian Wilhelm aus Weinheim (4/90 Trimaris): Purpure, in fess two goblets and on a point pointed Or, a bunch
of grapes purpure, on a chief Or, a dachshund couchant sable. No conflicts found.
Ettiene, et al.: Device should be returned. Blazon should read: Purpure, a human figure Saracen Or…
Knut: When a human figure's vesting is not part of its definition (e.g. the savage, the Saracen), the vesting or lack of same is normally blazoned. (Austrechild von Mondsee, December, 1992, pg. 11) Precedents - Bruce under Human or humanoid figure
RfS VII.3 - Period Artifacts. - Artifacts that were known in the period and domain of the Society may be registered in armory, provided theyare depicted in their period forms.
We want to remind the College that we register what is submitted, and not the blazon. Precedents - Jaelle under Administrative
This blazon is poor and should have been completely ignored. The first thing to do is look at the picture. This is not a specifically defined human female, therefore it is a maiden vested (as...) According to the current rules for submission, the next question isn't if European heralds knew what the object was, (would an English herald have known that a seeblatt wasn't a funny shaped heart?), the applicable question is whether any Europeans could reasonably have known what the object was (RfS VII.3). There is a
precedent (Elsbeth - under weirdness) involving flora and fauna which specifies Sub-Saharan African as a weirdness. The deliberate omission of northern Africa in the precedent probably indicates that northern
African (and Middle Eastern) items aren't weirdnesses. This vesting does need to be documented since it hasn't been registered before. (Sorry, I missed this the last time it came up, I was focusing on other
problems with the submission.) The default posture of a human or humanoid monster is statant affronty (Glossary of Terms - Table 4). Arm positions are usually left to artistic license and not specifically
blazoned. The dachshund is mentioned as being a period breed in the precedents of Karina under dachshund. While this is a very old precedent, it should still be valid.
The drawing still has some problems. The B&W drawing shouldn't have the maiden touching the chief, and the dachshund isn't that identifiable.
A better and larger drawing of the dachshund with interior detailing (argent because of the sable charge) emphasizing the hound ears and forelegs would greatly help.
To the best of our knowledge, period blazons did not specify an exact breed of dog; at best, they would describe a dog by its general characteristics (levrier) or for a cant (talbot). The SCA does permit
known period breeds to be specified in blazon, but I consider the practice an anomaly or "weirdness"; another anomaly in the design...might itself be sufficient grounds for return. (Jean Philippe des
Bouviers Noirs, August, 1993, pg. 18)Precedents - Bruce under BEAST -- Dog, Fox, and Wolf
A weirdness for the specific breed of dog. Clear - I don't care if she is claiming to be the improprietress of the weinerhund and wench inn, this concept doesn't directly violate any rules or precedents that I can find.
Return for redraw and documentation of vesting.
Aelfreda, et al: Our best guess for blazon is "Purpure, a Saracen maiden statant affronty, arms raised Or, on a chief argent, a dachshund statant sable."
Athenais: I would probably take the safest course and blazon this simply as “a maiden, arms upraised, vested Or,” and let Wreath decide on the appropriateness of the dancer’s clothing. The daschund is not in chief, but on a chief. Suggested reblazon: Purpure, a maiden, arms upraised, vested Or and on a chief argent a daschund sable. This looks clear of conflict.
Aryanhwy: It's not so much a problem of the blazon of the dancer maiden, it's a problem of authenticity. Before this can be registered, we need to know that such humanoid figures (in this posture)
were used in period armory. Also, the dog still needs to be redrawn. It is not identifiable as such.
12) Margyt Withycombe. New Name and Device.
Purpure, a horse’s head couped and in dexter chief a mullet argent.
Margyt is dated to 1450 in Scott, “Feminine Given Names in A Dictionary of English Surnames” (http://www.sca.org/heraldry/laurel/reaneyintro.html). Withycombe is found in Elliott, “A Survey of the History of English Place-Names” (http://www.sca.org/heraldry/laurel/names/engplnam.html) where it states that the name is found in Somerset, and means "valley where the willowtrees grow.” The client will NOT accept MAJOR changes.
Name Commentary
Athenais: The documentation given in the ILoI needs to be specific, giving dates and other information as possible. “Margyt” is dated to 1450, under the header “Margaret” in “Feminine Given Names in A Dictionary of English Surnames,” (http://www.sca.org/heraldry/laurel/reaneyintro.html) by Brian M. Scott (Talan Gwynek). “Withycombe” is found “A Survey of the History of English Place-Names,” by Kristine Elliot (Dame Cateline de la Mor la souriete) (http://www.sca.org/heraldry/laurel/names/engplnam.html), where it states that the name is found in Somerset, and means "valley where the willowtrees grow.” This information comes from A Dictionary of English Placenames by A.D. Mills, published in 1991. It’s also found in Reaney & Wilson, A Dictionary of English Surnames, under “Widdecombe,” p.490, where the only in-period spelling it lists is Geoffrey de Widecumbe 1196.
Since the submitter will apparently take major and minor changes to the name, I would suggest “Margyt Widecumbe” as a more plausible spelling.
Aryanhwy: Name: This spelling of the given name is dated to 1570 in the cited article.
Device Commentary
Angharad: Horse’s head is drawn completely devoid of internal detail, which makes it hard to distinguish; client should probably draw in some details.
Pendar: If the field were divided Per bend sinister, this blazon would work, but in this case the horse's head is larger and more central than the mullet, making this Purpure, a horse's head couped and in dexter chief a mullet argent. You note "Horse's head is drawn completely devoid of internal detail, which makes it hard to distinguish; client should probably draw in some details." But this is not necessary. See Laurel's notes concerning internal detailing at http://home.earthlink.net/~mranc/sca/wreath.html#Emblazon In this particular case, I agree that at least an eye and nostril would help the identifiability a lot! But it is not returnable as it still looks like a horse's head. No conflicts found.
Ettiene, et al.: Pend for re-draw. There should be more detail on horse head.
Knut: Rafael Diego de Burgos -- The following badge associated with this name was registered in
December of 1986 (via Ansteorra): Purpure, a mullet dismembered argent. CD for number of primary group, No CD for type of half of group, removing the horse head is a single CD counted under number. No CD for arraingement, remove the head and the mullet moves to the middle. No
CD for plain vs dismembered mullet. Conflict.
Athenais: The horse’s head could use some internal details on the emblazon, but is recognizable without them. Since the mullet is of the default five points, it needn’t be specified. Slight typo: It’s a “horse’s head.” Suggested reblazon: Purpure, in bend a mullet and a horse’s head couped argent.
Aryanhwy: While it would be nice if the horse's head did have internal detailing, I think it's recognizable enough as it is, and can be sent on to Laurel, with a note to the client to draw the detailing in the future. The couping of the horse's head is a little irregular, but, again, it shouldn't be too big a problem.
13) Morgan of Angelsey. Change of Registered Device.
Per chevron purpure and vert, three bees within a bordure Or.
{Name reg’d 4/96}
If this is registered, client would like her old device (Quarterly purpure and vert, a sea-horse and a bordure wavy argent) [reg’d 4/96] released.
{Pendar and Athenais: To the best of my knowledge, we do not “not do Linnean heraldry” – we simply reserve it for charges that are hard to identify without it. If I am wrong, please direct me to the Laurel precedent to the contrary. Athenais: your cite only addresses the tincture and posture (separate issues, for which I thank you). Still, I agree in principle, in this case these are bees.]
Device Commentary
Pendar: "Apis melliferi"? What is an "apis melliferi"? We don't do linnean heraldry where the object and/or its tincture has to be defined by its latin name. These look like bees to me. Per chevron purpure and vert, three bees and a bordure Or. Close but clear of Giovanna Beatrice di Grazia (7/00 Atenveldt): Vert, three bees within an orle Or. 1 CD for changes to the field. 1 CD for type of peripheral charge. No conflicts found.
Ettiene, et al.: OK
Aelfreda, et al: Apis mellifera is the honey bee. We suggest using either "bee" or "honey bee" in the blazon. http://animaldiversity.ummz.umich.edu/accounts/apis/a._mellifera.html Have the bees feed the bordure. (grin)
Knut: Per chevron purpure and vert, three bees displayed within a bordure Or. Clear.
Athenais: The Society has not used Linnaean proper (scientific names) for creatures for quite some time; these are simply bees, which are in their default posture and thus need not be specified. Aryanhwy: The per chevron line should be drawn a lot more acute. Additionally, we no longer blazon flora or fauna by their Latin name, so these should be reblazoned as flies or bees, whichever they are.
14) Mwynwen Ysginidd. New Badge.
(Fieldless) A strawberry argent.
{Name reg’d 12/97}
Badge Commentary
Pendar: The color version is not argent, but some weird shade of grey. No conflicts found. Y'know, white strawberries aren't ripe...what does that say about the client? :)
Ettiene, et al.: OK
Knut: Is this identifiably a strawberry? The B&W drawing is a bit modern with it's single continuous line drawing style and slight top down perspective, but the color depiction is just an unidentifiable blob. Also, although the wedge shaped fruit is quite common in nature, I think that that the conically shaped fruit is the more common and identifiable popular depiction.
Clear but return for redraw.
Athenais: This looks clear of conflict. Nice badge!
Aryanhwy: Badge: No conflicts found.
{*) Mwynwen Ysginidd. New Badge
Or, a shepherd’s crook pale, sable between a left hand print dexter chief azure, a left hand print dexter base purpure, a right hand printer sinister chief gules, and a right hand print sinister base vert.
{Name reg. Dec. 1997}
{The commentators of the College were nearly unanimous that this design is not in the style of period heraldry. The shepherd’s crook is largely unidentifiable and the handprints appear to be obtrusively modern in design. That much said, the device might be considered registerable if sufficient indication could be provided that the handprints were depicted in a period style and if the crook could be more clearly drawn. It might be easier to simply explore more period designs and go for a complete redesign.}
Badge Commentary
Angharad: on b) ye gods! There are six tinctures and five separately blazoned charges (not a charge group even) yielding a modestly estimated complexity of at least 8 (if you count all hand prints left and right as the “same” charge”) probably more. Furthermore, I have never seen a human handprint used as a charge-- hands, gauntlets, sleeves, fists, yes, but no handprints. Lastly, this badge is wholly and glaringly modern (say Olympic flag) in my opinion.
Pendar: Hurmmm....I have nothing nice or useful to say. You could send it to Laurel simply to
set new precedents when it gets returned.
Ettiene, et al.: Ary isn’t RS anymore. Can we mock bad heraldry again, please? We found six reasons to return this. 1) Complexity, Pt. VIII 1a-charge limit. 2) Slot Machine, Pt. VIII 1a 3) Too modern-Pt.VIII 4-Obtrusive Modernity 4) Pictorial design- Pt. VIII 4a-Pictoral design. 5) Hand prints are not period Pt. VIII 3-Period Armorial Elements 6) A hand apalmy gules is a reserved charge used by British heraldry. It is called the Hand of Ulster. Pt. XI Presumptious armory. If the client used a hand Instead of a hand print and limited the complexity, this might work.
Aelfreda, et al: We have not found any handprints, but did find a human footprint. Evah Marguerita Palma de Yuste The following badge associated with this name was registered in March of 1986 (via Caid):
Argent, a sinister human footprint bendwise sinister within a bordure azure. for the Fellowship of the Footprint
Knut: Or, a licorice candy cane issuant from base proper between two pairs of hands azure & gules, and purpure & vert. The complexity count of charges only pays attention to type, not tincture or facing. The complexity count is eight, for the tinctures Or, sable, azure, purpure, gules and vert, and the charges hand and whatever it is. There is nothing that I am aware of under the current RfS or precedents applying to them that addresses complexity of anything other than type in a single charge group. Would it be appropriate to suggest an
extension of RfS VIII.1.a (slot machine), "As another guideline, three or more types of charges should not be used in the same group." Along the lines of: As another guideline, three or more independently different instances of any characteristic that gives difference (except placement, which is covered under balance) should not be used in the same group. For example; In the device Argent, a pellet, a hurt and a tort, there are three independent tinctures in the primary group which exceeds the guideline. However in the device per pale argent and sable, three roundels counterchanged, although each roundel's tincture is a full CD from the other two, the counterchanging provides a common theme which means the tinctures are not independent. Also, In argent, a crescent, an increscent and a decrescent sable, the different orientations exceed the limit while there are many arrangements "in ordinary" where the arrangement provides the unifying motif for several different orientations.
Athenais: Oh, my. This has a complexity count of nine, and is glaringly modern. (Does the submitter work with children, by any chance?) This definitely needs to be returned for a redraw, and probably redesign, unless the submitter can prove that hand prints were used in period heraldry.
Aryanhwy: Badge: Oh dear.
15) Negan Arslan. New Name.
Negan (“one”) and Arslan (“lion”) are both found in Farrell, “On the Documentation and Construction of Period Mongolian Names” (http://www.sca.org/heraldry/laurel/names/mongol.html) who also notes:
“Period names of the n+n pattern are combined of two elements, both of which can stand on their own. The exception to this are names of this pattern that consist of a given name and an epithet. Examples of these are Al Altan (crimson gold), Qori Buqa (twenty bulls), and Mongke Temur (eternal iron).
This name follows the example given in “Qori Buqa (twenty bulls)” and should be acceptable.
Name Commentary
Ettiene, et al.: OK
Athenais: The article cited, “On the Documentation and Construction of Period Mongolian Names,” (http://www.s-gabriel.org/names/baras-aghur/mongolian.html) by Mike Farrell (Baras-aghur Naran), states,
“Period names of the n+n pattern are combined of two elements, both of which can stand on their own. The exception to this are names of this pattern that consist of a given name and an epithet. Examples of these are Al Altan (crimson gold), Qori Buqa (twenty bulls), and Mongke Temur (eternal iron).
This name follows the example given in “Qori Buqa (twenty bulls),” so seems fine.
Aryanhwy: Name: No comments.
16) Siban ingen Chartaig. New Device.
Azure, an escarbuncle and a bordure Or semy of shamrocks vert.
{Name reg’d 5/98}
Device Commentary
Pendar: The charges on the bordure are shamrocks, not trefoils. Trefoils have only one lobe, shamrocks have two. Similar concept to but clear of Maria Pagani (6.99 East): Purpure, an escarbuncle Or, a bordure Or semy-de-lys purpure.No conflicts found.
Ettiene, et al.: OK
Knut: Azure, an escarbuncle and a bordure Or, trefoily, vert. Clear.
Aryanhwy: No conflicts found.
17) Simonis Adriane. New Device.
Azure, on a pale Or between two swords inverted argent, a cat rampant sable.
{Name reg’d 12/00}
Device Commentary
Shauna: I did a conflict check and found nothing that appeared to conflict. Would have been nice if we knew _why_ it was returned last summer - don't you have a set of Northshield files going yet? Also, blazon correction - Azure, on a pale Or between two swords inverted argent a cat rampant sable. Only capitalize the first word of a blazon, proper nouns and the tincture 'Or'.
Athenais: The submitter's name was registered 12/00 via the Middle.The device looks clear of conflict.
Ettiene, et al.: OK
Aryanhwy: The client’s name was registered 12/00 via the Middle. The client’s previous submission, identical to this, was returned by Rouge Scarpe 08/01 for redrawing. As the cat is clearly rampant here, this resubmission fixes the original problem. However, the pale in this one is awfully large; the client should be advised to draw it narrower (though I do not think this is too large to necessitate a return). Some blazon-fu: “Azure, on a pale Or between two swords inverted argent, a cat rampant sable.”
18) Threewalls, Canton of. New Device.
Per fess vert and sable, a fess betressed between a chalice and a laurel wreath Or.
{Name reg. 2/99}
Device Commentary
Pendar: Blazon-fu: Per fess vert and sable, a fess betressed between a chalice and a laurel wreath Or.
This is actually reminiscient of the arms of Afghanistan! :) No conflicts found.
Ettiene, et al.: OK
Knut: Per fess vert and sable, a fess betressed between a chalice and a laurel wreath Or Clear
Athenais: This looks like a bend bretessed, since the crenelations are lined up with each other, rather than embattled counter embattled, where they would alternate. Generally, we blazon the primary charge first, which also allows us to drop “in chief” and “in base,” since the charge on top is blazoned before the bottom charge. Suggested reblazon: Per fess vert and sable, a fess bretessed between a chalice and a laurel wreath Or. This looks clear of conflict.
Aryanhwy: Blazon-fu: "Per fess vert and sable, a fess embattled counter-embattled between a chalice and a laurel wreath Or.
19) Vivienne de la Chartreuse. Device Change.
Purpure, a unicorn rampant argent and a chief lozengy vert and argent.
{Name reg’d 4/00}
If registered, client would like her old device (Azure, a unicorn rampant argent and a chief lozengy purpure and argent) [reg’d 4/00] released.
{To Aelfreda, et al: I have no idea. My preference would be to take them in the order they were actually sent in, but those records usually do not exist. I suspect that the standard option is to take the first one on the LoI}
Device Commentary
Pendar: ...so she wants to change her field tincture.... Toyota. No conflicts found. Granted, there are other rampant white unicorns on purple fields, but the tincture of the chief is different and the chief is charged.
Ettiene, et al.: OK
Aelfreda, et al: This is clear of the device of Julianna de Pardieu, # 12 above, with CDs for changing type and tincture of the secondaries. For future reference, what is the procedure when two submissions, both on the same letter, are clear of conflict with previous registrations, but conflict with each other?
Knut: The head looks equine and the beard isn't very prominent. Is this a grandfathered depiction? Clear.
Athenais: This looks clear of conflict.
Aryanhwy: No conflicts found.
Done by my hand this 15th day of July,
Paul Wickenden of Thanet, Rouge Scarpe
Paul W Goldschmidt
Sable, a bend sinister azure fimbriated Or, overall a flamberge gules, hilted and the blade enflamed Or. The enflaming motif is grandfathered to the Barony.
Could you ask the submitter to note grandfathered usage of now illegal motifs? We won't always catch them.
PRECEDENT: The College of Arms will no longer register flora and fauna in their natural "proper" tinctures if to do so they require the Linnaean genus and species. Proper is allowed for natural flora and fauna where there is a widely understood default coloration for the charge so specified. (Cover Letter, 04/91)
The “per chevron” line of division is awfully shallow, but should probably be cause for an artist’s note to the submitter rather than a return. Suggested reblazon: Per chevron purpure and vert, three bees within a bordure Or.
The submitter’s name and original device were registered 04/96 via the Middle.
Once again, look at the picture, not the blazon. I can't tell what the thing in the middle is, but it isn't a shepherd's crook. A shepherd's crook is a long thin staff with a large hook at the end. It is a tool, the hook must be able to fit around a sheep's neck. This is too thick (too heavy to carry around all day) and the hook is too small. Unlike paws, the human hand is virtually identical in outline to it's print. These are hands with funny detailing. I don't know if these are acceptable depictions of hands, but I believe this must be returned because of the thing in the middle anyway. The blazon is clear if properly drawn. Return for redraw.
3071 Cimarron Trail
Madison WI 53719
goldschp@mailbag.com
Disclaimer: This page is not officially sanctioned by the SCA,
Inc., the Middle Kingdom, or the MK College of Heralds. It is a private
project of the Escutcheon Herald (Angharad Rhos Tewdwr of Pembroke) and the Rouge Scarpe Herald (Paul Wickenden of Thanet) who
have based the information published here on publicly-available
documentation.