https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/YANGTOOLS-837 yangtools <p><a href="https://tools.ietf.org/html/rfc7895#page-9" class="external-link" target="_blank" rel="nofollow noopener">https://tools.ietf.org/html/rfc7895#page-9</a> and <a href="https://tools.ietf.org/html/rfc7950#section-5.6" class="external-link" target="_blank" rel="nofollow noopener">https://tools.ietf.org/html/rfc7950#section-5.6</a> defines a 'conformance' leaf to be associated with a module advertised by the device.</p> <p>There are two conformance levels:</p> <ul class="alternate" type="square"> <li>implement</li> <li>import</li> </ul> <p>We currently always 'implement' a module included in CrossStatementSourceReactor, even if it is only needed to satisfy imports (e.g. is added as libSource).</p> <p>For modules pulled in from the module library to satisfy imports we should mark the resulting effective module as import only and only process its reusable pieces (groupings, typedefs, identities).</p> YANGTOOLS-837

Add support for varied model conformance

Improvement Medium Resolved Done Robert Varga Robert Varga Wed, 22 Nov 2017 16:49:17 +0000 Mon, 20 Jun 2022 15:02:55 +0000 Mon, 20 Jun 2022 15:02:55 +0000 9.0.0 parser 0 2 <p>This information should be exposed via ModuleEffectiveStatement. Note that FeatureEffectiveStatementNamespace should only be exposing features that are supported, rather than all features present in the model. Each ModuleEffectiveStatement should also export the deviations which have been applied to the module.</p> <p>Preliminary patch: <a href="https://git.opendaylight.org/gerrit/69209" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/69209</a></p> <p>This requires modifications to the parser API, so that the implementation/import constraints are taken into account as as what deviations to apply, so that we do not automatically apply deviations and do not process instantiation statements.</p> <p>StatementDefinition needs to grow a new method, which will identify whether a statement defines a data definition node (and therefore should be ignored in the import-only case).</p> <p>Is there an outlook on when this would be available? </p> <p>Having this would help us in reusing e.g. groupings from some YANG modules without actually marking support for those modules, for which we typically now copy those groupings over.</p> <p>I cannot commit to anything, as this keeps being pushed out by other priorities.</p> <p>A contribution or a contract would help landing this in a predictable timeline <img class="emoticon" src="https://jira.opendaylight.org/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> Duplicate YANGTOOLS-861 Relates YANGTOOLS-1341 Development Rank 0|i038e7: