<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Officer Titles</title>
	<atom:link href="http://www.adamsdrafting.com/2006/09/24/officer-titles/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2006/09/24/officer-titles/</link>
	<description></description>
	<lastBuildDate>Tue, 31 Jan 2012 01:23:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2006/09/24/officer-titles/comment-page-1/#comment-1486</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Thu, 14 Dec 2006 16:01:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/09/24/officer-titles/#comment-1486</guid>
		<description>Postscript: I ran my issue with longer titles by the Chicago Manual of Style&#039;s online Q&amp;A, giving them the example I used in my post plus one other. This is what they said:

&quot;Chicago style lowercases the title and we feel no reluctance! Your sentences look just fine to me. But if you&#039;re uncomfortable lowercasing, by all means uppercase them. It would be a bad idea to mix and match styles for titles of different lengths, however.&quot;

So with renewed confidence I&#039;ll advocate lowercase across the board.

Ken</description>
		<content:encoded><![CDATA[<p>Postscript: I ran my issue with longer titles by the Chicago Manual of Style&#8217;s online Q&#038;A, giving them the example I used in my post plus one other. This is what they said:</p>
<p>&#8220;Chicago style lowercases the title and we feel no reluctance! Your sentences look just fine to me. But if you&#8217;re uncomfortable lowercasing, by all means uppercase them. It would be a bad idea to mix and match styles for titles of different lengths, however.&#8221;</p>
<p>So with renewed confidence I&#8217;ll advocate lowercase across the board.</p>
<p>Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2006/09/24/officer-titles/comment-page-1/#comment-933</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Fri, 06 Oct 2006 13:34:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/09/24/officer-titles/#comment-933</guid>
		<description>Michael: Regarding your question, I don&#039;t have a problem with using &quot;the&quot; in the defined term &quot;the Customer.&quot; In fact, I prefer including &quot;the.&quot; (See MSCD 2.39.) We are, after all, dealing with a common noun rather than a name. You wouldn&#039;t, after all, tell your sales staff &quot;Customer is always right!&quot; You&#039;d say &quot;The Customer is always right.&quot; (Assuming you share that sentiment!) Ken</description>
		<content:encoded><![CDATA[<p>Michael: Regarding your question, I don&#8217;t have a problem with using &#8220;the&#8221; in the defined term &#8220;the Customer.&#8221; In fact, I prefer including &#8220;the.&#8221; (See MSCD 2.39.) We are, after all, dealing with a common noun rather than a name. You wouldn&#8217;t, after all, tell your sales staff &#8220;Customer is always right!&#8221; You&#8217;d say &#8220;The Customer is always right.&#8221; (Assuming you share that sentiment!) Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Fleming</title>
		<link>http://www.adamsdrafting.com/2006/09/24/officer-titles/comment-page-1/#comment-807</link>
		<dc:creator>Michael Fleming</dc:creator>
		<pubDate>Sun, 24 Sep 2006 22:20:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/09/24/officer-titles/#comment-807</guid>
		<description>When the word is preceded by the article &#039;the&#039; it does not appear to be used as a title of a particular person, but rather to point the office.  So, unless it was a defined term from elsewhere in the agreement, it seems natural to go without a capital.

As for examples where the long-title issue arises, it seems hard to come up with a practical one that is not as in the above -- Stating what so-and-so&#039;s title will be now that so-and-so has accepted the job.

Speaking of &#039;the&#039; -- Is it fair to complain about a contract that creates a defined term for one of the parties that is also a generic for the role of the party in the contract, such as &#039;Customer,&#039; and then goes on to put &#039;the&#039; in front of the defined term for the party?  That seems to me to be saying something like, &quot;I was speaking to the Ken Adams the other day, and he said...&quot;</description>
		<content:encoded><![CDATA[<p>When the word is preceded by the article &#8216;the&#8217; it does not appear to be used as a title of a particular person, but rather to point the office.  So, unless it was a defined term from elsewhere in the agreement, it seems natural to go without a capital.</p>
<p>As for examples where the long-title issue arises, it seems hard to come up with a practical one that is not as in the above &#8212; Stating what so-and-so&#8217;s title will be now that so-and-so has accepted the job.</p>
<p>Speaking of &#8216;the&#8217; &#8212; Is it fair to complain about a contract that creates a defined term for one of the parties that is also a generic for the role of the party in the contract, such as &#8216;Customer,&#8217; and then goes on to put &#8216;the&#8217; in front of the defined term for the party?  That seems to me to be saying something like, &#8220;I was speaking to the Ken Adams the other day, and he said&#8230;&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

