geo-cheatsheet: Difference between revisions
Jump to navigation
Jump to search
({1}) |
m (Reverted edits by VimonDarva (Talk) to last version by AndyMabbett) |
||
| (12 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
<h1>geo cheatsheet</h1> | <h1>geo cheatsheet</h1> | ||
[[geo]] properties and how to use them. | |||
==Properties (Class Names)== | ==Properties (Class Names)== | ||
| Line 9: | Line 11: | ||
{{cheatsheet-key}} | {{cheatsheet-key}} | ||
==Notes== | ===Notes=== | ||
* | *{{rfc-2119-intro}} | ||
{{geo-note}} | |||
==Related pages== | ==Related pages== | ||
{{geo-related-pages}} | {{geo-related-pages}} | ||
*{{cheatsheets}} | *{{cheatsheets}} | ||
Latest revision as of 21:50, 20 December 2008
geo cheatsheet
geo properties and how to use them.
Properties (Class Names)
- geo {1}
- latitude?
- longitude?
Key
Based on Perl's standard quantifiers:
| bold {1} | MUST be present exactly once |
| italic* | OPTIONAL, and MAY occur more than once |
| + | MUST be present, and MAY occur more than once |
| ? | OPTIONAL, but MUST NOT occur more than once |
| [square brackets] | list of common values |
| (parentheses) | data format |
| # | comment |
| ! | awaiting documentation |
Notes
- The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
- Coordinates MUST use the datum of WGS84.
- If latitude is present, so MUST be longitude, and vice versa.
- Coordinates MAY be combined a single <abbr> element; then the latitude and longitude MUST be separated by a semicolon in the title attribute and latitude MUST be first:
<abbr class="geo" title="37.386013;-122.082932">home</abbr>
- Best practice is that the same number of decimal places SHOULD be used in each value, with trailing zeroes if applicable.
- Some sources for latitude/ longitude coordinates
Related pages
- Geo
- Geo cheatsheet
- Geo examples
- geo formats - previous/other attempts at geo related formats
- Geo brainstorming - brainstorms and other explorations relating to Geo (and Geo in hCard).
- see also hCard brainstorming
- Geo advocacy - encourage others to use Geo.
- Geo examples in the wild
- Geo forms part of hcard, so please use:
- hCard FAQ. If you have any questions about Geo, check the hCard FAQ.
- hCard feedback
- hCard issues
- location-formats - research which led to the development of Geo.
- proposed extensions
- geo-extension-nonWGS84 - extend Geo for representing coordinates on other planets, moons etc.; and for other terrestrial schema
- geo-extension-waypoints - extend Geo for representing: sets of waypoints; tracks; routes; and boundaries
- Geo profile - draft
- Other cheatsheets: hAtom cheatsheet, hCard cheatsheet (also adr cheatsheet + geo cheatsheet), hCalendar cheatsheet, hResume cheatsheet, hReview cheatsheet, PDF cheatsheet