Differences

This shows you the differences between two versions of the page.

--- dido:00-sip-ra:04-instructions-for-submitters:04-9-submission-format:04-9-1-general:start [2026/07/11 11:07] – ↷ Links adapted because of a move operation nick_dido
+++ dido:00-sip-ra:04-instructions-for-submitters:04-9-submission-format:04-9-1-general:start [2026/07/11 11:15] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 9: / Line 9: @@
 To the greatest extent possible, the Submission SHOULD follow the document structure set out in [[https://www.iso.org/directives-and-policies.html|ISO/IEC Directives, Part 2]]: Rules for the Structure and Drafting of International Standards [ISO2]. An OMG specification template is available to help follow these guidelines.
-The keywords "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", and "NEED NOT" SHALL be used as described in Part 2 of the ISO/IEC Directives [ISO2]. These [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:i:iso|ISO]] terms are compatible with the same terms in [[https://www.rfc-editor.org/rfc/rfc2119|IETF RFC 2119]] [RFC2119].
+The keywords "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "MAY", and "NEED NOT" SHALL be used as described in Part 2 of the ISO/IEC Directives [ISO2]. These [[dido:99_annexes:annex-b-terms-and-definitions:i:iso|ISO]] terms are compatible with the same terms in [[https://www.rfc-editor.org/rfc/rfc2119|IETF RFC 2119]] [RFC2119].
 The RFC 2119 terms "MUST", "MUST NOT", "OPTIONAL", "REQUIRED", "RECOMMENDED", and "NOT RECOMMENDED" SHALL NOT be used, even though RFC 2119 permits those terms.