Return-Path: 
 <cocoon-dev-return-20841-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 51952 invoked by uid 500); 10 Jan 2002 21:30:18 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 51933 invoked from network); 10 Jan 2002 21:30:17 -0000
Message-ID: <3C3DFFC4.13EDB4F4@apache.org>
Date: Thu, 10 Jan 2002 21:55:32 +0100
From: Stefano Mazzocchi <stefano@apache.org>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: wap serializer name change?
References: <02011019084400.02132@darthvader>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Chris Newland wrote:
> 
> Hi All,
> 
> Very low priority, but shouldn't the name for the WML serializer be 'wml' and
> not 'wap'?
> 
>    <map:serializer name="wap"    mime-type="text/vnd.wap.wml"
> src="org.apache.cocoon.serialization.XMLSerializer">
>     <doctype-public>-//WAPFORUM//DTD WML 1.1//EN</doctype-public>
>     <doctype-system>http://www.wapforum.org/DTD/wml_1.1.xml</doctype-system>
>     <encoding>ASCII</encoding>
>     <omit-xml-declaration>yes</omit-xml-declaration>
>    </map:serializer>
> 
> Each of the other serializers is named after the content type it produces
> (HTML, VRML, XML ...), but WAP (wireless access protocol) is a transport and
> not a content type?
> 
> E.g. WAP is to WML what HTTP is to HTML.
> 
> I can submit a 2 byte patch if you like ;)

You are right. I wrote this when almost nobody knew what WML was but WAP
was starting to appear. Today is common knowledge for anybody that
worked with it.

Anyway, it's back incompatible. So I'd suggest having *both*, deprecate
it and remove it on Cocoon 2.1 or later.

What do you guys think? anyway, is this really necessary?

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------



---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org