THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700


S U M M A R Y


DIARY: August 18, 2000 03:16 PM Friday; Rod Welch

DKR development plan focused by Eugene Kim on email, Augment.

1...Summary/Objective

ACTION ITEMS.................. Click here to comment!

1...1. Architecture and design for stage one: e-mail archiving.

CONTACTS 

SUBJECTS
OHS/DKR Development Plan
Focus Project Priorities, Eugene Kim
Architecture Finalize, Doug Meeting with Key People, Eugene Kim
Email Enhancement Tools, Hackable, 000428
DTD Email, Augment, Grant, Shinya, Eugene Kim
Client Mockups, Prototypes, Sheldon, Paul, Eugene Kim
OHS Development Vector, Doug, 000405
OHS Development Vector, Doug, 000419
Prototype Software Programming Multiple Views, Doug, 000608
Architecture Finalize, Doug Engelbart, Eugend Kim
Mock Up Screens Being Developed by Sheldon
Mozilla, DirectDom, JDOM Processors of XML DKR, 000427, Jack Park

4114 -    ..
4115 - Summary/Objective
4116 -
411601 - Follow up ref SDS 29 0000, ref SDS 27 0000.
411602 -
411603 - Received ref DRT 1 0001 from Eugene Kim following up correspondence on
411604 - 000812 discussing the sequence for project development, for example
411605 - Grant Bowman's letter, ref DRP 1 0001 responding to a letter submitted
411606 - to the DKR team by Eric Armstrong.
411607 -
411608 - Eugene says today that technical discussion has been going all over
411609 - the place on the list; he proposes people focus on...
411610 -
411611 -    1. Architecture and design for stage one: e-mail archiving.
411612 -       ref DRT 1 WH6L
411613 -
411614 -       Doug is meeting with several people individually to try to come
411615 -       up with a unified architecture, which we can then propose to the
411616 -       community at large.  Even if you are not one of those people
411617 -       Doug is meeting with initially, you can make some important
411618 -       contributions to the design, especially by commenting on some of
411619 -       the documents that have been produced
411620 -       and that will be produced.
411621 -       ..
411622 -    2. Augment->XML->HTML. ref DRT 1 AB7L
411623 -
411624 -       Shinya has done an initial translator, and Grant is going to
411625 -       help here also.  Hopefully, the two will start reporting on
411626 -       their progress on this list, especially so that others can start
411627 -       giving feedback.  Once an initial translator is up, this will
411628 -       have ramifications for the item above, because Doug will be able
411629 -       to put up many of his design notes and documentation from years
411630 -       past.
411631 -
411632 -    3. E-mail DTD and Augment DTD. ref DRT 1 PB8K
411633 -
411634 -       I proposed the former already, but it's nowhere close to ready
411635 -       for primetime.  I'm going to go over some specs this weekend to
411636 -       try to solve some of the outstanding issues, but help is always
411637 -       useful.  Grant and Shinya are ostensibly working on an Augment
411638 -       DTD.
411639 -
411640 -       If you want to contribute to these areas, the best thing you can
411641 -       do is absorb the appropriate XML specs, especially XLink and
411642 -       XPointer.  I know it would be useful for me if I had someone to
411643 -       kick ideas and questions off of regarding these technologies.
411644 -       ..
411645 -    4. Client mockups and prototypes. ref DRT 1 MC9M
411646 -
411647 -       The debate over what technologies we should assume in the
411648 -       clients are premature, in my opinion.  The first step should be
411649 -       to mockup potential user interfaces.  Sheldon is working on this
411650 -       right now, but other contributions would be great.
411651 -
411652 -       These mockups could be in the form of images or prototypes.
411653 -
411654 -          [On 000928 Eugene cites work on mock ups in progress report.
411655 -          ref SDS 30 3B6K
411656 -       ..
411657 -       Based on feedback from Eric and others, I'm convinced that
411658 -       we need to mockup a number of clients.  One absolutely needs to
411659 -       be web-based (HTML 4.0).  But we also need one or more
411660 -       prototypes that demonstrate fancier functionality.  These would
411661 -       not only demonstrate the direction the OHS is headed, but it may
411662 -       also persuade people, such as the Helix Code and Mozilla folks,
411663 -       to modify existing client software to incorporate the
411664 -       functionality of the OHS.  I think Python would be a great
411665 -       technology to use for these prototypes, and I hope Paul or
411666 -       others can offer advice or contribute in these areas.
411667 -
411668 -             [On 001101 Mozilla example of open source projects have
411669 -             overwhelming tendency to use bad management. ref SDS 31
411670 -             O5K
411671 -
411672 -           So far, there is no OHS/DKR, and so there is no
411673 -           functionality to incorporate.  On 000427 Jack Park cited
411674 -           Mozilla DirectDom as guidance for OHS/DKR design.
411675 -           ref SDS 5 1092
411676 -
411677 -           On 000515 Lee Iverson requested volunteers to evaluate
411678 -           Mozilla source code. ref SDS 14 G34I
411679 -
411680 -           There is no record that anything has been done.
411681 -
411682 -
411683 -
411684 -
411685 -
411686 -
411687 -
411688 -
411689 -
411690 -
411691 -
4117 -