<?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: Digital Branch Style Guide</title>
	<atom:link href="http://www.davidleeking.com/2009/02/10/digital-branch-style-guide/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.davidleeking.com/2009/02/10/digital-branch-style-guide/</link>
	<description>David Lee King is the Digital Branch &#38; Services Manager at the Topeka &#38; Shawnee County Public Library, where he plans, implements, and experiments with emerging technology trends. He has spoken in the U.S. and Canada about emerging trends, website usability and management, digital experience planning, and managing techie staff, and has been published in many library-related journals. David writes the Internet Spotlight column in Public Libraries Magazine with Michael Porter. David maintains a blog at http://www.davidleeking.com</description>
	<lastBuildDate>Sat, 20 Mar 2010 01:50:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Cindy Timmerman</title>
		<link>http://www.davidleeking.com/2009/02/10/digital-branch-style-guide/comment-page-1/#comment-23602</link>
		<dc:creator>Cindy Timmerman</dc:creator>
		<pubDate>Mon, 14 Dec 2009 12:55:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/?p=953#comment-23602</guid>
		<description>David: Thanks for this - lots of really great information, and we&#039;re going to use these ideas!</description>
		<content:encoded><![CDATA[<p>David: Thanks for this &#8211; lots of really great information, and we&#39;re going to use these ideas!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tech Training. It&#8217;s what I do. &#171; Sheaux.us</title>
		<link>http://www.davidleeking.com/2009/02/10/digital-branch-style-guide/comment-page-1/#comment-23001</link>
		<dc:creator>Tech Training. It&#8217;s what I do. &#171; Sheaux.us</dc:creator>
		<pubDate>Wed, 28 Oct 2009 22:35:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/?p=953#comment-23001</guid>
		<description>[...] library digital branch style guide. http://www.davidleeking.com/2009/02/10/digital-branch-style-guide/ [...]</description>
		<content:encoded><![CDATA[<p>[...] library digital branch style guide. <a href="http://www.davidleeking.com/2009/02/10/digital-branch-style-guide/" rel="nofollow">http://www.davidleeking.com/2009/02/10/digital-branch-style-guide/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: luvgardenias</title>
		<link>http://www.davidleeking.com/2009/02/10/digital-branch-style-guide/comment-page-1/#comment-22737</link>
		<dc:creator>luvgardenias</dc:creator>
		<pubDate>Mon, 28 Sep 2009 22:21:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/?p=953#comment-22737</guid>
		<description>Big LOL for the &quot;my way is the right way&quot; exchange.  Love the style guide and will suggest it as a model for our library.  Greatly appreciate all that you share.</description>
		<content:encoded><![CDATA[<p>Big LOL for the &#8220;my way is the right way&#8221; exchange.  Love the style guide and will suggest it as a model for our library.  Greatly appreciate all that you share.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: davidleeking</title>
		<link>http://www.davidleeking.com/2009/02/10/digital-branch-style-guide/comment-page-1/#comment-20505</link>
		<dc:creator>davidleeking</dc:creator>
		<pubDate>Sat, 21 Feb 2009 19:54:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/?p=953#comment-20505</guid>
		<description>One thing more - &lt;a href=&quot;http://www.thefictiondesk.com/spelling-email-vs-e-mail/&quot; rel=&quot;nofollow&quot;&gt;an introductory article&lt;/a&gt; on why I use &quot;email&quot; rather than &quot;E-mail.&quot;

Joe, you should ignore the slug in that link/link title, though :-)</description>
		<content:encoded><![CDATA[<p>One thing more &#8211; <a href="http://www.thefictiondesk.com/spelling-email-vs-e-mail/" rel="nofollow">an introductory article</a> on why I use &#8220;email&#8221; rather than &#8220;E-mail.&#8221;</p>
<p>Joe, you should ignore the slug in that link/link title, though <img src='http://www.davidleeking.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: davidleeking</title>
		<link>http://www.davidleeking.com/2009/02/10/digital-branch-style-guide/comment-page-1/#comment-20504</link>
		<dc:creator>davidleeking</dc:creator>
		<pubDate>Sat, 21 Feb 2009 19:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/?p=953#comment-20504</guid>
		<description>Joe - you said &quot;can you explain how the intended audience for your posting – librarians new to blogging – will in fact be using a CMS and not an off-the-shelf blog platform like Movable Type, WordPress, or Blogger?&quot; 

I would imagine they&#039;d use it in any number of ways??? Not really sure what you mean there. And that wasn&#039;t really &quot;the intended audience&quot; either - one of them, yes - but certainly not limited to that.

&quot;you don’t have a case for collapsing E- to e in every case, because the resulting compounds become incomprehensible&quot; - To you, maybe so. A 2-minute cursory search in a modern dictionary shows that &quot;email&quot; is, in fact, an alternative use for E-mail. Your argument isn&#039;t with me - it&#039;s with the dictionary writers. Have fun with that.

But more to the point - removing those hyphens is an emerging use of the term, whether or not you like it. And I prefer the new way.

&quot;I see you have learned exactly nothing about slugs&quot; - I could care less about slugs. I realize I DO have that option, but I choose to not do it. If you have a problem with my non-use of slugs, I suggest you get over it or move on, because I&#039;m not changing it any time soon.

&quot;Tell me: How is that actually better, in any respect, than the following? http://www.davidleeking.com/2009/02/18/itinerary09/&quot; Well - I would never use the word &quot;itinerary,&quot; for starters, so in my book what I did on my personal website is in every respect better than your suggestion. My blog, my way.

&quot;Some of us have been around longer and know more&quot; Um... I&#039;ve been successfully making and managing websites since 1995, and messing around with gopher before that. How long have you been doing it? Or did you mean your general age?</description>
		<content:encoded><![CDATA[<p>Joe &#8211; you said &#8220;can you explain how the intended audience for your posting – librarians new to blogging – will in fact be using a CMS and not an off-the-shelf blog platform like Movable Type, WordPress, or Blogger?&#8221; </p>
<p>I would imagine they&#8217;d use it in any number of ways??? Not really sure what you mean there. And that wasn&#8217;t really &#8220;the intended audience&#8221; either &#8211; one of them, yes &#8211; but certainly not limited to that.</p>
<p>&#8220;you don’t have a case for collapsing E- to e in every case, because the resulting compounds become incomprehensible&#8221; &#8211; To you, maybe so. A 2-minute cursory search in a modern dictionary shows that &#8220;email&#8221; is, in fact, an alternative use for E-mail. Your argument isn&#8217;t with me &#8211; it&#8217;s with the dictionary writers. Have fun with that.</p>
<p>But more to the point &#8211; removing those hyphens is an emerging use of the term, whether or not you like it. And I prefer the new way.</p>
<p>&#8220;I see you have learned exactly nothing about slugs&#8221; &#8211; I could care less about slugs. I realize I DO have that option, but I choose to not do it. If you have a problem with my non-use of slugs, I suggest you get over it or move on, because I&#8217;m not changing it any time soon.</p>
<p>&#8220;Tell me: How is that actually better, in any respect, than the following? <a href="http://www.davidleeking.com/2009/02/18/itinerary09/" rel="nofollow">http://www.davidleeking.com/2009/02/18/itinerary09/</a>&#8221; Well &#8211; I would never use the word &#8220;itinerary,&#8221; for starters, so in my book what I did on my personal website is in every respect better than your suggestion. My blog, my way.</p>
<p>&#8220;Some of us have been around longer and know more&#8221; Um&#8230; I&#8217;ve been successfully making and managing websites since 1995, and messing around with gopher before that. How long have you been doing it? Or did you mean your general age?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Clark</title>
		<link>http://www.davidleeking.com/2009/02/10/digital-branch-style-guide/comment-page-1/#comment-20503</link>
		<dc:creator>Joe Clark</dc:creator>
		<pubDate>Sat, 21 Feb 2009 19:14:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/?p=953#comment-20503</guid>
		<description>Joshua M. Neff, what is this CMS you are stuck using?

David Lee King, can you explain how the intended audience for your posting – librarians new to blogging – will in fact be using a CMS and not an off-the-shelf blog platform like Movable Type, WordPress, or Blogger?

Now, as someone who has little hesitation lecturing other people, let me say I don’t think it’s wise to lecture me about prescriptive vs. descriptive spelling, since I wrote an entire book about Canadian spelling. The right way to spell is the way everyone else spells. You may indeed have a case for &lt;cite&gt;website&lt;/cite&gt;. But you don’t have a case for collapsing &lt;cite&gt;E-&lt;/cite&gt; to &lt;cite&gt;e&lt;/cite&gt; in every case, because the resulting compounds become incomprehensible. Really, &lt;cite&gt;email&lt;/cite&gt; may work fine most of the time (capitalized at the beginning of a sentence? not so much), but ereader? ecommerce? econsultancy? ebook? Can you really defend those?

Also, David, I see you have learned exactly nothing about slugs:

http://www.davidleeking.com/2009/02/18/where-will-david-be-this-spring-and-summer/

Tell me: How is that actually better, in any respect, than the following?

http://www.davidleeking.com/2009/02/18/itinerary09/

Please contain your thanks and work harder on improving your practice. Some of us have been around longer and know more. You should learn from us instead of acting all miffed and digging in your heels (/2009/02/18/acting-all-miffed-and-digging-in-your-heels/).</description>
		<content:encoded><![CDATA[<p>Joshua M. Neff, what is this CMS you are stuck using?</p>
<p>David Lee King, can you explain how the intended audience for your posting – librarians new to blogging – will in fact be using a CMS and not an off-the-shelf blog platform like Movable Type, WordPress, or Blogger?</p>
<p>Now, as someone who has little hesitation lecturing other people, let me say I don’t think it’s wise to lecture me about prescriptive vs. descriptive spelling, since I wrote an entire book about Canadian spelling. The right way to spell is the way everyone else spells. You may indeed have a case for <cite>website</cite>. But you don’t have a case for collapsing <cite>E-</cite> to <cite>e</cite> in every case, because the resulting compounds become incomprehensible. Really, <cite>email</cite> may work fine most of the time (capitalized at the beginning of a sentence? not so much), but ereader? ecommerce? econsultancy? ebook? Can you really defend those?</p>
<p>Also, David, I see you have learned exactly nothing about slugs:</p>
<p><a href="http://www.davidleeking.com/2009/02/18/where-will-david-be-this-spring-and-summer/" rel="nofollow">http://www.davidleeking.com/2009/02/18/where-will-david-be-this-spring-and-summer/</a></p>
<p>Tell me: How is that actually better, in any respect, than the following?</p>
<p><a href="http://www.davidleeking.com/2009/02/18/itinerary09/" rel="nofollow">http://www.davidleeking.com/2009/02/18/itinerary09/</a></p>
<p>Please contain your thanks and work harder on improving your practice. Some of us have been around longer and know more. You should learn from us instead of acting all miffed and digging in your heels (/2009/02/18/acting-all-miffed-and-digging-in-your-heels/).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david lee king</title>
		<link>http://www.davidleeking.com/2009/02/10/digital-branch-style-guide/comment-page-1/#comment-20460</link>
		<dc:creator>david lee king</dc:creator>
		<pubDate>Thu, 19 Feb 2009 16:25:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/?p=953#comment-20460</guid>
		<description>The one space thing is actually good general practice. If you write something for the web, maybe your CMS will remove it. But if it&#039;s for the web, your print newsletter, and is going to the printer ... someone HAS to remove those extra spaces.

Teach staff to do it right the first time, and you don&#039;t have to go back and fix it later. Just sayin.</description>
		<content:encoded><![CDATA[<p>The one space thing is actually good general practice. If you write something for the web, maybe your CMS will remove it. But if it&#8217;s for the web, your print newsletter, and is going to the printer &#8230; someone HAS to remove those extra spaces.</p>
<p>Teach staff to do it right the first time, and you don&#8217;t have to go back and fix it later. Just sayin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joshua m. neff</title>
		<link>http://www.davidleeking.com/2009/02/10/digital-branch-style-guide/comment-page-1/#comment-20458</link>
		<dc:creator>joshua m. neff</dc:creator>
		<pubDate>Thu, 19 Feb 2009 12:58:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/?p=953#comment-20458</guid>
		<description>Joe, the CMS my library uses doesn&#039;t collapse multiple spaces into one, so when staff send me text with double spacing after punctuation, I have to fix it. We can&#039;t &quot;fix&quot; our CMS without paying a good amount of money to the company that sold us the CMS, and that&#039;s not really a good option these budget-crunchy days.

As for the spelling, David&#039;s right, &quot;email&quot; is a legitimate spelling. &quot;Website&quot; is also legit. English is not a static, &quot;there&#039;s only one way to do it&quot; language. Never has been, almost certainly never will be.</description>
		<content:encoded><![CDATA[<p>Joe, the CMS my library uses doesn&#8217;t collapse multiple spaces into one, so when staff send me text with double spacing after punctuation, I have to fix it. We can&#8217;t &#8220;fix&#8221; our CMS without paying a good amount of money to the company that sold us the CMS, and that&#8217;s not really a good option these budget-crunchy days.</p>
<p>As for the spelling, David&#8217;s right, &#8220;email&#8221; is a legitimate spelling. &#8220;Website&#8221; is also legit. English is not a static, &#8220;there&#8217;s only one way to do it&#8221; language. Never has been, almost certainly never will be.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: davidleeking</title>
		<link>http://www.davidleeking.com/2009/02/10/digital-branch-style-guide/comment-page-1/#comment-20445</link>
		<dc:creator>davidleeking</dc:creator>
		<pubDate>Wed, 18 Feb 2009 19:05:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/?p=953#comment-20445</guid>
		<description>Joe Clark - thanks for sharing!</description>
		<content:encoded><![CDATA[<p>Joe Clark &#8211; thanks for sharing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Clark</title>
		<link>http://www.davidleeking.com/2009/02/10/digital-branch-style-guide/comment-page-1/#comment-20444</link>
		<dc:creator>Joe Clark</dc:creator>
		<pubDate>Wed, 18 Feb 2009 19:01:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.davidleeking.com/?p=953#comment-20444</guid>
		<description>Fix your CMS if it is turning whitespace into nonbreaking spaces. What else is it doing to your content? 

My statement is correct: Writers can add as much whitespace as they want (save for non-breaking spaces, and, of course, anything inside &lt;code&gt;pre&lt;/code&gt;) and it will all be collapsed to a single space character.  Print practice is not Web practice.

 /2009/02/10/loading-your-slugs-up-with-every-word-in-the-title-of-your-post-even-if-the-title-is-over-a-dozen-words-long/ is not “good... SEO practice.” The use of semantic HTML is good SEO practice. WordPress, which you’re using, puts the true text of your title inside e.g. &lt;code&gt;H1&lt;/code&gt; tags, where it belongs and where it can be parsed for what it is: The most important heading on the page expressed in human language. Tell me, what is the most important part of /2009/02/10/loading-your-slugs-up-with-every-word-in-the-title-of-your-post-even-if-the-title-is-over-a-dozen-words-long/ and what language is it written in? (For non-English speakers using characters outside the US-ASCII repertoire, what &lt;em&gt;will&lt;/em&gt; their slugs look like?)

Again, my statement is correct: Slugs should be one or two memorable and distinctive words that relate to the posting. WordPress lets you easily modify slugs. &lt;a href=&quot;http://blog.fawny.org/&quot; title=&quot;At my personal blog, for example&quot; rel=&quot;nofollow&quot;&gt;The way I do it&lt;/a&gt; is the correct way. Now, Blogger and other substandard platforms interfere with doing things the correct way.

Incidentally, why are you even concerned about gaming the system so search engines will find your postings faster? What makes you think search engines (there’s only one that counts) have any trouble doing that? Why are you altering your content to suit a machine?

If you think E-mail is email, are E-consultancy and E-business econsultancy and ebusiness? How about &lt;a href=&quot;http://blog.fawny.org/2005/06/29/e/&quot; rel=&quot;nofollow&quot;&gt;ereader&lt;/a&gt;?</description>
		<content:encoded><![CDATA[<p>Fix your CMS if it is turning whitespace into nonbreaking spaces. What else is it doing to your content? </p>
<p>My statement is correct: Writers can add as much whitespace as they want (save for non-breaking spaces, and, of course, anything inside <code>pre</code>) and it will all be collapsed to a single space character.  Print practice is not Web practice.</p>
<p> /2009/02/10/loading-your-slugs-up-with-every-word-in-the-title-of-your-post-even-if-the-title-is-over-a-dozen-words-long/ is not “good&#8230; SEO practice.” The use of semantic HTML is good SEO practice. WordPress, which you’re using, puts the true text of your title inside e.g. <code>H1</code> tags, where it belongs and where it can be parsed for what it is: The most important heading on the page expressed in human language. Tell me, what is the most important part of /2009/02/10/loading-your-slugs-up-with-every-word-in-the-title-of-your-post-even-if-the-title-is-over-a-dozen-words-long/ and what language is it written in? (For non-English speakers using characters outside the US-ASCII repertoire, what <em>will</em> their slugs look like?)</p>
<p>Again, my statement is correct: Slugs should be one or two memorable and distinctive words that relate to the posting. WordPress lets you easily modify slugs. <a href="http://blog.fawny.org/" title="At my personal blog, for example" rel="nofollow">The way I do it</a> is the correct way. Now, Blogger and other substandard platforms interfere with doing things the correct way.</p>
<p>Incidentally, why are you even concerned about gaming the system so search engines will find your postings faster? What makes you think search engines (there’s only one that counts) have any trouble doing that? Why are you altering your content to suit a machine?</p>
<p>If you think E-mail is email, are E-consultancy and E-business econsultancy and ebusiness? How about <a href="http://blog.fawny.org/2005/06/29/e/" rel="nofollow">ereader</a>?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
