Refactor gen_address_space.js to make gen_nodeset.js. Add 1.0.4 schem…

…a files in prep for using them.

CHANGELOG.md

@@ -14,10 +14,12 @@ Planned future work is listed at the bottom.
   - Client and server side support for X509 identity tokens.
   - New `modbus-server` sample server which connects to a MODBUS device and presents values in OPC
   - Client [tutorial](./docs/client_tutorial.md)
+  - gen_nodeset.js script that can do ad hoc node set generation. The script gen_address_space.js refactored into a helper
+    nodeset.js to reuse the code for this.
+  - TODO fix leak issue with client disconnects not actually disconnecting all their tasks
   - TODO Add support for EventFilter in monitored items. This is quite a substantial new change
     that allows clients to evaluate complex expressions that trigger change events.
   - TODO address space. Add a create on demand callback
-  - TODO gen_types.js. Refactor so it could be used to generate code for any model
   - TODO prevent nested arrays from being deserialized
   - TODO More control over limits on the server - number of subscriptions, monitored items, sessions, min publishing interval
   - TODO Integration tests are broken and need to be fixed.

docs/compatibility.md

@@ -42,7 +42,9 @@ The following services are supported:
   * TranslateBrowsePathsToNodeIds
 
 * MonitoredItem service set
-  * CreateMonitoredItems - Data change filter including dead band filtering. 
+  * CreateMonitoredItems 
+    - Data change filter including dead band filtering.
+    - Event filter (work in progress) 
   * ModifyMonitoredItems
   * SetMonitoringMode
   * SetTriggering
@@ -73,7 +75,7 @@ Currently the following are not supported
 
 * Diagnostic info. OPC UA allows for you to ask for diagnostics with any request. None is supplied at this time
 * Session resumption. If your client disconnects, all information is discarded. 
-* Default nodeset is mostly static. Certain fields of server information will contain their default values unless explicitly set.
+* Default node set is mostly static. Certain fields of server information will contain their default values unless explicitly set.
 
 ## Client
 
@@ -109,12 +111,11 @@ The following security policies are supported - None, Basic128Rsa15, Basic256, B
 
 ## User identities
 
-The server and client support the following user identities
+The server and client support the following user identity tokens
 
 1. Anonymous - i.e. no identity
 2. UserName - encrypted and plaintext. User/pass identities are defined by configuration.
-
-X509 is intended for a future release.
+3. X509 certificates
 
 ## Crypto