Difference between revisions of "hcard-input-brainstorming"

From Microformats Wiki
Jump to navigation Jump to search
(drafted with rough outline of proposal thoughts, noted a couple of issues off the top of my head based on experience with real world examples so far)
 
m (Design goals)
Line 14: Line 14:
 
* how to markup <code>&lt;select&gt;</code> elements (e.g. for state/region and country name, many [[hcard-input-examples|examples]])
 
* how to markup <code>&lt;select&gt;</code> elements (e.g. for state/region and country name, many [[hcard-input-examples|examples]])
 
* how to markup compound input fields, e.g. City, State Zip all in one field (per [[hcard-input-examples#Yelp_add_business|Yelp add business example]])
 
* how to markup compound input fields, e.g. City, State Zip all in one field (per [[hcard-input-examples#Yelp_add_business|Yelp add business example]])
 +
 +
=== Design goals for “input microformats” === 
 +
Use the current microformat authoring conventions and schemas where possible. This goal should be understood in the light that most microformats are designed as hierarchical structures and whereas forms are not. Some breaking changes maybe required to deal with this fundamental difference, but these should be kept to a minimum.
 +
 +
Where possible any differences in authoring should be dealt with by creating a common superset of additional classes for auto-filling applications. This approach will limit the cognitive load on authors and allow the reuse of current parsers.
 +
 +
A primary design goal must be the consideration of i18n. This most effects dates and durations. The individual implementations may allow for language specific formatting, but it should not be part of this specification.
 +
   
 +
It should be reasonably easy for an author to add classes to a pre-existing form without having to change its data structure.
 +
 +
=== Auto-fill application vs generalist parsing documentation ===
 +
Auto-filling a form and parsing its contents are two different operations, although they share the same conventions and schemeas. The discussion on how a microformat parser should extract values from form elements can be different to the needs of an application that can auto-fill a form using microformat data.
  
 
== see also ==
 
== see also ==

Revision as of 14:21, 15 February 2011

This page is for documenting previous efforts at formats for web forms that input contact information (people or organizations/venues) towards brainstorming the use of hCard for input into forms for enabling hCard forms auto-fill and hCard 1.0 copy + paste.

This article is a stub. You can help the microformats.org wiki by expanding it.

proposals

hCard properties on form elements

Use hCard properties as class names on form elements inside a container (such as a containing <fieldset> or the containing <form>) to indicate that those form elements accept values with the semantics of the respective hCard properties.

Example:

  • how to markup a containing <form>, <fieldset>, or <div> element with the root class name vcard.
  • how to markup <input type="text" > elements with hCard property names

Details:

  • how to markup <select> elements (e.g. for state/region and country name, many examples)
  • how to markup compound input fields, e.g. City, State Zip all in one field (per Yelp add business example)

Design goals for “input microformats”

Use the current microformat authoring conventions and schemas where possible. This goal should be understood in the light that most microformats are designed as hierarchical structures and whereas forms are not. Some breaking changes maybe required to deal with this fundamental difference, but these should be kept to a minimum.

Where possible any differences in authoring should be dealt with by creating a common superset of additional classes for auto-filling applications. This approach will limit the cognitive load on authors and allow the reuse of current parsers.

A primary design goal must be the consideration of i18n. This most effects dates and durations. The individual implementations may allow for language specific formatting, but it should not be part of this specification.

It should be reasonably easy for an author to add classes to a pre-existing form without having to change its data structure.

Auto-fill application vs generalist parsing documentation

Auto-filling a form and parsing its contents are two different operations, although they share the same conventions and schemeas. The discussion on how a microformat parser should extract values from form elements can be different to the needs of an application that can auto-fill a form using microformat data.

see also