<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Andreas,<br>
<br>
</div>
<blockquote
cite="mid:CAKdk67s9C3jaXWAQBHWA2KMHv0V2PkKyWQZn2EUEZMRhpoetJg@mail.gmail.com"
type="cite">
<div dir="ltr">I am trying to make cobweb and cobweb_dom html5
compatible, so there is no requirement to use xhtml. xhtml is
not used much at all and may face extinction,
<div><br>
</div>
<br>
<div>The implication for x3d spec. is that it would be better to
have the field definitions in an attribute rather as in child
nodes. Something like</div>
<div><script ... fields=' "inputOnly SFBool isOver"
"outputOnly SFColor diffuseColor_changed" '></div>
<div>That would be also more concise.</div>
</div>
</blockquote>
<br>
This would get really messy if a field were inputOnly MFString and
you needed to specify multiple values in form '"v1" "v2" "v3" ...'.
Also if there are a lot of fields, especially with a large
collection of values (e.g., MFVec3D) you could run into attribute
value character limitations.<br>
<br>
If X3D is to be declarative, then all programming nodes (i.e.,
Script and Shader) should be eliminated and new nodes added that
provide for the most commonly needed features.<br>
<br>
Programmatic access and support can be added through new
capabilities that allow scripts to access scene information, but not
be controlled by the event system. Perhaps some nodes that convert
events back and forth to direct access would solve much of the
problem.<br>
<br>
<div class="moz-signature">-- <br>
<font class="tahoma,arial,helvetica san serif" color="#333366">
<font size="+1"><b>Leonard Daly</b></font><br>
3D Systems & Cloud Consultant<br>
LA ACM SIGGRAPH Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>