From keld  Sat Sep 30 23:58:56 1995
Received: (from keld@localhost) by dkuug.dk (8.6.12/8.6.12) id XAA07474 for sc22; Sat, 30 Sep 1995 23:58:56 +0100
Message-Id: <199509302258.XAA07474@dkuug.dk>
From: keld@dkuug.dk (Keld J|rn Simonsen)
Date: Sat, 30 Sep 1995 23:58:55 +0100
X-Charset: ISO-8859-1
X-Char-Esc: 29
Mime-Version: 1.0
Content-Type: Text/Plain; Charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Mnemonic-Intro: 29
X-Mailer: Mail User's Shell (7.2.2 4/12/91)
To: sc22
Subject: web format draft

DRAFT WWW Sample Pages
(Plain text form of document JTC1/SC22 AN-8, 22-Sep-1995.
 The notation _..._ denotes underlining in this plain text form.)


The attached pages are DRAFTs of sample WWW pages for SC22 WGs.

These sample pages here are offered for comments.  Please do comment.

The HTML formatting requirements are very straightforward HTML.
No complex capabilities are required for creating or viewing such pages.
Online examples will be provided at a later date.

==================================================================

   [ WG937 Home Page ]
+-----------------------------------------------------------------
| 
| _ISO_/_IEC JTC1_/_SC22_/WG937
| Programming Language TECO
| 
| Scope and Purpose
|
| The TECO working group is defining a standard for text editing
| commands and, more generally, any kind of executable line noise.
|
| Available Information
|
|   General Information
|     _Press Releases_
|     _Contacts_
|     _Membership
|       _Contacts_
|       ...
|     _Publications_
|       _Committee Drafts_
|       _Technical Reports_
|       ...
|   Administrative Information
|     _Meetings_
|     _Internal Documents_
|   Subprojects
|     _22.99.11.22.33.44.55.66.1 Cool programming tricks in Teco_
|     _22.99.11.22.33.44.55.66.2 Documentation conventions for Teco_
+-----------------------------------------------------------------

1. The items ISO, IEC JTC1, and SC22 are backpointers to home pages
   for these groups.  On pages other than the home page, the WG name
   points back to the WG home page.
2. It would be desirable for these parent organizations to provide
   official GIFs so that logos could be used instead.  Until this is
   done, however, the above textual format is recommended.
3. The items Contacts, etc. under General and Administrative Info
   are links to other pages with particular recommended formats
   (see subsequent pages of this document).  Subitems are pointers
   to the headings within those pages.
4. The Subprojects are pointers to pages which have the same
   recommended format as this page.
5. If there are no items for an information topic, the item
   (e.g., "Press Releases") may be omitted from this list and no
   corresponding page need be generated.  If a category name is not
   required (e.g., "Subprojects"), it may be omitted as well.

==================================================================

   [ WG937 Membership ]
+-----------------------------------------------------------------
|
| _ISO_/_IEC JTC1_/_SC22_/_WG937_ Membership
| Programming Language TECO
|
| Contact Information
|
|   _Convenor_
|     _John Doe_
|     ACME Corporation
|     New York, NY 00000 USA
|   _Project Editor_
|     _Fred Smith_
|     Ye Olde University
|     London AA00AA UK
|
| Member Organizations
|
|   _P-Members_
|     _Australia_
|     _Japan_
|     _United Kingdom_
|
| Liaisons
|
|   _WG2037_
|   _WG5678_
|
+-----------------------------------------------------------------

6. Hot titles ("Convenor" and "Project Editor", and later also
   "P-Members", "O-Members", etc.) are pointers to SC22-provided
   descriptions of the roles of these individuals so that those
   perusing these pages can more usefully select a correct point
   of contact.
7. Individual contact information should not be included without
   permission.
8. Contact information for both individuals and organizations might
   be "mailto:..." or convenitional home page URLs.
9. Liaison information is provided only for formal (SC22-recognized)
   relationships.

==================================================================

   [ WG937 Publications ]
+-----------------------------------------------------------------
|
| _ISO_/_IEC JTC1_/_SC22_/_WG937_ Publications
| Programming Language TECO
|
| Committee Drafts
|   _CD 923456 Specification for the Programming Language TECO_
|
| Technical Reports
|   ...
|
+-----------------------------------------------------------------

10. If there are no publications, the Publications section should
    contain merely "None."
11. The categories ("Committee Drafts", "Standards", "Technical Reports",
    etc.) are pointers to SC22-provided descriptions of the nature
    of these categories.
12. Pointers from the document should include all and only the
    public documents (active Standards, Committee Drafts available
    for review, Technical Reports, etc.) which have been produced by
    this committee.

==================================================================

   [ WG937 Meetings ]
+-----------------------------------------------------------------|
|
| _ISO_/_IEC JTC1_/_SC22_/_WG937_ Meetings
| Programming Language TECO
|
| Past Meetings
|
|   _9-17 March 2003, Tokyo_
|   _1-4 May 2003, Geneva_
|
| Planned Meetings
|
|   _10-20 Oct 2004, Orlando Florida_
|   1-5 Jun 2005, The South Pole (tentative)
|
+-----------------------------------------------------------------

13. Past meeting information should point to a working group document,
    if any, containing the minutes of the meeting.  (Information about
    the meeting logistics, attendance, documents considered, etc. may
    be obtained from the minutes, which may itself contain hypertext 
    pointers to home pages of representative bodies and committee
    documents.)
14. Future meeting information should point to a working group document
    containing details of the meeting plans, if available.  Tentative
    meetings should be indicated as such.

==================================================================

   [ WG937 Internal Documents ]
+-----------------------------------------------------------------
|
| _ISO_/_IEC JTC1_/_SC22_/_WG937_ Internal Documents
| Programming Language TECO
|
| Standing Documents
|
| The following documents are _standing documents_ of this working group:
|   _ISO/IEC JTC1/SC22/WG937 "Teco" N12345 Charter of WG937_
| Standing documents of SC22 may be obtained from _the appropriate
| SC22 page_.
|
| Document Register
|
| The following documents are the registered documents of WG937:
|   _N1 Welcome to WG937_
|   ...
|   _N12345 Charter of WG937_
|
| Related Documents
|
| The following are cross-references to additional documents that are
| or might be included in Publications of this Working Group:
|    _ISO-2738973-2002 User Interface Guidelines for Hand-Held Supercomputers_
|    _Fred Smith's Notes on Packaging of Computers as Breakfast Cereal Inserts_
|
+-----------------------------------------------------------------

15. The "Standing Documents" section will contain pointers to all and only
    officially designated standing documents of the committee belong here.
    If none, the list of documents would be replaced by the word "None."
16. The "Document Register" will contain an index of documents of the
    committee.  Those that are available online should contain hyperlinks to
    the actual document.  Those that are not available online should contain
    hyperlinks to information about who may order paper copies and how such
    ordering can be done.  (If this entry gets overly long, it is reasonable
    and appropriate to include here a pointer to that another page which
    contains primarily that information, so that the surrounding information
    here may be accessed more efficiently.)
17. The "Related Documents" should either be documents which in fact do
    appear as referenced documents of a committee publication or that have
    been determined by consensus of the working group to belong on this page.
    In this way, it is possible to include pointers here to documents which
    are not ordinarily referenceable by ISO standards but that are important
    background or useful informal references to members of the committees or
    interested parties.  Also, by requiring a consensus of the working group,
    we create an obstacle to the unfair and capricious placement of proprietary
    cross-references by requiring that the committee jointly agree that the
    reference is appropriate.

