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/MDSAL-40 mdsal <p>After working with binding specification v1 there were sevaral issues identified,<br/> which will require Binding Specification v2 along with migration plan.</p> <p>This milestone tracks design of binding specification and all items, which blocks it should be addressed by Binding Specification v2.</p> <p>Operating System: All<br/> Platform: All</p> MDSAL-40

Milestone: Implement Binding Specification v2

Improvement Resolved Done Martin Ciglan Tony Tkacik Thu, 24 Jul 2014 10:16:18 +0000 Fri, 9 Mar 2018 18:00:04 +0000 Fri, 10 Mar 2017 15:39:16 +0000 0 7 <p>Some thoughts are documented here:<br/> <a href="https://wiki.opendaylight.org/view/YANG_Tools:Design:Binding_Specification_v2_Analysis" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/YANG_Tools:Design:Binding_Specification_v2_Analysis</a></p> <p>Move to MDSAL</p> <p>I was tasked with surveying which kind of identifiers are usual.</p> <p>Repository with collection of models: <a href="https://github.com/YangModels/yang" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/YangModels/yang</a><br/> Script to mine identifiers: <a href="https://git.opendaylight.org/gerrit/37283" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/37283</a><br/> Resulting file: archived in attachment.</p> <p>There are some obvious false positives (parts of description sentences that are not actual definitions), there may be false negatives (script does not understand non-standard formatting).</p> <p>Most identifiers are lowercase with dashes (e.g. all-users). Also camel case (e.g. GigabitEthernet) or mixed case (e.g. FCoE) are common. Dot appears rarely and only between digits (e.g. eth-if-speed-2.5gb). Underscores occasionally replace dashes (e.g source-port_choice). There are no underscores at the start of an identifier. No identifier was enclosed in quotes (at place of definition).</p> <p>Attachment identifiers_20160407.tar.xz has been added with description: Archive with (identifier, statement type, multiplicity) lines</p> <p>based on design:<br/> <a href="https://bugs.opendaylight.org/show_bug.cgi?id=2356" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=2356</a></p> <p>basic infrastructure patch merged:<br/> <a href="https://git.opendaylight.org/gerrit/#/c/38567/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/38567/</a></p> <p>task in progress</p> <p>Does moving the milestone from Boron-M5 to Boron-RC0 mean that we're effectively adding a feature after code freeze?</p> <p>Yes. Given the scope, this has always been targeted as a preview in Boron.</p> <p>Based on code designed, developed and merged in Boron, this umbrella task continues in Carbon</p> <p>(In reply to Martin Ciglan from comment #8)<br/> &gt; Based on code designed, developed and merged in Boron, this umbrella task<br/> &gt; continues in Carbon</p> <p>Out of curiosity, does this mean that we're not planning to deprecate the Binding Spec v1 in Carbon?</p> <p>Binding2 Java API Generator patch chain:<br/> <a href="https://git.opendaylight.org/gerrit/#/c/46890/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/46890/</a></p> <p>So what is the expected status of V1 and V2 on Carbon release?<br/> I imagine V2 to be Experimental (upgrade from Preview)<br/> and V1 still default and non-deprecated.</p> Blocks MDSAL-1 MDSAL-42 MDSAL-52 MDSAL-67 MDSAL-73 MDSAL-75 MDSAL-76 MDSAL-101 MDSAL-146 MDSAL-185 MDSAL-187 MDSAL-233 CONTROLLER-604 MDSAL-6 MDSAL-51 YANGTOOLS-231 YANGTOOLS-250 Duplicate MDSAL-57 Development External issue ID 1411 External issue URL Issue Type ODL SR Target Milestone Rank 0|i02vxz: