[x3d-public] Registering NavigationInfo types as a means to facilitate formal evolution

[Don Brutzman]

We discussed this today in X3D Working Group meeting.

While registry entries are useful, and indeed we have multiple registry entries that are referenced and exactly matched in X3D Architecture, they do not necessarily speed along developers workflow or user testing.

In general, X3D good practices > Web3D recommend practices > X3D specification changes > potential registry updates.

We will enter this in Mantis, so that it can go on the ISO ballot list, then review/reconcile it later during X3D4 CD ballot review and reconciliation.


On 4/13/2021 10:49 AM, Don Brutzman wrote:
> Ongoing inquiry and experimentation often leads to new NavigationInfo types.  For example:
> 
> ==========================
> [1] X3D4 Architecture, Navigation component, 23.4.4 NavigationInfo
>     https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD/Part01/components/navigation.html#NavigationInfo
> 
> NavigationInfo : X3DBindableNode {
> [...]
> MFString [in,out] type            ["EXAMINE" "ANY"] ["ANY","WALK","EXAMINE","FLY", "LOOKAT","NONE","EXPLORE",...]
> ==========================
> 
> Other types have been suggested/proposed for HELICOPTER, TURNTABLE, etc. but not quite yet accepted.
> 
> Dick had a good idea how we might regularize the future addition of these in X3D4, without requiring a new revision or amendment, by creating a registry of items.  Specifically:
> 
> ==========================
> [2] X3D4 Architecture, Concepts, 4.10 Component and profile registration
>     https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD/Part01/concepts.html#Componentprofilereg
> 
> 4.10 Component and profile registration
> 
> This part of ISO/IEC 19775 allows new concepts to be defined by registration of components, new levels within components, and profiles. Registration shall not be used to modify any existing component, level of a component, or profile. New functionality is registered using the established procedures of the ISO International Register of Items (1). These procedures require the proposer to supply all information for a new registered item except for the level number. The level number (if applicable) is assigned and managed by the ISO International Registration Authority for Graphical Items. Registration shall be according to the procedures in ISO/IEC 9973.
> 
> (1) Contact information for the ISO-designated Registration Authority for Items registered under the ISO/IEC 9973 procedures is available at the ISO Maintenance Agencies and Registration Authorities web site: https://www.iso.org/iso/standards_development/maintenance_agencies.htm
> ==========================
> 
> We currently reference and utilize the following in X3D:
> 
> [3] ISO/IEC JTC 1/SC 24, ISO/IEC 9973 Items Register
>     https://www.iso.org/jtc1/sc24/register
> 
> * Hatchstyle Section
> * Linetype Section
> * Markertype Section
> 
> We might add NavigationInfo type as another registry section matching the existing types.  Adding new values (e.g. HELICOPTER, TURNTABLE, etc.) is straightforward and administered by our SC24 standards subcommittee.
> 
> If this sounds agreeable (or at least plausible!) then we will generate a Mantis issue to cover it, and include that as part of our pending ballot response to SC24 for X3D4 Architecture.
> 
> Looking even further ahead, possibly even profiles and components might be possible, we'll ponder that separately.
> 
> all the best, Don

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