Skip to content

[RFC] Consistent naming to describe DTPR, its elements and concept #235

@pichot

Description

@pichot

Problem

In deploying, discussing, and building upon DTPR over the past several years, we've found that there are concepts that are not explicitly named in the standard. This muddies discussions, and makes explaining what we mean to ourselves and to others difficult.

Proposal

Thus, we propose to name a few concepts in the standard to make discussions easier across our team and others.

Element

A DTPR Element is the primary structure within DTPR. It includes an Icon, Name, and Description. A user can add an Additional Description when deploying it. Elements are translated into all the languages supported by DTPR.

Image

In a datachain, the ordering of elements is determined by the deploying organization. In other words, elements can be placed in any order within their category.

Category

A DTPR Category groups a number of DTPR elements together. Categories are translated into all the languages supported by DTPR.

A category has a Name and Question that frames the category as a user question. For example:

Name: Accountable
Question: Who is accountable for this technology?

Depending on the datachain type, categories are specifically ordered based on the standard. For example, the DTPR Sensor Datachain orders provides these categories in this order:

  • Accountable
  • Purpose
  • Technology
  • Data Type
  • Processing
  • Access
  • Storage

Datachain

A DTPR datachain is a structured, ordered list of elements, ordered by their respective categories. The first version of the datachain was focused on describing data collection in public space, but future datachains will be able to describe systems such as AI-models or algorithms (#228).

An example of a Sensor Datachain on the left, with the ordered categories explained on the right:

Image

Honeycomb

The top-most DTPR element within the three hexagon-based DTPR categories can be brought together into a honeycomb. The honeycomb acts a the most succinct, high-level summary of a datachain. It distills into 3 icons answers to the most common questions people ask when encountering the described system. In the case of a sensor datachain the questions are:

  • Who is primarily responsible for the deployment of this data-collecting technology?
  • What purpose does this technology serve?
  • What is the primary technology used in the data-collection?
Image

Taxonomy

Given this definition:

Taxonomy is the practice and science of classification. It involves organizing and categorizing objects, concepts, or entities based on a systematic structure, typically in a hierarchical manner.

DTPR is a taxonomy for describing and classifying data collecting and processing technologies. The word taxonomy, when referring to DTPR, refers to the collection of all DTPR elements, categories, and the way they are organized in a hierarchical relationship.

Visual Language

Given this definition:

Visual language refers to a system of communication using visual elements rather than words. It relies on images, symbols, colors, shapes, and design principles to convey meaning, evoke emotions, or communicate ideas effectively.

DTPR is a visual language, insomuch as it attempts to communicate the purpose and use of technology using symbols and color. The phrase visual language, when referring to DTPR, refers to the visual elements of its taxonomy, namely the icons of the DTPR elements and the way they are presented together, both in the datachain and the honeycomb. In other words, the visual language of DTPR is the way the taxonomy is rendered in symbols and colors, but does not encompass the entirety of the taxonomy, as it does not include the titles or descriptions of elements, for example.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Request for CommentLarger proposal that goes beyond individual changes to DTPR elements

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions