Ericjenn srpwg wg1

safety-related-profile/README.md

@@ -2,9 +2,7 @@
 
 # ONNX Safety-Related Profile Working Group (WG)
 
-This repository is where ONNX Safety-Related Profile WG will capture various artifacts and deliverables. 
-
-The purpose of this WG is to elaborate an ONNX profile dedicated to safety-related systems.
+The purpose of this WG is to elaborate an ONNX profile dedicated to "safety-related" systems.
 
 An ONNX model is the representation of an ML/AI model to be implemented. In other words, it is the specification for the implementation activity. 
 The model may be either interpreted by a tool or translated into some lower level equivalent representation (e.g., some source code) by a tool or a human.  In both cases, to be able to interpret the model according to the intent of its designer, its syntax and semantics must be clear and non-ambiguous. 
@@ -13,29 +11,39 @@ This is for instance the case in the aeronautical domain for which evidences sha
 We consider that the current ONNX standard does not fully satisfy these requirements and that there is a need (i) to clarify the industrial needs in that matter, (ii) to identify and address the weaknesses of the current standard in a systematic manner in order to produce an "safety-related ONNX profile" that would to fulfil these needs.
 We also consider that these needs are specific and that the proposed changes and clarifications of the syntax, semantics, and documentation shall not prevent the use of ONNX in domains where constraints are relaxed. For instance, introducing restrictions on the parameters values for operators of the safety-related profile must not affect the usage of the same operators out of the profile. 
 
-## Working Group Status
+# Contents
+
+The main elements of this repository are:
+- [Slides of the Kick-Off Meeting](./meetings/general/2024-09-25%20-%20KOM/2024-09-25%20-%20SONNX%20KOM.pdf)
+- [Recent presentation of the projects results](./meetings/Other_meetings/SONNX%20-%20WG114-%20oct-2025.pdf)
+- [Minutes of the WG meetings](./meetings/minutes.md)
+- Deliverables (draft)
+  - [Industrial needs](./deliverables/needs/needs.md) (What are the needs of the industrial partners?)
+  - [Use cases](./deliverables/scope/scope.md) (What are the first models to be implemented using SONNX?)
+  - [Requirements](./deliverables/reqs/reqs.md) (How do the needs translate to constraints on the SONNX profile?)
+  - [Issues](./deliverables/issues/issues.md) (What are the first issues identified for the usage of ONNX in a safety-related system?) (obsolete)
+  - [Informal specification of operators](./sonnx/ops/spec/informal/)
+  - [Formal specification of operators](./sonnx/ops/spec/formal/)
+    Formal specification of operators is done using the [Why3](https://www.why3.org/).
+  - [Formal specification of graphs](./sonnx/graph/README.md) (tbc)
+Note that this is a **work in progress**. 
+
+
+# Working Group Status
 **ACTIVE**
 
-# Slack channel
-Please sign up at https://slack.lfai.foundation/ and join [onnx-safety-related-profile-wg](https://app.slack.com/client/TPUCV58TG/CPS6Y3N21) channel.
 
 # WG Lead(s)
 
-* Eric JENN (IRT Saint-Exupery) and Jean SOUYRIS (Airbus) (July 22, 2024 - Current)
-
-# Logistics
+* Eric JENN (IRT Saint-Exupery, France) and Jean SOUYRIS (Airbus, France) (July 22, 2024 - Current)
 
-* WG leads will drive the meeting.
-* Meeting annoucement will be posted in our Slack channel: https://lfaifoundation.slack.com/archives/C02AANGFBJB
-* Feedbacks and topic request are welcome by all.
-* Documents and artifacts: https://github.com/onnx/working-groups/tree/main/safety-related-profile
 
 # WG Meeting Info
 
-* Meeting (to be defined).
-* TEAMS Meeting link: (to be defined)
-* Meeting ID: (to be defined)
-
-# Meeting notes
+* Working group meetings take place every other Wednesday, 4 p.m. to 6 p.m. (Paris time)
+* To join, please subscribe to the SONNX mailing list (see below); we will come back to you.
+* The meeting notes can be found [here](./meetings/minutes.md). 
 
-The meeting notes can be found [here](https://github.com/onnx/working-groups/tree/main/safety-related-profile/meetings)
+# Mailing list
+* To subscribe to the mailing list, send an email to onnx-sonnx-workgroup+subscribe@lists.lfaidata.foundation
+

safety-related-profile/attic/operator_spec_sub_wg/2025-11-07-work_session.md

@@ -0,0 +1,38 @@
+### Notations and other conventions to be added to the *guidelines*
+- Change  the notation of variadic arguments from $X_i$ to $Xi$ .
+- All elements are indexed from $0$ to $L$ , L being the index of the **L**ast element.
+- In the spec of all operator, add an hyperlink to the ONNX operator  
+- To designate a specific element of a tensor $T$, use $T[i,j,..]$, i.e., square bracket rather than parentheses.
+- Comply with the ONNX naming conventions: $add$ becomes $Add$.
+- Use ONNX type lists (without the "tensor()) 
+- Provide a template of the informal spec that will serve as a basis for the writing of new operators (besides the *guidelines*)
+- [ ] (all) Modify the already specified operators to ensure compliance with these new conventions.
+
+### Review of the $\text{Slice}$ operator
+- See replies to Ricardo and Jõao's questions in [joao-ricardo-doubts.md](https://github.com/ericjenn/working-groups/blob/ericjenn-srpwg-wg1/safety-related-profile/sonnx/ops/spec/informal/slice/reviews/joao-ricardo-doubts.md)
+- Those questions raised very interesting discussions about empty tensors
+- [ ] (Eric) Create a side note about "empty tensors" (To be placed in "doc"). [project::[[SONNX]]] 
+- Ensure that all existing operators (and pseudo-op such as $bc$) handles tensors with null  dimensions correctly. (To be added in the guidelines.)
+
+### Review of the $\text{Clip}$ operator
+- Jõao and Ricardo have questions about the handling of NaN.
+	- The spec. should only refer to  $\min(M, \max(X[i],L))$  and define what $\min(x,NaN)$ and $\max(x,NaN)$ means.
+	- Consider other special values (+Inf, -Inf, $0^+$ +, $0^-$ )
+	- Check what the IEEE  says about min and max with these values. 
+- [ ] (Mariem) Give R&J a pointer to Why3 where NaN are handled.
+- [ ] (Mariem) Give R&J a feedback ont the formal spec (in particular: recall a few principles to be followed).
+
+### Review of $\text{Max}$ and broadcasting
+- See Eric's comments [here](https://github.com/ericjenn/working-groups/blob/ericjenn-srpwg-wg1/safety-related-profile/sonnx/ops/spec/informal/max/reviews/max-ejn.md)
+- [ ] (Jean-loup) Separate the spec broadcasting and the max operator 
+	- Broadcasting is specified as $(Z1,Z2,ZL)=\text{bc}(X1,X2,...,XL)$  
+	- The spec is to be placed in "common"
+	- "Properties" will be useful to support the verification (formal, test) activities but they have to be removed from the informal spec.
+    	- They should be specified in the most simple way so has to be traceable to some simple implementation using primitive operations (loops, simple mathematical operations). In particular, we should stick to two-step process : (i) construction of the broadcasted tensors and (ii) computation of the maxes on those tensors must be explicit.
+
+### Other topics
+- [ ] (Eric) Provide explanations about the new way to manage modifications (using Pull Requests).
+- [ ] Check the display problem with LaTeX formulae in Markdown (see $\text{Add}$)
+- [ ] (Eric) During next meeting ask participants if they know other issues similar to those raised by empty tensors.
+
+