MurdochNet Policy

Section 1: PREAMBLE

Section 1.1: Purpose
Section 1.2: Scope
Section 1.3: Field of Application
Section 1.4: Policy Vocabulary
Section 1.5: Key Terms

Section 2: INTRODUCTION

Section 2.1: Goals
Section 2.2: Boundary of MurdochNet
Section 2.3: Environment of MurdochNet

Section 3: CODE OF CONDUCT

Section 3.1: Servers
Section 3.2: Content
Section 3.3: Links
Section 3.4: Misconduct

Section 4: SERVER MANAGEMENT

Section 4.1: Registration of Web Servers
Section 4.2: Murdoch Sub-domains
Section 4.3: Alternate Domain Names
Section 4.4: Naming Conventions for Web Servers
Section 4.5: Availability of Web Servers
Section 4.6: Security of Web Servers
Section 4.7: Backup (Hardware, Software, Data) of Web Servers
Section 4.8: Web Server Software
Section 4.9: Responsibility for Web Servers

Section 5: CONTENT MANAGEMENT

Section 5.1: Content Categories
Section 5.2: Content Management Procedures & Practices
Section 5.3: Standards & Guidelines for Content Preparation
Section 5.4: Murdoch Conventions for Content Preparation
Section 5.5: Murdoch Guidelines for Content Preparation
Section 5.6: Applications & Tools
Section 5.7: Responsibility for Content

Section 6: LINK MANAGEMENT

Section 6.1: Permissible Links
Section 6.2: Link Validation & Checking
Section 6.3: Link Revision & Relocation
Section 6.4: Responsibility for Registered Links

Section 7: Glossary of MurdochNet Terminology

: SCHEDULES

Schedule 1: Forms
Schedule 2: Contracts
Schedule 3: Guidelines
Schedule 4: Regulations
Schedule 5: Disclaimers
Schedule 6: Roles & Responsibilities

Section 4 SERVER MANAGEMENT

Section 4.5 Availability of Web Servers

Section 4.5.2 Monitoring for Web Server Availability

Monitoring programs/software for Server availability shall make use of Server Registry information such as IP address, computer hostname, aliases, and Web Administrator contact details.

Web Administrators responsible for those MurdochNet Servers and Affiliated Web Servers selected for monitoring shall be alerted to Server availability problems and access problems related to services offered by those Servers. Various methods may be used to alert Web Administrators (eg. email, sms).

An out-of-hours Web Checking Procedure should be provided and used by designated staff to monitor the availability of nominated key Servers and services and report problems to appropriate staff (ie. Web Administrators).