<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Feb 25, 2014, at 1:35 AM, Marilyn Cade <<a href="mailto:marilynscade@hotmail.com">marilynscade@hotmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="hmmessage" style="font-size: 12pt; font-family: Calibri; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div dir="ltr">I return to my plea that we try to use commonly understood terms. <div>While of course, we all speak the languages we understand, even if they</div><div>are code for the specialization of our personal or professional daily lives.</div><div><br></div><div>We are seeking not to just hear views from all of us who work on a variety</div><div>of spaces, but to attract new participants to this space.</div></div></div></blockquote><br></div><div>+1. It�s *hard* to remember what it�s like to not know our particular jargon, but it�s the only way to find shared concepts and perspectives with other people who don�t. And learning other people�s language is a bonus :)</div><div><br></div><div>Suzanne</div></body></html>