Fixes from review

exasol · Nov 12, 2024 · 7358ca6 · 7358ca6
1 parent 9a1a302
commit 7358ca6
Showing 1 changed file with 16 additions and 11 deletions.
diff --git a/exaudfclient/docs/script_options_requirments.md b/exaudfclient/docs/script_options_requirments.md
@@ -199,7 +199,7 @@ Tags: V2
 ### Escape Sequence Script Options Parsing
 `req~escape-sequence-script-options-parsing~1`
 
-The following rules for escape sequences at any place within a script optionValue are to be applied:
+The following rules for escape sequences at any place within a script option value are to be applied:
 - '\n' => <line feed> character
 - '\r' => <carriage return> character
 - '\;' => ';' character
@@ -324,35 +324,40 @@ Needs: dsn
 Covers:
 - `feat~java-specific-script-options~1`
 
-### Java %import Option Handling
-`req~java-import-option-handling~1`
+### Java %import Option Handling V1
+`req~java-import-option-handling-v1~1`
 
 For each found `%import` option, the Java parser handler must handle nested Script Options appropriately:
-1. `%scriptclass` option must be ignored, but removed from the script code.
+1. `%scriptclass` option must be ignored.
 2. All other options must be handled as if they were part of the source script.
 3. Already imported scripts must not be imported again, but the `%import` statement must be removed
 
 Needs: dsn
 
+Tags: V1
+
 Covers:
 - `feat~java-specific-script-options~1`
 
-### Existing Parser Library License
-`req~existing-parser-library-license~1`
+### Java %import Option Handling V2
+`req~java-import-option-handling-v2~1`
 
-The parser needs to be usable in open source and closed source projects.
+For each found `%import` option, the Java parser handler must handle nested Script Options appropriately:
+1. `%scriptclass` option must be ignored, but removed from the script code.
+2. All other options must be handled as if they were part of the source script.
+3. Already imported scripts must not be imported again, but the `%import` statement must be removed
 
 Needs: dsn
 
 Tags: V2
 
 Covers:
-- `feat~general-script-options-parsing~1`
+- `feat~java-specific-script-options~1`
 
-### Existing Parser Linker Namespace Compatibility
-`req~existing-parser-linker-namespace-compatibility~1`
+### Existing Parser Library License
+`req~existing-parser-library-license~1`
 
-Ideally, the new parser should allow encapsulation in a custom C++ namespace, in order to avoid possible linker namespace conflicts with customer libraries.
+The parser needs to be usable in open source and closed source projects.
 
 Needs: dsn