| e-Gif
Standards
People
e-Forms
Contact Information
Back to top
|
What
is e-GIF?
e-GIF is the acronym for the e-Government Interoperability Framework.
It is a set of technical policies, recommendations and standards,
and not of itself a single, well defined standard. The framework
is constantly under review and is updated to reflect the changing technical
and policy environment in which it applies. Compliance with the
e-GIF is mandatory for public sector IT projects and procurements.
This section describes some of the standards that could have an impact
on you. For more information about all standards this includes
addresses, financial transactions etc contact kate@mis-ecosse.com
Further information on e-GIF and how compliancy
affects you can be found at:
http://www.egifcompliance.org/index.html
EGif Standards – people
Contents
Title
First Name
Family Name
Surname
Last Name
Gender
Birth Date
Date of Birth
|
|
|
| Ref: |
Standard |
User Text |
Field Name |
Stored Length |
Valid look up values |
Auto Fill |
Occur |
Gov. Ref |
| 2.1 |
Name |
Name |
PersonName Title |
35 |
Mr, Mrs, Ms, Dr, Rev, Sir, Lady, Lord,
Dame
|
Yes |
Many |
BSEN 28601
|
| 2.2 |
Name (Given & Family)
|
. |
. |
. |
... |
. |
. |
. |
| |
Given Name |
First Name |
PersonGiven Name
|
35 |
. |
Yes |
Many |
BSEN 7372:1993 |
| |
Family Name |
Surname / Last Name |
PersonFamily Name
|
35 |
|
Yes |
One? |
BSEN 7372:1993
|
| |
Gender Current
|
Sex |
Gender Current
|
1 numeric |
0 = Not known [1]
1=Male 2=Female
9=Not specified [2]
|
Yes |
One |
ISO 5218 1977 (E)
|
| 2.4 |
Birth Date |
Date of Birth Entered
DD-MM-CCYY
|
PersonBirth Date |
10 |
|
. |
. |
XML Schema Part 2: Datatypes W3C Recommendation
02 May 2001
|
|
| |
[1] Gender of person
not recorded
[2] Unable to specify sex
whether male or female
[3] Date should be
- a. Values less than 10 in the day, month or year elements, should
be entered with a zero in the first position.
- b. Days must not be greater than 30 in April, June, September and
November.
- c. Days must not be greater than 28 in February except when 29 is
allowed for a leap year.
- d. Dates before 1852-02-29 are invalid as are future dates
- e. CCYY should be a valid year number.
- f. MM in Range 01-12.
- g. DD in Range 01-31.
|
eForms
Back to top
|
Everyone should use a centralised template.
Each form should have a white background, a progress bar and a grey left
hand side help. The form is them broken down into sections that is:
Initial section (one page)
Data Protection Section (one page – this is optional and depends
on the data to be entered)
Body (may have one or many pages)
The body for people will use the centralised lookup
on peoples names and addresses
End section (with one page)
The size of each form should be 600 by 400 pixels.
The content management system or web site should provide a template specifically
for forms that is uncluttered, provides the appropriate corporate information
and branding with links to the home page and forms home page.
Names and address lookup
Names and addresses for forms should be picked up from web site
registration information if at all possible. This should include
amongst other things:
Centralised title lookup so that all forms can look up the title.
|
| Contact
Information |
This consists of three pieces of data that is:-
- e-mail address
- UK telephone number
- Uniform Resource Locator (URL) - not shown for further information
send e-mail to egif
|
|
Contacts
|
| Ref: |
Standard |
User Text |
Field Name |
Stored Length |
Valid look up values |
Auto Fill |
Occur |
Gov. Ref |
| 5.1 |
e-mail address |
e-mail |
Email Address |
254 |
.
|
Yes |
. |
IETF RFC2822
|
| 5.2 |
UK telephone number
|
Telephone number User given
default of UK 44 Then asked to enter national number This is then
brought together in one field TelephoneNumber |
TelephoneNumber
TelNationalNumber
TelExtensionNumber
TelCountryCode
|
35 |
Prefixed
by country code (44) no brackets and no zeroes but theses should
... |
Yes |
. |
.
. |
Back to top
|
| |
|