API packages vs Implementation packages

[rgwilton]

Is it helpful to differentiate packages into YANG API packages and YANG implementation packages?

Is this just a type, or a different structure? Or, if they are the same structure then do we limit fields that are available depending on the package type (e.g., disallow optional in an implementation package)?

[rgwilton]

Based on the discussion at the 8th Oct meeting, the consensus was that this adds too much complexity and it would be better to try and keep packages as simple as possible, at least in the initial version. Hence, the proposal, at least at this time is to not try and address this. I.e., a YANG package just defines a schema, and doesn't have any additional optionality beyond that supported by YANG feature statements.