<?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="112" t0="1231433860409">
     <GetChannelItem_Result>
      <Item>
       <Resource>
        <ObjectID>210687</ObjectID>
        <ObjectClass>Resource</ObjectClass>
        <OwnerID ObjectClass="Domain" Title="[Weblog] Marketing. Communication. Results.">76407</OwnerID>
        <CreatedByID ObjectClass="User" Title="$Admin">1</CreatedByID>
        <ModifiedByID ObjectClass="User" Title="aseidl">21</ModifiedByID>
        <CreateTime Title="2008-08-07 20:24:32 EDT">1218155072064</CreateTime>
        <ModifyTime Title="2008-08-24 12:39:32 EDT">1219595972534</ModifyTime>
        <SecurityModel>Controlled</SecurityModel>
        <Name>Blogging 2.0: Moving Toward Conversational "Flows"</Name>
        <Summary>Blogging 1.0 was great; commenting… not so useful. Flow applications; a natural extension of commenting that enhances the conversation and will dramatically impact the emergence of Blogging 2.0.</Summary>
        <Description>&lt;p&gt;It was only a matter of time before the idea of &amp;ldquo;&lt;b&gt;Blogging 2.0&amp;rdquo;&lt;/b&gt; made its appearance. In a recent post by Duncan Riley (&lt;a href="http://www.inquisitr.com/1964/the-changing-blogosphere-and-blogging-20/"&gt;The Changing Blogosphere and Blogging 2.0&lt;/a&gt;), he accurately underscores the revolution that is taking place &amp;ndash; conversations are moving away from blogs (specifically business blogs) as content consumers attempt to participate [more] in the conversational aspects of the blogosphere.&lt;/p&gt;&lt;p&gt;I don&amp;rsquo;t believe this shift is intentional; rather, it&amp;rsquo;s simply the market of content consumers (and providers) voting for better interaction and conversational services. If anything, it underscores why &lt;a href="http://twitter.com/"&gt;Twitter&lt;/a&gt; has grown so quickly and why other services such as &lt;a href="http://ping.fm/"&gt;Ping.FM&lt;/a&gt; have emerged.&lt;/p&gt;&lt;p&gt;In my view, Blogging 2.0 could (and possibly should) be called &amp;ldquo;Flow 1.0&amp;rdquo;. Stowe Boyd helped me get along with this thinking where he said &amp;hellip;&lt;/p&gt;&lt;blockquote dir="ltr" style="MARGIN-RIGHT: 0px"&gt;&lt;p&gt;&lt;em&gt;&amp;ldquo;So, larger numbers of blog refugees exist, who read blogs in RSS tools or are alerted to interesting stories and conversations in these flow apps, and comment there, into a minority of what once was the greater community of participants.&amp;rdquo;&lt;/em&gt; &amp;ndash; Stowe Boyd (&lt;a href="http://www.stoweboyd.com/message/2008/08/blogging-20-mem.html"&gt;Blogging 2.0 Meme Doesn't Go Far Enough&lt;/a&gt;)&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;Stowe takes it a bit further suggesting that the very fabric of the blogosphere is being challenged by the movement of information within windows of time &amp;ndash; i.e., through &amp;ldquo;flow&amp;rdquo; applications such as FaceBook, Tumblr, and Twitter.&lt;/p&gt;&lt;blockquote dir="ltr" style="MARGIN-RIGHT: 0px"&gt;&lt;p&gt;&lt;i&gt;&amp;quot;In this model, everything has become disconnected, everything is principally in the flow. The absolute address of any post, or comment, or vote, is irrelevant. And posts and other atrifacts may be copied with appropriate reference back to the original author, and some means to get to a URL, but only as a way to represent an identity.&amp;quot; &lt;/i&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;p /&gt;&lt;p&gt;Blogging itself represents reverse chronological publishing &amp;ndash; it is indeed a flow of sorts, but it&amp;rsquo;s typically a half-duplex (unilateral flow). In 1999 it was a revolutionary idea to publish content in this manner, but humans embraced it because a flow creates a time-centric process that people can easily relate to. Flow applications embrace the conversation slightly better because they allow conversational artifacts to more easily collect in natural ways. Ironically, in this &lt;a title="Comment by Jos Schuurmans" href="item/198459"&gt;comment&lt;/a&gt;, Jos Schuurmans equates the emergence of social networks with the end of &amp;ldquo;channels&amp;rdquo;.&lt;/p&gt;&lt;p&gt;&lt;b&gt;Conclusion&amp;hellip;&lt;/b&gt;&lt;/p&gt;&lt;p /&gt;&lt;p&gt;Blogging 1.0 was great; commenting&amp;hellip; not so useful. Flow applications; a natural extension of commenting that enhances the conversation and will dramatically impact the emergence of Blogging 2.0.&lt;/p&gt;&lt;p&gt;&lt;b&gt;Note to Self&amp;hellip; Blogging 2.0 Requirements&lt;/b&gt;&lt;/p&gt;&lt;p /&gt;&lt;ul&gt;&lt;li&gt;Integration (inbound and outbound) with flow applications.&lt;/li&gt;&lt;li&gt;Inviting flow application users to comment on specific posts related to recent flow-based conversations.&lt;/li&gt;&lt;li&gt;Search technologies that leverage the data in flow applications.&lt;/li&gt;&lt;li&gt;Social media embrace including search, syndication (inbound and outbound).&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;Two things we did when we designed the MyST Platform&amp;trade; was to ensure that (i) comment objects be treated as first class citizens in the common scheme of the content sphere, and (ii) that comments could represented by an abstract association with any other information objects. This gives us the agility to meet the new Blogging 2.0 requirements with ease. &lt;/p&gt;</Description>
        <ResourceTypeID ObjectClass="ResourceType" Title="Item:Content">10</ResourceTypeID>
        <ContentType>application/xml</ContentType>
        <ContentDocument>
         <ItemProperties>
               <CommonProperties>
                <Hidden>false</Hidden>

                <Keywords>
                 <Keyword>Blogging 2.0</Keyword>

                 <Keyword>Duncan Riley</Keyword>

                 <Keyword>flow applications</Keyword>

                 <Keyword>Stowe Boyd</Keyword>

       </Keywords>

      </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>Flow applications embrace the conversation slightly better because they allow conversational artifacts to more easily collect in natural ways. </ns3:Value>

        </ns3:Attribute>

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

                 <ns3:Attribute name="Blog" type="url"/>

                 <ns3:Attribute name="Title" type="text"/>

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

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

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

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

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

                 <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; .NET CLR 1.1.4322; .NET CLR 2.0.50727)</UserAgent>

                <RemoteHost>127.0.0.1</RemoteHost>

                <RemoteAddr>127.0.0.1</RemoteAddr>

                <RemoteUser>aseidl</RemoteUser>

                <ForwardedFor>68.40.167.222</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>
