Skip to content

Data Base Task Group

Request correction

Corporate brand

Unclaimed

The Data Base Task Group was a CODASYL working group that developed influential specifications for network databases, including database definition and manipulation languages.

Last updated August 25, 2026

AI crawler reads

No AI crawler has read this profile yet.

Overview

The Data Base Task Group (DBTG) was a technical working group formed within the Conference on Data Systems Language, better known as CODASYL, during the development of early business programming standards. Its work helped establish a formal approach to organizing and manipulating databases in the era when COBOL and large-scale commercial data processing were becoming central to government and corporate computing. The group originated in 1965 as the List Processing Task Force of the COBOL Committee, which had previously been known as the Programming Language Committee. In 1967, the task force was renamed the Data Base Task Group. William Olle of RCA chaired the group. Rather than operating as a commercial software company or a consumer-facing brand, DBTG functioned as a standards and specification body whose reports were intended to guide database-system designers, programming-language developers, and users of business data-processing systems. DBTG's principal contribution was the development of specifications for a network database model and associated languages. Its proposals distinguished between a Data Definition Language (DDL), used to describe the structure of a database, and a Data Manipulation Language (DML), used to access and update records. Early proposals appeared in 1969, followed by a major report issued in April 1971. Later work was revised and extended through reports published in 1973 and 1978. These documents became associated with the DBTG database model and, more broadly, with the CODASYL database model. The model represented data through record types and sets, allowing navigational relationships among records. This approach was particularly suited to the hardware, storage systems, and programming practices of the period, when database access was often tightly integrated with application code and sequential or pointer-like navigation was common. DBTG specifications influenced commercial database products and the vocabulary used by practitioners, even though implementations varied and the reports themselves evolved over time. The group's historical importance extends beyond its specific network model. DBTG helped popularize foundational database concepts such as the schema, describing the overall logical structure of a database, and the subschema, describing an application-oriented view or portion of that structure. These terms and related distinctions continued to influence database architecture and education after relational database systems became dominant. DBTG is therefore best understood as a historical computing standards initiative rather than an active operating brand. Its work belongs to the formative period of database management, bridging COBOL-oriented business programming and the emergence of more formal database management systems. The group is chiefly remembered through its reports, the network model associated with its name, and the broader CODASYL data-management tradition.

History

The Data Base Task Group was created in 1965 within CODASYL's COBOL Committee, an organization concerned with the development and standardization of the COBOL programming language and related data-processing practices. The group was initially called the List Processing Task Force. In 1967, its name changed to Data Base Task Group, reflecting a broader focus on the structure and management of persistent business data. William Olle of RCA served as its chair. The group worked during a period when database management was moving from individually designed files toward shared, structured systems. Commercial applications commonly relied on COBOL, and organizations needed ways to describe records, connect related data, and provide controlled access to information across multiple programs. DBTG addressed these needs through a network-oriented approach rather than through the relational model that would later become predominant. Initial DBTG proposals were published in 1969. In April 1971, the group issued a report specifying both a Data Definition Language and a Data Manipulation Language. The DDL described database structures, while the DML provided mechanisms for applications to navigate and manipulate stored records. The work was subsequently revised and developed by further committees and reports, including publications associated with 1973 and 1978. The resulting approach became known as the DBTG database model or the CODASYL database model. It organized information around record types and sets, creating explicit relationships that applications could traverse. This navigational structure reflected the technical environment of its time and was used as a conceptual or implementation basis by a number of database systems. DBTG's reports did not constitute a single commercial product, and implementations could differ in detail, but the specifications provided a significant common reference point for the database industry. The group's influence was also terminological. Concepts such as schema and subschema were prominent in its description of database organization. A schema represented the broader definition of a database, whereas a subschema represented a particular application-level view. These ideas helped separate database structure from the needs of individual programs and remained relevant even as later database architectures adopted different data models and query methods. As relational database technology gained influence, the navigational CODASYL model became less central to mainstream database development. Nevertheless, DBTG's work remains important in the history of database management because it formalized a major pre-relational approach and helped connect programming-language standardization with data-management architecture. The organization is now historical rather than active, and its legacy survives mainly in technical literature, archival standards reports, and the continuing use of concepts that emerged from early database standardization.

  • 1978

    Later specification development

    [1]

    Additional reports continued the revision and development of the DBTG and CODASYL database specifications.

  • 1973

    Further CODASYL data-description development

    [1]

    Subsequent CODASYL development refined the data-description aspects of the network database approach.

  • 1971

    Publication of the major DBTG report

    [2]

    The April 1971 report described specifications for a Data Definition Language and a Data Manipulation Language, forming a central reference for the DBTG database model.

  • 1969

    Initial DBTG proposals

    [1]

    The group published its first proposals for a standardized network-oriented database approach.

  • 1967

    Renamed Data Base Task Group

    [1]

    The List Processing Task Force adopted the name Data Base Task Group, signaling its focus on database organization and management.

  • 1965

    Formation as the List Processing Task Force

    [1]

    CODASYL's COBOL Committee established the group as the List Processing Task Force to address issues related to structured data processing.

Products and positioning

A historical computing standards group focused on formalizing network database structures, database description, and data manipulation for COBOL-era commercial data processing.

  • Database model · 1969

    DBTG database model

    A network database model associated with the group's reports. It represented information through record types and sets, allowing applications to navigate predefined relationships among records. The model was designed for the business data-processing environment of the COBOL era and became one of the principal pre-relational approaches to database organization.

  • Database definition language · 1971

    DBTG Data Definition Language

    A specification for describing database structures within the DBTG approach. It addressed the definition of records, relationships, and other elements needed to establish a database schema. The language was part of the broader effort to separate database description from the application programs that used stored data.

  • Data manipulation language · 1971

    DBTG Data Manipulation Language

    A specification for application access to and manipulation of data in a DBTG-style network database. Its navigational orientation reflected the implementation practices of the period, in which programs followed defined relationships among records rather than issuing the declarative relational queries common in later systems.

Sources3 sources

Cite this profile: Cite the canonical profile. /brand-wiki/data-base-task-group · Editorial policy · How profiles are compiled