David Bernard

remove of `subject.type`

1

## Why should we remove `subject.type`? `subject.type` seems useless, and to create more trouble (for SDK creator, user) that is solve: - the content is defined by `context.type`, `subject.type` alone...

type of `url` fields is inconsistent into jsonschema

2

In the JSON schema, the type and format of some URL fields (`subject.content.url`, `subject.content.wiewUrl`) is not consistent. Is this expected? And sometimes they are required with "minLength: 1" and sometimes...

value of $id should be aligned with `context.type`: - `context.type` follow the format: `dev.cdevents.{{subject}}.{{predicate}}.{{subject_predicate_version}}` - `$id` should follow the format: `https://cdevents.dev/{{spec_version}}/schema/{{subject}}-{{predicate}}-event` ``` "$id": "https://cdevents.dev/0.4.0-draft/schema/pipeline-run-queued-event", "properties": { "context": { "properties": {...

Use the same way to name files in examples & schema, both with _ as separator (snake_case format) : `{{subject}}_{{predicate}}.json` ## Questions 1. Why not add a number (2 digit)...

chore: add load test to example-axum-otlp to monitor memory leak

1

try to reproduce a possible memory leak see #191

I propose to rename the field `ticketURI` used in incident, several options (depends of the consistency target): 1. `ticketUrl` to be consistent with other 'uri' field like `url` and `viewUrl`...

proposal: merge `subject.source` and `subject.id` into a global reference / uri / id

2

# Problem Some points about `subject.source` and `subject.id` trouble me (in the usage): - The `source` of a subject is optional, and if not set, it should default to the...

[proposal] remove the `build` subject (for 0.6?)

1

following #109 and meeting of 2025-08-19 `build` could be removed for 0.5; it's a duplicate of `pipelineRun` or `taskRun`. Migration path (from 0.4): It is recommended to convert `build` into...

Added dioxus-iconify CLI tool entry with details.