Specifications of Generic data Elements and their Metadata

Allocation of Reference Numbers to the identified Generic Data Elements

Purpose

With the objective of linking the identified Generic data elements with their metadata, each one of them has been allocated a unique reference number. Further, the reference numbers are codified to ensure logical grouping of relevant generic data elements, some of which may be identified in future.

The coding scheme of Universal Postal Union (UPU) Standards S42a-5 and S42b-5 has been adopted for structuring of these reference numbers.

Rationale of Grouping of Generic Data Elements for their Codification

The Generic data elements identified for standardization can be described as:

• Data elements having distinct identity with only one level of description

• Data elements having two levels of description, where 2nd level describes the subtypes.

  These subtypes can be “Instances” or “Parts”, which also have distinct identity

Here Instance (a type representing the same data element in a different way) means representation of the same root data element at 1st level in different formats, which may or may not be mandatory to describe the root data element. For example, the generic data element “Date” can have different instances to represent date in different formats.

For example, one instance may represent the Date in format say dd/mm/yyyy, and another instance may represent the date in different format say dd-mm-yyyy

Part means physical sub division of the root data element at 1st level or its instance. The parts are mandatory to describe the root data element. For example, to describe the data element, “Date”, the parts- “day”, “month” and “year” - are mandatory.

For the purpose of standardization and interoperability, data elements of domain applications would be derived from the generic data elements, if applicable

Codification Scheme for Reference Numbers of Data Elements

A codification scheme has been adopted for grouping and referencing of data elements at two levels. The coding scheme represents an e-Governance domain, data element within the domain, instance of data element, and part of the data element, structured as domain no (xx): data element no within domain (yy)-Instance number (nn) - part number (mm).

S.No	Data Element	Instance ( a type representing the same data element in different way)	Parts	Codification scheme for its reference number
1	Data element having no parts and no instances	NA	NA	xx.yy
2	Data element having only instances, and no parts	Applicable	NA	xx.yy-nn For example: xx.yy-01 xx.yy-02
3	Data element having only parts and no instances	NA	Applicable	xx.yy-00-mm For example : xx.yy-00-01 xx.yy-00-02
4	Data element having parts as well as instances	Applicable	Applicable	xx.yy-nn-mm For example: xx.yy-01 -01 xx.yy-02-01 xx.yy-01-02 xx.yy-02-02

Here, xx : Defines the Domain number yy: Defines the Data Element number within the domain xx xx.yy-01 : Defines an Instance of Data element xx.yy xx.yy-00-01: Defines a Part of Data element xx.yy xx.yy-01-01: Defines the Instance of the Data element part xx.yy-00-01

Further “G” will be prefixed to indicate that the referenced data element is Generic, and “C” will be prefixed to indicate that the referenced data element is Customized for a specific purpose in the domain application, like “Date of Birth” derived from the generic data element “ Date”.

Illustrations of Codification Scheme

1. Data element “Date” has three parts like: Day, Month, Year Hence, reference numbers for Generic data element “date”, and its parts would be as follows:

Domain name (xx): Common for all domain applications	G00
Data Element: Date (in dd/mm/yyyy) format)	G00.01
1st Part of Date : Day	G00.01-00-01
2nd Part of Date : Month	G00.01-00-02
3rd Part of Date : Year	G01.01-00-03

2. Reference number of data element “Measurement” and its instances (different ways of a measurement) like: - Measurement of Distance in Meters/ Kilometers/ Centimeters/ Millimeters - Measurement of Area in Square Meters/ Kilometers/ Centimeters/ Millimeters/Hectares - Measurement of Volume in Cubic Meter/ Cubic Centimeter / Cubic Milliliters - Measurement of Weight in Gram / Kilogram

Hence the data element “measurement” will have difference instances, which would have reference numbers as follows:

Domain name (xx): Common for all domain applications	G00
Generic Data element: Measurement	G00.02
Measurement- Distance in Meters	G00.02-11
Measurement- Distance in Kilometers	G00.02-12
Measurement- Distance in Centimeters	G00.02-13
Measurement- Distance in Millimeters	G00.02-14
Measurement- Area in Square Meters	G00.02-21
Measurement- Area in Square Kilometers	G00.02-22
Measurement- Area in Square Centimeters	G00.02-23
Measurement- Area in Square Millimeters	G00.02-24
Measurement- Area in Hectares	G00.02-25
Measurement- Volume in Cubic Meters	G00.02-31
Measurement- Volume in Cubic Kilometers	G00.02-32
Measurement- Volume in Cubic Centimeters	G00.02-33
Measurement- Volume in Cubic Millimeters	G00.02-34
Measurement- Weight in Grams	G00.02-41
Measurement- Weight in Kilograms	G00.02.42
Measurement - Weight in Quintal	G00.02.43

List of Identified Generic Data Elements

Three types of generic data elements have been identified in the present version of MDDS standard, as listed below:

• Domain No. 00 - Generic data elements Common across all Domain applications

• Domain No. 01 - Generic data elements specific to Person Identification

• Domain No. 02 - Generic data elements specific to Land Region codification

Note:

a. With time, list of these domains would increase with standardization of generic data elements within the domains by using the above mentioned procedure of allocation of reference numbers to the identified data elements.

b. Storage format for all the Generic data elements in recognized Official language would be UTF-8, as recommended by Expert Committee on Indian Languages.

Generic Data Elements Common across all the Domain Applications

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format	Maximum Size
G00.01	Date	Calendar date having	Date	10
G00.01-00-01	Day of the Month	three sub divisions like day, month and year	(dd/mm/yyyy)
G00.01-00-02	Month
G00.01-00-03	Year
G00.02 Measurement
G00.02-11	Distance in Meters	The process of ascertaining dimensions (Distance, Area, and Volume) & quantity (Weight) in Metric system of measurement.	Decimal (p,3) Decimal (p,3)	P
G00.02-12	Distance in Kilometers	Note: For the purpose of uniformity, three decimal places have been standardized for this generic data element across the domain applications, and maximum size has been marked as “p”, which can be customized / standardized by domain applications as per their specific requirements.		P
G00.02-13	Distance in Centimeter		Decimal (p,3)	P
G00.02-14	Distance in Millimeters		Decimal (p,3)	P
G00.02-21	Area in Square Meters		Decimal (p,3)	p
G00.02-22	Area in Square Kilometers		Decimal (p,3)	p
G00.02-23	Area in Square Centimeters		Decimal (p,3)	p
G00.02-24	Area in Square Millimeters		Decimal (p,3)	p
G00.02-25	Area in Hectares		Decimal (p,3)	p
G00.02-31	Volume in Cubic Meters		Decimal (p,3)	p
G00.02-32	Volume in Cubic Kilometers		Decimal (p,3)	p
G00.02-33	Volume in Cubic Centimeters		Decimal (p,3)	p
G00.02-34	Volume in Cubic Millimeters		Decimal (p,3)	p
G00.02-41	Weight in Grams		Decimal (p,3)	p
G00.02-42	Weight in Kilograms		Decimal (p,3)	p
G00.02.43	Weight in Quintal		Decimal (p,3)	p
G00.03	Financial year	Financial year	Char	7
				nnmm- (mm+1)
G00.04	Amount	Amount in Rupees	Decimal (p,2)	p
		Note: For the purpose of uniformity, two decimal places have been standardized for this generic data element across the domain applications, and maximum size has been marked as “p”, which can be customized / standardized by domain applications as per their specific requirements.
G00.05-01	Language Code	Language codes for 22 State Recognized Official Languages and a code for English language Refer to code directory no. CD00.02	Integer	2
G00.06 Telephone Number
G00.06-00-01	International Access Code	This is the code to be used for dialing a telephone number internationally, which is sometimes referred as exit number also. For India its value is “00”, when dialing a telephone number of some other country from India. For dialing a telephone number in India from some other country, International Access Code of that country and Country code of India will have to be prefixed to Landline number /Mobile number.	Varchar1	3
G00.06-00-02	Country Code	Country code to be prefixed to the Landline number / Mobile number for dialing internationally For India its value is “91” when dialing from some other country.	Varchar	3
G00.06-00-03	Trunk Code	Trunk code to be prefixed with the Landline number / Mobile number while dialing from the place other than local area within the country; Its value is “0”	Char	1
G00.06-00-04	Area Code	Area code to be prefixed with Landline number while dialing from the place other than local exchange The size may be between 2-4 digits Note: Area code prefixed with trunk code is STD code in the terminology used by BSNL	Varchar	4
G00.06-00-05 Phone Number ( Landline number / Mobile number allocated by a service provider)
G00.06-01-05	Landline number	Landline number allocated by a service provider within an area when communication signal travels through a solid medium, either metal wire or optical fiber) The size may be between 6-8 digits in such a way that size of area code + Landline code is 10 digits	Varchar	8
G00.06-02-05	Mobile number	Mobile number allocated by a mobile network operator, when communication signal travels through radio waves	Char	10
G00.07	Calendar Year	Calendar year	Char	4
G00.08	Version no	A unique number or set of numbers assigned to a specific release of an entity	Varchar	5
G00.09	Email	Email of a Person/ Organization	Varchar	254

Generic Data Elements specific to Person Identification

Objective of Person Identification Codification

To describe / identify each and every Person uniquely at the National level to ensure interoperability of information related to individuals collected by various Government /non Government organizations. Also to ensure data integrity and smooth horizontal and vertical data exchange related to the individuals across the domain applications. Usually, following attributes are required to uniquely describe characteristics of a Person.

‐ Unique number for Identification of a Person

‐ Name of the Person including titles to be suffixed/ prefixed, in different ways

‐ Details about Father, Mother and Spouse

‐ Gender

‐ Marital Status

‐ Educational qualification & Occupation

‐ Religion

‐ Date of Birth & Place of Birth, Age

‐ Present Residential Address

‐ Permanent Residential Address

‐ Biometric data like face image, fingerprints, iris etc.

‐ Visual identification marks

‐ Specimen Signature / Thumb Impression

‐ Relationship with the head of household

‐ Telephone Number etc.

The following Generic data elements have been identified to meet the requirements of the above objective:

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format	Maximu m Size
G01.01	Unique Identification (UID)	Unique Person identification number at National level as per algorithm of UID devised by UIDAI	Integer (UIDAI has used Number, which is synonymous with Integer as per ANSI 92 data type)	12
G01.02 Name of the Person
G01.02-01	Short Name in English	Short Name in English as desired to be displayed in the documents / forms. (It is a set of character strings/ Initials each separated by a “blank space”, representing surname / given name/ middle name/….etc. The sequencing of the strings / initials has to be in the order, in which the Person desires the short name to be displayed in the documents / forms )	Varchar	30
G01.02-02	Full Name in English	Full Name in English as expanded and captured in natural order, for the purpose of searching records and data sharing by name strings (It is a set of expanded character strings, each separated by a “blank space”, representing surname / given name/ middle name/, etc. in any order as per cultural practices. In the full name, it is mandatory to include all character strings and the expanded strings of initials reflected in the short name. However, the full name can have additional character strings also, which might not have been included in the short name. The full name string should not include Appellation / title)	Varchar	99
G01.02-03	Short Name in Recognized Official Language	Short Name in Recognized Official language as desired to be displayed in the documents / forms. (It is a set of character strings/ Initials each separated by a “blank space”, representing surname / given name/ middle name/….etc. The sequencing of the strings/ initials has to be in the order, in which the Person desires the short name to be displayed in the documents / Forms )	Varchar Storage in UNICODE Standard UTF-8	30
G01.02-04	Full Name in Recognized Official Language	Full Name in Recognized Official language as expanded and captured in the natural order, for the purpose of searching records by name strings (It is a set of expanded character strings, each separated by a “blank space”, representing surname / given name/ middle name/….etc in any order as per cultural practices. In the full name, it is mandatory to include all character strings and the expanded strings of initials reflected in the short name. However, the full name can have additional character strings also, which might not have been included in the short name. The full name string should not include Appellation / title)	Varchar Storage in UNICODE Standard UTF-8	99
G01.03	Gender Identification Code	M - Male F - Female T - Transgender	Char	1
G01.04	Marital Status	Never married Currently married Widow / Widower Divorced Separated	Integer	1
G01.05-01	Appellation Code	An Appellation is a title for a Person like Mr., Dr. etc. to be prefixed with the name to indicate person’s gender, marital status, Professional status etc. Values as per code directory (CD01.04) Note: Maximum of two Appellations allowed for a person	Integer	2
G01.06-01	Suffix Code	Suffix to the name of the Person to indicate person’s positional status like IAS, IPS etc. Values as per code directory (CD01.05)	Integer	2
G01.07-01	Relation Type	H- Head of house hold N- Not head of household ( Default value “N”)	Char	1
G01.08-01	Relationship Code	Relationship of the Person, with head of the family like self, sister, brother etc. Values as per code directory (CD01.06)	Integer	2
G01.09 Face Image
G01.09-00-01	Face Image Record Header	Information about: -Format identifier -Version number -Length of record -Number of face images	Bytes	14
			24 Bit RGB
G01.09-00-03	Face Image data	Face image data acquisition Storage /archival in normal memory device Storage for verification in restricted memory device like smart card, mobile phone for the purpose of verification Note: For other specifications and best practices refer to GoI published Biometric standard for Face Image (http://egovstandards.gov.in/standardsandFramework/ biometric-standards/view)	Loss less ( Raw/PNG /Lossless JPEG2000/TI FF/ DNG) PNG JPEG 2000 with compression ratio up to 1:15
G01.10 Fingerprint Image
G01.10-00-01	Fingerprint General Record header	Information about : Format identifier Version no Record length Capture device ID Image acquisition level Number of fingers Scale units Scan resolution Scan resolution (vertical) Image resolution Image resolution(vertical) Pixel depth Image compression algorithm Rotation angle estimation flag Rotation uncertainty angle	Bytes	32
G01.10-00-02	Fingerprint Image Record Header	Information about: Length of finger data block Finger position Count of views View number Fingerprint image quality Impression type Horizontal line length Vertical line length Rotation angle	Bytes	14
G01.10-00-03	Fingerprint Image Data	Fingerprint Image Data Acquisition Storage / Archival on Normal Memory Device Storage on Restricted memory devices like smart card, mobile phone for the purpose of verification Note: For other specifications and best practices refer to GoI published Biometric standard for Fingerprint image data. o biometric-standards/view)	loss less ( Raw/PNG /Lossless JPEG2000) PNG JPEG 2000 with compression ratio up to 1:15
G01.11 Iris Image
G01.11-00-01	Iris Record Header	Information about: - Format ID “IIR” - Format version - Length of entire record - Capture device id - No. of iris biometric sub types - Record header length - Image property bit field - Horizontal orientation - Vertical orientation - Scan type Iris occlusions Boundary extraction Expected Iris diameter Image format Image width Image height Image intensity depth Transformation to polar image Device unique identifier	Bytes	45
G01.11-00-02	Iris Image Sub type Header	Information about: Biometric subtype identifier Number of iris images	Bytes	3
G01.11-00-03	Iris Image Header	Information about: Image sequence number Image quality Rotation angle Rotation uncertainty Size of image data	Bytes	11
G01.11-00-04	Iris Image Data	Iris Image data acquisition Storage / Archival on Normal memory device Note: For other specifications refer to GoI published Biometric standard for Iris Image data (http://egovstandards.gov.in/standardsandFramework/ biometric-standards/view)	Loss Less ( Raw/PNG /Lossless JPEG2000) PNG
G01.12	Specimen Signature/ Thumb impression	Scanned Image of Person’s own hand written Signature /Thumb impression - Storage / Archival format Resolution Aspect Ratio Dimension of Image	PNG Minimum 300 ppi (118 ppcm) 4:1 (W:H) 256 pixels (W) x 64 pixels (H) i.e. 1.4”/3.5cm (W) x 0.44”/ 1.06 cm (H)
G01.13-01	Education Attained Code	Code of Education attained by the Person Values as per code directory (CD01.03)	Integer	3
G01.14-01	Religion Code	Religion code of the Person Values as per code directory (CD01.01)	Integer	2
G01.15-01	Occupation Type Code	Current Occupation code of the Person. Values as per code directory (CD01.02)	Integer	2
G01.16	Date of Birth Type	Date of Birth capturing status Verified (Date verified with document evidence) Declared ( Date as declared & not verified with documentary evidence ) - Approximate (Date derived from mentioned age in years as on a particular date	Char	1
G01.17	Live Status	It represents live status of a person like: Alive Dead Default value is “A”	Char	1
G01.18	Visible Identification marks	Description of any other physical identification marks on body for visual inspection	Varchar	50

Note: The other characteristics like Date of Birth, Permanent Residential Address, and Present Residential Address would be derived from the list of Common Generic data elements & list of generic data elements for Land Region codification.

Refer Annexure- II for an illustration of Person Identification data elements derived from the Generic Data elements.

Generic Data Elements specific to Land Region Codification

1. Objective of Land Region Codification

   • To uniquely codify / describe geographically, a Land region and location of various Premises like buildings, establishments, residential /non-residential units, commercial units, institutes, land marks etc.

   • To identify Generic data elements associated with land regions, standardization of their metadata (business formats, validation checks, values, declarations, version, and ownership etc.), to meet requirements of interoperability for vertical / horizontal data exchange between various domain applications in e-Governance.

   • To identify data elements / attributes associated with Address Location.

   • To geographically represent the Address of a Premises to be taken up in (Phase - II)

2. Specification of Data Elements for Land Region Codification

Two Types of Land Region models in India

a. Based on Revenue Land Region, which is adopted by Office of Registrar General of India for the purpose of Census.

2. Based on Development Administration like Village/ Block / District Panchayat, Town Panchayat, Municipality, Corporation etc, as depicted below:

Note: Revenue Land Region model has been adopted for Land Region codification by the Expert Committee for MDDS.

Revenue village has been taken as smallest unit of Land region, for the purpose of standardization in the present version of the document.

Land Region Codified in the present version of the document

3. Codification of Address of Premises

Land Region Codified in the present version of the document

The Address of premises has mainly two components:

• House / Locality Details ( Coding not Standardized in this document)

• Land Region Details (Coding Standardized in this document)

Note: There could be a requirement of storing the address of a premises bilingually ( English and Recognized Official language of the State ). In such cases, usually, the data is captured in local language, and stored in English also. For this purpose, either the data will have to be captured in both the languages or there should be a mechanism to transliterate / translate the data from local language to English or vice versa, accurately without losing its meaning. This issue is NOT addressed in this document.

4. Segmented Approach for Address of Premises would be as follows:

   • Segment 1 – Premises Identifier

   • Segment 2 - Sub-locality Identifier

   • Segment 3 - Land Region Identifier (Revenue Village / Town / District / State)

   • Segment 4 - Additional data elements / attributes for internal storage only, which may be required for different purposes and interoperability with other domain applications.

The above has been diagrammatically explained below along with recommended printing of address lines:

Generic Data Elements to describe a Land Region

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format	Maximum Size
G02.01	Land Region Code (LRC)	A unique code allocated by Office of RGI at National level, for administrative units like State/ District / Sub District /Rural Region (Revenue Village) / Urban Region (Town) / any other Land identifier, to be used by domain applications for the purpose of interoperability among e- Governance applications, while exchanging Land region data	Integer	State - 2 District - 3 Sub-District - 5 Village - 6 Town – 6
G02.02 Name of Land Region
G02.02-01	Name of a Land region in English	Name of: Country / State / District / Sub District / Rural Land region (Revenue Village) / Urban Land region (Town) / any other Land identifier preferably in CAPITAL Letters	Varchar	50
G02.02-02	Name of Land region in Recognized Official language	Name of: Country / State / District / Sub District / Rural Land region ( Revenue Village) / Urban Land region (Town) / any other Land identifier	Varchar Storage in UNICODE Standard UTF-8	50
G02.05	Geocode	Geocode within a Land region (to be taken up in Phase-II)
G00.02-22	Area in Sq.Km	Measurement of Land Region area in Sq.Km	Decimal (15,3)	15

Note: Land region is a domain hence the common generic data element for measurement in Sq.Km (G00.02-22) has been adopted and value of ‘p’ has been standardized for this domain as “15”.

Data Elements to describe Premises

The following structure is applicable for Address of Premises representing a Commercial unit or a Residence in an Urban Land Region (Town) as well as Rural Land Region (Revenue Village).

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format	Maximum Size
G02.03 Address of a Premises
G02.03-00 Premises Identifier
G02.03-00-01	Address Type	Address type Residential Commercial	Varchar	15
G02.03-00-02	Premises Identifier	-House Number. / Door Number / House Identifier /Flat Number Building Number. / Plot Number Building Name / Building Identifier Stairwell / Lift Number	Varchar	60
G02.03-00-03 Sub Locality / Locality Identifier
G02.03-01-03	Sub Locality-1	-Block Name/Number or any other qualifier -Street Number /Name/ Mohalla/ Sector Number /any other qualifier	Varchar	60
G02.03-02-03	Sub Locality -2	Major / Minor Land mark In Urban Land region (Town) or Rural Land region (Revenue village) for easy location of Premises	Varchar	60
G02.03-03-03	Locality	Area Number/ Area Name / Suburb / Sub district in case of Village/ any other qualifier	Varchar	60

G02.04 Generic data elements for Postal Services
Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format	Maximum Size
G02.04-01	PIN	Postal Index Number	Integer	6
G02.04-02	POST	Post Office Service Type: PO box / GPO box/Free Post / Post Bag / e-Post service	Varchar	20
G02.04-03	POSNO	Post Office Service Number: PO box / GPO box/Free Post / Post Bag / e-Post number	Integer	6
G02.04-04	DPON	Delivery Post Office Name	Varchar	30
G02.04-05	BTNO	Beat Number	Integer	2
G02.05 Generic Data Elements for Geo referencing (to be taken up in Phase- II)
G02.05-00-01	Longitude
G02.05-00-02	Latitude
G02.05-00-03	Altitude

Refer Annexure- III for an illustration of recommended data elements of Residential Address along with examples of printing sample addresses.

Code Directories

In case of certain generic data elements, their values need to be controlled and defined in advance for using them uniformly across the domain applications. Such predefined values would be stored in prescribed structure, referred as “Code Directories” in this document.

The identified code directories and their structures are listed below:

Code Directories specific to Common Generic data elements

Ref. No. of Code Directory	Name of Code Directory	Ownership (Owner of Code Directory having update rights)	Ref number for Code Directories values
CD00.01	Measurement conversion table	Department of Land Records	Annexure IV of the document
CD00.02	State Recognized Language Codes Directory	Department of Official Language, Ministry of Home Affairs	Annexure IV of the document

State Recognized Official Language Code Directory (CD00.02)

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format	Maximum Size
G00.05-01	Language code	Unique code for Language	Integer	2
G00.05-02	Name of State language	Name of State Recognized Official Language	Varchar	20
G00.05-03	ISO Language code	Language code as per ISO 639-3	Char	3

Code Directories specific to Person Identification

Ref. No. of Code Directory	Name of Code Directory	Proposed Owner of the Code Directory	Ref number for Code Directories values
CD01.01	Religion	Anthropological Survey of India / Office of RGI	Annexure IV of the document
CD01.02	Occupation	Ministry of Labour	Annexure IV of the document
CD01.03	Education	Department of Higher Education	Annexure IV of the document
CD01.04	Appellation	Ministry of Home Affairs	Annexure IV of the document
CD01.05	Suffix	Ministry of Home Affairs	Annexure IV of the document
CD01.06	Relationship	Anthropological Survey of India	Annexure IV of the document

Code Directory for Religion (CD01.01)

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format	Maximum Size
G01.14-01	Religion Code	Unique code for Religion	Integer	2
G01.14-02	Name of Religion in English	Name of the Religion like: Hinduism	Varchar	15

Note: Code directory should include religions in alphabetical order

Code Directory for Occupation Type (CD01.02)

Generic data element Ref no. for its Metadata	Name of Data element	Description of Data element	Data format	Maximum Size
G01.15-01	Occupation Type Code	Unique code for Occupation	Integer	2
G01.15-02	Name of Occupation type in English	Name of the Occupation like: Corporate Manager, Teaching Professional	Varchar	50

Code Directory for Education Attained (CD01.03)

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format	Maximum Size
G01.13-01	Education Attained Code	Unique code for Education	Integer	3
G01.13-02	Name of Education Attained in English	Name of the Education like: Engineering and Technology, Medicine	Varchar	30

Code Directory for Appellation (CD01.04)

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format	Maximum Size
G01.05-01	Appellation Code	Unique code for Appellation	Integer	2
G01.05-02	Name of Appellation in English	Appellation to be prefixed with name of the Person like: Mr., Mrs.	Varchar	15

Note: It is recommended that Appellation codes equivalent in all Recognized Official languages should be tabulated and standardized.

Code Directory for Suffix attached with name (CD01.05)

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format	Maximum Size
G01.06-01	Suffix Code	Unique code for Suffix	Integer	2
G01.06-02	Name of Suffix in English	Suffix to be used with Person’s Name to indicate positional title like: IAS, IFS, etc.	Varchar	15

Code Directory of Relationship (CD01.06)

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format	Maximum Size
G01.08-01	Relationship Code	Unique code for Relationship	Integer	2
G01.08-02	Name of Relationship in English	Name of Blood Relationship with the Head of family like Sister, Husband, Wife, Self , Spouse etc.	Varchar	20

Code Directories specific to Land Region Codification

Ref. No. of Code Directory	Name of Code Directory	Ownership (Owner of Code directory having update rights on the basis of notifications issued by Competent Authorities)	External reference for values of Code Directories
CD02.01	Country	ISO 3166-1 alpha-3 Standard	http://en.wikipedia.org/wiki/ISO_3 166-1_alpha-3
CD02.02	State	Office of RGI	http://www.censusindia.gov.in/
CD02.03	District	Office of RGI	http://www.censusindia.gov.in/
CD02.04	Sub-District	Office of RGI	http://www.censusindia.gov.in/
CD02.05	Rural Land Region (Revenue Village)	Office of RGI	http://www.censusindia.gov.in/
CD02.06	Urban Land region (Town)	Office of RGI	http://www.censusindia.gov.in/
CD02.07	Police Station	NCRB (National Crime Record Bureau )
CD02.08	Geo-code	To be addressed in Phase- II

Note:

1. Over the years Office of Census Commissioner, India while conducting the decadal census, has developed code directories for a number of variables and standardized definitions etc. These are available on their web site also. Moreover, a number of Departments / Organizations have become conversant with these parameters. The committee recommends that this practice can continue till the identified code directories owners review the values in the code directories and decide to revise them.

2. Responsibility of maintenance of Centralized Repository Code Directory including allocation of new Land Region codes would be with Office of Registrar General of India (ORGI) on the basis of notification of changes for the same issued by Competent State Authorities from time to time.

3. Refer to Annexure IV for values in the Code Directories, as on date. The Standards website may be visited on regular basis to get latest updations.

Code Directory of Country (CD02.01)

Ref no. of Generic data element for its	Name of Data element	Description of Data element	Data format	Maximum Size
Metadata
G02.01	Country Short Name Code (CSNC) (primary key)	Unique Country Short Name Code at International level	Char	3
G02.02-01	Country Name in English (CNE)	Name of the Country in English ( Capital letters)	Varchar	50
G00.02-22	CAreaSKM	Area of the Country in Sq.km Since various states conventionally maintain area of land regions in different units, the Measurement conversion directory( CD.00.01) may be used for this purpose.	Decimal(15,3)	15
G02.05	GC	Geocode of the country (to be taken up in Phase-II)
G00.08	VNC	Defines Version number of the data record to be used for tracing history of changes in the values of the record related to the country data	Char	5
G00.01	DOUC	Date of last Update of the record	Date (dd/mm/yyyy)	10

Examples:

Country Name	CSNC	CAreaSKM in Sq.km	Geo code (GC)	Version Number for country (VNC )	Date of Last update of record (DOUC)
AFGHANISTAN	AFG	652090	In Phase-II	1
SOUTH GEORGIA AND THE SOUTH SANDWICH ISLANDS	SGS	3903	—do—	1
INDIA	IND	3287590	—-do—-	1

Code Directory of State (CD02.02)

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data Element	Data format	Maximu m Size
G02.01	State LRC (SLRC)	A unique land region code allocated by Office of RGI at National level, for administrative unit, State for the purpose of interoperability among e- Governance applications, while exchanging the Land region related data	Integer	2
G02.02-01	SNE	State Name in English	Varchar	50
G02.02-02	SNOL	Name of State in Recognized Official Language	Varchar Storage in UNICODE Standard UTF-8	50
G00.05-01	SOLC	State Recognized Official Language Code	Integer	2
	NSD	Nomenclature of Sub-District in the State (Sub district, Tahsil, Taluk, Revenue circle etc.) (Refer CD02.02 in Annexure IV for complete list)	Varchar Decimal(15,3)	15
G00.02-22	SAreaSKM	Area of the State in Sq.km		15
G02.05	GS	Geocode of the state (to be taken up in Phase-II)
G00.08	VNS	Defines Version number of the data record to be used for tracing history of changes in the values of the record related to the State data	Char	5
G00.01	DOUS	Date of last Update of the record	Date (dd/mm/yyyy)	10

Example:

State Land Region Code (SLRC)	State Name In English	SNL	SOLC	NSD	SAreaSKM In Sq.km	GS	VNS	DOUS
1	JAMMU AND KASHMIR		22	Tahsil	222236	In Phase-II	1
2	HIMACHAL PRADESH		6	Tahsil	55673	—-do—-	1

Code Directory of District (CD02.03)

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format	Maximum Size
G02.01	District LRC (DLRC)	A unique code allocated by Office of RGI at National level, for administrative unit, District for the purpose of interoperability among e-Governance applications, while exchanging the Land region related data	Integer	3
G02.01	SLRC	Parent State Land Region code for District	Integer	2
G02.02-01	DNE	District Name in English	Varchar	50
G02.02-02	DNL	District Name in Recognized Official Language of the State	Varchar Storage in UNICODE Standard UTF- 8	50
G00.02-22	DAreaSKM	Area of the District in Sq.km	Decimal (15,3)	15
G02.05	GD	Geocode of the District to be taken up in Phase-II)
G00.08	VND	Defines Version number of the data record to be used for tracing history of changes in the values of the record related to the District data	Char	5
G00.01	DOUD	Date of last Update for record	Date (dd/mm/yyyy)	10

Example:

DLRC	SLRC	DNL	DNE	DAreaSK M in Sq.km	GD	VND	DOUD
1	1		KUPWARA (District)		–do—	1.0
23	2		CHAMBA		–do–	1.0

Code Directory of Sub-District (CD02.04)

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format	Maximum Size
G02.01	Sub-District LRC (SDLRC)	A unique code allocated by Office of RGI at National level, for administrative unit, Sub-District for the purpose of interoperability among e-Governance applications, while exchanging the Land region related data	Integer	5
G02.01	SLRC	Parent State Land Region code for Sub District	Integer	2
G02.01	DLRC	Parent District Land Region code	Integer	3
G02.02-01	SDNE	Sub- District name in English	Varchar	50
G02.02-02	SDNL	Sub- District name in Recognized Official Language of the State	Varchar Storage in UNICODE Standard UTF-8	50
	NSDT	Nomenclature of Sub-District used in the state: - Tahsil Taluk C.D. Blocks Sub Division Circle R.D Blocks Mandal Police Station (For the purpose of standardization, the above nomenclatures used by various states would mean Sub- District only)	Varchar	15
G00.02-22	SDAreaSKM	Area of the Sub District in Sq.km	Decimal (15,3)	15
G02.05	GCSDC	Geocode of the Sub District (to be taken up in Phase-II)
G00.08	VNSD	Defines Version number of the data record to be used for tracing history of changes in the values of the record related to the sub district data	Char	5
G00.01	DOUSD	Date of last Update for record	Date (dd/mm/yyyy)	10

Example: of a Sub District

SDLRC	SLRC		(SDNE)	SDNL	NSDT	SDArea SKM ( In Sq.km)	GCSDC	VNSD	DOU SD
1	1	1	KUPWARA		Tahsil		—-do—	1.0
83	2	23	PANGI		Tahsil		—-do—

Here “KUPWARA” is a Sub District of parent State JAMMU & KASHMIR and District KUPAWARA

“PANGI” is a Sub District of parent State HIMACHAL PRADESH and District CHAMBA

Code Directory of Rural Land Region (Revenue Village (CD02.05))

In a sub-district, there can be two types of land regions like Urban Land Region and Rural land Region.

A land region like a Town / Municipal Corporation / Municipality/ Cantonment board etc., notified through Nagar Palika Act is categorized as Urban land region, and rest is categorized as Rural Land Region.

Following is the structure of code directory for Rural Land Region (Revenue Village)

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format	Maximum Size
G02.01	Village LRC (VLRC)	A unique code allocated by Office of RGI at National level, for administrative unit, Revenue Village for the purpose of interoperability among e-Governance applications, while exchanging the Land region related data	Integer	6
G02.01	SLRC	Parent State Land Region code	Integer	2
G02.01	DLRC	Parent District Land Region code	Integer	3
G02.01	SDLRC	Parent Sub District Land Region code	Integer	5
G02.02-01	VNE	Rural Land region ( Revenue Village ) name in English	Varchar	50
G02.02-02	VNL	Rural Land Region (Revenue Village) Name in Recognized Official Language of the State	Varchar Storage in UNICODE Standard UTF-8	50
	VStatus	Current Status of Rural Land U- Un-inhabitant I- Inhabitant T- Notified as town Note : Reserve Forest Area (RFA) and Census Town (CT) also included with indication of RFA and CT suffixed with the name of the rural land region within brackets	Char	1
G02.01	VTLRC	In case of Vstatus = “T”, Land region code of the town in which revenue village got associated	Integer	6
G00.02-22	VAreaSKM	Area of the Rural Land region (Revenue village) in Sq.km	Decimal (15,3)	15
G02.05	GV	Geocode of the Rural Land Region

Note: In case, a Revenue Village becomes part of Urban Land Region, its data will not be deleted from the Revenue Village code directory, but its status would change to” notified as part of Town”

VLRC	SLR C	DLRC	SDLRC	VNE	VNL	V Status	VAreaS KM (in Sq.km)	GV	VNV	DOUV
1	1	1	1	BORE				-do-
2	1	1	1	KERAN				-do-
3	1	1	1	BUGNA				-do-
6552	2	23	83	LUJ (RFA)				-do-
6553	2	23	83	LUJ				-do-
6554	2	23	83	DHARWA S				-do-

Here “BORE”, “KERAN”, “BUGNA” is a Village of parent State JAMMU & KASHMIR, parent District KUPWARA and parent Sub District KUPWARA

“LUJ (RFA)”, “LUJ”, “DHARWAS” is a Village of parent State HIMACHAL PRADESH, parent District CHAMBA and parent Sub District PANGI

Code Directory of Urban Land Region (Town) (CD02.05)

A land region like a Town / Municipal Corporation / Municipality/ Cantonment board etc., notified through Nagar Palika Act is categorized as Urban Land Region

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format	Maximum Size
G02.01	Town LRC (TLRC)	A unique code allocated by Office of RGI at National level, for Urban Land Region (Town) for the purpose of interoperability among e- Governance applications, while exchanging the Land region related data Here, Town can be a Town Panchayat/Census town/Municipality, Corporation or a Notified Area	Integer	6
G02.01	SLRC	Parent State Land Region code	Integer	2
G02.01	DLRC	Parent District Land Region code (For Addressing, in the case of Town spanning across two or more Districts, it will be indicated by value 0, and detailing will be given through linkage with another code directory CD02.05-01)	Integer	3
G02.01	SDLRC	Parent Sub-District Land Region code (For Addressing, in the case of Town spanning across two or more Sub Districts, it will be indicated by value 0, and detailing will be given through linkage with another code directory CD02.05-01)	Integer	5
G02.02-01	TNE	Urban Land Region (Town) Name in English	Varchar	50
G02.02-02	TNL	Urban Land Region (Town) Name in Recognized Official Language of the State	Varchar Storage in UNICODE Standard UTF-8	50
	Town Status	Status of Urban Land Region(Town) C.B. Cantonment board/Cantonment C.M.C City Municipal Council E.O Estate Office G.P Gram Panchayat I.N.A Industrial Notified Area I.T.S. Industrial Township M Municipality M.B. Municipal Board M.C Municipal Committee M.Cl Municipal Council M.Corp. Municipal Corporation/Corporation N.A. Notified Area N.A.C Notified Area Committee/Notified Area Council N.P Nagar Panchayat N.T Notified Town N.T.A Notified Town Area S.T.C Small Town Committee T.C. Town Committee/Town Area Committee T.M.C Town Municipal Council T.P Town Panchayat T.S. Township	Varchar	6
G00.02-22	TAreaSKM	Area of the Urban Land region (Town)in Sq.km	Decimal (15,3)	15
G02.05	GT	Geocode of the Town (to be taken up in Phase-II)
G00.08	VNT	Defines Version no. of record	Char	5
G00.01	DOUT	Date of last Update for record	Date (dd/mm/yyyy)	10

Example:

TLRC	SLRC	DLRC	SDLRC	TNE	TNL	Town Status	TAreaSKM ( in Sq. km)	GRV	DOUT
800001	1	1	1	KUPWARA (MC)				-do-
800002	1	1	2	HANDWARA (MC)				-do-
800010	1	4	13	KARGIL (MC)				-do-
800087	2	23	87	DALHOUSIE (CB)		CB
800088	2	23	87	DALHOUSIE (MCI)		MCI
800089	2	23	88	BAKLOH (CB)		CB

Here “KUPWARA (MC)”, “HANDWARA (MC)”, are Towns of parent State JAMMU & KASHMIR, parent District KUPWARA and Sub District KUPWARA

“DALHOUSIE (CB)”, and “DALHOUSIE (M CI)” are Towns of parent State HIMACHAL PRADESH, parent District CHAMBA and Sub District DALHOUSIE

Code Directory of Urban Land Region (Town) cutting boundaries across District / Sub District (CD02.05-01)

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format	Maximum Size
G02.01	Town LRC (TLRC)	A unique code allocated by Office of RGI at National level, for Urban Land Region (Town) for the purpose of interoperability among e- Governance applications, while exchanging the Land region related data Here, Town can be a Town Panchayat/Census town/Municipality, Corporation or a Notified Area	Integer	6
G02.01	DLRC	District Land Region code for Town cutting boundaries across Districts	Integer	3
G02.01	SDLRC	Sub District Land Region code for Town cutting boundaries across Sub Districts	Integer	5

Code Directory of Police Station (CD02.07)

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format	Maximum Size
G02.01	PSC (primary key)	Code of Police Station	Integer	6
G02.01	State LRC (SLRC)	State land region code where Police Station is located.	Integer	2
G02.01	District LRC (DLRC)	District code where Police Station is located	Integer	3
G02.02-01	PSNE	Police Station name in English	Varchar	50
G02.02-02	PSNL	Police Station name in Recognized Official Language of the State	Varchar Storage in UNICODE Standard UTF-8	50
G02.05	GPS	Geocode of the Police Station (to be taken up in Phase-II)
G00.08	CVPS	Defines Version no. associated with Police Station location Code	Char	5
G00.01	DOUPS	Date of Last Update for Police Station	Date (dd/mm/yyyy)	10

Example:

PSC ( Police Station code)	SLRC / State Name	DLRC / District Name	PSNE	PSNL	GPS
	08 / Delhi				In Phase-II
		08162 / Central District
0816208			Chandni Mahal
0816210			Darya Ganj
0816240			Pahar Ganj

Note: The Police Station Code Directory values, shown in the example, are taken as per the present data given by NCRB (National Crime Record Bureau), which does not match with Land Region Codes allocated by ORGI. However, these need to be changed, once the Standard is notified and enforced.

Geo-code Referencing Directory (to be taken up in Phase-II) (CD02.08)

Ref no. of Generic data element for its Metadata	Name of Data element	Description of Data element	Data format at Interface level	Finalizati on Status
G02.05-01	Geocode	Land Region Code (Country/ State/District/ Sub District/ Town / Village)
G02.05-01-01	Longitude		As per UTM coordinates
G02.05-01-02	Latitude		As per UTM coordinates
G02.05-01-03	Altitude	It defines Mean sea level

Metadata of Generic Data Elements

Template for Meta Data of Data Elements:

Based on eGIF (e-Governance Interoperability Framework) Standard of UK

#	Item	Description
1	Name	Name / Number of the Generic or Custom Data Element
2	Description	A simple and ambiguous definition of Generic or Custom Data Element.
3	Type	Generic or Custom Generic : commonly used data element across different e-Governance applications. Custom: Used in a particular application only
4	Is Part of
5	Parts if any
6	Data Format	Varchar/Character/Decimal(for real/ floating number) / Integer(Whole number)/Date etc Recommended style of printing / display, if required so
7	Max Size	Maximum Size of the data element
8	Validations	Generic Validations for Generic Data and Specific Validations for Custom Data to be applied for acceptance of data.
9	Values	List of Acceptable Values
10	Default Value	For any list of values, the default value to be used unless otherwise stated.
11	Owner	Name(s) of the departments who owns the Data element/ Code Directory and has the rights for updating.
12	Based on	Reference to document / standard / agency on the basis of which the data element is standardized by the Expert committee for MDDS
13	Version	The version number of Data element
14	Status	Current status of Standard (Draft or Accepted)
15	Date Agreed	The date on which this version was accepted as Data Standard for Government.
16	Verification	Steps taken to establish the correctness of Generic or Custom Data Elements. Such steps taken for different level of verifications by departments will be detailed here.
17	Comments	Additional Notes, if any
18	Date of Publishing	The date on which Standard is Published or HTML or PDF version will be created

Metadata of Common Generic Data Elements

Name of Data Element : Date (G00.01)
Description of Data Element	Date as per Indian Date Conventions
Data Element Type (Generic / Custom)	Generic
Is Part of
Parts, if any	Day -> G00.01-00-01 Month -> G00.01-00-02 Year -> G00.01-00-03
Data Format	Date (dd/mm/yyyy)
Max Size	10 (dd/mm/yyyy)
Validation	yyyy should be a valid year number mm in Range 01-12 dd not to be greater than 30 in April, June, Sept & Nov dd not to be greater than 31 in of Jan, Mar, May, July, Aug, Oct, Dec dd not to be greater than 28 in Feb, except leap year, when value 29 is allowed
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	As decided by the Expert Committee for MDDS
Version	1
status	Accepted
Date agreed
Verification
Comments	“/” to be used as delimiter for representation of Date
Date of Publication	16/11/11

Example: - 08/12/2008

08 -represents day

12 -represents month 2008-represents year

Name of Data Element : Measurement (G00.02)
Description of Data Element	The process of ascertaining dimensions ( Distance, area, volume) & quantity ( weight) in Metric system of measurement. For the purpose of uniformity, two decimal places have been standardized for this generic data element across the domain applications, and maximum size has been “p” marked: Measurement of Distance in: Meters (Meters) G00.02-11 Kilometers (km) G00.02-12 Centimeter (cm) G00.02-13 Millimeters (mm) G00.02-14 Measurement of Area in: Square Meters (Sq.meter) G00.02-21 Square Kilometers(Sq.km) G00.02-22 Square Centimeters(Sq.cm) G00.02-23 Square Millimeters (Sq.mm) G00.02-24 Hectares G00.02-25 Measurement of Volume in: Cubic Meters (Cu.meter) G00.02-31 Cubic Kilometers (Cu.km) G00.02-32 Cubic Centimeters(Cu.cm) G00.02-33 Cubic Millimeters (Cu.mm) G00.02-34 Measurement of Weight in: Grams(Grams) G00.02-41 Kilograms (kg) G00.02-42 Note: basic unit of measurement is Meter / Gram. More instances can be added for storage of measurement in other units, in future.
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Decimal(p,3)
Max Size	Value of “p”, the maximum size of the data element, would be decided by a domain depending upon the specific requirements of the applications in that domain.
Validation
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	SI units, ISO 1000:1992, and as decided by the Expert Committee for MDDS
Version	1.1
Status	Accepted
Date agreed
Verification
Comments	Specific to Land Region Codification: Since various states conventionally maintain area of land regions in different units, the Measurement conversion directory( CD.00.01) may be used for this purpose
Date of Publication	16/11/2011

Example: Area of Tahsil in Square Kilometers is 55673.000

Table of domain wise standardization of value of “p” for Generic Data Element: Measurement of Area in Square Kilometers (G00.02-22)

Domain Name	Value of p	Data Format
Land Region	15	Decimal(15,3)

Note: The above table will go on expanding based on standardization of values of “p” for different domains

Name of Data Element : Financial year (G00.03)
Description of Data Element	Financial Year
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Char ( nnmm-(mm+1))
Max Size	7
Validation	nnmm should be a valid Year number
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	As decided by the Expert Committee for MDDS
Version	1.0
Status	Accepted
Date agreed
Verification
Comments
Date of Publication	16/11/2011

Example: - Financial year: 2008-09

Name of Data Element : Amount (G00.04)
Description of Data Element	Amount - Amount must be stored in Rupees. Amount must be stored in the database as Numeric value along with two digits for paise The amount should be printed in Indian Standard For printing purpose there is a function to convert Numeric value into the Character (Crore, lakh, Thousand, Hundred) & (paisa).
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Decimal(p,2)
Max Size	“p” , the maximum size of the data element would depend upon the specific requirements of applications in a domain, hence kept variant. Domain applications can customize / standardize the maximum size accordingly. However, for the purpose of uniformity, two decimal places have been standardized for this generic data element across the domain applications, and maximum size has been marked as “p”.
Validation	It must be a positive number (Amount value >=0)
Values
Default value	0
Owner	Government of India, Department of Information Technology
Based on	As decided by the Expert Committee for MDDS
Version	1.1
Status	Accepted
Date agreed
Verification
Comments	The number before the decimal point in RUPEES and the Number after the decimal point in PAISE. For display / printing of amount in Rupees: The amount along with two decimals for paise should be prefixed with (the new symbol for Rupee) without a gap between Rupee symbol and the amount. “,” to be used to segregate hundreds, thousands, lacs, crores etc.
Date of Publication	16/11/11

Table of domain wise standardization of value of “p” for Generic Data Element: Amount (G00.04)

Domain Name	Value of p	Data Format
Banking	16	Decimal(16.2)

Note: The above table will go on expanding based on standardization of values of “p” for different domains

Example for printing amount:

2,34,55,255.50

Two Crore, Thirty Four Lakh, Fifty Five Thousand, Two Hundred Fifty Five Rupees & Fifty Paisa only

One Hundred Rupees = 100.00 One Thousand Rupees = 1,000.00 One Lakh Rupees = 100,000.00 One Crore Rupees = 10,000,000.00 etc.

Name of Data Element : Language code (G00.05-01)
Description of Data Element	Defines State Recognized Official Language code & A code for English Language / other languages.
Data Element Type (Generic/Custom)	Generic
Is part of any
Parts if any
Data Format	Integer
Max Size	2
Validations
Values	Values taken from Language Code Directory (CD00.02)
Default Value	99
Owner	Department of Official Language, Ministry of Home Affairs
Based on	Indian Census 2001, ORGI for language code ISO 369-3 for alphabetical Language Code.
Version	1.1
Status	Accepted
Date Agreed
Verification
Comments
Date of Publishing	16/11/2011

Example: language code 06 for Hindi as per ORGI Language code as per ISO 639-3 hin for Hindi

Name of Data Element : Telephone No (G00.06)
Description of Data Element	Landline or Mobile number allotted to a subscriber by a service provider along with various prefixes for trunk dialing / International dialing Here, Landline number means a phone number allocated by a service provider for transmission of communication signals through a hard-wired ( metal cable / optical fiber) or wireless system. Mobile number means a phone number allocated to a subscriber by a mobile network operator for transmission of communication signals through radio waves. In addition to telephony, modern mobile phones also support a wide variety of other services such as text messaging, MMS, e-mail, Internet access, short-range wireless communications (infrared, Bluetooth), business applications, gaming and photography. Mobile phones that offer these more general computing capabilities are referred to as smart phones also.
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any	International Access Code G00.06-00-01 Country code G00.06-00-02 Trunk Prefix G00.06-00-03 Area Code G00.06-00-04 Phone Number(With two instances for Landline number & Mobile Number) Landline number G00.06-01-05 Mobile number G00.06-02-05
Data Format	Varchar
Max Size	16 including the codes used for prefixing of parts
Validation	International Access Code Varchar(3) with value “00” for dialing a telephone number outside India Country Code Varchar(3) with value “91” for India -Trunk Prefix: Char(1) with value “0” Area Code(2-4) Varchar(4) Landline number(6-8) Varchar(8) Note: Total no. of character for area code & Subscriber number should be 10 digits For Landline number: Local calls : Landline number itself Calls within India – 11 digits (Trunk prefix - Area code - Landline number ) For calls to India from outside Country – Maximum 15 digits (International Access Code of the concerned country - Country code of India - Area Code - Landline number) For calls from India to an outside country (International Access Code of India ( value “00” + Country code of the specific country - Area Code & particular Landline number) For Mobile number Local Calls : 10 digits Calls within India – 11 digits (Trunk prefix - Mobile no ) For calls to India from outside Country - Maximum 15 digits (International Access Code of the concerned country - Country code of India - Mobile no ) For calls from India to outside country (International Access Code of India ( value “00”) - Country code of the specific country - Area Code & particular Mobile number )
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	ITU-TE.164 for Country code & Department of Telecommunications
Version	1.1
Status	Accepted
Date agreed
Verification
Comments	The international Access Code ( referred as exit code also), of India is 00. For calls to India from abroad ( ISD calls),the appropriate International access code should be dialed, followed by 91, followed by the area code , followed by the phone number. STD code in BSNL terminology means Trunk prefix value and area code
Date of Publication	16/11/11

Examples:

A. For Landline

A1. When a Person dials within INDIA

For example: Local call – Landline number: 2641939

A2. Call from anywhere in India Trunk prefix - (area code - Landline number)

For example: 0 - 145 - 2641939 i.e. 01452641939

(Here 0145 is STD number as per BSNL terminology)

A3. When a person dials to India from some other Country

International Access Code of that country - Country code of India - (Area Code + Landline number)

For example: Call from USA to a land line in India 011 - 91 - 11 - 24356987 i.e. 011911124356987

A4. When a person calls a landline of a country outside India :

International Access Code of India - country code of specific country - particular Landline number

For example: Call from India to a landline in USA 00 - 1 - 615216776 i.e 001615216776

B. For Mobiles:

Local Calls – Mobile number 9213546987

From any where in India = Trunk-prefix - Mobile no For example: 0 - 9213546987

When a person dials to India from some other country

International Access Code of that country - Country code of India - Mobile Number

For example: Call from USA to a mobile in India

011 – 91- Mobile Number

i.e. 011919896875214

When a person calls a mobile number of a country outside India:

International Access Code of India - country code of specific country - particular mobile number

For example: Call from India to a landline in USA

00 - 1- 617516781

**i.e. 001617516781*8

Refer http://www.howtocallabroad.com/codes.html for list of International Access Code( also called Exit Code) and Country Codes

Name of Data Element : Calendar year (G00.07)
Description of Data Element	Calendar Year
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Char
Max Size	4 (yyyy)
Validation	yyyy should be a valid Year number.
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	As decided by the Expert Committee for MDDS
Version	1.0
Status	Accepted
Date agreed
Verification
Comments
Date of Publication	16/11/2011

Example: - 2008 calendar year

Name of Data Element : Version no (G00.08)
Description of Data Element	A unique number or set of numbers assigned to a specific release of an entity Here entity can be a document, software, data element, Hardware device etc.
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Char
Max Size	5
Validation
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	As decided by the Expert Committee for MDDS
Version	1.0
Status	Accepted
Date agreed
Verification
Comments
Date of Publication	16/11/2011

Example: PAO Software Version 1.5

Data element “Date “Version 1.0

Name of Data Element : Email (G00.09)
Description of Data Element	Defines Email address / User Id of a Person / Organization with structure username@domainname
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Varchar
Max Size	254
Validation	The string before the symbol “@” would be user name and string after the symbol “@” would be domain name of the email server
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	IETF RFC2822 and as decided by the Expert Committee for MDDS
Version	1.0
Status	Accepted
Date agreed
Verification
Comments	In an organization, it is recommended that, there should be an uniform way of allocation of email IDs for employees. One of the recommended ways is: 1st given name.surname( running s.no, for 2nd repeat onwards)@domainname
Date of Publication	16/11/2011

Example: sumit.ghani@nic.in

Metadata of Generic Data Elements for Person Identification

Name of Data Element : Unique Identification Number (G01.01)
Description of Data Element	Unique Identification (UID) Number to be allocated by UIDAI to every Indian Citizen, which would enable interoperability of data related to a Person in various Domain applications
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Integer (UIDAI has used Number, which is synonymous with Integer as per ANSI 92 data type)
Max Size	12
Validation
Values
Default value
Owner	Unique Identification Authority of INDIA (UIDAI),
Based on	UID structure decided by UIDAI , UID DDSVP Committee, report Version 1.0, Dec 09, 2009
Version	1.1
Status	Accepted
Date agreed
Verification
Comments	Print and display format should be NNNN-NNNN-NNNN
Date of Publication	16/11/2011

Note: Using data format as” Integer” as per MDDS convention instead of Number defined by UIDAI

Name of Data Element : Name of the Person (G01.02)
Description of Data Element	Name of a Person can be represented in different ways like: Short name in English G01.02-01 Full name in English G01.02-02 Short name in Recognized Official Language G01.02-03 Full name in Recognized Official Language G01.02-04 These are instances of Name of the Person, which can be represented in different ways / formats
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Refer to the formats of instances corresponding to this Generic data element
Max Size
Validation
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	As decided by the Expert Committee for MDDS
Version	1.0
Status	Accepted
Date agreed
Verification
Comments	Name of the person should not include Appellation, which is a separate data element,and would be prefixed with name of the person while displaying / printing
Date of Publication	16/11/11

Name of Data Element : Short Name In English (G01.02-01)
Description of Data Element	Short Name in English as desired to be displayed in the documents / forms. (It is a set of character strings / Initials each separated by a “blank space”, representing surname / given name/ middle name/….etc. The sequencing of the strings / initials has to be in the order, in which the Person desires the short name to be displayed in the documents / forms ) The full name should NOT include Appellation / title. This is one of the instances of generic data element Name of the Person (G01.02), through which Name of the Person can be represented
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Varchar
Max Size	30
Validation
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	As decided by the Expert Committee for MDDS
Version	1.0
Status	Accepted
Date agreed
Verification
Comments	Name of the person should not include Appellation, which is a separate data element, and would be prefixed with name of the person while displaying / printing
Date of Publication	16/11/2011

Example:-Short name in English as desired by the Person to be displayed in the documents like: - K.B.T.NAIR - K.B.Timmappa Nair - Nair Timmappa K.B.

Name of Data Element : Full Name in English (G01.02-02 )
Description of Data Element	Full Name in English expanded and captured in natural order, for the purpose of searching records and data sharing by name strings (It is a set of expanded character strings, each separated by a “blank space”, representing surname / given name/ middle name/….etc in any order as per cultural practices. In the full name, it is mandatory to include all character strings and the expanded strings of initials reflected in the short name. However, the full name can have additional character strings also, which might not have been included in the short name.) It should NOT include Appellation / title. This is one of the instances of generic data element Name of the Person (G01.02), through which Name of the Person can be represented
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Varchar
Max Size	99
Validation
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	Length according to (ICAO 9303), Free format as per OASIS- CIQ-XNL version 2.0
Version	1.0
Status	Accepted
Date agreed
Verification
Comments	Preferably, at the time of capturing the data, the Name may be verified on the basis of some documentary evidence like Birth certificate, School leaving certificate, Ration card etc. The sub-strings ( in any order) in the full name may represent: Given name/First name (>=1) Surname/Family name/Last name (>=0) Middle name (>=0) Patronymic-name (>=0) Metronymic-name (>=0) Generational-Identifier (>=0) Village Name >=0 Any other name type (>=0) etc. The additional requirement of capturing information like Surname / Given name(s) is domain specific, hence NOT covered in this Standard. However, this specific information regarding Given Name(s), Surname can be derived from Full name string, by tagging / identifying the corresponding sub-strings positions, as specified in OASIS- CIQ-XNL version 2.0. Name of the person should not include Appellation, which is a separate data element, and would be prefixed with name of the person while displaying / printing
Date of Publication	16/11/11

Example: 1 -Full name in English (As per culture in Tamil Nadu)  Kagodu Bairappa Timmappa Nair

Where Kagodu: Village name Bairappa: Father’s name Timmappa: Given name Nair: Last / Surname

Example: 2 -Full name in English (As per culture in North India)

 Ram Prasad Sharma

Where

Ram - 1st Given name Prasad - 2nd given name Sharma - Surname

Name of Data Element : Short Name in Recognized Official language (G01.02-03)
Description of Data Element	Short Name in Recognized Official language as desired to be displayed in the documents / forms. (It is a set of character strings / Initials each separated by a “blank space”, representing surname / given name/ middle name/….etc. The sequencing of the strings / initials has to be in the order, in which the Person desires the short name to be displayed in the documents / forms ) It should NOT include Appellation / title. This is one of the instances of generic data element Name of the Person (G01.02), through which Name of the Person can be represented
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Varchar
Max Size	30, Storage in UNICODE Standard UTF-8
Validation
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	As decided by the Expert Committee for MDDS
Version	1.0
Status	Accepted
Date agreed
Verification
Comments	Name of the person should not include Appellation, which is a separate data element, and would be prefixed with name of the person while displaying / printing
Date of Publication	16/11/2011

Example: ए.के .शमार्

Name of Data Element : Full Name in Recognized Official language (G01.02-04 )
Description of Data Element	Full Name in Recognized Official language expanded and captured in natural order, for the purpose of searching records by name strings (It is a set of expanded character strings, each separated by a “blank space”, representing surname / given name/ middle name/….etc in any order as per cultural practices. In the full name, it is mandatory to include all character strings and the expanded strings of initials reflected in the short name. However, the full name can have additional character strings also, which might not have been included in the short name.) It should NOT include Appellation / title. This is one of the instances of generic data element Name of the Person (G01.02), through which Name of the Person can be represented
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Varchar
Max Size	99, Storage in UNICODE Standard UTF-8
Validation
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	Free format as per OASIS- CIQ-XNL version 2.0
Version	1.0
Status	Accepted
Date agreed
Verification
Comments	Preferably, at the time of capturing the data, the Name may be verified on the basis of some documentary evidence like Birth certificate, School Leaving certificate, Ration card etc. The sub-strings ( in any order) in the full name may represent: Given name/First name (>=1) Surname/family name/Last name (>=0) Middle name (>=0) Patronymic / father’s -name (>=0) Metronymic / mother’s -name (>=0) Generational-Identifier (>=0) Village Name >=0 Any other name type (>=0) etc. The additional requirement of capturing information like Surname / Given name(s) is domain specific, hence NOT covered in this Standard. However, this specific information regarding Given Name(s), Surname can be derived from Full name string, by tagging / identifying the corresponding sub-strings positions, as specified in OASIS- CIQ-XNL version 2.0. Name of the person should not include Appellation, which is a separate data element, and would be prefixed with name of the person while displaying / printing.
Date of Publication	16/11/11

Example1 -Full name in Hindi (As per culture in Tamil Nadu)

कागैडु बैरअप्पा ितमप्पा नायर

Where कागैडु Village name

बैरअप्पा - Father’s name

ितमप्पा -Given name

नायर - Surname / last name

Example: 2 -Full name in Hindi (As per culture in North INDIA)

 राम ूसाद शमार् Where राम - 1st Given Name

ूसाद - 2nd Given name

शमार् - Surname

Name of Data Element : Marital Status (G01.04)
Description of Data Element	Code for Marital Status of the Person
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Integer
Max Size	1
Validation
Values	Never Married Currently Married Widow / Widower Divorced Separated
Default value	1- Never Married
Owner	Office of RGI
Based on	-Australian Govt Institute of Health & Welfare http://meteor.aihw.gov.au/content/index.phtml/itemId/291045 -Census of INDIA,
Version	1.1
Status	Accepted
Date agreed
Verification
Comments
Date of Publication	16/11/11

Name of Data Element : Appellation Code (G01.05-01 )
Description of Data Element	An Appellation is title for a Person to be prefixed with His / Her name. It represents: Gender & Marital status like Mr., Mrs., Ms. Attained professional educational qualification like Dr., CA, Engineer etc. A Person can have two Appellations. Refer comments section for multiple Appellation concatenation at interface level.
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Integer
Max Size	2
Validation
Values	For Appellation codes & Values refer to Code Directory (CD01.04)
Default value
Owner	Ministry of Home Affairs
Based on	-UK government data Standard catalog, http://www.cabinetoffice.gov.uk/govtalk/schemasStandards/e- gif/dataStandards/Personinformation/Person_name/Person_title.aspx) -Census of INDIA
Version	1.1
Status	Accepted
Date agreed
Verification
Comments	Maximum of two Appellations are allowed as prefix to the name. The sequence of display / printing of multiple applications would be as follows: Attained Professional Appellation, followed by the “Gender & Marital status” Appellation within brackets. The code directory for Appellation should be multilingual for all the Official Recognized Languages
Date of Publication	16/11/11

Example of multiple Appellations: Dr. (Mrs.) S.K Karla  A Female Doctor

Name of Data Element : Suffix Code (G01.06)
Description of Data Element	Suffix is a title to be suffixed with the Name of a Person: It can be positional title like: IAS, IPS etc. (At times, it can be linked with positional title attained due to some educational qualification like: MD, etc.)
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Integer
Max Size	2
Validation
Values	For Suffix code & Values refer to Code Directory (CD01.05)
Default value
Owner	Ministry of Home Affairs
Based on	As decided by the Expert committee for MDDS
Version	1.1
Status	Accepted
Date agreed
Verification
Comments
Date of Publication	16/11/2011

Example:- Dr. Ramesh Saini, MD

Name of Data Element : Relation Type (G01.07-01)
Description of Data Element	It represents, if a Person is Head or not, of a House hold, to whom other Persons in the house hold are related
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Char
Max Size	1
Validation
Values	H-Head of household N-Not head of household
Default value	N
Owner	Office of RGI
Based on	Census of India
Version	1.1
Status	Accepted
Date agreed
Verification
Comments	Relationship of other Persons with the Head of the family will have to be revised, in case the head of the family in a house hold changes, due to any reason. Note: The business intelligence may have to be built in by Domain application, if required so.
Date of Publication	16/11/2011

Example:

Mr. R. Ramanujam is head of a house hold, and Ms. Ayappa Ramanujam is related to him as Daughter

When Mr. Ramanujam’s son becomes the head, then Ms. Ayappa Ramanujam is related to him as Sister

Name of Data Element : Relationship Code (G01.08-01)
Description of Data Element	Blood relationship / Marriage relationship with Head of the family like Husband, Wife, Daughter, Son, Self etc.
Data Element Type (Generic / Custom)	Generic
Is part of
Parts if any
Data Format	Integer
Max Size	2
Validation
Values	For Relationship codes & values refer to Code Directory (CD01.06)
Default value
Owner	Anthropological Survey of India
Based on	-Australian Government (Australian institute of health & welfare) http://meteor.aihw.gov.au/content/index.phtml/itemId/351361? &addItem=1&items[]=351361&meteorItemView=long -Census of INDIA,
Version	1.1
Status	Accepted
Date agreed
Verification
Comments	The UID number of the head of the family to be stored as attribute in Person Identification. The link will help in changing relationships, if the head of family changes due to any reason.
Date of Publication	16/11/2011

Example:-1 - represents Self

4 - represents Mother

Name of Data Element : Face Image Record (G01.09)
Description of Data Element	Photograph or face image required for human/manual verification of a Person
Data Element Type (Generic / Custom)	Generic
Is part of
Parts if any	Face Image Data Element has the following parts: Face Image Record Header G01.09-00-01 Face Image Record Data G01.09-00-02 Face Image Data G01.09-00-03
Data Format	For the data format, refer to the Metadata of the parts
Max Size
Validation
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	Face Image Data Standard for e-Governance Applications prepared by Expert Committee on Biometrics and released by DIT ( Version 1.0, November, 2010) & ISO 19785-1 ( Common Biometric Exchange Formats Framework – CBEFF) , ISO/IEC 19794-5:2005 (E) Face Image Data (http://egovstandards.gov.in/standardsandFramework/bio metric-standards/view)
Version	1
Status	Accepted
Date agreed
Verification
Comments	This Metadata is used for human verification, so features of the face are not included here.
Date of Publication	16/11/11

Name of Data Element : Face Image Record Header (G01.09-00-01)
Description of Data Element	It provides information about Face information format identifier, Version no, Length of records, Number of face image.
Data Element Type (Generic / Custom)	Generic
Is part of	G01.09 ( Face Image Record )
Parts if any	-Format identifier - 4 bytes -Version number - 4 bytes -Length of record - 4 bytes -Number of face images - 2 bytes
Data Format	Byte
Max Size	( 4+4+4+2)
Validation
Values	For default and prescriptive values, refer Face Image Data Standard prepared by Expert Committee on Biometrics
Default value
Owner	Government of India, Department of Information Technology
Based on	Face Image Data Standard for e-Governance Applications prepared by Expert Committee on Biometrics and released by DIT ( Version 1.0, November, 2010) & ISO 19785-1 ( Common Biometric Exchange Formats Framework – CBEFF) , ISO/IEC 19794-5:2005 (E) Face Image Data
Version	1.0
Status	Accepted
Date agreed
Verification
Comments	This information is important for ensuring interoperability among capturing devices, and more information about the captured face image
Date of Publication	16/11/2011

Name of Data Element : Face Image Record Data (G01.09-00-02)
Description of Data Element	It provides facial information ( record data length, no. of feature points, gender, eye color, hair color, property mask, expression, pose angle, pose angle uncertainty & Face image Information (Face image type, image data type, width, height, image color space source type, device type etc.)
Data Element Type (Generic / Custom)	Generic
Is part of any	G01.09 ( Face Image Record)
Parts if any	-Face Information block -Image information
Data Format	Byte
Max Size	(20+12)
Validation
Values	For default and prescriptive values, refer Face Image Data Standard prepared by the Expert Committee on Biometrics. Some of them are as follows: Resolution - Minimum 300 ppi (pixel per inch) Aspect ratio - between 1 : 1.25 and 1: 1.34, and preferably 1:1.28 Width and Height of Face Image: 420 pixel x 525 pixel (width x height) i.e. 1.4” / 3.5cm (W) x 1.75”/ 4.37 cm (H)
Default value
Owner	Government of India, Department of Information Technology
Based on	Face Image Data Standard for e-Governance Applications prepared by Expert Committee on Biometrics and released by DIT ( Version 1.0, November, 2010) & ISO 19785-1 ( Common Biometric Exchange Formats Framework – CBEFF) , ISO/IEC 19794-5:2005 (E) Face Image Data
Version	1.0
Status	Accepted
Date agreed
Verification
Comments	This information is important for ensuring interoperability among capturing devices, and more information about the captured face image
Date of Publication	16/11/2011

Name of Data Element : Face Image Data (G01.09-00-03)
Description of Data Element	It gives information about the captured Face Image.
Data Element Type (Generic / Custom)	Generic
Is part of any	G01.09 ( Face Image)
Parts if any
Data Format	Data capturing in lossless(Raw / PNG / LosslessJPEG2000/TIFF/DNG) Image Data Storage / Archival in normal memory devices- PNG Image Data storage for verification in restricted memory devices – JPEG2000 with compression ratio up to 1:15
Max Size
Validation
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	Face Image Data Standard for e-Governance Applications prepared by the Expert Committee on Biometrics and released by DIT ( Version 1.0, November, 2010) & ISO 19785-1 ( Common Biometric Exchange Formats Framework – CBEFF) , ISO/IEC 19794-5:2005 (E) Face Image Data
Version	1.0
Status	Accepted
Date agreed
Verification
Comments	This Metadata is used for visual human inspection, so features of the face are not included here. As per the referred GoI standard for face image data, spectacles (not heavy) & eye patch(s) on medical grounds are allowed. Turban for religious reasons only allowed. During enrolment, the quality of face image should be ensured, by filling the Check list given in best practices section 6.2 of the above referenced Face Image Data Standard prepared by the Expert Committee on Biometrics.
Date of Publication	16/11/11

Example:

Name of Data Element : Fingerprint Image Record (G01.10)
Description of Data Element	Fingerprint image required for Identification of a Person
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any	Fingerprint Image data element has the following parts: Fingerprint Image General Record Header G01.10-00-01 Fingerprint Image Record Header G01.10-00-02 Fingerprint Image Data G01.10-00-03
Data Format	For format, refer to Metadata of the parts
Max Size
Validation
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	Finger Image Data Standard for e-Governance prepared by Expert Committee on Biometrics released by DIT ( Version 1.0, November 2010) & ISO 19785-1 (Common Biometric Exchange Formats Framework – CBEFF), ISO 19794-4:2005 (E) Finger Image Data For more details refer (http://egovstandards.gov.in/standardsandFramework/biometri c-standards/view)
Version	1.0
Status	Accepted
Date agreed
Verification
Comments
Date of Publication	16/11/11

Name of Data Element : Fingerprint Image General Record Header (G01.10-00-01)
Description of Data Element	It provides information about Format identifier, Version number, Record length, Capture device ID, Image acquisition level, Number of fingers/palms, Scale unit, Scan resolution, Scan resolution(vertical) Image resolution, Image resolution (vertical), Pixel depth, Image compression algorithm, Pixel depth, Image compression algorithm, Rotation angle estimation flag, Rotation uncertainty.
Data Element Type (Generic / Custom)	Generic
Is part of any	G01.10 ( Fingerprint Image Record )
Parts if any	As mentioned in the description
Data Format	Byte
Max Size	32
Validation	For default and prescriptive values refer section 5 of Fingerprint Image Data Standard prepared by Expert Committee on Biometrics and released by DIT ( Version 1.0, November, 2010)
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	Finger Image Data Standard for e-Governance Applications prepared by the Expert Committee on Biometrics & ISO 19785-1 ( Common Biometric Exchange Formats Framework – CBEFF), ISO 19794-4:2005 (E) Fingerprint Image Data
Version	1.0
Status	Accepted
Date agreed
Verification
Comments
Date of Publication	16/11/2011

Name of Data Element : Fingerprint Image Record Header (G01.10-00-02)
Description of Data Element	It provides information about length of Finger data block, Finger position, Count of views, View number, Finger/Palm Image quality, Impression type, Horizontal line length, Vertical line Length, Rotational angle, Finer/palm image data.
Data Element Type (Generic / Custom)	Generic
Is part of	G01.10 (Fingerprint Image Record Header)
Parts if any	As mentioned in the description
Data Format	Byte
Max Size	14
Validation	For default and prescriptive values refer section 5 of Fingerprint Image Data Standard prepared by Expert Committee on Biometrics and released by DIT ( Version 1.0, November, 2010)
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	Fingerprint Image Data Standard for e-Governance Applications prepared by the Expert Committee on Biometrics & ISO 19785-1 ( Common Biometric Exchange Formats Framework – CBEFF), ISO 19794-4:2005 (E) Finger Image Data
Version	1.0
Status	Accepted
Date agreed
Verification
Comments
Date of Publication	16/11/2011

Name of Data Element : Fingerprint Image Data (G01.10-00-03)
Description of Data Element	It stores image of Fingerprint for the purpose of Storage and Extraction of Minutia for the purpose of verification
Data Element Type (Generic / Custom)	Generic
Is part of any	G01.10 (Fingerprint Image Record Header)
Parts if any
Data Format	Image Data Storage / Archival in normal memory devices- PNG Image Data storage for verification in restricted memory devices – JPEG2000 with compression ratio up to 1:15
Max Size	<= 12 KB
Validation	For default and prescriptive values refer section 5 of Fingerprint Image Data Standard prepared by the Expert Committee on Biometrics and released by DIT ( Version 1.0, November, 2010)
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	Fingerprint Image Data Standard for e-Governance Applications prepared by the Expert Committee on Biometrics, ISO 19794-4:2005(E) Finger Image Data
Version	1.0
Status	Accepted
Date agreed
Verification
Comments
Date of Publication	16/11/2011

Name of Data Element : Iris Image Record Header (G01.11-00-01)
Description of Data Element	It provides information about format identifier, Version no, Length of entire record, Capture device id, No. of iris biometric sub types, Record header length, Image property bit field, horizontal orientation, vertical orientation, scan type, iris occlusion filling, boundary extraction, Iris diameter, image format, image width, image height, image intensity depth, transformation to polar image, device unique identifier .
Data Element Type (Generic / Custom)	Generic
Is part of	G01.11 ( Iris Image)
Parts if any	As mentioned in the description
Data Format	Byte
Max Size	45
Validation	For default and prescriptive values refer section 5 of Iris Image Data Standard prepared by the Expert Committee on Biometrics and released by DIT ( Version 1.0, March 2011)
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	Iris Image Data Standard for e-Governance Applications prepared by the Expert Committee on Biometrics released by DIT (Version 1.0 March, 2011) & ISO 19785-1 (Common Biometric Exchange Formats Framework – CBEFF) , ISO 19785-3 (Patron Format Specification) and ISO/IEC 19794-6:2005 (E) Iris mage Data
Version	1.0
Status	Accepted
Date agreed
Verification
Comments
Date of Publication	16/11/2011

Name of Data Element : Iris Image sub type header (G01.11-00-02)
Description of Data Element	It provides information about biometrics sub type identifier, number of Iris images.
Data Element Type (Generic / Custom)	Generic
Is part of any	G01.11 (Iris Image)
Parts if any
Data Format	Byte
Max Size	3
Validation
Values	Biometric subtype identifier=0 (No Information Given) Biometric subtype identifier=1 (Right Eye) Biometric subtype identifier=2 (Left Eye)
Default value
Owner	Government of India, Department of Information Technology
Based on	Iris Image Data Standard for e-Governance Applications prepared by the Expert Committee on Biometrics released by DIT (Version 1.0, March, 2011) & ISO 19785-1 ( Common Biometric Exchange Formats Framework – CBEFF) , ISO/IEC 19794-6:2005 (E) Iris Image Data
Version	1.0
Status	Accepted
Date agreed
Verification
Comments
Date of Publication	16/11/2011

Name of Data Element : Iris image header (G01.11-00-03)
Description of Data Element	It give information about Image sequence number, Image quality, Rotation angle, Rotation uncertainty, Size of image data, Image data
Data Element Type (Generic / Custom)	Generic
Is part of any	G01.11 ( Iris Image)
Parts if any
Data Format	Bytes
Max Size	11
Validation
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	Iris Image Data Standard for e-Governance Applications prepared by the Expert Committee on Biometrics released by DIT (Version 1.0, March, 2011 & ISO 19785-1 ( Common Biometric Exchange Formats Framework – CBEFF) , ISO/IEC 19794-6:2005(E) Iris Image Data
Version	1.0
Status	Accepted
Date agreed
Verification
Comments
Date of Publication	16/11/2011

Name of Data Element : Iris Image Data (G01.11-00-04)
Description of Data Element	It gives information about Iris Image storage data
Data Element Type (Generic / Custom)	Generic
Is part of any	G01.11 ( Iris Image Header)
Parts if any
Data Format	Data capturing in lossless format (Raw / PNG / LosslessJPEG2000) Image Data Storage / Archival in normal memory devices- PNG
Max Size	Variable length size up to 11,862 bytes
Validation
Values
Default value
Owner	Government of India, Department of Information Technology
Based on	Iris Image Data Standard for e-Governance Applications prepared by the Expert Committee on Biometrics released by DIT (Version 1.0, March, 2011 & ISO 19785-1 ( Common Biometric Exchange Formats Framework – CBEFF) , ISO/IEC 19794-6:2005 (E) Iris Image Data
Version	1.0
Status	Accepted
Date agreed
Verification
Comments
Date of Publication	16/11/2011

Name of Data Element : Specimen Signature/Thumb Impression Image (G01.12)
Description of Data Element	Scanned Image of Person’s Own hand written Signature /Thumb impression The thumb impression means “ plain inked thumb impression image”
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Data Storage / Archival in normal memory devices - PNG Data storage in restricted memory devices – JPEG2000 with compression ratio up to 1:15
Max Size	The size of image would be 256 pixels in width & 64 pixels in Height i.e. 1.4” / 3.5cm (W) x 0.44” / 1.06 cm (H) Suggested Aspect ratio is 4:1(W:H)
Validation	Right hand thumb impression in case of Female, and Left hand thumb impression in case of Male
Values
Default value	The size of image would be 256 pixels in width & 64 pixels in height
Owner	Government of India, Department of Information Technology
Based on	Aspect ratio (Biometrics solution for authentication in An E- world written by David D. Zhang published by Springer), and as decided by the Expert Committee for MDDS
Version	1.0
Status	Accepted
Date agreed
Verification
Comments	It is NOT mandatory to store the image of the Specimen Signature and the data format also are suggestive.
Date of Publication	16/11/2011

Name of Data Element : Education Attained Code (G01.13-01)
Description of Data Element	Code for Educational Qualification attained by the Person
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Integer
Max Size	3
Validation
Values	For Education attained codes & values refer to Code Directory (CD01.03)
Default value
Owner	Department of Higher Education
Based on	Present comprehensive Code Directory values taken from Office of RGI
Version	1.1
Status	Accepted
Date agreed
Verification
Comments
Date of Publication	16/11/2011

Example: - 1 code represents Illiterate

Name of Data Element : Religion Code (G01.14-01 )
Description of Data Element	Religion Code
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Integer
Max Size	2
Validation
Values	For Religion codes & values to be taken from Code Directory (CD01.01)
Default value
Owner	Department of Anthropological Survey of India / Office of RGI
Based on	Present Code Directory values taken from Office of RGI
Version	1.1
Status	Accepted
Date agreed
Verification
Comments	This need NOT be mandatory for person identification, but may be required for other purposes by e-Governance Applications
Date of Publication	16/11/2011

Example:- code 3 represents Hinduism

Name of Data Element : Occupation Type Code (G01.15-01)
Description of Data Element	Current Occupation type code for the Person
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Integer
Max Size	2
Validation
Values	For Occupation type codes & values refer to Code Directory (CD01.02)
Default value
Owner	Ministry of Labour
Based on	Present comprehensive Code Directory values taken from Office of RGI
Version	1.1
Status	Accepted
Date agreed
Verification
Comments
Date of Publication	16/11/2011

Example:- code 1 represents Legislators

Name of Data Element : Date of Birth Type (G01.16)
Description of Data Element	This would be mainly used to flag , if the Date of Birth is actual or declared, in case, the Person is not sure about his Date of Birth Verified (verified from document) Declared (not verified with document) Approximate (calculated from the values mentioned in no. of years as on current date by taking month as 07 and day as 01, and backward calculation of the year)
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Char
Max Size	1
Validation
Values	V- Verified (verified from document) D- Declared (not verified with document) A - Approximate (calculated from the values mentioned in no. of years as on current date by taking month as 07 and day as 01, and backward calculation of the year)
Default value	V – Verified
Owner	Government of India, Department of Information Technology
Based on	As decided by the Expert committee for MDDS
Version	1
Status	Accepted
Date agreed
Verification
Comments
Date of Publication	16/11/2011

Example – In year 2009, while filling the form, a Person may say that he is approximately 50 year old. Then the approximate calculated Date of Birth of the Person would be : 01/07/1959

Name of Data Element : Live Status (G01.17)
Description of Data Element	Status of Person as Alive or Dead
Data Element Type (Generic / Custom)	Generic
Is part of any
Parts if any
Data Format	Char
Max Size	1
Validation
Values	A- Alive D- Dead
Default value	A- Alive
Owner	Government of India, Department of Information Technology
Based on	Expert committee for MDDS
Version	1
Status	Accepted
Date agreed
Verification
Comments	In case of change of status to “D” The Person’s record may need to be moved to Archival database If the Person’ relation type is “Head”, the relationship codes of other related Persons also to be prompted for change ( The link between them is through UID Number of the Head which is stored in the record of each related Person) Business intelligence would need to be built in the respective systems. Recommended prefixing of the title (Late) in case the status is “D” , while printing / display
Date of Publication	16/11/2011

Metadata of Generic data elements for Land Region Codification

Name of Data Element : Name of Land Region (G02.02)
Description of Data Element	Defines Name of Land Region like Country name, State name, District name, Sub District name, Rural Land region (Revenue Village), and Urban Land region(Town / Administrative Land region). It can be represented in English /recognized official language. This data element has two instances as follows: Name of Land Region in English G02.02-01 Name of Land Region in Recognized Official Language G02.02-02
Data Element Type (Generic/Custom)	Generic
Is Part of
Parts if any
Data Format	Refer to formats of corresponding Generic data instances
Max Size
Validations
Values	Country Name data to be taken as per ISO-3166-1981 Standard The data to be taken from ORGI(for State/ District/ Sub District/ Village / Town names)
Default Value
Owner	Office of RGI
Based on	ISO-3166-1981 Standard (for Country name) ORGI naming scheme for other Land regions
Version	1
Status	Accepted
Date Agreed
Verification
Comments
Date of Publishing	16/11/2011

Name of Data Element : Name of Land Region in English (G02.02-01)
Description of Data Element	This is instance of generic data element G02.02. This defines Name of Land Region like Country name , State name, District name, Sub District name, Rural Land region ( Revenue Village), and Urban Land region (Town / Administrative Land region) in English
Data Element Type (Generic/Custom)	Generic
Is Part of
Parts if any
Data Format	Varchar
Max Size	50
Validations
Values	Country Name data to be taken as per ISO-3166-1981 Standard The data to be taken from ORGI(for State/ District/ Sub District/ Village / Town names)
Default Value
Owner	Office of RGI
Based on	ISO-3166-1981 Standard (for Country name) ORGI naming scheme for other Land regions
Version	1
Status	Accepted
Date Agreed
Verification
Comments
Date of Publishing	16/11/2011

Name of Data Element : Name of Land Region in Recognized Official Language(G02.02-02)
Description of Data Element	This is instance of generic data element G02.02. Defines Name of Land Region like Country name , State name, District name, Sub District name, Rural Land region (Revenue Village) name, and Urban Land region (Town) name in Recognized Official Language (First Official language of the State)
Data Element Type (Generic/Custom)	Generic
Is Part of
Parts if any
Data Format	Varchar
Max Size	50 Storage in UNICODE Standard UTF-8
Validations	Should be from 22 recognized Official Languages
Values	Country Name data to be taken as per ISO-3166-1981 Standard The data to be taken from ORGI(for State/ District/ Sub District/ Village / Town names)
Default Value
Owner	Office of RGI
Based on	ISO-3166-1981 Standard (for Country name) ORGI naming scheme for other Land regions
Version	1
Status	Accepted
Date Agreed
Verification
Comments
Date of Publishing	16/11/2011

Metadata of Data elements for Address of Premises

Name of Data Element : Address of a Premises (G02.03)
Description of Data Element	To describe physical location of a commercial / residential premises within a rural or urban land region It has mainly three parts as follows: Address Type & Premises Identifier G02.03-00 Sub locality / Locality Identifier G02.03-00-03 Postal services data elements G02.04
Data Element Type (Generic/Custom)	Generic
Is Part of
Parts if any
Data Format	For format and other details refer to Metadata of the parts
Max Size
Validations
Values
Default Value
Owner	Department of Post
Based on	As per xAL version 2 Standard of OASIS, and format by Expert Committee
Version	1
Status	Accepted
Date Agreed
Verification
Comments
Date of Publishing	16/11/2011

Name of Data Element : Address Type (AT) (G02.03-00-01)
Description of Data Element	Address Type: It defines the category of address: Residential, Organizational
Data Element Type (Generic/Custom)	Generic
Is Part of	Address of Premises( G02.03)
Parts if any
Data Format	Varchar
Max Size	15
Validations
Values
Default Value
Owner	Department of Post
Based on	As per xAL version 2 Standard of OASIS, and format by Expert Committee
Version	1.0
Status	Accepted
Date Agreed
Verification
Comments
Date of Publishing	16/11/2011

Name of Data Element : Premises (G02.03-00-02)
Description of Data Element	Premises Identifier House Number/ Door Number. / Flat Number. / House Identifier Building Number / Plot Number Building Name Stairwell / Lift Number. One or more attributes separated by “,” can be used to identify a Premises / House / Building in a Sub Locality. At least one attribute is Mandatory in the Address of Premises to identify it uniquely.
Data Element Type (Generic/Custom)	Generic
Is Part of	Address of Premises (G02.03)
Parts if any
Data Format	Varchar
Max Size	60
Validations	Should be unique for each house within a Premises
Values
Default Value
Owner	Department of Post
Based on	As per xAL version 2 Standard of OASIS, and format by Expert Committee
Version	1
Status	Accepted
Date Agreed
Verification
Comments	If required, e-Governance applications can store various Premises identifiers as separate data element(s) to meet the domain specific requirements. Such storage would also help in Geo-referencing of Address of the Premises, which is being taken up in Phase-II. However size for printing/ display should be limited to Varchar(60)
Date of Publishing	16/11/2011

Name of Data Element : Sub Locality / Locality Identifier (G02.03-00-03)
Description of Data Element	It has three instances like: Sub Locality- 1 : G02.03-01-03 Sub Locality -2 : G02.03-02-03 Locality : G02.03-03-03 Sub Locality-1 : Block Name/Number or any other qualifier Street Number/Name/ Mohalla / Sector Number/any other qualifier Sub Locality-2 : Major / Minor Land Mark Locality : Area Number / Area Name / Suburb / Sub District Name in case of a village
Data Element Type (Generic/Custom)	Generic
Is Part of	Address of Premises (G02.03)
Parts if any
Data Format	Refer to metadata of instances
Max Size
Validations
Values
Default Value
Owner	Department of Post
Based on	As per xAL version 2 Standard of OASIS, and format by Expert Committee
Version	1.0
Status	Accepted
Date Agreed
Verification
Comments	If required, e-Governance applications can store various Sub- Locality / Locality identifiers as separate data element(s) to meet the domain specific requirements. Such storage would also help in Geo-referencing of Address of the Premises, which is being taken up in Phase-II.
Date of Publishing	16/11/2011

Name of Data Element : Premises (G02.03-00-02)
Description of Data Element	Premises Identifier House Number/ Door Number. / Flat Number. / House Identifier Building Number / Plot Number Building Name Stairwell / Lift Number. One or more attributes separated by “,” can be used to identify a Premises / House / Building in a Sub Locality. At least one attribute is Mandatory in the Address of Premises to identify it uniquely.
Data Element Type (Generic/Custom)	Generic
Is Part of	Address of Premises (G02.03)
Parts if any
Data Format	Varchar
Max Size	60
Validations	Should be unique for each house within a Premises
Values
Default Value
Owner	Department of Post
Based on	As per xAL version 2 Standard of OASIS, and format by Expert Committee
Version	1
Status	Accepted
Date Agreed
Verification
Comments	If required, e-Governance applications can store various Premises identifiers as separate data element(s) to meet the domain specific requirements. Such storage would also help in Geo-referencing of Address of the Premises, which is being taken up in Phase-II. However size for printing/ display should be limited to Varchar(60)
Date of Publishing	16/11/2011

Name of Data Element : Sub Locality -2 (G02.03-02-03)
Description of Data Element	Sub Locality -2 defines Major / Minor Land Mark It is an instance of Location Identifier G02.03-00-03
Data Element Type (Generic/Custom)	Generic
Is Part of	Address of Premises (G02.03)
Parts if any
Data Format	Varchar
Max Size	60
Validations
Values
Default Value
Owner	Department of Post
Based on	As per xAL version 2 Standard of OASIS, and format by Expert Committee
Version	1.0
Status	Accepted
Date Agreed
Verification
Comments	If required, e-Governance applications can store various Sub Locality - 2 identifiers as separate data element(s) to meet the domain specific requirements. Such storage would also help in Geo-referencing of Address of the Premises, which is being taken up in Phase-II. Recommended length of printing/ display of Sub Locality -1 + Sub Locality -2 should be Varchar(60)
Date of Publishing	16/11/2011

Name of Data Element : Locality (G02.03-03-03)
Description of Data Element	Locality defines Area Number / Area Name / Suburb It is an instance of Location Identifier G02.03-00-03
Data Element Type (Generic/Custom)	Generic
Is Part of	Address of Premises (G02.03)
Parts if any
Data Format	Varchar
Max Size	60
Validations
Values
Default Value
Owner	Department of Post
Based on	As per xAL version 2 Standard of OASIS, and format by Expert Committee
Version	1.0
Status	Accepted
Date Agreed
Verification
Comments	If required, e-Governance applications can store various Locality identifiers as separate data element(s) to meet the domain specific requirements. Such storage would also help in Geo-referencing of Address of the Premises, which is being taken up in Phase-II.
Date of Publishing	16/11/2011

Name of Data Element : Address Verification Status (VAS) (G02.03-00-04)
Description of Data Element	Defines the status of the Address, whether Verified or Self declared, required for internal storage
Data Element Type (Generic/Custom)	Custom
Is Part of	Address of Premises (G02.03)
Parts if any
Data Format	Char
Max Size	1
Validations
Values	V- Verified S- Self declared
Default Value	Self declared
Owner	Department of Post
Based on
Version	1.0
Status	Accepted
Date Agreed
Verification
Comments
Date of Publishing	16/11/2011

Metadata of Generic Data Elements for Postal Service

Name of Data Element : Postal Services (G02.04)
Description of Data Element	Instances to codify Postal Services like: G02.04-01 Postal Index Number G02.04-02 Post Office Service Type G02.04-03 Post Office Service Number G02.04-04 Delivery Post Office Name G02.04-05 Beat Number
Data Element Type (Generic/Custom)	Generic
Is Part of
Parts if any
Data Format	Refer to format of Instances corresponding to this Generic Data Element
Max Size
Validations	Unique for town/ revenue village
Values	Data to be taken as per Department of Post
Default Value
Owner	Department of Post
Based on	S42a-5 & S42b-5 Universal Postal Union Standard & Department of Post
Version	1
Status	Accepted
Date Agreed
Verification
Comments
Date of Publishing	16/11/2011

Name of Data Element: Postal Index Number (PIN) (G02.04-01)
Description of Data Element	Postal Index Number (PIN) Postal address element designating the code used for sorting the mail. Internationally, it is named as ZIP code It is an instance of the generic data element Postal Service (G02.04)
Data Element Type (Generic/Custom)	Generic
Is Part of
Parts if any
Data Format	Integer
Max Size	6
Validations
Values	Data to be taken as per Department of Post
Default Value
Owner	Department of Post
Based on	S42a-5 & S42b-5 Universal Postal Union Standard & Department of Post
Version	1.1
Status	Accepted
Date Agreed
Verification
Comments
Date of Publishing	16/11/2011

Name of Data Element : Post Office Service Type (POST) (G02.04-02)
Description of Data Element	Post Office Service Type PO box service GPO box service Free Post service Post Bag service e-Post service It is an instance of Postal Service G02.04
Data Element Type (Generic/Custom)	Generic
Is Part of	Postal Service (G02.04)
Parts if any
Data Format	Varchar
Max Size	20
Validations
Values	Data to be taken as per Department of Post
Default Value
Owner	Department of Post
Based on	S42a-5 & S42b-5 Universal Postal Union Standard & Department of Post
Version	1
Status	Accepted
Date Agreed
Verification
Comments
Date of Publishing	16/11/2011

Name of Data Element : Post Office Service Number (G02.04-03)
Description of Data Element	Post Office Service Number PO box number GPO box number Free Post number Post Bag number e-Post number It is an instance of Postal Service G02.04
Data Element Type (Generic/Custom)	Generic
Is Part of
Parts if any
Data Format	Integer
Max Size	6
Validations
Values	Data to be taken as per Department of Post
Default Value
Owner	Department of Post
Based on	S42a-5 & S42b-5 Universal Postal Union Standard & Department of Post
Version	1.1
Status	Accepted
Date Agreed
Verification
Comments
Date of Publishing	16/11/2011

Name of Data Element : Delivery Post Office Name (G02.04-04)
Description of Data Element	Delivery Post Office Name is a secondary qualifier in case Locality doesn’t have a Post Office -This element defines the address components that are specific to Postal Services. It can be used for the physical delivery of mail. It is an instance of Postal Service G02.04
Data Element Type (Generic/Custom)	Generic
Is Part of
Parts if any
Data Format	Varchar
Max Size	30
Validations
Values	Data to be taken as per Department of Post
Default Value
Owner	Department of Post
Based on	S42a-5 & S42b-5 Universal Postal Union Standard & Department of Post
Version	1.0
Status	Accepted
Date Agreed
Verification
Comments
Date of Publishing	16/11/2011

Name of Data Element : Beat Number (G02.04-05)
Description of Data Element	Beat Number The two digit number additional to PIN to be used by Postal Dept. for sorting the mail It is an instance of Postal Service G02.04
Data Element Type (Generic/Custom)	Generic
Is Part of
Parts if any
Data Format	Integer
Max Size	2
Validations
Values	Data to be taken as per Department of Post
Default Value
Owner	Department of Post
Based on	Department of Post
Version	1.1
Status	Accepted
Date Agreed
Verification
Comments
Date of Publishing	16/11/2011

Metadata of Generic Data Element for Geo Referencing (To be taken up in Phase-II)

Name of Data Element : Geo-coding of a Land region / G02.05
Description of Data Element	Geo-code of a Land region / Address of a Premises
Data Element Type (Generic/Custom)	Generic
Is Part of	Geo Referencing (G02.05)
Parts if any	Longitude (G02.05-00-01) Latitude (G02.05-00-02) Altitude (G02.05-00-03)
Data Format	Degree minute second
Max Size
Validations
Values
Default Value
Owner of Data element Standard
Based on
Version	1
Status	Accepted
Date Agreed
Verification
Comments
Date of Publishing	16/11/2011