<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:55:23 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-1172] Integrate rfc8528-data-api into yang-data-api</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-1172</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;Mountpoints are an inherent design part of NormalizedNode API, as it expresses a special case in terms of a ForeignDataNode.&lt;/p&gt;

&lt;p&gt;As such, mountpoints form a separate tree, similar to metadata. This needs to be expressed in NormalizedNodeResult class hierarchy.&lt;/p&gt;

&lt;p&gt;As such, MountPointNode needs to be renamed, as it is not a NormalizedNode, but rather:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;we have NormalizedData, which does not imply PathArgument&lt;/li&gt;
	&lt;li&gt;we have NormalizedNode, which implies PathArgument and is a tree&lt;/li&gt;
	&lt;li&gt;we have NormalizedMountData, which is attached to a NormalizedNodeResult&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Note that NormalizedMountData has an identifier, and that identifier has a QName, but it is &lt;b&gt;not&lt;/b&gt; a NodeIdentifier. This implies we need to separate NormalizedNodeContainer from NormalizedNode &#8211; as the latter implies PathArgument. This will also pave the way for dealing with rc:data, which is NormalizedNodeContainer, but its identifier is a raw string (and therefore is &lt;b&gt;not&lt;/b&gt; a NormalizedNode, but a top-level construct as the one introduced in this issue).&lt;/p&gt;</description>
                <environment></environment>
        <key id="33562">YANGTOOLS-1172</key>
            <summary>Integrate rfc8528-data-api into yang-data-api</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="10000">Done</resolution>
                                        <assignee username="rovarga">Robert Varga</assignee>
                                    <reporter username="rovarga">Robert Varga</reporter>
                        <labels>
                            <label>pt</label>
                    </labels>
                <created>Fri, 13 Nov 2020 22:56:51 +0000</created>
                <updated>Wed, 17 May 2023 20:34:19 +0000</updated>
                            <resolved>Wed, 17 May 2023 20:34:05 +0000</resolved>
                                                    <fixVersion>11.0.0</fixVersion>
                                    <component>data-api</component>
                    <component>data-impl</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="70314" author="rovarga" created="Wed, 1 Dec 2021 12:41:49 +0000"  >&lt;p&gt;MountPointNode currently has a codec-only view of what a mount point looks like. Most notably it contains a reference to EffectiveModelContext, which is something that kinda works, but breaks down if we hit binary serialization &#8211; i.e. yang-data-codec-binfmt. Also the interaction with DataTree is underfined.&lt;/p&gt;

&lt;p&gt;Both of these need to have a solid story before we integrate the concept. Note that binfmt also has a slight gap in various anyxml/anydata representations, so we probably want to tackle all three at the same time.&lt;/p&gt;</comment>
                            <comment id="71819" author="rovarga" created="Wed, 11 Jan 2023 02:01:25 +0000"  >&lt;p&gt;The codec-only aspect is going to be solved by NormalizedNodeResult integration &#8211; making this a concept that needs outside integration.&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_10002" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>YANGTOOLS-1022</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03w7z:</customfieldvalue>

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