<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:54:26 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-832] Add instance-identifier and leaf-reference native types</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-832</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;We need a bridge between yang-model-api and yang-data-api where types are concerned. Specifically, we need to map TypeDefinitiion.getDefaultValue() to native types, as expected by yang-data-api.&lt;/p&gt;

&lt;p&gt;We can generalize YangInstanceIdentifier, but its deficiencies must be fixed first:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;augmentation cross-over happens on namespace change, without an explicit node, e.g. AugmentationIdentifier is actually QNameNamespace different from parent&lt;/li&gt;
	&lt;li&gt;ability to target via list order, for user ordered lists and leaf-lists&lt;/li&gt;
	&lt;li&gt;it really needs to align to the XPath view of yang-modeled data&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;More impact/tradeoff analysis is required.&lt;/p&gt;</description>
                <environment></environment>
        <key id="28764">YANGTOOLS-832</key>
            <summary>Add instance-identifier and leaf-reference native types</summary>
                <type id="10103" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10311&amp;avatarType=issuetype">New Feature</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <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="10002">Duplicate</resolution>
                                        <assignee username="rovarga">Robert Varga</assignee>
                                    <reporter username="rovarga">Robert Varga</reporter>
                        <labels>
                    </labels>
                <created>Tue, 14 Nov 2017 01:26:27 +0000</created>
                <updated>Sun, 10 Apr 2022 18:36:02 +0000</updated>
                            <resolved>Tue, 26 Oct 2021 23:37:49 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="64802" author="rovarga" created="Mon, 27 Aug 2018 23:35:47 +0000"  >&lt;p&gt;With &lt;a href=&quot;https://jira.opendaylight.org/browse/YANGTOOLS-585&quot; title=&quot;Data tree: automatic structural lifecycle&quot; class=&quot;issue-link&quot; data-issue-key=&quot;YANGTOOLS-585&quot;&gt;&lt;del&gt;YANGTOOLS-585&lt;/del&gt;&lt;/a&gt; out of the way, we really do not need AugmentationIdentifier. We can provide QNameModule query in yang-data-api to allow remote filtering based on namespace.&lt;/p&gt;</comment>
                            <comment id="70010" author="rovarga" created="Tue, 26 Oct 2021 23:37:14 +0000"  >&lt;p&gt;While this issue is older, &lt;a href=&quot;https://jira.opendaylight.org/browse/YANGTOOLS-1356&quot; title=&quot;Introduce model.api.stmt.DataNodeIdentifier&quot; class=&quot;issue-link&quot; data-issue-key=&quot;YANGTOOLS-1356&quot;&gt;&lt;del&gt;YANGTOOLS-1356&lt;/del&gt;&lt;/a&gt; provides a targeted solution based on what our downstreams need.&lt;/p&gt;

&lt;p&gt;DataNodeIdentifier solves the instance-identifier part, as it has exactly the same semantics as we need &amp;#8211; it operates on data tree addressing and is the counterpart to SchemaNodeIdentifier. YANG parser understands both schema and data trees, hence it will have little trouble with it.&lt;/p&gt;

&lt;p&gt;DataNodeFilter solves the leaf-reference part, as it is a superset of leaf-reference can address without bringing any of the XPath complexities to the table.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="34802">YANGTOOLS-1356</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i037on:</customfieldvalue>

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