# Form — v2.0

Describes a form

## Files

| File | Purpose |
|---|---|
| [https://schema.nfh.global/Form/v2.0/attributes.yaml](https://schema.nfh.global/Form/v2.0/attributes.yaml) | OpenAPI schema envelope (versioned path) |
| [https://schema.nfh.global/Form/v2.0/attributes.jsonschema.yaml](https://schema.nfh.global/Form/v2.0/attributes.jsonschema.yaml) | JSON Schema document (versioned path) |
| [https://schema.nfh.global/Form/v2.0/context.jsonld](https://schema.nfh.global/Form/v2.0/context.jsonld) | JSON-LD context (versioned path) |
| [https://schema.nfh.global/Form/v2.0/vocab.jsonld](https://schema.nfh.global/Form/v2.0/vocab.jsonld) | RDF vocabulary (versioned path) |

## Properties

| Property | Required | Type | Description |
|---|---|---|---|
| `@context` | yes | string | - |
| `@type` | yes | string | - |
| `url` | no | string | The URL from where the form can be fetched. The content fetched from the url must be processed as per the mime_type specified in this object. Once fetched, the rendering platform can choosed to render the form as-is as an embeddable element; or process it further to blend with the theme of the application. In case the interface is non-visual, the the render can process the form data and reproduce it as per the standard specified in the form. |
| `data` | no | object | The form submission data |
| `mime_type` | no | string | This field indicates the nature and format of the form received by querying the url. MIME types are defined and standardized in IETF's RFC 6838. |
| `submission_id` | no | string | - |