Editing Travel Names
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 61: | Line 61: | ||
> 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. | > 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. | This ruling went into effect with this, the May 2009 Pelican meeting. | ||
http://heraldry.sca.org/loar/2009/05/09-05cl.html | [[http://heraldry.sca.org/loar/2009/05/09-05cl.html]] | ||
==='''April 2009 - Traveler documented, not just SCA compatible:'''=== | ==='''April 2009 - Traveler documented, not just SCA compatible:'''=== |