4 Scope

4.1.1 This document addresses the requirement for an electronic Directory service to facilitate generic e-government applications in the public service. Its scope is as follows:

4.1.1.1 The S.E.E. Directory is only for the use of core public service agencies , which are members of the Secure Electronic Environment (S.E.E.) (referred to in this document as S.E.E. member agencies).

4.1.1.2 Nevertheless, the specification and architecture of the S.E.E. Directory should not be formulated in such a way as to preclude future extension, either of the Directory itself or of the concept and specification, to wider sectors. These might include the entire state sector, the wider public sector, SOEs, the private business sector or even government interaction with citizens, but any such extension will be carried out in accordance with an agreed e-government initiative.

4.1.1.3 The purpose of the S.E.E. Directory is to represent the current state of affairs at any point in time. Historical information (e.g. relating to roles that persons have held, services that are no longer provided, or agencies or business units that no longer exist) is outside the scope of the S.E.E. Directory.

4.1.1.4 The S.E.E. Directory will be for the use of S.E.E. member agencies for generic e-government applications only. This will not preclude use of alternative Directory solutions for other specific applications.

4.1.1.5 This document addresses the policy, architecture and reference schema for a S.E.E. Directory at the business level. It does not consider questions relating to detailed design, implementation or selection of technology solutions. In particular the following are out of scope:

Implementation issues such as detailed schema design

Operational considerations such as (but not confined to):

• Access and security policies

• Selection of technology suppliers

• Interfaces between the Directory and data sources.