<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.web.zope.plone.plip-advisories">
    <title>gmane.comp.web.zope.plone.plip-advisories</title>
    <link>http://blog.gmane.org/gmane.comp.web.zope.plone.plip-advisories</link>
    <description></description>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq><rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1040"/>
 </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1040">
    <title>[PLIP-Advisories] #10902: New collections (merged plip)</title>
    <link>http://comments.gmane.org/gmane.comp.web.zope.plone.plip-advisories/1040</link>
    <description>&lt;pre&gt;#10902: New collections (merged plip)
---------------------+------------------------------------------------------
 Reporter:  elvix    |       Owner:  elvix
     Type:  PLIP     |      Status:  new  
 Priority:  minor    |   Milestone:  4.1  
Component:  Unknown  |    Keywords:       
---------------------+------------------------------------------------------
 == Motivation ==

 Collections in Plone are the most powerful tool content editors and site
 managers have to construct navigation and site sections. They do, however
 create somewhat of a mess in their current form and are still hard to use.

 This proposal is for supplying a replacement type for collections, using
 ajax/javascript to make a simpler, more sane and streamlined user
 experience for using collections and having a more lightweight backend
 that does not depend on many nested criteria types.

 The criteria (i.e the internal implementation details) of old style
 collections are implemented as Archetypes content types. Thi&lt;/pre&gt;</description>
    <dc:creator>Change notifications for Plone PLIPs on Trac.</dc:creator>
    <dc:date>2010-08-12T21:01:28</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.web.zope.plone.plip-advisories">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.web.zope.plone.plip-advisories</link>
  </textinput>
</rdf:RDF>

