<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:52:28 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[YANGTOOLS-173] Usability: Rename the yang.data.api.InstanceIdentifier to yang.data.api.YangInstanceIdentifier</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-173</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;One of the comments on usability of MD-SAL is that classes with the same name make it really difficult to use and interact with MD-SAL. &lt;/p&gt;

&lt;p&gt;On that front, we would like to rename the InstanceIdentifier class name, for which there are two classes (a binding aware and binding independent version).&lt;/p&gt;

&lt;p&gt;org.opendaylight.yangtools.yang.data.api.InstanceIdentifier to org.opendaylight.yangtools.yang.data.api.BIInstanceIdentifier&lt;/p&gt;

&lt;p&gt;and &lt;/p&gt;

&lt;p&gt;org.opendaylight.yangtools.yang.binding.InstanceIdentifier to&lt;br/&gt;
org.opendaylight.yangtools.yang.binding.BAInstanceIdentifier&lt;/p&gt;

&lt;p&gt;By renaming these classes we can make it clearer if we are using the BI or BA version, and it will also allow them to coexist in the same class with out having to fully qualify the class names.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: Mac OS&lt;br/&gt;
Platform: PC&lt;/p&gt;</environment>
        <key id="22593">YANGTOOLS-173</key>
            <summary>Usability: Rename the yang.data.api.InstanceIdentifier to yang.data.api.YangInstanceIdentifier</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="rovarga">Robert Varga</assignee>
                                    <reporter username="devin.avery@brocade.com">Devin Avery</reporter>
                        <labels>
                    </labels>
                <created>Wed, 28 May 2014 13:33:49 +0000</created>
                <updated>Sun, 10 Apr 2022 18:35:06 +0000</updated>
                            <resolved>Wed, 30 Jul 2014 09:24:09 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="42766" author="tony.tkacik@gmail.com" created="Wed, 4 Jun 2014 10:12:35 +0000"  >&lt;p&gt;This changes a lot of APIs, this needs to be taken care of carefully.&lt;/p&gt;</comment>
                            <comment id="42767" author="devin.avery@brocade.com" created="Wed, 4 Jun 2014 11:58:58 +0000"  >&lt;p&gt;Tony - what if we derive two new classes from each with the below suggested names, and @Deprecate the old ones. That way folks can start using the new syntax, but we don&apos;t have to change any API. &lt;/p&gt;

&lt;p&gt;After projects start to migrate we can do a final push to move all remaining code. &lt;/p&gt;

&lt;p&gt;This way it would be less of a &quot;shock&quot; to the system and should keep everything compiling even though the API changes.&lt;/p&gt;

&lt;p&gt;Additionally, this would allow instanceof calls etc to still work. So as long as we are not check explict class types anywhere we should be safe.&lt;/p&gt;</comment>
                            <comment id="42768" author="tony.tkacik@gmail.com" created="Wed, 4 Jun 2014 13:14:07 +0000"  >&lt;p&gt;Hi Devin, could you propose patch for this (leave existing,&lt;br/&gt;
create subclasses with new names)&lt;/p&gt;

&lt;p&gt;I would suggest naming:&lt;br/&gt;
  BindingInstanceIdentifier - for yang-binding version&lt;br/&gt;
  DOMInstanceIdentifier - for yang-data-api version&lt;/p&gt;

&lt;p&gt;These names are more self-explaining as BI/BA versions.&lt;/p&gt;</comment>
                            <comment id="42769" author="rovarga" created="Tue, 29 Jul 2014 10:22:51 +0000"  >&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/9427/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/9427/&lt;/a&gt;&lt;br/&gt;
&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/9428/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/9428/&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1092</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=1092]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10204" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>ODL SR Target Milestone</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10370"><![CDATA[Helium]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10202" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Priority</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10312"><![CDATA[High]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i025lb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>