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


S U M M A R Y


DIARY: April 18, 2000 07:58 AM Tuesday; Rod Welch

Eric Armstrong suggests using Traction for DKR project communications.

1...Summary/Objective
2...Traction Supports Internet Explorer, a Real "Diamond"
3...DKR Project Should Adopt Traction for Project Communications
4...Journaling System Explains Powerful Advantage of Traction
5...Explaining Knowledge Management in 25 Words or 30 Seconds is Tricky
......Traction Uses XML to Track Ideas, Explore, Collaborate
......Interface - Internet Explorer and Netscape
......Editing Flexible, Powerful
......Limitations -
......Transclusions (Inline Linking), Inclusions, Hierarchy, Reduction
.........Transclude Title
.........Transclusion Problems???
6...Twisted Systems "Walks the Talk" on XML Editor for DKR
7...Traction Used by Twisted Systems for Daily Management
8...Versioning Control Supported by Traction
9...Reduction (?) and Summary
10...Traction Scoped to Projects
11...Permissions, Security, Privacy, Confidentiality
12...Linking Hypertext Supported by Traction
13...Catagories Powerful Traction Feature, Supports Some gIBIS
14...Query and Report Derivitive from Catagory Capability
15...Summary of Paragraphs also called "Hierarchy"
16...DKR Project Meeting Agenda for 000420

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

1...Would be helpful to get a few example of "transclusion" and

CONTACTS 

SUBJECTS
OHS Open Hyperdocument System
XML Editing Capability
Traction Journal Management, 000326

1205 -    ..
1206 - Summary/Objective
1207 -
120701 - Follow up ref SDS 29 0000, ref SDS 20 0000.
120702 -
120703 - Chris responds to Eric's important questions, clarifying that Traction
120704 - is an XML editor, which supports Netscape, and multilevel hierarchy,
120705 - versioning and reduction.  Traction is scoped to projects, so should
120706 - be ideal for the DKR project. ref SDS 0 5271  Eric submits agenda
120707 - proposing further review of Traction, and other pending matters, for
120708 - the meeting on 000420. ref SDS 0 5831
120709 -
120710 - Submitted ref DIT 1 0001 linked to the record on 000413, ref SDS 27
120711 - 0001, Eric's analysis on 000414, ref SDS 29 0001, this record and to
120712 - the record on 000414 showing I will be in trial for the next several
120713 - weeks. ref SDS 28 0001  Cited letter on sponsor outreach on 000407.
120714 - ref SDS 24 0001  Supported Eric's suggestion to try Traction, since
120715 - this will be an easy way for the team to get started on Doug's request
120716 - 000405 to start putting links in email. ref SDS 22 2484
120717 -
120718 -     [On 000420 Eric supplements review commenting Traction does not
120719 -     have a sense of hierarchial documents. ref SDS 30 0001
120720 -
120721 -
120722 -
120723 -
1208 -
1209 -
1210 - Progress
1211 -
121101 -  ..
121102 - Traction Supports Internet Explorer, a Real "Diamond"
121103 - DKR Project Should Adopt Traction for Project Communications
121104 -
121105 - Follow up ref SDS 29 3450, ref SDS 27 4209,
121106 -
121107 - Received ref DRT 1 0001 dated 000416 from Eric Armstrong responding to
121108 - analysis on Traction running under Internet Explorer, set out in
121109 - Eric's letter on 000414. ref SDS 29 8448   Reasons for using Internet
121110 - Explorer are suggested. ref DRT 1 4212
121111 -
121112 -     [...below, Chris clarifies that Netscape is supported. ref SDS 0
121113 -     8448
121114 -
121115 - Eric affirms favorable review on 000414 that recommends the DKR "seed"
121116 - team use Traction to replace email, ref SDS 29 3450, per Doug's plan
121117 - on 000405 for the "seed" team to first use links in email for DKR
121118 - project work. ref SDS 22 2484  Eric's notes today that Traction is the
121119 - closest thing to a usable OHS/DKR he has seen, and solves a lot of
121120 - problems he has been wrestling with. ref DRT 1 8216
121121 -
121122 -     [...below, Eric submits Traction for further review at meeting on
121123 -     000420. ref SDS 0 4176
121124 -
121125 -     [On 000420 Eric supplements review commenting Traction does not
121126 -     have a sense of hierarchial documents. ref SDS 30 0001
121127 -
121128 -     [On 000420 project "seed" team decided at project meeting to use
121129 -     an existing tool for adding linking ability in email. ref SDS 31
121130 -     2537
121131 -
121132 - Received second letter from Eric, ref DRT 2 0001, submitting comments
121133 - from Chris Nuzum to questions in Eric's letter, ref DRP 1 0001, on
121134 - 000414 which reviewed Traction, ref SDS 29 3450, based on the
121135 - presentation Chris gave on 000413. ref SDS 27 4209
121136 -
121137 -
121138 -  ..
121139 - Journaling System Explains Powerful Advantage of Traction
121140 - Explaining Knowledge Management in 25 Words or 30 Seconds is Tricky
121141 -
121142 - Follow up ref SDS 29 5850.
121143 -
121144 - Chris appreciates Eric's analysis on 000414 showing Traction provides
121145 - powerful and useful new capability. ref SDS 29 5850
121146 -
121147 - Responding to Eric's concern that Traction's advantages are not
121148 - conveyed by the explanation of a "journal" system, Chris notes that
121149 - Twisted Systems has worked hard to formulate an effective marketing
121150 - message. ref DRT 2 8964
121151 -
121152 - Chris cites Doug's experience showing difficulty helping people grasp
121153 - new capabilities outside their daily experience, ref DRT 2 9020, e.g.,
121154 - Doug's 1992 paper on groupware, citing "intelligence" collection,
121155 - which was reviewed on 991222. ref SDS 1 8064  More recently on 000327
121156 - Doug's paper in 1972 explained objectives for knowledge management to
121157 - improve handling of daily working information, which has not been
121158 - addressed as yet by the Colloquium. ref SDS 19 3971   On 000407 agenda
121159 - for DKR team to define KM was proposed, ref SDS 24 2805, which
121160 - provides a foundation for learning new advantages of integrating time
121161 - and information, called out in POIMS. ref OF 1 0561
121162 -
121163 -
121164 -       ..
121165 -      Traction Uses XML to Track Ideas, Explore, Collaborate
121166 -
121167 -      Follow up ref SDS 29 8160.
121168 -
121169 -      Chris responds to Eric's comment on desirability of Traction
121170 -      using XML, reported on 000414, ref SDS 29 5796, explaining
121171 -      background of Traction development team was in SGML systems.  He
121172 -      and Greg Lloyd met at EBT, where they worked on DynaText.
121173 -      Traction makes extensive use of XML tools, including Pierre
121174 -      Richard's excellent XML parser and XSL transformer, ref DRT 2
121175 -      5265 -- see
121176 -
121177 -      http://www.jaxo.com
121178 -
121179 -      ...for info on Pierre's current venture, Jaxo.
121180 -
121181 -
121182 -       ..
121183 -      Interface - Internet Explorer and Netscape
121184 -
121185 -      Follow up ref SDS 29 8448.
121186 -
121187 -      Chris clarifies Eric's understanding reported on 000414, noting
121188 -      that he demonstrated Traction using IE 5 on Windows, but it works
121189 -      just as well with IE 4 and Netscape 4.x.  Hit F11 in IE to go to
121190 -      full-screen mode; right-click on the top toolbar and select
121191 -      auto-hide to get rid of it.  Right click on the task bar, select
121192 -      properties, and check auto-hide to get rid of it.  Chris suggests
121193 -      Netscape develop a similar full-screen browsing feature.  It's
121194 -      very addictive. ref DRT 2 7968
121195 -
121196 -
121197 -       ..
121198 -      Editing Flexible, Powerful
121199 -
121200 -      Follow up ref SDS 29 8738.
121201 -
121202 -      Chris answers Eric's question on 000414, ref SDS 29 8738, noting
121203 -      that in Traction you *can* edit the paragraphs.  Next to each
121204 -      paragraph we display a marker, e.g. [04].  It's this marker to
121205 -      which the labels (tags) are attached. ref DRT 2 3332
121206 -
121207 -
121208 -       ..
121209 -      Limitations -
121210 -      Transclusions (Inline Linking), Inclusions, Hierarchy, Reduction
121211 -
121212 -      Follow up ref SDS 29 0006.
121213 -
121214 -      Chris responds to Eric's question on inclusion and Ted Nelson's
121215 -      work, reported on 000414, ref SDS 29 0006, noting...
121216 -
121217 -         Transclude Title
121218 -
121219 -         Until we integrated the XSL transformer, there was a danger of
121220 -         violating the HTML content model when transcluding arbitrary
121221 -         other segments of the journal.  We've come so close to "just
121222 -         doing it", because it's such an appealing feature, but we
121223 -         wanted to make sure it wouldn't cause support problems; you
121224 -         might be surprised at how badly browsers can get wedged when
121225 -         you feed them mangled HTML.  But now we can hardly wait to
121226 -         turn it on!  We do (carefully) already transclude the title
121227 -         when displaying cross-references; when the title is updated,
121228 -         all cross-links will reflect the change. ref DRT 2 0756
121229 -         ..
121230 -         Transclusion Problems???
121231 -         
121232 -         Other problems with transclusion include interface issues
121233 -         relating to whether you expect to find fulltext search hits in
121234 -         in/transcluded content, how you address into included
121235 -         content... doing this feature right does get a little tricky
121236 -         (when I talked with Doug about this yesterday, he said they
121237 -         had run into the same questions, and that nobody had "funded
121238 -         the research" to answer them :-), ref DRT 2 0363
121239 -
121240 -      Would be helpful to get a few example of "transclusion" and
121241 -      "inline" linking, with explanation of money and time saved by
121242 -      using these features, per questions on 000414, ref SDS 29 5146,
121243 -      and the meeting on 000413. ref SDS 27 1081
121244 -
121245 -
121246 -
121247 -
1213 -

SUBJECTS
Useful Technology Used Alot
Vendors Use Their Products Walk the Talk

140401 -  ..
140402 - Twisted Systems "Walks the Talk" on XML Editor for DKR
140403 - Traction Used by Twisted Systems for Daily Management
140404 -
140405 - Follow up ref SDS 29 9477.
140406 -
140407 - Chris responds to Eric's understanding that Traction is used by
140408 - developers in France, reported on 000414, ref SDS 29 9477, noting
140409 - geographically speaking, Traction was mostly designed and built in
140410 - Providence, RI and Washington, DC.  The parser and transformer were
140411 - imported from France.  The distributed team uses Traction as its
140412 - primary coordination vehicle. ref DRT 2 3696
140413 -
140414 -     On 000414 set action item to review some history to see the level
140415 -     of use for supporting daily management. ref SDS 29 5796
140416 -
140417 -
140418 -
140419 -
140420 -
1405 -

SUBJECTS
Computers, Software Design, Version Control

1804 -
180401 -  ..
180402 - Versioning Control Supported by Traction
180403 -
180404 - Follow up ref SDS 29 5973.
180405 -
180406 - Chris confirms Eric's understanding reported on 000414, ref SDS 29
180407 - 5973, of versioning in Traction is correct, noting...
180408 -
180409 -     We call the versioning mechanism "update" (used to be "correct"),
180410 -     and we originally intended it to allow you to fix errors or
180411 -     reflect changes in fact. ref DRT 2 5504
180412 -
180413 - ..
180414 - Reduction (?) and Summary
180415 - 
180416 - Chris responds to Eric's question on 000414, ref SDS 29 4588,
180417 - concerning summary and reduction, noting...
180418 -
180419 -     Summary in Tration lets you take some set of entries and post a
180420 -     new entry which "summarizes" the other set.  Whenever you look at
180421 -     any entry, you can see what entries summarize it. Summaries are
180422 -     listed in order of most specific to most general; a summary of a
180423 -     specific set of entries would be listed before a summary of the
180424 -     month, which would in turn be listed before a summary of the year.
180425 -     ref DRT 2 5092
180426 -
180427 -     Summaries of a time period are displayed on the newspage covering
180428 -     the time period.  So you can post a status report on Monday
180429 -     morning summarizing last week, and it will appear on last week's
180430 -     newspage. ref DRT 2 0884
180431 -
180432 -        This sounds a bit like the diary summary in SDS.
180433 -
180434 -     For the idea of reduction, note that the primary method Traction
180435 -     currently has for threading discussions is by tagging the relevant
180436 -     messages (or paragraphs) with the discussions to which they
180437 -     belong, e.g. this paragraph might be part of :discussion:traction.
180438 -     ref DRT 2 5168
180439 -
180440 -     If you later want to prune the thread, or post a summary, you can
180441 -     just change what entries (or paragraphs) are labeled
180442 -     ":discussion:traction".  The ones not labeled will fade into the
180443 -     background (unless you go looking for them using Traction's
180444 -     perspective control).  While not exactly what you are looking for,
180445 -     it is a form of reduction which you might find interesting to work
180446 -     with; we use it extensively. ref DRT 2 0744
180447 -
180448 -
180449 -
180450 -
1805 -

SUBJECTS
Confidentiality Security Privacy Balance Intelligence for Collaborati
Privacy/Security

2005 -
200501 -  ..
200502 - Traction Scoped to Projects
200503 - Permissions, Security, Privacy, Confidentiality
200504 -
200505 - Follow up ref SDS 29 5271.
200506 -
200507 - Chris responds to Eric's question on 000414, ref SDS 29 5271, about
200508 - adding someone to the "authors list," noting...
200509 -
200510 -     Permissions include read, submit, update, reclassify, create
200511 -     category, administer project, administer server.  They are scoped
200512 -     to projects. ref DRT 2 4056
200513 -
200514 -     Question:
200515 -     ..
200516 -     Has Traction been pilot tested on any projects; what cost
200517 -     savings have been established or calculated?
200518 -
200519 -
200520 -
200521 -
200522 -
2006 -

SUBJECTS
Hyperdocuments
Linking Connections
Linking HTML Too Slow for Management

2506 -
250601 -  ..
250602 - Linking Hypertext Supported by Traction
250603 -
250604 - Follow up ref SDS 29 5974.
250605 -
250606 - Chris responds to Eric's question about drag and drop feature for
250607 - linking reported on 000414, ref SDS 29 5974, noting...
250608 -
250609 -     Drag and drop depends on the interface you are using; Outlook and
250610 -     IE support it.  Other browsers vary. ref DRT 2 6831
250611 -
250612 -
250613 -
250614 -
2507 -

SUBJECTS
Catagorize
Subject Index Method

3205 -
320501 -  ..
320502 - Catagories Powerful Traction Feature, Supports Some gIBIS
320503 - Query and Report Derivitive from Catagory Capability
320504 -
320505 - Follow up ref SDS 29 1350, ref SDS 20 1350.
320506 -
320507 - Chris responds to Eric's questions about "query" reported in the
320508 - record on 000414, ref SDS 29 1350, noting...
320509 -
320510 -     Allows... but who really wants to write "newspage week today" when
320511 -     they can write "nwt"? ref DRT 2 4002
320512 - ..
320513 - Chris responds to Eric's question about using hierarchies more
320514 - than two levels deep, reported on 000414, ref SDS 29 0578, noting....
320515 -
320516 -        [On 000420 Eric supplements review commenting Traction does not
320517 -        have a sense of hierarchial documents. ref SDS 30 0001
320518 -
320519 -     Categories *can* be n levels deep.  Perhaps the confusion came in
320520 -     when I explained that we have some predefined structure at the
320521 -     root level. ref DRT 2 5780
320522 -
320523 -     ::project:partition:you:can:go:as:deep:as:you:like
320524 -
320525 -     Partitions include topic, action, discussion, resource and
320526 -     "response" or "semantic".  Topic is the "default" partition, so
320527 -     ::project:topic:news is the same as ::project:news. ref DRT 2 1092
320528 -
320529 -     We support wildcards in the Rapid Selector to allow you, for
320530 -     example, to look at ::*:*:open. ref DRT 2 1872
320531 -
320532 -
320533 -
320534 -
3206 -

SUBJECTS
Summary Linked to Detail = Knowledge

3304 -
330401 -  ..
330402 - Summary of Paragraphs also called "Hierarchy"
330403 -
330404 - Follow up ref SDS 29 6988.
330405 -
330406 - Chris responds to Eric's questions about summary in the record on
330407 - 000414, ref SDS 29 6988, noting that
330408 -
330409 -     In our terminology, the Traction "journal" collects "entries" in
330410 -     "projects".  Entries may be of various types, corresponding to
330411 -     different XML content models.  So far, the main type we have
330412 -     implemented and use is based on an email message with n paragraphs
330413 -     (actually HTML block containers).  The first paragraph is rendered
330414 -     as the subject, the rest as body. Each one is addressable.
330415 -     ref DRT 2 6232
330416 -
330417 -   [...see also above under Reduction. ref SDS 0 0642
330418 -
330419 -   [On 000422 Joe Williams explains summary and hierarchial structures
330420 -   for DKR specification. ref SDS 32 0918
330421 -
330422 -
330423 -
3305 -

SUBJECTS
OHS/DKR Meeting at SRI 000420

3404 -
340401 -  ..
340402 - DKR Project Meeting Agenda for 000420
340403 -
340404 - Follow up ref SDS 26 0001, ref SDS 24 6554.
340405 -
340406 - Received ref DRT 3 0001 from Eric setting out the agenda for the
340407 - meeting on 000420....
340408 -
340409 -    •  <4466 Joe: A Picture We Can Present
340410 -
340411 -       Focuses on marketing/education/technology transfer issues, I
340412 -       believe, aimed at providing a picture we can use to quickly and
340413 -       easily communicate the benefits of the technology. ref DRT 3
340414 -       0001
340415 -
340416 -           [On 000420 Joe gave formal presentation. ref SDS 31 5880
340417 -
340418 -         This aligns with planning on 000407 for Joe to complete
340419 -         preliminary explanations of ideas for creating the DKR.
340420 -         ref SDS 24 2576
340421 -
340422 -         The presentation was planned for 000413, but was there was not
340423 -         enough time. ref SDS 27 7200
340424 -
340425 -    •  <4176 Twisted Systems futures
340426 -
340427 -       Being simply god awful at delegating tasks, I neglected to make
340428 -       sure someone was following up with Chris Nuzum to see how we can
340429 -       work together with Twisted Systems, and at least get a copy of
340430 -       Traction to use. Doug met with him over the weekend, and I'll
340431 -       talk to him later today. Hopefully one of us will have something
340432 -       to report. ref DRT 3 3072
340433 -
340434 -         This aligns with Eric's analysis on 000414, ref SDS 29 3450,
340435 -         and above. ref SDS 0 3450
340436 -
340437 -         May address issues from prior presentation on 000413.
340438 -         ref SDS 27 0351
340439 -
340440 -    • <1152 Licensing Options
340441 -
340442 -      (discussion so far, unless anyone has specific proposals to
340443 -       make), ref DRT 3 6290
340444 -
340445 -        Not sure what this means.
340446 -
340447 -        On 000407 agenda issue was proposed to discuss business issues,
340448 -        ref SDS 24 6973, which included legal questions on open source
340449 -        from the meeting on 000324, ref SDS 15 3055, and licensing is
340450 -        evidently related to sponsor funding, from the meeting on
340451 -        000406. ref SDS 23 3055
340452 -
340453 -    • Open Standard vs. Open Source -- discussion
340454 -
340455 -      Which is desirable? Which is fundable? ref DRT 3 5112
340456 -
340457 -        On 000407 agenda issue proposed to discuss open source as part
340458 -        of business analysis. ref SDS 24 6973
340459 -
340460 -    • Business Models
340461 -
340462 -      See above.
340463 -
340464 -        Guess this relates to licensing and open source issues.
340465 -
340466 -
340467 - Submitted ref DIT 1 0001 linked to the record on 000413, Eric's
340468 - analysis on 000414, this record and to the record on 000414 showing I
340469 - will be in trial for the next several weeks. ref SDS 28 0001 Supported
340470 - Eric's suggestion to try Traction, since this will be an easy way for
340471 - the team to get started on Doug's request 000405 to start putting
340472 - links in email. ref SDS 22 2484
340473 -
340474 -
340475 -
340476 -
340477 -
340478 -
340479 -
340480 -
340481 -
340482 -