place-brainstorming: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 20: | Line 20: | ||
** photo ('''<code>photo</code>''').(permalink). optional. | ** photo ('''<code>photo</code>''').(permalink). optional. | ||
** url ('''<code>url</code>''').(permalink). optional. | ** url ('''<code>url</code>''').(permalink). optional. | ||
=== Field and Element details === | |||
==== hplace ==== | |||
* A place element is identified by the class name <code>hplace</code>. | |||
* A place element should represent a geospatial place or area. | |||
* A place element {{could}} have a nested sub places. | |||
==== name ==== | |||
* A place name element is identified by the class name <code>name</code>. | |||
* A place element {{may}} be defined. |
Revision as of 19:47, 30 March 2012
<entry-title>place</entry-title> This document represents a draft microformat specification. Although drafts are somewhat mature in the development process, the stability of this document cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Watch this wiki page, or follow discussions on the #microformats IRC channel to stay up-to-date.
Draft Specification
- Editor/Author
- Flávio Oliveira
Copyright
Per the public domain release on Flávio Oliveira, this specification is released into the public domain.
Format
- hplace (
hplace
). required.
Field and Element details
hplace
- A place element is identified by the class name
hplace
. - A place element should represent a geospatial place or area.
- A place element Template:could have a nested sub places.
name
- A place name element is identified by the class name
name
. - A place element MAY be defined.