> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/snomed-international-documents/snomed-ct-glossary/d/dnf.md).

# dnf

## DNF

**An abbreviation for the now obsolete "distribution normal form" replaced by necessary normal form.**

## necessary normal form

An inferred view of a concept definition that includes only defining relationships that are necessarily true.

#### Notes

* The necessary normal form is designed to represent an inferred view derived from the enhanced concept definitions in a form that can be distributed in the relationship file. Although the enhanced features cannot be fully represented within the structure of the relationship file, the necessary normal form provides a view of the results of classifying data that is accessible to those without access to description logic tools.

#### Change Notices

* Changes introduced in the July 2019 release of the International Edition, enhanced the ability of SNOMED CT to support more advanced description logic. These changes allow the stated view of concept definitions to use axioms represent using the OWL Functional Syntax.

## Alternatives

* **NNF**

## Historical Reference

* Distribution normal form - obsolete-definition

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SNOMED+Glossary&#x26;entry.670899847=dnf" class="button primary">Provide Feedback</a>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snomed.org/snomed-international-documents/snomed-ct-glossary/d/dnf.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.