geo-extension-nonWGS84: Difference between revisions
		
		
		
		
		
		Jump to navigation
		Jump to search
		
				
		
		
	
| AndyMabbett (talk | contribs)  (→Issues) | AndyMabbett (talk | contribs)  m (→Notes) | ||
| Line 27: | Line 27: | ||
| # A list of acceptable, case-insensitive, values for 'body' would need to be drawn up (e/g/ "Earth", "Mars", "Luna", "Venus", etc.) wither "Earth" being assumed if none is specified. | # A list of acceptable, case-insensitive, values for 'body' would need to be drawn up (e/g/ "Earth", "Mars", "Luna", "Venus", etc.) wither "Earth" being assumed if none is specified. | ||
| # A list of acceptable values for 'schema' would need to be drawn up, for each body, with one being declared the default, to be used if no value is present. | # A list of acceptable values for 'schema' would need to be drawn up, for each body, with one being declared the default, to be used if no value is present. | ||
| # As with geo, if the "latitude" and "longitude" classes are omitted, the two values MUST be comma <!-- OR IS IT A SEMICOLON? Not specified on [[geo]] --> separated and latitude MUST be first:<code><nowiki><span class=geo">37.386013,-122.082932</span></nowiki></code> | # As currently with geo, if the "latitude" and "longitude" classes are omitted, the two values MUST be comma <!-- OR IS IT A SEMICOLON? Not specified on [[geo]] --> separated and latitude MUST be first:<code><nowiki><span class=geo">37.386013,-122.082932</span></nowiki></code> | ||
| :Also: | :Also: | ||
| :*If latitude is present, so MUST be longitude, and vice versa. | :*If latitude is present, so MUST be longitude, and vice versa. | ||
Revision as of 20:09, 11 December 2006
Geo Extension Straw-Man Proposal
Further to proposals for luna and mars equivalents to geo, the following is a "straw-man" proposal, to allow further debate to take place. Please feel free to critique it harshly but fairly!
Author
Straw-Man
<span class="geo">
  <span class="body">
    Mars 1
  </span>
  <span class="schema">
    [name of mapping schema] 2
  </span>
  <span class="latitude">37.386013</span>, 
  <span class="longitude">-122.082932</span> 3
</span>
Notes
- A list of acceptable, case-insensitive, values for 'body' would need to be drawn up (e/g/ "Earth", "Mars", "Luna", "Venus", etc.) wither "Earth" being assumed if none is specified.
- A list of acceptable values for 'schema' would need to be drawn up, for each body, with one being declared the default, to be used if no value is present.
- As currently with geo, if the "latitude" and "longitude" classes are omitted, the two values MUST be comma  separated and latitude MUST be first:<span class=geo">37.386013,-122.082932</span>
- Also:
- If latitude is present, so MUST be longitude, and vice versa.
- The same number of decimal places SHOULD be used in each value.
 
Issues
- Should other bodies be included in geo, or have stand-alone microformats?
- What effect will this have on existing 'geo' parsers, and it is safe to ignore that?
- What appropriate schemas exist?
- Lunar: Mean Earth Polar Axis
- ??
 
- Luna is the scientific name for Earth's moon. Should we use that, or reserve "Moon"?
- Is it appropriate to use the name "geo" (which means "Earth") for other bodies?
- is body an acceptable class name, given that it's also an HTML element?
Comments
???