[x3d-public] Leading and trailing comments in X3D JSON loader...how to handle

[John Carlson]

Note that any leading and trailing comments are not removed using my
loader, so they will accumulate.  I will need to go into parent DOM object,
check for comments, and remove them.  I don't think I want to remove all
children, but that's a possibility too.  What do the users want?
On Dec 1, 2015 2:50 AM, "John Carlson" <yottzumm at gmail.com> wrote:

> Leonard, we were trying to capture comments into json with a special key
> "#comment" however I have noticed issues with leading and trailing
> comments.  If I recall right, they cause the JSON parse to fail, or perhaps
> just my loader.  I haven't investigated it enough to be sure yet.  I
> imagine that any JSON schema will have to incorporate comments...should be
> interesting.  There may be some way to represent that in schema at a global
> level, not sure.
>
> John
> On Dec 1, 2015 1:25 AM, "Leonard Daly" <web3d at realism.com> wrote:
>
>> Comments are not allowed in a JSON file (I used
>> http://stackoverflow.com/questions/244777/can-i-use-comments-inside-a-json-file
>> and the references contained in the page, especially to json.org, RFC
>> 4627 and RFC 7159).
>>
>> Does this approach puts comments into JSON data elements? If so, that
>> means comments have been elevated from text in the file to data in the
>> file. If this approach is to capture comments throughout the original
>> non-JSON file, does that mean the data model between a JSON-encoded scene
>> and an XML-encoded scene is significantly different?
>>
>> Out of curiosity, does the compressed binary encoding capture comments
>> from anyplace in the original scene file? If so, does the data model that
>> is stored in the CBE file match that of the original file?
>>
>>
>> Leonard Daly
>>
>>
>>
>>
>> On 11/30/2015 9:27 PM, Don Brutzman wrote:
>>
>> On 11/30/2015 4:23 PM, John Carlson wrote:
>>
>> There might be a comment before the first x3d object.
>>
>>
>> very interesting observation!
>>
>> - since JSON does not support comments, and
>> - since we have come up with an allowable approach for comments inside an
>> X3D scene graph that allows round-trip support with other encodings,
>>
>> then
>>
>> - we probably ought to deliberately avoid capturing or including any
>> comments in the JSON encoding that might appear outside the "X3D" object
>> declaration.
>>
>> all the best, Don
>>
>>
>>
>> --
>> *Leonard Daly*
>> X3D Co-Chair
>> Cloud Consultant
>> President, Daly Realism - *Creating the Future*
>>
>> _______________________________________________
>> x3d-public mailing list
>> x3d-public at web3d.org
>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20151201/dca5fbdb/attachment.html>