<?xml version="1.0" encoding="iso-8859-1" ?>
<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:content="http://purl.org/rss/1.0/modules/content/"
 xmlns:wfw="http://wellformedweb.org/CommentAPI/">
<channel><title>Chris Doig's Blog | Comments</title><description>Collaboration, IT Management and more...</description><link>http://chrisdoig.net/chrisdoig/chrisdoig.nsf/</link><language>en-us</language><lastBuildDate>Tue, 11 May 2010 05:52:15 AM -0500</lastBuildDate>
<item>
<title>Missing keystrokes problem.</title>
<pubDate>Tue, 11 May 2010 05:52:15 AM -0500</pubDate>
<dc:creator>saç ekimi</dc:creator>
<dc:subject>Missing keystrokes problem.</dc:subject>
<description><![CDATA[Hi;<br /><br />Unfortunately, although I realize I could not read the topic defalrca to help me in this regard would be glad if the mail.<br /><br />mary lou<br /><br />marylou23@gmail.com<br /><br />{ <a href="http://www.nakliyatfirmalari.org" target="_blank" title="Link: www.nakliyatfirmalari.org">Link</a> }]]></description>
<content:encoded><![CDATA[Hi;<br /><br />Unfortunately, although I realize I could not read the topic defalrca to help me in this regard would be glad if the mail.<br /><br />mary lou<br /><br />marylou23@gmail.com<br /><br />{ <a href="http://www.nakliyatfirmalari.org" target="_blank" title="Link: www.nakliyatfirmalari.org">Link</a> }]]></content:encoded>
<link>http://chrisdoig.net/chrisdoig/chrisdoig.nsf//dx/12172005015052PMCDOTMD.htm?opendocument&amp;comments#11.05.2010055215HOSERQ.htm</link>
</item>
<item>
<title>Using categories to tame your in-box.</title>
<pubDate>Tue, 12 Jan 2010 05:18:01 AM -0500</pubDate>
<dc:creator>sander</dc:creator>
<dc:subject>Using categories to tame your in-box.</dc:subject>
<description><![CDATA[{ <a href="http://www.google.com" target="_blank" title="Link: www.google.com">Link</a> }]]></description>
<content:encoded><![CDATA[{ <a href="http://www.google.com" target="_blank" title="Link: www.google.com">Link</a> }]]></content:encoded>
<link>http://chrisdoig.net/chrisdoig/chrisdoig.nsf//dx/09122005081233PMCDO5SF.htm?opendocument&amp;comments#12.01.2010051801HOSF9X.htm</link>
</item>
<item>
<title>DocMaster 4.2.14 Released</title>
<pubDate>Thu, 19 Mar 2009 12:17:48 AM -0500</pubDate>
<dc:creator>Yavo</dc:creator>
<dc:subject>DocMaster 4.2.14 Released</dc:subject>
<description><![CDATA[Good work!<br /><br />There is only one thing. When I update the Help file and restart the application, the Sarbanes Oxley folder disappears. Is there a work around?]]></description>
<content:encoded><![CDATA[Good work!<br /><br />There is only one thing. When I update the Help file and restart the application, the Sarbanes Oxley folder disappears. Is there a work around?]]></content:encoded>
<link>http://chrisdoig.net/chrisdoig/chrisdoig.nsf//dx/06042008122721PMCDOQTP.htm?opendocument&amp;comments#03192009121748AMHOS88P.htm</link>
</item>
<item>
<title>New version of DocMaster: 4.2.x</title>
<pubDate>Fri, 12 Dec 2008 07:06:00 AM -0500</pubDate>
<dc:creator>Zafar Shaikh</dc:creator>
<dc:subject>New version of DocMaster: 4.2.x</dc:subject>
<description><![CDATA[HI i need the latest version of DocMaster.<br /><br />Can you please send it to me.<br /><br />Thanks & Regards,<br /><br />Zafar Shaikh]]></description>
<content:encoded><![CDATA[HI i need the latest version of DocMaster.<br /><br />Can you please send it to me.<br /><br />Thanks & Regards,<br /><br />Zafar Shaikh]]></content:encoded>
<link>http://chrisdoig.net/chrisdoig/chrisdoig.nsf//dx/06022008064724PMCDO458.htm?opendocument&amp;comments#12122008070600AMHOSHDB.htm</link>
</item>
<item>
<title>New version of DocMaster: 4.2.x</title>
<pubDate>Mon, 22 Sep 2008 08:32:01 PM -0500</pubDate>
<dc:creator>Dale Flannery</dc:creator>
<dc:subject>New version of DocMaster: 4.2.x</dc:subject>
<description><![CDATA[Hi Chris<br /><br />&gt;&gt; attachments to come June 4th<br /><br />June of which year? :-P<br /><br />Cheers<br /><br />Dale]]></description>
<content:encoded><![CDATA[Hi Chris<br /><br />&gt;&gt; attachments to come June 4th<br /><br />June of which year? :-P<br /><br />Cheers<br /><br />Dale]]></content:encoded>
<link>http://chrisdoig.net/chrisdoig/chrisdoig.nsf//dx/06022008064724PMCDO458.htm?opendocument&amp;comments#09222008083201PMHOS3TQ.htm</link>
</item>
<item>
<title>You may be right...</title>
<pubDate>Sun, 8 Jun 2008 06:16:58 PM -0500</pubDate>
<dc:creator>Philip Storry</dc:creator>
<dc:subject>A Thought on SharePoint as File Server 2.0</dc:subject>
<description><![CDATA[Officially, it was pulled because it was too slow and it had scaling issues - it was practically useless for network usage. (Or so I heard.)<br /><br />In that latter use case, SharePoint is a better alternative to WinFS anyway. It also has scaling issues, but at least they're a little easier to handle because you usually "segment" your SharePoint apps into per-department or per-project sets anyway, which makes capacity handling somewhate easier than if it was a filesystem (local or networked).<br /><br />In essence, I suspect that their first issue was support. Call it a filesystem, and people will expect NTFS speed and scalability - local or networked.<br /><br />The fact that canning it allows them to sell SharePoint is merely convenient compared to how much money and face it saved them if they'd shipped it.<br /><br />That having been said, the WinFS work was apparently rolled back into SQL Server, and lies with them now. So I do expect to see SharePoint being the end recipient of WinFS work, albeit now requiring two sets of licenses rather than just one.]]></description>
<content:encoded><![CDATA[Officially, it was pulled because it was too slow and it had scaling issues - it was practically useless for network usage. (Or so I heard.)<br /><br />In that latter use case, SharePoint is a better alternative to WinFS anyway. It also has scaling issues, but at least they're a little easier to handle because you usually "segment" your SharePoint apps into per-department or per-project sets anyway, which makes capacity handling somewhate easier than if it was a filesystem (local or networked).<br /><br />In essence, I suspect that their first issue was support. Call it a filesystem, and people will expect NTFS speed and scalability - local or networked.<br /><br />The fact that canning it allows them to sell SharePoint is merely convenient compared to how much money and face it saved them if they'd shipped it.<br /><br />That having been said, the WinFS work was apparently rolled back into SQL Server, and lies with them now. So I do expect to see SharePoint being the end recipient of WinFS work, albeit now requiring two sets of licenses rather than just one.]]></content:encoded>
<link>http://chrisdoig.net/chrisdoig/chrisdoig.nsf//dx/06062008122221PMCDOQQK.htm?opendocument&amp;comments#08062008181658HOSVB6.htm</link>
</item>
<item>
<title>Version 4.2.x coming</title>
<pubDate>Thu, 29 May 2008 09:41:06 AM -0700</pubDate>
<dc:creator>Chris Doig</dc:creator>
<dc:subject>New version of DocMaster: 4.1.9</dc:subject>
<description><![CDATA[Hi James, I am working on version 4.2.2 - just cleaning out a few minor bugs before posting it. Two new features have been added in version 4.2: 1) Document Issues and associated workflow 2) Sarbanes Oxley documents, workflows etc. I have also partially updated the help to include these features. I expect to post a version in the next few days - probably early next week.]]></description>
<content:encoded><![CDATA[Hi James, I am working on version 4.2.2 - just cleaning out a few minor bugs before posting it. Two new features have been added in version 4.2: 1) Document Issues and associated workflow 2) Sarbanes Oxley documents, workflows etc. I have also partially updated the help to include these features. I expect to post a version in the next few days - probably early next week.]]></content:encoded>
<link>http://chrisdoig.net/chrisdoig/chrisdoig.nsf//dx/02212007075159PMCDO32L.htm?opendocument&amp;comments#05292008094106AMCDOMKT.htm</link>
</item>
<item>
<title>DocMaster 4.1.9</title>
<pubDate>Thu, 29 May 2008 08:47:48 AM -0500</pubDate>
<dc:creator>james</dc:creator>
<dc:subject>New version of DocMaster: 4.1.9</dc:subject>
<description><![CDATA[Hi Chris<br /><br />I was hoping to find a downloadable version of 4.1.9 but could only find version 4.0.82. <br /><br />Is that intentional or am I missing something?<br /><br />james]]></description>
<content:encoded><![CDATA[Hi Chris<br /><br />I was hoping to find a downloadable version of 4.1.9 but could only find version 4.0.82. <br /><br />Is that intentional or am I missing something?<br /><br />james]]></content:encoded>
<link>http://chrisdoig.net/chrisdoig/chrisdoig.nsf//dx/02212007075159PMCDO32L.htm?opendocument&amp;comments#05292008084748AMHOSJ7F.htm</link>
</item>
<item>
<title>More Excel Woes</title>
<pubDate>Thu, 29 May 2008 08:05:01 AM -0500</pubDate>
<dc:creator>Palmi</dc:creator>
<dc:subject>More Excel Woes!</dc:subject>
<description><![CDATA[Chris - I hope that Symphony 1.0 is going to have support for Lotus123. MS Office 2007 (Security patch) disables the save of WK4 format.]]></description>
<content:encoded><![CDATA[Chris - I hope that Symphony 1.0 is going to have support for Lotus123. MS Office 2007 (Security patch) disables the save of WK4 format.]]></content:encoded>
<link>http://chrisdoig.net/chrisdoig/chrisdoig.nsf//dx/05282008044109PMCDOVSB.htm?opendocument&amp;comments#05292008080501AMHOSHCP.htm</link>
</item>
<item>
<title>Thanks for the input...</title>
<pubDate>Sat, 26 Apr 2008 10:10:29 AM -0700</pubDate>
<dc:creator>Chris Doig</dc:creator>
<dc:subject>Excel 2007 can&#8217;t open Lotus 123 spreadsheets</dc:subject>
<description><![CDATA[Kevin, thanks for that input - I'll take a look when I get a chance.<br /><br />Chris.]]></description>
<content:encoded><![CDATA[Kevin, thanks for that input - I'll take a look when I get a chance.<br /><br />Chris.]]></content:encoded>
<link>http://chrisdoig.net/chrisdoig/chrisdoig.nsf//dx/04222008033527PMCDOUH8.htm?opendocument&amp;comments#04262008101029AMCDON65.htm</link>
</item>
<item>
<title>SuperNTF has nice and simple Excel export tools</title>
<pubDate>Wed, 23 Apr 2008 01:48:26 PM -0500</pubDate>
<dc:creator>Kevin Pettitt</dc:creator>
<dc:subject>Excel 2007 can&#8217;t open Lotus 123 spreadsheets</dc:subject>
<description><![CDATA[Hi Chris,<br /><br />While I agree the lack of native support for excel exports in Notes is kinda silly, I've been getting along quite well with a couple of simple exports agents I blogged about here: { <a href="http://www.lotusguru.com/lotusguru/LGBlog.nsf/d6plinks/KPET-6ZGL9L" target="_blank" title="Link: www.lotusguru.com/lotusguru/LGBlog.nsf/d6plinks/KPET-6ZGL9L">Link</a> }<br /><br />Those are now a standard component of my SuperNTF framework { <a href="http://www.superntf.org " target="_blank" title="Link: www.superntf.org ">Link</a> } which also incorporates the ASND Export Facility from OpenNTF, which allows for the creation of reusable report definitions.<br /><br />hth]]></description>
<content:encoded><![CDATA[Hi Chris,<br /><br />While I agree the lack of native support for excel exports in Notes is kinda silly, I've been getting along quite well with a couple of simple exports agents I blogged about here: { <a href="http://www.lotusguru.com/lotusguru/LGBlog.nsf/d6plinks/KPET-6ZGL9L" target="_blank" title="Link: www.lotusguru.com/lotusguru/LGBlog.nsf/d6plinks/KPET-6ZGL9L">Link</a> }<br /><br />Those are now a standard component of my SuperNTF framework { <a href="http://www.superntf.org " target="_blank" title="Link: www.superntf.org ">Link</a> } which also incorporates the ASND Export Facility from OpenNTF, which allows for the creation of reusable report definitions.<br /><br />hth]]></content:encoded>
<link>http://chrisdoig.net/chrisdoig/chrisdoig.nsf//dx/04222008033527PMCDOUH8.htm?opendocument&amp;comments#04232008014826PMHOSQ3D.htm</link>
</item>
<item>
<title>This behavior is not what I would expect...</title>
<pubDate>Tue, 22 Apr 2008 03:34:10 PM -0700</pubDate>
<dc:creator>Chris Doig</dc:creator>
<dc:subject>Outlook 2007 Calendar Bug</dc:subject>
<description><![CDATA[Even if it is working as designed, its now what I would expect as a user. From a UI perspective I would say that it is broken.]]></description>
<content:encoded><![CDATA[Even if it is working as designed, its now what I would expect as a user. From a UI perspective I would say that it is broken.]]></content:encoded>
<link>http://chrisdoig.net/chrisdoig/chrisdoig.nsf//dx/03142008034835PMCDOURF.htm?opendocument&amp;comments#04222008033410PMCDOUGG.htm</link>
</item>
<item>
<title>&quot;Working As Designed&quot;</title>
<pubDate>Sun, 30 Mar 2008 11:11:12 AM -0500</pubDate>
<dc:creator>Philip Storry</dc:creator>
<dc:subject>Outlook 2007 Calendar Bug</dc:subject>
<description><![CDATA[I strongly suspect that this is working as designed.<br /><br />IIRC, Outlook uses an embedded copy of Word as its editor/renderer for emails, but probably doesn't use the same editor for calendar entries.<br /><br />That would certainly explain this behaviour, anyway...]]></description>
<content:encoded><![CDATA[I strongly suspect that this is working as designed.<br /><br />IIRC, Outlook uses an embedded copy of Word as its editor/renderer for emails, but probably doesn't use the same editor for calendar entries.<br /><br />That would certainly explain this behaviour, anyway...]]></content:encoded>
<link>http://chrisdoig.net/chrisdoig/chrisdoig.nsf//dx/03142008034835PMCDOURF.htm?opendocument&amp;comments#30032008111112HOSLZ3.htm</link>
</item>
<item>
<title>Missing keystrokes problem.</title>
<pubDate>Sun, 12 Aug 2007 05:22:28 PM -0500</pubDate>
<dc:creator>Theron Price</dc:creator>
<dc:subject>Missing keystrokes problem.</dc:subject>
<description><![CDATA[There is also a very common virus that will drop keystrokes. It is very hard to remove. I had to reformat my Harddrive and reinstall windows.]]></description>
<content:encoded><![CDATA[There is also a very common virus that will drop keystrokes. It is very hard to remove. I had to reformat my Harddrive and reinstall windows.]]></content:encoded>
<link>http://chrisdoig.net/chrisdoig/chrisdoig.nsf//dx/12172005015052PMCDOTMD.htm?opendocument&amp;comments#08122007052228PMHOSU94.htm</link>
</item>
<item>
<title>Template Build Number</title>
<pubDate>Thu, 8 Jun 2006 11:05:21 PM -0500</pubDate>
<dc:creator>Chad Schelfhout</dc:creator>
<dc:subject>Using Version Numbers to Manage Database Designs</dc:subject>
<description><![CDATA[Chris some discussion has been going on about using this application and a web service at { <a href="http://openNTF.org " title="Link: openNTF.org ">Link</a> } to determine if there any updates available. The only issue is the template version can not be used to determine if an update is available because it is text, so a number field should be used. Check out the discussion and the recommended solution here: { <a href="http://chadsmiley.com/chadsmiley/home.nsf/d6plinks/CHAY-6QL6BM " title="Link: chadsmiley.com/chadsmiley/home.nsf/d6plinks/CHAY-6QL6BM ">Link</a> } <br /><br />Please let me know your thoughts.]]></description>
<content:encoded><![CDATA[Chris some discussion has been going on about using this application and a web service at { <a href="http://openNTF.org " title="Link: openNTF.org ">Link</a> } to determine if there any updates available. The only issue is the template version can not be used to determine if an update is available because it is text, so a number field should be used. Check out the discussion and the recommended solution here: { <a href="http://chadsmiley.com/chadsmiley/home.nsf/d6plinks/CHAY-6QL6BM " title="Link: chadsmiley.com/chadsmiley/home.nsf/d6plinks/CHAY-6QL6BM ">Link</a> } <br /><br />Please let me know your thoughts.]]></content:encoded>
<link>http://chrisdoig.net/dx/08062005080427AMCDOKPD.htm?opendocument&amp;comments#06082006110521PMHOS6TE.htm</link>
</item>
<item>
<title>Can you supply some examples?</title>
<pubDate>Thu, 1 Jun 2006 09:54:15 PM -0700</pubDate>
<dc:creator>Chris Doig</dc:creator>
<dc:subject>Reusability with Standards</dc:subject>
<description><![CDATA[Dan, thanks for your comments. But can you supply a few examples of "standards that address problems that rarely if ever occur". Bear in mind that I am not thinking of a highly regulated environment like the nuclear industry, but rather the context is more in the common corporate IT environment. What is the point of having a standard if it does not solve a problem? My thoughts are to use whatever is available out there, open source or anything else. There is no point in re-inventing the wheel when you can easily go and get one with much less effort. <br /><br />If a standard isn't documented it is not a standard. The idea is that you select the standards that matter to you, and document them. Then everybody who needs to use the standard knows where to find it, and can use it. What it is, is almost immaterial. What is important is that it is written down, and everybody is held accountable to it. <br /><br />With reference to your comment on exception handling - I quite agree. I'm not proposing everything be written down. Every system has an edge, you mst select a reasonable edge when you start. Rather start off with the basics, and work from there. Pilot your approach. Oh - and also provide the means for people to suggest improvements to standards so they can be continuously refined. No one person can think of everything - the more you get the team to pool their expertise, the better results you will have. And this gets standard development out of the ivory tower and into the real world.]]></description>
<content:encoded><![CDATA[Dan, thanks for your comments. But can you supply a few examples of "standards that address problems that rarely if ever occur". Bear in mind that I am not thinking of a highly regulated environment like the nuclear industry, but rather the context is more in the common corporate IT environment. What is the point of having a standard if it does not solve a problem? My thoughts are to use whatever is available out there, open source or anything else. There is no point in re-inventing the wheel when you can easily go and get one with much less effort. <br /><br />If a standard isn't documented it is not a standard. The idea is that you select the standards that matter to you, and document them. Then everybody who needs to use the standard knows where to find it, and can use it. What it is, is almost immaterial. What is important is that it is written down, and everybody is held accountable to it. <br /><br />With reference to your comment on exception handling - I quite agree. I'm not proposing everything be written down. Every system has an edge, you mst select a reasonable edge when you start. Rather start off with the basics, and work from there. Pilot your approach. Oh - and also provide the means for people to suggest improvements to standards so they can be continuously refined. No one person can think of everything - the more you get the team to pool their expertise, the better results you will have. And this gets standard development out of the ivory tower and into the real world.]]></content:encoded>
<link>http://chrisdoig.net/dx/05082006104721AMCDONV7.htm?opendocument&amp;comments#06012006095415PMCDO7RZ.htm</link>
</item>
<item>
<title>Solving real problems vs potential problems</title>
<pubDate>Thu, 1 Jun 2006 11:15:06 PM -0500</pubDate>
<dc:creator>Dan Sickles</dc:creator>
<dc:subject>Reusability with Standards</dc:subject>
<description><![CDATA[Chris, I agree about cost savings and re-use. There is a risk management aspect to it that plys a big role in highly regulated environments.<br /><br />But there are problems. The phrase "to solve recurring problems" is key. Some standards address problems that rarely if ever occur. Rather than applying these stanrds as normal practice, perhaps they could be invoked in exceptional cases. The geek in me can't help but make the obvious code analogy. With exception handling, the normal case is concise, readable and efficient, unecumbered by code that defends against what likely will not happen while code for the exceptional case lives in it's own place ready to be invoked on the rare occasion.<br /><br />For problems that are truly recurring, we have many conventions, best practices, techniques, language features and tools to help and be re-used. This is why I prefer emergent standards such as XP to those that feel like they were conceived in an ivory tower and imposed on, rather than adapted to, IT organizations.]]></description>
<content:encoded><![CDATA[Chris, I agree about cost savings and re-use. There is a risk management aspect to it that plys a big role in highly regulated environments.<br /><br />But there are problems. The phrase "to solve recurring problems" is key. Some standards address problems that rarely if ever occur. Rather than applying these stanrds as normal practice, perhaps they could be invoked in exceptional cases. The geek in me can't help but make the obvious code analogy. With exception handling, the normal case is concise, readable and efficient, unecumbered by code that defends against what likely will not happen while code for the exceptional case lives in it's own place ready to be invoked on the rare occasion.<br /><br />For problems that are truly recurring, we have many conventions, best practices, techniques, language features and tools to help and be re-used. This is why I prefer emergent standards such as XP to those that feel like they were conceived in an ivory tower and imposed on, rather than adapted to, IT organizations.]]></content:encoded>
<link>http://chrisdoig.net/dx/05082006104721AMCDONV7.htm?opendocument&amp;comments#06012006111506PMHOS6ZH.htm</link>
</item>
<item>
<title>This is absolutely brilliant</title>
<pubDate>Tue, 9 May 2006 07:47:58 AM -0500</pubDate>
<dc:creator>Dave Conradie</dc:creator>
<dc:subject>Drill Down Views in Notes</dc:subject>
<description><![CDATA[Chris - you just saved me a huge bunch of time and effort with this posting, it couldn't have appeared at a better time. I'm currently two weeks late on a project which has its first review tomorrow - errm, better make that "later today"... - and your post has just enabled me to drop in some cool & handy functionality to make the project look closer to completion than it was 15 minutes ago. Magic - many thanks.]]></description>
<content:encoded><![CDATA[Chris - you just saved me a huge bunch of time and effort with this posting, it couldn't have appeared at a better time. I'm currently two weeks late on a project which has its first review tomorrow - errm, better make that "later today"... - and your post has just enabled me to drop in some cool & handy functionality to make the project look closer to completion than it was 15 minutes ago. Magic - many thanks.]]></content:encoded>
<link>http://chrisdoig.net/dx/03292006063740AMCDOK6M.htm?opendocument&amp;comments#05092006074758AMHOSH22.htm</link>
</item>
<item>
<title>I&#180;ll describe the technique used to create the drill down view.</title>
<pubDate>Wed, 8 Mar 2006 08:09:18 PM -0700</pubDate>
<dc:creator>Chris Doig</dc:creator>
<dc:subject>IT Management failures</dc:subject>
<description><![CDATA[Scott, the technique used is based on an article in the View some years back. It uses a little known trick to fool the view into thinking documents are responses when they are not. I'll write up the details an post an example of the code in the near future.]]></description>
<content:encoded><![CDATA[Scott, the technique used is based on an article in the View some years back. It uses a little known trick to fool the view into thinking documents are responses when they are not. I'll write up the details an post an example of the code in the near future.]]></content:encoded>
<link>http://chrisdoig.net/dx/03082006015538AMCDODND.htm?opendocument&amp;comments#03082006080918PMCDO6VW.htm</link>
</item>
<item>
<title>THe same thing will repeat the platform&#180;s not the problem</title>
<pubDate>Wed, 8 Mar 2006 11:56:45 AM -0500</pubDate>
<dc:creator>Brian Benz</dc:creator>
<dc:subject>IT Management failures</dc:subject>
<description><![CDATA[Yep. I wrote about this a year ago, about another similar situation:<br /><br />{ <a href="http://bbenz.typepad.com/softwaresoapbox/2005/01/making_bad_deci.html" title="Link: bbenz.typepad.com/softwaresoapbox/2005/01/making_bad_deci.html">Link</a> }]]></description>
<content:encoded><![CDATA[Yep. I wrote about this a year ago, about another similar situation:<br /><br />{ <a href="http://bbenz.typepad.com/softwaresoapbox/2005/01/making_bad_deci.html" title="Link: bbenz.typepad.com/softwaresoapbox/2005/01/making_bad_deci.html">Link</a> }]]></content:encoded>
<link>http://chrisdoig.net/dx/03082006015538AMCDODND.htm?opendocument&amp;comments#03082006115645AMHOSP32.htm</link>
</item>

</channel></rss>
