[x3d-public] Everit summary, auto-generated versus roy's, X3DUOM min/max for rotation. RFE for X3DUOM
John Carlson
yottzumm at gmail.com
Thu Apr 1 21:06:05 PDT 2021
From what I see online, the @rotation X,Y,Z should be normalized.
Therefore, the min/max ranges in Roy's X3D JSON schema should be maintained.
I will go ahead and copy/paste Roy's rotation sub-schema into the X3D
JSON schema generator, in hopes that the normalization requirements will
fit into X3DUOM at some point.
Thanks,
John
On 4/1/21 8:53 PM, John Carlson wrote:
> Is rotation "normalization" something the schematron finds? This seems
> like something valuable that we don't want to lose.
>
> John
>
> On 4/1/21 8:41 PM, John Carlson wrote:
>> coderextreme at coderextreme-Kubuntu20:~/x3dschema$ grep json-schema
>> javaresults3.txt |wc
>> 88 1259 22590
>> coderextreme at coderextreme-Kubuntu20:~/x3dschema$ grep json-schema
>> javaresults6.txt |wc
>> 5104 63203 1236543
>>
>>
>> So auto-generated schema found 88 validation errors, and roy's schema
>> found 5104 validation errors. Ouch!
>>
>>
>> Can someone confirm this part of Roy's schema? It would seem like
>> X,Y,Z is normalized. I don't see how to generate this from X3DUOM.
>> Are these min/maxes correct? This is like 1800 of the validation
>> errors. I suspect we will find more like this. Today it the first day
>> I've compared auto vs roy with Java. It appears we can enhance
>> X3DUOM in at least this case?
>>
>>
>>
>> "@rotation": {
>> "description": "Validates all four components",
>> "type": "array",
>> "minItems": 4,
>> "maxItems": 4,
>> "items": [
>> {
>> "type": "number",
>> "minimum": -1,
>> "maximum": 1,
>> "default": 0
>> },
>> {
>> "type": "number",
>> "minimum": -1,
>> "maximum": 1,
>> "default": 0
>> },
>> {
>> "type": "number",
>> "minimum": -1,
>> "maximum": 1,
>> "default": 1
>> },
>> {
>> "type": "number",
>> "default": 0
>> }
>> ],
>> "additionalItems": false
>> },
>>
>>
More information about the x3d-public
mailing list