[x3d-public] MFString quoting [was: interesting sample]

[yottzumm at gmail.com]

??

[“SFString”, “SFString”]

Not

‘“SFString” “SFString”’

In JSON.

(I know I’m not using the correct characters, oh well).

John


Sent from Mail for Windows 10

From: Roy Walmsley
Sent: Thursday, April 27, 2017 9:00 AM
To: 'Andreas Plesch'; 'Don Brutzman'
Cc: 'X3D Graphics public mailing list'
Subject: Re: [x3d-public] MFString quoting [was: interesting sample]

Hi,

Adding to Andreas comment, we should also remember that the JSON language specification requires strings to be double quoted too.

Roy

From: x3d-public [mailto:x3d-public-bounces at web3d.org] On Behalf Of Andreas Plesch
Sent: 27 April 2017 13:40
To: Don Brutzman <brutzman at nps.edu>
Cc: X3D Graphics public mailing list <x3d-public at web3d.org>
Subject: Re: [x3d-public] MFString quoting [was: interesting sample]

On Wed, Apr 26, 2017 at 10:39 PM, Don Brutzman <brutzman at nps.edu> wrote:
On 4/26/2017 7:10 AM, Andreas Plesch wrote:


On Apr 25, 2017 11:16 PM, "Michalis Kamburelis"

    So

       " ' MFString or SFString ? ' "

    is either
    - an incorrect MFString (you cannot use ' to delimit parts within MFString)

Yes, you are right, that is incorrect.

agreed that is incorrect
But that brings up SFStrings.
When not used as part of an MFString, they still have the double quote requirement while XML allows both single or double quotes.
agreed for SFString values.  Equivalent constructs:

XML
        <WorldInfo title='Hello world!'/> 
        <WorldInfo title="Hello world!"/>

Are you implying that  <WorldInfo title='Hello world!'/> should be a conforming X3D XML encoding (of the WorldInfo node with a title field value) ?
I think you may since the X3D XML encoding does not get to define the outer quotes of an attribute value, meaning that we are all pretty much on the same page.


ClassicVRML and VRML encodings do not permit such variation, simply

        WorldInfo {
          title "Hello world!"
        }

Perhaps the X3D XML encoding spec. should retain a  paragraph on best practices for consistency with the VRML encoding.

-Andreas

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170427/7e294529/attachment-0001.html>