<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:13:03 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 add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[FOLIO-1399] Improve lint-raml to handle RMB v20+ schema $ref as key names</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-1399</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;The script folio-tools/lint-raml/lint_raml_cop.py does already handle &quot;RAML 1.0&quot; as well as &quot;RAML 0.8&quot;.&lt;/p&gt;

&lt;p&gt;The new RMB v20 (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;RMB-109&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-109&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;RAML 1.0 support: use raml-for-jax-rs rather than obsolete raml-jaxrs-codegen&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-109
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
) uses &quot;RAML 1.0&quot; only.&lt;/p&gt;

&lt;p&gt;Its dependencies still utilise the schema key names declared in the RAML files as the $ref value to link a parent JSON schema to another schema. However now it does not allow those $ref values to be a filename or relative pathname.&lt;/p&gt;

&lt;p&gt;So the lint_raml_cop.py independent verification script needs to continue to handle our previous style of $ref using pathnames (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-573&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-573&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Use a consistent method for RAML to refer to a parent JSON schema which refers to another JSON schema&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-573
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
), as well as now the key names.&lt;/p&gt;</description>
                <environment></environment>
        <key id="80745">FOLIO-1399</key>
            <summary>Improve lint-raml to handle RMB v20+ schema $ref as key names</summary>
                <type id="10003" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium">Task</type>
                                            <priority id="10002" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p3.svg">P3</priority>
                        <status id="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Done</resolution>
                                                        <assignee accountid="61cd0ca0bce5e00069e98be7">David Crossley</assignee>
                                                                <reporter accountid="61cd0ca0bce5e00069e98be7">David Crossley</reporter>
                                    <labels>
                            <label>ci</label>
                            <label>core</label>
                            <label>raml</label>
                            <label>sprint44</label>
                    </labels>
                <created>Mon, 6 Aug 2018 03:17:12 +0000</created>
                <updated>Mon, 12 Nov 2018 14:24:52 +0000</updated>
                            <resolved>Thu, 16 Aug 2018 17:45:10 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                <comments>
                                                            <comment id="194920" author="5bffed52a1b46046f530c8f7" created="Mon, 6 Aug 2018 06:47:54 +0000"  >&lt;p&gt;If I rightly understand the implications here, we are actively moving &lt;em&gt;away from&lt;/em&gt; what the JSON Schema standards specifies.&lt;/p&gt;

&lt;p&gt;And this means that our actual JSON Schemas are likely to become more and more standards-non-conformant, which means that mod-graphl&apos;s JSON Schema handling code won&apos;t be able to use standard tools.&lt;/p&gt;

&lt;p&gt;Am I missing something?&lt;/p&gt;</comment>
                                                            <comment id="194924" author="61cd0ca0bce5e00069e98be7" created="Tue, 7 Aug 2018 08:52:18 +0000"  >&lt;p&gt;This is the way that the RMB&#8217;s dependencies (raml-for-jax-rs and jsonschema2pojo) operate &amp;#8211; an implementation-specific technique. This is the way that it was with the original RMB because of those dependencies. Then with 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-573&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-573&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Use a consistent method for RAML to refer to a parent JSON schema which refers to another JSON schema&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-573
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 we found a standard way to address that, using the relative pathnames, so that all raml-related tools could operate.&lt;/p&gt;

&lt;p&gt;There are some comments in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;RMB-109&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-109&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;RAML 1.0 support: use raml-for-jax-rs rather than obsolete raml-jaxrs-codegen&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            RMB-109
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 and 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-573&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-573&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Use a consistent method for RAML to refer to a parent JSON schema which refers to another JSON schema&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-573
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 that have links to some remote issues regarding this.&lt;/p&gt;

&lt;p&gt;This 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1399&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1399&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Improve lint-raml to handle RMB v20+ schema $ref as key names&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1399
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 is just about handling either style of $ref for this validation script, and is not trying to address that wider issue.&lt;/p&gt;</comment>
                                                            <comment id="194927" author="557058:b8e64633-1f7c-402d-9caf-9959a5ba5d0d" created="Wed, 8 Aug 2018 13:14:51 +0000"  >&lt;p&gt;Guys, (adding &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f8314dfbdef80006f6f572d&quot; class=&quot;user-hover&quot; rel=&quot;5f8314dfbdef80006f6f572d&quot; data-account-id=&quot;5f8314dfbdef80006f6f572d&quot; accountid=&quot;5f8314dfbdef80006f6f572d&quot; rel=&quot;noreferrer&quot;&gt;Adam Dickmeiss&lt;/a&gt;) I wonder if we should investigate if it&apos;s possible to patch the library to allow $ref linking that is compliant with the JSON schema standard.&lt;/p&gt;</comment>
                                                            <comment id="194931" author="5f8314dfbdef80006f6f572d" created="Thu, 16 Aug 2018 11:13:09 +0000"  >&lt;p&gt;I don&apos;t think we need to do this anymore.. At least I can get stock raml-cop to pass RAML files with 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;RMB-203&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-203&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;$ref should follow the JSON schema spec&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            RMB-203
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
.&lt;/p&gt;</comment>
                                                            <comment id="194934" author="61cd0ca0bce5e00069e98be7" created="Thu, 16 Aug 2018 13:34:08 +0000"  >&lt;p&gt;After the 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;RMB-203&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/RMB-203&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;$ref should follow the JSON schema spec&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            RMB-203
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 fix, things are so much more simple. I can now remove much of the complex verification stuff from this script.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="80499">FOLIO-1027</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="10647">UXPROD-1046</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="56925">RMB-203</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="80284">FOLIO-573</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="80750">FOLIO-1264</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="56807">RMB-109</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzyrgv:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Mon, 6 Aug 2018 06:47:54 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10025" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>[CHART] Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>