<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:53:39 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-576] Introduce canonical-pattern extension</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-576</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;Introduce cannonical-format extension to describe pattern of cannonical value of string and provide enforcement tools&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="22996">YANGTOOLS-576</key>
            <summary>Introduce canonical-pattern extension</summary>
                <type id="10103" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10311&amp;avatarType=issuetype">New Feature</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="10001">Won&apos;t Do</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="tony.tkacik@gmail.com">Tony Tkacik</reporter>
                        <labels>
                    </labels>
                <created>Mon, 25 Jan 2016 16:15:26 +0000</created>
                <updated>Tue, 12 Jun 2018 13:31:24 +0000</updated>
                            <resolved>Tue, 12 Jun 2018 13:31:24 +0000</resolved>
                                                                    <component>codecs</component>
                    <component>parser</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="43722" author="abbas.pareedkunju@tcs.com" created="Fri, 20 May 2016 09:38:22 +0000"  >&lt;p&gt;Hi Tony,&lt;/p&gt;

&lt;p&gt;I would like to work on this concern you have raised. Would you be please able to give some more details on what you are looking for?&lt;/p&gt;


&lt;p&gt;Thanks,&lt;br/&gt;
Abbas&lt;/p&gt;</comment>
                            <comment id="43723" author="abbas.pareedkunju@tcs.com" created="Tue, 31 May 2016 08:48:05 +0000"  >&lt;p&gt;really appreciate any more details.&lt;/p&gt;</comment>
                            <comment id="43724" author="rovarga" created="Wed, 7 Sep 2016 15:31:27 +0000"  >&lt;p&gt;To clarify a bit. RFC6020 has the pattern restriction, which defines how an allowed value must look like &amp;#8211; allowing for multiple representations.&lt;/p&gt;

&lt;p&gt;This is evident in ietf-inet-types, where IPv6 and MAC addresses can have both capitalized and non-capitalized letters.&lt;/p&gt;

&lt;p&gt;Unfortunately YANG does not define a mechanism to define what the canonical format looks like, e.g. lower-case letters in MAC.&lt;/p&gt;

&lt;p&gt;Hence we need to define an extension, canonical-pattern, which will take a single argument, just like pattern does and can be applied only once in a type hierarchy.&lt;/p&gt;</comment>
                            <comment id="63413" author="rovarga" created="Tue, 12 Jun 2018 13:31:24 +0000"  >&lt;p&gt;We don&apos;t really need this, as in 3.0.0 we will actually use specialized value classes to support canonical representation &#8211; with conversion and storage.&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>5087</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=5087]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10308"><![CDATA[New Feature]]></customfieldvalue>

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

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