<?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"
	>
<channel>
	<title>Comments on: Web Data: Randomly Erratically Variably Unpredictably Incomplete?</title>
	<atom:link href="http://blog.jimnovo.com/2007/10/25/randomly-incomplete/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jimnovo.com/2007/10/25/randomly-incomplete/</link>
	<description>Moving from a Low Accountability to a High Accountability Business Model</description>
	<pubDate>Tue,  6 Jan 2009 14:17:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Steve</title>
		<link>http://blog.jimnovo.com/2007/10/25/randomly-incomplete/#comment-8794</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Wed, 07 Nov 2007 01:08:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jimnovo.com/2007/10/25/randomly-incomplete/#comment-8794</guid>
		<description>Sorry for delay. Been meaning to write. Best intentions etc. :-(

Unpredictably works for me. I remain unconvinced we (at some point in the future?) can't predict and deal with this in some sort of model. But we certainly can't right here and now.

As I mentioned in my email you quoted. :-) I stayed away from the double negatives, but ... well... best of a bad bunch?
Cheers!
- Steve</description>
		<content:encoded><![CDATA[<p>Sorry for delay. Been meaning to write. Best intentions etc. :-(</p>
<p>Unpredictably works for me. I remain unconvinced we (at some point in the future?) can&#8217;t predict and deal with this in some sort of model. But we certainly can&#8217;t right here and now.</p>
<p>As I mentioned in my email you quoted. :-) I stayed away from the double negatives, but &#8230; well&#8230; best of a bad bunch?<br />
Cheers!<br />
- Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Novo</title>
		<link>http://blog.jimnovo.com/2007/10/25/randomly-incomplete/#comment-8331</link>
		<dc:creator>Jim Novo</dc:creator>
		<pubDate>Mon, 29 Oct 2007 23:51:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jimnovo.com/2007/10/25/randomly-incomplete/#comment-8331</guid>
		<description>"And it's not like I've ever seen marketing folk spend weeks arguing over a word or phrase or colour. Heaven forbid! ;-)"

Thanks Steve...

We now have a vote for "Variably" due to "E&lt;font size="2"&gt;rratically&lt;/font&gt;" being too close to "Randomly" in meaning - at least in Australia!

Variably Incomplete is OK, but "Variability" can sometimes be predicted and dealt with in a model.

How about going back to the original premise of modeling not being an answer to this problem, and going with:

Unpredictably Incomplete

What say you Steve?  Anyone else?</description>
		<content:encoded><![CDATA[<p>&#8220;And it&#8217;s not like I&#8217;ve ever seen marketing folk spend weeks arguing over a word or phrase or colour. Heaven forbid! ;-)&#8221;</p>
<p>Thanks Steve&#8230;</p>
<p>We now have a vote for &#8220;Variably&#8221; due to &#8220;E<font size="2">rratically</font>&#8221; being too close to &#8220;Randomly&#8221; in meaning - at least in Australia!</p>
<p>Variably Incomplete is OK, but &#8220;Variability&#8221; can sometimes be predicted and dealt with in a model.</p>
<p>How about going back to the original premise of modeling not being an answer to this problem, and going with:</p>
<p>Unpredictably Incomplete</p>
<p>What say you Steve?  Anyone else?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Novo</title>
		<link>http://blog.jimnovo.com/2007/10/25/randomly-incomplete/#comment-8319</link>
		<dc:creator>Jim Novo</dc:creator>
		<pubDate>Mon, 29 Oct 2007 14:23:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jimnovo.com/2007/10/25/randomly-incomplete/#comment-8319</guid>
		<description>You see, with these technology guys, they are always trying to hold you to a specific definition...and I take it unless the data is truly random by the mathematical definition, "random" is not a satisfactory qualifier.

How about Erratically Incomplete?</description>
		<content:encoded><![CDATA[<p>You see, with these technology guys, they are always trying to hold you to a specific definition&#8230;and I take it unless the data is truly random by the mathematical definition, &#8220;random&#8221; is not a satisfactory qualifier.</p>
<p>How about Erratically Incomplete?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://blog.jimnovo.com/2007/10/25/randomly-incomplete/#comment-8297</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Sun, 28 Oct 2007 21:50:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jimnovo.com/2007/10/25/randomly-incomplete/#comment-8297</guid>
		<description>I respectfully disagree on the "Randomly" part. Rest is spot on.

Why disagree?
Fundamentally the data being incomplete is not random. I've had (way more than...) sufficient exposure to crypto to appreciate the horrendous issues with getting truly random data. 
As for Analytics? There are actual rules and conditions around why the data is incomplete. Cache. Cookies. Javascript woes and so on. It's a highly complex problem with lots of unknowns.

Unknowns != Random! :-)

I would find "incomplete", as a standalone phrase, adequate to the task of explaining the problems. But perhaps another descriptive leader than Randomly may be appropriate? It's too early in the morning here to engage my brain to come up with something else.

Thoughts? Cheers!
- Steve</description>
		<content:encoded><![CDATA[<p>I respectfully disagree on the &#8220;Randomly&#8221; part. Rest is spot on.</p>
<p>Why disagree?<br />
Fundamentally the data being incomplete is not random. I&#8217;ve had (way more than&#8230;) sufficient exposure to crypto to appreciate the horrendous issues with getting truly random data.<br />
As for Analytics? There are actual rules and conditions around why the data is incomplete. Cache. Cookies. Javascript woes and so on. It&#8217;s a highly complex problem with lots of unknowns.</p>
<p>Unknowns != Random! :-)</p>
<p>I would find &#8220;incomplete&#8221;, as a standalone phrase, adequate to the task of explaining the problems. But perhaps another descriptive leader than Randomly may be appropriate? It&#8217;s too early in the morning here to engage my brain to come up with something else.</p>
<p>Thoughts? Cheers!<br />
- Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted</title>
		<link>http://blog.jimnovo.com/2007/10/25/randomly-incomplete/#comment-8242</link>
		<dc:creator>Ted</dc:creator>
		<pubDate>Sat, 27 Oct 2007 14:00:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jimnovo.com/2007/10/25/randomly-incomplete/#comment-8242</guid>
		<description>Great blog.
INCREDIBLE book! Thank you so much!</description>
		<content:encoded><![CDATA[<p>Great blog.<br />
INCREDIBLE book! Thank you so much!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
