Difference between revisions of "adr-poll"

From Microformats Wiki
Jump to navigation Jump to search
 
(General comments)
Line 4: Line 4:
  
 
<blockquote>
 
<blockquote>
Where the <code>adr</code> has content, but no sub-properties, parsers ['''MAY | SHOULD | MUST'''] output the content of that <code>adr</code> as a single vCard ['''output-field'''] field.
+
Where the <code>adr</code> has content, but no valid sub-properties, parsers ['''MAY | SHOULD | MUST'''] output the content of that <code>adr</code> as a single vCard ['''output-field'''] field.
 
</blockquote>
 
</blockquote>
  
Line 36: Line 36:
  
 
===locality===
 
===locality===
 +
 +
==General comments==

Revision as of 12:18, 9 April 2007

Change to adr spec

Further to discussion at hcard-brainstorming#ADR with no children, it is proposed to amend the adr spec, and the corresponding part of the hCard spec, thus:

Where the adr has content, but no valid sub-properties, parsers [MAY | SHOULD | MUST] output the content of that adr as a single vCard [output-field] field.

Please indicate you support or objections preferred wording and choice of output-field, below, using an asterisk and three tildes (* ~~~), followed by any comments. Please indicate your preferences, even if you object to the main proposal, so that they may still be considered if the proposal carries. You may change your votes at any time, until a community decision is made.

Main proposal

Support

Object

(please give reasons)

Wording

MAY

SHOULD

MUST

Output field

street-address

extended-address

region

locality

General comments