Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 80367 invoked by uid 500); 3 Mar 2003 15:03:58 -0000 Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: forrest-dev@xml.apache.org Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 80335 invoked from network); 3 Mar 2003 15:03:57 -0000 Received: from unknown (HELO pulse.betaversion.org) (217.158.110.65) by daedalus.apache.org with SMTP; 3 Mar 2003 15:03:57 -0000 Received: (qmail 8057 invoked from network); 3 Mar 2003 15:03:57 -0000 Received: from unknown (HELO apache.org) (stefano@80.105.91.155) by pulse.betaversion.org with SMTP; 3 Mar 2003 15:03:57 -0000 Message-ID: <3E636F15.5040504@apache.org> Date: Mon, 03 Mar 2003 16:04:53 +0100 From: Stefano Mazzocchi User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030202 X-Accept-Language: en MIME-Version: 1.0 To: forrest-dev@xml.apache.org Subject: Re: [RT] Dynamic sitemaps References: <20030228122712.GA6105@expresso.localdomain> <3E626458.7000307@apache.org> In-Reply-To: <3E626458.7000307@apache.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Nicola Ken Barozzi wrote: >> - We need a way to assemble a sitemap, pulling in only the snippets that >> the user needs. Eg, most people don't need the community/* support, or >> XML from DTDs, or Forrest's JIRA feed. > > > Yeah. Seems like blocks to me. The block design (as it stands right now) doesn't include sitemap conditioanl capabilities, even if it is possible to do so by providing a way for the sitemap to fall back if a resource doesn't exist. Currently, there are no optional dependencies in the block concept: if a block depends on that block, cocoon has to make it available or that block won't run. We might think of 'optional blocks' and have a precise way for teh sitemap to fall back in case you are referring to a resource that is contained into an 'optional' block. That would make the conditionals if-resource-exists totally transparent and wouldn't require additional semantics, and will make us stay away from the evil dynamic sitemap FS! What do you think? -- Stefano Mazzocchi Pluralitas non est ponenda sine necessitate [William of Ockham] --------------------------------------------------------------------