• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: MISC-830
Type: New Feature New Feature
Status: Open Open
Priority: Normal Normal
Assignee: Unassigned
Reporter: Dzonatas Sol
Votes: 12
Watchers: 5
Operations

If you were logged in you would be able to see more operations.
4. Second Life Misc Issues - MISC

Asset Exchange: COLLAborative Design Activity (COLLADA)

Created: 01/Dec/07 08:59 AM   Updated: 17/Apr/09 09:24 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Environment: protocols that involve a wide range of areas: WEB, VWR, SVC, external, high and low level asset exchanges
Issue Links:
Relates


 Description  « Hide
Please see: http://en.wikipedia.org/wiki/COLLADA

COLLADA provides a standard to exchange assets. The assets may vary in actual content, but the core data deals mainly with geometry and physics. Such core data makes up the heart of what virtual worlds are about.

Instead of the need for virtual worlds to reinvent the wheel to support a variety of asset information, like OBJ, 3DS, JT, Sculptied prims, etc, the protocols of the virtual world integrate the exchange methods of COLLADA in order to exchange such information in a standard way. Once the data is at its destination, it may be put trough filters that best match for an individual implementation. Hence, the burden for all destinations to carry the same implementation becomes nil. This also allows a particular implementation filter content once and then just use the optimized version from the filter output. The implementation may use the actual core data of the COLLADA format or the filtered output.

As for protocols that deal more with the exchange of the COLLADA format, they mainly need to understand the metadata of the format in order to transfer complete asset information, but they need not know about the actual core data.

Action: As a new feature request, this jira is intended to build consensus and collaborate resources about COLLADA. Most likely this will appear as a meta issue, but that is due more to the wide scope that assets affect. Immediate implementation is not requested in any particular area, but this jira may serve more to influence the current development to allow such collaborative design.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order

Strife Onizuka added a comment - 20/Jul/08 02:53 PM
SL does have some support for collada. I've seen it mentioned in the source code.

Dzonatas Sol added a comment - 17/Apr/09 09:24 PM
HTTP_Texture branch falls in scope of COLLADA. The new pipeline could queue a fetch to an asset manager. The alternative file format to recognize would be the collada file, and the metadata in the collada file may queue more fetches as needed when decoded.

A few random thoughts:

  • Anonymous fetches would get readonly privileges
  • Users could log into asset manager to store data, or gain read privs to the source of the data
  • The decode process could compile the collada file and cache the generated images.
  • Asset manager could pre-optimize encapsulated data for the viewer (separate project)
  • The collada file could have metadata to already compiled and/or pre-optimized images/models
  • Simulator could make a separate fetch to the asset manager for just physical data out of the collada file.