WWML
From World Wind Wiki
(Difference between revisions)
| Revision as of 02:16, 29 April 2006 (edit) Ghchinoy (Talk | contribs) m ← Previous diff |
Revision as of 02:17, 29 April 2006 (edit) (undo) Ghchinoy (Talk | contribs) Next diff → |
||
| Line 12: | Line 12: | ||
| * The para describing GML as verbose and the necessity for some form of binary transport needs no justification. I believe GML is recognized as way too verbose already. I'm not sure that needs to be in the introductory section. | * The para describing GML as verbose and the necessity for some form of binary transport needs no justification. I believe GML is recognized as way too verbose already. I'm not sure that needs to be in the introductory section. | ||
| + | ** [http://www.w3.org/XML/Binary/ W3C XML Binary Characterization Working Group Public Page] | ||
| ** [http://xmsf.sourceforge.net/xsbc.html XSBC: XML Schema-based Binary Compression] | ** [http://xmsf.sourceforge.net/xsbc.html XSBC: XML Schema-based Binary Compression] | ||
| ** [http://xml.coverpages.org/ni2004-08-02-a.html The Web3D Consortium and Sun Microsystems have announced the creation of a new X3D Binary Format Working Group] story from XML Cover Pages, Aug 2004 | ** [http://xml.coverpages.org/ni2004-08-02-a.html The Web3D Consortium and Sun Microsystems have announced the creation of a new X3D Binary Format Working Group] story from XML Cover Pages, Aug 2004 | ||
Revision as of 02:17, 29 April 2006
World Wind Markup Language (WWML)
This is the discussion page for the newly developed WorldWind Markup Language for World Wind 1.5. You can view the current data sheet here.
WWML is, for the most part, GML+WW additions. (More to be added later)
- What is the 8cm stuff? Why are you specifying an absolute display size in a some geographic data?
- The OverlayImagery example implies WW will be supporting TimeSpan constructs.
- No Rotation attributes for ImageOverlays, no support for non-linear stretching of IO's
- The para describing GML as verbose and the necessity for some form of binary transport needs no justification. I believe GML is recognized as way too verbose already. I'm not sure that needs to be in the introductory section.
