ALMAS16 — Completeness gaps / areas needing clarification

• Security model is minimal and arguably under-specified, especially for registration and access control.
• Error handling is inconsistently defined:
o some operations specify mandatory failure conditions,
o others leave too much to implementation-specific behavior.
• Language/locale handling needs tighter normative definition:
o expected locale format,
o fallback behavior,
o required behavior if translation is unavailable.
• Persistence/recovery behavior is only lightly defined despite Persistent attribute.
• Receiver selection/actionee resolution should be specified more rigorously, especially in hierarchy fallback scenarios.