CONTACTS 
0201 - Minciu Sodas Laboratory              011 370 2 60 67 38
020101 - Mr. Andrius Kulikauskas, Ph.D.; Director =619 298 7019
020102 - ms@ms.lt

SUBJECTS
Document Management
OHS, Email
Integrate Email Hyperdocuments
Open Hyperdocument System (OHS)

1307 -
1307 -    ..
1308 - Summary/Objective
1309 -
130901 - Follow up ref SDS 49 0000, ref SDS 47 0000.
130902 -
130903 - Eric submits a detailed explanation of a document system, which seems
130904 - effective for collaboration on producing documents, rather than to
130905 - facilitate performance of the work.
130906 -
130907 -
130908 -
1310 -
1311 -
1312 - Progress
1313 -
131301 -  ..
131302 - OHS and Email Detailed Outline Specification
131303 -
131304 - Follow up ref SDS 49 3596, ref SDS 46 3867.
131305 -
131306 - Received ref DRT 1 0001 from Eric providing design requirements for
131307 - document management, previously described on 000208 as integrating
131308 - Open Hyperdocument System and Email. ref SDS 49 3596
131309 -
131310 - He indicates XML is basis of Editor, per design ideas submitted on
131311 - 000129, ref SDS 48 0957, but this could be changed. ref DRT 1 2820
131312 -  ..
131313 -
131314 -      [On 000326 Traction manages email with web journal system that
131315 -      may accomplish DKR objective; does not mention XML. ref SDS 51
131316 -      5877
131317 -
131318 -  ..
131319 -
131320 - On 000124 a series of document management issues were identified for
131321 - consideration in preparing a design. ref SDS 44 4130
131322 -
131323 - Generally, this design supports the process of document preparation,
131324 - but not document "management" that is needed to facilitate daily
131325 - management, i.e., it is not clear how this capability supports the
131326 - ordinary needs of managing meetings, calls, and using documents like
131327 - formal correspondence, books, articles and memos.  Eric's design seems
131328 - excellent for collaborative tasks like preparing a contract, a brief,
131329 - a specification, where the document is the work product, as discussed
131330 - at the KMCI meeting on 991217. ref SDS 40 0196
131331 -
131332 - On 940114 differences between document preparation and the process of
131333 - generating knowledge for daily management, were reviewed. ref SDS 4
131334 - 4928
131335 - ..
131336 - Eric does not address today the concern on 00125 that capability
131337 - to expose knowledge of complexity would be overwhelming. ref SDS 46
131338 - 3975
131339 -
131340 - More thought is needed for a system to manage meetings, calls, email,
131341 - and using documents in planning and performing daily management on a
131342 - broader scale, for example solving the big problems others have in
131343 - mind.
131344 -
131345 -  ..
131346 - Functional overview, ref DRT 1 4884, lists following...
131347 -
131348 -        •  Authoring Documents
131349 -        •  Receiving Documents
131350 -        •  Browsing Documents
131351 -        •  Responding to Documents
131352 -        •  Receiving Responses
131353 -        •  Revising Documents
131354 -        •  Receiving New Versions
131355 -        •  Backpedalling
131356 -
131357 -      [On 000305 Xanadu project appears to address these objectives and
131358 -      may have source code for implementation. ref SDS 50 0782]
131359 -                               ..
131360 -   This list might add following to support "managment"
131361 -   requirements...
131362 -       ..
131363 -       Tools for quickly identifying documents in knowledge space
131364 -       according to organizational objectives, per POIMS. ref OF 1 1110
131365 -
131366 -       Differentiate formal correspondence from "Other Documents" per
131367 -       POIMS. ref OF 1 1107
131368 -
131369 -       Subject - organic structure to organize knowledge space, per
131370 -       POIMS. ref OF 1 1110
131371 -
131372 -          Multiple assignments to documents and other stuff
131373 -
131374 -       Description
131375 -       Date received
131376 -       Date issued
131377 -       Response due
131378 -          ..
131379 -          Who When
131380 -
131381 -       Publications
131382 -
131383 -          Publisher, author
131384 -
131385 -
131386 -      ..
131387 -     Authoring Documents
131388 -     Hierarchially Structured Document
131389 -
131390 -     Eric says
131391 -
131392 -     You are working in an XML-editor of some kind, operating on a
131393 -     hierarchically structured document to which you can add links.
131394 -     Every change you make is time-stamped or given a unique internal
131395 -     version number. Every node you create lists you as its author.
131396 -     ref DRT 1 7656
131397 -
131398 -  ..
131399 -         What is a hierarchially structured document?
131400 -
131401 -            Is there a source that defines this?
131402 -
131403 -         What is a change?
131404 -
131405 -            Everytime a character is entered, it changes the document.
131406 -            When do changes begin to be time stamped?  Is there a
131407 -            procedure for releasing an initial document that then sets
131408 -            it up for changes?
131409 -
131410 -         Why time stamp all changes, rather than those designated by
131411 -         the author?
131412 -         ..
131413 -         This will be a lot of stuff to track.  How reliable will
131414 -         this system be.  What happens when there is a glitch of some
131415 -         kind, and everything gets mixed up, how difficult will it be
131416 -         to recover, or shrug and go on?
131417 -         ..
131418 -         How important is versioning?
131419 -         ..
131420 -         If versioning were not provided, how much would this
131421 -         impact earnings?
131422 -
131423 -         Primary need is a secure means of archiving the original of an
131424 -         issued document, so there is a direct method of fixing or
131425 -         anchoring communication which influences action, as with a
131426 -         signed printed document.
131427 -
131428 -            [On 000406 Eric Armstrong presented requirements for XML
131429 -            OHS Editor that has extensive versioning capability.
131430 -            ref SDS 52 0375
131431 -
131432 -            [On 000407 listed agenda item to consider legal entitlement
131433 -            to act on virtual document. ref SDS 53 5938
131434 -
131435 -
131436 -
131437 -      ..
131438 -     Receiving Documents
131439 -
131440 -     Eric says...
131441 -
131442 -     When you receive a new document, it is stored in your file system
131443 -     at a location you have designated. It can then be treated like any
131444 -     other read-only XML document on your system. (You can always edit
131445 -     a copy, but the original generally remains untouched.),
131446 -     ref DRT 1 3410
131447 -
131448 -          ..
131449 -         Comments
131450 -
131451 -         How quickly can the thing be identified within an organic
131452 -         subject structure for storage and timely retrieval when
131453 -         needed?  This is enables for effective management, per organic
131454 -         subject system. ref SDS 0 3009
131455 -
131456 -         How do we add anchors for linking to accomplish alignment,
131457 -         and what is advantage of having multiple versions, if it is
131458 -         necessary to insert information for clarification.
131459 -
131460 -         Don't multiple versions the risk of working off the wrong
131461 -         version, leading to mistakes and big losses?
131462 -
131463 -
131464 -      ..
131465 -     Browse Documents
131466 -
131467 -     Eric says...
131468 -
131469 -     As you browse the document, you can set bookmarks, flag sections
131470 -     for comment or follow up, move to the next unread section, or go
131471 -     to one the bookmarks you have set for that document. ref DRT 1
131472 -     2610
131473 -
131474 -     The "bookmark" list only shows you bookmarks you have set for the
131475 -     current document. A "reference" list also exists that shows you
131476 -     the documents in the system, indicating which you have stored
131477 -     locally, and which are not. ref DRT 1 3864
131478 -
131479 -         ..
131480 -         Not sure what is proposed.  If a document is received,
131481 -         it must be read into the local system, otherwise it has not
131482 -         really been received.  When it is received, it is placed in
131483 -         the context of related history, other documents, planning and
131484 -         analysis.
131485 -
131486 -
131487 -
131488 -      ..
131489 -     Revising Documents
131490 -
131491 -     Eric says...
131492 -
131493 -     As you work on new versions of the document, feedback on previous
131494 -     versions is continuously available.  If feedback arrives on a node
131495 -     that no longer exists, the earlier version is displayed in gray,
131496 -     with the version number visibly indicated. You can then chose to
131497 -     copy the feedback to a new location &/or make it disappear, along
131498 -     with the original node. (When you start getting a lot of these
131499 -     artifacts, you know it's time to post a new version.), ref DRT 1
131500 -     2688
131501 -         ..
131502 -         This sounds like the law office issue where a bunch of
131503 -         people in different offices around the world are working on a
131504 -         contract or other instrument.
131505 -
131506 -         Might arise for design operations for engineers as well.
131507 -
131508 -
131509 -
131510 -
131511 -
131512 -
131513 -
131514 -
131515 -
131516 -
131517 -
131518 -