<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">It seems to me that there is some
confusion, though I am not sure if the confused is me or others.
Certainly I made a mistake that Patrick Dahne caught and commented
on (thanks).<br>
<br>
For X3D all string elements must be quoted. This is true in any
text-based encoding. <br>
<br>
Using the field 'string' of the 'Text' node as an example defining
a 2-element MFString field. For Classic VRML it is <br>
<br>
string ["string 1" "string 2"]<br>
<br>
in the XML encoding the elements still need to be quoted. XML (as
many have noted) also requires that all attribute values be
quoted, though it does not care if a single or double quote is
used. So both of the following are legal:<br>
<br>
<Text string='"string 1" "string 2"'/><br>
<Text string=""string 1" "string
2""/><br>
<br>
Note that the XML element produces an MFString with 1 element<br>
<br>
<Text string="'string 1' 'string 2'"/><br>
<br>
In this case the single element would be - 'string 1' 'string 2'<br>
<br>
<br>
Finally, my comment about turning individual elements into
children applied to all MFString fields. I don't think there is
the same value for MFColor, MFVec3f, etc. It certainly does not
apply to S* data types (e.g., SFVec3f). So the translation field
of Transform would remain as SFVec3f and be represented as a
3-tuple of floating-point numbers.<br>
<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</div>
<blockquote
cite="mid:E9A48584B4554D968C768BA6DF4739DE@joe1446a4150a8"
type="cite">
<blockquote type="cite">For instance, in XML all attribute values
must be quoted, unlike HTML
<br>
</blockquote>
<br>
Yeah, so XML can be hard for X3D MFStrings. When web3d started
with X3D XML, XML didn't really know about any MF fields. MFString
equivalents are complicated when user wants legal html double and
single quotes and apostrophies in the displayed text.
<br>
<br>
X3D cannot allow the html legacy unquoted MFString and still
function as expected. So that is only the first of the reasons why
X3D must stick as close as possible to XML and XHTML rules and not
allow the the legacy htmlized unquoted string in any <x3d >
... </x3d> syntax. Leonard has pointed to the most simple
solution for simple encodings that don't allow mulitple data
strings like x3d uses for urls and other MFString fields listing
multiple strings that use coombinations of htmllegal single or
multiple quotes to enclose the MFString and separate the
individual SFStrings, and also character entities and escaping.
<br>
<br>
So, for these string cases, like Leonard suggests, maybe allow an
optional construction that doesn't use MFString form and, if it is
an X3D MFString, then allow listing each or the the strings
individually as elements? However I might fear that is only a
slippery slope to allowing other MFfields (like translation, for
instance) to be broken up and maybe even end up with ultimate
ridiculous simplications that lose strong type checking (like
translation becoming a wrapper for individual x y z element
content).
<br>
<br>
Thanks and Best,
<br>
Joe
<br>
<br>
<br>
<br>
----- Original Message ----- From: "Yves Piguet"
<a class="moz-txt-link-rfc2396E" href="mailto:yves.piguet@gmail.com"><yves.piguet@gmail.com></a>
<br>
To: "Don Brutzman" <a class="moz-txt-link-rfc2396E" href="mailto:brutzman@nps.edu"><brutzman@nps.edu></a>
<br>
Cc: "Andreas Plesch" <a class="moz-txt-link-rfc2396E" href="mailto:andreasplesch@gmail.com"><andreasplesch@gmail.com></a>; "X3D
Graphics public mailing list" <a class="moz-txt-link-rfc2396E" href="mailto:x3d-public@web3d.org"><x3d-public@web3d.org></a>;
"Leonard Daly" <a class="moz-txt-link-rfc2396E" href="mailto:Leonard.Daly@realism.com"><Leonard.Daly@realism.com></a>
<br>
Sent: Wednesday, March 15, 2017 8:08 AM
<br>
Subject: Re: [x3d-public] MFString quotes
<br>
<br>
<br>
<blockquote type="cite">
<blockquote type="cite">On 15 Mar 2017, at 15:35, Don Brutzman
<a class="moz-txt-link-rfc2396E" href="mailto:brutzman@nps.edu"><brutzman@nps.edu></a> wrote:
<br>
<br>
Short summary:
<br>
<br>
a. The abstract specification is unambiguous.
<br>
</blockquote>
<br>
Imo, XML applications like the XML encoding of X3D shouldn't
restrict XML, or they shouldn't claim to be XML. So 19776-1
should be modified.
<br>
<br>
<blockquote type="cite">b. Different file and language encodings
have similar yet different rules about escaping quotes.
<br>
c. We have no control over external equivalences, since user
agents decide independently (e.g. " and ")
<br>
</blockquote>
<br>
I agree.
<br>
<br>
<blockquote type="cite">d. Round-tripping is difficult/tedious
but possible in every case. Repeatable code blocks can help.
<br>
</blockquote>
<br>
Usually possible for a given implementation. If you think
round-tripping is useful, one should refer to a canonical XML
representation. See <a class="moz-txt-link-freetext" href="https://www.w3.org/TR/xml-c14n">https://www.w3.org/TR/xml-c14n</a>
<br>
<br>
Same for JSON. Same for Classic (standardized pretty-printed?)
<br>
<br>
<blockquote type="cite">I think one relaxation might be possible
where an unquoted MFString value might be treated as a single
SFString value in the array.
<br>
</blockquote>
<br>
I'd rather not. The more permissive, the more difficult it will
be to fix design oversights later if there are. XML isn't nice
to write by hand anyway, one shouldn't try to accept sloppy
code.
<br>
<br>
For instance, in XML all attribute values must be quoted, unlike
HTML. Being lenient here would go against this design choice.
<br>
<br>
Best,
<br>
<br>
Yves
<br>
<br>
<br>
_______________________________________________
<br>
x3d-public mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>
<br>
<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> </blockquote>
<br>
<br>
</blockquote>
<br>
<p><br>
</p>
<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>