<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!--Web 2.0 Content Powered by MyST Blogsite® (http://blogsite.com)-->
<!--A service of MyST Technology Partners, Inc. (http://myst-technology.com)-->
<?xml-stylesheet href="http://blogsite.com/public/styles/etc/object.xsl" type="text/xsl"?>

<?myst-baseUrl http://blogsite.com/public/?>

<MySmartChannels Public="true" UserID="76091" dT="88" t0="1231424229901">
     <GetChannelItem_Result>
      <Item>
       <Resource>
        <ObjectID>209469</ObjectID>
        <ObjectClass>Resource</ObjectClass>
        <OwnerID ObjectClass="Domain" Title="[Weblog] Marketing. Communication. Results.">76407</OwnerID>
        <CreatedByID ObjectClass="User" Title="bfrench">24</CreatedByID>
        <ModifiedByID ObjectClass="User" Title="bfrench">24</ModifiedByID>
        <CreateTime Title="2008-07-21 23:06:01 EDT">1216695961743</CreateTime>
        <ModifyTime Title="2008-07-23 21:27:01 EDT">1216862821543</ModifyTime>
        <SecurityModel>Controlled</SecurityModel>
        <Name>Manage Blog Commenting as a Marketing Opportunity: Treat Your Vocal Visitors Like Royalty</Name>
        <Summary>MyST Blogsite's commenting system is far more advanced than most blog systems and intentionally so.</Summary>
        <Description>&lt;p&gt;It&amp;rsquo;s true &amp;ndash; things that are inherently designed differently (as compared with the status-quo) are typically not obvious and [sometimes] intentionally so. This is partially the case with the MyST Blogsite commenting design. &lt;/p&gt;&lt;p&gt;There&amp;rsquo;s no shortage of other products that have become more complex because they had to, or they wouldn&amp;rsquo;t be better than their predecessors. I prefer ultra-simple solutions to complex problems, but given the constraints, our clients expect extraordinary findability for anything that&amp;rsquo;s published in their marketing advertorials and this includes comments.&amp;nbsp;To satisfy this requirement,&amp;nbsp;all information objects (including comments) must include more meta-information; far more meta-data than&amp;nbsp;typical blog commenting features and quite different from visitor expectations.&lt;/p&gt;&lt;p&gt;You could say&amp;nbsp;we have a fundamental problem with doing it the way all other &amp;quot;blog&amp;rdquo; tools&amp;nbsp;have done it in the past, partly because most companies really want to do more than just blog and get people to leave comments. While conversations are good, high-quality conversations are probably far more valuable in reaching your marketing objectives.&lt;/p&gt;&lt;p&gt;Intentionally, we expose three fields for commenting and &lt;em&gt;&lt;strong&gt;n&amp;hellip;&lt;/strong&gt;&lt;/em&gt; options for adding link properties to a comment. This is far more comprehensive than any commenting system presently on the web, which typically include only a comment field. In fact, commenting (as we know it) &lt;em&gt;&lt;u&gt;constrains&lt;/u&gt;&lt;/em&gt; findability rather than increasing it. Why? Because most blog tools are so unable to control track-back and comment spam that they had to take a defensive posture by removing any incentive to publish off-domain links. Our platform and approach is exactly the opposite &amp;ndash; for business advertorials (where brand matters greatly), we recommend that comments should always be moderated, and generally enhanced with keywords, clear titles, comprehensive summaries, quotes, images, and additional link properties where appropriate.&lt;/p&gt;&lt;p&gt;In our view, a comment is no different than a blog post &amp;ndash; it is a &lt;em&gt;&lt;u&gt;class-A content element&lt;/u&gt;&lt;/em&gt; and it should enjoy the same power of a normal post. This achieves many benefits;&amp;nbsp;two primary advantages - (i) a more search optimized comment&amp;nbsp;attracts new visitors, and (ii) you can assist your commenters in making a clear point. Elevating the importance of comments by allowing visitors to include more meta-data pays big SEO dividends, but one advantage that you may have overlooked &amp;ndash; it provides an opportunity for visitors (that comment) to feel special because they have been accorded the same publishing features that the authors of your blogsite use. &lt;/p&gt;&lt;p&gt;&lt;em&gt;&lt;strong&gt;How special would you feel if your comment were given the &amp;ldquo;royal treatment&amp;rdquo; and enhanced in ways that really helped the&amp;nbsp;you make a clear and concise point?&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;&lt;p&gt;Ironically, we can see an example of how we treat our own visitors in this post about &amp;ldquo;&lt;a title="Channel Conversations" href="item/192677" target="_self"&gt;channel conversations&lt;/a&gt;&amp;rdquo;. You can readily see that comments don&amp;rsquo;t have to be bland. Nor&amp;nbsp;must they blend into the background - they can be loud and boisterous and they can include links and other enhanced publishing components, and tags.&lt;/p&gt;&lt;p&gt;A really simple commenting system (with just a field for text) is likely to generate a few more comments because there are fewer fields. However, constraining the opportunity for visitors to share additional meta-data makes it more difficult to understand what they are trying to say. Besides, how valuable is comment volume? Aren't we really looking for the gems of agreement and the controversial diamonds of dissent to help us tell our business and marketing stories more clearly?&lt;/p&gt;&lt;p&gt;Tell me how you make your commenting visitors feel special?&lt;/p&gt;</Description>
        <ResourceTypeID ObjectClass="ResourceType" Title="Item:Content">10</ResourceTypeID>
        <ContentType>application/xml</ContentType>
        <ContentDocument>
         <ItemProperties>
               <CommonProperties>
       
                <Keywords>
                 <Keyword>commenting</Keyword>

                 <Keyword>conversations</Keyword>

                 <Keyword>story-telling opportunity</Keyword>

       </Keywords>

               <Hidden>false</Hidden>
        </CommonProperties>

              <ns3:Details xmlns="urn:MyST-Technology.Structured.Details" xmlns:ns3="urn:MyST-Technology.Structured.Details">
               <ns3:Collection name="Quote" type="urn:MyST-Technology.Structured.Collection.Captyx.Quote">
                <ns3:Attribute name="Quote" type="large-text">
                 <ns3:Value>In our view, a comment is no different than a blog post - it is a &lt;i&gt;class-A content element&lt;/i&gt; and it should enjoy the same power of a normal post to attract new visitors and help those that comment, make a clear point.</ns3:Value>

        </ns3:Attribute>

                <ns3:Attribute name="Name" type="text" value="Bill French"/>

                <ns3:Attribute name="Blog" type="url" value="http://blogsite.com"/>

                <ns3:Attribute name="Title" type="text" value="Co-Founder"/>

                <ns3:Attribute name="Company" type="text" value="MyST Technology Partners"/>

                <ns3:Attribute name="Web" type="url" value="http://myst-technology.com"/>

                <ns3:Attribute name="Icon" type="checkbox" value="true"/>

                <ns3:Attribute name="Frame" type="text" value="bars"/>

                <ns3:Attribute name="HTML" type="checkbox" value="true"/>

                <ns3:Attribute name="Alignment" type="text" value="right"/>

                <ns3:Attribute name="Text Size" type="text" value="medium"/>

                <ns3:Attribute name="Container" type="text" value="div"/>

                <ns3:Attribute name="Container ID" type="text"/>

                <ns3:Attribute name="Container Class" type="text" value="Quote"/>

                <ns3:Attribute name="Container Style" type="text"/>

                <ns3:Attribute name="_captyx.position" type="text" value="_top"/>

                <ns3:Attribute name="_captyx.embargo" type="checkbox" value="false"/>

                <ns3:Attribute name="_captyx.scope" type="text"/>

                <ns3:Attribute name="_captyx.sortkey" type="text"/>

       </ns3:Collection>

      </ns3:Details>

              <RemoteInfo>
               <UserAgent>Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Dosware Team Internet Browser; .NET CLR 1.1.4322; .NET CLR 2.0.50727)</UserAgent>

               <RemoteHost>127.0.0.1</RemoteHost>

               <RemoteAddr>127.0.0.1</RemoteAddr>

               <RemoteUser>bfrench</RemoteUser>

               <ForwardedFor>76.120.48.245</ForwardedFor>

      </RemoteInfo>

     </ItemProperties>
       </ContentDocument>
      </Resource>
      <Shares/>
      <Subjects/>
      <UserPermissions>
       <CanDelete>false</CanDelete>
       <CanDiscover>true</CanDiscover>
       <CanEdit>false</CanEdit>
       <CanEditPermissions>false</CanEditPermissions>
       <CanRead>true</CanRead>
      </UserPermissions>
      <CommentInfo>
       <CommentChannelRef AllowAnonymous="true" Inherited="true">
        <ChannelID ObjectClass="Channel" Title="[Public] Public Comments">174050</ChannelID>
        <UserPermissions>
         <CanCreateChannelItem>false</CanCreateChannelItem>
         <CanDelete>false</CanDelete>
         <CanDiscover>true</CanDiscover>
         <CanEdit>false</CanEdit>
         <CanEditPermissions>false</CanEditPermissions>
         <CanPublish>false</CanPublish>
         <CanRead>true</CanRead>
        </UserPermissions>
       </CommentChannelRef>
       <Comments/>
      </CommentInfo>
      <Views>
       <SourceID ObjectClass="Channel" Title="[Weblog] Marketing. Communication. Results.">76407</SourceID>

              <View>
               <Name>blog</Name>

               <Model>blogsite/Blogsite/web</Model>

               <Style/>

               <Scheme/>

       </View>

              <View>
               <Name>edit-item</Name>

               <Model>blogsite/Blogsite/right-content</Model>

               <Style/>

               <Scheme/>

       </View>

              <View>
               <Name>left</Name>

               <Model>blogsite/Blogsite/left-content</Model>

               <Style/>

               <Scheme/>

       </View>

              <View>
               <Name>right</Name>

               <Model>blogsite/Blogsite/right-content</Model>

               <Style/>

               <Scheme/>

       </View>

              <View>
               <Name>wide</Name>

               <Model>blogsite/Blogsite/wide-content</Model>

               <Style/>

               <Scheme/>

       </View>

      </Views>
       <Views>
        <SourceID ObjectClass="Channel" Shared="true" Title="[Public] What's New">102736</SourceID>

               <View>
                <Name>blog</Name>

                <Model>blogsite/Blogsite/my-whatsnew</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>edit-item</Name>

                <Model>blogsite/Blogsite/right-content</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>left</Name>

                <Model>blogsite/Blogsite/left-content</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>right</Name>

                <Model>blogsite/Blogsite/right-content</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>wide</Name>

                <Model>blogsite/Blogsite/wide-content</Model>

                <Style/>

                <Scheme/>

       </View>

      </Views>
       </Item>
      </GetChannelItem_Result>
     </MySmartChannels>
