PROTO - SC22 WG prototype homepage structure

Source: Keld Simonsen
Reference: SC22 N1970: Annapolis resolution 95-37
Date: 1996-02-01
Status: living document based on approved SC22 web document

ISO/IEC JTC1/SC22/WG99 homepage http://www.dkuug.dk/JTC1/SC22/WG99/ is a prototype web entry page (homepage) for SC22 WGs. It is the updated version of the apporoved SC22 web document

The homepage structure has been created, based on the original AN-8 contribution, offline communications with Jim Isaac and Keld Simonsen, and email contributions from Brian Meek, Bob Follett and Bob Mathis. Also consulted were the ISO/CS contributions on "The Discovery and Retrieval of Internet Resources from ISO" (ISO ITSCG AWG 1 N27) and "Identification and Distribution of JTC 1-Related documentation" (JTC1 E3778) and general Internet guides on HTML style (http://union.ncsa.uiuc.edu:80/HyperNews/get/www/html/guides.html).

The pages have been made so it should be straightforward to generate it out of existing WG material, combined with the produced prototype web pages, which have been made in a HTML-utilitities independent, portable and strictly conforming (to HTML 2.0) way. Basically what you need is the WG scope, the convener's report to the SC, your membership and liaisons lists, and then possibly descriptions of standards for example as text from the originating NP. Keld Simonsen, keld@dkuug.dk has offered to help in merging the WG materials with the HTML sources, as well as offered hosting of the pages.

The WG web pages should be structured so that it is readable, also as a freestanding paper submission, as these pages are also an example of.

The prototype has the following pages:

index - with overall description and shortkeys
news - with individual articles
standards - description of published standards
projects - work in progress - conveners report
internals - for the work of the WG: access to ftp archive, emails
meetings - including next meeting
contacts - membership, liaisons, related areas

The "internals" section is for confidential information, such as standards and other copyrighted work, working group documents and email, and provisions are made for accessing this information via individual userids and passwords. The rest of the information scheduled as per this prototype web structure has been checked with the proposed JTC1 guidelines (JTC1 E3778) and should be OK for general distribution, as the following document types are classified for "open" distribution: Document register, secretariat report, programme of work, meeting notice, meeting agenda, meeting report, meeting resolutions, together with procedural information. NPs are not for open distribution, but a deriative of it produced for public information should be OK for open distribution. These JTC1 guidelines does not cover the WG level, but SC22 should make guidelines for the WGs that could apply to itself as well.

A number of ressources are drawn upon, including the ISO and IEC web servers, and the document lists provided by Danish Standards.

A number of guidelines for each of the documents have been written.

The structure of the WG web pages most likely will differ somewhat from WG to WG and will also neccesarily develop over time, but some structure should be kept common, also for use in general ISO-wide text retrieval and web systems.

Maintaining web pages

The WG should appoint maintainers for each of the documents, in many cases the pages will be maintained by the same person.

It is important that the web pages are well kept. A way to do this is to have a direct relation to information already being generated by the WG, such as conveners reports, project status, membership lists, ftp archives etc. As the web pages are advised to be readable clear text, the web document could be the same as the normal WG document.

Some of the information needed may be be automatically updated, like ftp archive contents and email subject list, and some may be done already by other sources, such as updated standards lists from ISO and document lists from Danish Standards.

You should check your document for correct HTML before releasing it.

Keld Simonsen