<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">It may make some sense to combine
several X3D profiles; however, the three profiles mentioned
(Interchange, CAD Interchange, and Model) do not have just a few
nodes of differences. <br>
<br>
<b>Interchange</b> - Base X3D profile for X3D-modeled scenes.
Includes several nodes related to scene definition/management.<br>
<b>CAD Interchange</b> - Focus on CAD data structures. Includes
NURBS (no other existing profile does), but does not include
triangles. Includes some scene definition/management.<br>
<b>Model</b> - Reusable static models with full support for
surfaces (triangles, quads, NURBS) and volumes. No scene
definition/management or animation.<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
<br>
</div>
<blockquote type="cite"
cite="mid:33c49de5-260e-1d52-0503-0afae00a344a@nps.edu">Another
relevant X3D profile for comparison is CADInterchange
<br>
<br>
========================================================================
<br>
X3D Abstract Specification, Annex H CADInterchange profile
<br>
<br>
H.1 General
<br>
<br>
This annex defines the X3D components that comprise the
CADInterchange profile. This annex includes not only the nodes
that shall be supported but also which fields in the supported
nodes may be ignored.
<br>
<br>
This profile is targeted towards:
<br>
<br>
* Distillation of computer-aided design (CAD) data to downstream
applications.
<br>
* Appropriately supporting Geometry and Appearance capabilities
data for CAD.
<br>
<br>
========================================================================
<br>
<br>
As ever, getting clear on goals and use cases can be very
helpful. Are there overlapping motivations for Interchange,
CADInterchange, glTF and model exchange? If there is lots of
common ground and the differences are small, perhaps all should be
converged in a new profile for X3D v4.
<br>
<br>
<br>
On 1/31/2018 9:40 AM, Don Brutzman wrote:
<br>
<blockquote type="cite">Interesting discussions. Here are some
additional profile possibilities to improve model interchange.
<br>
<br>
Since profiles are intended to provide common shared needs,
these design criteria are all good to consider and
compare/contrast together.
<br>
<br>
========================================================================
<br>
========================================================================
<br>
<br>
1. Background. The architecture for X3D profile, component,
level is defined to support diverse extensibility, with profiles
intended to define a commonly used palette of capabilities that
support common use cases for browser implementations and scene
authors. References:
<br>
<br>
* X3D Abstract Specification, Concepts, 4.5 Components
<br>
<a class="moz-txt-link-freetext" href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/concepts.html#Components">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/concepts.html#Components</a>
<br>
"An X3D component is a set of related functionality consisting
of various X3D objects and services as described below."
<br>
<br>
* X3D Abstract Specification, Concepts, 4.6 Profiles
<br>
<a class="moz-txt-link-freetext" href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/concepts.html#Profiles">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/concepts.html#Profiles</a>
<br>
"A profile is a named collection of functionality and
requirements that shall be supported in order for an
implementation to conform to that profile."
<br>
and
<br>
"Each set of requirements is directed at supporting the needs of
a particular constituency. Not all constituencies may be
satisfied by the functionality represented by these profiles.
Therefore, this part of ISO/IEC 19775 allows for defining
additional profiles either through amendment to this part of
this International Standard or by registration."
<br>
<br>
* X3D for Web Authors, Brutzman and Daly, Chapter 1 Technical
Overview
<br>
2.5.3. Profile statements and 2.5.4. Component statements, pp.
12-15
<br>
<a class="moz-txt-link-freetext" href="http://x3dgraphics.com/examples/X3dForWebAuthors/Chapter01TechnicalOverview/Chapter01Technical_Overview.pdf">http://x3dgraphics.com/examples/X3dForWebAuthors/Chapter01TechnicalOverview/Chapter01Technical_Overview.pdf</a>
<br>
<br>
========================================================================
<br>
========================================================================
<br>
<br>
2. As part of X3D version 4, which allows us considerable design
leeway, we might consider updating the current Interchange and
Interactive Profile design criteria. The original criteria are
not "wrong" per se, but they might well be improved to better
match modern capabilities and practices.
<br>
<br>
What is missing from these motivations? Copied here:
<br>
<br>
========================================================================
<br>
X3D Abstract Specification, Annex B Interchange profile
<br>
<a class="moz-txt-link-freetext" href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/interchange.html">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/interchange.html</a>
<br>
<br>
B.1 General
<br>
<br>
This annex defines the X3D components that comprise the
Interchange profile. This includes not only the nodes that shall
be supported but also which fields in the supported nodes may be
ignored.
<br>
<br>
This profile is targeted towards:
<br>
<br>
* Exchange of geometry and animations between authoring systems,
<br>
* Possible implementation in a low-footprint engine requiring no
interaction (EXAMPLE an applet or small browser plug-in),
<br>
* Addressing the limitations of software renders not capable of
dealing with all details of the full X3D lighting model, and
<br>
* Allowing a broader range of implementations by eliminating
some complexity of a complete X3D implementation.
<br>
<br>
========================================================================
<br>
X3D Abstract Specification, Annex C (normative) Interactive
profile
<br>
<a class="moz-txt-link-freetext" href="http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/interactive.html">http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/interactive.html</a>
<br>
<br>
C.1 General
<br>
<br>
This annex defines the X3D components that comprise the
Interactive profile. This includes not only the nodes that shall
be supported but also which fields in the supported nodes may be
ignored.
<br>
<br>
This profile is targeted towards:
<br>
<br>
* implementing a lightweight playback engine that supports rich
graphics and interactivity,
<br>
* possible implementation in a low-footprint engine requiring
limited navigation and environmental sensor control (EXAMPLE an
applet or small browser plug-in), and
<br>
* allowing a broader range of implementations by eliminating
some complexity of a complete X3D implementation.
<br>
<br>
========================================================================
<br>
========================================================================
<br>
<br>
3. Also of interest is to consider glTF capabilities, and
whether a corresponding X3D Profile for glTF 2 might be defined.
<br>
<br>
[x3d-public] X3D and glTF Features Comparison
<br>
<a class="moz-txt-link-freetext" href="http://www.web3d.org/mailman/private/x3d-public_web3d.org/2017-December/008028.html">http://www.web3d.org/mailman/private/x3d-public_web3d.org/2017-December/008028.html</a>
<br>
<br>
glTF X3D Features Comparison (3 NOV 2017)
<br>
<a class="moz-txt-link-freetext" href="http://www.web3d.org/sites/default/files/page/X3D%20Version%204/glTfX3dFeaturesComparison.pdf">http://www.web3d.org/sites/default/files/page/X3D%20Version%204/glTfX3dFeaturesComparison.pdf</a>
<br>
<br>
Thanks everyone for considering all of these possibilities. The
potential for improving profiles is a real opportunity with X3D
version 4.
<br>
<br>
all the best, Don
<br>
</blockquote>
<br>
<br>
all the best, Don
<br>
</blockquote>
<p><br>
</p>
<div class="moz-signature">-- <br>
<font class="tahoma,arial,helvetica san serif" color="#333366">
<font size="+1"><b>Leonard Daly</b></font><br>
3D Systems & Cloud Consultant<br>
LA ACM SIGGRAPH Past Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>