WWML
From World Wind Wiki
(Difference between revisions)
| Revision as of 02:52, 29 April 2006 (edit) Ghchinoy (Talk | contribs) ← Previous diff |
Current revision (21:13, 21 August 2019) (edit) (undo) F0urtyfive (Talk | contribs) m (Reverted edits by Monday (Talk); changed back to last version by Adamhill) |
||
| (6 intermediate revisions not shown.) | |||
| Line 3: | Line 3: | ||
| This is the discussion page for the newly developed WorldWind Markup Language for World Wind 1.5. You can view the current data sheet [http://worldwind.arc.nasa.gov/dev/WWMLv0.93.pdf here]. | This is the discussion page for the newly developed WorldWind Markup Language for World Wind 1.5. You can view the current data sheet [http://worldwind.arc.nasa.gov/dev/WWMLv0.93.pdf here]. | ||
| - | WWML is, for the most part, GML+WW additions. (More to be added later) | + | WWML is, for the most part, a subset of [http://opengis.net/gml/ GML 3.1] plus WW additions. (More to be added later) |
| + | |||
| + | * NASA needs a nice, concise list of what they want WWML to be and '''not to be'''. Along with a list of all the elements they are adding and all the GML pieces they will be supporting and the ones they '''will not be''' supporting. | ||
| * What is the 8cm stuff? Why are you specifying an absolute display size in a some geographic data? | * What is the 8cm stuff? Why are you specifying an absolute display size in a some geographic data? | ||
| + | |||
| + | * Weird example about embedding WW in a web page via XHTML. WTF? | ||
| * The OverlayImagery example implies WW will be supporting TimeSpan constructs. | * The OverlayImagery example implies WW will be supporting TimeSpan constructs. | ||
| Line 17: | Line 21: | ||
| ** [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 | ||
| - | * NASA should simply drop the namespaces and adhere to a de facto interpretation of some OGC GML 3.1 elements/attrs. Namespaces may be constant reminders of the deference to a larger standard, but they don't assist in understanding the subset that WWML is attempting to achieve. (No need for users to understand GML to understand WWML.) | + | * NASA should simply drop the namespaces and adhere to a de facto interpretation of some OGC GML 3.1 elements/attrs. Namespaces may be constant reminders of the deference to a larger standard, but they don't assist in understanding the subset that WWML is attempting to achieve. A requirement should be that there is no need for users to understand GML to understand and utilize WWML. |
| + | |||
| + | (Sorry but this doesn't make any sense, drawing lines on a oblate, spheroid with grid corrections in any one of 20-30 different projections is just plain hard, sometimes even hard to understand. Getting a pushpin at a specific lat/long is easy, thats what GeoRSS is for, not GML) | ||
| + | |||
| + | * GML Application Profile | ||
| + | |||
| + | *Pushback - [http://lptf.blogspot.com/2006/05/wwml-spec.html] | ||
| [[Category:Dev]] | [[Category:Dev]] | ||
Current revision
[edit] 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, a subset of GML 3.1 plus WW additions. (More to be added later)
- NASA needs a nice, concise list of what they want WWML to be and not to be. Along with a list of all the elements they are adding and all the GML pieces they will be supporting and the ones they will not be supporting.
- What is the 8cm stuff? Why are you specifying an absolute display size in a some geographic data?
- Weird example about embedding WW in a web page via XHTML. WTF?
- 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.
- CWXML/BXML - the proposed binary format implementation in WWML spec
- W3C XML Binary Characterization Working Group Public Page
- XSBC: XML Schema-based Binary Compression
- 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
- NASA should simply drop the namespaces and adhere to a de facto interpretation of some OGC GML 3.1 elements/attrs. Namespaces may be constant reminders of the deference to a larger standard, but they don't assist in understanding the subset that WWML is attempting to achieve. A requirement should be that there is no need for users to understand GML to understand and utilize WWML.
(Sorry but this doesn't make any sense, drawing lines on a oblate, spheroid with grid corrections in any one of 20-30 different projections is just plain hard, sometimes even hard to understand. Getting a pushpin at a specific lat/long is easy, thats what GeoRSS is for, not GML)
- GML Application Profile
- Pushback - [1]
