[HwoPages] N:...HwoPages

Note: 20-[061130] This page is in the midst of major changes!

This page is expected to evolve into;

The initial Introduction to the Hwo library of PUBlished pages.
- As such, it is a WIP that is frequently over-written.
A set of nested tables that can be used to categorize the referenced pages, as the envisioned library of pages grows.
An explanation of Hwo's web page style that is;
- Written for a Novice level User and includes a few simple Footnotes for practice (e.g. [9]).
- A set of examples and references that illustrate what is possible within the current hwoStyle and the state of the art, as practiced by Hwo.
- Heavily influenced by the Goal of efficiently communicating by
  - Assembling existing content, within an appropriately focused Context.
  - Creating new content onlyOnce, in accordance with c2:OnceAndOnlyOnce concepts.
  - Continuously refining this library of pages, but only as specific content is needed as particular components of the tasks that are a part of active Projects.
An central [TOC] for the emerging "virtual" library of pages.
...

[Foreword]

This page serves a number of diverse and unrelated purposes;

It is a directory for and an [Introduction] to the entire set of [HwoPages] (Hans WObbe's PAGES published on the internet).
- It contains (relatively elaborate) information regarding the conventions used in creating these pages.
  - This material is generally contained within this Foreword chapter in an effort to balance the needs of some interested parties (including contributing Authors) against those of the general reader who wishes to only refer to this material when it is needed.
...
It is a central (default) repository for (reference) material that has not justified the creation of a separate page.
It is a test facility for various aspects of the Collaboration experiments.
- It is frequently manipulated using radically different software (e.g. being edited with various c2:WikiEngines, textEditors, MSC Word, ...). For this reason, the apparent hyperlinks may not be fully functional, in a consistent manner, at times.
- Maximum practical page size for this pageType.
...

Furthermore, the text of these pages makes extensive use of wiki concepts, such as ...

Several of the c2:WikiDesignPrinciples
[TransClusion] and other microContent concepts fundamental in tiddlyWiki.
cw:LinkLanguage
...

HwoPages


loCal


datafix fIrewall(ed)


interNet (public)


internet Private, by Password

hwoPages are available in a number of different environments that can be distinquished by the apparent (disk) drive letter that preceeds their names. These 'drive letters' are actually c2:InterWikiMap references within the Author environments.
- Other (generally longer- e.g. 'c2' = Wards Wiki, 'cw' = Community wiki, 'mb' = meatBall, ...) interWikiMap prefixes may also appear throughout these pages.
...

Abridged Table(s) Of Content(s)

This abridged table of contents provides an initial overview this file's content that can be used to jump to those areas that are most important to people not familiar with the structure of these pages.

[11] An introduction to Footnotes ( a key navigation feature used in this library of pages).
- (Return to the Top of this page by clicking this '[0]' or using the 'Back' (via rightClick).)
- [namingConventions] for Footnotes and larger blocks.
[12] Typographic conventions.
[2] Table(s) of Content(s).
[80] Work In Progress comments

[11] An Introduction to Footnotes.

This Page (and most of the others in this library) uses "Footnotes" (internal 'anchors' and hyperlinks).

Since considerable use is made of these Footnotes, beginners are strongly advised to practice here (in a less complicated example) until fully grasping the basic fact that there are always at least two apparent Footnotes.

The 'destination' value exists only once (always at the beginning of a line) and its apparent link can be used to return to the FIRST appearance of the Footnote value on a page.

Authors may have structured their use of Footnotes in 'ranges' such as those appearing in the Table of Contents example on this page.

[namingConventions] for Footnotes and larger blocks.

My hyperTextNaming conventions have evolved under the influence of several forces. Specifically;

[BobTrower]'s [STD] organization.
tseEdit's macro support and the need to use indirection to access files that are frequently relocated. (Hwo's A.EXE)
HTML standards
Wikis and their use of CamelCase?, to generate HTML from simpler markup.

My camelCaseNaming conventions...

Since western cultures generally read left-to-right, top-to-bottom; the inital string segments are assumed to be most significant.
Context expectations may affect the legnth of these inital segments, in order to make them more or less specific.
- Context expectaions are set by various assumptions such as;
  - The size and diversity of the Audience.
    - Personal notes can be very short (and cryptic, unless the (short-hand) codes are understood).
    - Professional audiences generally accept jargon since it is more efficient and can be more precise.
    - Effective communications with the general public must be relatively simple.
The first set of camelCaseSyllabels should are generally the Title.
- The [Zz] syllabel acts as a delimter, ending the Title.

My footnoteNaming conventions

These conventions are heavily influenced by the tools I use;
- mb:WxWikiServer
  - Footnotes are alphaNumberic strings that actas bydirectional hyperlinks. They can only include the characters 0-9 & a-z (which are treated as case-insentitive.
- qEdit - (TSE The Semware Editor)

My pageNaming conventions are affect by;

html pages that refer to other pages assume these pages are siblings within the same folder.

[111] Chapter numbers are always single digit Footnotes.

Deprecated...
For example:


[0] [1] [2] [3] [4] [5] [6] [7] [8] [9] [zz]	Z

The preceding [0] ... [9] values are the single digits that are consistently used as Chapter numbers throughout this library of Pages.

... . .

[12] Typographic conventions.

The typographic conventions that are being adopted in this library of pages is heavily influenced by:

The skills of the participating Authors, as well as their Assistants and their Editors.

The Tools that these participants use to create their contributions.
- Wiki software generally provides an easily typed set of 'markup' conventions that are then 'rendered' to create the effect of HTML when viewed with browser software. In this case, the resulting effects include:
  - c2:CamelCase which is used to create hyperlinks automatically, within Wikis.
  - Italics are used to distinguish;
    - Editorial comments, or
    - an Included page, identified by its name, when used inside the upper left corner of a bordered table.
  - The ";" is used at the end of a line introducing a list (rather than the traditional ":") since the : is parsed as a wiki metaCharacter used to create interWiki links.

The following line illustrates some unexpected rendering as a result of using the 'pipe'.

This results from the use of the pipe symbol as table markup within the usemod wiki, that was carried forward into wxWikiServer too.

... . .

[121] Title (heading) conventions.

see appendix ...

[Contents] Table(s)

The entries in this generated Table Of Contents are hyperlinks that will skip to the named sections.


0. 0. 0. 0. 0. 1. [HwoPages] [http://janus.datafix.com/hwo/HwoPages.htm N:...HwoPages] 1. [Foreword] 1. 1. Abridged Table(s) Of Content(s) 2. [Contents] Table(s) 3. [Summary] 4. [Introduction] 4. 1. [Observations] of 'fundamental' importance. 4. 2. [Audience] assumptions; 5. [Findings] 5. 0. 1. [fPreamble] 6. [Conclusions] 7. [Recommendations] 8. [Appendices] 8. 1. [Glossary] of terms 8. 2. [Versions] 8. 2. 1. Deprecated material 9. [EndNotes] 9. 1. [pageTypes] 9. 2. Credits;

This Table shows that the structure of this that of a standard report, at least at the level "1" headings.

Deprecated (?) ...

Develop the following list into a type of 'local [TOC]'.

[11] An introduction to Footnotes.
[12] Typographic conventions.
[511] Past activities.
...

If using the following table to navigate within this page, do not forget to avoid the use of the single digit values Footnote unless this preface is the intended destination.

HwRptToc

[TOC] HwRptToc


[Covers] [Foreword] [Contents] [Summary] [Introduction] [Findings] [Conclusions] [Recommendations] [Appendices] [EndNotes]

This Chapter TOC and its bi-directional 'footnote' hyperlinks are included as navigation aids for Browser-based Audiences.

This table of footnotes is being phased in to replace the [z] version that predates the ability to have alphabetic characters in footnotes.

[otherPages] in this library include;


HwMo	a stale 'rawHtml' page, retained as a demonstration of prior experiments and as a research tool.

This is not a complete list, even at this early at this time.

[Summary]

See the [Foreword] for a more up-to-date version of this material.

This page is an introduction to a library of pages, made up of collections of pages that are often stored in other (perhaps even) restricted sites. The following simplistic convention may be a useful indication of how all of this material is organized.

Files that are prefixed with;

:c\... - are local references, available only to Authors on their computers.
f:\... - are Topics that exist within a set of phpForums, ranging from Public, to Semi-Private, to Private.
i:\... - are Intranet files available on the Dfx LAN.
n:\... - are interNet accessible files that are generally readOnly.
p:\... - are Private folders that require interested parties to be invited to Log-in.
p2:\... - are pages that reside on a phpWiki.
s:\... are Secure files that cannot be accessed, except by individuals with specific authorities.
etc. ...

[Introduction]

Since the emergence of the World Wide Web as an adjunct to the Internet in the early 1990's, web pages have literally exploded into existance in a manner that appears not at all dis-similar to the emergence of the universe as described in the Big Bang theory. As these web things begin to "cool down" a bit, it is becomming apparent that "not all pages are created equal".

[Observations] of 'fundamental' importance.

Specific Observations include;

Web pages are quite different from paper pages.
- The technologies used to create and deliver web pages cause important disctinctions between the web and paper media.
  - ...
- ...

Writing efficiency is heavily impacted by tool choices and skills.
- These pages are created using Wiki technologies. This results in;
  - Adoption of "onlyOnce" writing methods.
    - Components in this library of pages are intended and designed to be written c2:OnceAndOnlyOnce.

This material is expected to remain a Work In Progress that may well become a "Never Ending Story". This has several implications;
- Extensive use is made of hyperlinks to other trusted repositories, such as;
  - c2:WardsWiki
  - mb:MeatballMission
  - cw:SiteMap
  - wp:Main_Page http://en.wikipedia.org/wiki/Main_Page
    - the :wp does not seem to be working?

[Audience] assumptions;

First and foremost, this page in particular is being written specifically for 'publication' via the internet. This basic fact has some implications;

The internet makes it difficult to follow the traditionally important maxim; "Know your audience".
- Even worse, given the current "state of the (hypertext) art" [SoTa], it is barely possible to even know what any member of the audience may see when viewing this page.

This page is a high-level object that may be referenced by many unrelated Audiences, Authors, (web) Sites and various independantly published Thoughts, including other Pages which are not publically available.
- This 'plurality' of uses makes this page more of a 'reference' document, than a self-contained page that always presents material in a manner that is internally consistent.

Deprecated material, being salvaged.

This page has been on the 'net for a considerable time period, during which a great many evolutionary cysles have occurred, For that reason, it has accumulated considerable mateerial that needs to be 'refactored' (a concept from c2:WardsWiki.)


[ !HwoPage0] The space in '[ !' breaks the INCLUDE sysntax and renders the page name as a simple hyperlink (all be it one that probably appears 'broken')

[Findings]

[fPreamble]

This Findings PREAMBLE segment tests the value of having separate, local "preamble" comments in ecah of a report's Chapters. As such, it uses ...

An initial list of Footnotes that are local to this chapter.
...

This list (of the footnotes) and points in this Findings chapter provides an overview of the sub-heading that have not been included in the [Contents] in order to conserve space in that list.

[FiPreamble]
Technology is a signifinant force affecting [PageStyle].
[Collaboration] is affected by tool choices.
...

[PageStyle] ...

[Collaboration] necessitates the use of tools that at least produce compatible outputs.

The caption for this segment is particularly pertinent if Collaboration is expected to be as efficient as possible.

This segment may be obsolete, since footnotes were enhanced to include alphabetic characters.


RpT50: [50] Preface 500 'Findings' list: 501 Preamble [51]: Status: [511] [Pst] Past: [512] [Ths] This (Present): 2005 year: 200501 month: 2005010 fortnight (decimal): 050103 date [513] [Nxt] Next: [52]: Observations:

[50]

As stated in the Foreword, this page makes extensive use of numeric footnotes. It also makes use of 'named anchors' which are equiavelnt to internal bookmarks that can be accessed directly by external programs that know both the page name and the internal anchor names. In general, these anchors appear in alphabetic sequence starting at [alpha] (aka "Alphabetic Topics").

[511] ('Pst') Past activities:

Initial Publications include:

[040821] HwoPages

[040906] HwoPage0

[041123] HwoPages - updated in an effort to confirm the use of the Prw image that Julie requested.

[050902] Logs showed spider activity on this page,

Linking to non existant references, given that this page is now automatically generated within my private wiki, and may well contain links that are only accessible on my private localhost.

[060411] Updated this page.

Tested the PUBLISH mechanism and confirmed that it is working satisfactorily.
...

[200604]

Publish the current version of this page.

[toDo2006041]

remove the remaining [ nnn] markup instances from this file.
...

Alphabetic Topics:


[0] [1] [2] [3] [4] [5] [6] [7] [8] [9] [zz]	Z

p2:CommonTextBlocks

This segment is resereved for future use, since the heading is a standard report heading that is likely to become useful in this page's future.

http://janus.datafix.com/hwo/photos.htm

[Conclusions]

"OnlyOnce" writing methodologies can be extremely efficient.

[Recommendations]

... . .

[Appendices]

[Glossary] of terms
[Versions] of this page.
[pageTypes]
...

[80] Appendices Work In Progress [WIP] comments:

Headings within this page are not yet consistent.
This page needs to be PUBlish(ed) or it needs to have a hardcoded link to http://janus.datafix.com/hwo/HwoPages.html
The HwoPage0 inclusion needs to be modified to eliminate the Footnotes that are references that do not exist in this page.
...

Add an Appendix of topicPages here.

These miniPages would consist of text that is needed to explain certain miniPages that should not have the information in them.
- e.g. ...N(ote) pages that have format constraints because of the way they are included.

[Glossaries]

This area of this mail file needs to be developed into a generic introduction for the various Glossaries that could be included, such as ...

Terms for the... Postal, Telco, ... Views.
...

##Glossary

[Glossary] of terms

Entries in this appendix are in case-sensitive, alpabetic order.

Required entris include; [Goals], [Objectives], ...
A simple list of the entries may be helpful, although this might need to appear very early in the file to minimize any confusion caused by Returns to the first instance of a footnote.
Inevitably, a cascading set of Glossary libraries will be needed, perhaps culminating in various existing public versions. (wikiPedia(?) or others that can be accessed using the interWiki capabilities?)
...

[Footnote]s are local, bi-directional hyperlinks.

[Goals]

[milliPage]

Recognizing the emerging influence of tiddlyWiki and its "microContent" termonology, the 'milliPage' term is used for the concept of an onlyOnce block of text. This is an attempt to distinguish blocks of Content that are used as small page segments from the smaller blocks of microContent that may be used as sub-block (paragraph) components.

[Objectives]

[SoTa] State Of The Art. This acronym exists only because the term is used so frequently that it saves considerable effort to reduce it.

[STD] Standard Directory Structure

An early effort at organizing files into directories (or Folders) that would minimize collissions in naming convenions
...

[WIP] Work In Progress.

There may exist many valid reasons for publishing WIP notes. This area may be referenced by such blocks of text.

Interestingly, this area itself demonstrates one of the valid reasons. For example; The cited reasons for publishing WIP notes could be listed here, but at the time of this writing, other matters were more urgent.

[dfx] DataFix - see www.datafix.com

##Versions

[Versions]

As of early 2006, it is apparent that Version numbers may no longer be needed, assuming that Date suffixes become a standard part of document names. There are, however, some considerations that have not yet been fully resolved. For example ...

Should the most current version of a dicument merely exclude the final Date segment?
Would it be more efficient to substitute an Alais suffic such as Aa... ; Ba... ; ...

The standard for Version numbers is being updated. In the mean time, the dates of recent changes are being provided, together with some notes.

Changes to this file are generally recorded by Date.

Completed items can easily be assigned the date on which they were finnished.
Future or Pending items could use the timePeriod notation that is crystalizing out of the efforts to rank and schedule activities appropriately.
Releases (tentatively defined as a published version of the file that may contain a set of changes accumulated since the last publication date) may need to be distinguished.
- This might be done by simply hi-liting the date.

Prior versions that are accessible at this time include ...

[050908]
...

This segment lists the dates when versions of this file are updated on the 'net.

[T051007] Added references to other components of the [HwoPages] library.
050927 Added an image segment to test pages/Flickr/html mixtures.
- http://janus.datafix.com/hwo/HwoPages.htm
050919 Added a couple of Assumptions to the Introduction.
- [SoTa]

[T051007];

phpForums; dfx/Private; ...
deprecated the use of the numbers [z] chapter numbers.

[050908] - Spider sighting note of [050902] added.
c;...050831 Added thoughts about using timePeriods in Version or Release names.
c;...050830 minor (but fundamental) refinements to support more active use of this page.
c;---050829

"Glossary of terms" heading.
published manually @ Dfx.

050826 Refinements added.
050824 Versions section added.

[toDo]

Consider the value of a set of local toDo's.
- If generalized, these could take the form of subbjectToDo...
  - where the '...' suffix could be a timeScope string or a Rank (Aa, ...) string.
- It may make sense to incoproate this into the Versions Appendix and perhaps allocate it to proposed Releases.
  - Try using the timeScope concepts to name proposed releases.
    - This allows precise Dates to be used for past releases.
[toDo2006041]
...

Appendix A

This appendix includes text from other pages that can be store more efficiently here, that 'in-line' in those pages.

...

Appendix B

Deprecated material

[512]

Deprecated...

Consider the use of a Revisions Appendix in conjunction with the preceding Pst (Past) page.

[513]

... . .

[52]

... . .

[EndNotes]

[ToDoHw] - pending tasks.

Develop endNotes based on Includes & Folders
Use the immediately preceding [9] to return to its first instance. Alternatively, the Browsers 'back' function or a mouse rightClick (not available to Mac users) can be used.
...

[MicroContent]

...
- Link to a 'net based definition, probably the tiddlyWiki one, or one that I incorporate into mb:TiddlyWiki.

[TransClusion]

This Mb:TransClusion page provides some additional information, which may be important given these pages making extensive use of this approach and are create using a set of specific wiki tools that support it.

##pageTypes

[pageTypes]

from ThisDay;
- timePeriod(s) and Subjects (especially those that span Dates) generally contain Date miniPages or HyperNotes.
  - Each such page's Date HyperNotes will then be followed by the points (bullets) that are specific to the context of the Period or Subject.

Credits;


HwoPages9a Acknowledgements: This 'HwoPagePreface' is implemented as an instance of an internal bookmark ( or a name(d) anchor). Ryan Norton's version ( mb:WxWikiServer) of the Eddies Wiki software extended the Footnote support and added html named anchor support to the Include capability that was part of Eddies original software that was carried forward in several of the subsequent development forks such as the Michael van de Water ( c2:MichelVanDeWetering ) version. This respectful acknowledgment of the work of these developers exists because these page designs are heavily dependant on these features, as is the efficient Authoring the software enables.

[BobTrower] - for introducing the Standard Directory Strustures in the early days of our work setting up the Trilon / Royal Trust Product Initiatives Laboratory.

[hosting] by DataFix
...

[hosting]

This page segment is the last since its contents are rawHtml, making it convenient to share the trailing textBlock.

Any following list of pages (after the "Hosted by:... logo) illustrates a most useful feature of wikis, namely 'backlinks'.

Deprecated...

ZzPage

These footnotes provide a 'backstop' for the opening Z references.


[0] [1] [2] [3] [4] [5] [6] [7] [8] [9] [zz]	Z

[0]
[1]
[2]
[3]
[4]
[5]
[6]
[7]
[8]
[9]
[zz]

Add an explanation of this miniPage and the following 'skipped' notes into this page's forward.

2 - skipped; because it is in use in the heading.
3 - skipped; "
5 - skipped; "
6 - skipped; "
7 - skipped; "
8 - skipped; "
9 - skipped; "

[zz] - This footnote is a convenient way of reaching this pages backlinks.

Flicker/HTML test.

Copy area...

^{Hosted by:}

Generated 'backlinks':...
-

Abridged Table(s) Of Content(s)

[11] An Introduction to Footnotes.

[namingConventions] for Footnotes and larger blocks.

[111] Chapter numbers are always single digit Footnotes.

[12] Typographic conventions.

[121] Title (heading) conventions.

[Contents] Table(s)

[Observations] of 'fundamental' importance.

[Audience] assumptions;

Deprecated material, being salvaged.

[PageStyle] ...

[Collaboration] necessitates the use of tools that at least produce compatible outputs.

Alphabetic Topics:

[Glossary] of terms

Appendix A

...

Appendix B

Deprecated material

Credits;

Acknowledgements: