Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 41667 invoked from network); 14 Apr 2000 21:33:50 -0000 Received: from dnai-216-15-97-206.cust.dnai.com (HELO kali.betaversion.org) (216.15.97.206) by locus.apache.org with SMTP; 14 Apr 2000 21:33:50 -0000 Received: from apache.org(firewall-68.exoffice.com[207.33.160.68]) (1536 bytes) by kali.betaversion.org via smail with P:esmtp/R:internet/T:smtp (sender: ) id for ; Fri, 14 Apr 2000 14:33:58 -0700 (PDT) (Smail-3.2.0.106 1999-Mar-31 #3 built 1999-Sep-21) Message-ID: <38F78147.A08E8CB2@apache.org> Date: Fri, 14 Apr 2000 13:36:23 -0700 From: "Pier P. Fumagalli" X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; I) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: Cocoon 2.0: proposed battleplan References: <38EFA459.59F07375@apache.org> <38F0E3B0.C2910B9@relativity.yi.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N "Kevin A. Burton" wrote: > > > > > - XLink (Gerard van Enk) > > Pier said: "I don't see how XLink can work on the server side" > > I thought so right off the bat. But it is perfect on the server side. > The linking between documents and them providing a "arch" between all > them could be translated into links for HTML... xLink and XHTML A > links are not compatible so... we should take care of that :) Hmm... The more I see that spec, the more I don't see it fitting in our sitemap model... I mean, we can easily translate the links supplied with XLINK in the sources, _BUT_ that's already done by our URL rewriting engine... Pier -- ---------------------------------------------------------------------- pier: stable structure erected over water to allow docking of seacraft ----------------------------------------------------------------------