search

saeaadl / emv2

AADL Error Model V2 annex language
0 stars 0 forks source link

Grammar for type reference in EMV2 annex specific path #19

Closed buzden closed 4 years ago

buzden commented 8 years ago

As it written in the annex, emv2_annex_specific_path

may optionally be followed by an error_type_reference, separated by a dot (“.”)

We think that dot-separation syntax is not adequate for type reference because type is not a part of a referenced event or state. We propose to change the syntax to make type references to be easily distinguishable from subcomponents references or similar things.

I.e. we'd like to see something like state{type} instead of state.type.

reteprelief commented 8 years ago

I like the idea. However, this is a syntactic change

buzden commented 8 years ago

However, this is a syntactic change

We really consider this change worth to be done.

You know, in context of AADL we talk so much about early validation and verification of modelled systems to avoid errors on early stages of development because such errors may lead to a lot of rework on further stages.

But what if we are making similar mistake by saying "However, this is a syntactic change" in the modelling language? Don't you think that not making this syntactic change will lead to much worse results?

reteprelief commented 8 years ago

Denis,

I personally agree with you. I just sometimes get complaints about the stability of the standard.

I plan to discuss this errata at the meeting.

jjhugues commented 4 years ago

Closed as this has been implemented