@@ -18,7 +18,6 @@ requirements and recommendations.
1818 - [ Prerequisites] ( #prerequisites )
1919 - [ 1. Modify the YAML model] ( #1-modify-the-yaml-model )
2020 - [ Code structure] ( #code-structure )
21- - [ Schema files] ( #schema-files )
2221 - [ 2. Update the markdown files] ( #2-update-the-markdown-files )
2322 - [ Hugo frontmatter] ( #hugo-frontmatter )
2423 - [ 3. Check new convention] ( #3-check-new-convention )
@@ -36,6 +35,7 @@ requirements and recommendations.
3635 - [ Update the tables of content] ( #update-the-tables-of-content )
3736 - [ Markdown link check] ( #markdown-link-check )
3837 - [ Yamllint check] ( #yamllint-check )
38+ - [ Schema files] ( #schema-files )
3939- [ Merging existing ECS conventions] ( #merging-existing-ecs-conventions )
4040
4141<!-- tocstop -->
@@ -57,8 +57,7 @@ key, but non-obvious, aspects:
5757- All descriptions, normative language are defined in the ` docs/ ` directory.
5858- All changes to existing attributes, metrics, etc. MUST be allowed as
5959 per our [ stability guarantees] [ stability guarantees ] and
60- defined in a schema file. As part of any contribution, you should
61- include attribute changes defined in the ` schema-next.yaml ` file.
60+ defined in a schema file.
6261- Links to the specification repository MUST point to a tag and ** not** to the ` main ` branch.
6362 The tag version MUST match with the one defined in [ README] ( README.md ) .
6463
@@ -164,21 +163,6 @@ are defined in `/model/aws/lambda-spans.yaml` and `/model/aws/sdk-spans.yaml` fi
164163Deprecated conventions should be placed under ` /model/{root-namespace}/deprecated `
165164folder.
166165
167- #### Schema files
168-
169- When making changes to existing semantic conventions (attributes, metrics, etc)
170- you MUST also update the ` schema-next.yaml ` file with the changes.
171-
172- For details, please read
173- [ the schema specification] ( https://opentelemetry.io/docs/specs/otel/schemas/ ) .
174-
175- You can also take examples from past changes inside the ` schemas ` folder.
176-
177- > [ !WARNING]
178- >
179- > DO NOT add your changes to files inside the ` schemas ` folder. Always add your
180- > changes to the ` schema-next.yaml ` file.
181-
182166### 2. Update the markdown files
183167
184168After updating the YAML file(s), you need to update
@@ -434,6 +418,23 @@ If it is the first time to run this command, install `yamllint` first:
434418make install-yamllint
435419```
436420
421+ ## Schema files
422+
423+ > [ !WARNING]
424+ >
425+ > DO NOT add your changes to files inside the ` schemas ` folder. These files are
426+ > generated automatically by the release scripts and can't be updated after
427+ > the corresponding version is released.
428+
429+ Release script uses the following command to generate new schema file:
430+
431+ ``` bash
432+ make generate-schema-next NEXT_SEMCONV_VERSION={next version}
433+ ```
434+
435+ For details, please read
436+ [ the schema specification] ( https://opentelemetry.io/docs/specs/otel/schemas/ ) .
437+
437438## Merging existing ECS conventions
438439
439440The Elastic Common Schema (ECS) is being merged into OpenTelemetry Semantic
0 commit comments