<?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="91" t0="1227167047355">
     <GetChannelItem_Result>
      <Item>
       <Resource>
        <ObjectID>192677</ObjectID>
        <ObjectClass>Resource</ObjectClass>
        <OwnerID ObjectClass="Domain" Title="[Weblog] Blogsite News">76096</OwnerID>
        <CreatedByID ObjectClass="User" Title="bfrench">24</CreatedByID>
        <ModifiedByID ObjectClass="User" Title="$Admin">1</ModifiedByID>
        <CreateTime Title="2007-12-17 15:43:56 EST">1197924236866</CreateTime>
        <ModifyTime Title="2008-01-28 23:02:54 EST">1201579374234</ModifyTime>
        <SecurityModel>Controlled</SecurityModel>
        <Name>Business Week: "Blogs will change your business."</Name>
        <Summary>There's no debating it - businesses must engage in the conversational web.</Summary>
        <Description>&lt;p&gt;This &lt;a title="The Search Engine's Love Affair With Blogs" href="http://www.grokdotcom.com/2007/12/13/search-engines-love-blogs/" target="_blank"&gt;Business Week cover story&lt;/a&gt; was one of the better written pieces about business blogging that I've seen in years. Typically, these stories are rife with misconceptions and misleading information. But the &lt;a href="http://www.hispanictrending.net/"&gt;author&lt;/a&gt; focused on two of the most important requirements - &lt;u&gt;&lt;em&gt;relevance&lt;/em&gt;&lt;/u&gt; and &lt;em&gt;&lt;u&gt;freshness&lt;/u&gt;&lt;/em&gt;. There are many other requirements and&amp;nbsp;the author makes this clear.&lt;/p&gt;&lt;blockquote dir="ltr" style="MARGIN-RIGHT: 0px"&gt;&lt;p&gt;&amp;quot;&lt;em&gt;&lt;strong&gt;Don&amp;rsquo;t add a blog to your site if you're not willing to consistently invest time and effort&lt;/strong&gt;. An outdated blog will reflect the opposite image of whatever it is you want potential customers to know about your company&lt;/em&gt;.&amp;quot; -- &lt;a title="Posts by Juan Tornoe" href="http://www.grokdotcom.com/author/juan-tornoe/"&gt;Juan Tornoe&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;MyST Blogsite provides the automated machinery to keep a blogsite fresh and tools to help keep it relevant. Automated briefings and inbound syndicated content capabilities work together to always provide fresh material relavant to your content focus.&lt;/p&gt;&lt;blockquote dir="ltr" style="MARGIN-RIGHT: 0px"&gt;&lt;p&gt;&lt;em&gt;&amp;quot;The power of a relevant and consistently updated blog is not to be taken lightly, nor is it for the faint of heart. Years and years of posting relevant information about the subject made Google consider the blog so relevant that, when this specific term was searched, they listed it &amp;ldquo;Numero Uno.&amp;quot; &lt;/em&gt;-- &lt;a title="Posts by Juan Tornoe" href="http://www.grokdotcom.com/author/juan-tornoe/"&gt;Juan Tornoe&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;More excellent advice. A business blogsite is a serious decision and it has long-lasting effects. This is why we build quality assurance tools into our services;&amp;nbsp;you'll appreciate the help maintaining the high content quality your customers expect.&lt;/p&gt;</Description>
        <ResourceTypeID ObjectClass="ResourceType" Title="Item:Link">9</ResourceTypeID>
        <ContentType>application/xml</ContentType>
        <ContentDocument>
         <ItemProperties>
               <CommonProperties>
                <Hidden>false</Hidden>

                <Keywords>
                 <Keyword>blogosphere</Keyword>

                 <Keyword>BusinessWeek</Keyword>

                 <Keyword>content relevance</Keyword>

                 <Keyword>posting frequency</Keyword>

                 <Keyword>quality assurance</Keyword>

       </Keywords>

                <Links>
                 <Link>
                  <Title>Business Week: "Blogs will change your business."</Title>

                  <Synopsis>You've read in one too many places that your website should include a blog in order to get better positioning in search engine results.</Synopsis>

                  <URL>http://www.grokdotcom.com/2007/12/13/search-engines-love-blogs</URL>

        </Link>

                 <Link>
                  <Title>Future Now's Marketing Optimization Blog</Title>

                  <Synopsis>GrokDotCom is published by the knowledge-thirsty folks at Future Now and focuses on grokking human reactions to marketing, sales, PR &amp; evolving media.</Synopsis>

                  <URL>http://www.grokdotcom.com/</URL>

        </Link>

       </Links>

      </CommonProperties>

               <ns3:Details xmlns="urn:MyST-Technology.Structured.Details" xmlns:ns3="urn:MyST-Technology.Structured.Details">
                <ns3:Collection name="Google BlogSearch (*)" type="urn:MyST-Technology.Structured.Collection.Captyx.Google_Blogsearch">
                 <ns3:Attribute name="Title" type="text" value="Google BlogSearch"/>

                 <ns3:Attribute name="Subject Query" type="text" value="BusinessWeek &quot;blogs will change your business&quot;"/>

                 <ns3:Attribute name="Tooltip" type="text" value="Here's what other bloggers are saying."/>

                 <ns3:Attribute name="Image" type="url:image" value="http://blogsearch.google.com/blogsearch/intl/en_ALL/images/g_bsrch_logo_sm.gif"/>

                 <ns3:Attribute name="Image Link" type="url" value="http://blogsearch.google.com/"/>

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

       </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>$Admin</RemoteUser>

      </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>
         <Comment>
          <Item>
           <Resource>
            <ObjectID>198459</ObjectID>
            <ObjectClass>Resource</ObjectClass>
            <OwnerID ObjectClass="Domain" Title="[Public] Public Comments">174050</OwnerID>
            <CreatedByID ObjectClass="User" Title="$Anonymous">173239</CreatedByID>
            <ModifiedByID ObjectClass="User" Title="aseidl">21</ModifiedByID>
            <CreateTime Title="2008-02-29 03:48:35 EST">1204274915509</CreateTime>
            <ModifyTime Title="2008-08-24 12:37:37 EDT">1219595857816</ModifyTime>
            <SecurityModel>Controlled</SecurityModel>
            <Name>Dugg: Social Media Will Change Your Business | BusinessWeek</Name>
            <Summary>Three aspects of social media are truely qualitative departures from the past.</Summary>
            <Description>&lt;p&gt;The three aspects of social media that I'd like to view as qualitative departures from the past are:&lt;/p&gt;&lt;ol&gt;&lt;li&gt;'The End of Channels' in that online conversations happen all over the place;&lt;/li&gt;&lt;li&gt;'The Wisdom of the Crowd', social software helping people navigate their way through online coversations;&lt;/li&gt;&lt;li&gt;The participatory and co-creational nature of social media. &lt;/li&gt;&lt;/ol&gt;&lt;p /&gt;</Description>
            <ResourceTypeID ObjectClass="ResourceType" Title="Item:Link">9</ResourceTypeID>
            <ContentType>application/xml</ContentType>
            <ContentDocument>
             <ItemProperties>
                   <CommonProperties>
                    <Hidden>false</Hidden>

                    <Keywords>
                     <Keyword>distributed conversations</Keyword>

                     <Keyword>end of channels</Keyword>

                     <Keyword>wisdom of crowds</Keyword>

       </Keywords>

                    <Links>
                     <Link>
                      <Title>The End of Channels?</Title>

                      <Synopsis>Three aspects of social media are truely qualitative departures from the past.</Synopsis>

                      <URL>http://www.josschuurmans.com/2007/09/the-dilution-of.html</URL>

        </Link>

                     <Link>
                      <Title>Other Posts by Jos about Conversations</Title>

                      <Synopsis>Posts Categorized as "conversation"</Synopsis>

                      <URL>http://www.josschuurmans.com/conversation/</URL>

        </Link>

       </Links>

      </CommonProperties>

                   <ns3:Details xmlns="urn:MyST-Technology.Structured.Details" xmlns:ns3="urn:MyST-Technology.Structured.Details">
                    <ns3:Collection name="Jos Schuurmans" type="urn:MyST-Technology.Structured.Collection.Contact">
                     <ns3:Attribute name="EMail" type="email" value="jos@josschuurmans.com"/>

                     <ns3:Attribute name="Web" type="url" value="http://www.josschuurmans.com/2007/09/the-dilution-of.html"/>

       </ns3:Collection>

                    <ns3:Collection name="Quote" type="urn:MyST-Technology.Structured.Collection.Captyx.Quote">
                     <ns3:Attribute name="Quote" type="large-text">
                      <ns3:Value>A published article is no longer the start of a discussion, nor does its channel any longer host that discussion. A published article contributes to The Conversation around the topic at hand (which in most cases was already taking place in various shapes elsewhere) and which can unfold in a thousand different directions in conversation threads across the Web and over time.</ns3:Value>

        </ns3:Attribute>

                     <ns3:Attribute name="Name" type="text" value="Jos Schuurmans"/>

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

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

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

                     <ns3:Attribute name="Web" type="url" value="http://www.josschuurmans.com/2007/09/the-dilution-of.html"/>

                     <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>
           <UserPermissions>
            <CanDelete>false</CanDelete>
            <CanDiscover>true</CanDiscover>
            <CanEdit>false</CanEdit>
            <CanEditPermissions>false</CanEditPermissions>
            <CanRead>true</CanRead>
           </UserPermissions>
           <CommentInfo>
            <CommentChannelRef>
             <ChannelID/>
            </CommentChannelRef>
            <Comments/>
           </CommentInfo>
          </Item>
         </Comment>
         <Comment>
          <Item>
           <Resource>
            <ObjectID>198564</ObjectID>
            <ObjectClass>Resource</ObjectClass>
            <OwnerID ObjectClass="Domain" Title="[Public] Public Comments">174050</OwnerID>
            <CreatedByID ObjectClass="User" Title="bfrench">24</CreatedByID>
            <ModifiedByID ObjectClass="User" Title="aseidl">21</ModifiedByID>
            <CreateTime Title="2008-03-02 12:46:55 EST">1204480015508</CreateTime>
            <ModifyTime Title="2008-03-14 21:43:44 EST">1205549024469</ModifyTime>
            <SecurityModel>Controlled</SecurityModel>
            <Name>The End of Channels</Name>
            <Summary>... in that online conversations happen all over the place.</Summary>
            <Description>&lt;p&gt;Hmmm... yes, conversations happen all over the place, but humans (and machines) typically try to create order from chaos. They do this by meta-categorizing information. This seems to be a natural objective in virtual and physical worlds.&lt;/p&gt;&lt;p&gt;One might even conclude that while conversations [about a specific subject] occur everywhere and across all mediums, natural bonds based on say, tags(?) can be used to describe a &amp;quot;conversation channel&amp;quot;. This is a virtual channel in that its topology is guided and shaped by tags (in this theoretical example).&lt;/p&gt;&lt;p&gt;People tend to prefer the benefits that channels provide - they create the notion of a &amp;quot;meta-handle&amp;quot; that makes it easier for them to understand, know about, and share. Search engines love channels - they provide clumps of related information that make it easier for them to recommend as a source of knowledge because the content has a certain degree of density about a single topic.&lt;/p&gt;&lt;p&gt;While most MyST Blogsites define separate blogs within a single blogsite as a &amp;quot;channel&amp;quot;, the architecture embraces this idea purely as a logical array of like-minded information. The conversations that may occur within and peripheral to a given post (i.e., an item resource in a channel) are not bound to that channel. &lt;a title="Topic Cloud FAQ" href="blog/108399"&gt;Topic Cloud&lt;/a&gt; automatically exposes relationships that are &amp;quot;channel-less&amp;quot; and our filter-pattern technology allows us to create virtual channels to meet future unknown business requirements.&lt;/p&gt;</Description>
            <ResourceTypeID ObjectClass="ResourceType" Title="Item:Link">9</ResourceTypeID>
            <ContentType>application/xml</ContentType>
            <ContentDocument>
             <ItemProperties>
                   <CommonProperties>
                    <Hidden>false</Hidden>

                    <Keywords>
                     <Keyword>channels</Keyword>

       </Keywords>

                    <Links>
                     <Link>
                      <Title>What's the difference between channels and blogs?</Title>

                      <Synopsis>A channel is a container for content; a blog is a type of channel but there can be other types as well.</Synopsis>

                      <URL>item/154366</URL>

        </Link>

                     <Link>
                      <Title>Channels and Comments</Title>

                      <Synopsis>Kevin Lynch (Macromedia) recently asked if there were good ways to create a commenting infrastructure for Weblogs.</Synopsis>

                      <URL>http://myst-technology.com/public/blog/18736</URL>

        </Link>

       </Links>

      </CommonProperties>

                   <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>
           <UserPermissions>
            <CanDelete>false</CanDelete>
            <CanDiscover>true</CanDiscover>
            <CanEdit>false</CanEdit>
            <CanEditPermissions>false</CanEditPermissions>
            <CanRead>true</CanRead>
           </UserPermissions>
           <CommentInfo>
            <CommentChannelRef>
             <ChannelID/>
            </CommentChannelRef>
            <Comments/>
           </CommentInfo>
          </Item>
         </Comment>
         <Comment>
          <Item>
           <Resource>
            <ObjectID>198703</ObjectID>
            <ObjectClass>Resource</ObjectClass>
            <OwnerID ObjectClass="Domain" Title="[Public] Public Comments">174050</OwnerID>
            <CreatedByID ObjectClass="User" Title="$Anonymous">173239</CreatedByID>
            <ModifiedByID ObjectClass="User" Title="bfrench">24</ModifiedByID>
            <CreateTime Title="2008-03-04 11:59:57 EST">1204649997307</CreateTime>
            <ModifyTime Title="2008-07-21 21:19:34 EDT">1216689574091</ModifyTime>
            <SecurityModel>Controlled</SecurityModel>
            <Name>Simply 'conversations'</Name>
            <Summary>Why distributed online conversations are not channels...</Summary>
            <Description>&lt;p&gt;Bill:&lt;/p&gt;&lt;p&gt;Great stuff, thanks Bill! I'm adding on to this conversation as well:&lt;br /&gt;&lt;br /&gt;&amp;quot;Channels&amp;quot; does not sufficiently describe the dynamics of distributed online conversations - so why not simply call them &amp;quot;conversations&amp;quot;? &lt;/p&gt;</Description>
            <ResourceTypeID ObjectClass="ResourceType" Title="Item:Link">9</ResourceTypeID>
            <ContentType>application/xml</ContentType>
            <ContentDocument>
             <ItemProperties>
                   <CommonProperties>
                    <Hidden>false</Hidden>

                    <Keywords>
                     <Keyword>channels</Keyword>

                     <Keyword>collaborative filtering</Keyword>

                     <Keyword>distributed conversations</Keyword>

       </Keywords>

                    <Links>
                     <Link>
                      <Title>'Channels' does not sufficiently describe the dynamics of distributed online conversations.</Title>

                      <Synopsis>The way I used "channels" in my post on 'The End of Channels?' was with the traditional notion of, if you will, media titles, in mind: TV/radio channels or shows, zines, newspapers, websites, blogs, forums...</Synopsis>

                      <URL>http://www.josschuurmans.com/2008/03/channels-does-n.html</URL>

        </Link>

       </Links>

      </CommonProperties>

                   <ns3:Details xmlns="urn:MyST-Technology.Structured.Details" xmlns:ns3="urn:MyST-Technology.Structured.Details">
                    <ns3:Collection name="Jos Schuurmans" type="urn:MyST-Technology.Structured.Collection.Contact">
                     <ns3:Attribute name="EMail" type="email" value="jos@josschuurmans.com"/>

                     <ns3:Attribute name="Web" type="url" value="http://www.josschuurmans.com/2008/03/channels-does-n.html"/>

       </ns3:Collection>

                    <ns3:Collection name="Quote" type="urn:MyST-Technology.Structured.Collection.Captyx.Quote">
                     <ns3:Attribute name="Quote" type="large-text">
                      <ns3:Value>But if we look passed the keeper of the gate and over the garden wall, I am willing to accept that channels - as in "meta-handlers" - are not necessarily disappearing, but rather evolving into new forms, such as distributed conversations connected by tags.</ns3:Value>

        </ns3:Attribute>

                     <ns3:Attribute name="Name" type="text" value="Jos Schuurmans"/>

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

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

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

                     <ns3:Attribute name="Web" type="url" value="http://www.josschuurmans.com/2008/03/channels-does-n.html"/>

                     <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; 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>
           <UserPermissions>
            <CanDelete>false</CanDelete>
            <CanDiscover>true</CanDiscover>
            <CanEdit>false</CanEdit>
            <CanEditPermissions>false</CanEditPermissions>
            <CanRead>true</CanRead>
           </UserPermissions>
           <CommentInfo>
            <CommentChannelRef>
             <ChannelID/>
            </CommentChannelRef>
            <Comments/>
           </CommentInfo>
          </Item>
         </Comment>
         <Comment>
          <Item>
           <Resource>
            <ObjectID>199185</ObjectID>
            <ObjectClass>Resource</ObjectClass>
            <OwnerID ObjectClass="Domain" Title="[Public] Public Comments">174050</OwnerID>
            <CreatedByID ObjectClass="User" Title="aseidl">21</CreatedByID>
            <ModifiedByID ObjectClass="User" Title="aseidl">21</ModifiedByID>
            <CreateTime Title="2008-03-11 09:26:42 EST">1205245602168</CreateTime>
            <ModifyTime Title="2008-03-11 10:07:00 EST">1205248020943</ModifyTime>
            <SecurityModel>Controlled</SecurityModel>
            <Name>Conversations and channels are terms at different levels of abstraction</Name>
            <Summary>Would anyone suggest choosing between the terms 'building' and 'home'?</Summary>
            <Description>&lt;p&gt;From the very beginning, our work on the MyST Platform (a layered set of services roughly organized, from bottom up, as MyST Information Object Model, MyST Web Services Platform, MySmartChannels Weblog Application Server, MyST Blogsite), has been guided by the topic map research that Bill and I did while we were both at Starbase.&amp;nbsp; Our goal was to design and build an information management platform &lt;span style="FONT-STYLE: italic"&gt;almost&lt;/span&gt; as abstract as topic maps.&amp;nbsp; (While we both remain strong believers in the topic map vision, we also witnessed first hand the practical challenges of commercializing true topic map technologies--and as a small start up in 2002, we needed shorter routes to demonstrable applications.)&lt;/p&gt;&lt;p&gt;So, in that mindset, we created the MyST Object Model--a highly abstract information model capable of representing any conceivable thing (motivated by the impressively general definition of &lt;em&gt;subject&lt;/em&gt;&amp;nbsp;in topic map speak.)&amp;nbsp; Fundamental building blocks in the MyST Object Model are &lt;em&gt;Resources&lt;/em&gt;, &lt;em&gt;Domains&lt;/em&gt;, and &lt;em&gt;Associations&lt;/em&gt;.&amp;nbsp; (Technically, we could have done without domains, but domains are one of those concessions to pragmatism.)&lt;/p&gt;&lt;p&gt;The MyST Web Services Platform builds web services and security&amp;nbsp;around a MyST Object Model persistence layer.&amp;nbsp; Inherent in this platform is the idea of &lt;em&gt;plug-ins&lt;/em&gt; that expose new object models which are based on the underlying MyST Object Model but are more specialized--i.e., more naturally suited to solving a specific class of problems.&amp;nbsp; The MySmartChannels object model is one such derived object model and forms the heart of the next layer in the MyST technology stack, the MySmartChannels Weblog Application Server.&lt;/p&gt;&lt;p&gt;Central to the MySmartChannels object model are &lt;em&gt;Spaces&lt;/em&gt;, &lt;em&gt;Channels&lt;/em&gt;, and &lt;em&gt;Items &lt;/em&gt;(and various association types).&amp;nbsp; Without getting into details, these object classes are more specialized than the underlying Domain and Resources classes of the MyST Object Model, but are still very abstract.&amp;nbsp; For example, we use &lt;em&gt;channels&lt;/em&gt; to represent many differing &lt;em&gt;kinds&lt;/em&gt; of collections of information--weblogs, competitive intelligence, site navigation details, various process configurations, public comments, etc.&lt;/p&gt;&lt;p&gt;Finally, we can talk about &lt;em&gt;conversations&lt;/em&gt;.&amp;nbsp; The term &amp;quot;conversation&amp;quot; generally refers to a communication between two or more people (or more generally, agents.)&amp;nbsp; Conversations do, in fact, take place all over the place, and channels may be suitable mechanism for capturing and representing some conversations.&amp;nbsp; (Other conversations may be more complex--i.e., contain more information--than can be easily represented in an single channel, perhaps suggesting multiple channels, various typed associates, etc.)&lt;/p&gt;&lt;p&gt;The point of all this, of course, is that&amp;nbsp;&amp;quot;channel&amp;quot; and &amp;quot;conversation&amp;quot; are useful, related,&amp;nbsp;but &lt;em&gt;different&lt;/em&gt; concepts;&amp;nbsp;just as &amp;quot;building&amp;quot; and &amp;quot;home&amp;quot; are useful, related,&amp;nbsp;but different concepts.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;</Description>
            <ResourceTypeID ObjectClass="ResourceType" Title="Item:Content">10</ResourceTypeID>
            <ContentType>application/xml</ContentType>
            <ContentDocument>
             <ItemProperties>
                   <CommonProperties>
                    <Hidden>false</Hidden>

                    <Keywords>
                     <Keyword>channels</Keyword>

                     <Keyword>object model</Keyword>

       </Keywords>

      </CommonProperties>

                   <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>
           <UserPermissions>
            <CanDelete>false</CanDelete>
            <CanDiscover>true</CanDiscover>
            <CanEdit>false</CanEdit>
            <CanEditPermissions>false</CanEditPermissions>
            <CanRead>true</CanRead>
           </UserPermissions>
           <CommentInfo>
            <CommentChannelRef>
             <ChannelID/>
            </CommentChannelRef>
            <Comments/>
           </CommentInfo>
          </Item>
         </Comment>
        </Comments>
       </CommentInfo>
       <Views>
        <SourceID ObjectClass="Channel" Title="[Weblog] Blogsite News">76096</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>
