The Standards Profile (NTV-1) provides a list of standards that guide and constrain the implementation of systems as defined in the various subviews of the NATO System View.

In HOPEX NAF, a standard is a specific independent notion that can be created in order to establish a list. The standard notion encompasses all the technical and non technical items that are recommended by the company for designing the architecture.

A standard can be linked to the definition of repository items such as applications, databases, artifacts, resource architectures and communication protocols. This link, even though non mandatory, is useful in helping to provide a more accurate definition of the standard.

The sections below indicate how standards can be described. For more information on the metamodel behind the standard notion, see NTV-1 Standards Profile and NTV-2 Standards Forecast.

A standard can be decomposed into sub-parts. Each part is called a Standard Component. A standard component can reference another existing standard, in which case the name of the component can be automatically created from the name of the standard on which it is based (this is not mandatory and the user can rename the component).

For example, the DNS standard is defined from different smaller standards:

A standard is approved/created by an organization. For example, HTML is created by the W3C and UML is created by the OMG.

Declaring a list of standards can be useful, however, comparing this list to the standard that is used to implement a resource architecture is more beneficial. This comparison can be made if the components of the architecture detail the standards on which they are based. To make the comparison, a special link exists between architecture items and standards.