[x3d-public] AllX3dElementsAttributes.xml listing of all X3D elements and attributes
Joe D Williams
joedwil at earthlink.net
Sat Nov 28 20:52:25 PST 2015
Hi Don,
good info here, and a fine goal.
> basis for tools that want to know the entire X3D vocabulary quickly.
Looking at 30 - Event Utilities component,
BooleanFilter : X3DChildNode {
SFBool [in] set_boolean
SFNode [in,out] metadata NULL [X3DMetadataObject]
SFBool [out] inputFalse
SFBool [out] inputNegate
SFBool [out] inputTrue
}
this list:
<BooleanFilter containerField="children" />
and
BooleanSequencer : X3DSequencerNode {
SFBool [in] next
SFBool [in] previous
SFFloat [in] set_fraction
MFFloat [in,out] key [] (-∞,∞)
MFInt32 [in,out] keyValue [] [0|1]
SFNode [in,out] metadata NULL [X3DMetadataObject]
SFBool [out] value_changed
}
vs
<BooleanSequencer key="" keyValue="" containerField="children" />
Seems like I want my complete vocabulary to include all interfaces of
any node.
I probably understand why possible contained nodes aren't listed,
<Appearance containerField="appearance" />
Appearance : X3DAppearanceNode {
SFNode [in,out] fillProperties NULL [FillProperties]
SFNode [in,out] lineProperties NULL [LineProperties]
SFNode [in,out] material NULL [X3DMaterialNode]
SFNode [in,out] metadata NULL [X3DMetadataObject]
MFNode [in,out] shaders [] [X3DShaderNode]
SFNode [in,out] texture NULL [X3DTextureNode]
SFNode [in,out] textureTransform NULL [X3DTextureTransformNode]
}
but what about all my gozintas and gozoutas that I might want to know
about?
> the entire X3D vocabulary ,,,
of [in,out]s but not [in]s or [out]s, or contained nodes.
Also, this list makes all elements look empty.
Thanks and Best,
Joe
----- Original Message -----
From: "Don Brutzman" <brutzman at nps.edu>
To: "Roy Walmsley" <roy.walmsley at ntlworld.com>
Cc: "X3D Graphics public mailing list" <x3d-public at web3d.org>
Sent: Friday, November 27, 2015 4:16 PM
Subject: [x3d-public] AllX3dElementsAttributes.xml listing of all X3D
elements and attributes
> As discussed a number of times on the X3D working group
> teleconferences, attached is an XML file listing all X3D elements
> and attributes.
>
> Had to add a root element so that it would be valid XML.
>
> Caveat: this is NOT a valid X3D scene, nor will it ever be.
>
> Motivation. The intent is to provide this file resource as a
> simpler basis for tools that want to know the entire X3D vocabulary
> quickly. The X3D Schemas are quite thorough and as close as
> possible to the authoritative reference, which is actually the X3D
> Abstract specification. The schemas describe an object-oriented
> model, however, so we use the same XML stylesheet which creates HTML
> for the XML Encoding annexes to produce this XML.
>
> Roy, production note: BuildSpecificationXmlEncodingFromSchema.xslt
> code blocks are at the end. TODO more refactoring is planned but
> this is a good start and appears to be mostly complete.
>
> Filename sound OK? Regular destination is part of the stylesheets
> directory, updates will appear at:
>
> http://www.web3d.org/x3d/stylesheets/AllX3dElementsAttributes.xml
>
> Was thinking that maybe we should also make a text version to simply
> browsing, inspection & modification. Come to think of it, that
> would be a good example stylesheet that walks this XML file to
> produce something else. 8)
>
> Request to all: please alert us if you "see anything missing" and we
> will dial in the final version of this new product.
>
> Have fun with XML X3D!
>
> 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
>
--------------------------------------------------------------------------------
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
More information about the x3d-public
mailing list