<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>OregonStatutes.biz</title>
	<atom:link href="http://www.oregonstatutes.biz/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.oregonstatutes.biz</link>
	<description>Legislative Research &#38; Writing</description>
	<lastBuildDate>Sun, 28 Apr 2013 18:24:18 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Synonyms Bolster Court&#8217;s Construction</title>
		<link>http://www.oregonstatutes.biz/uncategorized/court-looks-to-definitions-of-synonyms/</link>
		<comments>http://www.oregonstatutes.biz/uncategorized/court-looks-to-definitions-of-synonyms/#comments</comments>
		<pubDate>Wed, 27 Jun 2012 19:49:53 +0000</pubDate>
		<dc:creator>oregonst</dc:creator>
				<category><![CDATA[uncategorized]]></category>

		<guid isPermaLink="false">http://www.oregonstatutes.biz/?p=1425</guid>
		<description><![CDATA[State v. McBride, 352 Or 159 (2012) Holding:&#160;&#160;&#160;Child endangerment statute makes it illegal to permit a person under 18 to enter or remain in place where unlawful drug activity is occurring. Defendant didn’t own the house, and, the children were the offspring and guest of the person who did, and, Defendant didn’t do anything to [...]]]></description>
				<content:encoded><![CDATA[<p><strong><em>State v. McBride</em>, 352 Or 159 (2012)</strong></p>
<p><em>Holding:</em>&nbsp;&nbsp;&nbsp;Child endangerment statute makes it illegal to permit a person under 18 to enter or remain in place where unlawful drug activity is occurring.  Defendant didn’t own the house, and, the children were the offspring and guest of the person who did, and, Defendant didn’t do anything to affirmatively make the children’s presence possible.  Thus, defendant didn’t permit them to be there, and trial court should have granted motion for acquittal.</p>
<p><strong>1)</strong>&nbsp;&nbsp;&nbsp;“To determine the legislature’s intent * * * we consider the statute’s text, context and legislative history.” <em> citing State v. Gaines.</em>  <em>at p. 164.</em></p>
<p><strong>2)</strong>&nbsp;&nbsp;The commentary to the 1971 overhaul of the criminal code supports the conclusion drawn from examining the text.  <em>at pp. 164-65.</em></p>
<p><strong>3)</strong>&nbsp;&nbsp;Courts will look at the definitions of synonyms to bolster its choice of which definition more closely matches legislative intent.  <em>at p. 166.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.oregonstatutes.biz/uncategorized/court-looks-to-definitions-of-synonyms/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>&#8220;The&#8221; Doesn&#8217;t Always Refer to a Single Thing</title>
		<link>http://www.oregonstatutes.biz/uncategorized/the-doesnt-always-refer-to-a-single-thing/</link>
		<comments>http://www.oregonstatutes.biz/uncategorized/the-doesnt-always-refer-to-a-single-thing/#comments</comments>
		<pubDate>Tue, 26 Jun 2012 20:05:38 +0000</pubDate>
		<dc:creator>oregonst</dc:creator>
				<category><![CDATA[uncategorized]]></category>

		<guid isPermaLink="false">http://www.oregonstatutes.biz/?p=1439</guid>
		<description><![CDATA[SAIF v. DeLeon, 352 Or 130 (2012) Holding:&#160;&#160;&#160;Injured worker received an 11 percent permanent partial disability. SAIF requested a hearing before an administrative law judge (ALJ), who agreed with SAIF and reduced the permanent partial disability to zero. Claimant appealed, and, the Workers’ Comp. Board reinstated the 11 percent award. Claimant allowed attorney fees for [...]]]></description>
				<content:encoded><![CDATA[<p><strong><em>SAIF v. DeLeon</em>, 352 Or 130 (2012)</strong></p>
<p><strong>Holding:</strong>&nbsp;&nbsp;&nbsp;Injured worker received an 11 percent permanent partial disability.   SAIF requested a hearing before an administrative law judge (ALJ), who agreed with SAIF and reduced the permanent partial disability to zero.  Claimant appealed, and, the Workers’ Comp. Board reinstated the 11 percent award.  Claimant allowed attorney fees for efforts before the ALJ, even though she lost, because she was successful on appeal.</p>
<p><strong>1)</strong>&nbsp;&nbsp;The initial examination when construing a statute is the text itself. <em> citing State v. Gaines.</em> <em> at p. 133.</em></p>
<p><strong>2)</strong>&nbsp;&nbsp;&nbsp;Use of definite article “the” does not necessarily rule out the notion that it may take multiple tribunals before the question is resolved.  Here, the use of “the” is grammatically correct either way the statute is interpreted.  <em>at p. 138.</em></p>
<p><strong>3)</strong>&nbsp;&nbsp;Concentration on the tense of the word “be” does not support SAIF’s position.  By changing the way the sentence is constructed, use of the present tense can mean many things. <em> at p. 139.</em></p>
<p><strong>4)</strong>&nbsp;&nbsp;&nbsp;“Legislative inaction in response to a judicial interpretation of a statute does not amount to an endorsement of the court’s interpretation.  <em>at p. 141.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.oregonstatutes.biz/uncategorized/the-doesnt-always-refer-to-a-single-thing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fact That Text is Silent Creates the Ambiguity</title>
		<link>http://www.oregonstatutes.biz/uncategorized/fact-that-text-is-silent-creates-ambiguity/</link>
		<comments>http://www.oregonstatutes.biz/uncategorized/fact-that-text-is-silent-creates-ambiguity/#comments</comments>
		<pubDate>Mon, 25 Jun 2012 20:18:02 +0000</pubDate>
		<dc:creator>oregonst</dc:creator>
				<category><![CDATA[uncategorized]]></category>

		<guid isPermaLink="false">http://www.oregonstatutes.biz/?p=1456</guid>
		<description><![CDATA[Mark Lathan Excavation, Inc. v. Deschutes County, 250 OrApp 543 (2012) Holding:&#160;&#160;&#160;In 1995, County allowed surface mining of a certain property, but neither the “Program to Meet the Goal” (PTMG) nor the assessment of the “Economic, Social, Environmental and Energy” (ESEE) consequences as to the decision expressly addressed mining of a hillside that was part [...]]]></description>
				<content:encoded><![CDATA[<p><strong><em>Mark Lathan Excavation, Inc. v. Deschutes County</em>, 250 OrApp 543 (2012)</strong></p>
<p><strong>Holding:</strong>&nbsp;&nbsp;&nbsp;In 1995, County allowed surface mining of a certain property, but neither the “Program to Meet the Goal” (PTMG) nor the assessment of the “Economic, Social, Environmental and Energy” (ESEE) consequences as to the decision expressly addressed mining of a hillside that was part of the property.  County was correct in requiring a Post Acknowledgment Plan Amendment before the hillside could be mined.</p>
<p><strong>1)</strong>&nbsp;&nbsp;&nbsp;Ambiguity does not require confusion as to the meaning of a particular word or phrase.  Sometimes, fact that the text is silent creates the ambiguity.  <em>at p. 555.</em></p>
<p><strong>2)</strong>&nbsp;&nbsp;&nbsp;Here, the existing ESEE is part of the legislative history, and legislative history may be used “to convince a court that superficially clear language actually is not so plain at all–that is, that there is a kind of latent ambiguity in the statute.”  <em>quoting State v. Gaines.  at p. 556.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.oregonstatutes.biz/uncategorized/fact-that-text-is-silent-creates-ambiguity/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Scope of Preemption Question of Construction</title>
		<link>http://www.oregonstatutes.biz/uncategorized/scope-of-preemption-question-of-construction/</link>
		<comments>http://www.oregonstatutes.biz/uncategorized/scope-of-preemption-question-of-construction/#comments</comments>
		<pubDate>Sun, 24 Jun 2012 20:26:29 +0000</pubDate>
		<dc:creator>oregonst</dc:creator>
				<category><![CDATA[uncategorized]]></category>

		<guid isPermaLink="false">http://www.oregonstatutes.biz/?p=1461</guid>
		<description><![CDATA[Homebuilders Assoc. Of Metro. Portland v. Metro, 250 OrApp 437 (2012) Holding:&#160;&#160;&#160;Metro ordinance extending a construction excise tax and enlarging the uses of that tax revenue did not amount to imposition of a new construction excise tax of the kind prohibited by a 2007 state statute. 1)&#160;&#160;&#160;Staff Measure Summaries are legitimate indicators of legislative intent. [...]]]></description>
				<content:encoded><![CDATA[<p><strong><em>Homebuilders Assoc. Of Metro. Portland v. Metro</em>, 250 OrApp 437 (2012)</strong></p>
<p><strong>Holding:</strong>&nbsp;&nbsp;&nbsp;Metro ordinance extending a construction excise tax and enlarging the uses of that tax revenue did not amount to imposition of a new construction excise tax of the kind prohibited by a 2007 state statute.</p>
<p><strong>1)</strong>&nbsp;&nbsp;&nbsp;Staff Measure Summaries are legitimate indicators of legislative intent.  <em>at p. 443</em>.</p>
<p><strong>2)</strong>&nbsp;&nbsp;&nbsp;The scope of the preemptive effect of a state law is a question of statutory construction, and questions “of statutory construction (are) resolved by resort to the familiar methodology set forth in <em>State v. Gaines</em>, (<em>cite omitted</em>), starting with the statutory text in context.”  <em>at p. 443</em>.</p>
<p><strong>3)</strong>&nbsp;&nbsp;While the general rule is that undefined terms are given their plain and ordinary meanings as shown by contemporary general dictionaries, “the word ‘tax’ is most often used in a legal context.  Thus, we look first to its technical legal meaning.” <em> at p. 444.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.oregonstatutes.biz/uncategorized/scope-of-preemption-question-of-construction/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Parallel Subsections Given Parallel Readings</title>
		<link>http://www.oregonstatutes.biz/uncategorized/parallel-subsections-given-parallel-readings/</link>
		<comments>http://www.oregonstatutes.biz/uncategorized/parallel-subsections-given-parallel-readings/#comments</comments>
		<pubDate>Sat, 23 Jun 2012 20:32:20 +0000</pubDate>
		<dc:creator>oregonst</dc:creator>
				<category><![CDATA[uncategorized]]></category>

		<guid isPermaLink="false">http://www.oregonstatutes.biz/?p=1472</guid>
		<description><![CDATA[State v. Johnson, 250 OrApp 429 (2012) Holding:&#160;&#160;&#160;A blasting cap, still in its commercial packaging and outfitted with a metal shunt to act as a safety, qualified as a bomb within the statute prohibiting unlawful possession of a destructive device. 1)&#160;&#160;&#160;When construing statutes “we examine the text of a statute in context, along with any [...]]]></description>
				<content:encoded><![CDATA[<p><strong><em>State v. Johnson,</em> 250 OrApp 429 (2012)</strong></p>
<p><strong>Holding:</strong>&nbsp;&nbsp;&nbsp;A blasting cap, still in its commercial packaging and outfitted with a metal shunt to act as a safety, qualified as a bomb within the statute prohibiting unlawful possession of a destructive device. </p>
<p><strong>1)</strong>&nbsp;&nbsp;&nbsp;When construing statutes “we examine the text of a statute in context, along with any relevant legislative history, to discern the legislative intent.”  <em>citing State v. Gaines.  at p. 433.</em></p>
<p><strong>2)</strong>&nbsp;&nbsp;Two parallel subsections of the same statute should, typically, be given parallel readings.  <em>at p. 434.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.oregonstatutes.biz/uncategorized/parallel-subsections-given-parallel-readings/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Negative Implication Helps Construe Statute</title>
		<link>http://www.oregonstatutes.biz/uncategorized/negative-implication-helps-construe-statute/</link>
		<comments>http://www.oregonstatutes.biz/uncategorized/negative-implication-helps-construe-statute/#comments</comments>
		<pubDate>Sun, 27 May 2012 00:15:17 +0000</pubDate>
		<dc:creator>oregonst</dc:creator>
				<category><![CDATA[uncategorized]]></category>

		<guid isPermaLink="false">http://www.oregonstatutes.biz/?p=1329</guid>
		<description><![CDATA[State v. McDowell, 352 Or 27 (2012) Holding:&#160;&#160;&#160;Defendant was arrested and held for 236 days. On the day of trial, the Circuit Court dismissed the charges. Several days later, the State reindicted on the same charges and arrested Defendant again. For purposes of the statute limiting pre-trial custody, the clock began running the first time [...]]]></description>
				<content:encoded><![CDATA[<p><strong><strong>State v. McDowell</strong>, 352 Or 27 (2012)</strong></p>
<p><strong>Holding:</strong>&nbsp;&nbsp;&nbsp;Defendant was arrested and held for 236 days.  On the day of trial, the Circuit Court dismissed the charges.  Several days later, the State reindicted on the same charges and arrested Defendant again.  For purposes of the statute limiting pre-trial custody, the clock began running the first time the defendant was arrested.</p>
<p><strong>1)</strong>&nbsp;&nbsp;“Our task is to discern what the legislature contemplated in enacting (the statute), examining the text in context and, where appropriate, legislative history and other aids to construction.”  <em>citing State v. Gaines.  at p. 30</em>.</p>
<p><strong>2)</strong>&nbsp;&nbsp;&nbsp;“Context may include other statutes enacted simultaneously with the statute at issue, (<em>cite omitted</em>), as well as prior versions of the same statute.”  at pp. 30-31.</p>
<p><strong>3)</strong>&nbsp;&nbsp;&nbsp;The statute says that if defendant’s custody is interrupted, the time he or she is not in custody after the interruption must be excluded from the 60-day limit.  “That implies that the time which the defendant was in custody before the interruption <em>does</em> count.”  <em>at p. 32.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.oregonstatutes.biz/uncategorized/negative-implication-helps-construe-statute/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Courts use Standard Method to Construe Rules</title>
		<link>http://www.oregonstatutes.biz/uncategorized/courts-use-standard-method-to-construe-rules/</link>
		<comments>http://www.oregonstatutes.biz/uncategorized/courts-use-standard-method-to-construe-rules/#comments</comments>
		<pubDate>Sat, 26 May 2012 18:23:54 +0000</pubDate>
		<dc:creator>oregonst</dc:creator>
				<category><![CDATA[uncategorized]]></category>

		<guid isPermaLink="false">http://www.oregonstatutes.biz/?p=1336</guid>
		<description><![CDATA[Noble v. Dept. of Fish and Wildlife, 250 OrApp 252 (2012) Holding:&#160;&#160;&#160;The ODFW correctly construed its rule regarding fish passage requirements, and, the rule is consistent with the fish passage statute. 1)&#160;&#160;&#160;Courts employ the same methodology to construe administrative rules as they do to construe statutes. at p. 259. 2)&#160;&#160;&#160;“At the first level of analysis, [...]]]></description>
				<content:encoded><![CDATA[<p><strong><em>Noble v. Dept. of Fish and Wildlife</em>, 250 OrApp 252 (2012)</strong></p>
<p><strong>Holding:</strong>&nbsp;&nbsp;&nbsp;The ODFW correctly construed its rule regarding fish passage requirements, and, the rule is consistent with the fish passage statute.</p>
<p><strong>1)</strong>&nbsp;&nbsp;&nbsp;Courts employ the same methodology to construe administrative rules as they do to construe statutes.  <em>at p. 259</em>.</p>
<p><strong>2)</strong>&nbsp;&nbsp;&nbsp;“At the first level of analysis, we examine the text and context of the rule to discern the intent of the agency (<em>cite omitted</em>).”  <em>at p. 259.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.oregonstatutes.biz/uncategorized/courts-use-standard-method-to-construe-rules/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Words Given Plain and Ordinary Meaning</title>
		<link>http://www.oregonstatutes.biz/uncategorized/referral-enacted-as-of-original-council-action/</link>
		<comments>http://www.oregonstatutes.biz/uncategorized/referral-enacted-as-of-original-council-action/#comments</comments>
		<pubDate>Fri, 25 May 2012 18:35:49 +0000</pubDate>
		<dc:creator>oregonst</dc:creator>
				<category><![CDATA[uncategorized]]></category>

		<guid isPermaLink="false">http://www.oregonstatutes.biz/?p=1402</guid>
		<description><![CDATA[American Energy, Inc. v. City of Sisters, 250 OrApp 243 (2012) Holding:&#160;&#160;&#160;City ordinance imposing a local fuel tax was enacted the day it was approved by the city council, not the day is was subsequently approved by the people at a citizen referendum election. 1)&#160;&#160;&#160;“We (construe statutes) by examining the text of a statute in [...]]]></description>
				<content:encoded><![CDATA[<p><strong><em>American Energy, Inc. v. City of Sisters</em>, 250 OrApp 243 (2012)</strong></p>
<p><strong>Holding:</strong>&nbsp;&nbsp;&nbsp;City ordinance imposing a local fuel tax was enacted the day it was approved by the city council, not the day is was subsequently approved by the people at a citizen referendum election.</p>
<p><strong>1)</strong>&nbsp;&nbsp;&nbsp;“We (construe statutes) by examining the text of a statute in context, along with any relevant legislative history, to discern the legislative intent.”  <em>citing State v. Gaines.  at p. 247.</em></p>
<p><strong>2)</strong>&nbsp;&nbsp;&nbsp;Where there is no statutory definition, Courts give common words their “plain and ordinary” meaning, and consult contemporary dictionaries to divine what is plain and ordinary.  <em>citing PGE v. BOLI, at p. 247.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.oregonstatutes.biz/uncategorized/referral-enacted-as-of-original-council-action/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>&#8220;Or&#8221; Implies Phrases Mean Different Things</title>
		<link>http://www.oregonstatutes.biz/uncategorized/use-of-word-or-implies-phrases-are-different/</link>
		<comments>http://www.oregonstatutes.biz/uncategorized/use-of-word-or-implies-phrases-are-different/#comments</comments>
		<pubDate>Thu, 24 May 2012 19:05:03 +0000</pubDate>
		<dc:creator>oregonst</dc:creator>
				<category><![CDATA[uncategorized]]></category>

		<guid isPermaLink="false">http://www.oregonstatutes.biz/?p=1410</guid>
		<description><![CDATA[Blachana, LLC v. Bureau of Labor and Industries, 250 OrApp 80 (2012) Holding:&#160;&#160;&#160;BOLI erred in finding that Blachana, which operated a restaurant and bar, was a “successor to the business” of NW Sportsbar, and, therefore, liable for wage claims brought against the former business. 1)&#160;&#160;“(W)e determine the legislature’s intended meaning of the relevant statutory text [...]]]></description>
				<content:encoded><![CDATA[<p><strong><em>Blachana, LLC v. Bureau of Labor and Industries</em>, 250 OrApp 80 (2012)</strong></p>
<p><strong>Holding:</strong>&nbsp;&nbsp;&nbsp;BOLI erred in finding that Blachana, which operated a restaurant and bar, was a “successor to the business” of NW Sportsbar, and, therefore, liable for wage claims brought against the former business.</p>
<p><strong>1)</strong>&nbsp;&nbsp;“(W)e determine the legislature’s intended meaning of the relevant statutory text (<em>cite omitted</em>) by examining the text and context of the statute, including any relevant legislative history, and, if ambiguity remains after that examination, resorting to applicable statutory construction canons.”  <em>citing State v. Gaines.  at p. 85.</em></p>
<p><strong>2)</strong>&nbsp;&nbsp;&nbsp;Courts give statutory terms their “plain, natural, and ordinary meaning unless the text  or context indicates that another meaning was intended.”  <em>at p. 86.</em></p>
<p><strong>3)</strong>&nbsp;&nbsp;&nbsp;“We give words that have well-defined legal meaning those meanings.”  <em>at p. 86.</em></p>
<p><strong>4)</strong>&nbsp;&nbsp;&nbsp;If there are no statutory definitions provided, Courts “look to definitions from dictionaries <strong><em>in use at the time</em></strong> the statute was enacted  * * *.”  <em>at p. 86.</em></p>
<p><strong>5)</strong>&nbsp;&nbsp;Legislature’s use of the word “or” suggests that the lawmakers intended that the two clauses contained in the sentence are “intended to be disjunctive and distinctive.”  If the Court concludes that this is so, it should avoid an interpretation that renders the clauses repetitive. <em> at pp. 87-88.</em></p>
<p><strong>6)</strong>&nbsp;&nbsp;The common law “sometimes is helpful in providing a backdrop against which the statute was enacted.” <em> at p. 88.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.oregonstatutes.biz/uncategorized/use-of-word-or-implies-phrases-are-different/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Semantic Differences Sometimes Unimportant</title>
		<link>http://www.oregonstatutes.biz/uncategorized/semantic-differences-still-interchangeable/</link>
		<comments>http://www.oregonstatutes.biz/uncategorized/semantic-differences-still-interchangeable/#comments</comments>
		<pubDate>Fri, 27 Apr 2012 19:44:16 +0000</pubDate>
		<dc:creator>oregonst</dc:creator>
				<category><![CDATA[uncategorized]]></category>

		<guid isPermaLink="false">http://www.oregonstatutes.biz/?p=1266</guid>
		<description><![CDATA[State v. Miskell/Sinibaldi, 351 Or 680 (2012) Holding:&#160;&#160;&#160;Statutory phrase “circumstances * * * [that] are of such exigency that it would be unreasonable to obtain a court order,” given the legislative history, sought to convey the same requirements as the phrase “exigent circumstances.” 1)&#160;&#160;&#160;Fact that the legislature allowed police greater leeway when investigating certain crimes [...]]]></description>
				<content:encoded><![CDATA[<p><strong><em>State v. Miskell/Sinibaldi</em>, 351 Or 680 (2012)</strong></p>
<p><strong>Holding:</strong>&nbsp;&nbsp;&nbsp;Statutory phrase “circumstances * * * [that] are of such exigency that it would be unreasonable to obtain a court order,” given the legislative history, sought to convey the same requirements as the phrase “exigent circumstances.”</p>
<p><strong>1)</strong>&nbsp;&nbsp;&nbsp;Fact that the legislature allowed police greater leeway when investigating certain crimes does not logically foreclose the possibility that the lawmakers intended the more-stringent standard to apply to other types of crime.  <em> at p. 692.</em></p>
<p><strong>2)</strong>&nbsp;&nbsp;Even though the case could “most likely” be resolved by examining the “text and context” alone, the Court may consider the statute’s legislative history, when such “history is useful to the court’s analysis.”  <em>at p. 692-93.</em></p>
<p><strong>3)</strong>&nbsp;&nbsp;&nbsp;The legislative history dating back decades shows that the lawmakers “understood the phrases to be interchangeable,” even though the two phrases are semantically different. <em>at p. 693.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.oregonstatutes.biz/uncategorized/semantic-differences-still-interchangeable/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
