[X3D-Public] X3D MultiTexturing - how about we start fixing thespec? :)

Joe D Williams joedwil at earthlink.net
Sat Aug 3 18:06:50 PDT 2013

Hi Michalis,
The only way you get to talk to the specmaster around here is to 
submit your findings as bugs against the spec as entered using the 
Web3D.org Spec comment form.
That is the only way to work with spec bugs in the ISO process.

The step that would finally need to be done is to identify each 
paragraph and sentence by title and number then rewrite the text:

Is: ...
Should be: ...

and offer the replacement or new text directly. Really the goal is 
just a precise set of instructions for the editor so once the comment 
is approved, the editor won't have to think about it, just make the 
correct keystrokes and we can check against the final input.

Good Work on MultiTexture, it is needed for HAnim. Have you verified 
your thoughts by looking at what WebGL does?

Best Regards,

----- Original Message ----- 
From: "Michalis Kamburelis" <michalis.kambi at gmail.com>
To: "x3d-public" <x3d-public at web3d.org>
Sent: Saturday, August 03, 2013 10:01 AM
Subject: [X3D-Public] X3D MultiTexturing - how about we start fixing 
thespec? :)

> Hi,
> While I'm on the roll, I thought that I remind about our page with 
> multi-texturing tests, problems and proposed solutions on:
>   http://castle-engine.sourceforge.net/x3d_multi_texturing.php
> I propose to start applying the proposed fixes to the specification. 
> :) Let's not let this effort go in vain. I'm very willing to prepare 
> the exact prose to the spec (actually, the above page already 
> contains a sensible prose for some fixes). All I need is someone to 
> actually modify the spec to include it.
> Since there were no objections on the list, I assume that people are 
> fine with all the proposed fixes? (And if not, please speak up :).
> Let's at least start with easy fixes, things that have easy (local 
> wording fixes) solutions:
> - problem 2 ("REPLACE" mode is specified as "Arg2", which makes no 
> sense)
> - problem 3 (The meaning of ADDSIGNED and ADDSIGNED2X modes is not 
> clear)
> - problem 5 (It's not specified what channels are inverted by the 
> function="COMPLEMENT" value)
> - problem 6 (two paragraphs should be swapped in spec)
> Regards,
> Michalis
> _______________________________________________
> X3D-Public mailing list
> X3D-Public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org 

More information about the X3D-Public mailing list