<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:admin="http://webns.net/mvcb/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"

xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssMod
ule">

<channel>
<title>Between Lawyers</title>
<link>/home/corante/public_html/betweenlawyers/</link>
<description>technology + culture + law</description>
<dc:language>en-us</dc:language>
<dc:creator>dhowell@gmail.com</dc:creator>
<dc:date>2007-06-28T13:02:12-05:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=3.34" />
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>

<item>
<title>Agreeing To The Cloud (Denise Howell)</title>
<link>http://betweenlawyers.corante.com/archives/2007/06/28/agreeing_to_the_cloud.php</link>
<description><![CDATA[<p>As more and better communication and collaboration functions move to the Web (under non-negotiated, vendor-centric terms of use), what are our obligations as both tech- and ethics-savvy lawyers?  I for one am not about to give up Gmail.  So, what's the best practice?  <br />
<ul><br />
<ol>Shun Web services, you simply can't control the data?</ol><br />
<ol>Use Web services only when you have specific, confidentiality and reliability guaranteeing service level agreements?</ol><br />
<ol>Use Web services liberally, but acquaint yourself with the applicable terms of use and make sure clients are amenable?</ol><br />
</ul><br />
I lean toward #3.  You?</p>]]></description>
<guid isPermaLink="false">72455@/home/corante/public_html/betweenlawyers/</guid>
<dc:subject>Practice of Law</dc:subject>
<dc:date>2007-06-28T13:02:12-05:00</dc:date>
</item>
<item>
<title>Blog In Peace (Denise Howell)</title>
<link>http://betweenlawyers.corante.com/archives/2006/06/09/blog_in_peace.php</link>
<description><![CDATA[<p>A colleague recently asked me what concrete steps I thought an organization could take to help ensure the concepts underlying a blogging policy are actually understood and implemented.  Bearing in mind I am <em>so</em> not an employment lawyer, I did have a few thoughts.</p>
<ol>
<li><strong>Blog.</strong>  I suspect that <a href="http://www.socialtext.net/bizblogs/index.cgi)">companies pursuing their own blogging initiatives</a> in addition to implementing policies intended to cover unsanctioned employee blogs will run into fewer problems with employee mistakes or misunderstandings.  This is because the  management and culture throughout the organization is bound to better grasp the process and related security and compliance issues.  IMO, the best &quot;training&quot; occurs by example and widespread use.</li>
<li><strong>Breathe.</strong>  As I've <a href="http://betweenlawyers.corante.com/archives/2006/03/06/blogs_least_risky_of_all.php
">pontificated here before</a>, there's a pretty good case to be made that blogs and their ilk are
actually the least risky form of corporate communication.  If a company adequately gets across the reasons it expects certain employee conduct with regard to external communications, confidential
information, and technology use, blogs, etc. are at least as &quot;safe&quot; as email and the phone; in fact, because people are more likely to understand up front these technologies are designed to accomplish wide and persistent information distribution, people are more likely to approach their use with caution and respect.</li>
<li><strong>Mix.</strong>  Organizations need to make sure their P.R./marketing and legal arms are communicating about how employees should be relaying work related information to third parties or the world at large, and they need to have an open-eyed appreciation of all the ways people might be or are using technology to do so.  Brace yourself:  P.R. and legal goals just might compete.  Management needs to understand those conflicts and decide what resolution best fits what they're trying to accomplish (and what the law <em>insists</em> they accomplish).</li>
</ol>]]></description>
<guid isPermaLink="false">59822@/home/corante/public_html/betweenlawyers/</guid>
<dc:subject>Blogging Policies</dc:subject>
<dc:date>2006-06-09T23:06:47-05:00</dc:date>
</item>
<item>
<title>Miller Brews Up a Little Email Controversy (Dennis M. Kennedy)</title>
<link>http://betweenlawyers.corante.com/archives/2006/02/21/miller_brews_up_a_little_email_controversy.php</link>
<description><![CDATA[<p>Did you ever wish that you could have old email addresses forward to your new email address? How about a way to remember which of your throw-away email addresses you might have used to register on a website?</p>

<p>A <a href="http://www.computerworld.com/blogs/node/1825">story on the ComputerWorld website</a> reports that Miller Brewing has touched off some controversy by sending follow-up emails to the "real" email addresses of people who register with "throw-away" email addresses. Some describe it as a little eerie or feeling a little like being stalked. I'm wondering if there might be a business model in providing a service that eventually reaches you at a good email address as you change, forget and move through a variety of email addresses. </p>

<p>I'll let you decide how creepy <a href="http://www.computerworld.com/blogs/node/1825">this story</a> seems to you. </p>

<p>The detective efforts of the people involved are noteworthy for giving you excellent practical tips for digging for this type of information.</p>]]></description>
<guid isPermaLink="false">49032@/home/corante/public_html/betweenlawyers/</guid>
<dc:subject>E-Mail</dc:subject>
<dc:date>2006-02-21T15:31:33-05:00</dc:date>
</item>
<item>
<title>That&apos;s Not What I Meant in My Email (Dennis M. Kennedy)</title>
<link>http://betweenlawyers.corante.com/archives/2006/02/16/thats_not_what_i_meant_in_my_email.php</link>
<description><![CDATA[<p>Dave Pollard has a great post called "<a href="http://blogs.salon.com/0002007/2006/02/16.html#a1439">That's Not What I Meant</a>" about the importance of communication, context, tone and other cues in a world where some say that the tone, and often the intent, of half of all e-mail is misconstrued by readers. That also happens every now and then with blog posts. ;-)</p>]]></description>
<guid isPermaLink="false">48742@/home/corante/public_html/betweenlawyers/</guid>
<dc:subject>Blink &amp;#8250;</dc:subject>
<dc:date>2006-02-16T19:36:20-05:00</dc:date>
</item>
<item>
<title>A $4 Billion Email Problem? (Dennis M. Kennedy)</title>
<link>http://betweenlawyers.corante.com/archives/2006/02/14/a_4_billion_email_problem.php</link>
<description><![CDATA[<p>Makes you wonder what's buried in your email inbox, doesn't it? - <a href="http://www.computerworld.com/softwaretopics/software/groupware/story/0,10801,108682,00.html">E-mail glitch hides $4B in Air Force deals</a>.</p>

<p>Another reason to institute some email training. </p>]]></description>
<guid isPermaLink="false">48582@/home/corante/public_html/betweenlawyers/</guid>
<dc:subject>Blink &amp;#8250;</dc:subject>
<dc:date>2006-02-14T21:28:18-05:00</dc:date>
</item>
<item>
<title>You&apos;ve got mail, dude (Tom Mighell)</title>
<link>http://betweenlawyers.corante.com/archives/2005/11/07/youve_got_mail_dude.php</link>
<description><![CDATA[<p>Which causes the mind to be more distracted -- marijuana, or e-mail?  If you picked e-mail, you'd be right.  A recent study found that people who had to check e-mail and instant messages while taking an IQ test <a href="http://www.discover.com/issues/nov-05/departments/emerging-technology/">scored lower</a>  than those who took the test while they were stoned.</p>

<p>It definitely raises an important question:  are we doing our best thinking while we are in front of the computer?</p>]]></description>
<guid isPermaLink="false">37713@/home/corante/public_html/betweenlawyers/</guid>
<dc:subject>E-Mail</dc:subject>
<dc:date>2005-11-07T06:16:45-05:00</dc:date>
</item>

<creativeCommons:license>http://creativecommons.org/licenses/by-nc/2.0/</creativeCommons:license>
</channel>
</rss>