Scalable Open Software Standard for Creating Interactive 3D Content - Essay Example

3D XML Overview X3D Overview X3D is a scalable open software standard for creating and presenting interactive 3D content in real-time. Merging real-time 3D data, presentations and controls with non-3D content becomes fast and easy using X3D’s XML-encoding and Scene Authoring Interface (SAI) features, which are provided for both web and non-web applications. X3D visual effects and behavioural modelling have a great number of uses, including GIS, CAD, visual stimulation, medical visualization, entertainment, education and other such multimedia presentations. The software can also be used across hardware devices. X3D builds on the success of the Virtual Reality Modelling Language (VRML) with expanded features such as stricter conformance, additional data encoding formats, and more advanced APIs. Its componentized architecture introduces the profiles feature, which allows for a modular approach to supporting the standard. X3D also features backward compatibility with legacy VRML data (http://www.web3d.org/x3d/specifications/x3d/).  Introduction In order to model the numerous graphics nodes constituting a virtual environment, the X3D software makes use of a scene graph, which is a directed and cyclic tree structure. This type of graph has a definite beginning with parent-child relationships between each node, with each node having a single parent. The only exception to this rule is the X3D root at the very top of the graph. The graph in itself contains no cycles or loops, and it organizes all aspects of a 3D scene in a hierarchal manner that systematizes appearance, animation, geometry and event routing (Brutzman, Daily, 2007). As has been already stated, the software is based on VRML or the Virtual Reality Modelling Language, an international standard first adopted in 1997. However, X3D differs from VRML in its inclusion of Extensible Markup Language (XML), which allows it to integrate with other Internet-based software (Brutzman, Daily, 2007).  Historical background: VRML, ISO and Web3D Consortium X3D’s scene-graph architecture and file-format encoding are based on existing VRML technology, which is formally known as the ISO/IEC 14772 -1:1997 international standard. However, it is more commonly known as VRML 2 or VRML 97, and it is well-known for a highly expressive 3D interchange format that is supported by a wide range of codebases and tools. VRML 97’s geometry and behaviour capabilities are expressed in X3D through XML. Moreover, X3D enables users to carry out node prototyping and program scripting, whether in ECMAScript or in Java. All of these features provide outstanding support for scene-graph extensions and new languages functionally defined by users (Brutzman, Daily, 2007). VRML traces its origins back to Mark Pesce and Tony Parisi, who spearheaded the creation of an open competition in 1994 for a new markup language to be used for Internet 3D graphics. OpenInventor, a language created by Rikk Carey and Paul Strauss of Silicon Graphics Inc. (SCI) eventually won the competition and became the basis of VRML 1.0. This first version of the Virtual Reality Markup Language was created through an informal, consensus-based group effort. A new and improved VRML 2.0 made its appearance some years later and was accepted by the industry as International Standard 14772-1 :1997 or simply VRML 97. ( Brutzman, Daily , 2007)  X3D Browser This type of browser, also known as a player or a viewer, can parse (or read) scenes from X3D and then render (or draw) them. The viewer can not only examine 3D objects from various angles, but also animate and interact with these objects. X3D browsers often come in the form of plug-ins that are bundled with regular hypertext markup language (HTML) web browsers. They can also be packaged as standalone or imbedded applications.      Figure 1: Sample software architecture of an X3D browser. The flowchart in Figure 1 presents a typical example of software architecture present in an X3D browser. This paragraph will describe the flowchart beginning with the upper-leftmost box, travelling in a counter-clockwise direction. Normally, X3D scenes are files that the browser reads or writes. Parsers are used to read the file-format encoding, after which nodes are generated and then sent to the scene-graph manager. This manager keeps track of defined geometry, appearance, locations and orientations. It also constantly goes back and forth between the nodes to quickly generate output image frames. This process continually draws and redraws the 3D image in order to synchronize with changes in the user’s orientation and point of view. The event graph, on the other hand, keeps track of the animation nodes, which calculate the data, draw events based on that data, and then feed those events into the scene graph. Any event fed into the scene graph can alter the image presented to the user. Scripts supplement the animation nodes as they can send or receive events, as well as generate or erase geometry from the scene. Scripts utilize programming code from JavaScript and other such languages. The SAI or Scene Authoring Interface enables authors to write code that can work across various operating systems and browsers by controlling how these APIs or application programming interfaces perform. As seen in the final box in the uppermost right corner of Figure 1, HTML web pages and other external applications can also be used to embed X3D browsers. These browsers are then seen by Internet users as interactive 3D images. ( Brutzman, Daily, 2007).  XML Motivations XML is a compelling language to use for many reasons. First of all, it is the backbone of virtually all data languages used on the Internet today. Second, it is imperative to code using XML in order to create professional web pages—that is to say, web pages that interface smoothly with users and servers worldwide (Brutzman, Daily, 2007). In 2001, Bert Boss compiled a list of ten characteristics that make XML stand out. The following list is a paraphrase of his article. 1. Structured data. XML is not a programming language. Rather, it is a set of rules that are used in order to design text formats and structure data. 2. Resemblance to HTML. The use of tags, which are words surrounded by angle brackets, is shared by HTML and XML. In addition, they both make use of the attribute name=”value”. However, while HTML governs individual tags in order to directly impact presentation, XML defines general relationships between tags and attributes. These relationships and semantics can then be customized by other applications. 3. Text format. Programs that produce structured data store that data either in binary or text format. Data in text format is much easier for humans to read, and for developers to debug. XML is one of the languages that produces this type of data. Thus, broken XML files are a rarity. 4. Verbosity. XML files are relatively large in size because they are in text and not binary format. XML file sizes also balloon because of their great dependence on tags. However, this is compensated for by other features. 5. Extensions. XML is not simply one language. Its usefulness is greatly augmented by an extended family of support languages such as Xlink, which describes hyperlinks, and Xpointer, which is a syntax for pointing to a specific part of an XML document. 6. Innovation. XML was based on SGML or Standard Generalized Markup Language, a widely used ISO standard from the eighties. HTML, on the other hand, was developed in the early nineties. Developers in the late nineties took the best from HTML and SGML in order to create XML, a language that is as powerful as SGML but much more user-friendly. 7. XHTML. The development of XML in turn led to this innovation. XHTML, while retaining many of HTML elements, derives its syntax from XML. 8. Modularity. XML is modular, meaning it allows the user to define a new document format by combining elements from previous formats. It also helps the user avoid name confusion through XML Schema. 9. Semantic Web. XML provides the basis for Semantic Web and for W3C Resource Description Framework ( RFD), which is a language used to express metadata. 10. Universality. The language is platform-independent, license-free, and supported worldwide. Many tools are designed with XML in mind, and many engineers are adept at using this technology.   XML design for X3D The XML language is a fundamental part of the X3D software. This section will describe the design patterns used in creating X3D’s XML tagset. The program expresses X3D nodes as elements of XML. The program also expresses X3D simple-tyre fields as attributes of XML. In addition, default values may be safely omitted from .x3d model documents. The parent-child relationships between X3D nodes are mirrored by corresponding parent-child relationships between XML elements. These three design patterns contributed much to the success of the X3D program. By using XML, the classical scene graph that was first introduced in VRML 97 was greatly improved upon. Moreover, compatibility with WEN-based technologies was significantly increased. Projects such as server-side 3D and Web-driven animation services also became a reality. The swift rise in the use of X3D has led to a substantial change in the way the Internet has developed in recent years (Brutzman, Daily , 2007). 1.1 Why 3D XML? 3D XML is a versatile XML-based format that allows efficient sharing of 3D data. 3D information can be integrated quickly and painlessly into all types of human communication, from maintenance manuals, to marketing brochures, to technical documentation, to emails and to websites, to name just a few. This flexibility proves 3D XML’s usefulness to the average person. 1.1.1 Easy Adoption 3D XML is not only self-describing, it can also be read or written using easily available tools. It is also easily interpreted by many industry-standard applications. This universality reduces the costs inherent in 3D data processing. 1.1.2 Extensibility The 3D XML instance/reference model can be extended. While a pre-defined set of tags is available to the user, the user can customize this set and add new data. 1.1.3 Low Volume and Quick Loading Users who take advantage of 3D XML’s capabilities find that they can record and share 3D data much more smoothly and efficiently. When combined with other programs that compress very complex data, 3D XML can produce files 95 percent smaller than those of other comparable formats. Furthermore, XML files are easily transmitted through the Internet and used in collaborative projects (Dassault Systemes , 2007). 2.3.4 Recommendations for Creating a Document from Scratch   1. Before creating a new document, the user must define a Product Structure. This involves assessing the assembly to be created and determining which elements will be repeated. Organizing one’s assembly into instances and references will make the project more efficient. 2. The user must then create a first Project Structure that instantiates all the objects only once. For example, the chassis. These types of objects can be straightforwardly described in 3D XML. The user must define the reference for each object, along with the representation and the related instance. 3. Next, the user must verify this first Project Structure with the 3D XML syntax and display it in the Player. At this stage, the user will end up with a basic Project Structure having all instances directly aggregated to the root reference. 4. The user may then proceed to add representations and graphic properties to this basic Project Structure. (Dassault Systèmes, 2007)  3D XML 3D XML is an especially useful tool for clients such as manufacturing companies. The product developers in these companies need reliable and efficient tools in order to take a product from initial design to actual manufacturing and to the highly competitive markets of today. 3D XML is one such tool. According to Dassault Systèmes, 3D XML is a “lightweight, standard XML-based format that enables users to capture and share accurate 3D data quickly and easily.” Extensible Markup Language’s (XML) streamlined and adaptable text format is an Internet standard for transmitting information, and Dassault Systèmes’ 3D XML applies an EXL schema in order to relay vital information such as product geometry, product structure, and graphical display properties. Through the use of XML as an industry standard, all software programs will be able to create 3D XML content using widely available tools. As a result, Dassault Systèmes foresees 3D XML will be adopted by the majority of software developers and that the cost of converting files from current proprietary 3D formats will be significantly lessened. (Versprille, 2005)    PDM Existing computer systems are now capable of enhancing the exchange and application of engineering information at all levels of a company. Computer systems are able to do this through an improved control over engineering data, engineering activities, engineering changes and product configurations. They also play a vital supporting role to product teams and methods such as Concurrent Engineering. Thanks to these computer systems, market leaders have benefited from the following reductions: Engineering costs are lowered by at least 10 % Product development cycles are trimmed by at least 20 % Engineering change handling times are lessened by at least 30 % Number of engineering changes are minimized by at least 40% In terms of product development, these computer systems: Shorten the time needed to introduce new products Diminish the cost of developing new products Curb the cost of new products Increase the quality of products and services Substantially affect the company’s competitiveness, market share and revenues These systems are commonly known as Engineering Data Management (EDM) or EDM/PDM systems, a term which encompasses a broad spectrum of computer systems. Specific examples of EDM/PDM systems are Product Data Management (PDM) systems and Engineering Document Management Systems (EDMS). EDM/PDM systems have many uses. One of their primary functions is to manage engineering data. The engineering data itself is generated mostly through systems such as CAM, CAE and CAD. The EDM/PDM systems oversee these other computer systems. They manage all the information related to the company’s products, such as the design and manufacturing processes that it must undergo before being released to the public. EDM/PDM systems also support processes such as Concurrent Engineering that seek to optimize engineering workflow. In other words, EDM/PDM systems are the overall tool that companies use to control the entire process of engineering. They are the backbone of the manufacturing process and of the product life cycle. Common issues such as control, quality, reuse, security and availability of engineering data are all addressed by EDM/PDM. Those who can take full advantage of such a powerful tool will find that many of their recurring problems can be easily solved. However, this does not mean that all engineering-related problems can be solved by an EDM/PDM system. It must be remembered that the system’s primary function is to simply manage engineering data and its associated workflow. Other solutions must be found for these persistent problems. One such solution is the previously mentioned technique of Concurrent Engineering, which EDM/PDM can support. Despite the great advances made with EDM/PDM technology, not all engineering problems have an automatic solution.  Introduction to Product Lifecycle Management Product Lifecycle Management (PLM) is a concept that includes, but is not limited to, Product Data Management (PDM). In the late 1980s, Engineering Data Management (EDM) and soon after Product Data Management (PDM) were developed as strategies for storing and managing the increasingly complex design files created by Computer Aided Design (CAD) systems. PDM gave engineers the capability to organize and standardize document files, to maintain BOM’s, to handle item, BOM and document revision levels, and to quickly grasp the increasingly complicated relationships between parts and assemblies. Engineers could do all of this using PDM systems, as well as minimize the risk of using incorrect design plans, as wells as maximizing the potential of existing product information. In reality, there are many more advantages to using a PLM system. Besides introducing new tools and technologies, PLM also improves upon existing infrastructure. This results in sometimes drastic changes in long-established practices and methods. However, the company enjoys an increased amount of control over the product’s lifecycle. Apart from boosting incremental savings, greater bottom line savings and top-line revenue growth savings, PLM systems also increase the company’s market share and profitability. PLM streamlines the business processes, enabling better, faster, smoother production over which the company has much more control. All of these factors are decisive in delivering pioneering and lucrative products to market.   (Saaksvuori, Immonen)  Unclear citation from original document All the various functions of a PLM system can be boiled down into two main tasks. First, a PLM system is an archive for all the information concerning a specific product. Second, a PLM system is a means of communication among those who have a stake in the creation of a product. These sectors typically consist of the design, marketing, engineering, manufacturing and field service divisions in a company. PLM serves as a common reference system for all of these groups. It is where all these groups’ specializations are synthesized in order to create the final product. The fundamental characteristics of a PLM system are as follows: To supervise design and handle documents To create and manage bills of material/product structure records To serve as an archive for electronic files To ascertain environmental compliance of the materials to be used To facilitate workflow and to become a mechanism for approving changes To manage multi-user secured access in the form of security controls such as electronic signatures To assign item-focused tasks To export data to downstream ERP systems To include built-in and custom parts and documents metadata (otherwise known as attributes) (http://www.product-lifecycle-management.com/) Read More