<?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="86" t0="1337229091691">
     <GetChannelItem_Result>
      <Item>
       <Resource>
        <ObjectID>9926</ObjectID>
        <ObjectClass>Resource</ObjectClass>
        <OwnerID ObjectClass="Domain" Title="[Weblog] Into the MyST">214</OwnerID>
        <CreatedByID ObjectClass="User" Title="bfrench">24</CreatedByID>
        <ModifiedByID ObjectClass="User" Title="aseidl">21</ModifiedByID>
        <CreateTime Title="2003-07-16 22:03:13 EDT">1058407393470</CreateTime>
        <ModifyTime Title="2007-10-28 00:38:06 EDT">1193546286314</ModifyTime>
        <SecurityModel>Controlled</SecurityModel>
        <Name>Weblogs: Public, Private, and Corporate</Name>
        <Summary>Smart people are starting to realize that blogs can represent 'channels' of information for different objectives.</Summary>
        <Description>
&lt;P&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif" size=2&gt;Most people look at 
me like I'm from a different planet when I advocate the use of multiple weblogs 
for different purposes, especially inside corporate environments. Typically, 
bloggers believe that weblogs are for one purpose - a personal journal; this is 
extremely narrow-minded thinking. A few bright people are starting to realize 
that they could be useful for customer-facing content, but they too carry 
baggage concerning the assumed use of blogs on the Public Web. Some go so far as 
to define what a blog must and must not have - rubbish - a blog doesn't need a 
'voice'; it could have hard facts and science - it's simply a medium for 
conveying information. Some of it may be subjective, some of it may be 
objective.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif" size=2&gt;Unfortunately very 
few companies realize the potential of friction-free, personal publishing for 
enterprise use, but Chad Dickerson get's it, and further recognizes that varying 
types of content need to be&amp;nbsp;streamed (or channeled) to different types of 
users and with secure methodologies.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif" size=2&gt;"&lt;EM&gt;Not everything 
I deal with on a daily basis can be distributed publicly, but there is still 
information that needs to be disseminated regularly and made available to a 
group on an ongoing basis&lt;/EM&gt;."&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif" size=2&gt;Chad correctly 
points out that corporate weblogs have a different set of requirements that 
revolve around security, permissions, and discovery. The blogging framework must 
be designed to meet these requirements.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif" size=2&gt;"&lt;EM&gt;I think one of 
the biggest mistakes people in corporate IT make is wrongly assuming that 
documentation is something that ends at some point. In reality, IT is an organic 
beast, and documentation is never really complete. Fortunately, the Weblog 
paradigm gives corporate IT the means to create documentation that works the way 
people think -- in dates (When did this happen to the system?), incidents (What 
happened, and how was it fixed?), and people (Who fixed it?). We've used the 
Groove discussion to manage the IT logistics of office moves, server migrations, 
and the RFP (request for proposal) process for Web hosting. This method of group 
documentation works better in practice than anything I've ever 
seen.&lt;/EM&gt;"&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="Verdana, Arial, Helvetica, sans-serif" size=2&gt;Chad also 
recognizes the need for chrono-based content; something that blogs tend to 
force. However, the architecture of the blog tool should allow other types of 
displays and content reuse that may require other formats (ergo, XSLT, XML-based 
persistence model, etc.).&lt;/FONT&gt;&lt;/P&gt;</Description>
        <ResourceTypeID ObjectClass="ResourceType" Title="Item:Link">9</ResourceTypeID>
        <ContentType>application/xml</ContentType>
        <ContentDocument>
         <ItemProperties>
               <CommonProperties>
       
                <Links>
                 <Link>
                  <Title>Weblogs meet the enterprise</Title>

                  <Synopsis>Whether it's public, internal, or personal communication, Weblogs fit the bill</Synopsis>

                  <URL>http://www.infoworld.com/article/03/07/11/27OPconnection_1.html</URL>

        </Link>

       </Links>

               <Hidden>false</Hidden>
        </CommonProperties>

              <RemoteInfo>
               <UserAgent>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; MyIE2; .NET CLR 1.0.3705; .NET CLR 1.1.4322)</UserAgent>

               <RemoteHost>66.17.237.47</RemoteHost>

               <RemoteAddr>66.17.237.47</RemoteAddr>

               <RemoteUser>bfrench</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">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>

