<?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="346" t0="1231439655612">
     <GetChannelItem_Result>
      <Item>
       <Resource>
        <ObjectID>186459</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="aseidl">21</ModifiedByID>
        <CreateTime Title="2007-10-14 22:44:19 EDT">1192416259606</CreateTime>
        <ModifyTime Title="2008-03-22 10:27:15 EST">1206199635965</ModifyTime>
        <SecurityModel>Controlled</SecurityModel>
        <Name>The Difference Between [Desktop] Search and Mobile Search</Name>
        <Summary>The definition of "mobile content" is rapidly changing -- but one aspect is constant - quality content is important to people on the move.</Summary>
        <Description>&lt;p&gt;A technology partner familiar with mobile content recently echoed an industry expert who suggests&amp;nbsp;&lt;em&gt;mobile search&lt;/em&gt; is all about advertising and discovery of mobile-specific content.&lt;/p&gt;&lt;p&gt;I agree with the first part - pretty much &lt;u&gt;&lt;em&gt;everything&lt;/em&gt;&lt;/u&gt; is about advertising. But I strongly disagree with the second part - the Internet and mobile devices have become very&amp;nbsp;good buddies. The release of&amp;nbsp;the iPhone and specifically, the rapid maturity of the Safari browser driven by the &lt;a href="http://webkit.org/"&gt;WebKit Open Source Project&lt;/a&gt;, have transformed the definition of &amp;quot;mobile content&amp;quot;.&amp;nbsp;With my iPhone I can access almost 100% of the content I presently access with my dual 20&amp;quot; displays.&lt;/p&gt;&lt;p&gt;But there's more to this than you might think. Consider the rapid pace that Google has set for mobility in general; the gPhone is comming, everything about Google is ad-based, the Google Web Toolkit is based on WebKit, and Google is busy &lt;a href="http://en.wikipedia.org/wiki/GPhone#Google_files_for_GPhone_payment_patent"&gt;filing patents&lt;/a&gt; that are mobile-friendly.&lt;/p&gt;&lt;p&gt;I see a bright future for mobile search because the world will soon be flooded with devices that can interoperate without the limitations that caused us to think of mobile search as something entirely differen from [desktop] search.&lt;/p&gt;&lt;p&gt;There are still some things that you'll have to consider to pave the way for greater findability and consumption of your content with these new devices and browser technologies.&amp;nbsp; At MyST we're constantly thinking about ways to make sure your advertorial content is indexable, discoverable, and consumable from mobile devices.&amp;nbsp; With its strong XML infrastructure, Blogsite can integrate with existing mobile content distributors. &lt;/p&gt;&lt;p&gt;You can see an example of&amp;nbsp;two mobile integrations&amp;nbsp;at &lt;a href="http://news.ridecme.com/"&gt;RideCME&lt;/a&gt;, &lt;a href="http://www.cmex.com/"&gt;Colorado Mountain Express&lt;/a&gt;' blogsite. For mobile content consumers they provide a special &lt;a href="http://news.ridecme.com/public/item/152792"&gt;Mobile Phone Ski Report&lt;/a&gt; notification service that leverages their RSS content using Bloglines' new mobile service (&lt;a href="http://m.beta.bloglines.com/"&gt;http://m.beta.bloglines.com/&lt;/a&gt;). &lt;/p&gt;&lt;p&gt;CME is also&amp;nbsp;experimenting with a new mobile subscription and access platform from &lt;a href="http://www.buzmob.com/"&gt;BuzMob&lt;/a&gt; which makes it easy to &lt;a href="http://m.buzmob.com/urlsms.php?page=cme"&gt;subscribe&lt;/a&gt; to and read CME content from almost any cell phone including the iPhone.&lt;/p&gt;&lt;p&gt;Take a few moments to watch this &lt;a href="http://web.mac.com/bill.french/iWeb/Site/CME%20Blogsite%20iPhone%20Mobile%20Experience.html"&gt;video&lt;/a&gt; - it demonstrates some of these new mobile ideas, and please drop us a comment if you know of other mobile content services you'd like us to integrate with.&lt;/p&gt;</Description>
        <ResourceTypeID ObjectClass="ResourceType" Title="Item:Link">9</ResourceTypeID>
        <ContentType>application/xml</ContentType>
        <ContentDocument>
         <ItemProperties>
               <CommonProperties>
                <Hidden>false</Hidden>

                <Keywords>
                 <Keyword>Google Web Toolkit</Keyword>

                 <Keyword>mobile content</Keyword>

                 <Keyword>mobile search</Keyword>

                 <Keyword>Safari</Keyword>

                 <Keyword>WebKit</Keyword>

       </Keywords>

                <Links>
                 <Link>
                  <Title>Google Web Toolkit 1.2 Uses WebKit</Title>

                  <Synopsis>GWT allows web developers to create shiny AJAX web applications entirely in Java, which GWT compiles to JavaScript.</Synopsis>

                  <URL>http://webkit.org/blog/81/google-web-toolkit-12-uses-webkit/</URL>

        </Link>

                 <Link>
                  <Title>The WebKit Open Source Project</Title>

                  <Synopsis>WebKit is an open source web browser engine.</Synopsis>

                  <URL>http://webkit.org/</URL>

        </Link>

                 <Link>
                  <Title>gPhone Rumors Abound</Title>

                  <Synopsis>Speculation has ranged from ideas that the search giant might build a revolutionary device that rivals Apple?s iPhone and provide free mobile services to more tame ideas that Google is likely to provide software that will be embedded within many mobile devices of the future.</Synopsis>

                  <URL>http://accuracast.com/search-daily-news/mobile-7471/rumours-about-gphone-googles-mobile-device-abound/</URL>

        </Link>

       </Links>

      </CommonProperties>

               <ns3:Details xmlns="urn:MyST-Technology.Structured.Details" xmlns:ns3="urn:MyST-Technology.Structured.Details">
                <ns3:Collection name="Captioned Image" type="urn:MyST-Technology.Structured.Collection.Captyx.Captioned_Image">
                 <ns3:Attribute name="Image Source" type="url:image" value="http://blogs.sun.com/jonathan/resource/JavaFX_Mobile.png"/>

                 <ns3:Attribute name="Image Height" type="number"/>

                 <ns3:Attribute name="Image Width" type="number" value="250"/>

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

                 <ns3:Attribute name="Image Class" type="text"/>

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

                 <ns3:Attribute name="Link" type="url" value="http://blogs.sun.com/jonathan/entry/when_not_where"/>

                 <ns3:Attribute name="Tooltip" type="text" value="Speculation has ranged from ideas that the search giant might build a revolutionary device that rivals Apple?s iPhone and provide free mobile services to more tame ideas that Google is likely to provide software that will be embedded within many mobile devices of the future."/>

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

                 <ns3:Attribute name="Caption" type="text" value="Google gPhone?"/>

                 <ns3:Attribute name="Caption Link" type="url" value="http://en.wikipedia.org/wiki/GPhone"/>

                 <ns3:Attribute name="Caption Tooltip" type="text" value="Google Phone (or gPhone) is a potential mobile phone or smartphone speculated to be connected with search engine giant Google."/>

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

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

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

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

                 <ns3:Attribute name="Container Style" type="text" value="float:right; padding-left:4px; text-align:center;"/>

                 <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>
         <Comment>
          <Item>
           <Resource>
            <ObjectID>186463</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="2007-10-15 00:44:41 EDT">1192423481102</CreateTime>
            <ModifyTime Title="2008-01-19 20:57:54 EST">1200794274867</ModifyTime>
            <SecurityModel>Controlled</SecurityModel>
            <Name>Mobile search vs. Search from your Mobile...</Name>
            <Summary>(currently) the two do not mean the same thing</Summary>
            <Description>&lt;p&gt;I agree with everything you wrote, but (there's always a &amp;quot;but&amp;quot;)... what you are describing is performing a &amp;quot;web search&amp;quot; from a mobile device.&amp;nbsp; In effect, there is nothing inherently &amp;quot;mobile&amp;quot; about what you do - you use the exact same search engine (and browser) you would on your PC.&amp;nbsp; You're likely to obtain the same result set as well, unless your operator shares location/behavioral information with your search engine of choice (hmm... privacy concerns anyone?).&lt;br /&gt;&lt;br /&gt;&amp;quot;Mobile search&amp;quot;, as an industry, currently does not refer to this at all, which is why the term &amp;quot;mobile search&amp;quot; is somewhat misleading.&amp;nbsp; For the +2B mobile users out there who do not have Safari, and who are unlikely to have such sophisticated devices anytime soon, search is about discovering &amp;quot;mobile friendly&amp;quot; services and mobile content - mobile friendly websites, mobile downloadables such as videos, ringtones, games, etc.&amp;nbsp; The search engines they have access to are typically provided by the carrier (pre-installed on the device).&amp;nbsp; They (the engines) index the carrier's content deck first, and then (if at all) the rest of the world.&lt;/p&gt;&lt;p&gt;I've no doubt that the future will see the demise of mobile search, in favor of a cross-platform (web)search.&amp;nbsp; The mobile device will simply be another access point to the &amp;quot;generic&amp;quot; search platform.&amp;nbsp; &lt;br /&gt;&lt;br /&gt;--- Oren&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>mobile search</Keyword>

       </Keywords>

      </CommonProperties>

                   <ns3:Details xmlns="urn:MyST-Technology.Structured.Details" xmlns:ns3="urn:MyST-Technology.Structured.Details">
                    <ns3:Collection name="Oren" type="urn:MyST-Technology.Structured.Collection.Contact">
                     <ns3:Attribute name="EMail" type="email" value="oren.friedman@contec.ca"/>

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

       </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>186542</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="2007-10-15 20:24:15 EDT">1192494255971</CreateTime>
            <ModifyTime Title="2008-01-27 11:57:38 EST">1201453058813</ModifyTime>
            <SecurityModel>Controlled</SecurityModel>
            <Name>The mobile device will simply be another access point to the "generic" search platform.</Name>
            <Summary>Oren - I think we are saying the same thing (if not agreeing on the eventual outcome).</Summary>
            <Description>&lt;p&gt;However, I think the mobile service providers may be underestimating the market in two ways -&lt;/p&gt;&lt;ol&gt;&lt;li&gt;&lt;font face="Verdana" size="2"&gt;Customers want freedom of choice&lt;/font&gt;&amp;nbsp;- forcing them to take a specific [constrained] view of the &amp;quot;Web&amp;quot; is likely to create dissatisfaction (over time).&lt;/li&gt;&lt;li&gt;Technology providers (the device and software manufacturers) are continually improving on the lack-luster performance; both speed and browser agility.&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;&lt;font face="Trebuchet MS"&gt;I believe these two dimensions are converging very quickly to create disruption - probably very soon for business users. Even a dated product such as a Treo 650 has a decent browsing experience that doesn't require proprietary search and content services for search tasks.&lt;/font&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>mobile search</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>
         <Comment>
          <Item>
           <Resource>
            <ObjectID>186549</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="2007-10-15 22:36:41 EDT">1192502201813</CreateTime>
            <ModifyTime Title="2008-01-19 21:00:11 EST">1200794411310</ModifyTime>
            <SecurityModel>Controlled</SecurityModel>
            <Name>This just in...</Name>
            <Summary>Yahoo! Mobile Search, Aligns with Telefonica, to Service Over 100 Million</Summary>
            <Description>&lt;p&gt;&lt;font face="Trebuchet MS"&gt;If &lt;a href="http://www.webhostingtalk.com/news/yahoo-mobile-search-aligns-with-telefonica-to-service-over-100-million/"&gt;partnerships like this&lt;/a&gt; are happing as we type, (i) there must huge be demand for open and unfettered [common] search, and (ii) devices and their embedded browsers have now become advanced enough to use&amp;nbsp;open mobile search solutions&amp;nbsp;such as m.yahoo.&lt;/font&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>mobile search</Keyword>

                     <Keyword>Telefonica</Keyword>

                     <Keyword>Yahoo</Keyword>

       </Keywords>

                    <Links>
                     <Link>
                      <Title>Yahoo! Mobile Search, Aligns with Telefonica, to Service Over 100 Million</Title>

                      <Synopsis>Under the terms of the agreement, the search solution has the potential to reach more than 100 million consumers worldwide. Telefonica's local subsidiaries agree to offer Yahoo! oneSearch as the search engine partner on their mobile portals in Ireland, Latin America and the UK -- Telefonica will also integrate Flickr and Yahoo! Mail into its portfolio of mobile Internet services.</Synopsis>

                      <URL>http://www.webhostingtalk.com/news/yahoo-mobile-search-aligns-with-telefonica-to-service-over-100-million/</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>
        </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>
