This is the July 2004 Middle Kingdom Letter of Acceptances and Returns for Escutcheon’s May 2004 Letter of Intent.

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. Commentary, rulings, etc. by Rouge Scarpe are placed in small cap print. Thanks to Malachai, Canute, Malcolm, Femke, the SW Ohio Commenting Consortium, and Master Talan Gwynek for this month’s commentary.

(Esct Note: This was edited after this was posted as commentaries from Mikhail and AElfreda was missed. Special apologies from Rouge Scarpe and Escutcheon for being missed.)

From the June LoAR

#7. Jaret {of} Coventry – Device Pended – Per chevron inverted sable and vert, a pheon inverted Or.

Device was pended since the charge was actually a broadarrow, not a pheon. The client was contacted as he does want a pheon so the device is being returned for redraw.

1) Ivegard Sask (F) -- New Name and Device – {Vert, on a fess argent a yew branch proper fructed gules between two horses passant argent}

Blazon changed to: Vert, on a fess between two horses galloping argent a yew branch reversed vert fructed gules

According to the client: "Literally, Ivegard the Saxon, per conventions in the low countries circa 800 AD. [Ivegard] is comprised of prothema 'Iv' -- meaning "yew" and deuterothema - 'gard', meaning "fenced court, young descendant, or branch" (feminine deuterothema in the low countries in this period). So the first name could mean 'Yew branch." I have relied entirely on the onomastic research done by Kees Niewenhuisjen, and I have included our correspondence. All my reference information came directly from his web pages."

The client has included several pages of emails from Kees Nieuwenhuijsen plus several pages of a biography. Also the following webpages: http://www.koeblergerhard.de/afrieswbhinw.html
http://www.keesn.nl/names/index/html

Client will not accept major changes and cares most about 9^th century continental Saxon language/culture.

Name Commentary

Talan - > So the first name could mean 'Yew branch."

No, it couldn't, even ignoring the fact that by ca.800 Germanic compound names were no longer generally treated as meaningful compounds; the Germanic deuterotheme -gard is from Proto-Germanic *gard- 'enclosure; yard; house', in names probably with the extended sense 'protection, defense'.

Kees is fairly knowledgeable, but in this case he steered her astray. His own data do not support the claim for a prototheme Iv-: they show the element only in the masculine simplex name Ivo. Tavernier-Vereecken, Gentse Naamkunde van ca. 1000 tot 1253, p. 165, says that the the name is French, of unknown origin, though it may in at least some cases be Germanic, from a pet form of some longer name. Forssner s.n. Ivo doubts that it is Germanic, since it occurs almost exclusively in Romance contexts, and is inclined to think it of Celtic origin.

Morlet (I:148b) has a small amount of evidence for such a Germanic element: it may appear in the masculine names Hifarius, Ivesomus, Ibaldus, and Ibuinus, for each of which she has a single attestation. (She also has numerous instances of Ivo and a few of its feminine counterpart Iva, as well as some diminutives of each.) However, these are not entirely unproblematic even apart from their scarcity. The Germanic root underlying the putative Iv- theme is *îwaz 'yew' (where the circumflex indicates a long vowel), which was still îwa in Old High German. It wasn't until fairly late in the MHG period that this /w/ became /b/ in some dialects, eventually leading to the modern German Eibe 'yew'. [Watkins s.r. ei²; von Kienle, Sect. 135] The names Ibaldus and Ibuinus, on the other hand, are attested from 943 and no later than ca.830, respectively, late in the Old High German period. One might consider the possibility that this is somehow the result of Romance influence, since the names were recorded in what is now France, but this does not appear to be the normal development in Old French. [Pope, Sect. 636]

One might wonder whether it is just coincidence that the deuterothemes in both Ib- names originally started with /w/, being from Proto-Germanic *-waldaz and *-wini-, respectively; it may not be, but so far I've found no indication that /b/ (in Ibaldus) or /bw/ (in Ibuinus) is a normal outcome of /ww/ in either Old French or the German dialects. It seems likelier that Ib- here, as in Ibricho (Müller, 19), is a variant of Eb-, a secondary prototheme from Ebur- found in a handful of names in Morlet (I:78b): Ebehardus, Ebnandus, Ebrada.

Finally, I've found no evidence of such a 'yew' prototheme in any other Germanic language.

On balance I do not think that the evidence supports the existence of a Germanic prototheme Iv- (or similar) that would justify constructing a hypothetical feminine name Ivegard.

Forssner, Thorvald. Continental-Germanic Personal Names in England in Old and Middle English Times (Uppsala: K.W. Appelbergs Boktryckeri, 1916).

von Kienle, Richard. Historische Laut- und Formenlehre des Deutschen (Tübingen: Max Niemeyer Verlag, 1969).

Müller, Gunter. Studien zu den Theriophoren Personennamen der Germanen (Köln: Böhlau Verlag, 1970).

Pope, M.K. From Latin to Modern French (Manchester: Manchester University Press, 1966).

Watkins, Calvert. The American Heritage Dictionary of Indo-European Roots, 2nd ed. (Boston: Houghton Mifflin, 2000).

>“The client has included several pages of emails from Kees Nieuwenhuijsen plus several pages of a biography.”

(Bibliography, I presume, not biography.) It's possible that Kees had more in the way of evidence than is apparent from the summary in the ILoI and the information on his website; I'd be happy to look at his documentation.

> Also the following webpages:

> http://www.koeblergerhard.de/afrieswbhinw.html

Presumably this, which is an on-line etymological dictionary of Old Frisian, is offered as support for the byname. It gives sask as a variant of the adjective sassisk 'Saxon', the noun being Saxa 'a Saxon'. But there are a couple of problems.

First, while we have isolated words and names in Latin texts from an earlier date, the earliest surviving connected text in Old Frisian is from the second half of the 13th century. Some early Old Frisian texts are probably copies of 11th century material, but that still leaves quite a gap back to the language of ca.800. It's not at all clear that sask is an old enough form; if it's a worn-down form of sassisk, which appears likely, it may well be too young. (In fact it would not be surprising if sassisk itself derived from an earlier, unattested *sahsisk by assimilation of /hs/ to /ss/.)

Secondly, we have no information on the proper grammatical structure for an ethnic byname. The submitted byname uses an adjective in the so-called strong form, but it's possible that the weak form saske is wanted. Then again, it may be that the noun is more appropriate, and that would raise yet another issue: was the masculine noun Saxa used for both men and women, or was there a corresponding feminine noun? And whether it should be the adjective or the noun, is it more likely to have been used with or without the definite article? (I'm ignoring here the fact that bynames were extremely rare ca.800 anyway; this does mean, unfortunately, that the answers to these questions may simply not be known.)

In short, unless there's something useful in the e-mails from Kees, I don't think that this name is acceptable.

> http://www.keesn.nl/names/index/html

The correct URL is <http://www.keesn.nl/names/index.html>.

Device Commentary

Talan - Vert, on a fess between two horses galloping argent a yew branch reversed vert fructed gules; it wouldn't greatly surprise me to find a period example or two of horses in this posture, but in the Society it's likely to be a bit problematic. Certainly it would be better to make them passant or courant.

Canute - Vert, on a fess between two horses ??? argent a yew branch reversed proper fructed gules

This naturalistic posture isn't statant or passant because more than one foot is raised off of the ground and it isn't courant because the legs aren't extended. This could have a problem with blazonability and reproducibility issues.

Clear

Malcolm - Device: Stylistic concerns only. I don’t find a conflict here.

1) The horses aren’t passant. I don’t know what they are, but it suggests motion. It looks like they are running, and I don’t believe this to be period in style.

2) It suggests “slot machine” style. It isn’t, but … It looks modern.

I’d return for redraw and reblazon; I think he has a good base to work from, but I don't think it would pass muster and I don't think we do him any service to send it along.

Femke - As has been discussed, this should probably be reblazoned with the horses as courant rather than passant, and the submitter urged to draw them in a more heraldic style in the future. No conflicts noted.

Ohio - Proposed reblazon to " Vert on a fess between two horses courant argent, a yew branch proper fructed gules". The groups opinion was that the horses are clearly not passant, but to be represented as galloping. The usual term we know of for this would be courant. Unfortunately, the horses as represented are not in the classic courant positioning, however, since this appears to be the desired position, we feel it falls within reasonable license to be termed courant.

We found the terms " galoppant" and "in full career" in Parker. We had no certainty of the use of galoppant in period, though the intent is obvious and the term does not appear to have been used previously in SCA. The group was divided as to whether or not " in full career" would be the same as courant. Demanding a redraw seems a bit extreme, as the submittor clearly intended two galloping horses, and in fact drew two recognizeably galloping horses. It seemed unlikely that a group of period heralds would be standing around looking at a galloping horse and debating on whether it was courant or galoppant or some other term. That said, we felt that with provision for artistic license, courant was the simplest and most direct solution to the problem. If by chance a return were made based on conflict or failure of the name the client could be advised as to the more heraldically proper representation of courant. There was also question as to whether the use of Yew would require the Linnaean name as well. Mistakes in the cited URL were noted, but worked around. Recommend pass on with reservations.

Mikhail and AElfreda -- The horses are in a naturalistic posture (galloping?), rather than in a standard heraldic posture.

Name – passed on to Laurel for Pelican to look at correspondence/Documenation and make final determination.

Device – passed on to Laurel for consideration and final determination on word usage.

2) Jonet of Keyth (F) -- New Name

[Jonet]: A.D. 1391 under the heading of Joan in “A List of Feminine Personal Names in Scottish Records” by Talan (http://www.s-gabriel.org/names/talan/scottishfem/scottishfemearly.html)
Black’s “Surnames of Scotland” -- p 119 Jonet is found under [Burrel] and [Towers] p. 777

[of Keyth]: Before 1375 A.D. “13th & 14th Century Scottish Names,” by Symon Freser of Lovat (http://www.s-gabriel.org/names/symonFreser/scottish14/scottish14_sur.html )
“The Bruce: The Book of the Most Excellent and Noble Prince, Robert de Broyss, King of Scots” completed in 1375.

Client will not accept major changes and cares for 14th Century Lowland Scots language/culture.

Commentary

Ohio - No issues found with the name. Documentation seems sound. Okily-dokily. Recommend pass on.

Passed to Laurel

3) Kastenstadt, Canton of—Name Resubmission
Returned by Rouge Scarpe on the July 2003 LoAR because there was no documentation for Kasten- as used. The client has now provided some documentation.

The group will not accept major changes and cares more about sound and to be authentic for German language/culture.

The group states that they are not particularly attached to the meaning of the name but are much more focused on the name itself.

According to the client: “The name [Kastenstadt] is made up of two elements.

According to genealogy.net (http://www.genealogienetz.de/misc/etym/ortsnamen.html) [Kasten] which is Modern German for “box.” [Kasten] was used as a determinant word in the following German place names: Kasten, Kastendiek, Kastenreuth, and Kastenseeon. In old german: “Kasten” means “grainery, or grain-box.”

The root of the name is - ‘stadt’ meaning “town” or “city.”

When putting these two elements together: “City where there are Graineries.”

A petition is included with the submission.

Commentary

Talan - It was submitted on the 5/03 ILoI and returned on the 7/03 ILoAR on the grounds that no support was provided for Kasten- as used. They have at least attempted to address the issue.

> According to the client: ‘The name [Kastenstadt] is made up of two elements.

> According to genealogy.net (http://www.genealogienetz.de/misc/etym/ortsnamen.html)

[Kasten] which is Modern German for ‘box.’ [Kasten] was used as a determinant word in the following German place names: Kasten, Kastendiek, Kastenreuth, and Kastenseeon. In old german: ‘Kasten’ means ‘grainery, or grain-box.’

The term Kasten does not even occur on the cited page, which discusses common second elements. Unless the ILoI has inadequately summarized their documentation, they've offered no evidence for the claim that Kasten once meant 'granary; grain-box'. The statement is, however, approximately correct. More accurately, Middle High German kaste had as one of its meanings kornboden, kornhaus, bes. zur aufbewahrung des zehendgetreides 'granary, especially for storage of the grain tithe':

<germa83.uni-trier.de/cgi-bin/gotoMWVLemma.tcl?LK00540>.

There is also MHG keste 'chestnut tree', together with kesten and kestene, which can refer either to the tree or to its fruit:

<germa83.uni-trier.de/cgi-bin/gotoMWVLemma.tcl?LK01030>.

The tree is also kestenboum, kastenboum, with boum 'tree' (modern Baum). The modern term is Kastanie, and the MHG term does occur with a in the first syllable (as seen also in kastenboum above).

It is very unlikely that all of the place-names Kasten, Kastendiek, Kastenreuth, and Kastenseeon contain MHG kaste 'granary; grain-box'. Brechenmacher s.n. Kastenholz notes that this is a place-name from Kastanie 'chestnut', hence 'chestnut-wood'. Since -reuth indicates a clearing, it would be quite surprising if Kestenreuth weren't originally 'clearing in the chestnut trees'. Similarly, -seeon is 'lakes', from the dative plural sewun, sewon of Old High German seo 'a lake', and '(at the) lakes among the chestnuts' is a far likelier place-name than '(at the) lakes among the granaries'. For that matter, Low German -diek, which can represent either High German Teich 'a pond, a pool' or Deich 'a dike, an embankment', is more plausibly modified by 'chestnut' than by 'granary'.

> The root of the name is - ‘stadt’ meaning ‘town’ or ‘city.’

> When putting these two elements together: ‘City where there are Graineries.’

> The group isn’t that attached to meaning as much as the name.

Good: the meaning's unlikely, but something close in form is perhaps justifiable for a town that grew up in a chestnut wood. Brechenmacher s.n. Eichstett(er) notes places named Eichstädt, Eichstätt, and Eichstetten, and s.n. Apfelstetter he notes a place names Apfelstetten; the first elements are apparently 'oak' and 'apple', respectively. I was unable to find any other place-names combining a tree name with a stadt-like element, however, though there's some small indication in the form of rare surnames on the web that a few may have existed. A stadt-like place-name based on the 'chestnut' word may not be the best historical re-creation, but it does appear to be possible.

The second elements in these place-names are ultimately from Old High German stat 'a place; a region'; this became Middle High German stat, with the same senses and, from about 1200, the sense of modern German Stadt 'town'. (For the date see the German etymological dictionary at <www.koeblergerhard.de/derwbhin.html> s.v. Stadt.) The dative singular of stat was stete; the nominative gave rise to modern German Stadt 'a town' and Statt 'stead, place' (as in an seiner Statt 'in his stead, in his place'), while the dative gave rise to the modern German Stätte 'a place'. The spellings -städt and -stätt derive from the dative, which was required by most locative prepositions; they retain its vowel – ä and e are pronounced almost identically and are often interchanged in MHG and early modern German – though they've lost the final -e. The form -stetten appears to be from the dative plural, MHG steten.

Besides the forms shown above, -stadt and -statt also occur in modern place-names. I don't know what factors have gone into determining the modern forms. I'm reasonably sure that there is an element of chance involved, but there also seems to be some regional variation. On balance I think that it's probably safest to stick to a straightforward MHG spelling: Kastenstat is very close to what they submitted and would be orthographically unremarkable in the 14^th century, so far as I can tell. (E.g., Brechenmacher s.n. Kallstadt notes the byname de Kalstat 1316.)

Ohio - With deference to Talan's commentary ( we are not worthy...) by whatever documentary tapdance required it's a nice name and actually makes some sense. The only question we had in their presented argument was that nowhere does it indicate that any of the " kasten-" place names is period. Also, if the use of the feminine name karsten is used, is the -stadt part still appropriate to link with the feminine name? Recommend passing on if questions answer reasonably.

Passed to Laurel as is for final determination of spelling.

{4) Mystic Straits, Canton of—[Resubmission] Name and Device -- Azure, between two mullets argent a bend enbowed counter-embowed of the second, overall a laurel wreath counterchanged.}

There are no records of this having ever been submitted, therefore it is being treated as a new submission.

According to the paperwork, the canton has been into existence in 1971 as the Canton of Northwoods. The canton became dormant for several years and became a part of the Barony of Roaring Waste. The name "Roaring Waste" refers to the 'roaring waste" that poured into the Detroit River. “Mystic Straits” refers to the huge billows of steam when the steel tailings dumped into the river.

"The name would have been consistent with the medieval naming practices of a population that lived near a largely unexplainable natural phenomenon. We feel that it is important to maintain this continuity with our Barony's past, and hope that we may continue to use a name that has a document able history in the kingdom from before the time when names needed to be registered."

Included in the documentation is a Pale announcement dated October 13/14, 1973 for Crown Tournament.

A petition is also included for both name and device.

Client will not accept major changes and cares more for meaning.

Name Commentary

Talan - The name is not consistent with any medieval place-naming practices. The justification reflects modern sensibilities and word usage. The only period sense of mystic noted in the OED is 'spiritually allegorical or symbolical; of the nature of, or characteristic of, a sacred mystery; pertaining to the mysteries of the faith', which is clearly inappropriate.

The summary suggests that either there was no such group at the time when its name could have been registered, or the group simply failed to register it. Neither is grounds for a special hardship dispensation.

Malcolm - The reason for the original return isn’t provided, though it suggests inactivity. In any event, “mystic” implies some supernatural endowment. I don’t find “magical” or any such other thing occurring in place names in period, so IMO it’s fantasy. Thus, I’d recommend it be bounced for those reasons. Sadly, this bounces the arms too, which I find to be quit pretty and well drawn.

Femke - I’m not sure what the existence of the canton has to do with the suitability of the submitted name. Nor am I sure that “mystic” is an acceptable descriptor. Perhaps “misty” might work out better?

Ohio - The name has minimal plausibility even if the presented documentation qualified as documentation. Setting aside the TSCA provisions, we deemed it unlikely that real folks in period would choose to live near an unexplained phenomenon, (or near Detroit, for that matter) let alone advertise it. Such things would probably be largely avoided when it came to a place to settle. The fact that the name has a history seems rather irrelevant, as does a thirty-year-old Pale ad.

Nothing we found would indicate the period use of something like this, even assuming that steaming water in a river would be deemed mysterious. Recommend return of both items.

Mikhail and AElfreda -- There does not seem to be a strong case presented for passing this name under the hardship clause. When the Shire of Starleaf Gate's name was passed (August 1991 Laurel Letter of Acceptance and Returns), it was
stated "While the name quite possibly would not pass under the current rules, the situation described by Lord Dragon in the LoI makes it an overwhelmingly strong candidate for consideration under the hardship clause".  Unfortunately, the Midrealm Letters of Acceptances and Returns are not online from that far back, so I cannot tell what sort of case was made in that instance.

Device Commentary

Talan - Azure, surmounting a bend sinister embowed counter-embowed between two mullets of eight points argent a laurel wreath counterchanged. Or Azure, a bend sinister embowed counter-embowed between two mullets of eight points argent and surmounted by a laurel wreath counterchanged.

Malachai - Improperly drawn as blazoned but did not find any conflicts. If picture is correct should be: Azure, between two mullets a bend sinister enbowed counter-embowed argent, overall a laurel wreath counterchanged.

Malcolm - The blazon is Victorian in style: Blazon fu: Azure, a bend sinister embowed-counter-embowed between two mullets of eight points argent, ______ a Laurel Wreath counterchanged. There’s a term for this, it’s not overall, and not throughout, and I am drawing a blank – my wife has my Books in the trunk of the car, and I can’t think of the term.

Canute - [Or, a bend sinister sable, overall on a delf ployé counterchanged] Current precedent indicates: The only time we permit a charge to be counterchanged over another is when they are both ordinaries. (Shire of Crystal Crags, 12/98 p. 13)... [Tarvin, Shire of, 08/01, R-Atlantia] Precedents - François, under Counterchanging

Return for violating RfS VIII.3

Ohio - Preferred reblazon "Azure between two mullets a bend embowed counterembowed argent overall a laurel wreath counterchanged". That "of the first" and "second" business is just annoying (Anluan). Oy Vey. The opinion was that the device dies quickly for counterchanging the complex charge, as in the oft-cited Bruce precedent.

Mikhail and AElfreda -- The bend sinister is probably too straight to be called "embowed counter-embowed". However, the much bigger problem is the counterchanged Laurel wreath. According to The Precedents of Jaella of Armida "The only time we permit a charge to be counterchanged over another is when they are both ordinaries. (Shire of Crystal Crags, 12/98 p. 13)." We suggest return for redrawing.

Name – Returned for non-period practice.

Device – Returned with name, also for violating RfS VIII.3

{5) Osric Edwardson (M) -- New Name and Device -- Per bend sinister purpure and sable, over all a chimera passant with a head and body of a lion, head and foreleg of a goat, head of a dragon, and the tail of a snake Or, armed argent and langued with fire issuing from its mouth azure.}

[Osric] - Saxon name occurs historically primarily in “King Osric of North Umbria,” who was belived to be the younger brother of Osred I, and succeeded (Oenred in 718 AD and was succeeded by Ceolwulf in 729).

According to the client: “Osric also appears in Wm Shakespeare;s play “Hamlet” as a very small background character. It may be safe to assume that the name, though maybe not in vogue at the time, would have occured anywhere inbetween and would be recognized by thepopulous of the times as an appropriate name for a person.”

According to the client: “Edward has been a popular British name throughout the ages and so has the practice of using son/father relationships as surnames.”

Client will not accept major changes and wants late 15th century English name. He cares most about sound.

Name Commentary

Talan - He was preceded by Coenred, not Oenred.

> According to the client: ‘Osric also appears in Wm Shakespeare’s play ‘Hamlet’ as a very small background character. It may be safe to assume that the name, though maybe not in vogue at the time, would have occured anywhere inbetween and would be recognized by the populous of the times as an appropriate name for a person.’

Well, no, it isn't, especially since Hamlet is set in Denmark and is based on a tale told by Saxo Grammaticus (early 13th century); there is no reason to assume much of anything about the names used. In fact I have found no instance of Osric later than the 9th century: it is not in von Feilitzen, Seltén, Bardsley, Andreanna Innes's index of forenames occurring in Bardsley, or Reaney & Wilson (or any of several less general sources that I've checked). It apparently died out so early and so thoroughly that it did not produce a modern surname.

> According to the client: ‘Edward has been a popular British name throughout the ages and so has the practice of using son/father relationships as surnames.’

It should be noted, however, that English patronymics took different forms in different periods. An Old English Osric Eadweardes sunu would be fairly unremarkable, but usage changed after the Conquest, and the usual form of patronymic was then simply the father's name, unmodified. It isn't until about 1300 that Middle English patronymics in <-son> become common. However, Edwardson is not a problem: RW s.n. Edwardson have William Edwardson 1518. (Of course by 1518 this was an inherited surname and not a true patronymic anyway.)

> Client wants late 15th century English name.

I'm afraid that Osric is incompatible with the late 15th century and with the surname in the submitted form.

Malcolm - All respects to Lord Osric, but Osric is early period, and the Bard doesn’t really qualify as an onomastic source in any reference I can find on Laurel site. I don’t believe the burden of proof has been met.

Femke - <Osric> is Old English. I can’t find any evidence for it within the submittor’s specified period. Nor can I find any evidence for <Edwardson>, though <Edwards> seems relatively common. Some change may be necessary to create a registerable name from this. <Osgood Edwards> would work for the submittor’s requested period.

Ohio - Name appears well documented and even reasonable. Pretty basic.

Device Commentary

Talan - This is neither a Greek chimera, an English heraldic chimera, nor a German heraldic Schimäre. It is probably best blazoned as a three-headed chimerical monster composed of ....

Malachai - Kathryn the Innocent

The following device associated with this name was registered in May of 1984 (via An Tir): Vert, a chimera passant with a lion's body, a dragon's tail, a lion's head, a goat's head, and a dragon's head regardant, Or.

Malcolm - Patching this through my PSPro and making the purpure not violet, the division isn’t all that clear. That is also not a Chimera. Lord, that blazon is a mouthful.

Canute - Per bend sinister purpure and sable, a chimeric monster passant with a head Or incensed azure and body of a lion, head and forelegs of a goat, head of a dragon, and tailed with the head and body of a snake Or

Pol MacNeill - December of 2000 (via Meridies):

Per bend sinister purpure and sable, a catamount statant reguardant, in sinister chief a mullet of four points Or.

CD for the mullet of four. Possible CD for the difference in the forelegs and the extra heads. The head of the snake is visually similar to the tuft of a lion's tail.

Ohio - A fairly cursory check came up with a likely conflict, Kathryn the Innocent (05/84 An Tir) "Vert, a chimera passant with a lion's body, a dragon's tail, a lion's head, a goat's head, and a dragon's head regardant, Or". We get 1CD for the field. The details of the chimeric beast's construction presumably would not merit a CD. The azure fire expressed on the purpure field seems poor stylistically, but probably not relevant to differencing. Recommend device return for conflict.

Name – returned for non-compatible construction. Talan’s comments will be sent to the client for help in reconstructing a name.

Device – returned with name, also for conflict with Kathryn the Innocent.

6) Philippa of Otterbourne (F)-- New Device -- Azure, an otter rampant and on a chief wavy Or,{3} harps azure

(Name reg’d Apr ‘94)

Blazon will be change to ‘three’

Commentary

Malcolm - The otter rampant is unusual, but it’s a nice cant, and a good blazon. I find no conflicts.

Cantue - Lorimel the Gentle - July of 1974:

Azure, an otter sejant erect Or.

CDs for the secondary and tertiary groups.

Clear

Ohio - Spent significant time chewing on potential conflicts; nothing stuck. Recommend pass on to more thorough conflict checkers than us.

Mikhail and AElfreda -- Device: Nice cant!

Note: The name was submitted on the March 15 2003 Internal Letter of Intent as Philippa of Otterbourne (note: one "L"). On the May 2003 Internal Letter of Acceptances and Returns it was passed, but with two "L"s. No explanation
was given for the spelling change. The name passed on the September 2003 Laurel Letter of Acceptances and Returns, but with two "L"s. The submitter has mentioned that she is appealing the spelling change, but we do not know the status of that appeal.

Passed to Laurel

7) Richard of Stokesley (M) -- Device Resubmission – {Argent, a chevron and three boars passant gules}

(Name sent to Laurel Nov ‘03)

Blazon changed to: Argent, a chevron between three boars passant gules

Device was returned for conflict by Rouge Scarpe November 2003. The client has since gotten permission to conflict with Basileios Philanthropenos Philomathes: “Argent, a chevron between three crosses of Jerusalem gules.”

(Esct. Note: There is a typo in the permission which the herald has written to explain. The type reads “John Vandenburg” and it should read John Stockley.)

Commentary

Talan - Argent, a chevron between three boars passant gules.

Malcolm - Blazon Fu: The Chevron is BETWEEN three boars, et al. The only conflict I find is covered by his permission to conflict, so it looks to me like he is good to go.

Canute - Argent, a chevron between three boars passant gules

Basileios Philanthropenos Philomathes - January of 2000 (via Meridies): Argent, a chevron between three crosses of Jerusalem gules.

Single CD for type of secondaries.

Return for conflict.

Ohio - Obviously cleared of cited conflict by writ of permission. No other conflicts found. Everyone liked it. Recommend pass on

Passed to Laurel. It is clear of conflict with Basileios by the simplicity rule.

In Service,

Mistress Elena de Vexin

Rouge Scarpe Herald