[x3d-public] Discussions of JSON schema: ProtoInstance USE without name

[John Carlson]

Please provide test cases.  I think we will have these 3 subschemas (choose
one):

@USE required, (no other fields allowed)
@name required && @USE required (no other fields allowed)
@name required @USE not allowed (other fields allowed)
Other options not allowed (must have @USE or @name).  Generally, we will
match just one of the subschemas. @containerField is not in JSON.

Does this apply for ProtoInstance and all other nodes with @name field, or
just ProtoInstance?

Let's work through this logically.

I'm assuming at some point you will be creating a stylesheet for generating
schema, or perhaps preferably, validation code.

I think I'm going to wait for draft 8 until Ajv catches up, ns.  I think
Ajv 7 may still be in beta.  There's a promising JavaScript validator that
might be used instead, but it looks like it may require major changes to
code, ns.

Thanks,

John

On Sat, Dec 5, 2020 at 9:56 PM Don Brutzman <brutzman at nps.edu> wrote:

> On 12/5/2020 4:00 PM, John Carlson wrote:
> >
> > If anyone is using the generated X3D Schema (4.0), let me know.
>
> Yes I certainly remain interested John but have a lot of other work on
> X3D4 that must get resolved first.
>
> In general, as we succeeded before, I expect that when we add JSON Schema
> draft 8 validation to the existing X3D JSON encoding, it will remain a
> nearly exact match with X3D XML encoding where node/field
> (element/attribute) data delimiters and some string escaping are the only
> differences.
>
> all the best, Don
> --
> Don Brutzman  Naval Postgraduate School, Code USW/Br
> brutzman at nps.edu
> Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
> X3D graphics, virtual worlds, navy robotics
> http://faculty.nps.edu/brutzman
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20201206/95db6b6f/attachment-0001.html>