<?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: Establishing General Submission Guidelines</title>
	<atom:link href="http://medbloggercode.com/2007/07/24/establishing-general-submission-guidelines/feed/" rel="self" type="application/rss+xml" />
	<link>http://medbloggercode.com/2007/07/24/establishing-general-submission-guidelines/</link>
	<description>Blogging Code for Healthcare Professionals and Patients</description>
	<pubDate>Sat, 06 Sep 2008 01:45:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Roy</title>
		<link>http://medbloggercode.com/2007/07/24/establishing-general-submission-guidelines/#comment-135</link>
		<dc:creator>Roy</dc:creator>
		<pubDate>Mon, 20 Aug 2007 22:41:36 +0000</pubDate>
		<guid isPermaLink="false">http://medbloggercode.com/?p=16#comment-135</guid>
		<description>Thanks, Rob. That's helpful and make sense (except the IP rights bit).  And thanks for fixing the sidebar for us.  Keep up the great work.</description>
		<content:encoded><![CDATA[<p>Thanks, Rob. That&#8217;s helpful and make sense (except the IP rights bit).  And thanks for fixing the sidebar for us.  Keep up the great work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://medbloggercode.com/2007/07/24/establishing-general-submission-guidelines/#comment-127</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Fri, 17 Aug 2007 20:56:08 +0000</pubDate>
		<guid isPermaLink="false">http://medbloggercode.com/?p=16#comment-127</guid>
		<description>Roy:
Check out the "Get the Code For Your Blog" page.  It is the result of this discussion.  The bottom line is that we just want some criteria by which to judge blogs.  This is not the code itself, but a way in which we can exclude blogs that don't meet what we are going after.  If we have commercial sites or sites that are just "link farms", then the code will be meaningless.  I would rather police on the front end than later.

Regarding the HON code (which I mysteriously did qualify for - I guess they like llamas), I feel that the HON code is too exclusive and more oriented toward scientific websites.  Medical bloggers need a way to define the rules by which they are blogging (both for the sake of the blogger and for the reader).  The goal of this code was just to put in writing for bloggers the rules.  It saves us all having to reinvent the wheel for our own blogs.  Most of these things are things we are doing or feel should be done anyhow.

Makes sense?</description>
		<content:encoded><![CDATA[<p>Roy:<br />
Check out the &#8220;Get the Code For Your Blog&#8221; page.  It is the result of this discussion.  The bottom line is that we just want some criteria by which to judge blogs.  This is not the code itself, but a way in which we can exclude blogs that don&#8217;t meet what we are going after.  If we have commercial sites or sites that are just &#8220;link farms&#8221;, then the code will be meaningless.  I would rather police on the front end than later.</p>
<p>Regarding the HON code (which I mysteriously did qualify for - I guess they like llamas), I feel that the HON code is too exclusive and more oriented toward scientific websites.  Medical bloggers need a way to define the rules by which they are blogging (both for the sake of the blogger and for the reader).  The goal of this code was just to put in writing for bloggers the rules.  It saves us all having to reinvent the wheel for our own blogs.  Most of these things are things we are doing or feel should be done anyhow.</p>
<p>Makes sense?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roy</title>
		<link>http://medbloggercode.com/2007/07/24/establishing-general-submission-guidelines/#comment-126</link>
		<dc:creator>Roy</dc:creator>
		<pubDate>Fri, 17 Aug 2007 19:34:54 +0000</pubDate>
		<guid isPermaLink="false">http://medbloggercode.com/?p=16#comment-126</guid>
		<description>I'm a little late to this party, but thought I'd chime in, nontheless.
I agree with 3 months being a minimum, but favor the "AND" over the "OR" regarding # of posts.  Otherwise, I could easily start a blog, churn out 15 posts in the next 2 days, and then be eligible.  And if it is done this way, then maybe use 10 as a minimum.  If someone posts once weekly, in 3 months they'll only have 12.

Must be a "real blog".  How is that defined?

"Active blog":  I suggest operationalizing that definition, such as "Must have at least one post in each of the last 3 months" or "Must have at least one post in the last 35 days."

"Must respect copyright and intellectual property rights."  I am in favor of either getting rid of this or qualifying it in some way.  There is too much room for interpretation.  For example, Rob listed some examples of requirements, without attributing them to specific authors.  Is that respecting rights?  I include song snippets sometimes at the end of our podcasts, with attribution to the artist and links to iTunes or eMusic to buy the song.  We did not get permission.  Is that Fair Use?  Does it respect rights?  I personally feel uncomfortable with the current guideline as written.

Oh, one last thing, is there discussion elsewhere about how this code complements/augments/replaces similar codes, such as HON?  I admire you for taking this on, as it is needed, but I have not spent much time thinking about how such a code protects bloggers.  I do recall looking at HON some time ago and thinking that our blog wouldn't make the cut, though I forget why (might be because of need for full name and next review date, or something similar).

Thanks!</description>
		<content:encoded><![CDATA[<p>I&#8217;m a little late to this party, but thought I&#8217;d chime in, nontheless.<br />
I agree with 3 months being a minimum, but favor the &#8220;AND&#8221; over the &#8220;OR&#8221; regarding # of posts.  Otherwise, I could easily start a blog, churn out 15 posts in the next 2 days, and then be eligible.  And if it is done this way, then maybe use 10 as a minimum.  If someone posts once weekly, in 3 months they&#8217;ll only have 12.</p>
<p>Must be a &#8220;real blog&#8221;.  How is that defined?</p>
<p>&#8220;Active blog&#8221;:  I suggest operationalizing that definition, such as &#8220;Must have at least one post in each of the last 3 months&#8221; or &#8220;Must have at least one post in the last 35 days.&#8221;</p>
<p>&#8220;Must respect copyright and intellectual property rights.&#8221;  I am in favor of either getting rid of this or qualifying it in some way.  There is too much room for interpretation.  For example, Rob listed some examples of requirements, without attributing them to specific authors.  Is that respecting rights?  I include song snippets sometimes at the end of our podcasts, with attribution to the artist and links to iTunes or eMusic to buy the song.  We did not get permission.  Is that Fair Use?  Does it respect rights?  I personally feel uncomfortable with the current guideline as written.</p>
<p>Oh, one last thing, is there discussion elsewhere about how this code complements/augments/replaces similar codes, such as HON?  I admire you for taking this on, as it is needed, but I have not spent much time thinking about how such a code protects bloggers.  I do recall looking at HON some time ago and thinking that our blog wouldn&#8217;t make the cut, though I forget why (might be because of need for full name and next review date, or something similar).</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://medbloggercode.com/2007/07/24/establishing-general-submission-guidelines/#comment-89</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Sat, 28 Jul 2007 18:27:00 +0000</pubDate>
		<guid isPermaLink="false">http://medbloggercode.com/?p=16#comment-89</guid>
		<description>OK:&lt;br/&gt;I agree that there must be clear &lt;i&gt;guidelines&lt;/i&gt; set.  The must, however, only be guidelines.  There will be some exceptions to any rule eventually.  We can say that an English language blog is essential, but what if a blog does part in English and part in French (I have one such person interested already).  With translation tools on browsers, you can at least check to see if the integrity of a blog is consistent with the guidelines.  &lt;br/&gt;&lt;br/&gt;I would certainly say that in general, the blog should have at least 3 months (I wouldn't say 6) and/or 15 posts.  &lt;br/&gt;&lt;br/&gt;The biggest problem for me is the possibility of the code being usurped by people who want to use it for their marketing advantage.  I want this code to be for and by bloggers.&lt;br/&gt;&lt;br/&gt;I also like the idea of featuring a site on a regular basis.  When new bloggers come on board, we can run a post that talks about their blog and what it is about.  This would increase the visibility of the blog and would also increase the visibility of the code, as people go to it to learn about new medical blogs.&lt;br/&gt;&lt;br/&gt;I am very frustrated presently by the limitations of Blogger, however.  I left it for Wordpress on my own blog, and I am starting to wonder if I shouldn't do it with this one as well.  Dean had some very good ideas about ways to enable people applying for right to display the code, but I see no way of doing that in Blogger.</description>
		<content:encoded><![CDATA[<p>OK:<br />I agree that there must be clear <i>guidelines</i> set.  The must, however, only be guidelines.  There will be some exceptions to any rule eventually.  We can say that an English language blog is essential, but what if a blog does part in English and part in French (I have one such person interested already).  With translation tools on browsers, you can at least check to see if the integrity of a blog is consistent with the guidelines.  </p>
<p>I would certainly say that in general, the blog should have at least 3 months (I wouldn&#8217;t say 6) and/or 15 posts.  </p>
<p>The biggest problem for me is the possibility of the code being usurped by people who want to use it for their marketing advantage.  I want this code to be for and by bloggers.</p>
<p>I also like the idea of featuring a site on a regular basis.  When new bloggers come on board, we can run a post that talks about their blog and what it is about.  This would increase the visibility of the blog and would also increase the visibility of the code, as people go to it to learn about new medical blogs.</p>
<p>I am very frustrated presently by the limitations of Blogger, however.  I left it for Wordpress on my own blog, and I am starting to wonder if I shouldn&#8217;t do it with this one as well.  Dean had some very good ideas about ways to enable people applying for right to display the code, but I see no way of doing that in Blogger.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amanda</title>
		<link>http://medbloggercode.com/2007/07/24/establishing-general-submission-guidelines/#comment-86</link>
		<dc:creator>Amanda</dc:creator>
		<pubDate>Fri, 27 Jul 2007 23:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://medbloggercode.com/?p=16#comment-86</guid>
		<description>&lt;i&gt;I'd say that the age of the blog could be a guideline/ number of posts could be an and/ either/ or proposition.&lt;/i&gt;&lt;br/&gt;&lt;br/&gt;Sigh... what I meant to say was...&lt;br/&gt;&lt;br/&gt;"I'd say that the age of the blog / number of posts could be an and/ either/ or proposition."&lt;br/&gt;&lt;br/&gt;This is why I always told my students to have someone else proofread their work.  Self-editing can lead one to overlook &lt;b&gt;glaring&lt;/b&gt; errors.</description>
		<content:encoded><![CDATA[<p><i>I&#8217;d say that the age of the blog could be a guideline/ number of posts could be an and/ either/ or proposition.</i></p>
<p>Sigh&#8230; what I meant to say was&#8230;</p>
<p>&#8220;I&#8217;d say that the age of the blog / number of posts could be an and/ either/ or proposition.&#8221;</p>
<p>This is why I always told my students to have someone else proofread their work.  Self-editing can lead one to overlook <b>glaring</b> errors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amanda</title>
		<link>http://medbloggercode.com/2007/07/24/establishing-general-submission-guidelines/#comment-85</link>
		<dc:creator>Amanda</dc:creator>
		<pubDate>Fri, 27 Jul 2007 23:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://medbloggercode.com/?p=16#comment-85</guid>
		<description>I'd say that the age of the blog could be a guideline/ number of posts could be an and/ either/ or proposition.  Some excellent blogs won't be up to 15 posts in three months, but there may be a consistent posting pattern just the same.  Some excellent blogs may be more youthful, but have an incredibly dynamic posting rhythm and already have a substantial amount of traffic.&lt;br/&gt;&lt;br/&gt;Then again, I'm the literature major among us, where everything is mutable; I may be oversimplifying the matter.</description>
		<content:encoded><![CDATA[<p>I&#8217;d say that the age of the blog could be a guideline/ number of posts could be an and/ either/ or proposition.  Some excellent blogs won&#8217;t be up to 15 posts in three months, but there may be a consistent posting pattern just the same.  Some excellent blogs may be more youthful, but have an incredibly dynamic posting rhythm and already have a substantial amount of traffic.</p>
<p>Then again, I&#8217;m the literature major among us, where everything is mutable; I may be oversimplifying the matter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DrGwenn</title>
		<link>http://medbloggercode.com/2007/07/24/establishing-general-submission-guidelines/#comment-84</link>
		<dc:creator>DrGwenn</dc:creator>
		<pubDate>Thu, 26 Jul 2007 01:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://medbloggercode.com/?p=16#comment-84</guid>
		<description>I'm a big advocate of "set in stone" guidelines because of accountability issues and the guidelines you proposed seem fair and reasonable as a starting point. Similar to the HON reasoning, we're trying to weed out the rif-raf, nothing more, and give us something to fall back upon should someone say "hey, why didn't I get 'approved'". &lt;br/&gt;&lt;br/&gt;We have a cool logo and a set of principles that we can now proudly stand behind so having writing guidelines we can point to makes good sense.</description>
		<content:encoded><![CDATA[<p>I&#8217;m a big advocate of &#8220;set in stone&#8221; guidelines because of accountability issues and the guidelines you proposed seem fair and reasonable as a starting point. Similar to the HON reasoning, we&#8217;re trying to weed out the rif-raf, nothing more, and give us something to fall back upon should someone say &#8220;hey, why didn&#8217;t I get &#8216;approved&#8217;&#8221;. </p>
<p>We have a cool logo and a set of principles that we can now proudly stand behind so having writing guidelines we can point to makes good sense.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean Moyer</title>
		<link>http://medbloggercode.com/2007/07/24/establishing-general-submission-guidelines/#comment-83</link>
		<dc:creator>Dean Moyer</dc:creator>
		<pubDate>Wed, 25 Jul 2007 17:44:00 +0000</pubDate>
		<guid isPermaLink="false">http://medbloggercode.com/?p=16#comment-83</guid>
		<description>Hi greg,&lt;br/&gt;&lt;br/&gt;I visited a couple of dozen directories. All were different. I didn't run across anyone using duplicate guidelines.</description>
		<content:encoded><![CDATA[<p>Hi greg,</p>
<p>I visited a couple of dozen directories. All were different. I didn&#8217;t run across anyone using duplicate guidelines.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: greg</title>
		<link>http://medbloggercode.com/2007/07/24/establishing-general-submission-guidelines/#comment-82</link>
		<dc:creator>greg</dc:creator>
		<pubDate>Wed, 25 Jul 2007 15:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://medbloggercode.com/?p=16#comment-82</guid>
		<description>Hi Dean:&lt;br/&gt;&lt;br/&gt;Just curious where you found those example submission guidelines.  It would appear that somebody is using the BOTW Directory guidelines...</description>
		<content:encoded><![CDATA[<p>Hi Dean:</p>
<p>Just curious where you found those example submission guidelines.  It would appear that somebody is using the BOTW Directory guidelines&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://medbloggercode.com/2007/07/24/establishing-general-submission-guidelines/#comment-81</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Wed, 25 Jul 2007 10:40:00 +0000</pubDate>
		<guid isPermaLink="false">http://medbloggercode.com/?p=16#comment-81</guid>
		<description>Yes, the problem that I saw was twofold:&lt;br/&gt;First was that I was getting commercial blogs that posted with the intent on just selling a product.  The blog was really a ruse to get people to get interested in a product.  Even with full disclosure, it seemed to me to be something that crossed the line with respect to the code.&lt;br/&gt;&lt;br/&gt;The second was, as Dean spelled out, the inclusion of blogs that used secondary content (or 'script generated' content).  How can they say they adhere to a code of ethics when they are not producing most of the content?  It seems impossible.&lt;br/&gt;&lt;br/&gt;I just wonder if these need to be set forth in stone, or if they can be guidelines we use when we peak at a site and decide if it is OK for it to display the code.  I think we should have them written down so that when I or someone else respond to a request negatively, I can site the criteria.  It is important to have some structure.&lt;br/&gt;&lt;br/&gt;That is why I wanted Dean to post this.</description>
		<content:encoded><![CDATA[<p>Yes, the problem that I saw was twofold:<br />First was that I was getting commercial blogs that posted with the intent on just selling a product.  The blog was really a ruse to get people to get interested in a product.  Even with full disclosure, it seemed to me to be something that crossed the line with respect to the code.</p>
<p>The second was, as Dean spelled out, the inclusion of blogs that used secondary content (or &#8217;script generated&#8217; content).  How can they say they adhere to a code of ethics when they are not producing most of the content?  It seems impossible.</p>
<p>I just wonder if these need to be set forth in stone, or if they can be guidelines we use when we peak at a site and decide if it is OK for it to display the code.  I think we should have them written down so that when I or someone else respond to a request negatively, I can site the criteria.  It is important to have some structure.</p>
<p>That is why I wanted Dean to post this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
