An example of this is Pocket Blog, http://www.pocketblog.com. I have
used it to enter blog entries on my Pocket PC, and then publish them
to an internal Radio weblog when I got back to the office.

--- In klogs@y..., "xmlwriter03842" <peterharbeson@m...> wrote:
> If you generalize this a bit, I think you have just two cases:
>
> A mobile device with an input method and a live connection to a
> database/site generation/syndication system behind a firewall.
>
> A mobile device with an input method and local storage with
> some sort of synchronization system to a "home" system.
>
> A third possible case is where the storage is decentralized and
> the mobile device contains a database/site generation/
> syndication system, and is connected continuously to the
> organization's network.
>
> Allow for at least the first two cases, add a reasonable degree of
> device independence (see http://www.w3.org/2001/di/)
> and you'd have a pretty good system for the "klogging" portion of
> your knowledge management system.
>
> It seems to me it would be particularly useful to tag messages
> with metadata about where an item was written. As well as other
> things, of course. And this metadata would ideally enable you to
> integrate the klogging system with other sources of information,
> giving you more complete knowledge management capabilities.
> I'd bet on RDF (see http://www.w3.org/RDF/) as the way
> to go for klog metadata.
>
> -Pete Harbeson
> peterharbeson@m...
> www.infoliage.com/blog.html
>
> --- In klogs@y..., "John Robb" <jrobb@u...> wrote:
> > Dear K-Loggers,
> >
> ...
>
> > There are three modes of remote K-Logging. They are:
> >
> > 1) Remote access to a K-Log through a browser on a random
> PC. K-Log tools
> > that are located on a server or desktop PC (through remote
> access settings)
> > can be accessed while on the road as long as the systems
> can be accessed from
> > outside he corporate firewall via a variety of connection
> techniques (VPN,
> > VNC, Microsoft Terminal Server, browsers equiped with
> certificates, etc).
> >
> > 2) Mobile laptop with a local K-Log tool. With a laptop K-
> Logging tool,
> > employees can K-Log while on a plane, in a hotel room, and in
> a client
> > meeting -- all while disconnected. When they reconnect, the
> publishing
> > process is fast and efficient as K-Log updates on the desktop
> are published
> > to the host. Additionally, news headlines are downstreamed to
> the laptop.
> > This is very similar in concept to the efficient e-mail
replication
> found in
> > Lotus Notes (and what made it successful). This is also what
> I do
> > personally.
> >
> > 3) Remote K-Logging via e-mail. E-mail works great as a way
> to post updates
> > to a K-Log tool on the desktop or server while on the road
> without a laptop.
> > Many employees now use e-mail enabled devices like
> Blackberries and wireless
> > Palms. These tools don't support high quality browsing, but
> they do a
> > fairly good job with e-mail. For those employees that want to
> make an
> > immediate post to their K-Log via a Blackberry while stuck in
> traffic, the
> > e-mail to K-Log feature is the best way to go.
> >
> > E-mail to K-Log is also a great way to build a group or team K-
> Log using a
> > desktop K-Log tool. In many respects, this is very much like a
> private
> > Yahoo Group, but done with a K-Log tool on a desktop PC
> inside the corporate
> > firewall. All participating employees are given an e-mail
> address to send
> > updates to. All e-mails from these employees are aggregated
> by the K-Log
> > tool and posted to the Intranet. It would require a minor
> modification to
> > the K-Log tool to send e-mails back to the participating
> employees on a per
> > post or daily summary basis.
> >
> > Sincerely,
> >
> > John Robb
> >
> > Personal Weblog: http://jrobb.userland.com