<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:54:34 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-877] Add yang-model-api model of an XPath expression</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-877</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;Current RevisionAwareXPath is quite deficient in expressing the XPath stored therein. More specifically it requires anyone attempting to use it infer the prefix/namespace mapping and then parse the expression itself.&lt;/p&gt;

&lt;p&gt;Instead of going through these hoops, we really should have an object model of the expression, similar to org.jaxen.expr.Expr, which would act as an intermediate representation format, where all prefixes would already be properly resolved so that we are dealing with QNames instead of prefix+localnames.&lt;/p&gt;

&lt;p&gt;The parser should also bind function invocations for YANG-defined functions, so that their arguments are resolved to proper types.&lt;/p&gt;</description>
                <environment></environment>
        <key id="29894">YANGTOOLS-877</key>
            <summary>Add yang-model-api model of an XPath expression</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>
                    </labels>
                <created>Wed, 2 May 2018 11:03:11 +0000</created>
                <updated>Thu, 2 Aug 2018 08:51:12 +0000</updated>
                            <resolved>Thu, 2 Aug 2018 08:51:12 +0000</resolved>
                                                    <fixVersion>2.0.10</fixVersion>
                                    <component>parser</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="62709" author="rovarga" created="Wed, 2 May 2018 11:18:44 +0000"  >&lt;p&gt;Note that this layer of XPath model needs to provide for predicates for node lookups, unlike &lt;a href=&quot;https://jira.opendaylight.org/browse/YANGTOOLS-878&quot; title=&quot;Add yang-data-api model of an XPath expression&quot; class=&quot;issue-link&quot; data-issue-key=&quot;YANGTOOLS-878&quot;&gt;YANGTOOLS-878&lt;/a&gt;, which should further extend the model to resolve them to PathArgument lookups.&lt;/p&gt;

&lt;p&gt;The possibility of binding expression (literals, identity references, etc.) to Java types should be evaluated &#8211; it needs to happen in places where we can statically infer the type and should happen either in scope of this issue or in &lt;a href=&quot;https://jira.opendaylight.org/browse/YANGTOOLS-878&quot; title=&quot;Add yang-data-api model of an XPath expression&quot; class=&quot;issue-link&quot; data-issue-key=&quot;YANGTOOLS-878&quot;&gt;YANGTOOLS-878&lt;/a&gt;. It is okay to have a partial type binding, as the XPath evaluation engine needs to be able to cope with both.&lt;/p&gt;</comment>
                            <comment id="64464" author="rovarga" created="Wed, 1 Aug 2018 17:43:43 +0000"  >&lt;p&gt;This is still missing an implementation.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="29895">YANGTOOLS-878</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|i03e3z:</customfieldvalue>

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