# Structure & Versioning of the Standards ## Structure ### Common and Interface-Specific Standards Some standards can be reused and are valid across multiple interfaces (stored in the common space/main page that you are looking at), others are valid only for their own respective interface (stored in the respective space of their interface linked on the left, e.g. for CRVS, specific in CRVS with SP-MIS standards). For instance, a name may always be defined in the same manner for multiple different workstreams, which would classify it as common, whereas a person could be defined slightly differently, depending on the use case (payment, CRVS, social registry, etc.), hence, it would fall under interface-specific standards and be stored in the respective interface space. ### Three Parts — Process, Data, API Each standard is split into three main parts:


Process standards serve as a proof of concept of the implemented data and API interface-specific standards. Hence, when the standards are implemented for a social protection use case—what would the process flow look like? These process flows provide examples of the most relevant implementation use cases, but are of course not exhaustive.		/files/flWUQMd6ScRtat0u9Ss3
Data	standards ensure a shared language and format for data used across diverse systems and by different organisations. They are further divided into the /pages/ommYXD1JUvuE5NxMENyV#data-object such as, e.g. a person (containing attributes like first name, sex, etc.),/pages/ommYXD1JUvuE5NxMENyV#code-directory(containing a list of possible values for an attribute like marital status) and /pages/czOVjevbpUaHNhtFdkJD(e.g. whether it is a string or a decimal and for some types, e.g. a string, how to format them, e.g. a date).	/files/gN6IJkSWcSYB3g3uNirf
API standards contain the different specifications per interface that are needed for information exchange. Valid across all interfaces, API standards deal with considerations regarding design principles, including security and versioning.		/files/mYCOPLYB5psEHRx6wQFa

Process

standards serve as a proof of concept of the implemented data and API interface-specific standards. Hence, when the standards are implemented for a social protection use case—what would the process flow look like? These process flows provide examples of the most relevant implementation use cases, but are of course not exhaustive.

Data

standards ensure a shared language and format for data used across diverse systems and by different organisations. They are further divided into the /pages/ommYXD1JUvuE5NxMENyV#data-object such as, e.g. a person (containing attributes like first name, sex, etc.),/pages/ommYXD1JUvuE5NxMENyV#code-directory(containing a list of possible values for an attribute like marital status) and /pages/czOVjevbpUaHNhtFdkJD(e.g. whether it is a string or a decimal and for some types, e.g. a string, how to format them, e.g. a date).

/files/gN6IJkSWcSYB3g3uNirf

API

standards contain the different specifications per interface that are needed for information exchange. Valid across all interfaces, API standards deal with considerations regarding design principles, including security and versioning.

/files/mYCOPLYB5psEHRx6wQFa

## Versioning The overall standards are versioned directly in the GitBook via the naming of the space. Hence, CRVS v1.0 is the first version of the CRVS with SP-MIS standards. The versioning of the APIs is explained in the [Design Principles](/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/api/design-principles.md) section. You can find all previous versions of the standards in the respective 'Previous Versions' page at the very end of each space. For instance, this is the [Previous Versions](/standards/crvs-v1.0-1/crvs/previous-versions.md) page of the CRVS with SP-MIS standards. ## --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://standards.spdci.org/standards/standards-for-interoperability-interfaces/structure-and-versioning-of-the-standards.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.