Return-Path: 
 <forrest-dev-return-6258-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 53681 invoked by uid 500); 16 Jul 2003 09:49:19 -0000
Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:forrest-dev-help@xml.apache.org>
list-unsubscribe: <mailto:forrest-dev-unsubscribe@xml.apache.org>
list-post: <mailto:forrest-dev@xml.apache.org>
Reply-To: forrest-dev@xml.apache.org
Delivered-To: mailing list forrest-dev@xml.apache.org
Received: (qmail 53668 invoked from network); 16 Jul 2003 09:49:18 -0000
Received: from fep02.tuttopmi.it (HELO fep02-svc.flexmail.it)
 (212.131.248.101)
  by daedalus.apache.org with SMTP; 16 Jul 2003 09:49:18 -0000
Received: from apache.org ([80.204.154.190]) by fep02-svc.flexmail.it
          (InterMail vM.5.01.05.09 201-253-122-126-109-20020611) with ESMTP
          id <20030716094918.BQRE11015.fep02-svc.flexmail.it@apache.org>
          for <forrest-dev@xml.apache.org>; Wed, 16 Jul 2003 11:49:18 +0200
Message-ID: <3F151F33.2080201@apache.org>
Date: Wed, 16 Jul 2003 11:47:31 +0200
From: Nicola Ken Barozzi <nicolaken@apache.org>
Reply-To: nicolaken@apache.org
Organization: Apache Software Foundation
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: forrest-dev@xml.apache.org
Subject: Re: Adding *.html matcher to xdocs
References: <20030714102540.GA964@expresso.localdomain>
 <002201c34b6c$fd7880f0$fabafea9@KokGesin>
In-Reply-To: <002201c34b6c$fd7880f0$fabafea9@KokGesin>
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


Johan Kok wrote, On 16/07/2003 9.36:

>>So, to keep everyone's blood pressure within healthy limits, how about
>>using a namespace attribute instead of <asis>?  Namespaces
>>are nice and
>>declarative; "this is HTML, treat it how you will".
> 
> That will imply that we will have to get 'transformers' for these at some
> stage, e.g. when one add WAP or WIG outputs as well for mobile usage.

Hmmm, not exactly if I understand what you mean.

We have different steps in this:

  1 XMLification -> 2 translation to DocDTD -> 3 skinning

What we have agreed upon is that (2)->(3) will pass all tags that are 
not DocDTD to the skinning, that can decide if to show them or not.

What AFAIK we will do, is to have the skin pass them as they are if the 
skin creates output with that type, or block them otherwise. For 
example, if I include a FO-namespaced part, it will appear only in 
FOP-generated outputs (PDFs ATM), and not in the html pages.

So if you want your content to be transformed with a WAP skin, you 
should not use html-namespaced tags, as they will not be transformed.

But - using html as a start point, (1)->(2) will transform the html into 
DocDTD, so there you will use html tags, since they will all be 
transformed to DocDTD.

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------