¡í Æ÷·³ ¼Ò½Ä
ÀÛ¼ºÀÚ
ÀÛ¼ºÀÏ
2008-04-29 (01:07:08)
±ÛÁ¦¸ñ
[consortium] Standardization Process
Before we go banging our heads against each other, let's figure out what

we really want to happen.



I want to steer this thread to a slightly different course. This is by

no means a repudiation of anyone's arguments, but more back to the

fundamentals. The WG needs to establish exactly what we are trying to

do. The course I want to see is a discussion of the goals of the new

specification process. Alan has laid many of those down in the document

- and if I could find it, I would list them here.



So to have a starting point I have an initial list. Please comment or

revise the list at Will:



1) Specification reflects current technology

2) Specification is consistent and correct

3) Specification is implementable

4) Interoperable browsers (process the same data to produce the same

results)

5) Browsers produce correct (wrt the specification) results

6) Conformance test to ensure and measure the performance of browsers

and other tools





I specifically did not put open-source on this list. It seems that there

are deeper reasons than stating something like "open-source

implementation". Perhaps those reasons are something like

"non-proprietary implementation" or "example implementation" or

"reference implementation". These are all different and I want to get to

the fundamental goals and build from there.





Leonard Daly



[previous messages delete because they were getting too long...]



--

+--------

| Leonard Daly

| Internet Solutions http://realism.com/

| eBusiness Specialist

| X3D Book: http://x3dGraphics.com

+------------------------------

´äº¯ ¼öÁ¤ »èÁ¦ Ãßõ

´ÙÀ½±Û ¸®½ºÆ®




°Ô½Ã¹°:71  ÂʹøÈ£:1/6  ¿À´Ã:20  Àüü:623880 RSS Çǵå 2.0(XML)
ȨÀ¸·Î ´ÙÀ½ÆäÀÌÁö ¸®½ºÆ®
ÀÛ¼ºÀÚ ±ÛÁ¦¸ñ ³»¿ë    °Ë»ö¸®½ºÆ®
¤Ó Æ÷·³¼Ò°³¤Ó Æ÷·³¼Ò½Ä¤Ó Ä¿¹Â´ÏƼ¤Ó °ø°³ÀÚ·á½Ç¤Ó ȸ¿ø°øÀ¯ÀÚ·á½Ç¤Ó ±¹Á¦Ç¥ÁØÈ­Á¦Ç°¤Ó ¸â¹ö½Ê¤Ó X3D Resources¤Ó