Data management

Standard id Standard Clasification
DAT.DM.001 Use DBMS that supports JDBC latest version for java based applications. Recomended
DAT.DM.002 Use DBMS that supports ODBC for non-Java based applications. As ODBC drivers are implemented by various vendors, it would be advisable to identify DBMS that support the latest stable version of the ODBC. Recomended
DAT.DM.003 Support for SQL:2003 standards defined in ISO/IEC 9075. SQL:2003 is the fifth revision of SQL used by relational database. Mandatory
DAT.DM.004 Support for SQL:2008 standards defined in ISO/IEC 9075. SQL:2008 is the latest 2008 revision of SQL used by relational database. Recomended
DAT.DM.005 There is no technical standard for compliance. Please refer to Best Practices for more information. Recomended
DAT.DM.006 There is no technical standard for compliance. Please refer to Best Practices for more information. Recomended
DAT.DM.007 There is no technical standard for compliance. Please refer to Best Practices for more information. Recomended
DAT.DM.008 There is no technical standard for compliance. Please refer to Best Practices for more information. Recomended

Data design

Standard id Standard Clasification
DAT.DD.001 Use one of the following notations for data modelling:
(a) Unified Modelling Language (UML)
(b) Barker's Notation
(c) Information Engineering.
Recomended
DAT.DD.002 Use Unicode standard to support the worldwide. Recomended

Extract, Transform, Load (ETL)

Standard id Standard Clasification
DAT.ETL.001 ETL tools should be used in scenarios where large amounts of data need to be moved, transformed, enriched, and/or merged from multiple data sources to a target source. An example of this is the loading of data from source systems into a data warehouse Recomended
DAT.ETL.002 ETL processes should be scheduled so that they do not impact the operations and end users of the source systems they are extracting from Recomended
DAT.ETL.003 The ETL process should encourage to move the data from the source to the ETL environment quickly and should access the source only once. The target architecture should ensure re-use of a single data copy from production sources to minimize resource utilization on the source system Recomended
DAT.ETL.004 The artefacts of ETL processes (e.g., scripts, SQL code, data mappings, etc.) should be kept in a repository and managed so that lineage of the data produced from those processes is traceable Recomended
DAT.ETL.005 ETL processes should encourage use of a centralized metadata repository to ensure data quality and integrity. Recomended
DAT.ETL.006 ETL processes should provision for a facility to perform standard centralized data quality checks with required and optional checks which may be decided by the target system Recomended
DAT.ETL.007 ETL processes should provision for a storage mechanism for clean data thus eliminating the need for new processes to re-source data recheck values or re-compute derived values. Recomended

Metadata Management

Standard id Standard Clasification
DAT.MM.001 Element : Element description Mandatory
DAT.MM.002 Creator : Person or organisation primarily responsible for creating the intellectual content of the resource-e.g., authors in the case of written documents, and artists, photographers, etc. in the case of visual resources Mandatory
DAT.MM.003 Publisher : The entity (e.g., agency, including unit/branch/section) responsible for making the resource available in its present form, such as a publishing house, a university department, or a corporate entity. Mandatory
DAT.MM.005 Rights Management : A rights management statement or an identifier that links to a rights management statement. Mandatory
DAT.MM.006 Title : The name given to the resource, usually by the creator or publisher. Mandatory
DAT.MM.007 Subject : The topic of the resource. Typically, this will be expressed as keywords or phrases that describe the subject or content of the resource. Controlled vocabularies and formal classification schemes are encouraged. Mandatory
DAT.MM.008 Date : A date associated with the creation or availability of the resource. Mandatory
DAT.MM.009 Identifier : A string or number used to uniquely identify the resource. Examples for networked resources include URLs, Purls, and URNs. ISBN or other formal names can be used. Mandatory
DAT.MM.010 Description : A textual description of the content of the resource, including abstracts in the case of document-like objects or content descriptions in the case of visual resources. Mandatory
DAT.MM.011 Source : The work, either print or electronic, from which this object is derived (if applicable). Source is not applicable if the present resource is in its original form. Mandatory
DAT.MM.012 Language : The language of the intellectual content of the resource. Mandatory
DAT.MM.013 Relation : Relationship to other resources-e.g., images in a document, chapters in a book, or items in a collection Mandatory
DAT.MM.014 Coverage : Spatial locations and temporal duration characteristic of the resource. Mandatory
DAT.MM.015 Type : The category of the resource, such as home page, novel, poem, working paper, technical report, essay, or dictionary. Mandatory
DAT.MM.016 Format : The data format of the resource, used to identify the software and possibly hardware that might be needed to display or operate the resource-e.g., postscript, HTML, TXT, JPEG, or XML. Mandatory

Data Security

Standard id Standard Clasification
DAT.DS.001 Use cryptographic techniques for encryption of sensitive data. The reference standards for cryptography include Triple Data Encryptions Standard (3DES), Advance Encryption Standard (AES). Recommended
DAT.DS.002 Databases should not be accessible directly from external network (non-government network). Mandatory
DAT.DS.003 Use RDBMS with security controls to ensure aggregation (value of disclosed data) and inference (confidentiality). Mandatory
DAT.DS.004 Use RDBMS that supports the following security controls:
Data access as an intended privilege
(b) Key management and encryption
(c) Integrity constrains such as domain constraints, attribute constraints, relation constraints, and database constraints
(d) High availability implementation, backup, restoration and data replication
(e) Database log and policy enforcement
Mandatory
DAT.DS.005 Data destruction shall be done using degaussing (NIST 800-88 guidelines for Media Sanitisation), data overwriting (Bruce chneier algorithm, DOD 5220.22-M, Peter Gutmann Secure Deletion) and physical Recommended

Data Storage, Backup and Archival

Standard id Standard Clasification
DAT.DBA.001 Data Archiving shall support integrity checking through hashing, audit logging and regulatory compliance. Mandatory
DAT.DBA.002 Strict security policies should be established for archived data to prevent unauthorised access and data loss. Mandatory
DAT.DBA.003 Use ISO 15489-1 for records management. Recommended
DAT.DBA.004 Use the Dublin Core metadata element set for resource description based on ISO 15836. Recommended
DAT.DBA.005 Use portable document format for document management based on ISO 32000-1. Recommended
DAT.DBA.006 Use ISO/TR 18492 for long-term preservation of electronic document-based information. Recommended
DAT.DBA.007 Use Open Archival Information System (OAIS) to establish a system for archiving information for both digitalized and physical. This framework is based on ISO 14721. Recommended

Metadata, Spatial data Management, Enterprise Schema and BI

Standard id Standard Clasification
DAT.MSEB.001 Use XML Schemas 1.0 and above to manage and overall Enterprise Schema. Mandatory
DAT.MSEB.002 Use Metadata Object Facility (MOF) to define, manipulate and integrate metadata and data in a platform independent manner. Mandatory
DAT.MSEB.003 Support Resource Description Framework (RDF) framework for describing and interchanging metadata based on resource, properties and statements definitions. Recommended
DAT.MSEB.004 Support Common Warehouse Metamodel (CWM) to enable interchange of warehouse and BI metadata between warehouse tools, warehouse platforms and warehouse Metadata repositories in distributed heterogeneous environments. Recommended
DAT.MSEB.005 Support Common Warehouse Metamodel Metadata Interchange Patterns to add semantic context to the interchange of Metadata in terms of recognised sets of objects or object patterns. Recommended
DAT.MSEB.006 Use the set of standards produced by ISO/TC 211 that supports the understanding and usage of geographic information. Recommended
DAT.MSEB.007 Support Open Geospatial Consortium (OpenGIS) Simple Feature that provides a way for application to access spatial data in RDBMS. There are three standards available – CORBA, SQL and OLE/COM. Recommended
DAT.MSEB.008 Use Open GIS Geography Markup Language Encoding Standard (GML 2, GML 3) for transfer and storage of geographic information. Recommended
DAT.MSEB.009 Support Open GIS Web Map Service (WMS), Web Feature Services (WFS) and Web Coverage Service (WCS) specifications which specify protocols that provide uniform access by HTML clients to maps rendered by WMS enabled map servers on the internet. Recommended
DAT.MSEB.010 Support Open GIS Catalogue Services Interface Standards (CAT) to publish and search collections of descriptive information (metadata) about geospatial data, services and related resources. Recommended
DAT.MSEB.011 Support Open GIS Keyhole Markup Language (KML)Service for geographic visualisation, including annotation of maps and images. Recommended

Industry data exchange standards

Standard id Standard Clasification
DAT.IDES.001 Use Extensible Markup Language (XML 1.0 or XML1.1) as a preferred data exchange standard. Recommended
DAT.IDES.002 Support the following standards for exchange of textual data:
(a) Extensible Markup Language (XML 1.0 or XML 1.1) for most applications
(b) Support Comma Separated Value (CSV) for legacy applications
Recommended
DAT.IDES.003 Support the following standards for exchange of image data:
(a) Joint Photographic Experts Group (JPEG) for photography images
(b) Graphics Interchange Format (GIF) for internet images due to its small size and support for animation
(c) Tagged Image File Format (TIFF) for scanned Images
(d) Portable Network Graphic (PNG) for internet images which require increased colour depth compared to GIF
Mandatory
DAT.IDES.004 Support the following standards for exchange of video and audio data:
(a) Moving Pictures Expert Group (MPEG-1 to MPEG-4) for most audio and video applications
(b) 3rd Generation Partnership Project (3GPP and 3GPP2) for audio and video over 3G mobile Networks
Recommended
DAT.IDES.005 Support the file transfer through client file transfer and Server File transfer – FTP server Recommended
DAT.IDES.006 Web Service Description Language is an XML based interface definition language that is used describing the functionality offered by a web service N.A.
DAT.IDES.007 Web Services Security (WS-Security, WSS) is an extension to SOAP (Simple Object Access protocol) to apply security to Web services N.A.
DAT.IDES.008 Use XML Metadata Interchange (XMI) as a XML Integration framework for defining, interchanging, manipulating and integrating XML data and objects. Recommended
DAT.IDES.009 Use xPath 2.0, an XML path language for selecting nodes from an XML document. Recommended
DAT.IDES.010 Use XQuery 1.0 to design query collections for XML data. Recommended
DAT.IDES.011 Use XSLT 2.0 for transforming XML documents into other XML documents. Recommended
DAT.IDES.012 Message queues and mailboxes are software-engineeringcomponents used for inter-process communication (IPC), or for inter-thread communication within the same process N.A.
DAT.IDES.013 A directory service is a software system that stores, organizes, and provides access to information in a computer operating system's directory N.A.