[x3d-public] x3d-3.3-JSONSchema documentation available

Tue Dec 6 02:39:56 PST 2016

Hi Yves,

Thank you for your comments. You made five, which I will respond to.

1)      "connect" only listed within "IS": Was it intentional?  It wasn't
intentional to not list it separately. However, it is only used by IS. But
where is it in the abstract specification 19775-1? Hadn't noticed before,
but I'm not finding it. This seems to be an omission that needs
rectification. Thanks for drawing attention to this topic.

2)      JSON is planned for 19776 Part 5: Will there be a Part 4? Yes, a
part 4 was planned first, although it has been overtaken in terms of
progress by JSON. Part 4 was planned to be the Efficient Binary Encoding.
See http://www.web3d.org/specifications/X3dSpecificationRelationships.png.

3)      Use of the distinct prefixes "@" and "-": I'll let Don answer this
one more fully. However, below is the section from the draft standard (which
is at the stage where we are working to get approval for release to the
public for review - see also comment 5)) which covers this important point :

4)      Rationale for use of prefix "@": We tried to keep the prefix for use
on fields, or properties of "statements" that are like fields. "Statements"
do not get a prefix.

5)      Access to draft standard: Sorry, but the draft standard is currently
only available to members. This is a requirement of the Consortium bylaws
which arises because of possible IPR issues (it applies to all new drafts).
There are procedures for making it public. It is hoped to do that soon.

----------------------------------------------------------------------------
----------------------------------------------------------------------------
----------------------------------------------------------------------------

4.3.1.3 Encoding of field names

Each node type defines the names and types of it's fields. These can be
broadly classified into two main field types:

1.	Children fields: These fields are either SFNode or MFNode type, and
their values are other nodes.
2.	Value fields: These are all the remaining field types.

As defined in 4.3.2.10 Field property syntax
<file:///E:/Software%20Development/HTML5%20Training/Github/X3D/ISO-IEC%20197
76/ISO-IEC%2019776-5/ISO-IEC%2019776-5%20V3.3/ISO-IEC%2019776-5%20V3.3%20WD1
/Part05/concepts.html#FieldPropertySyntax>  a field statement consists of
the encoded name of the field, a comma separator, and then the value or
values. The field name shall always be a JSON string. To disambiguate
language constructs that are not X3D nodes or structural statements a field
name shall be prefixed as follows, with no change to the capitalization of
the field name:

1.	Children fields: The "-" character.
2.	Value fields: The "@" character.

EXAMPLE: The Box node has three fields, namely metadata, size, and solid, as
defined in the node signature in 13.3.1 Box of ISO/IEC 19775-1
<file:///E:/Software%20Development/HTML5%20Training/Github/X3D/ISO-IEC%20197
76/ISO-IEC%2019776-5/ISO-IEC%2019776-5%20V3.3/ISO-IEC%2019776-5%20V3.3%20WD1
/Part05/references.html#I19775_1> . When encoded into JSON these three field
names are encoded as "-metadata", "@size", and "@solid" respectively.

----------------------------------------------------------------------------
----------------------------------------------------------------------------
----------------------------------------------------------------------------

Thanks again,

All the best,

Roy

-----Original Message-----
From: x3d-public [mailto:x3d-public-bounces at web3d.org] On Behalf Of Yves
Piguet
Sent: 06 December 2016 07:50
To: Don Brutzman <brutzman at nps.edu>
Subject: Re: [x3d-public] x3d-3.3-JSONSchema documentation available

Many thanks for these links, Don. Somme comments:

> On 6 Dec 2016, at 01:29, Don Brutzman < <mailto:brutzman at nps.edu>
brutzman at nps.edu> wrote:

> 

> Documentation (generated by XML Spy) is now available with figures:

> 

>
<http://www.web3d.org/specifications/X3dJsonSchemaDocumentation3.3/x3d-3.3-J
SONSchema.html>
http://www.web3d.org/specifications/X3dJsonSchemaDocumentation3.3/x3d-3.3-JS
ONSchema.html

"connect" is missing from this list; it can only be found in the description
of "IS". I don't know it it's intended.

> More about X3D JSON Encoding can be found at

> 

>              <http://www.web3d.org/wiki/index.php/X3D_JSON_Encoding>
http://www.web3d.org/wiki/index.php/X3D_JSON_Encoding

Section
<http://www.web3d.org/wiki/index.php/X3D_JSON_Encoding#Standardization>
http://www.web3d.org/wiki/index.php/X3D_JSON_Encoding#Standardization states
"The most probable place to put it is as a new Part 5 to ISO/IEC 19776. In
this manner, it would correspond to the XML, Classic VRML, and Compressed
Binary encodings". Will there be a part 4?

Is there a rationale available for two distinct prefixes "@" and "-"? Except
for a closer match to the XML encoding, but I would humbly object to that:
per
<http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/concepts.
html#Dataencodings>
http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/concepts.h
tml#Dataencodings "concrete data encodings for X3D shall conform to this
abstract specification" (in ISO/IEC 19775), so peculiarities of one encoding
shouldn't be inherited by another one. Or the JSON encoding should be
clearly defined as a sub-encoding of the XML encoding.

Is there a rationale available for a prefix in front of some (e.g.
"@protoField"), but not all (e.g. "connect") the properties of elements
which are not X3D nodes?

> Upcoming X3D Working Group review efforts include consideration of

> 

>             Initial working draft:  X3D JSON Encoding

>             ISO-IEC 19776-5 V3.3 WD1/

>
<https://github.com/Web3DConsortium/X3D/tree/master/ISO-IEC%2019776/ISO-IEC%
2019776-5/ISO-IEC%2019776-5%20V3.3>
https://github.com/Web3DConsortium/X3D/tree/master/ISO-IEC%2019776/ISO-IEC%2
019776-5/ISO-IEC%2019776-5%20V3.3

404 for non-members :(

Thanks,

Yves

_______________________________________________

x3d-public mailing list

 <mailto:x3d-public at web3d.org> x3d-public at web3d.org

 <http://web3d.org/mailman/listinfo/x3d-public_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/20161206/77c864cd/attachment.html>