Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: forrest-dev@xml.apache.org
Message-ID: <3DF7A843.7040401@yahoo.de>
Date: Wed, 11 Dec 2002 22:04:03 +0100
From: "J.Pietschmann" <j3322ptm@yahoo.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.2.1) Gecko/20021130
MIME-Version: 1.0
To: forrest-dev@xml.apache.org
Subject: Re: [RT] Adding protocols to links: why?
References: <20021209155925.GA1761@expresso.localdomain>
 <1039453241.9892.28.camel@yum.ot>
 <20021210051539.GA4027@expresso.localdomain>
 <3DF62F07.5030700@outerthought.org> <3DF647C4.8060604@apache.org>
 <20021211075449.GB2801@expresso.localdomain>
 <3DF6F87A.5020505@outerthought.org> <3DF79F50.1010202@yahoo.de>
 <3DF79F50.2020008@outerthought.org>
In-Reply-To: <3DF79F50.2020008@outerthought.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Steven Noels wrote:
> A SchemeResolutionTransformer perhaps?
It will have to be aware of the target format. Will this be
passed together with the input data, or will it be determined
by a sitemap parameter? In the letter case, you'll have to
places where the target format matters:
- the style sheet
- the link resolution transformer.
The syntax should be choosen in a way that a mismatch between
the link resolution target format and the XSLT result (or
the serializer) is pretty obvious.

Another concern: usually one XML source file iss mapped onto
one HTML document, but often several XML source files are
mapped into one PDF document. There may be still several PDF
documents generated. You'll need a convention whether a
certain link maps into an external or an internal PDF link.

J.Pietschmann