Data definition specification

From HandWiki

In computing, a data definition specification (DDS) is a guideline to ensure comprehensive and consistent data definition. It represents the attributes required to quantify data definition. A comprehensive data definition specification encompasses enterprise data, the hierarchy of data management, prescribed guidance enforcement and criteria to determine compliance.

Overview

A data definition specification may be developed for any organization or specialized field, improving the quality of its products through consistency and transparency. It eliminates redundancy (since all contributing areas are referencing the same specification) and provides standardization, making it easier and more efficient to create, modify, verify, analyze and share information across the enterprise.[1]

To understand how a data definition specification works in an enterprise, we must look at the elements of a DDS. Writing data definitions, defining business terms (or rules) in the context of a particular environment, provides structure for an organization's data architecture. In developing these definitions, the words used must be traceable to clearly defined data.

A data definition specification may be used in the following activities:

Criteria

A data definition specification requires data definitions to be:

  • Atomic – singular, describing only one concept. Commonly used and ambiguous terms should be defined.[2] While a term refers to one concept, several words may be used in a term:
  • File – A concept identifiable with one word
  • File extension – A concept identifiable with more than one word
  • Traceable – Mapped to a specific data element. In business, a term may be traced to an entity (for example, a customer) or an attribute (such as a customer's name). A term may be a value in a data set (such as gender), or designate the data set itself. Traceability indicates relationships in the data hierarchy.
  • Consistent - Used in a standard syntax; if used in a specific context, the context is noted
  • Accurate - Precise, correct and unambiguous, stating what the term is and is not[3]
  • Clear - Readily understood by the reader
  • Complete - With the term, its description and contextual references
  • Concise - To avoid circular references

Applications

Enterprise data

A data definition specification was produced by the Open Mobile Alliance to document charging data.[4] The document, the centralized catalog of data elements defined for interfaces, specifies the mapping of these data elements to protocol fields in the interfaces. Created for the exchange of financial data, Market Data Definition Language (MDDL) is an XML specification designed

to enable the interchange of information necessary to account, to analyze, and to trade financial instruments of the world's markets. It defines an XML-based interchange format and common data dictionary on the fields needed to describe: (1) financial instruments, (2) corporate events affecting value and tradability, and (3) market-related, economic and industrial indicators. The principal function of MDDL is to allow entities to exchange market data by standardizing formats and definitions. MDDL provides a common format for market data so that it can be efficiently passed from one processing system to another and provides a common understanding of market data content by standardizing terminology and by normalizing the relationships of various data elements to one another ... From the user perspective, the goal of MDDL is to enable users to integrate data from multiple sources by standardizing both the input feeds used for data warehousing (i.e., define what's being provided by vendors) and the output methods by which client applications request the data (i.e., ensure compatibility on how to get data in and out of applications)."[5]

Clinical submissions

The Clinical Data Interchange Standards Consortium, a global, multidisciplinary, non-profit organization, has established standards to support the acquisition, exchange, submission and archiving of clinical research data and metadata. CDISC standards are vendor-neutral, platform-independent and freely available from the CDISC website. The Case Report Tabulation Data Definition Specification (define.xml) draft version 2.0, the oldest data definition specification, is part of the evolution from the 1999 FDA electronic submission (eSub) guidance and electronic Common Technical Document (eCTD) documents specifying that a document describing the content and structure of included data be included in a submission. Define.xml was developed to automate the review process by generating a machine-readable data-definition document. Define.xml has standardized submissions to the Food and Drug Administration, reducing review times from over two years to several months.[6]

Archival data

A data definition specification is the foundation of metadata for scientific data archiving. The Metadata Encoding and Transmission Standard (METS) uses one principle of a DDS: consistent use of key terms to catalog digital objects for global use. The METS schema is a flexible mechanism for encoding descriptive, administrative and structural metadata for a digital library object and expressing complex links between metadata, and can provide a useful standard for the exchange of digital-library objects between repositories.[7]

A similar effort is underway to preserve complex data associated with video-game archiving. Preserving Virtual Worlds attempted to address archival-format deficiencies, citing the lack of suitable documentation for interactive fiction and games at the bit level: specifically, the absence of "representation information" needed to map raw bits into higher-level data constructs.[8] Preserving Virtual Worlds 2 is a research project expanding on initial efforts in this field.[9]

See also

References

  1. ↑ Gouin, Deborah. & Corcoran, Charmane K. (2008). Developing the MSU Enterprise Data Definition Standard. Michigan State University Web site: http://eis.msu.edu/uploads/---University%20EIS%20Working%20Committee%20Meetings/05%20August%202008/Enterprise%20Data%20Definition%20Standard%20Presentation082708.pdf
  2. ↑ Thomas, Gwen. (2008). Writing Enterprise-Quality Data Definitions: Tips for Creating Terms and Definitions. Data Governance Institute Web site: http://www.datagovernance.com/dgi_wp_writing_enterprise-quality_data_definitions.pdf
  3. ↑ International Organization for Standardization JTC1/SC32 Committee. (2004) ISO 11179-4. http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html.
  4. ↑ "Charging Data". 1 February 2011. pp. 6, 35. Archived from the original on 6 October 2013. https://web.archive.org/web/20131006172727/http://technical.openmobilealliance.org/Technical/release_program/docs/Charging_Data/V1_0-20110201-A/OMA-DDS-Charging_Data-V1_0-20110201-A.pdf. Retrieved 12 March 2014. 
  5. ↑ "Market Data Definition Language (MDDL)". December 26, 2002. Archived from the original on December 14, 2013. https://web.archive.org/web/20131214075132/http://xml.coverpages.org/mddl.html. Retrieved March 12, 2014. 
  6. ↑ "Define-XML". 2012. Archived from the original on October 4, 2013. https://web.archive.org/web/20131004232219/http://www.cdisc.org/define-xml. Retrieved March 12, 2014. 
  7. ↑ Metadata Encoding & Transmission Standard (METS) Web site from The Library of Congress- Standards https://www.loc.gov/standards/mets/
  8. ↑ “Meta Data Schema Development” (2008) Preserving Virtual Worlds website
  9. ↑ Preserving Virtual Worlds 2, Researching best practices for videogame preservation. (2012). http://pvw.illinois.edu/pvw2/



Retrieved from "https://handwiki.org/wiki/index.php?title=Data_definition_specification&oldid=3380552"