ANNEX HG
ISO/IEC
JTC 1 Web Server Policy
I. Web Page Structure:
The minimal structure of web based pages for JTC 1 and its SCs (jointly
referred to simply as committee). It is not intended to dictate structure
or content at the WG level.
II. Web Server Content: The
minimal structure/content of JTC 1 and SC web servers
III. Web Server Maintenance: Policy concerning the maintenance of
those web pages
It is expected that National Bodies and Committees
will utilise this document as they begin their
web-server implementation. Additional information is available in Tips
and Techniques for JTC 1 Web Pages.
I. Web Page Structure
Every JTC 1/SC web page shall contain the following structural elements:
(These elements may appear in any order, however it is
highly recommended that the committee retain the same style for all pages
within the committee's purview.)
1. Title Block (should have a common
"look-and-feel" within the committee)
a. Title of committee
with the ISO/IEC logo.
b. The page author and date created or
last modified (preferably generated automatically)
c. A version number
d. Optional use of a common
background image may also be employed.
e. Optional committee logo if desired
2. Body - contains information specific to the
committee. The use of forward navigational pointers is highly recommended
3. Web Master information -
who to contact for errors, suggestions, etc.
4. Consistent Set of Back Pointers (for example the
Parent Committee main page, Committee web-page design guidelines, primary site
information, etc.)
II. Web
Server Content
Each web server (JTC 1 and
SC) shall provide the following, mandatory information in the form of web pages
which conform to the common look and feel of the Web Page Structure appropriate
to the committee.
1. Description of the Organisation
Structure of the committee
2. Committee Membership (List of P, O, L members and the
contact information for liaisons and rapporteurs)
3. Committee Meeting schedule
4. Next meeting information
a. Agenda
b. Venue
5. Programme of Work
6. A single document register for all committee
documents
7. Personnel information on officers and members
Although optional, each secretariat is strongly
encouraged to add the following information as appropriate.
1. Frequently Asked Questions (FAQ) Page
2. Ballot information
a. Due dates
b. Document number of balloted text
c. Document number of
Summary of Voting
3. Procedures (which may simply point to the parent
committee's procedures)
4. News and Press releases
5. Links to committee relevant Publications
and Standards
6. Links to non-JTC 1 sites shall be done in such a
way that it is obvious to the viewer that what is being viewed is NOT under the
auspices or control of JTC 1. This is especially important in frame-based
sites.
III. Web Server Maintenance
1. Open Access vs
Defined Access Documents
The committee shall distinguish between open access vs defined access documents as per Annex HD.
2. Password Protection
The server administrator shall provide appropriate limited access to
non-members by use of group level passwords with appropriate notification to
users. Non-members attempting to access protected pages shall be
automatically replied to with a message stating the criteria for access.
3. Data Integrity
a. Site shall be backed up automatically
b. All Documents shall contain authorship
and timestamp information as defined in the Web Page Structure Title Block
The original document shall be considered the "source"
document. NBs or committees may utilise the
source document in a variety of ways:
a. By simply
linking to it or e-mailing its URL (highly recommended in the event that there
is no password involved)
b. Creating a new
document with a unique document number representing a cover letter plus the
content of the original document
c. NB mirroring of the original
document
In the event of a difference in
content between the original and the copy, the content of the original shall
take preference. It is therefore up to the administrator of the mirror
site or new document to ensure its
integrity.
d. Site shall utilise
virus checking - In the event a virus is detected, the files shall be cleaned
prior to updating or retransmission and the original sender of the infected
file notified of the infection.
4. Document Registration, Retention and Archival
a. Hierarchy
Structured with a
register list every 50th document
b. Access
- Each register shall show all Document
numbers, title, date, due date, including those
produced by the committee before electronic documents were available.
- Register entries shall be hot-linked to
the actual documents where available
- Provisions shall be provided to
download documents as a package (e.g. for documents with enclosures, annexes,
drawings, embedded data, etc.)
- Provision shall be made for providing
paper printouts of documents to those with no web access.
c. On-line Retention
Documents shall be retained for a minimum of
two years or two complete plenary cycles, whichever is greater.
d. Archival
After the retention period, documents may
be removed from on-line availability and shall be available from the
secretariat in a format at the discretion
of the secretariat. All WGs and SCs shall formulate a policy for the maintenance
of their archives and shall include this in their business plans and on their
web site together with information on the format in which the archived
documents are available.
5. Use of Embedded Executable Code (e.g. Java, Active-X,
etc) in HTML Documents
a. Care should be taken to utilise only those constructs which can be viewed using all
commonly available browsers.
Foreword
Table of Contents List of Abbreviations Index
Chapter: 1 2 3 4 5
6 7 8 9 10 11 12 13 14 15 16 17 18
Annex: A B C D E F G
H HA HB
HD HE HF HG I
J K L LA LB M MA
N O