Return-Path: Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 59898 invoked from network); 5 May 2000 23:16:26 -0000 Received: from pop.systemy.it (194.20.140.28) by locus.apache.org with SMTP; 5 May 2000 23:16:26 -0000 Received: from apache.org (pv9-pri.systemy.it [194.21.255.9]) by pop.systemy.it (8.8.8/8.8.3) with ESMTP id BAA00620 for ; Sat, 6 May 2000 01:16:07 +0200 Message-ID: <39135731.75534091@apache.org> Date: Sat, 06 May 2000 01:20:17 +0200 From: Stefano Mazzocchi Organization: Apache Software Foundation X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; I) X-Accept-Language: en,it MIME-Version: 1.0 To: cocoon-users@xml.apache.org Subject: Re: Relative Stylesheet URIs not fixed? References: <3912DFE7.1F3BF274@denic.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Ulrich Mayring wrote: > > Hi there, > > I just downloaded the latest source from CVS and found that relative > URIs are still not accepted in > instructions. > > Currently cocoon does something confusing and IMHO also a little > dangerous: one time cocoon looks for a file, another time for a URL, all > depending on the string "://" occurring in the given URI. This kills > relative URLs, because they usually don't contain "://" - so they will > always be interpreted as files. Correct, I thought this was the intended behavior. > The W3C has a recommendation out for this problem (see > http://www.w3.org/TR/xml-stylesheet/) and I quote from there: > > "NOTE: Since the value of the href attribute is a URI reference, it may > be a relative URI and it may contain a fragment identifier. In > particular the URI reference may contain only a fragment identifier." Uh, I was wrong :( > I would therefore suggest to implement this recommendation. Any > opinions? It makes sense. Here's the plan: - if the URI is fully specified, it's opened as it is - if the URI is only a fragment, it's treated like relative to the requested resource. is this ok with everyone? NOTE: it could possibly break back compatibility!!!! > Anyway: why has this issue disappeared from the to-do list? Because I thought I fixed the problems. Evidently it is not :) -- Stefano Mazzocchi One must still have chaos in oneself to be able to give birth to a dancing star. Friedrich Nietzsche -------------------------------------------------------------------- Missed us in Orlando? Make it up with ApacheCON Europe in London! ------------------------- http://ApacheCon.Com ---------------------