Conventions Throughout this specification you will see the following headings on certain paragraphs. These headings instill special meaning on these paragraphs. must be followed to ensure compatibility with the System Framework. A rule is characterized by the Rules use of the words and in bold upper case characters. These words are not used in SHALL SHALL NOT this manner for any other purpose other than stating rules. consist of advice to implementers that will affect the usability of the final device. They Recommendations are included in this standard to draw attention to particular characteristics that the authors believe to be important to end user success. are included to specific implementations or uses of system components. A Permissions authorize permission is characterized by the use of the word MAY in bold upper case characters. These permissions are granted to ensure specific System Framework components are well defined and can be tested for compatibility and interoperability. spell out implications of rules and bring attention to things that might otherwise be Observations overlooked. They also give the rationale behind certain rules, so that the reader understands why the rule must be followed. Any text that appears without heading should be considered as A Note on the text of the specification: description of the standard and how the architecture was intended to operate. The purpose of this text is to give the reader a deeper understanding of the intentions of the specification including the underlying model and specific required features. As such, the implementer of this standard should take great care to ensure that a particular implementation does not conflict with the text of the standard.
Conventions Throughout this specification you will see the following headings on certain paragraphs. These headings instill special meaning on these paragraphs. Rules must be followed to ensure compatibility with the System Framework. A rule is characterized by the use of the words SHALL and SHALL NOT in bold upper case characters. These words are not used in this manner for any other purpose other than stating rules. Recommendations consist of advice to implementers that will affect the usability of the final device. They are included in this standard to draw attention to particular characteristics that the authors believe to be important to end user success. Permissions are included to authorize specific implementations or uses of system components. A permission is characterized by the use of the word MAY in bold upper case characters. These permissions are granted to ensure specific System Framework components are well defined and can be tested for compatibility and interoperability. Observations spell out implications of rules and bring attention to things that might otherwise be overlooked. They also give the rationale behind certain rules, so that the reader understands why the rule must be followed. A Note on the text of the specification: Any text that appears without heading should be considered as description of the standard and how the architecture was intended to operate. The purpose of this text is to give the reader a deeper understanding of the intentions of the specification including the underlying model and specific required features. As such, the implementer of this standard should take great care to ensure that a particular implementation does not conflict with the text of the standard.
vpp436_2016-06-07.docx