Difference between revisions of "Plans for Merging X3D AR Proposals"
From Web3D.org
| Line 1: | Line 1: | ||
This page is for discussing plans for merging X3D AR proposals, compared in [[Comparison of X3D AR Proposals]]. | This page is for discussing plans for merging X3D AR proposals, compared in [[Comparison of X3D AR Proposals]]. | ||
| − | == | + | == Yvonne == |
| − | == | + | == Gerard Kim == |
| + | |||
| + | == Gun == | ||
| − | |||
1. Discuss general strategy/policy/guidelines | 1. Discuss general strategy/policy/guidelines | ||
* General guidelines in Web3D consortium? | * General guidelines in Web3D consortium? | ||
Revision as of 01:39, 20 March 2012
This page is for discussing plans for merging X3D AR proposals, compared in Comparison of X3D AR Proposals.
Yvonne
Gerard Kim
Gun
1. Discuss general strategy/policy/guidelines
- General guidelines in Web3D consortium?
- From the scene writer's point of view, preferably less code for commonly/frequently used features, while detail control available for special cases.
- From the user's (viewer's) point of view, the scene should be adopted to the hardware/software environment (tracker, camera device, browser, etc.) s/he has. In other words, scene writer should not specify hardware/software environment in the scene, which is on the users' side.
2. Investigate each functional features stepwise
- Camera video stream image in the scene (texture and background)
- Tracking (including support for general tracking devices)
- Camera calibration (viewpoints)
- Others (color-keying, depth occlusion)
3. Integration of functional features
- Conflicts between individual components
- Merging components
4. Specification writing
5. Review
