CONTACTS 
0201 - IBM Internet                       800 821 4612 fax or 800...
020101 - Mr. Donald McKenzie; Technical Support

SUBJECTS
Intranet, HTML Code
Memos, 022F05, and ASCII for Internet
Citations, Open SDS records references in
Web, Knowledge Creep
SDS Linking System
Intelligence, Delivery Medium for Business

1808 -    ..
1809 - Summary/Objective
1810 -
181001 - Follow up ref SDS 12 4674, ref SDS 11 4674.
181002 - ..
181003 - Began research to develop process that can call the new
181004 - processor for SDS records, 070405, completed yesterday, ref SDS 12
181005 - 1668, so when a link is opened, the user can access links within the
181006 - opened record.
181007 -
181008 -     [Completed development on 971206. ref SDS 17 4862]
181009 -
181010 - Called Morris about potential to create a processor to convert SDS
181011 - records as they are loaded.
181012 -
181013 - Called IBM Advantis for pricing of a Web site URL address.
181014 -
181015 -
181016 -
181017 -  ..
1811 -
1812 -
1813 - Planning
1814 -
181401 -  ..
181402 - Process SDS Records When Opened from HTML Link
181403 -
181404 - The next step is to create code in SDS that embeds the target line for
181405 - a link using a specific "anchor" tag.
181406 -
181407 -    The objective was described on 971105. ref SDS 9 2367, ref SDS 9
181408 -    3266. ref SDS 9 4099, and on 971108. ref SDS 10 3204.
181409 -    ..
181410 - We have not been doing this.  If we add this it is an additional
181411 - distraction for creating the record to read past, but it is something
181412 - people can get used to.  It would increase the size of the files quite
181413 - a bit.  If we print a record, this stuff could be removed.
181414 -
181415 -     [On 971117 began scheme in SDS linking to support HTML links and
181416 -     eliminate knowledge creep. ref SDS 16 3991]
181417 -
181418 -     [Decided on 971118 not to use the full HTML anchor spec in order
181419 -     to avoid significant distraction, ref SDS 17 0034.]
181420 -
181421 -  ..
181422 - The idea would be for SDS tools to create HTML anchors at the target
181423 - location when a link is created in SDS.  The source record where the
181424 - link is cited would use the target definition instead of the current
181425 - line number.  We would use a locate command instead of line command to
181426 - open the target at the specified position, which would be slightly
181427 - slower, but it would not be noticed.
181428 -
181429 - The anchor has to be unique, so future editing does not cause it to
181430 - get messed up.
181431 -
181432 - We could use the record ID and six digits of time.  This makes a long
181433 - bunch of stuff in the text file.  We may be able to get by with just
181434 - four digits of time, minutes and seconds.  That seems like 1 in 3600
181435 - of getting a duplicate.  A typical record will have links entered
181436 - maybe at most 50 to 100 different occassions when the minute could be
181437 - the same.  If we added the hour that would be 1 in 86400, but is
181438 - probably more like 1 in 43200 because most work will be concentrated
181439 - in an approximate 12 hour period.
181440 -
181441 -  ..
181442 - What would it look like:
181443 -
181444 -         <a name="971114 082819 00101 3402x">
181445 -
181446 - A problem we will have is when the specification is wrapped onto
181447 - another line.  HTML will not be able to find the end of the string,
181448 - because it will encounter the line number field and some space.
181449 -
181450 -         <a name="971114 082819 00101 3402x"> Here is an example of
181451 -         what I mean.  We create this little bit of stuff and have the
181452 -         anchor embedded wherever it seems convenient. <a name="971114
181453 -         082819 00101 3402x"> HTML cannot read this.  It will get lost
181454 -         at the line number and the space.  SDS links can read this,
181455 -         but not HTML.
181456 -
181457 -  ..
181458 - There may be an advantage for SDS to add a source record identificaton
181459 - for a link, because it seems like a way to eliminate knowledge creep,
181460 - per discussion at ref SDS 6 1111.
181461 -
181462 -     [On 971117 began code to add link anchor system. ref SDS 16 2026
181463 -
181464 -  ..
181465 - Historically we tried using the SDS line number field, and found that
181466 - adding or deleting subjects later, which often occurs in a sub-record,
181467 - causes alignment to fail because it changes the line numbers, ref SDS
181468 - 1 1881.  So the file line number was adopted, ref SDS 1 8228, and
181469 - later changed a bit at ref SDS 6 7777.
181470 -
181471 -  ..
181472 - This causes "knowledge creep." ref SDS 2 9403
181473 -
181474 - We have tried to to mitigate knowledge creep by allowing a space of 15
181475 - lines or so to provide a window of change through which subsequent
181476 - editing (thinking) can retain the alignment, ref SDS 6 7777.  This
181477 - works fairly well, since even if we exceed the window of 15 lines, the
181478 - mind can still often recognize the association well enough to manually
181479 - update the line numbers in the citation.
181480 -
181481 -  ..
181482 - Placing an anchor in the target text would solve this problem,
181483 - although it will clutter up the origination of the stuff.
181484 -
181485 - Another idea would be to enter the links with SDS.  When a link is
181486 - called, open the file with SDS and enter an HTML link as a continuous
181487 - string.
181488 -
181489 -
181490 -  ..
181491 - Script to Add HTML to SDS Records When Opened
181492 -
181493 - Since converting even a large record to HTML with the new 070405 macro
181494 - takes less than a second, we should be able to call a java script in a
181495 - link to edit the link, or alternatively to open the file with SDS in a
181496 - separate window.
181497 -
181498 - So another approach is just to process a record as it is read or
181499 - called and embed temporary link addresses along with HTML formatting
181500 - provided by 0704013 and 070405.
181501 -
181502 -     Actually, we do not need to do all of the 0704013 stuff to create
181503 -     an Executive Summary and Action Item list.  Just embed the anchor
181504 -     addresses, and convert SDS links to HTML anchor calls.
181505 -     ..
181506 -     We also need to convert line char to dashes.
181507 -
181508 -
181509 -
181510 -  ..
181511 - Applet, Param, Embed Commands May permit calling processor
181512 -
181513 - The book purchased Wednesday on HTML, ref SDS 12 2934, indicates we
181514 - might be able to call a file and process it with the macro created
181515 - today so that all of the links are accessible.
181516 -
181517 - If we can get people looking up chronology, at some time they will
181518 - want a report.
181519 -
181520 - We might be able to sell various levels of support.
181521 -
181522 -
181523 -
181524 -  ..
1816 -
1817 -
1818 - 1248 called Morris
1819 -
181901 - He thinks it might be possible to call e.exe with the SDS code to
181902 - execute the macro file against the target file.
181903 -
181904 -  ..
181905 - Need to call e.exe with the macro 070405; process the file, then close
181906 - e.exe and 070405, so the user simply sees the processed target file.
181907 - We might hold e.exe in memory, in case the user clicks on another
181908 - link.
181909 -
181910 -  ..
181911 - Morris mentioned another idea of creating a java program that does the
181912 - conversion that the 070405 macro does.
181913 -
181914 -
181915 -  ..
181916 - Web URL Address
181917 -
181918 - We can put records on the Web that will let others access them as
181919 - needed.
181920 -
181921 - The current idea is to create a processor that will open the target
181922 - file and embed a target address.
181923 -
181924 - We can then attend a meeting, create a record and let the customer
181925 - decide if they want to buy the service.
181926 -
181927 - We can create a comparable system for them, and/or provide content
181928 - support.
181929 -
181930 -
181931 -     ..
181932 -    Web Space Acquisition Considerations
181933 -
181934 -    [On 980308 received information on procurement issues to consider
181935 -    for Web URL space. ref SDS 19 3137]
181936 -
1820 -
1821 -
1822 - 1650 called IBM about URL
1823 -
182301 - Talked to Ladan.
182302 -
182303 -  ..
182304 - She seemed to indicate that IBM provides as part of our internet
182305 - address a URL address for Web space. There are two methods.
182306 -
182307 -       1.  Basic
182308 -           ..
182309 -       2.  Comprehensive
182310 -
182311 - She suggested I talk to Jeromy Winters
182312 -
182313 -
182314 -  ..
1824 -
1825 -
1826 - 1652 called Jeromy Winters   972 402 6139
1827 -
182701 - Left message asking about getting a URL address
182702 -
182703 -
182704 -
182705 -  ..
1828 -
1829 -
1830 - 1914 received pricing in URL site
1831 -
183101 - Received ref DRT 1 line 30 from Ladan, explaining we can buy 3 MB of
183102 - space for $30 per month, and can buy 4 MB for $40
183103 -
183104 -  ..
183105 - Got a message from Bill DeHart later saying we can get a price by
183106 - logging onto www.jps.net.  He said the price will in the range of $300
183107 - for a year to use 20MB of space.
183108 -
183109 - Bill suggests checking Micro Times for ads.
183110 -
183111 -     [On 980308 contacted JPS Web site. ref SDS 19 3901]
183112 -
183113 -
183114 -
183115 -
183116 -
183117 -
183118 -
183119 -
183120 -
183121 -
183122 -
183123 -
183124 -
183125 -