<commit_before># CVC Language reference
## Inclusions

The current version of Cascaded Vorbis Comments supports the following inclusion
directives:

### The @INCLUDE inclusion directive
This directive might be used to include any other CVC file. The file may be
specified with its absolute path, or with a path relative to the including CVC
file. The `@INCLUDE` directive is used to include arbitrary CVC files, which do
not belong to a datastore.

Example: `@INCLUDE=../common`

### The @CHOIR inclusion directive
This directive allows to include a CVC file from the `CFG_IncludePath_CHOIR`
directory. Those files describe vocal ensembles. They are named after the
international name of the ensemble, without accents nor diacritics.

Example: `@CHOIR=RIAS Chamber Choir`

### The @COMPOSER inclusion directive
This directive allows to include a CVC file from the `CFG_IncludePath_COMPOSER`
directory. Those files describe music composers. They are named after the
international name of the composer, sorted form, without accents or diacritics.

Example: `@COMPOSER=Bach, <NAME>`

### The @CONDUCTOR inclusion directive
This directive allows to include a CVC file from the
`CFG_IncludePath_CONDUCTOR` directory. Those files describe music conductors.
They are named after the international name of the conductor, sorted form,
without accents or diacritics.

Example: `@CONDUCTOR=Barenboim, Daniel`

### The @INSTRUMENT inclusion directive
This directive allows to include a CVC file from the
`CFG_IncludePath_INSTRUMENT` directory. Those files describe music instruments.
They are named after the english name of the instrument.

Example: `@INSTRUMENT=Viola`

### The @LABEL inclusion directive
This directive allows to include a CVC file from the `CFG_IncludePath_LABEL`
directory. Those files describe music labels. They are named after their
international name, without accents nor diacritics. Using inclusions for labels
allows to easily update music files when labels are sold, bought, renamed or
merged without overwriting the original label name.

Example: `@LABEL=Deutsche Grammophon`

### The @MUSICALERA inclusion directive
This directive allows to include a CVC file from the
`CFG_IncludePath_MUSICALERA` directory. Those files describe musical eras.
They are named after their english name. Note that CVC names musical eras with
nouns, not adjectives.

Example: `@MUSICALERA=Romantism`

### The @ORCHESTRA inclusion directive
This directive allows to include a CVC file from the
`CFG_IncludePath_ORCHESTRA` directory. Those files describe instrumental
ensembles. They are named after their international name, without accents
or diacritics.

Example: `@ORCHESTRA=<NAME>`

### The @SLICE inclusion directive
This directive allows to include a CVC file from the `CFG_IncludePath_SLICE`
directory. Those files describe parts of music works. Music works are usually<commit_msg>Updated the documentation.<commit_after># CVC Language reference


## Inclusion directives

The current version of Cascaded Vorbis Comments supports the following inclusion
directives:

### The @INCLUDE inclusion directive
This directive might be used to include any other CVC file. The file may be
specified with its absolute path, or with a path relative to the including CVC
file. The `@INCLUDE` directive is used to include arbitrary CVC files, which do
not belong to a datastore.

Example: `@INCLUDE=../common`

### The @CHOIR inclusion directive
This directive allows to include a CVC file from the `CFG_IncludePath_CHOIR`
directory. Those files describe vocal ensembles. They are named after the
international name of the ensemble, without accents nor diacritics.

Example: `@CHOIR=RIAS Chamber Choir`

### The @COMPOSER inclusion directive
This directive allows to include a CVC file from the `CFG_IncludePath_COMPOSER`
directory. Those files describe music composers. They are named after the
international name of the composer, sorted form, without accents or diacritics.

Example: `@COMPOSER=Bach, <NAME>`

### The @CONDUCTOR inclusion directive
This directive allows to include a CVC file from the
`CFG_IncludePath_CONDUCTOR` directory. Those files describe music conductors.
They are named after the international name of the conductor, sorted form,
without accents or diacritics.

Example: `@CONDUCTOR=Barenboim, Daniel`

### The @INSTRUMENT inclusion directive
This directive allows to include a CVC file from the
`CFG_IncludePath_INSTRUMENT` directory. Those files describe music instruments.
They are named after the english name of the instrument.

Example: `@INSTRUMENT=Viola`

### The @LABEL inclusion directive
This directive allows to include a CVC file from the `CFG_IncludePath_LABEL`
directory. Those files describe music labels. They are named after their
international name, without accents nor diacritics. Using inclusions for labels
allows to easily update music files when labels are sold, bought, renamed or
merged without overwriting the original label name.

Example: `@LABEL=<NAME>`

### The @MEDIUMTYPE inclusion directive
This directive allows to include a CVC file from the
`CFG_IncludePath_MEDIUMTYPE` directory. Those files describe types of audio
media.

Example: `@MEDIUMTYPE=CDDA`

### The @MUSICALERA inclusion directive
This directive allows to include a CVC file from the
`CFG_IncludePath_MUSICALERA` directory. Those files describe musical eras.
They are named after their english name. Note that CVC names musical eras with
nouns, not adjectives.

Example: `@MUSICALERA=Romantism`

### The @ORCHESTRA inclusion directive
This directive allows to include a CVC file from the
`CFG_IncludePath_ORCHESTRA` directory. Those files describe instrumental
ensembles. They are named after their international name, without accents
or diacritics.

Example: `@ORCHESTRA=Berliner Philharmoniker`

### The @RELEASECHANNEL inclusion directive
This directive allows to include a CVC file from the
`CFG_IncludePath_RELEASECHANNEL` directory. Those files describe channels
of diffusion for audio releases.

Example: `@RELEASECHANNEL=Retail`

### The @RELEASESOURCE inclusion directive
This directive allows to include a CVC file from the
`CFG_IncludePath_RELEASESOURCE` directory. Those files describe the source
of the audio material included in a release.

Example: `@RELEASESOURCE=Live recording`


### The @SLICE inclusion directive
This directive allows to include a CVC file from the `CFG_IncludePath_SLICE`
directory. Those files describe parts of music works. Music works are usually
{'fraction_non_alphanumeric': 0.05257494235203689, 'fraction_numerical': 0.0, 'mean_word_length': 5.591691995947315, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4166339', 'n_tokens_mistral': 1764, 'n_tokens_neox': 1668, 'n_words': 850}