Difference between revisions of "X3D and Augmented Reality"
|Line 54:||Line 54:|
== Tasks ==
== Tasks ==
Revision as of 15:27, 20 April 2011
Web3D Consortium has a special interest in the recent AR initiatives and creating the AR Technology Road Map.
- X3DOM can serve as an out of the box, standards-based solution for AR developers.
- X3D and X3DOM continue to improve scripting options for X3D with HTML5 and this has good promise for AR applications.
- X3DOM is being considered for potential standardization in a Mobile and/or Augmented Reality (AR) profile for X3D.
Our Web3D Korea Chapter members from ETRI are working on Mixed Reality visualization in X3D.
- The Consortium as been working closely within W3C HTML5 WG to align our standards for 3D visualization on the Web.
Additional details are available at:
- Web3D Consortium will be starting an AR working group in March 2011 to develop a roadmap for AR standardization. We encourage your participation.
- The technology discussions and meetings will be conducted publicly so that the widest possible comment and reaction can be considered from the Community. Feedback from this community will help X3D quickly and stably adopt new technologies to provide ongoing archival value for all 3D graphics.
- Meanwhile Web3D Members still retain important membership rights of proposing significant new technology and considering patented technologies within a "safe haven" prior to public release.
Slideset summary from last summer's Mobile X3D ISO Workshop has also been linked: how Mobile, HTML5 and possibly Augmented Reality (AR) components might be alignable together as an X3D Mobile Profile.
Many new Web3D capabilities are becoming available. There has been no better time to discuss X3D technologies and also join the Web3D Consortium. Get involved in these early discussions to create the AR Technology Road Map. We look forward to your participation.
Adding points to this section will be the subject of the next meetings.
The Augmented Reality Working/Special Interest Group focuses on utilizing/extending X3D functions to support augmented and mixed reality applications.
These X3D AR discussion are part of a special interest group. This effort is moving forward by forming the X3D AR Working Group. The charter, roles and responsibilities are being defined.
Planned goals of AR WG/SIG include:
- Collect requirements and describe typical use cases of using X3D for AR/MR application.
- Develop and extend functions and nodes for X3D specification required to support AR/MR
- Produce sample AR/MR applications with X3D
- Investigate state-of-the-art technologies related to X3D and AR/MR
- Develop and extend X3D specification to support AR/MR applications
- Promote X3D in AR/MR field by developing and demonstrating use cases
Deliverables and Timeline
- Use cases of X3D for AR/MR application - May, 2011 TBD
- Requirements for X3D to support AR/MR applications - May, 2011 TBD
- Proposed new/extended functions and nodes for X3D specification - TBD
- Sample AR/MR applications with X3D - TBD
Our twice-monthly teleconference for X3D and Augmented Reality is usually
- Together with Korea Chapter Meeting:
1710-1810 (Pacific time)/2010-2110 (Eastern time) on 1st Wednesday, which is 0910-1010 (Korea time) on 1st Thursday.
- AR only Meeting:
1710-1810 (Pacific time)/2010-2110 (Eastern time) on 3rd Tuesday, which is 0910-1010 (Korea time) on 3rd Wednesday.
Our next public teleconference is 15/16 March 2011.
Meeting agenda: TBA through the mailing list.
Discussions occur on the email@example.com mailing list. If the email traffic becomes very busy then we can create a separate email list.
Meeting minutes are also distributed on the X3D-Public mailing list and archived online.
A Mixed Reality framework developed and maintained by Fraunhofer IGD, which uses X3D as application description language and which thus also provides corresponding nodes and concepts for developing AR/MR applications. The full documentation is on IR-Docs.
There also exist several tutorials on vision-based tracking with Instant Reality, which e.g. describe specific nodes like the IOSensor for retrieving the camera streams and the tracking results of the vision subsystem, as well as the PolygonBackground for displaying the camera images behind the virtual objects or some useful camera extensions to the X3D Viewpoint node etc: Tracking-Tutorial.
In addition, some papers on AR and MR rendering already were pubished at the Web3D conferences. Here, e.g. occlusions, shadows and lighting in MR scenes were discussed in the context of X3D:
There are moreover some more ideas on realistic MR rendering in X3D outlined in chapter 6 (p. 163 ff.), and especially in section 6.4, in the following PhD thesis: Pdf.
The Korea chapter has been keenly interested in the standardization of augmented reality in many aspects including the AR based contents. This is especially due to the recent world-wide appearances of mobile AR services and realization (from both academia and industry) of the definite need for exchanging service contents on different platforms.
Three main proposals have been made within the Korean chapter, by: (1) Gerard Kim from Korea University (also representing KIST), (2) Gun A. Lee (formerly with ETRI, now with HITLabNZ), and (3) Woontack Woo of Gwangju Inst. of Science and Tech.
Here, we briefly describe each proposal and provide links to documents with more detailed descriptions. These short summararies also try to highlight their distinctions with regards to other proposals, but not in the critical sense, but as a way to suggest alternatives.
(1) Gerry Kim's proposal can be highlighted by the following features:
- Extension of existing X3D "sensors" and formalisms to represent physical objects serving as proxies for virtual objects
- The physical objects and virtual objects are tied using the "routes" (e.g. virtual objects' parent coordinate system being set to that of the corresponding physical object).
- Below shows an example construct which is a simple extension of the "VisibilitySensor" attached to a marker. The rough semantic would be to attach a sphere to a marker when visible. The visibilty would be determined by the browser using a particular tracker. In this simple case, a simple marke description is given through the "marker" node.
<Scene> <Group> <Marker DEF = “HIRO” enable “TRUE” filename=”C:\hiro.patt”/> <VisibilitySensor DEF='Visibility' description='activate if seen' enabled=”TRUE”/> <Transform DEF='BALL'> <Shape> <Appearance> <Material/> </Appearance> <Sphere/> </Shape> </Transform> </Group> <ROUTE fromNode=’Vsibility’ fromField='visible' toNode=’BALL’ toField=’visible’ /> </Scene>
- Different types of sensors can be newly defined or old ones extended to describe various AR contents. These include proximity sensors, range sensors, etc.
- Different physical object description will be needed at the right level of abstraction (such as the "marker" node in the above example). These include those for image patch, 3D object, GPS location, natural features (e.g. points, lines), and etc.
(2) Gun Lee's proposal
- Extension of the TextureBackground and Movie texture node to handle video background for video see-through AR implementation.
- Introduction of a node called "LiveCam" representing the video capture or vision based sensing in a video see-through AR implementation.
- The video background would be routed from the "LiveCam" node and be supplied with the video image and/or camera parameters.
- Extension of the virtual view point to accomodate more detailed camera parameters and to be set according to the parameters of the "LiveCam".
(3) Woo's proposal
- Woo proposes to use XML, as meta descriptors, with existing standards (e.g. X3D, Collada, etc.) for describing the augmentation information themselves.
- As for the context (condition) for augmentation, a clear specification of "5W" approach is proposed: namely who, when, where, what and how.
- "who" part specifies the owner/author of the contents.
- "when" part specifies content creation time.
- "where" part specifies the location of the physical object to which an augmentation is attached.
- "what" part specifies the what is to be augmented content (augmentation information).
- "how" part specifies dynamic part (behavior) of the content.
- Anita Havele
- Damon Hernandez
- Don Brutzman
- Gerard J. Kim
- Gun Lee
- Len Daly, Daly Realism
- Timo Engelke
- Sabine Webel
- Yvonne Jung
Participation and Liaisons
- Other partnerships can also be considered as appropriate.
- Of interest is that Web3D Consortium Intellectual Property Rights (IPR) Policy insists on open, royalty free (RF) specifications. These coexist effectively with the Web Architecture and many different business models.