[x3d-public] X3D JSON #comment and #sourceText as arrays?

[John Carlson]

Will we be standardizing the schema or usage patterns?  Do we have to wait
until JSON schema is standardized?

John

On Mar 7, 2018 1:26 PM, "John Carlson" <yottzumm at gmail.com> wrote:

> Ajv supports draft 07, but that fact was not reported on the schema site.
>  I can go with draft-07, but I will have to upgrade quite a bit of stuff.
>
> John
>
> On Mar 7, 2018 1:09 PM, "John Carlson" <yottzumm at gmail.com> wrote:
>
>>
>>
>> On Mar 7, 2018 12:45 PM, "Don Brutzman" <brutzman at nps.edu> wrote:
>>
>> We should also look ahead to
>>
>> a. upgrading current X3D JSON Schema to correct internal flaws detected
>> when validating X3D Examples suite (3900+ examples)
>>
>>
>> Yes, I have previous emails on this.
>>
>> b. upgrading current X3D JSON Schema to latest draft-07 version,
>> http://json-schema.org
>>
>>
>> Draft-07 isn't well supported yet.   I suggest draft-06 to get
>> uri-reference support (relative uris).  Plus my schema generator works with
>> draft-06.
>>
>>
>> c. once patterns are established, autogenerating that schema from X3D
>> Unified Object Model
>>
>>
>> Mostly done.   Work needs to be done with Ajv to reduce number of errors
>> associated with @USE.   I believe there is an ajv-errors package.
>>
>> d. taking stock, are we ready to write X3D JSON Encoding Specification?
>>
>> What does that entail?
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20180307/5aa1e6e4/attachment.html>