CONTACTS 

SUBJECTS
Colloquium Unfinished Revolution, 000106
Procedures Robert's Rules of Order
Segment Collection
XML Editor
DKR Specification
OHS, 000307
Authoring Requirements, Eric Armstrong, 000219
Specifications, DKR, OHS

1210 -    ..
1211 - Summary/Objective
1212 -
121201 - Follow up ref SDS 24 0000, ref SDS 23 0000.
121202 -
121203 - Eric submits 5 features proposed for the Editor to facilitate
121204 - content generation, i.e., writing.  Some of the node identification
121205 - and manipulation explanation sounds similar to subjects in SDS.  Not
121206 - clear the team appreciates that this task is very complicated.  There
121207 - is no feature for integrating time with information, and with
121208 - contacts and subjects.
121209 -
121210 -     [On 000306 Eric updates requirements on Editor. ref SDS 30 0782
121211 -
121212 -     [On 000307 Joe Williams comments on Editor spec.
121213 -
121214 -     [On 000504 Eugene Kim sumbitted explanation of an editing
121215 -     environment he is developing that discusses a schedule and
121216 -     contacts system. ref SDS 31 6033
121217 -
121218 -
121219 -
121220 -  ..
1213 -
1214 -
1215 - Progress
1216 -
121601 -  ..
121602 - Editor Authoring Requirements
121603 -
121604 - Received letter, ref DRT 1 0001, from Eric that sets out five
121605 - functions needed for authoring, which seems like another word for
121606 - writing and editing.
121607 -
121608 - Generally functions are useful, but implementation sounds complicated.
121609 - To this list need to add integrating time, people and subjects, as
121610 - reported on 000124. ref SDS 14 4130
121611 -
121612 -
121613 -  ..
121614 -
121615 -    1.  Segmentation Collection
121616 -
121617 -        Specify a document as the "current target", then roam through
121618 -        the Document Repository, select text, a node, or a subtree,
121619 -        ref DRT 1 8460, and invoke one of the following operations:
121620 -
121621 -        a. make reference
121622 -        b. copy
121623 -
121624 -           These are the copy and citation feature in SDS.
121625 -
121626 -        The reference or copied text appears in the target document.
121627 -        For the copy operation, both the copied text and the reference
121628 -        to where it came from are instantiated. ref DRT 1 5548
121629 -        ..
121630 -        After the reference/copy operation, the context does
121631 -        *not* switch to the target document. You stay where you are, so
121632 -        you can keep browsing and selecting additional items.
121633 -        ref DRT 1 6399
121634 -
121635 -           Should be able to set this according to changing editing
121636 -           needs.
121637 -
121638 -        As a side effect, setting the target document should mark that
121639 -        page so you can easily get back to it. ref DRT 1 7225
121640 -
121641 -           SDS returns to the target record, where the citation is
121642 -           entered.  It can then click the link to return to that
121643 -           location, if needed.
121644 -
1217 -

SUBJECTS
XML Editor
Page Marks, Multi-Level, Context Sensitive

1405 -
140501 -  ..
140502 -
140503 -    2.  Context-Sensitive, Multi-Level Pagemarks
140504 -
140505 -        The PageMark list context-sensitive and multi-leveled. When you
140506 -        access a document, the pagemarks in that document should be
140507 -        readily available. They may have been accessible in a hierarchy
140508 -        before, but they should now be readily available, and possibly
140509 -        displayed. ref DRT 1 4900
140510 -
140511 -        There should also be a working list" of pagemarks. At a
140512 -        minimum, that list would typically consist of the target
140513 -        document for reference/copy operations and the document being
140514 -        read ("mined") for references. ref DRT 1 5852
140515 -        ..
140516 -        An easily-selected operation should allow cycling among
140517 -        entries in the working list, so you can rapidly change context
140518 -        between multiple documents you are working on. ref DRT 1 7482
140519 -
140520 -
1406 -

SUBJECTS
XML Editor
Destimations Automatic

160401 -  ..
160402 -
160403 -    3.  Automatic Destinations
160404 -
160405 -        When you are in a functional specification, and you create a
160406 -        design note, that "target" document for that note should be
160407 -        automatically determined by the current context. ref DRT 1 6474
160408 -
160409 -        The implementation may use pre-specified target locations for
160410 -        nodes of a given type. For example, "design notes" for a given
160411 -        functional spec might go into a predefined "design document"
160412 -        hierarchy. Alternatively, the system might allow building
160413 -        preliminary document-versions using queries, like: "Give me all
160414 -        design notes that correspond to functional requirements in this
160415 -        version of the design doc", ref DRT 1 5467
160416 -
160417 -           [On 000505 Eric added Queryable function to editor spec to
160418 -           accomplish this function. ref SDS 32 2709
160419 -
160420 -
1605 -

SUBJECTS
XML Editor
Linking Typed Nodes Automatic
Oranic Subject Structure
Organization Method

2207 -
220701 -  ..
220702 -
220703 -    4.  Automatic Linking of Typed Nodes
220704 -
220705 -        When nodes are created, they are necessarily typed. The default
220706 -        for a new node is the type of it's parent. It then lives under
220707 -        that parent. For example, creating a new node under a
220708 -        functional specification heading produces a functional
220709 -        specification node. ref DRT 1 4526
220710 -
220711 -              [On 000223 Eric discusses "nodes" to identify paragraphs
220712 -              for organizing the record. ref SDS 28 5325]
220713 -
220714 -            Need definition of "context" to implement -- it gets very
220715 -            complicated, very quickly. see POIMS, ref OF 1 0561
220716 -            ..
220717 -            Not sure how pratical this, except for specialized
220718 -            work. Users need tools they don't need to think a lot
220719 -            about, but can just focus on content.
220720 -
220721 -        It should also be possible to create a node with a different
220722 -        type -- for example, when creating a design note. Links are
220723 -        then automatically created between the new node and the origin
220724 -        node, unless you specify "unrelated". (That lets you track
220725 -        random thoughts that occur to you and have them go the right
220726 -        place without a meaningless link.), ref DRT 1 5593,
220727 -
220728 -        It must be possible to easily see and select node types from
220729 -        the current context. Node-relations must be defined as well.
220730 -        For example, if you create a design note from a functional-spec
220731 -        node, the need for a link is defined by that relationship
220732 -        (unless you specify otherwise). On the other hand, if you
220733 -        create a personal-calendar node after receiving a phone call,
220734 -        the system should understand that the default in that case is
220735 -        "no link", unless you specify otherwise. ref DRT 1 3024
220736 -        ..
220737 -        TBD: Should node types be pre-defined? If they are, it
220738 -        prevents one person from specifying "Design Idea" while another
220739 -        specifies "Design Note" or "Design Topic". Without that
220740 -        regularity, it becomes impossible to ensure that a query has
220741 -        accessed all the relevant information. On the other hand,
220742 -        on-going investigations into "wicked problems" may need to
220743 -        organize as they go. So it may be best to allow node-type
220744 -        creation on the fly. ref DRT 1 5500
220745 -
220746 -            Beginning to sound like subject identification, proposed to
220747 -            the Colloquium on 000120. ref SDS 13 5063
220748 -
220749 -            [On 000220 Eric submits Colloquium Reference Material with
220750 -            "organization". ref SDS 26 8044]
220751 -
220752 -            [On 000221 Jack Park recommends universal "ontology" for
220753 -            web. ref SDS 27 8044]
220754 -
220755 -            [On 000227 Eric cites benefits of organizing information on
220756 -            the Internet. ref SDS 29 0937]
220757 -        ..
220758 -        If specified-targets are used to define "destinations",
220759 -        the system can ensure that a second type does not point to the
220760 -        same target. That is not a complete solution, since competing
220761 -        targets could be created. In that case, a merge operation might
220762 -        be a solution. It would need to
220763 -
220764 -           a.  put the two documents together and
220765 -
220766 -           b.  change all links of one type to the other type.
220767 -
220768 -        On the other hand, if the query system is used exclusively to
220769 -        find related nodes, then there would be no checks at all on
220770 -        dynamically created node types. ref DRT 1 1794
220771 -
220772 -
220773 -
220774 -
220775 -
220776 -
2208 -

SUBJECTS
XML Editor
Drag and Drop Linking

2405 -
240501 -  ..
240502 -
240503 -    5.  Drag and Drop Produces a LINK
240504 -
240505 -        With a node-typing system comes the need to change a node's
240506 -        type. As the problem is better understood, thoughts originally
240507 -        captured in one venue will need to be retargeted for a
240508 -        different purpose. ref DRT 1 2108
240509 -
240510 -            This is a common occurrance.
240511 -
240512 -        XML's entity references leap to the rescue here.
240513 -        (Unfortuantely, the term "reference" is a misnomer.
240514 -        Syntactically, there is a "reference" to another information
240515 -        node, but semantically that node is "copied" inline into the
240516 -        current document. So it's not a "reference" the way you think
240517 -        of a book reference. Instead, it's a "reuse" of the specified
240518 -        entity. So "Entity Reuse" would be more descriptive. Possible
240519 -        terms based on that might be "entity reuse reference", "entity
240520 -        reuse link", "entity reuse specification", or "entity reuser".
240521 -        ref DRT 1 1792
240522 -        ..
240523 -        Given the existence of "entity reusers", it becomes clear
240524 -        that the result of a drag and drop gesture should be the
240525 -        production of either an entity-reuse-link or a reference-link
240526 -        to the original document segment. Doing that lets you
240527 -        recategorize information without changing the original. A
240528 -        "move" operation thus consists of a) Linking to the original
240529 -        from a new location and b) "Deleting" the original from the new
240530 -        version of the document. (It still exists in the old version.),
240531 -        ref DRT 1 1450
240532 -
240533 -
240534 -
240535 -
240536 -
240537 -
240538 -
240539 -
240540 -
240541 -
240542 -
240543 -
240544 -
240545 -
240546 -
240547 -
240548 -
240549 -
240550 -
240551 -
240552 -
240553 -