<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">According to the standard X3D is
case-sensitive<br>
XML:
<a class="moz-txt-link-freetext" href="http://www.web3d.org/documents/specifications/19776-1/V3.3/Part01/concepts.html#XMLEncoding">http://www.web3d.org/documents/specifications/19776-1/V3.3/Part01/concepts.html#XMLEncoding</a>
(9th paragraph)<br>
VRML:
<a class="moz-txt-link-freetext" href="http://www.web3d.org/documents/specifications/19776-2/V3.3/Part02/concepts.html#ClassicVRMLEncoding">http://www.web3d.org/documents/specifications/19776-2/V3.3/Part02/concepts.html#ClassicVRMLEncoding</a>
(6th paragraph)<br>
Compressed Binary: Use XML as an intermediate step so those rules
apply.<br>
<br>
That does not mean that browser hard-enforce that requirement. <br>
<br>
The X3DOM browser is not case sensitive because HTML tags are not
(in HTML5), though there is a very strong preference for lower
case (even in compound words - e.g., onclick).<br>
<br>
In the non-HTML environment, case sensitivity should apply to
nodes, fields, and keywords (e.g., DEF, USE, IS, etc.)<br>
<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
<br>
</div>
<blockquote
cite="mid:CAKdk67t2aEzxBXLzp=J+nNkeurco1sVpgLvhTB_T7wmhR9XyWw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>Judging from the behaviour of the octaga and
freewrl x3d browsers, node names and (most?) field
names are case insensitive although there is a
preferred form.<br>
</div>
Key words such as ROUTE (and perhaps IMPORT/EXPORT and
others) as well as DEF and USE (key word or field name?)
are, however, case sensitive, eg. need to be in all
capitals.<br>
</div>
There is probably a section in the standard which spells
this out ?<br>
</div>
Probably the intention is to improve human readability. But
if so one could imagine stricter rules for capitalization in
general and even formatting. And ALL CAPITALS is often
considered harmful for readability. Is there another line of
reasoning ? So enforcing case sensitivity in some parts of a
x3d xml encoded file but not others does seem somewhat
arbitrary.<br>
</div>
I ran into this because a nice x3d generator (Andy Yeh's
impressive online logo system) did not quite get the
capitalization conforming (now fixed) which I thought was very
understandable.<br>
</div>
<div>Case sensitivity might play a role in the json effort as
well.<br>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>Andreas<br clear="all">
</div>
<div><br>
-- <br>
<div class="gmail_signature">Andreas Plesch<br>
39 Barbara Rd.<br>
Waltham, MA 02453</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
x3d-public mailing list
<a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>
<a class="moz-txt-link-freetext" href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a>
</pre>
</blockquote>
<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>
X3D Co-Chair on Sabbatical<br>
LA ACM SIGGRAPH Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>