Replies: 1 comment
-
|
@qor-lb @arsibo @AThums please discuss inside the architecture community |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Eclipse S-CORE community,
URML (urml.dev) is a small, Apache-2.0 language for describing robot intent: it validates a request against a capability manifest and a safety envelope, then dispatches to the substrate below. S-CORE is the open, service-oriented, AUTOSAR-Adaptive-aligned SDV core URML's AUTOSAR work targets, so let me be upfront about the layer: URML sits above S-CORE as a typed, validated intent vocabulary, not as a competing platform.
Nothing here asks S-CORE to adopt, host, or maintain anything. This is a request for comment.
The mapping I shipped (urml.dev, RFC-0019):
Two real questions: (1) Is call_program plus an ara::com id triple the right granularity to name an S-CORE service method from an outside intent layer, or is a different handle more natural in your model? (2) Does mapping Execution-Management timing onto a descriptive realtime block (period + watchdog, no enforcement claim) read as honest from your side?
Full write-up: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0387-eclipse-score-outreach.md
Thanks for S-CORE; an open, safety-minded SDV core built in the open is a genuinely good thing for the field.
Ido Yahalomi (URML, greenvh@gmail.com)
AI-assisted prose, maintainer-reviewed before posting (see VIBE.md). Human-only correspondence available on request.
Beta Was this translation helpful? Give feedback.
All reactions