Victorian Electronic Records Strategy


VERS STORY	STANDARD	ASSESSMENT	PROJECTS	DIGITAL ARCHIVE	TRAINING	TOOLKIT	PUBLICATIONS

Introduction

Standard
(Version 1)
  Specification 1
  Specification 2
  Specification 3

Standard
(Version 2)
  Specification 1
  Specification 2
  Specification 3
  Specification 4
  Specification 5
  Advice 9
  Advice 10
  Advice 11
  Advice 12
  Advice 13
  Advice 14

Home > Standard > Standard (Version 2) > Advice 12 > Native compliance

6.2 Native compliance

6.2.1 Native compliance (Version 1 systems)

The only additional requirement we are requiring of systems already compliant with Version 1 is that all VEOs must contain a digital signature. All Version 1 systems currently compliant with Specification 3 already fulfil this requirement.

We would expect that systems holding VEOs natively would also provide the ability to generate 'onion' records (see section 3.5.1).

Once this Specification is issued, no further systems will be tested for compliance with Version 2.

6.2.2 Native compliance (Version 2 systems)

The system must produce VEOs that conform to this version of the Specification and must also be capable of producing Modified VEOs.

This level of compliance is only applicable to those systems that use the VEO internally as a native format, as these systems need to be able to modify the contents of VEOs. This level of compliance has no relevance for those systems that only produce VEOs upon export.

Specifically, to achieve this level of compliance, systems must produce VEOs that contain the following:

All of the features required in section 6.1.2.
The Modified VEO element (M156).
Either a vers:forContentsSeeElement attribute or a vers:forContentsSeeOriginalDocumentAndEncoding attribute in each unmodified Document Data (M133) element.

printer friendly