<?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://myst-technology.com/public/styles/etc/object.xsl" type="text/xsl"?>

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

<MySmartChannels Public="true" UserID="125119" dT="333" t0="1328724251191">
     <GetChannelItem_Result>
      <Item>
       <Resource>
        <ObjectID>230076</ObjectID>
        <ObjectClass>Resource</ObjectClass>
        <OwnerID ObjectClass="Domain" Title="[Weblog] Into the MyST">214</OwnerID>
        <CreatedByID ObjectClass="User" Title="$Admin">1</CreatedByID>
        <ModifiedByID ObjectClass="User" Title="$Admin">1</ModifiedByID>
        <CreateTime Title="2009-04-06 22:24:08 EDT">1239071048420</CreateTime>
        <ModifyTime Title="2009-04-06 22:35:10 EDT">1239071710137</ModifyTime>
        <SecurityModel>Controlled</SecurityModel>
        <Name>Importance of Twitter Search Emerges, But The Infrastructure Also Holds Great Value</Name>
        <Summary>While marketers search for the silver-bullet in micro-blog search, many have missed the importance of new pipes that carry all the messages.</Summary>
        <Description>
One company, Gnip (&lt;a href="http://gnipcentral.com"&gt;gnipcentral.com&lt;/a&gt;) is quietly building the &amp;quot;listening post&amp;quot; for all conversational traffic.&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Gnip provides a convenient platform infrastructure that allows Web 2.0 services to publish their content flows. Everything happing in Twitter (and many other services including macro-blogs) is accessible today in Gnip.&amp;nbsp;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;More importantly, Gnip also provides mechanisms to consume information from the flows based on specific consumer &amp;quot;taps&amp;quot;; filtering mechanisms that allow content seekers to capture focused topic flows in real-time.&amp;nbsp;&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;Based on filtered flows, all sorts of information-centric applications can emerge. The true value of micro-blogging, macro-blogging, and nearly any type of social-centric content will someday stem from this plumbing system.&lt;/div&gt;</Description>
        <ResourceTypeID ObjectClass="ResourceType" Title="Item:Link">9</ResourceTypeID>
        <ContentType>application/xml</ContentType>
        <ContentDocument>
         <ItemProperties>
               <CommonProperties>
                <Hidden>false</Hidden>

                <Keywords>
                 <Keyword>Gnip</Keyword>

                 <Keyword>macro-blogging</Keyword>

                 <Keyword>micro-blogging</Keyword>

                 <Keyword>social media value</Keyword>

                 <Keyword>Twitter</Keyword>

       </Keywords>

                <Links>
                 <Link>
                  <Title>Utility Computing: A Business Model for the Twitter Economy?</Title>

                  <Synopsis>Given that FriendFeed, Twitter and eventually Gnip are popular because of the APIs they offer, who wins should not be the question. Instead of these applications being the destination that many people crave, they are just the enablers for future applications.</Synopsis>

                  <URL>http://mashable.com/2008/07/06/utility-computing/</URL>

        </Link>

                 <Link>
                  <Title>Google/Twitter Marriage Would Be Joyous Occasion For Marketers</Title>

                  <Synopsis>Twitter has the pulse on search to deliver the world's news, agreed Nicholas Graham, VP of communications at search engine Ask.com, and Richard Sim, VP of product management and marketing at Anchor Intelligence.</Synopsis>

                  <URL>http://www.mediapost.com/publications/?fa=Articles.showArticle&amp;art_aid=103460</URL>

        </Link>

                 <Link>
                  <Title>Gnip</Title>

                  <Synopsis>Data for the Real-time Web</Synopsis>

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

        </Link>

       </Links>

      </CommonProperties>

               <ns3:Details xmlns="urn:MyST-Technology.Structured.Details" xmlns:ns3="urn:MyST-Technology.Structured.Details">
                <ns3:Collection name="Bill French" type="urn:MyST-Technology.Structured.Collection.Contact">
                 <ns3:Attribute name="Company" type="text"/>

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

                 <ns3:Attribute name="Address" type="location"/>

                 <ns3:Attribute name="EMail" type="email"/>

                 <ns3:Attribute name="EMail2" type="email"/>

                 <ns3:Attribute name="Work" type="phone"/>

                 <ns3:Attribute name="Mobile" type="phone"/>

                 <ns3:Attribute name="Home" type="phone"/>

                 <ns3:Attribute name="Skype" type="skype"/>

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

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

                 <ns3:Attribute name="Twitter" type="twitter"/>

                 <ns3:Attribute name="Photo (L)" type="url:image"/>

                 <ns3:Attribute name="Photo (M)" type="url:image"/>

                 <ns3:Attribute name="Photo (S)" type="url:image"/>

                 <ns3:Attribute name="Notes" type="large-text"/>

       </ns3:Collection>

                <ns3:Collection name="Quote" type="urn:MyST-Technology.Structured.Collection.Captyx.Quote">
                 <ns3:Attribute name="Quote" type="large-text">
                  <ns3:Value>Given that FriendFeed, Twitter and eventually Gnip are popular because of the APIs they offer, who wins should not be the question. Instead of these applications being the destination that many people crave, they are just the enablers for future applications.</ns3:Value>

        </ns3:Attribute>

                 <ns3:Attribute name="Name" type="text" value="Rob Diana"/>

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

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

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

                 <ns3:Attribute name="Web" type="url" value="http://mashable.com/2008/07/06/utility-computing/"/>

                 <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/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/1.0.154.53 Safari/525.19</UserAgent>

                <RemoteHost>127.0.0.1</RemoteHost>

                <RemoteAddr>127.0.0.1</RemoteAddr>

                <RemoteUser>$Admin</RemoteUser>

                <ForwardedFor>67.172.146.66</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">190014</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] Into the MyST">214</SourceID>

               <View>
                <Name>blog</Name>

                <Model>blogsite/MySTHome/web</Model>

                <Style/>

                <Scheme/>

       </View>

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

                <Model>blogsite/MySTHome/web</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>left</Name>

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

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>right</Name>

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

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>wide</Name>

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

                <Style/>

                <Scheme/>

       </View>

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

                <View>
                 <Name>blog</Name>

                 <Model>blogsite/MySTHome/whatsnew</Model>

                 <Style/>

                 <Scheme/>

       </View>

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

                 <Model>blogsite/MySTHome/web</Model>

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>left</Name>

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

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>right</Name>

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

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>wide</Name>

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

                 <Style/>

                 <Scheme/>

       </View>

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

