PER CS 3.0: 3. Declare Statements, Namespace, and Import Statements

Author: screamer-gi

src/Standards/PER-CS3.0/ruleset.xml

@@ -120,17 +120,19 @@
 
     <!-- When a file contains a mix of HTML and PHP, any of the above sections may still be used. If so, they MUST be present at the top of the file, even if the remainder of the code consists of a closing PHP tag and then a mixture of HTML and PHP. -->
 
-    <!-- When the opening php tag is on the first line of the file, it MUST be on its own line with no other statements unless it is a file containing markup outside of PHP opening and closing tags. -->
+    <!-- When the opening php tag is on the first line of the file, it MUST be on its own line with no other statements unless it is a file containing markup outside of PHP opening and closing tags. The php tag MUST always be lower case. -->
     <!-- checked by PSR12.Files.OpenTag -->
+    <!--todo-->
 
     <!-- Import statements MUST never begin with a leading backslash as they must always be fully qualified. -->
     <!-- checked by PSR12.Files.ImportStatement -->
 
-    <!-- Compound namespaces with a depth of more than two MUST NOT be used. -->
+    <!-- When using compound namespaces, there MUST NOT be more than two sub-namespaces within the group. -->
     <!-- checked by PSR12.Namespaces.CompoundNamespaceDepth -->
+    <!--todo-->
 
     <!-- When wishing to declare strict types in files containing markup outside PHP opening and closing tags, the declaration MUST be on the first line of the file and include an opening PHP tag, the strict types declaration and closing tag. -->
-    <!-- Declare statements MUST contain no spaces and MUST be exactly declare(strict_types=1) (with an optional semicolon terminator). -->
+    <!-- Declare statements MUST NOT contain any spaces and MUST be exactly declare(strict_types=1) (with an optional semicolon terminator). -->
     <!-- Block declare statements are allowed and MUST be formatted as below. -->
     <!-- checked by PSR12.Files.DeclareStatement -->