1.1Technical Requirements
The suites of learning objects should be discoverable, interoperable, editable and reusable and capable of being delivered online and accessed using a web browser. The products are to be designed for ease of use and accessibility to the maximum number of target users.
1.1.1Hardware
The resources should be platform independent and allow for maximum portability to providers’ delivery platforms and learners’ computer systems.
The products are to be suitable for installation on a standard web server and should be operable on both Windows and Unix operating systems.
Developers should ensure that their products can be delivered successfully to client computers with the following minimum specifications:
An IBM compatible computer with a 300 MHz processor, 128 Mb of SDRAM, an 800 x 600 display, 4 GB hard disk, 1.44 Mb floppy disk, CD ROM drive, sound card and 28.8 k modem, or higher configuration;
AND
An Apple Macintosh capable of running OS 9.x, with a display resolution of 800 x 600 pixels and a minimum number of “thousands of colours”.
1.1.2Software
The products should support both Netscape (6.2 and higher) and Internet Explorer (versions 5.1.7 and higher) on both IBM compatible and Macintosh platforms.
The following software versions should be used: XHTML 1.0 Transitional, Java version 1.3, JavaScript version 1.3.
Components should be in acceptable industry standard file formats which are preferably vendor-independent and which support the browsers and platforms listed above. The following data packaging formats are preferred: GIF, JPEG, PNG, PDF, AVI, AU, VRML, SWF, MOV, MP3. Where PDF files are used, an RTF alternative should be provided.
The suites of learning objects should use style sheets to separate presentation from structure. Use CSS 1 or CSS 2.
HTML files should be limited to a download time on a 28.8k modem of no more than 30 seconds given reasonable connectivity. The use of browser plug-ins should be kept to a minimum with the selection based on maximum ease of access, minimum download times for users and the need for customisation.
Developers should use readily available development software, and use HTML code where customisation can be anticipated, with more sophisticated development software (eg Flash) reserved for components that are less likely to be changed.
Products that use resources with high bandwidth requirements must also provide a low bandwidth alternative. For example, streaming or downloadable video could have as an alternative, a series of still images with a transcript.
NOTE: These standards were required for the Series 7 round of Toolbox development in 2004/5.
For more information, please visit the Toolbox website at .