<?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: Model Resolution in Palantir Finance: avoiding N2</title>
	<atom:link href="http://blog.palantirtech.com/2009/02/02/model-resolution-in-palantir-finance/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.palantirtech.com/2009/02/02/model-resolution-in-palantir-finance/</link>
	<description>Articles from the Engineering Group at Palantir Technologies</description>
	<lastBuildDate>Mon, 07 Jun 2010 12:21:26 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andy</title>
		<link>http://blog.palantirtech.com/2009/02/02/model-resolution-in-palantir-finance/comment-page-1/#comment-189</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Wed, 08 Apr 2009 21:14:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.palantirtech.com/?p=180#comment-189</guid>
		<description>Hey Ed,
 
You&#039;re correct in that it&#039;s often incorrect to resolve two securities just because they&#039;re associated with the same company.  The actual fields we cited as being resolved on are just examples, and the proper fields to resolve likely depend on what your dataset looks like.  We&#039;ve made the modeling and resolution layer pluggable within our platform, so you can define the properties you wish to resolve on, and the system will act based on what&#039;s been defined.</description>
		<content:encoded><![CDATA[<p>Hey Ed,</p>
<p>You&#8217;re correct in that it&#8217;s often incorrect to resolve two securities just because they&#8217;re associated with the same company.  The actual fields we cited as being resolved on are just examples, and the proper fields to resolve likely depend on what your dataset looks like.  We&#8217;ve made the modeling and resolution layer pluggable within our platform, so you can define the properties you wish to resolve on, and the system will act based on what&#8217;s been defined.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed</title>
		<link>http://blog.palantirtech.com/2009/02/02/model-resolution-in-palantir-finance/comment-page-1/#comment-188</link>
		<dc:creator>Ed</dc:creator>
		<pubDate>Wed, 08 Apr 2009 19:19:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.palantirtech.com/?p=180#comment-188</guid>
		<description>I think you may find that you are missing a layer in your model.  There are companies and there are securities.  A company may have multiple securities.  Price data is a property of a security.  A Balance Sheet is a property of a company.  In your example, Google the company has a balance sheet that it reports for a given fiscal period.  Google&#039;s capital structure may include multiple classes of stock plus preferred stock, warrants, etc. as equity and various bonds and notes as debt instruments.  Each of those securities will have prices that are determined by the exchange (if any) that they trade on.</description>
		<content:encoded><![CDATA[<p>I think you may find that you are missing a layer in your model.  There are companies and there are securities.  A company may have multiple securities.  Price data is a property of a security.  A Balance Sheet is a property of a company.  In your example, Google the company has a balance sheet that it reports for a given fiscal period.  Google&#8217;s capital structure may include multiple classes of stock plus preferred stock, warrants, etc. as equity and various bonds and notes as debt instruments.  Each of those securities will have prices that are determined by the exchange (if any) that they trade on.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
