[x3d-public] X3dToJson.xslt. MFStrings translated improperly GeoMetadata at summaryTwo SFStrings become one in X3D JSON
John Carlson
yottzumm at gmail.com
Wed Oct 25 01:49:32 PDT 2017
Is the problem with the Object Model or the Schema or the Example, for not using keywords? Or do we need to extend the enumeration with additionalEnumerationValuesAllowed="true" in the summary field of GeoMetadata in the object model?
Roy’s schema has minitems = 2. This is not in the object model. Do we need to update the object model twice, and update the examples?
My schema passes this, and it shouldn’t, I don’t think. Do we need to update the object model to reflect pairs of SFStrings? How else can create Schema to validate?
25.3.5:
The summary string array contains a set of keyword/value pairs, with each keyword and its subsequent value contained in a separate string; i.e., there should always be an even (or zero) number of strings. This provides a simple, extensible mechanism to include metadata elements that are human-readable and easy to parse. Table 25.5 specifies a number of keywords and the format that should be used to describe their values. If an unknown keyword is found, it (and its associated value) are ignored.
John
I read this as saying minitems=0 is valid. Even summary=’’
So the examples are wrong for not having 2 SFStrings. And the Object Model should allow additional enumeration values. And my schema generator will not be able to validate this field until I get more info about draft06 of JSON schema, unless Roy has a good idea. And Roy’s schema is “wrong” in that it requires at least two items (but I wouldn’t change it).
Sent from Mail for Windows 10
From: John Carlson
Sent: Wednesday, October 25, 2017 4:20 AM
To: Don Brutzman; Roy Walmsley; x3d-public at web3d.org
Subject: RE: X3dToJson.xslt. MFStrings translated improperly GeoMetadata at summaryTwo SFStrings become one in X3D JSON
No. It looks like the original example should have 2 SFStrings.
John
Sent from Mail for Windows 10
From: John Carlson
Sent: Wednesday, October 25, 2017 4:17 AM
To: Don Brutzman; Roy Walmsley; x3d-public at web3d.org
Subject: X3dToJson.xslt. MFStrings translated improperly GeoMetadata @summaryTwo SFStrings become one in X3D JSON
Problem with X3dToJson.xslt I believe:
Ajv 6.0 Validation failed on C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/Locations/SouthernCaliforniaBorder/N2942E5237DTED2.json
dataPath: X3D > Scene > -children > 0 > GeoMetadata > @summary
value: ["DTED2 N290E520"]
Ajv 6.0 Validation failed on C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/Locations/SouthernCaliforniaBorder/N2942E5238DTED2.json
dataPath: X3D > Scene > -children > 0 > GeoMetadata > @summary
value: ["DTED2 N290E520"]
Ajv 6.0 Validation failed on C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/Locations/SouthernCaliforniaBorder/N2942E5239DTED2.json
dataPath: X3D > Scene > -children > 0 > GeoMetadata > @summary
value: ["DTED2 N290E520"]
Ajv 6.0 Validation failed on C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/Locations/SouthernCaliforniaBorder/N2942E5240DTED2.json
dataPath: X3D > Scene > -children > 0 > GeoMetadata > @summary
value: ["DTED2 N290E520"]
Ajv 6.0 Validation failed on C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/Locations/SouthernCaliforniaBorder/N2943E5237DTED2.json
dataPath: X3D > Scene > -children > 0 > GeoMetadata > @summary
value: ["DTED2 N290E520"]
Ajv 6.0 Validation failed on C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/Locations/SouthernCaliforniaBorder/N2943E5238DTED2.json
dataPath: X3D > Scene > -children > 0 > GeoMetadata > @summary
value: ["DTED2 N290E520"]
Ajv 6.0 Validation failed on C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/Locations/SouthernCaliforniaBorder/N2943E5239DTED2.json
dataPath: X3D > Scene > -children > 0 > GeoMetadata > @summary
value: ["DTED2 N290E520"]
Ajv 6.0 Validation failed on C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/Locations/SouthernCaliforniaBorder/N2944E5237DTED2.json
dataPath: X3D > Scene > -children > 0 > GeoMetadata > @summary
value: ["DTED2 N290E520"]
Ajv 6.0 Validation failed on C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/Locations/SouthernCaliforniaBorder/N2944E5238DTED2.json
dataPath: X3D > Scene > -children > 0 > GeoMetadata > @summary
value: ["DTED2 N290E520"]
Ajv 6.0 Validation failed on C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/Locations/SouthernCaliforniaBorder/N2944E5239DTED2.json
dataPath: X3D > Scene > -children > 0 > GeoMetadata > @summary
value: ["DTED2 N290E520"]
Ajv 6.0 Validation failed on C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/Locations/SouthernCaliforniaBorder/N2944E5240DTED2.json
dataPath: X3D > Scene > -children > 0 > GeoMetadata > @summary
value: ["DTED2 N290E520"]
Ajv 6.0 Validation failed on C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/Locations/SouthernCaliforniaBorder/N2945E5237DTED2.json
dataPath: X3D > Scene > -children > 0 > GeoMetadata > @summary
value: ["DTED2 N290E520"]
Ajv 6.0 Validation failed on C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/Locations/SouthernCaliforniaBorder/N2945E5238DTED2.json
dataPath: X3D > Scene > -children > 0 > GeoMetadata > @summary
value: ["DTED2 N290E520"]
Ajv 6.0 Validation failed on C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/Locations/SouthernCaliforniaBorder/N2945E5239DTED2.json
dataPath: X3D > Scene > -children > 0 > GeoMetadata > @summary
value: ["DTED2 N290E520"]
Ajv 6.0 Validation failed on C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/Locations/SouthernCaliforniaBorder/N2945E5240DTED2.json
dataPath: X3D > Scene > -children > 0 > GeoMetadata > @summary
value: ["DTED2 N290E520"]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20171025/020224cd/attachment.html>
More information about the x3d-public
mailing list