|
|||||||||
![]() |
|
||||||||
| Change Requests are valid for published MESA specifications and not for "working drafts". In line with the MESA Technical Working Procedures, when a published MESA deliverable (MESA Specification or MESA Report) is revised in order to produce a subsequent version, this shall be performed under change control within the relevant SSG or TSG. All development of the deliverable shall be achieved by change requests to be approved by the SSG or TSG. For delegates who want to propose an editorial modification, the addition of a feature, a functional modification of a feature or a correction to one of the approved MESA documents, please follow the instructions below. HOW TO CREATE A CHANGE REQUEST (CR)
Examples of expressions of provision in MESA specifications:To ensure that everybody else understands your proposed changes the same way that you do, it is very important to keep to the following rules: SHALL: To be used to indicate a requirement. e.g. "The ACH shall be used for sending RFCH in the downlink" is correct. Do not use "The ACH is used for sending RFCH in the downlink" or "The ACH must be used for sending RFCH in the downlink". SHOULD: To be used to indicate recommendation. i.e. if among several possibilities one is recommended as particularly suitable, without mentioning or excluding others, or a certain course of action is preferred but not necessarily required, or (in the negative form) a certain possibility or course of action is deprecated but not prohibited. MAY: To be used to indicate permission. To be used instead of phrases such as "is permitted", "is allowed" or is permissible". The opposite of "may" is "need not". CAN: To be used to indicate possibility and capability. To be used instead of phrases such as "be able to", "there is a possibility of" or "it is possible to".
|
|||||||||
|
|||||||||