Hi all, In the mean time some additional requirements surfaced, which I added in [1].
I also updated the feature model format, mostly based on existing requirements. It can be found at [2]. Once it's matured we should create a JSON Schema for it (or something similar)... Main additions are: * Support for variables * Comments can now also be put in the document by using a key that starts with a hash '#'. This is because most JSON editors don't support the JSMin (/* */ and //) style comments and show these as errors. * Some small additions that make it possible to 100% roundtrip between the provisioning and the feature model which is especially important during the phase where users are migrating. Best regards, David [1] https://github.com/apache/sling-whiteboard/commit/2dcab0e45866ce51f732ac525ebf100a82737099 [2] https://github.com/apache/sling-whiteboard/blob/master/featuremodel/design/feature-model.json
