fix cdavernas comments serverlessworkflow#926 (review)

Signed-off-by: Jean-Baptiste Bianchi <[email protected]>

Author: JBBianchi

dsl-reference.md

@@ -40,9 +40,9 @@
   + [Extension](#extension)
   + [Error](#error)
     - [Standard Error Types](#standard-error-types)
-  + [Event](#event)
   + [Event Consumption Strategy](#event-consumption-strategy)
   + [Event Filter](#event-filter)
+  + [Event Properties](#event-properties)
   + [Retry](#retry)
   + [Input](#input)
   + [Output](#output)
@@ -230,9 +230,9 @@ The Serverless Workflow DSL defines a list of [tasks](#task) that **must be** su
 - [Call](#call), used to call services and/or functions.
 - [Do](#do), used to define one or more subtasks to perform in sequence.
 - [Fork](#fork), used to define one or more subtasks to perform concurrently.
-- [Emit](#emit), used to emit [events](#event).
+- [Emit](#emit), used to emit [events](#event-properties).
 - [For](#for), used to iterate over a collection of items, and conditionally perform a task for each of them.
-- [Listen](#listen), used to listen for an [event](#event) or more.
+- [Listen](#listen), used to listen for an [event](#event-properties) or more.
 - [Raise](#raise), used to raise an [error](#error) and potentially fault the [workflow](#workflow).
 - [Run](#run), used to run a [container](#container), a [script](#script) or event a [shell](#shell) command. 
 - [Switch](#switch), used to dynamically select and execute one of multiple alternative paths based on specified conditions
@@ -495,7 +495,7 @@ Allows workflows to publish events to event brokers or messaging systems, facili
 
 | Name | Type | Required | Description |
 |:--|:---:|:---:|:---|
-| emit.event | [`event`](#event) | `yes` | Defines the event to emit. |
+| emit.event | [`eventProperties`](#event-properties) | `yes` | Defines the event to emit. |
 
 ##### Examples
 
@@ -1391,7 +1391,7 @@ Represents the configuration of an event consumption strategy.
 | any | [`eventFilter[]`](#event-filter) | `no` | Configures the workflow to wait for any of the defined events before resuming execution.<br>*Required if `all` and `one` have not been set.* |
 | one | [`eventFilter`](#event-filter) | `no` | Configures the workflow to wait for the defined event before resuming execution.<br>*Required if `all` and `any` have not been set.* |
 
-### Event
+### Event Properties
 
 An event object typically includes details such as the event type, source, timestamp, and unique identifier, along with any relevant data payload. The [Cloud Events specification](https://cloudevents.io/), favored by Serveless Workflow, standardizes this structure to ensure interoperability across different systems and services.
 
@@ -1404,11 +1404,14 @@ An event object typically includes details such as the event type, source, times
 | type | `string` | `no` | Describes the type of event related to the originating occurrence. `source` + `id` is unique for each distinct event.<br>*Required when emitting an event using `emit.event.with`.* |
 | time | `string` | `no` | The timestamp of when the occurrence happened. |
 | subject | `string` | `no` | Describes the subject of the event in the context of the event producer. |
-| datacontenttype | `string` | `no` | Content type of `data` value. If omitted, it implies the `data` is a JSON value confiorming to the "application/json" media type. |
+| datacontenttype | `string` | `no` | Content type of `data` value. If omitted, it implies the `data` is a JSON value conforming to the "application/json" media type. |
 | dataschema | `string` | `no` | An URI that identifies the schema that `data` adheres to. |
 | data | `object` | `no` | The event payload. |
 
-Additional properties can be supplied.
+*Additional properties can be supplied.*
+
+*When used in an [`eventFilter`](#event-filter), at least one property must be supplied.*
+
 
 ### Event Filter
 
@@ -1418,7 +1421,7 @@ An event filter is a mechanism used to selectively process or handle events base
 
 | Property | Type | Required | Description |
 |----------|:----:|:--------:|-------------|
-| with | [`event`](#event) | `yes` | A name/value mapping of the attributes filtered events must define. Supports both regular expressions and runtime expressions.  |
+| with | [`eventProperties`](#event-properties) | `yes` | A name/value mapping of the attributes filtered events must define. Supports both regular expressions and runtime expressions.  |
 | correlate | [`map[string, correlation]`](#correlation) | `no` | A name/definition mapping of the correlations to attempt when filtering events. |
 
 ### Correlation

schema/workflow.yaml

@@ -357,7 +357,7 @@ $defs:
             type: object
             properties:
               with:
-                $ref: '#/$defs/event'
+                $ref: '#/$defs/eventProperties'
                 required: [ source, type ]
             additionalProperties: true
         required: [ event ]
@@ -781,7 +781,7 @@ $defs:
         $ref: '#/$defs/referenceableAuthenticationPolicy'
         description: The authentication policy to use.
     required: [ uri ]
-  event:
+  eventProperties:
     type: object
     properties:
       id:
@@ -837,7 +837,7 @@ $defs:
     properties:
       with:
         title: WithEvent
-        $ref: '#/$defs/event'
+        $ref: '#/$defs/eventProperties'
         minProperties: 1
         description: An event filter is a mechanism used to selectively process or handle events based on predefined criteria, such as event type, source, or specific attributes.
       correlate: