[ODE] XML ODE Data Interchange Format (revision 5)

[George Birbilis]

do checkout www.web3d.org (site is under reworking at the moment) for the
X3D spec (VRML3.0). It supports an XML encoding too apart from the classic
VRML one and a binary encoding is under way

VRML2.0 is an ISO spec and X3D is under ISO processes already

you can get ideas (and discuss on the VRML list too) about what they chose
to do with such issues

plus transcoding to/from X3D and more interoperation with it would be very
cool I think

-----
George Birbilis (birbilis at kagi.com)
http://www.kagi.com/birbilis
--------------
----- Original Message ----- 
From: "Jon Watte" <hplus-ode at mindcontrol.org>
To: "William Denniss" <lists at omegadelta.net>; "Nate W" <coding at natew.com>
Cc: <ode at q12.org>
Sent: Monday, March 15, 2004 7:09 PM
Subject: RE: [ODE] XML ODE Data Interchange Format (revision 5)


>
> > The XSL argument is a very good one, and one which solves the whole
> > ordering format argument (ie. being able to specify x,z,y) without the
> > need for smarter importers.
>
> There is a huge time penalty for putting each vertex in an element.
>
> Do you ACTUALLY intend to process your vertex data with XSLT? I mean,
enough to make up for the fact that the format just won't scale for large
level loads?
>
> Big arrays of data works better. I'd be happier if you could specify some
number of extra elements per vertex (and per triangle!) but I think
element-per-vertex is WAY over-flexible (much worse than allowing X, Y and Z
to be in different orders in a format specifier, which I'm also not for :-).
>
> Anyway, you does what you does. Except I believe it won't scale if you do
it in a particular way.
>
> Cheers,
>
> / h+
>
>
> _______________________________________________
> ODE mailing list
> ODE at q12.org
> http://q12.org/mailman/listinfo/ode
>