Hi Shuah, I don't have write access to the document, so I'll put my comments here. I find that initial strategy documents often just contain solutions and my first reflex was to consider the document

+1 I could quibble... but basically I agree wholeheartedly.

Hi Shuah, TLDR: The technical strategy document discussions mix the desired outcomes, with the primary and subordinate goals of the various ELISA activities and that makes it unnecessarily hard to ach

For those who find the text in the mindmap too small, - I've managed to prepare the text corresponding to the upper half - I uploaded the (working copy of the) Freeplane file to the website [1] Cheers

Hi Lukas, You've really hit a nerve! I don't think I've seen a longer thread in any ELISA mailing list... with so many people who are so _serious_ about having _fun_. Wow. Unfortunately, it's all been

Hi Lukas, Hmmm... as we would say in German "Everything's OK, Don't worry". My comments were directed at the technical strategy, and therefore at the TSC, and were not in any way a suggestion how the

Hi Sanjay: Actually, you can subscribe to the calendar (and any other WG calendar) and then you'll be automatically kept up-to-date on the schedule. It's under the Tech Community website[1], which, at

Hi Min, I like the new design. It's quite improvement over the somewhat stodgy old design. But.... in the old format, when you clicked in the upper bar (About, Membership, Community, News&Events... )

Hi Shuah, If we have some spare time, we might waste a couple of thought-cycles on the fate of the white paper... Cheers John

Hi Paul, I'd like to participate / contribute / review. In the context of yesterday's sync telco, I was going to say that you missed Denglish, where things can be as clear as dumpling broth. (==> a li

Hi, Jochen brought this topic up in the sync call yesterday, but somehow or other I didn't get around to addressing it. It came up in our Automotive WG working session today, so I'm throwing it out to

Hi Shuah, Now that some safety people are busy like beavers reading 800 page 15-year old books to figure out the Linux internals, maybe it's time to challenge the Linux people as well. In the last cou

Search for good MBD / MBSE resources for safety applications and standards interpretation. - What information is needed? - Who knows what? - Does anybody have a recommendation? - Do we need to pick be

Hi Paul Great start. I'd have started with Shakespeare too! The point for me, as I said in the last Sync Telco, was the issue is not just the nomenclature. It's understanding what comprises each of th

Mea Culpa, I've always been guilty of seeing the forest and forgetting a couple of trees...

Hi Chris The referenced definition is great - in-depth, with a discussion of the different perceptions of the term "architecture" and then again not too long. It addresses my concern that the definiti

Hi At least I now have a framework to explain what's bugging me (Thanks Chris). To Elana's question: Referring to the conceptual model of an architectural description[1] which was linked in Chris' des

Hi I'm not sure either, but 26262 is not explicit enough. Back to my original comment that this goes beyond nomenclature. We should also keep in mind that we're not _just_ talking about 26262. I'm sur

-------------------------------------- Error: I misread the spec and Part 6 Clause 7 has the System Architecture Design, not the Software Architecture Design as input. The process in that clause is re

Hi Paul I'm in for a call after the Dev Proc WG session. Others may not be although, as Thursday is Ascension Day in Germany and it's one of the few opportunities to have a 4 day weekend by taking one