[FEO Weekly 2025-04-29] #1011

4og · 2025-04-29T11:49:38Z

4og
Apr 29, 2025
Collaborator

Safe JSON Parser feature request: Feature Request: JSON Parser #822
- to be part of S-CORE 0.5. FEO needs JSON parser to read configuration files and the activity chain files. It must have a Rust implementation.
- YAML parser has never been discussed.
Code drop in inc_feo repo: FEO Prototype improvements inc_feo#39
Status update FEO FT (view)
- @LittleHuba will discuss the snapshotting feature in Communication CFT. The goal of the input service activity in FEO is just to freeze the inputs (by holding the sample pointer). With that the activities in the activity chain are bound to read the same data (i.e. the data don't change during the activity run).
- Each data slot in mw::com has a a monotonic incremental counter ordering the messages. The mw::com doesn't assume that two communication parties have the same time base.
- https://github.com/eclipse-score/inc_feo/issues/23 Follow up meeting is needed to define the scope for 0.5 @ramceb to schedule the follow up and invite the participants from the first meeting https://github.com/orgs/eclipse-score/discussions/944
- A lot of issues are not linked with epics. @ramceb and @4og will address this.