Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <4385A876.3020703@apache.org>
Date: Thu, 24 Nov 2005 11:48:06 +0000
From: Ross Gardler <rgardler@apache.org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: dev@forrest.apache.org
Subject: Re: [Summary] Recent proposals around v2
References: <1132697107.13942.8.camel@localhost>
	 <200511232050.01985.diwaker@apache.org> <1132829182.8222.34.camel@localhost>
In-Reply-To: <1132829182.8222.34.camel@localhost>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Thorsten Scherler wrote:
> El mi=C3=A9, 23-11-2005 a las 20:50 -0800, Diwaker Gupta escribi=C3=B3:=

>=20
>>This is not in SVN yet right? Just confirming, because I don't see anyt=
hing=20
>>yet... :)
>=20
>=20
> No, I had a simple transformer that was "just" transforming the
> contracts into the position where it could be found.=20
>=20
> I wanted to check that in but started to clean the code and added
> comments. Doing this I then started to apply recent proposals and it is=

> not that easy. ;-) The challenge is to create a DOM result with SAX
> events out of attributes of contracts and the structure path of the
> hooks and then inject it again in the SAX result stream. I hope to have=

> a first version ready after the weekend.=20
>=20
>=20
>>On Tuesday 22 November 2005 2:05 pm, Thorsten Scherler wrote:
>>
>>>Contract implementation
>>>^^^^^^^^^^^^^^^^^^^^^^^
>>>1) contracts are now standalone, which means that they need to
>>>match=3D"/".
>>
>>Sorry I don't think I follow the terminology here :( By stand-alone, yo=
u are=20
>>implicitly saying that earlier contracts depended on something else?
>=20
>=20
> Yeah, it was dependent from calls in the themer.html.xsl
> (xsl:call-templates name=3D"*-body").=20
>=20
> Now you can see what I mean with following example:
> <map:match pattern=3D"testContract.**">
>   <map:generate src=3D"{dataURI}" />
>   <map:transform src=3D"{contract.xsl}"/>
>   <map:serialize />
> </map:match>

Perhaps the contract production stuff should actually be a generator:

<map:match pattern=3D"testContract.**">
   <map:generate type=3D"contract">
     <map:parameter name=3D"dataURI" value=3D"..."/>
     <map:parameter name=3D"contractURI" value=3D"..."/>
   </map:generate>
   <map:serialize />
</map:match>

Another random idea for consideration, not a recomendation, I'm=20
wondering why you chose not to do it this way ;-)

Ross