Mailing-List: contact batik-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: batik-dev@xml.apache.org
Received-SPF: pass (hermes.apache.org: domain of herve.girod@club-internet.fr
 designates 194.158.104.44 as permitted sender)
Message-ID: <002001c4929e$447dce00$3f9a2cd5@hppav>
Reply-To: =?iso-8859-1?Q?Herv=E9_Girod?= <herve.girod@club-internet.fr>
From: =?iso-8859-1?Q?Herv=E9_Girod?= <herve.girod@club-internet.fr>
To: <batik-dev@xml.apache.org>
References: <001001c49142$488ebe80$130c223e@hppav>
 <20040903005953.GA13507@mcc.id.au>
Subject: Re: SVG, sXBL and Batik
Date: Sat, 4 Sep 2004 18:43:12 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Cameron McCormack wrote :

> The draft having just been released, I don't think there is much other
> information about sXBL out there yet.  You could look at some RCC
> examples on the web.  RCC was the mechanism proposed in some SVG 1.2
> working drafts to handle custom elements, but was subsequently dropped
> in favour of sXBL.  RCC was partially implemented in ASV6pr1.
>
> Also of course you could come along to SVG Open!  There are apparently
> still places left for the workshops on Tuesday.
>

Unfortunately, it is now too late for me to go there (my fault, I should
have a look at the proceedings long ago...), but I will check later for
abstracts / papers when they will be available.

>
> Yes, if you keep your original contents as XML, sXBL would be one
> possibility for having your format rendered as SVG behind the scenes.
>

This seems very interesting. I will look further on the specification and do
some exercices with sXBL and RCC to better understand it.

And thank you for your answer !

Herve


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