OPC UA offers the XML schema NodeSet2 to represent an Information-Model.

Currently this format is used for two major cases:

• Offline-Configuration of Clients
  (Get a NodeSet2 from a Server and feed it into a client to tell the
  client which nodes are available on the server)
• Tool-supported Generation of Information-Models
  (Tool can generate a Information-Model, outputs NodeSet which can be
  transported to the Server)

New requirements for Offline-Configuration of Servers:

NodeSet2 misses certain features for this usecase.

1)The XML should be able to represent dynamic behavior of a Information-Model, i.e. indicate that node can be added (in a pacticular location). This might be done with a <placeholder> type construct or via a reference or some other XML based construct or in some other manner.
2) The xml should be able to represent that node can disappear
3) This applies to instance - not to types.

Requested:
provide some manner of controlling the number of possible instance that appear or if attributes are to be included for a given object via the nodeset file