Clarification, was Re: [MR] RE: heraldry

[EoganOg at aol.com]

Ok, I guess my posting was a little too vague.  I've recieved a number of 
private emails regarding this, so before I get too many more, let me just say 
that I am well aware of the various cases in which Laurel may change a 
blazon, and the cases in which a submitter may propose a change to his or her 
own blazon.  

What I found odd in the original post I was replying to was that it suggested 
that this *Kingdom* had altered the blazon, and that this change in blazon 
resulted in a different *emblazon* and thus a change in the actual device.  I 
knew this could not have been the case and so was asking for clarification, 
which I have recieved.  Thanks.

I was *not* suggesting that Laurel could not reblazon a device or that such 
changed do not or should not occur.
Aye,
Eogan

In a message dated 6/4/01 9:07:14 PM Eastern Daylight Time, 
silverdragon at charleston.net writes:


> > > That in itself is a matter open for discussion. Years after the blazon
> > > of my device had been approved and registered, this kingdom changed
> > > it -  and as blazoned, it is no longer the same device.
> > >
> >
> > Something doesn't sound right about this.  Years *after* your device was
> > registered by Laurel at the Society level, someone in this *kingdom* 
> changed
> > the way it was blazoned?
> >
> > And the blazon was significantly different enough that it actually 
> changed
> > your device?  (There are often many ways to blazon the same device).
> >
> > As far as I know, once a particular blazon is registered, it's set.  The 
> only
> > way to change it would be if you requested a change by basically going
> > through the submission process again, with documentation as to why you 
> wanted
> > to registered blazon to be altered.  But that has to be initiated by you, 
> not
> > anyone else.
> >
> > What went on here?
> >
> > Aye,
> > Eogan
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://seahorse.atlantia.sca.org/pipermail/atlantia-atlantia.sca.org/attachments/20010604/55cd73e0/attachment-0020.htm>