.zap files are too large and contain redundant data about zap HOT 2 OPEN

@tecimovic
Should .zap capture the version of xml it is complying with for "versioning" purpose?
Otherwise, what happens when the XML are updated and the .zap's "baseline" is essentially changed?

from zap.

Based on our discussion, we can have a save as option which just saves the enabled content in the zap file. The saved options should follow the hierarchy in the following order:

1. endpoint
2. cluster
3. attribute and commands

For eg:

• If 1 is not enabled then we should lose 2 and 3 from the json file.
• if 2 is not enabled for an endpoint then lose 3 from the json file

from zap.