This TitleBar shows that a Chapter's cell can be 'expanded' to show
the sections of that chapter. It aslo shows a "N:", which indicates
that this is a public file, available via the interNet. Other
storage environments exist to provide more secure, private venues or
environments in which various groups an Post and Collaborate.
Note that '...' characters are used to compress the TitleBar, rather
than allowing it to develop into an unwieldly structure. These may
or may not retain their function as hyperlinks if their targets are
contextually obvious.
One challenge that results from making a file publically accesible is
that it is much more difficult to write for a 'unknown' audience.
Obviously, Browsers will inevitably have differing levels of
sophistication and tools at their dispoal, creating a need to satisfy
both a Novice and an Expert, simultanteously. This file will try
different ways of doing so.
Comparing this title bar to the standard bar appearing at the start
of each Chapter, illustrates how each of the ten chapters of this file
may each be expanded to show their local sub-sections. Since this
expansion needs more horizontal space, the text for the adjacent Chapter
titles is generally reduced to '...', although the associated
hyplerlinks still function correctly.
Preamble:
This 'Help' section relates specifically to this file. For the
information of the more observant, the second 'Help' that appears in
the Menus located throughout this file, is a placeholder for the
proposed assistance that may be needed by the environment Box that
encapsulates this file.
. . .
This file is: . . .
A PUBlished file, accessible via the InterNet, via
http://janus.datafix.com/hwo/HwMo.htm
Being accessible via the InterNet, it is not only fully public,
it is also indexed and fully cached by various search engines,
noteably www.google.com.
Since this raises many questions regarding "OwnerShip",
Intellectual Property Rights, CopyRight, ..., etc. There is reason to
restrict its content to material that I would not be embarassed by,
any more than if I were to be filmed while writing on the walls of
the bedroom of a glass house. (I could have used the more effective
analogy that is available elsewhere, but (as stated) this is a public
file.)
. . .
Designed to use HwoBox menu constructs, which are introduced
in the typographic conventions section of this file.
Very much a "Work in Progress", meaning that it is in a
continuous state of flux. Specifically:
New structures are implemented in whatever area of the file may
be in use to support current activities.
Certain hyperlinks may not function in a consistent manner,
especially if they are in an area that is currently bring refined or
extended.
. . .
Provided for the use of several different Audiences.
Hence, if you find your view of this file confusing, ...
. . . Don't panic!
Rest assured that, perhaps eventually, but only in response to
specific questions, additional help may be provided.
While this is mainly just a place holder for future content, it is
useful for making a few quick comments:
This file's current role is to provide interested parties with an
over-view of Hans Wobb'e commitments. A proper HwoBox structure will be
incorporated here to place these in an appropriate context.
At this time, the main Report heading bars that have been
installed in this file are not populated with content. They were
installed in this file purely for testing purposes, and in anticipation
of potential future use. Furthermore, they may well be replaced by the
emerging HwoBox constructs, given the apparent preliminary advantages of
well-illustrated encapsulation.
Links to the WikiWikiWeb Produced and Sponsored by Hwo will be
provided for people who are brave enough to actually ask questions,
rather than simply 'lurking' in the background.
. . .
Author's style.
This file is a 'Work in Progress', largely for the following reasons:
A one small part of a long-term Research project into
Collaboration, it needs to be publically accessible via the internet.
The fact that it is public and is accessed by diverse people for a
number of different reasons definitely affects most aspects of its
design and content.
It is continuously evolving and not all of its contents are
necessarily at the same level. This is because:
All of this file's contents are created as a by-product of
other work that is being undertaken. While this emphasizes the
practical applications of the contents, it does restrict the
time and scope of the contents by applying the constraints of
the active work.
The fundamental capabilities of Html are still being
learned, at the same time as they too are evolving.
...
The capabilities of emerging technologies are forcing a
fundamental re-evaluation of work methods. For example, the use of
html very quickly leads to re-considering the definitions of a Page
and how it can and should be navigated using modern Browsers.
This file contains 'Back' links that browsers may encounter. These
are provided as a convenient 'return' method for users who may jump into
this file from others, such as in the case of jumping here to review a
term in this file's Glossary.
This file contains 'Act(ion)Bars', a special case of 'TitleBars'.
These try to provide users with a locally applicable set of convenient
options for their next jumps, such as: Return (to the last location),
... This is especially helpful when users jump into the middle of a
file from different locations since it allows them to return to their
respective starting points. This also makes the sharing of text more
efficient for authors.
. . .
I should document myMarkUp conventions here, including:
Considerable 'white space has been added to the end of each
scetion of the report to reduce the visual cluttter that results from
running sections together. The usual resulting problem of forcing
extensive scrolling should be avoidable by using the HwoBox Menus to
navigate this file.
"N:\...\" prefixes identify HyperLinks to InterNet
accessible locations are generally work.
'I:' " @Dfx
.
'C:' " @Hwo
"C:\...\" prefixes identify
Hyperlinks to other files that are generally
not available on the InterNet .
Filename
Chapter
Title
Foreword
Contents
Summary
Introduction
Found
Concluded
Recommended
Appendix
. . . " . . .
. . .
Findings
ByTime
ByTopic
BySubject
Time
Space
This HwMo file continues to be a Work In Progress. Past
details have been archived to other data stores, although significant
MileStone items may be re-introduced.
HyperLink conventions being used in this file, that can
be relied on, include those presented in the preceding table, as well
as:
"C:\...\ HyperLinks will not work. For example:
C:Su = Hwo's laptop SushiWiki.
This file is also an initial test site for HtMl enhancements.
Experiments with Style, designed to quantify and define
elements that are most effective in collaborative enterprises are
especially of interest.
. . .
Since many such experiments have been retained to illustrate what
can be done, this file's style may appear un-necessarily complicated
and disorganized.
A 'Preface' style for Hwo (HwPref) should be created. Consider
the style used by the W3C authors, as opposed to this use of italics.
...
Raa's navigation complaints were resolved within 30 seconds on a
demonstration. She claimed she became dis-oriented when she first
looked at all of the material. There may well need to be a 'Don't
Panic' for first time users that stresses "take this tuutorial".
PDF's may also be a way of helping less technocal users. and should
certainly avoid problems such as screen resolution.
Hwo's DOCument resources are introduced via this simplified table.
The focus of this table is predominantly this file, since it is the
original 'seed' file from which the rest of the environment will be
cultivated. Subsequent tables will try to provide both a broader and
a deeper context.
N:\\...\hwo\...
HwMo.htm (A.K.A. 'Almanac' & HwoDocAl...)
A - Title
B - Foreword
C - Contents
D - Summary
E - Introduction
F - Findings
G - Conclusions
H - Recommendations
I - Appendices
J - Help.
...
This next table introduces a bit more complexity by expanding the
Findings section and introducing the Shared Pages Library.
This final table expands hoizontally to show yet more of the details
of this file and vertically to reveal the position of the "N" file space
within a deeper context of other Views and internet Domains.
{draft.doc(s) - only by Request.}
( Stored only @ Dfx. )
...\'Mm' = "Mail matters ..."
C:\...
(Hwo's personal disks.)
'Mm'Working copy
...\Pages\... mini-versions of this file, shared via
Email.
Others
...
This nested table structure is helpful to the extent it makes the
relationships amongst its components more evident and it provides
hyperlinks that can be used to navigate this report more efficiently.
Hint: Users who are interested in linking
directly to this file's bookmarks are reminded that mouseOver
displays of hyperlinks will reveal the names of internal bookmarks
for their use. These should be relatively reliable since efforts
have been made to standarize the names of these references and
they will not be changed until adequate Version control
conventions are implemented. In fact, the standardization of
names has been taken to such extremes that the bookmarks for these
hyperlinks can be copied freely amongst files, retaining their
functionality. An additional layer of encapsulation can be
applied to enclose files or documents that address the same
Subject, but with specialized views for multiple, disparate
Authors and Audiences. Finally, this entire system can itself be
enclosed with the standard classifications of both the Library of
Congress and the Dewey Decimal systems of classification.
Subsets of these tables may be placed throughout the Chapters,
Sections and segments and Blocks of this type of document as a
visualization aid for all and as a navigation aid for those who are
reviewing it electronically.
This file evolves solely as a by-product of all of the other
activities that are undertaken by Hwo to satisfy DataFix clients, using
the full range of his Associations. In general, its contents result
from:
Attempts at extensive collaboration in order to to be as
effective and efficient as possible in our work efforts.
Striving to avoid repeatedly searching for previously used
information and having to repeat the efforts needed to present it
properly.
Attempting to actually document (ideally with appropriate
illustrations and supporting examples) those aspects of our work that
should be shared more broadly.
From its initial role as simply a publically accessible calendar,
Into a central control point that can serve the needs of all of
the individuals that are involved in active collaborative efforts.
A repository of re-useable text.
An 'almanac' that provides information of use to more than one
other individual.
A 'BookSeed' that may actually be encouraged to grow into a
formal publication. To understand the possible scope of such an
undertaking it has been necessary to classify, structure and
encapsulate the various activities that otherwise seem to absorb most
of the time that is available. This leads to a more formal
treatments of Goals and Ojectives that can be found in the
Introduction.
Hans Wobbe, at DataFix, focuses on providing specialized information
technology services that are the best available value, to as few
Clients as possible, in mutually benefical relationships.
Hans has done this since the start of his career in 1969 in the
University of Waterloo's state of the art computing center, by
continuously improving his skilled applications of computer and
related technologies to the problems of Business and Government, and
by creating co-operative relationships amongst Clients.
This internet-based file provides information that supports
collaboration with others, as does information in a variety of other
different environments such as:
The following table has been reduced to be more useful in a typical
proposal which needs to span the range of considerations from
immediate 'next steps' to 'significant eventual benefits'.
The next table needs to be compared to the preceding ones since the
nest inversion on the horizontal access seems to be a more effective
apparent enclosure.
This table illustrates what I have come to accepts as appropriate
definitions. The striving for defineable targets led to this effort
since many people seem to be of the opinion that without a defined
purpose, progress is difficult.
In considering the setting of meaningful purpose, it became apparent
that people use Goals and Objectives interchangeably, especially
between different contexts such as business pursuits and sporting
activities. Since 'management by objectives' became a universal
mantra in the North American business environment that encompassed
the activities needed to earn an annual binus, I have chosen to adopt
the term Objectives to refer to annual plans. This freed Goals up
for use in a longer (decades) context.
As can be inferred from the preceding TitleBar fragment, this
Findings section has three significant sub-sections. This 'Found'
section's MenuBar is 'opened' to show the nested components of
ByTime. This is done for the convenience of this file's users, who
seem to follow this path, than the others. Of course, the components
of the other two sibling categories will appear 'open' on their own
sub-pages.
Specifically, items are clustered ByTime, ByTeam and BySubject.
Additionally,
A Status (ByTime) section encapsulates all material in proper
chronological sequences, that may also appear clustered under the
headings of Forecast ('Next' or Future), Present ('This') and
Background ('Past').
Background information is provided to ensure that the
bulk of the material in this file is presented in an effective
context and that it is properly supported. Background
information obviously evolves as newer versions of this file are
published. Hence, prior Findings (or 'Found' material)
Conclusions and Recommendations) may also be included in this
area of the file, relying on hyperlinks for effective navigation
and presentation.
A ByTeam section presents material that is specifically related
to the interests and activities of other Associates.
A BySubject section presents accumulated material by major
Classification categories such as the DeweyDecimal or
LibraryOfCongress systems or by Themes or Ideas.
I should try to convert the bulk of this note into an EndNote,
leaving just a menu stub visible here as a reminder to myself and
anyone else that may be interested.
Page layout considerations are affected by the desire for navigation
menus and the wish to reduce scrolling. Ideally, it should be
possible to see the way Back, the Current situation, including
siblings and the next generation of choices.
This is illustrated in the preceding table's nested Status box. If
the other three siblings for Status that are enclosed in Findings
were all expanded, this TitleBar would have to be expnded into a
miniTable.
This is also illustrated in the next "background' table, showing the
'parent Findings and the Child thoughts of Known and Assumed.
Registration is important. The effect of having the navigation bars
properly aligned is efficient and effective. Since this depreciates
the use of the traditional Headings as titles that provide visual
breaks, these titles can be positioned above the Anchor, just out of
sight.
The 'Present' can be thought of as a set of nested time periods each
enclosed within larger scenes. Specifically, This Day is part of This
Week, which is in turn part of this Month, etc., as shown in the next
table.
Taking the same view of the past, and arranging both the Past and the
Next periods around the 'This Hour' Present period, is illustrated in
the next tables.
This section's menu presents the three time chronological sequences
of Past, Present ('This') and Future ('Next') in a different sequence
than the corresponding text blocks that exist in this document. This
is based on the assumptions that:
The future is most important, assuming present actions can still
affect it. It is presented first for this reason, in spite of
inverting the common sequence of having Past periods on the left and
Next periods on the right of the current (This) period.
The present is next in importance since it is here to enjoy
('Play') now or for the 'Work' activities that are one of several
sources of 'Income' which one can 'Spend' or 'Invest'.
The past is least important since it can only serve as
instruction regarding previous events and their consequences.
In the design of this file, the dimension of Time took on additional
significance. This is largely because this file evolved; incorporating
additional information from other sources, many of which included Dated
notes and spawning additional repositories when it made sense on the
basis of emerging guidelines. Furthermore, in the absense of any other
organizational structure (e.g. Subject, Author, ...) chronological
filing preserves the sequene of notes, mainatining this Contextual
information, which may add value.
Efforts to provide a dense set of hyperlinks that can be used to
navigate in this dimension started with the following simplistic table
and evolved into the subsequent, extended version that spans from an
Hour to a Millennium.
Day
Past...
This
...Next
This is a well structured, three period, minimal version of a
'Present' table, showing how both the Past and Next time frames can
be recursively encapsulated in periods with decreasing resolution.
A
B
This ...
B
A
Extending this a bit and applying familiar time periods yields this
is a well-structured, three cell version of a 'Time' table that
include the Past, Present and Next periods, and that can be
structured to accomodate different time resolutions. Note that the
resolution of the Past and Next periods should be equal to or greater
than the center 'This' period, to avoid over-laps.
Year
Month
Week
This Week
Week
Month
Year
This next table will be relocated since it was criticised as being
'too boxy". It will be retained in a Syle document as an
illustrative example for design considerations.
Year
Month
Week
This Day
Week
Month
Year
The following, more extreme extension tests this limits of the width
of such a table that are practical.
Can be nested within a Subject or other material that has a time
dimension of sufficient scope to warrant navigation on this
dimension. In these cases, the resolution can be changed by setting
the 'This' center period to be larger or small and by extending the
end periods.
Could be enclosed in a Past This Next structure, with this Hour
being the fluid This element.
Should be extended to also support the "big Bang", at its oldest
extreme.
The increases in the thickness of the borders that corresponds to
their nesting level, evident in the earlier table, is omitted to
reduce the space that this consumes.
Appears inverted when considered in the light of the enclosing
'next steps' that expand to the right. None the less, this may be
valid since its perspective is that of the 'present' Hour with the
extremes of time being more distant. I should try inverting this, if
only as a comparision.
In the middle of this table, for planning purposes, the 'Hour' is the
smallest useful time allocation that is considered. Assuming that
'ThisHour' is the trasition between the Past and Next time periods,
the Next hour is the first that can be allocated, fundamentally to
either Play or Work.
...
Parts of this file still use an early version featuring 'ByTopic'.
Newer versions are experimenting with replacing this (since ByTopic and
BySubject are not generally well differentiated), allowing 'ByTeam' to
recognize the important dimension of individual entities.
The current Month calendar on the title page is used to access
specific dates. This area may be used to at least link to the WorkLoad
table, which should remain a small separate file, to facillitate
printing.
The 'simple list' structure of tables like these is better suited for
long comments.
Significant events and future dates beyond the scope of the next few
months are generally listed here. Hyperlinks in the Date field are
restricted to Hwo's C:. Hyperlinks in the 'till Time field return to
the Present Week calendar.
It may, however, make sense to leave lapsed intems in this table
(assuming they do not 'interfer', at least those that are
sufficiently important to warrant being transfered into a Summary
form. It is also already evident that it will be possible to
introduce significant navigation refinements for the underlying data
structures by extending the controlling HIMs.
These comments are here temporarily, pending the restructuring of this
file's Past, Present and Futures actions.
Current plans for this section of this file include:
Repace the preceding calendar with (HwoBox(Date)).
One additonal sub-section exists within this Present Section;
specifically, a WIP (Work In Progress) section
containing information about active undertakings.
It may be prferable to relocate this WIP sectio into the Next
(Future) section rather than modifying the title bars throughout
this section.
This area of this file is designed to accomodate the use of a Day
calendar subTable that is also exists in a PocketPc form factor. Part
of this design change includes inverting the order of the section in
this area to flow ..., Day, Week, Month, ... rather than the reverse.
Ideally, this will allow a less sophisticated user to find desired
content more easily, while still allowing an experienced user to jump
to the denser, more efficient formats.
Additional tables designed to function in both PocketPc and DesktopPc
environments include at least the next table of the heirarchial
priorities that generally fall within time Periods.
This "This day" section does not include a calendar since this Day is
a part of this month, which appears at the start of this file. The Days
in the Month calndars are a convenient way of accessing Day details in
the following table. If this document's Past, Present, Future structure
is strictly enforced, the following table's content should be relocated
into Past and Future areas, leaving only 'this day:' items in this
section. At this time, this requires more maintenance than can be
justified.
The current Month table is also replicated on my PocketPc as (
C:\HwoPcp
). It is still under development, so it has not been integrated into
this file fully.
This 'ThisWeek' area includes a 'ThisDa'y table in order to provide a
larger, more flexible area than is available in the 'This day:'
section.
The current Activities column of the HwoDa(y) table is 200 pixels
wide, making it practical to have a 5 working day week View for devices
larger than PocketPcs.
2004-04-12
MonDay
...
try nested Tasks.
TuesDay
...
Wednesday
...
ThursDay
...
FriDay
...
The following section's content is probably obsolete.
This week:
This area is being developed to become a simpler Calendar intended
for less experienced uses. It will not use as dense a presentation of
Enclosed tables since these appear to be confusing to beginners.
The preceding table is part of this effort, breaking out the TitleBar
as a separate table.
It is being developed to be used in conjunction with ...
C:\pcktPc
..., a table designed to be used on my Pocket Pc. This table structures
a Day as a Column for the PocketPc's form factor, and because it assumes
that Days will be enclosed within Weeks.
This table is a subset of the following one. It has been isolated as
part of the design of a simplified table structure that may be more
appealing to less expert users.
This 1000 pixel width cell is used to set the table size
for "align=right" elements.
In the preceding table:
The vertical axis of rows, contain relative priorities, with the
highest being at the top of this 'push down' stack. The current
degign assumption is predicated on Western cultures' 'left to right,
top to bottom' reading conventions.
The horizontal axis of columns is generally associated with time
or at least a required relative sequence of cells.
It may make sense to invert the Dfx priority encapsulations, or
to use the same approach as is used in the Hwo row.
...
In the following table:
Row '01' is properly structured.
Row '02' 's 'Hwo' cell has a left-nested table, as could the
cells of all of the Teams ("C" is the one that remains without
nesting). Note that the activities of the four Teams could be shown
to be happening in parallel by making them rows that would appear to
be concurrent in Time.
Row '03' is a collapsed copy of '01'.
Explain the 'PushDown' stack concept as it is applied to the
Ranked Rows.
Refer to an explanation of the 2nd column's NextSteps box.
...
01
A
B
C
D
E
02
...
Hwo
...
"A"
...
"B"
"C"
Teams sales
DfxSales
03
A
B
C
D
E
In the preceding table:
'Hwo sales' should be expanded to be a peer to 'Team sales'. I
could then nest 'next steps to its left.
...
A
B
C
D
E
F
This is a properly structured table that can be extended easily by:
Moving the whole structure 8 spaces to the right.
Adding my four standard Table, tr, td and /table tags.
The Present should also be enclosed within the Status section which
is itself nested within the ByTime section. This is not evident in the
following TitleBar which, therefore, needs to be revised.
A 'Constraint' is an impediment that creates Needs which would
otherwise already have been filled. It may be thought of as the walls
of the box that contain the vaccuum Nature abhors.
A 'Need' is an impediement to an achievement. (A.K.A. 'excuse'?)
An 'Idea' is a suggestion regarding how a Need might be fullfilled.
A 'Task' is one of the efforts needed to test the idea as well as
the rest of the work needed to create the Plan that allocates Resources.
A (project) 'Plan' is the proposed allocation of Resources to an
undertaking that is intended to meet an Objective. It also includes the
Actual time and other Resources that are consumed in addition to the
original proposal.
An 'Objective' is the final Activity that defined the end of a Plan.
Also, in the Business context of Management By Objectives, Objectives
are the achievments that trigger bonus payments.
A 'Goal' is the longer term result of achieving many Objectives.
'Stacks' can be used to illustrate Priorities. The following table
is properly laid out and can be compressed.
03
02
01
00
01
02
03
09
08
07
06
05
04
03
02
01
00
01
02
03
04
05
06
07
08
09
I'm not sure I understand the appearance of the initial empty cell
that results from trying to enclose the two separate tables as columns
of another and structuring the Tables in a most regular way.
Try separating them and structuring them most formally.
Traditionally, on a scale of 1 to 10 the numbers ascend.
HwoStyle. It may be necessary to substitute
Silver for Grey.
Width % sets the table width as a fraction of the available
horizontal space. This shows total allocation is 1/2 of available
width, adjusted automatically as the window's width changes.
Scrolling is enforced to meet this constraint.
Why does the # of TRs determine the # of Columns?
How is the relative width of the Columns set?
width = 1,000 pixels.
r1,c1
r2,c1
r2,c2
width set to 1,000 pixels.
r1,c1 it seems to be proportional to the longest string in each
column, or at least so it seems. In adding this last sentence, I
am expecting to see r1,c2 compressed to less space than it
needs, forcing this colum to wrap.
r1,c2 1000 pix
r2,c1
r2,c2
t1(r1,c1)
t2@75%(r1,c1)
t2(r1,c2)
....
t1(r2,c1)
It appears that the second table gets 75%, yet it has trailing space?
Consider inverting the nesting to show a small next step that is
enclosed within the Plan's Objective, the Entity's Goal and the eventual
Vision.
Spare table copy...
Millennium's Visions
Life's legacy
Decade's goals
Year's objectives
Month's plan
Week's schedule
Day's activity
'DepthGuage' = Level 2
replication try...
.
.
.
A reversal try...assuming that the nesting position is the first, not
the second, column. This table can be extended by imply copying the
first and last two rows as a growing enclosure.
'LeftEnclosed' table strutures have several uses. The following one
shows a 'NextSteps' view of Time.
hour
day
week
month
year
decade
century
millenium
This same structure can be used for a 'thin' organizational hierarchy
that supports hyperlinks, which should be 'open' to the right since this
implies more scope at the higher levels. For example:
WendyBurgess
Pauline ?
JimJack
DavidMcCutcheon
? Smitherman
The layout of these tables' source code is based on the most easily
recognized patterns. Compressions of the source code are possible, for
more efficient copying, once a table has been 'debugged'.
A oneRow table that has three initial columns, for:
'Top' always jumps to the Top, or start of the current file.
'ToC' always jumps to the current file's Tables Of Contents.
'Here:' is the name of the current section, which should generally
appear in the Tables of Contents.
'Known' items that are recognized as facts that the time of
publication.
'Assumed' items that are current assumptions the time of
publication that should be confirmed or for which the optional
outcomes should have contingency plans.
'Past' dates that include prior dated material or material
from previously published Conclusions or Recommendations.
This section of this file uses a Date type of title bar to separate,
label and identify its contents appropriately.
The material in this section of this file is in chronological
sequence. While this makes it possible to easily review the evolotion
of the material, it does require first reviewing material that may
not longer be current. An alternative to this 'flow down' approach
may be to jump to to the most recent calendar date and rely on
existing hyperlinks to be able to follow 'thought threads' backwards.
Efforts will be made to create a list of the threaded thoughts in
order to bring the topics to the attention of Users.
This approach to organizing material by date has the added benefit of
obviously displaying the frequency of updates and of allowing people
to jump into a specific time range easily.
It may make sense to move Past items into the Concluded section of
this file. Perhaps this approach could even by used within specific
clusters of material that has been Categorized.
Note: Combining the use of the 'em' tag and my 'hCmnt' style only
works to my satisfaction with some relatively elaborate raw html.
I should add a hyperlink that jumps to the Backround section
just below the current set of Calendars, in order to make it easier
to return to the main TitleBar for this file.
The preceding titleBar should be moved above the Background
title and should be replaced with a subTitleBar that deals with just
this Background section.
The following obsolete material is stored within this
Date until it can be relocated.
I need a single row nested table for the H2 levels of Findings. At
the extremes, a table will either be full width in a single row, or
if it become multiple rows, is not constrained until it becomes a
full screen's display depth of rows. (Technically, even these
limitations can be exceeded if scrolling is acceptable.
The following table the serves as a template for the h2 levels.
This section was the first incomplete introduction of formal report
headings into this file. It is merely being tested at this time in an
attempt to determine the value of proceding. Considerations that may
need to be balanced include:
Creating an apparently complex file structure that causes more
confusion for viewers than they care to tolerate.
Adding as much content as practical to this file, in order to
reduce the number of files that are being maintained.
Determining the optimum balance between replicating the
Contents Boxes for convient access to hyoerlinks, but thereby
creating additional mainetence effor, should the links change. For
example, replicating the Status box is un-necessary, if the ToC
link is used to return to the Tables of Conent, which can then be
used to go to the next Present section, rather than going there
directly.
'Domains' (Perceived Dimensions) may be introduced to
accomodate at least the two views of Time and Space.
This "Past items:" section was restructured to include DateTitleBars
and to position "Known facts:" and "Current assumptions:" properly
within this Background section.
The increasing use of Outlook during the last couple of weeks,
included capturing much of the date related material that used to be
in this file, in new environments.
This file's main Navigation Bar was refined. The use of colors was
abandoned in favour of simply using nested Boxes to differentiate the
Return levels.
The redesigned 2004-04-24 date now cascades to ths area where more
details about this day may be found as opposed to returning directly
to the current Month calendar.
A preliminary 'thisYear' calendar was incorporated into this file.
Js = John Smart -
(2004(01(..))) (29) confirming Email, copied to Raa, Jaw;
(28) Js email & Hwo called to discuss 'urgency';
(26) Dfx Interest & Resource review
(22 13:30-15:30) Js & Hwo met to discuss telco data acquisition
2004-01
Ba
...
Bb
Aa
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Aa = ...
Ba = ...
2004-01
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Ba
...
Bb
Aa
Aa = ...
Ba = ...
The tables in this page segment are 'pristine', being devoid of
inputs so that they can be used as templates. They are included here
to illustrate the various time visualizations that have been
effective so far.
Millennium
Century
Decade
Year
Month
Week
Day
Hour
Day
Week
Month
Year
Decade
Century
Millennium
2000
....
2003
2004-
01 - January
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
-02
...
2005
....
The preceding table appears to be replicated. It is included a
second time because it is a template that has been condensed into a
single text line.
The next set of generic templates should be populated at specific
levels in order to be useful.
Extend the nests to include minutes, in multiples of :05 initially.
The Past, This, Next structure is probably not effective.
Try a mirror with This* as its center while Past expands to the
left and Next expands to the right. The building blocks exist in
the 'reversal try.
This 'Past' copy of the ThisWeek table can be:
- Cut down to a pristine state.
- Populated with Complete tasks from this week.
- Needs refinements to its header row that, once made, should be
taken back to the this week table.
This table should evolve to aggregate significant events that need to
be summarized.
People (individuals) can be grouped into Teams that are as small as a
single pair, or as large as the whole population of the planet.
Furthermore, Individuals are inevitably members of more than one 'Team'.
This is an attempt to set up a 'thin' 'People' table.
This table's 'nesting' takes place on the right side since the
Individuals are the smallest organization unit that can be encapsulated
in organizationstructures that may expand to the right.
Notes related to the concept of an 'Enterprise' are being developed
in an attempt to explain the ways in which Individuals form into various
types of Teams (or Groups) to Collaborate within an Undertaking.
Recent considerations have led to using 'ByGroup' to replace the
'ByTopic' heading. This may address a number of accumulated concerns and
also introduce a few new considerations. Specifically:
A 'Group' could be as small as two people (discussing a
'Topic') or as large as a global organization such as the United
Nations. A heiracrchial clustering that encompasses these might be:
'Topics' and 'Subjects' are not clearly differentiated in
common usage of English. While the current Glossary entries define
the difference in terms of the Time dimension, allowing the 'Subject'
to be thought of as the current 'State of the Art' independant of
Time, this could alternatively be achieved by creating a current
Summary of the accumulated Topics.
. . .
Preliminary notes related to Topics (of 'conversation' or
'discourse' or 'works in progress' or 'ideas under development'):
Topics may span dates, creating an important dimensional context,
as opposed to Subjects whose material is generally structured
according to criteria other than time.
Various Collaborators ('Users' (of this file)) may have specific
needs that require accomodation.
...
. . .
ByTopic
IPSA
HJL
BMO
PDS
RT
DFX
Hwo
Current Users' area:
This area (may need a link from the Top of this file as opposed to -
to be returned to the Top of the file in the Preface area), located
conveniently near the top of this file, may be used to house
information temporarily of interest to various users.
This area will enclose items that are parts of current discussions
with various Associates.
2004-02-17 meeting in Toronto:
Wiki notes predominantly regarding @010 Winter Olympics.
2004-01-14 Angela:
The browser's 'back' facility can be used to return to
the top of this file, as could the Ctrl+Home keys.
The RightClick mouse menu is particularly convenient but,
sadly, is not available to MAC users. Its appeal is simply that it
presents a menu which includes a 'Back' option which functions
identically to the one on the Browser's Control bar, but without
requiring the mouse movement to the top of the window that becomes a
source of tendonities for 'couch potatoes' whose most intense form of
physical activity involves the use of the Remote Control for a
television.
Agriculture Canada is ending its work with biotech giant Monsanto to
develop wheat that is genetically modified to make it resistant to the
herbicide Roundup.
FULL STORY:
Monsanto040110
The first bar is an example using the color codes and their assigned
numeric values from electronic resistor encoding standards. The
second bar is the values assigned by the current RGB model technical
specifications underlying HTML.
Blue
MediumBlue
DarkBlue
0 black
1 brown
2 red
3 orange
4 yellow
5 green
6 blue
7 violet
8 grey
9 white
A gold +/- 5%
B silver +/- 10%
C white
D white
E white
F white
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
0 black
1 silver
2 grey
3 white
4 maroon
5 red
6 purple
7 fuchsia
8 green
9 lime
A olive
B yellow
C navy
D blue
E teal
F aqua
This is a test of Silver as a background color for comments, with a
colored border to distinguish mine (Hwo=blue).
The color bars in the next area of this file are an early
(now 'out of date') test of what can be done. As time allows a more
more elegnat Style Sheet will evolve that can then be used to create
a much more effective illustration that this one.
Ideally, a proper illustration will even demonstrate an
answer to Angela's suggestions regarding how a chat might be
'threaded' effectively by using a combination of Colors and Columns.
Gremlins appear in both '2' rows. Also, the 'A' and 'B' columns
of row 1 and a couple of others appear to be wrapped because of
window constraints, as opposed to invoking scrolling.
Much 'real' work needs to be done to define styles that are
effective, probably even recognizing the idiosyncracies of particular
audiences, now that the simple technical stuff is done.
. . .
... Confirming that BR does not interrupt it.
... ensuring that the effect does not persist inappropriately.
Colors is documented at W3c html 6.5 as: Black, Silver, Gray, Maroon,
Red, Purple, Fuchsia, Green, Lime, Olive, Navy, Blue, Teal, Aqua.
The preceding material should be transformed to become part of our
EsDb ConCepts.
.
.
.
.
.
.
.
.
This is now finally a display area that I am working in. This means
that I am ready to add the titles to this file for style. However, I
will once again have to limit myself to just another interim step since
it seems that I do not yet have the ability to spanLists.
The following bars should be removed once the corresponding
test segments are removed from my style sheet.
This Conclusions chapter may be an effective location for a directory
of available Pages, especially those that have common users who may
link to them from different points of origin. Currently these exist
as entries in the HwoPages Appendix, but it is obvious that a more
informative table can be constructed and positioned here.
First, the logical view of information in a Page heirarchy:
(S)ubject
(T)opic
(F)older
(P)age
(V)iew
Then, the restrictions inherent in specific physical
environments can be applied to meet the needs of various User(s).
These different environments are denoted by using a set of disk drive
letters to denote fundamentally different environments. An
illustrative table is available via
Ý
(use your Browser's 'Back' function to Return here), the same link as
is incorporated into the generic 'nBar' table available throughout
this file.
Finally, it becomes possible to combine all of the preceding
into a structure that:
Recognizes:
A Subject will generally start as a
single page, as may a Topic and as might the introductory
comments stored in a Folder.
A file generally grows until its contents need to be
restructured within a folder.
A file may be 'spliced', removing a block of text to a
new file that can be shared as a part of different Contexts.
...
...
...
It is already obvious that some of these Pages will inevitably grow
to become files in their own right. At present, these pages are
useful to:
Simplify the Views presented to a Novice user who is not yet
sufficiently experienced to appreciate the denser display that
Experts prefer.
Facilitiate printing, since html does not really support
pagination.
...
It is also important to note the the concept of a web 'page'
generally maps to a single file. However, files may contain multiple
apparent pages or Views, which, as in the case of this file, are
delimited by white space, which can be avoided during navigation, by
well placed hyperlinks and their target anchors.
Additional Conclusions include:
RawHtml certainly provides maximum control over vitually all
aspects of the Browser's visual presentation.
There appears to be sufficient value in this EnterPrize to
warrant further efforts.
Future elaborations of the preceding statement could include:
A "guesstimate" of the size of the potential Reserve value.
. . .
Bring the '3ballsTemp.jpg file in from janus, rather than I:.
This page segment is being expanded into a Table of Contents for
Appendices.
To make room for the 'Opened' boxes of hyperlinks, the titleBars
"Foreword', 'Introduction' and 'Concluded' links have been replaced with
'...', but are still active.
This area of the file may include just links to other html pages that
exist in 'N:\...\Pub\Pages'. If so, then these pages should at least
contain a 'Back' link to return to the users point of origin.
Other 'HwoPages' included in this section of this file may include
pages from my SushiWike that are stored here to avoid the problems of
that environment's editor. These HwoR(eport) pages are in alphabetic
sequence, ignoring their common HwoR prefix which has been replaced
by the string '....'.
To improve the presentation of these pages within the wiki, a HR has
been added to separate navigation aids from the rest of the content.
This appears un-necessary when the source is displayed directly
within a browser.
This table introduces 'navigation' symbols that are currently being
used to indicate Back, Up, Down and Forward respectively. By using
these, it is possible to eliminate the redundant TitleBars that are
included at the start of each Chapter.
{
/\
\/
}
There may also be a use for these (temporary) symbols.
{{
}}
|{
}|
These symbols should be replaced in the near future.
This page is my initial attempt at setting up a series of html pages
within this wiki. Ideally, this page displays readily within both a
standard Broswer and the sushi wiki since I am using a raw html file
to store the contents and am then copying it into the Sushi simply so
that automated procedures using SushiUtils can access the content.
I should try to create the structures that I need to automatically
assemble an html file from various components such as this page.
These html based pages seem to be able to accomodate all standard
html. This should include supporting the nested table structures
that I seem to be developing.
This page can be edited directly, using TseEd but,. since the html
character substitutions will have to be made, it is probably easier to
just paste the new text.
The entries in this Glossary result from Hwo's attempts to precisely
define his use of words. Since this may not coincide with common usage
practices, these entries contain both his working definitions and may
also contain a statement of the intended scope these definitions have.
This Glossary is shared as a resource by several other files. Thas
makes it impossible to provide explicit hyperlinks that allow a User to
return to the point they were at prior to jumping here. Users are
reminded that the Return function of their Browser can be used to do so.
Within this glossary, capitalized words may also be entries, at least
until such time as this demarkation is replaced by a standard hypertext
or mouseOver methodology.
Additional words that I should include given the specific meaning I
generally intend to convey include: ... (Strength, Weakness, Threat),
...
The final task (formal completion confirmation) of a Plan, generally
published using a project planniung tool such as Microsoft's Project.
This is because ...
Note that Hwo's use of Goals and Objectives is differentiated since
these terms are frequently used interchangeably by different members of
different groups in spite of being defined by various groups in
conflicting manners.
A master alphabetic Index table may be needed. The structure of this
section of the file needs to be considered in the light of its role as a
traditional Index, which list all of the appearances of a term,
throughout the file. The Index sections can be propogated entirely in
advance since they will be needed.
In the following Day segments of this file, this month's calendar
header will not necessarily have all of the Dates set up as active
hyperlinks. Hence, it may be convenient to:
Use the "2003-mm" (in the upper left portion of each day's page) to
return to the calendar for a month since it generally has hyperlinks to
all of the active dates.
use the '/\' and '\/' links to skip to the Preceding and Follwing
months, respectively.
