Difference between revisions of "DAE"

From GICL Wiki
Jump to: navigation, search
Line 4: Line 4:
 
'''Version ID:''' As of 2009-05, COLLADA v1.4.1 (stable release), v1.5 (newest release)
 
'''Version ID:''' As of 2009-05, COLLADA v1.4.1 (stable release), v1.5 (newest release)
  
'''Date released:''' 2008-04 and 2008-06 repsectively
+
'''Date released:''' 2008-03 and 2008-06 repsectively
  
 
'''Date:''' 2004
 
'''Date:''' 2004

Revision as of 12:57, 10 May 2009

Title(s): COLLADA (COLLAborative Design Activity) DAE (Digital Asset Exchange) Format

Version ID: As of 2009-05, COLLADA v1.4.1 (stable release), v1.5 (newest release)

Date released: 2008-03 and 2008-06 repsectively

Date: 2004

Creator(s): The Khronos Group. The Khronos Group is an industry consortium creating open standards for the authoring and acceleration of parallel computing, graphics and dynamic media on a wide variety of platforms and devices. All Khronos members are able to contribute to the development of Khronos API specifications, are empowered to vote at various stages before public deployment, and are able to accelerate the delivery of their cutting-edge 3D platforms and applications through early access to specification drafts and conformance tests.

Contributor(s): Sony Computer Entertainment, NVIDIA, ATI, Softimage, Autodesk, Google, and Intel.

Description: COLLADA is a royalty-free XML schema that enables digital asset exchange within the interactive 3D industry.

History: Before the decision was made to start the COLLADA project, the team looked at all the existing formats and decided that, unfortunately, they needed to create a new one that would have a chance to become a standard.

Most existing formats are not open formats and have not been designed by a working group, but by a single company. That is a problem: Will all other companies agree to support a format that they have not participated in designing? But most importantly, what would happen if that one company were to disappear or decide to prioritize their support for different tools?

The main existing interchange technologies are not designed as a language, but rather as APIs (available under a license on a limited number of platforms). This enables data to be exchanged among applications that have licensed the technology, but it does not help at all to liberate the data from proprietary formats. How can one risk having one's vital assets stored in a format that one does not have sufficient control over, including the exact specifications for?

What happened to Kaydara (being acquired by Alias) and then Alias (being acquired by Autodesk) should remind everyone of the risks of using proprietary formats, and all of us should keep asking for COLLADA to be widely supported by all DCC companies and different tool makers.

Example(s): DAE Example

Identifier: http://www.khronos.org/collada/

Documentation: DAE Documentation

File Extensions: .DAE

Applications: https://collada.org/mediawiki/index.php/Portal:Products_directory

Rights: © 2005-2008 The Khronos Group Inc., Sony Computer Entertainment Inc. All Rights Reserved. Excerpt - This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast, or otherwise exploited in any manner without the express prior written permission of Khronos Group...

Khronos Group grants express permission to any current Promoter, Contributor, or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible...

Typical use: Enables digital asset exchange within the interactive 3D industry