RE: [ba-ohs-talk] Mobile HyperScope?
Saw your ideas posted on the OHS/DKR mailing list. Your ideas relate to
a software development project that I've been working on. I'm responding
personally rather than to the list because the application is not yet
publicly announced. (02)
What I've created is an outliner that runs on a server. The first
outline editor I've created is designed for IE/Windows, but other
editors would be possible. (03)
The outlines are stored in a database on the server, and are secured by
password. Security designed is such that controlled collaboration on
outlines by multiple authors is possible. (04)
Since the outline content is stored in a database and mapped to HTML,
other mappings are also possible. For example, I have a mapping to OPML,
which is an XML outline storage format designed by Dave Winer at
One of the features I've planned for this project, but have not yet
implemented, is to generate output that would be easily readable on
mobile devices. This might in fact be a collection of different
rendering formats, targeted to different devices. For example, a WML
rendering would be distinct from a "light" HTML rendering that's
formatted for small displays and simple navigation. (06)
I imagine editing would be limited. It would be limited to the most
likely use cases for mobile users. Perhaps it would only allow a user to
manipulate one record at a time rather than editing an entire document. (07)
Let me know whether this project seems related to the mobile OHS that
you have in mind. The existing feature set is small, but plans are big
and hands are few. We might be able to seed your project with work I've
Here's the Alpha web site: http://www.dynamiclsit.com/ (09)
San Francisco CA (010)
> -----Original Message-----
> From: email@example.com
> [mailto:firstname.lastname@example.org] On Behalf Of Teppo Raisanen
> Sent: Tuesday, January 14, 2003 5:27 AM
> To: ohs-talk
> Subject: [ba-ohs-talk] Mobile HyperScope?
> We are interested using HyperScope (and OHS) with different
> mobile devices (especially mobile phones and PDA's).
> Here are some random thoughs conserning our research:
> 1. HyperScope should be a server side application.
> Most of the work should be done on server and as little
> information as possible send to mobile device. This is
> because mobile devices lack the computing power and memory of
> a normal PC. Also with mobile devices bandwidth should not be wasted.
> So this HyperScope Server would transfer for example
> html-files to XML+ format which would then be transfered into
> WML (or other suitable format for mobile devices) with XSLT.
> 2. Special "Mobile HyperScope" should not be implemented.
> With XSLT XML+ files can be transfered to XHTML, WML or any
> other similar language. So HyperScope server could be
> accessed with web browsers, wap browsers etc.
> HyperScope server should be implemented in "mobile aware"
> way. (see http://www9.org/final-posters/poster23.html)
> 3. Problems will occur with screen size, editing documents
> and so on...
> Of course many problems will occur. Most of them are probably
> caused by small display (imagine reading a long document with
> a mobile phone).
> Also most of the mobile devices don't have proper keyboard for input.
> We are very interested about your comments. Especially about
> points 1 and 2. Also all the possible problems you can
> imagine will help us (we are planning on testing this at
> least on some level).
> Teppo Räisänen email@example.com
> University of Oulu, Finland (011)