VRML - is x3d specification aprobbed by ISO?

Author

is x3d specification aprobbed by ISO?

Jordi R. Cardona

2004-07-20, 10:51 pm

Hello.

I'd like to know if ISO has approbed the X3d spec. Do you know it?

Jordi.

Joe D Williams

2004-08-14, 4:17 am

"Jordi R. Cardona" <kioto-25@jazzfree.com> wrote in message
news:cd6r5l$70m$1@news.ya.com...
> Hello.
>
> I'd like to know if ISO has approbed the X3d spec. Do you know it?
>
> Jordi.
>
>

Hi Jordi,
The short respose - Yes.
The long response - see following.

============

X3D International Standards and Draft Standards

1 ============

Abstract Nodes and Interfaces
X3D framework & SAI - ISO/IEC 19775:200x
2004 Aug. ISO/IEC Adopted Final Draft
Some very minor changes not yet public.

Part 1 defines the abstract X3D framework
and the standardized components and profiles.

Part 2 defines the scene access interface (SAI)
that can be used to interact with X3D worlds both
from within the worlds or from external programs.

And really, the changes are minor from what is
there. Any specific questions?

My favourite abstract spec pages:

http://www.web3d.org/x3d/specifications/
ISO-IEC-19775-FDIS-X3dAbstractSpecification/
Part01/nodeIndex.html

http://www.web3d.org/x3d/specifications/
ISO-IEC-19775-FDIS-X3dAbstractSpecification/
Part02/vrml97.html

2 =========

UTF-8 Text Files
X3D encodings - ISO/IEC 19776:200x
Mostly Final Draft almost ready for final submission.

Part 1 specifies the encoding of X3D files using the
Extensible Markup Language (XML).

Part 2 specifies the encoding of X3D using the
Classic VRML encoding.

Mostly final draft. At this precise moment the
Classic VRML - where the text is presented in
what is very close to the VRML97 style - is
Final Draft and on the verge of being accepted.
Please notice that on this day, there is a
different link to get to this updated version of Part 2.

The XML spec text is just a bit 'behind' on this day
due to minor delays but the stuff works fine.

My favorite encodings spec pages (so far):

http://www.web3d.org/x3d/specifications/
ISO_IEC_19776-2-FDIS-X3dEncodings/
Part02/examples.html

http://www.web3d.org/x3d/specifications/
ISO_IEC_19776-2-FDIS-X3dEncodings/
Part02/EncodingOfNodes.html

Still some minor updates to match the final Abstract,
but close. Comments?

3 ==============

ECMAScript and Java Implementations
X3D language bindings - ISO/IEC 19777:200x
How the X3D funcionality is implemented for
internal script nodes and for
external application access.

Part 1 specifies the bindings for ECMAScript.

Part 2 specifies the bindings for Java.

You really want to see the latest update of this
because several comments have been made to match it
to Part 2 of the Abstract. Unfortunately it is
not now ready for the public viewing, evidently.
However, there are some ECMAScript examples in the
encodings spec.

My favorite bindings links:

http://www.web3d.org/x3d/specifications/
ISO-IEC-19777-FCD-X3dLanguageBindings/
Part1/concepts.html#GeneralConcepts

http://www.web3d.org/x3d/specifications/
ISO-IEC-19777-FCD-X3dLanguageBindings/
Part2/concepts.html#FieldAccess

Overall, the objective to unite internal and external
access rules seems like it may work.
I've been trying to work with it so give a yell
if you wish to see updated versions of the
current examples.

=================

So these are the basic specs.
Since ISO/IEC has accepted the Abstract spec
this month and are expected to accept
the Classic VRML encoding any week now,
we can pretty well say that X3D is a
done deal that is moving forward and
will prevail as a real time interactive distributed
3D transport standard having both
authortime and runtime specifications.

How can you tell if your favorite 3D browser does X3D?
Go to the encodings part2 examples link listed
above and click on the link in the text,
maybe just like you did with the VRML97 spec.
If your browser loads the things,
then you are already WWW X3D.

Even more simple, go to:

http://www.web3d.org/x3d/specifications/
ISO_IEC_19776-2-FDIS-X3dEncodings/
Part02/Examples/

and have a look.

Thanks and Best Regards,
Joe

Joe D Williams

2004-08-16, 12:17 pm

Joe D Williams

2004-08-17, 11:16 pm

"Joe D Williams" <joedwil@earthlink.net> wrote in message
news:1ufTc.20457$9Y6.17567@newsread1.news.pas.earthlink.net...
>
> "Jordi R. Cardona" <kioto-25@jazzfree.com> wrote in message
> news:cd6r5l$70m$1@news.ya.com...
>
> Hi Jordi,
> The short respose - Yes.
> The long response - see following.

I thought some of this would get some sorts of
responses. The main idea I can get out of the
spec is that what you see, with small in-process
refinements and great opportunities for extension,
is what we have. And, the spec has some
built-in features that may make it easy to use.

For example, I should have simplified

> X3D framework & SAI - ISO/IEC 19775:200x
> Part 1 defines the abstract X3D framework
> and the standardized components and profiles.

to:
19775 Part 1 describes the authoring and run times and
lists the Node and Fields

but the link is great!

http://www.web3d.org/x3d/specifications/
ISO-IEC-19775-FDIS-X3dAbstractSpecification/
Part01/nodeIndex.html

caamon, paste the thing together and go there.

What Hoo! an alpha list of nodes.
Go ahead, scroll down and find one that
looks familiar and select it. Look at the
fields and default values.
You can copy and paste field names
into your source code.
Very familiar, right?

If the field access types and variable types
make you uncomfortable, forget them.
Or notice that what you learned has not
changed deeply, just a tad more complete.
Maybe look at the hierarchy diagram in Section 4?
There is another complete listing of the nodes.

Thanks and Best Regards,
Joe

>
> ============
>
> X3D International Standards and Draft Standards
>
> 1 ============
>
> Abstract Nodes and Interfaces
> X3D framework & SAI - ISO/IEC 19775:200x
> 2004 Aug. ISO/IEC Adopted Final Draft
> Some very minor changes not yet public.
>
> Part 1 defines the abstract X3D framework
> and the standardized components and profiles.
>
> Part 2 defines the scene access interface (SAI)
> that can be used to interact with X3D worlds both
> from within the worlds or from external programs.
>
> And really, the changes are minor from what is
> there. Any specific questions?
>
> My favourite abstract spec pages:
>
> http://www.web3d.org/x3d/specifications/
> ISO-IEC-19775-FDIS-X3dAbstractSpecification/
> Part01/nodeIndex.html
>
> http://www.web3d.org/x3d/specifications/
> ISO-IEC-19775-FDIS-X3dAbstractSpecification/
> Part02/vrml97.html
>
> 2 =========
>
> UTF-8 Text Files
> X3D encodings - ISO/IEC 19776:200x
> Mostly Final Draft almost ready for final submission.
>
> Part 1 specifies the encoding of X3D files using the
> Extensible Markup Language (XML).
>
> Part 2 specifies the encoding of X3D using the
> Classic VRML encoding.
>
> Mostly final draft. At this precise moment the
> Classic VRML - where the text is presented in
> what is very close to the VRML97 style - is
> Final Draft and on the verge of being accepted.
> Please notice that on this day, there is a
> different link to get to this updated version of Part 2.
>
> The XML spec text is just a bit 'behind' on this day
> due to minor delays but the stuff works fine.
>
> My favorite encodings spec pages (so far):
>
> http://www.web3d.org/x3d/specifications/
> ISO_IEC_19776-2-FDIS-X3dEncodings/
> Part02/examples.html
>
> http://www.web3d.org/x3d/specifications/
> ISO_IEC_19776-2-FDIS-X3dEncodings/
> Part02/EncodingOfNodes.html
>
> Still some minor updates to match the final Abstract,
> but close. Comments?
>
> 3 ==============
>
> ECMAScript and Java Implementations
> X3D language bindings - ISO/IEC 19777:200x
> How the X3D funcionality is implemented for
> internal script nodes and for
> external application access.
>
> Part 1 specifies the bindings for ECMAScript.
>
> Part 2 specifies the bindings for Java.
>
> You really want to see the latest update of this
> because several comments have been made to match it
> to Part 2 of the Abstract. Unfortunately it is
> not now ready for the public viewing, evidently.
> However, there are some ECMAScript examples in the
> encodings spec.
>
> My favorite bindings links:
>
> http://www.web3d.org/x3d/specifications/
> ISO-IEC-19777-FCD-X3dLanguageBindings/
> Part1/concepts.html#GeneralConcepts
>
> http://www.web3d.org/x3d/specifications/
> ISO-IEC-19777-FCD-X3dLanguageBindings/
> Part2/concepts.html#FieldAccess
>
> Overall, the objective to unite internal and external
> access rules seems like it may work.
> I've been trying to work with it so give a yell
> if you wish to see updated versions of the
> current examples.
>
> =================
>
> So these are the basic specs.
> Since ISO/IEC has accepted the Abstract spec
> this month and are expected to accept
> the Classic VRML encoding any week now,
> we can pretty well say that X3D is a
> done deal that is moving forward and
> will prevail as a real time interactive distributed
> 3D transport standard having both
> authortime and runtime specifications.
>
> How can you tell if your favorite 3D browser does X3D?
> Go to the encodings part2 examples link listed
> above and click on the link in the text,
> maybe just like you did with the VRML97 spec.
> If your browser loads the things,
> then you are already WWW X3D.
>
> Even more simple, go to:
>
> http://www.web3d.org/x3d/specifications/
> ISO_IEC_19776-2-FDIS-X3dEncodings/
> Part02/Examples/
>
> and have a look.
>
> Thanks and Best Regards,
> Joe
>
>
>

Joe D Williams

2004-08-19, 10:38 pm

Joerg Scheurich aka MUFTI

2004-08-25, 6:17 am

> X3D International Standards and Draft Standards

> And really, the changes are minor from what is
> there. Any specific questions?

What are the changes in the NURBS component relative to

http://www.web3d.org/x3d/specificat...ents/nurbs.html

?

NURBS was often a moving target in the X3D drafts and (very much more ugly)
some (most ?) of them were not compatible to ISO/IEC 14772-2:2002 8-(

so long
MUFTI
--
A number of the Windows-based application programming interfaces (APIs) that
are documented as accepting only a module handle are defined incorrectly.
(aus einer M$Windows Dokumentation)

Joe D Williams

2004-08-25, 6:17 am

> What are the changes in the NURBS component relative to
>
>
http://www.web3d.org/x3d/specificat...tractSpecificat
ion/Part01/components/nurbs.html
>
> ?
>

From what I have seen, the current spec is it.

>
> NURBS was often a moving target in the X3D drafts and (very much more ugly)
> some (most ?) of them were not compatible to ISO/IEC 14772-2:2002 8-(
>

Yes, X3D NURBS is different. All VRML97 will need to be changed,
and some will need significant reorganization.

X3DParametricGeometryNode
..NurbsCurve
..NurbsSweptSurface
..NurbsSwungSurface
..X3DNurbsSurfaceGeometryNode
...NurbsPatchSurface
...NurbsTrimmedSurface
X3DNurbsControlCurveNode
..ContourPolyline2D
..NurbsCurve2D

NurbsSet (X3DBoundedObject)*
NurbsOrientationInterpolator
NurbsPositionInterpolator
NurbsSurfaceInterpolator

NurbsTextureCoordinate

http://www.web3d.org/x3d/specifications/
ISO-IEC-19775-FDIS-X3dAbstractSpecification/
Part01/concepts.html#f-Objecthierarchy

http://www.web3d.org/x3d/specifications/
ISO_IEC_19776-2-FDIS-X3dEncodings/
Part02/EncodingOfNodes.html

The encodings spec may the the latest published.

Best Regards,
Joe

"Joerg Scheurich aka MUFTI" <rusmufti@helpdesk.rus.uni-stuttgart.de> wrote in
message news:cgg7n4$bkp$1@infosun2.rus.uni-stuttgart.de...
>
>
> What are the changes in the NURBS component relative to
>
>
http://www.web3d.org/x3d/specificat...tractSpecificat
ion/Part01/components/nurbs.html
>
> ?
>
> NURBS was often a moving target in the X3D drafts and (very much more ugly)
> some (most ?) of them were not compatible to ISO/IEC 14772-2:2002 8-(
>
> so long
> MUFTI
> --
> A number of the Windows-based application programming interfaces (APIs) that
> are documented as accepting only a module handle are defined incorrectly.
> (aus einer M$Windows Dokumentation)

Jordi R. Cardona

2004-08-26, 12:28 pm

Thank you.
Yesterday I saw on web3d.org that it has already been unanimously aprobed by
ISO. Soon final spec will be in ISO to download.

Thanks a lot

Jordi

Joerg Scheurich aka MUFTI

2004-08-30, 7:17 pm

> Yes, X3D NURBS is different. All VRML97 will need to be changed,
> and some will need significant reorganization.

Reorganization ? I see nothing, which is similar to the CoordinateDeformer 8-(

http://www.web3d.org/x3d/specificat...rdinateDeformer

> X3DParametricGeometryNode
> .NurbsCurve
> .NurbsSweptSurface
> .NurbsSwungSurface
> .X3DNurbsSurfaceGeometryNode
> ..NurbsPatchSurface
> ..NurbsTrimmedSurface
> X3DNurbsControlCurveNode
> .ContourPolyline2D
> .NurbsCurve2D

> NurbsSet (X3DBoundedObject)*
> NurbsOrientationInterpolator
> NurbsPositionInterpolator
> NurbsSurfaceInterpolator

> NurbsTextureCoordinate

so long
MUFTI
--
Eine Unter-Speisekarte wird erscheinen, in der Sie waehlen koennen,
entweder zu spielen, oder das Video zu schlingen.
(aus einem Software-Handbuch, Stichworte: menu und loop)

Joe D Williams

2004-08-30, 7:17 pm

>
> Reorganization ? I see nothing, which is similar to the CoordinateDeformer 8-(
>

Please look at things like:

http://www.web3d.org/x3d/specifications/
ISO_IEC_19776-2-FDIS-X3dEncodings/
Part02/EncodingOfNodes.html#NurbsSurfaceInterpolator

"Joerg Scheurich aka MUFTI" <rusmufti@helpdesk.rus.uni-stuttgart.de> wrote in
message news:cgvpnv$b9m$11@infosun2.rus.uni-stuttgart.de...[color=darkred]
>
> Reorganization ? I see nothing, which is similar to the CoordinateDeformer 8-(
>
>
http://www.web3d.org/x3d/specificat...rt1/nodesRef.ht
ml#CoordinateDeformer
>
>
>
>
>
> so long
> MUFTI
> --
> Eine Unter-Speisekarte wird erscheinen, in der Sie waehlen koennen,
> entweder zu spielen, oder das Video zu schlingen.
> (aus einem Software-Handbuch, Stichworte: menu und loop)

Joerg Scheurich aka MUFTI

2004-08-30, 11:16 pm

>> Reorganization ? I see nothing, which is similar to the CoordinateDeformer 8-(

> Please look at things like:

> http://www.web3d.org/x3d/specifications/
> ISO_IEC_19776-2-FDIS-X3dEncodings/
> Part02/EncodingOfNodes.html#NurbsSurfaceInterpolator

This is a interpolator which can be used for a NURBS node.
I would not say, this is total useless, but you can interpolate NURBS nodes
with usual CoordinateInterpolators as well

http://www.csv.ica.uni-stuttgart.de...ne/seesnail.wrl
(VRML97 Amendment 1 browser required, e.g. cc3dglut)

In difference, CoordinateDeformer is responsible for modifing non NURBS
nodes.

http://www.web3d.org/x3d/specificat...rdinateDeformer

| CoordinateDeformer allows a free form deformation on a set of MFVec3f Coordinate nodes

Possibly CoordinateDeformer can be used to "bow"/"knead" a IndexedFaceSet
or IndexedLineSet, which would be very useful especially for modelling.

Unfortunatly, there is no instructive example for the CoordinateDeformer,
only animation examples with zillions of scripting 8-(

so long
MUFTI
--
Eine Unter-Speisekarte wird erscheinen, in der Sie waehlen koennen,
entweder zu spielen, oder das Video zu schlingen.
(aus einem Software-Handbuch, Stichworte: menu und loop)

Joerg Scheurich aka MUFTI

2004-08-31, 12:19 pm

Joe D Williams

2004-09-01, 4:16 am

Joerg Scheurich aka MUFTI

2004-09-05, 11:17 pm