The current standard has legality rules that require annex libraries to be placed inside core AADL packages. Similarly, annex subclauses are required to be placed in component types, implementations, and feature group types.
It is desirable to be able to have annex libraries without being wrapped inside a core AADL package. This would allow annex specific file extensions. It would make clearer what the qualified name of such a library is - currently the standard is silent. In EMV2 we use the convention of package name plus annex name. For RDAL Dominique has a separate library without being wrapped in an AADL package.
Proposal: take a look at the text in V2.1 to see if we can rephrase things such they do not require annexes to be stored inside core model specifications, but allow separate storage as an option.
The current standard has legality rules that require annex libraries to be placed inside core AADL packages. Similarly, annex subclauses are required to be placed in component types, implementations, and feature group types.
It is desirable to be able to have annex libraries without being wrapped inside a core AADL package. This would allow annex specific file extensions. It would make clearer what the qualified name of such a library is - currently the standard is silent. In EMV2 we use the convention of package name plus annex name. For RDAL Dominique has a separate library without being wrapped in an AADL package.