<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:53:41 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-584] DESCRIPTION is not valid for INPUT or OUTPUT.</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-584</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;I am getting Error when trying to parse a yang file.&lt;/p&gt;

&lt;p&gt;my yang is:&lt;br/&gt;
module zws {&lt;br/&gt;
   namespace &quot;a:b:c&quot;;&lt;br/&gt;
   prefix zws;&lt;br/&gt;
   revision 2010-09-24 &lt;/p&gt;
{
     description
      &quot;Initial revision.&quot;;
   }
&lt;p&gt;   rpc method1 {&lt;br/&gt;
     input {&lt;br/&gt;
       description &quot;input des.&quot;;&lt;br/&gt;
       leaf param &lt;/p&gt;
{
         type string;
       }&lt;br/&gt;
     }&lt;br/&gt;
     output {&lt;br/&gt;
       description &quot;output des.&quot;;&lt;br/&gt;
       leaf param {         type string;       }
&lt;p&gt;     }&lt;br/&gt;
   }   &lt;br/&gt;
 }&lt;/p&gt;

&lt;p&gt;the error is:&lt;br/&gt;
10:55:18.052 &lt;span class=&quot;error&quot;&gt;&amp;#91;main&amp;#93;&lt;/span&gt; WARN  o.o.y.y.p.i.YangStatementParserListenerImpl - DESCRIPTION is not valid for INPUT. Error in module zws (QNameModule&lt;/p&gt;
{ns=a:b:c, rev=2010-09-24}
&lt;p&gt;)&lt;br/&gt;
org.opendaylight.yangtools.yang.parser.spi.meta.InvalidSubstatementException: DESCRIPTION is not valid for INPUT. Error in module zws (QNameModule&lt;/p&gt;
{ns=a:b:c, rev=2010-09-24}
&lt;p&gt;)&lt;br/&gt;
	at org.opendaylight.yangtools.yang.parser.spi.SubstatementValidator.validate(SubstatementValidator.java:92) ~&lt;span class=&quot;error&quot;&gt;&amp;#91;classes/:na&amp;#93;&lt;/span&gt;&lt;br/&gt;
	...&lt;br/&gt;
10:55:18.053 &lt;span class=&quot;error&quot;&gt;&amp;#91;main&amp;#93;&lt;/span&gt; WARN  o.o.y.y.p.i.YangStatementParserListenerImpl - DESCRIPTION is not valid for OUTPUT. Error in module zws (QNameModule&lt;/p&gt;
{ns=a:b:c, rev=2010-09-24}
&lt;p&gt;)&lt;br/&gt;
org.opendaylight.yangtools.yang.parser.spi.meta.InvalidSubstatementException: DESCRIPTION is not valid for OUTPUT. Error in module zws (QNameModule&lt;/p&gt;
{ns=a:b:c, rev=2010-09-24}
&lt;p&gt;)&lt;br/&gt;
	at org.opendaylight.yangtools.yang.parser.spi.SubstatementValidator.validate(SubstatementValidator.java:92) ~&lt;span class=&quot;error&quot;&gt;&amp;#91;classes/:na&amp;#93;&lt;/span&gt;&lt;br/&gt;
	...&lt;/p&gt;

&lt;p&gt;I think there may be have descriptions in the input or ouput node of rpc method. This may be a bug, there may be something wrong in the code of yangtools project.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="23004">YANGTOOLS-584</key>
            <summary>DESCRIPTION is not valid for INPUT or OUTPUT.</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</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="-1">Unassigned</assignee>
                                    <reporter username="zhuweisheng@huawei.com">zhuweisheng</reporter>
                        <labels>
                    </labels>
                <created>Thu, 18 Feb 2016 03:24:43 +0000</created>
                <updated>Sun, 10 Apr 2022 18:35:44 +0000</updated>
                            <resolved>Thu, 18 Feb 2016 09:50:13 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="43756" author="tony.tkacik@gmail.com" created="Thu, 18 Feb 2016 09:01:25 +0000"  >&lt;p&gt;I see why it makes tempting to have description in input / output,&lt;br/&gt;
but RFC6020 actually does not allow it.&lt;/p&gt;

&lt;p&gt;See:&lt;br/&gt;
&lt;a href=&quot;https://tools.ietf.org/html/rfc6020#section-7.13.2.1&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://tools.ietf.org/html/rfc6020#section-7.13.2.1&lt;/a&gt;&lt;br/&gt;
&lt;a href=&quot;https://tools.ietf.org/html/rfc6020#section-7.13.3.1&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://tools.ietf.org/html/rfc6020#section-7.13.3.1&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Description to input / output will not be even added in YANG 1.1 (see &lt;br/&gt;
&lt;a href=&quot;https://tools.ietf.org/html/draft-ietf-netmod-rfc6020bis-09#section-7.14.2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://tools.ietf.org/html/draft-ietf-netmod-rfc6020bis-09#section-7.14.2&lt;/a&gt; ).&lt;/p&gt;

&lt;p&gt;If you think about it, it actually makes sense - you describe whole rpc&lt;br/&gt;
and input, output are there only to model data of rpc.&lt;/p&gt;</comment>
                            <comment id="43757" author="zhuweisheng@huawei.com" created="Thu, 18 Feb 2016 09:50:13 +0000"  >&lt;p&gt;Sorry&#65292; I neglect. Yes, I agree with that. Thanks!&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>5379</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=5379]]></customfieldvalue>

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

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