[x3d-public] [x3d] announce: X3D XML schema updates supporting X3D Object Model

John Carlson yottzumm at gmail.com
Thu Sep 22 02:17:08 PDT 2016


Don, given I have my own XML schema, how hard or easy is it to generate my
own object model and Java API?  How does this compare to the OpenAPI
Specification?  (for REST).   Can the networking group leverage any of this
work to create a REST API?

Thanks,

On Sep 22, 2016 1:12 AM, "Don Brutzman" <brutzman at nps.edu> wrote:

> Summary: an excellent X3D XML schema update has been deployed supporting
> the X3D Object Model.  Note that the following schema changes should not
> affect validation of XML-encoded scenes.  Regression testing of scenes in
> the X3D Example Archives will occur next.  All feedback welcome.
>
> ============================================================
> =================
> X3D Schema update activity:
>
> 21 September 2016, brutzman walmsley
> - Significant release update includes all enumeration types and method
> annotations
>   needed for X3D Object Model.
> - Provided strict justifyValues enumeration list to only allow correct
> values
>   for FontStyle/ScreenFontStyle justify attribute
> - Corrected names for r_thelion/l_thelion (omitting "bustpoint")
> - (v3.2+) removed extraneous X3DBoundedObject from X3DRigidJointNode
> - (v3.2+) removed extraneous X3DChildNode from DISEntityTypeMapping
> - (various versions) Add enumeration lists: alignValues, forceOutputValues,
>   fontFamilyValues, intersectionTypeValues, modeMultiTextureValues,
> offsetUnitValues,
>   scaleModeValues, sizeUnitValues, transitionTypeValues, typeValues,
> geoSystemValues,
>   and hanimHumanoidInfoKeyValues.
> - Close review and update of simpleType enumeration lists with attribute
> types,
>   either strictly required (as part of regular XML schema validation) or
>   optionally extendible (multiply defined, with base type listed in
> appinfo).
>   Tested with X3D Object Model and X3D Java SAI autogeneration.
> - Corrected MFString enumerations for appliedParametersValues, labelled
> others.
> - appinfo indication to suggest default value for required (user-specified)
>   values in X3D statements (X3D version/profile, HAnimHumanoid version,
> etc.)
>   Values are still explicitly required for inclusion in XML-encoded scenes.
> - Added metaNameValues as an extendible enumerations list to encourage
> inclusion
>   and consistent use of meta elements describing scene models.
>
> TODO: add regular expressions (regexes) for further validation of field
> content for each data type.
> ============================================================
> =================
>      New. X3D Object Model is autogenerated from X3D XML Schema, and in
> turn is being used to autogenerate other products such as Java SAI Library.
>
>         http://www.web3d.org/specifications/X3DObjectModel-3.3.xml
>
> New, alpha testing. Open-source Java Scene Access Interface (SAI) Library
> (javadoc, example HelloWorldExample.java, TODO list, classes.jar, full.jar,
> and source tree).
>
>         http://www.web3d.org/specifications/java/
>         http://www.web3d.org/specifications/java/javadoc
>         http://www.web3d.org/specifications/java/examples/HelloWorld
> Program.java
>
> ============================================================
> =================
>
> These assets can be found on the X3D Specifications: XML Schema and
> DOCTYPE Validation page.
>
>           http://www.web3d.org/specifications
>
> Full documentation updates have been autogenerated for the XML Schema and
> DOCTYPE, available for X3D versions 3.0 through 3.3 plus experimental 4.0.
> Recommended X3D version is 3.3.
>
>       http://www.web3d.org/specifications/X3dSchemaDocumentation3.
> 3/x3d-3.3.html
>       http://www.web3d.org/specifications/X3dDoctypeDocumentation3.3.html
>
> Corresponding updated assets: lists of all X3D elements and attributes,
> with default values, autogenerated from X3D XML Schema.
>
>      http://www.web3d.org/specifications/AllX3dElementsAttributes3.3.txt
>      http://www.web3d.org/specifications/AllX3dElementsAttributes3.3.xml
>
> Additional updated assets: X3D JSON Schema (manual) and X3D Object Model
> (autogenerated) by Roy Walmsley.
>
>      http://www.web3d.org/specifications/x3d-3.3-JSONSchema.json
> (experimental)
>      http://www.web3d.org/specifications/X3dJsonSchemaDocumentat
> ion3.3/x3d-3.3-JSONSchema.html
>
>      http://www.web3d.org/specifications/X3DObjectModel-3.3.xml
> (experimental)
>
> X3D Schematron Validation and Quality Assurance (QA) rules are also
> regularly updated in concert with these changes.
>
>       http://www.web3d.org/x3d/tools/schematron/X3dSchematron.html
>
> The X3D Working Group also maintains the X3D Graphics Standards:
> Specification Relationships diagram up to date, showing the roadmap for all
> major planned work.
>
>       http://www.web3d.org/specifications/X3dSpecificationRelation
> ships.png
>       http://www.web3d.org/specifications/X3dSpecificationRelation
> ships.pdf
>
> Please note that X3D version 4.0 Schema and DTD are experimental and
> support specification development.
>
> All versions of these assets are maintained under open-source version
> control at
>
>       https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/s
> pecifications
>
> Changes are tested through validation regression testing of 3800+
> open-source X3D scenes.
>
>       X3D Resources: Examples
>       http://www.web3d.org/x3d/content/examples/X3dResources.html#Examples
>
>       X3D Resources: Quality Assurance (QA)
>       http://www.web3d.org/x3d/content/examples/X3dResources.html#
> QualityAssurance
>
> Corresponding updates are also regularly released in the following public
> assets:
>
>       X3D Tooltips
>       http://www.web3d.org/x3d/content/examples/X3dResources.html#Tooltips
>
>       X3D Validator
>       https://savage.nps.edu/X3dValidator
>
>       X3D-Edit Authoring Tool
>       https://savage.nps.edu/X3D-Edit
>
> You can comment on the X3D Specifications in multiple ways.  All feedback
> gets considered.
>
>       mailto:x3d-public at web3d.org
>       http://www.web3d.org/x3d/content/examples/X3dResources.html#Feedback
>       http://www.web3d.org/content/web3d-standards-comment-form
>
> Feedback is always welcome.  Thanks for all test reports and idea
> contributions.
>
> Want to help support this work building the future Web?  The value of
> membership in the Web3D Consortium continues to steadily grow.  Your
> engagement can definitely help, there are lots of cool challenges to
> pursue.  Please consider joining as a company, institution or individual to
> participate.
>
>      http://www.web3d.org/join
>
>      http://www.web3d.org/projects/wish-list
>
> ============================================================
> =================
>
> Have fun with X3D!   8)
>
> 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/brutzma
> n
>
> _______________________________________________
> x3d mailing list
> x3d at web3d.org
> http://web3d.org/mailman/listinfo/x3d_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160922/4b49ee2f/attachment-0001.html>


More information about the x3d-public mailing list