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

<?myst-baseUrl http://bfrench.info/public/?>

<MySmartChannels Public="true" UserID="91605" dT="113" t0="1268177142331">
     <GetChannelItem_Result>
      <Item>
       <Resource>
        <ObjectID>5994</ObjectID>
        <ObjectClass>Resource</ObjectClass>
        <OwnerID ObjectClass="Domain" Title="[Weblog] Weblogs, Portals, and KM">5936</OwnerID>
        <CreatedByID ObjectClass="User" Title="bfrench">24</CreatedByID>
        <ModifiedByID ObjectClass="User" Title="bfrench">24</ModifiedByID>
        <CreateTime Title="2003-04-22 16:49:49 EDT">1051044589126</CreateTime>
        <ModifyTime Title="2003-05-20 10:41:53 EDT">1053441713136</ModifyTime>
        <SecurityModel>Controlled</SecurityModel>
        <Name>Transforming Information into Knowledge at the Portal</Name>
        <Summary>E-mail is where knowledge goes to die.</Summary>
        <Description>
&lt;P&gt;&lt;FONT size=2&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif"&gt;On a daily 
basis almost every knowledge-worker reads news and other sources of business 
content and then creates comments and observations that other business 
associates, colleagues, customers, and vendors consume. The usual and customary 
method for creating annotations and observations is by e-mail. I have nothing 
against e-mail - in fact - my philosophical perspective is that SMTP and e-mail 
processes represent valuable collaboration tools for enterprises that cannot be 
discarded, but may certainly be optimized. However, the place where e-mail 
content comes to rest is problematic - &lt;EM&gt;e-mail is where knowledge goes to 
die&lt;/EM&gt;. &lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size=2&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif"&gt;Portals (such 
as &lt;A href="http://www.metadot.com/" target=_blank&gt;Metadot&lt;/A&gt;) are the primary 
delivery source of news feeds. Imagine a portal component that allows users to 
create annotations that tie one or more news or other information items together 
with annotation text. Further imagine that the annotations are stored in a 
knowledge channel that can then be consumed in many ways &amp;ndash; such as in a weblog, 
a report, an e-mail, or as an RSS news feed item. In most companies annotations 
and observations are typically created in e-mail with some messagestaining links 
that point out to specific information objects relevant to the message. Aside 
from the message itself, the knowledge dies a slow death in the inbox of office 
workers and executives. Creating a process so that annotations and business 
observations may live as uniquely addressable information objects, clearly has 
greater advantages; especially for portal users. &lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size=2&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif"&gt;Here's a 
scenario that might help organizations and teams transform information into 
reusable knowledge.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;FONT size=2&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif"&gt;The 
knowledge-worker uses a simple &amp;ldquo;annotate&amp;rdquo; button that has been integrated into 
news and other content feeds in Metadot.&lt;/FONT&gt;&lt;/FONT&gt; 
&lt;LI&gt;&lt;FONT size=2&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif"&gt;When a user 
selects an annotate button, MySmartChannels responds by displaying a dialog with 
entry fields for title, synopsis, etc. The user is free to enter observations 
and notes about the content item.&lt;/FONT&gt;&lt;/FONT&gt; 
&lt;LI&gt;&lt;FONT size=2&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif"&gt;The dialog 
automatically adds a link to the content that was selected to annotate. Multiple 
content items may be annotated under one channel item and multiple links are 
added dynamically to the open channel item dialog.&lt;/FONT&gt;&lt;/FONT&gt; 
&lt;LI&gt;&lt;FONT size=2&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif"&gt;Once the 
annotation is entered into a channel, it is available for consumption through 
many processes and knowledge-discovery tools. Additionally, the annotations are 
secure.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;&lt;FONT size=2&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif"&gt;&lt;EM&gt;&lt;U&gt;The 
benefits:&lt;/U&gt;&lt;/EM&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;FONT size=2&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif"&gt;&lt;U&gt;Complex 
annotations&lt;/U&gt; &amp;ndash; users may browse and assimilate items from multiple reports to 
create a single annotation that connects all report end-points;&lt;/FONT&gt;&lt;/FONT&gt; 
&lt;LI&gt;&lt;FONT size=2&gt;&lt;FONT 
face="Verdana, Arial, Helvetica, sans-serif"&gt;&lt;U&gt;Annotation templates&lt;/U&gt; - 
templates provide advanced classification, consistency of annotation items, and 
greater annotation productivity;&lt;/FONT&gt;&lt;/FONT&gt; 
&lt;LI&gt;&lt;FONT size=2&gt;&lt;FONT 
face="Verdana, Arial, Helvetica, sans-serif"&gt;&lt;U&gt;Annotation viewing&lt;/U&gt; &amp;ndash; 
annotations may be presented in Web pages, news feeds, portals, and other 
applications.&lt;/FONT&gt;&lt;/FONT&gt; 
&lt;LI&gt;&lt;FONT size=2&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif"&gt;&lt;U&gt;Expertise 
domains&lt;/U&gt; - annotations can be associated with other types of information 
objects;&lt;/FONT&gt;&lt;/FONT&gt; 
&lt;LI&gt;&lt;FONT size=2&gt;&lt;FONT 
face="Verdana, Arial, Helvetica, sans-serif"&gt;&lt;U&gt;Annotation syndication&lt;/U&gt; &amp;ndash; 
annotation content may be used in a syndicated form through native 
RSS;&lt;/FONT&gt;&lt;/FONT&gt; 
&lt;LI&gt;&lt;FONT size=2&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif"&gt;&lt;U&gt;XML and 
RSS&lt;/U&gt; &amp;ndash; flexible consumption support for all annotation content;&lt;/FONT&gt;&lt;/FONT&gt; 

&lt;LI&gt;&lt;FONT size=2&gt;&lt;FONT 
face="Verdana, Arial, Helvetica, sans-serif"&gt;&lt;U&gt;Publish-subscribe&lt;/U&gt; &amp;ndash; 
integrated publish, sharing, and subscription services;&lt;/FONT&gt;&lt;/FONT&gt; 
&lt;LI&gt;&lt;FONT size=2&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif"&gt;&lt;U&gt;Microsoft 
Office&lt;/U&gt; &amp;ndash; automatic linking to annotations from Microsoft Office XP 
documents.&lt;/FONT&gt;&lt;/FONT&gt;&lt;/LI&gt;&lt;/UL&gt;
&lt;P&gt;&lt;FONT face=Verdana size=2&gt;In my humble opinion,&amp;nbsp;this sounds like a more 
meaningful approach than e-mailing everything and everyone.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face=Verdana size=2&gt;&amp;nbsp;&lt;A 
href="mailto:bfrench@myst-technology.com"&gt;Let me know&lt;/A&gt; how you 
feel...&lt;/FONT&gt;&lt;/P&gt;&lt;FONT size=2&gt;
&lt;P&gt;--- bf&lt;/P&gt;&lt;/FONT&gt;</Description>
        <ResourceTypeID ObjectClass="ResourceType" Title="Item:Content">10</ResourceTypeID>
        <ContentType>application/xml</ContentType>
        <ContentDocument>
         <ItemProperties>
               <CommonProperties>
                <Hidden>false</Hidden>

      </CommonProperties>

     </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">174031</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>241769</ObjectID>
            <ObjectClass>Resource</ObjectClass>
            <OwnerID ObjectClass="Domain" Title="[Public] Public Comments">174031</OwnerID>
            <CreatedByID ObjectClass="User" Title="$Anonymous">173239</CreatedByID>
            <ModifiedByID ObjectClass="User" Title="$Anonymous">173239</ModifiedByID>
            <CreateTime Title="2009-09-25 02:20:45 EDT">1253859645750</CreateTime>
            <ModifyTime Title="2009-09-25 02:20:45 EDT">1253859645750</ModifyTime>
            <SecurityModel>Controlled</SecurityModel>
            <Name>RE: Transforming Information into Knowledge at the Portal</Name>
            <Summary/>
            <Description>To represent the data in the heading form is easy to understand for the users. In the same way the user has to be conscious while selecting the institution to attain the web hosting certificate and the best one is test king.&amp;nbsp;</Description>
            <ResourceTypeID ObjectClass="ResourceType" Title="Item:Link">9</ResourceTypeID>
            <ContentType>application/xml</ContentType>
            <ContentDocument>
             <ItemProperties>
                   <CommonProperties>
                    <Hidden>true</Hidden>

                    <Links>
                     <Link>
                      <Title>web hosting</Title>

                      <Synopsis/>

                      <URL>http://www.1-hit.com</URL>

        </Link>

       </Links>

      </CommonProperties>

                   <ns3:Details xmlns="urn:MyST-Technology.Structured.Details" xmlns:ns3="urn:MyST-Technology.Structured.Details">
                    <ns3:Collection name="denialjohn71" type="urn:MyST-Technology.Structured.Collection.Contact">
                     <ns3:Attribute name="EMail" type="email" value="denial.john574@gmail.com"/>

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

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

       </ns3:Collection>

      </ns3:Details>

                   <RemoteInfo>
                    <UserAgent>Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5 GTB5</UserAgent>

                    <RemoteHost>127.0.0.1</RemoteHost>

                    <RemoteAddr>127.0.0.1</RemoteAddr>

                    <ForwardedFor>124.29.218.88</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] Weblogs, Portals, and KM">5936</SourceID>

               <View>
                <Name>blog</Name>

                <Model>blogsite/BFrench/web</Model>

                <Style/>

                <Scheme/>

       </View>

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

                <Model>blogsite/BFrench/web</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>left</Name>

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

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>right</Name>

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

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>wide</Name>

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

                <Style/>

                <Scheme/>

       </View>

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

                <View>
                 <Name>blog</Name>

                 <Model>blogsite/BFrench/whatsnew</Model>

                 <Style/>

                 <Scheme/>

       </View>

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

                 <Model>blogsite/BFrench/web</Model>

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>left</Name>

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

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>right</Name>

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

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>wide</Name>

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

                 <Style/>

                 <Scheme/>

       </View>

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