Writing needs in MyST

The MyST forms of the specimens on Writing needs, each rendered live by this page’s own Markdown parser. Their needs carry ids of their own, because a need id must be unique in the project.

Need parts

A need with two parts

```{req} Report header
:id: EX_REQ_MYST_EXPORT_HEADER
:status: open

The file {need_part}`(columns)starts with a row naming the columns`
and {np}`(encoding)is encoded as UTF-8`.
```
Requirement: Report header EX_REQ_MYST_EXPORT_HEADER
status: open

The file starts with a row naming the columns columns and is encoded as UTF-8 encoding.

Card options

Card options

```{spec} Quote fields that hold a comma
:id: EX_SPEC_MYST_EXPORT_QUOTING
:status: open
:links: EX_REQ_MYST_EXPORT
:collapse: true

A field that holds a comma is written in double quotes.
```

```{spec} Name the file after the report
:id: EX_SPEC_MYST_EXPORT_FILENAME
:status: open
:links: EX_REQ_MYST_EXPORT
:layout: complete
:style: green_border

The file takes the report's title as its name.
```
Specification: Quote fields that hold a comma EX_SPEC_MYST_EXPORT_QUOTING
status: open
links outgoing: EX_REQ_MYST_EXPORT

A field that holds a comma is written in double quotes.

Name the file after the report
Specification
status: open
links outgoing: EX_REQ_MYST_EXPORT

The file takes the report’s title as its name.