<?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="89" t0="1231442141697">
     <GetChannelItem_Result>
      <Item>
       <Resource>
        <ObjectID>171612</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="2007-06-09 13:25:36 EDT">1181409936378</CreateTime>
        <ModifyTime Title="2007-12-10 12:23:40 EST">1197307420085</ModifyTime>
        <SecurityModel>Controlled</SecurityModel>
        <Name>Embarrasing and Unintended Relationships Emerge in RSS Feeds -- May Affect Your Brand Reputation</Name>
        <Summary>Terry Heaton is a brand and his brand reputation is important. But Web 2.0 creates the opportunity for runaway problems in RSS mashups.</Summary>
        <Description>&lt;p&gt;I caught a glimpse of &lt;a title="Nude Nurses Snuck Into Terry's Feed" href="http://www.intuitive.com/blog/nude_japanese_nurses_snuck_into_terrys_rss_feed.html" target="_blank"&gt;Terry's problem&lt;/a&gt; on the &lt;a title="Intuitive Life Business Blog" href="http://www.intuitive.com/blog/index.shtml" target="_blank"&gt;Intuitive Life Business Blog&lt;/a&gt; (Dave Taylor).&lt;/p&gt;&lt;p&gt;Whenever mass quantities of disparate information are aggregated into one spot, the likelihood of unintended assimilations grow - perhaps exponentially (I'm no math genius). &lt;/p&gt;&lt;p&gt;We build and manage a fair number of mashup feeds based on a variety of content sources, but we've learned that (for business purposes) trusted content sources represent the only viable approach to leveraging external content. But even so, there still remains a slight risk of getting bad content. We use Google's API, Google News, and specifically targeted domains to build both internal intelligence and customer-facing content aggregations. Sometimes we use other known and trusted feeds. &lt;/p&gt;&lt;p&gt;Our automated (MyST-X) services leverage RSS resources and re-deilver the results as secure (or public) HTML pages and also offer RSS feeds depending on the business requirement. To further manage the slight risk of attracting unintended hits, we provide our customers with a content review process that allows them to jettison any information of questionable origin or deemed unsuitable. Once an item (or domain) is given the boot, our services monitor all feeds (not just the one where the nefarious item was discovered) and never allows the content in. Lastly, we provide specific configuration commands that can be employed to filter incoming content with great prejudice, lowering the risk of poor quality items long before the feed is constructed. &lt;/p&gt;&lt;p&gt;In the case of Terry's situation, the &lt;a title="Wikipedia: Semantic Web" href="http://en.wikipedia.org/wiki/Semantic_Web" target="_blank"&gt;semantic web&lt;/a&gt; has proven to be not so semantically astute. ;-) It's not surprising - most of us understand why this happens, but what we didn't anticipate was the rapid adoption of &amp;quot;persistent search&amp;quot; - i.e., the ability for anyone to create a search feed that's always fresh with new discoveries. This is a very powerful idea because it provides a way for content to find &lt;u&gt;&lt;strong&gt;you&lt;/strong&gt;&lt;/u&gt; in your news reader (instead of the other way around). However, when search feeds are poorly constructed, you're likely to get lots of crap. This represents one definition of a low-quality feed. &lt;/p&gt;&lt;p&gt;&lt;em&gt;How does Terry (or anyone or any business) combat this problem? &lt;/em&gt;&lt;/p&gt;&lt;p&gt;Ironically, the same approach that created the problem, also provides a&amp;nbsp;solution - create an intelligence service based on persistent searches that comprehensively watch for assimilations of your business brand with terms you might not like to see. There are many ways to do this - my favorite is &lt;a title="MyST Blogsite"&gt;Blogsite&lt;/a&gt; of course, but &lt;a title="Yahoo! Pipes: Rewire the Web" href="http://pipes.yahoo.com/pipes/" target="_blank"&gt;YahooPipes&lt;/a&gt; is also a great place to create and manage your own intelligence dashboard. &lt;/p&gt;</Description>
        <ResourceTypeID ObjectClass="ResourceType" Title="Item:Link">9</ResourceTypeID>
        <ContentType>application/xml</ContentType>
        <ContentDocument>
         <ItemProperties>
               <CommonProperties>
                <Hidden>false</Hidden>

                <Keywords>
                 <Keyword>briefings</Keyword>

                 <Keyword>Dave Taylor</Keyword>

                 <Keyword>intelligence</Keyword>

                 <Keyword>Intuitive Life Business Blog</Keyword>

                 <Keyword>persistent search</Keyword>

                 <Keyword>RSS mashups</Keyword>

                 <Keyword>Terry Heaton</Keyword>

       </Keywords>

                <Links>
                 <Link>
                  <Title>The Intuitive Life Business Blog</Title>

                  <Synopsis>Dave Taylor has been involved with the Internet since 1980 and is widely recognized as an expert on both technical and business issues. He has been published over a thousand times, launched four Internet-related startup companies, has written twenty business and technical books and holds both an MBA and MS Ed.</Synopsis>

                  <URL>http://www.intuitive.com/blog/index.shtml</URL>

        </Link>

                 <Link>
                  <Title>Terry Heaton's PoMo Blog</Title>

                  <Synopsis>Postmodernism is a change-or-be-changed world. The word is out: Reinvent</Synopsis>

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

        </Link>

                 <Link>
                  <Title>Yahoo! Pipes</Title>

                  <Synopsis>Rewire the web.</Synopsis>

                  <URL>http://pipes.yahoo.com/pipes/</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="&quot;Japanese Nurses snuck into Terry's RSS feed&quot;"/>

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

                 <ns3:Attribute name="Image" type="url" 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; 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>71.196.246.102</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>
