Ok, I thought #droolsdev was ok too. Sorry about that. <div>The idea to have a &#39;name&#39; and a &#39;description&#39; attribute in &lt;Resource&gt; elements inside a change-set is to tag them or to add them some human-friendly information so you can refer to it not using the URL or the name of the asset (could be duplicated in different packages), but with a name and a description.</div>

<div>These changes are 100% end-users oriented, that is why I put those attributes in API. End users applications (like Guvnor) could take advantages on these new attributes.</div><div><br></div><div>So, a change-set now could look like this (the new attributes are not mandatory):</div>

<div><br></div><div><div>&lt;change-set&gt;            </div><div>    &lt;add&gt;</div><div>      &lt;resource <b>name=&quot;Loan Rules&quot; description=&quot;Rules about loans&quot;</b> type=&quot;DRL&quot; source=&quot;<a href="http://someHost:1234/someDRLResource.drl">http://someHost:1234/someDRLResource.drl</a>&quot;/&gt;      </div>

<div>      &lt;resource <b>name=&quot;Risk Rules&quot; description=&quot;Rules about Risk evaluation&quot;</b> type=&quot;DRL&quot; source=&quot;<a href="http://someHost:1234/someOtherDRLResource.drl">http://someHost:1234/someOtherDRLResource.drl</a>&quot;/&gt;</div>

<div>    &lt;/add&gt;</div><div>&lt;/change-set&gt;</div></div><div><br></div><div>These attributes can also be used in Spring&#39;s configuration:</div><div><br></div><div><div>&lt;drools:kbase id=&quot;kbase1&quot; node=&quot;node1&quot;&gt;</div>

<div>    &lt;drools:resources&gt;     </div><div>        &lt;resource <b>name=&quot;Loan Rules&quot; description=&quot;Rules about loans&quot;</b> type=&quot;DRL&quot; source=&quot;<a href="http://someHost:1234/someDRLResource.drl">http://someHost:1234/someDRLResource.drl</a>&quot;/&gt;      </div>

<div>        &lt;resource <b>name=&quot;Risk Rules&quot; description=&quot;Rules about Risk evaluation&quot;</b> type=&quot;DRL&quot; source=&quot;<a href="http://someHost:1234/someOtherDRLResource.drl">http://someHost:1234/someOtherDRLResource.drl</a>&quot;/&gt;      </div>

<div>    &lt;/drools:resources&gt;</div><div>&lt;/drools:kbase&gt;</div></div><div><br></div><div>WDYT?<br clear="all"><br></div><div>Best Regards,</div><div><br>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br><br>Esteban Aliverti<br>

- Developer @ <a href="http://www.plugtree.com" target="_blank">http://www.plugtree.com </a><br>- Blog @ <a href="http://ilesteban.wordpress.com" target="_blank">http://ilesteban.wordpress.com</a><br>
<br><br><div class="gmail_quote">On Mon, Sep 12, 2011 at 6:25 AM, Mark Proctor <span dir="ltr">&lt;<a href="mailto:mproctor@codehaus.org">mproctor@codehaus.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

Shoudn&#39;t name and description be on InternalResource, not on Resource?<br>
<br>
I think it&#39;s time to put a restriction on changes to &quot;-api&quot;. Feel free<br>
to change core/compiler etc, but if you want to change -api we&#39;ll need<br>
to propose it here.<br>
<br>
Mark<br>
<br>
_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
</blockquote></div><br></div>