hcard-input-brainstorming - Revision history

GlennJones: Added link to also see

2011-04-23T08:30:18Z

Added link to also see

← Older revision		Revision as of 08:30, 23 April 2011
Line 291:		Line 291:
	* [[hcard-input-examples]]		* [[hcard-input-examples]]
	* [[hcard-input-formats]]		* [[hcard-input-formats]]
			* [[hcard-input-repeatable]]

GlennJones: Added notes/ideas from brighton meet-up

2011-04-15T10:10:30Z

Added notes/ideas from brighton meet-up

@@ Line 39: / Line 39: @@
 This would allow authors and applications to determine the intended use case i.e. the microformat mark-up is for form auto-fill. It would also be a simple task to update the current generalist parsers to ignore the mark-up if they were looking for content only. By default, most of the current parsers would already ignore an empty form marked-up with microformats as the required properties such as fn in hCard would be blank.
 === Form fields should use the classname attribute ===
@@ Line 52: / Line 47: @@
 &lt;input class=&quot;fn&quot; id=&quot;name&quot; type=&quot;text&quot; /&gt;
 </nowiki></pre>
 === Text inputs and textareas ===
@@ Line 172: / Line 172: @@
 An auto-fill application working in a browser would duplicate the whole DOM node and append it as a sibling. All element ids and form field names would be appended with an index number to keep the HTML valid. The label for attribute would also be updated to any changed id reference.
 === Repeating microformat structures within one form ===
@@ Line 186: / Line 196: @@
 &lt;/form&gt;
 </nowiki></pre>
 === Defining types in the classname attribute ===
@@ Line 195: / Line 211: @@
 &lt;input class=&quot;tel fax&quot; name=&quot;fax-number&quot; type=&quot;text&quot; /&gt;
 </nowiki></pre>
 === String Concatenation ===
@@ Line 203: / Line 234: @@
 &lt;input class=&quot;category comma-space-delimited&quot; name=&quot;tags&quot; type=&quot;text&quot; /&gt;
 </nowiki></pre>
 === Logical operators "or" ===
@@ Line 214: / Line 263: @@
 &lt;input class=&quot;extended-address street-address or&quot; name=&quot;address3&quot; type=&quot;text&quot; /&gt;
 </nowiki></pre>
 == <input type="vcard"> ==

GlennJones: Added notes from meet-up as discussion

2011-04-15T09:24:29Z

Added notes from meet-up as discussion

← Older revision		Revision as of 09:24, 15 April 2011
Line 39:		Line 39:

	This would allow authors and applications to determine the intended use case i.e. the microformat mark-up is for form auto-fill. It would also be a simple task to update the current generalist parsers to ignore the mark-up if they were looking for content only. By default, most of the current parsers would already ignore an empty form marked-up with microformats as the required properties such as fn in hCard would be blank.		This would allow authors and applications to determine the intended use case i.e. the microformat mark-up is for form auto-fill. It would also be a simple task to update the current generalist parsers to ignore the mark-up if they were looking for content only. By default, most of the current parsers would already ignore an empty form marked-up with microformats as the required properties such as fn in hCard would be blank.

			<div class="discussion">
			* Monday 12 April - [[events/2011-04-12-uk#Using_the_class_attribute_and_hierarchies\| Brighton meet-up]] There was full agreement for the use of the className attribute instead of the form field name attribute. The name attribute can only take a single value and does not give enough flexibility to the author of a form as the name maybe dictated by the server side code.
			** +1 [[User:GlennJones\|Glenn Jones]]
			</div>

	=== Form fields should use the classname attribute ===		=== Form fields should use the classname attribute ===

GlennJones: Logical operators

2011-02-15T15:12:53Z

Logical operators

@@ Line 154: / Line 154: @@
 Min and Max checking on form fields
 If a <code>min</code> or <code>max</code> attribute exists for a number or datetime input the value being passed needs to be checked to make sure it is in range before the input is updated.
 == <input type="vcard"> ==

TobyInk at 15:04, 15 February 2011

2011-02-15T15:04:10Z

← Older revision		Revision as of 15:04, 15 February 2011
Line 154:		Line 154:
	Min and Max checking on form fields		Min and Max checking on form fields
	If a <code>min</code> or <code>max</code> attribute exists for a number or datetime input the value being passed needs to be checked to make sure it is in range before the input is updated.		If a <code>min</code> or <code>max</code> attribute exists for a number or datetime input the value being passed needs to be checked to make sure it is in range before the input is updated.

			== <input type="vcard"> ==

			Hey, that would be nice: if "vcard" were just an input type in forms. My browser could fill it in with my vCard, or with a vCard read from disk, or with data scraped from an hCard somewhere online. I wonder how doable this is using a JS shim?

	== see also ==		== see also ==

GlennJones: Mark-up examples

2011-02-15T14:55:01Z

Mark-up examples

@@ Line 48: / Line 48: @@
 </nowiki></pre>
-=== Text inputs and Textareas ===
+=== Text inputs and textareas ===
 The mapping of content into text inputs and textareas is relatively straightforward, matches are made on the classname attribute and the whole value is used to fill in the form field.
@@ Line 57: / Line 57: @@
 </nowiki></pre>
 == see also ==

GlennJones: The input classname

2011-02-15T14:35:58Z

The input classname

@@ Line 26: / Line 26: @@
 === 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 ==

GlennJones: Design goals

2011-02-15T14:21:25Z

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 compound input fields, e.g. City, State Zip all in one field (per [[hcard-input-examples#Yelp_add_business|Yelp add business example]])
 == see also ==

Tantek: 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

2009-06-12T07:26:52Z

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

New page

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-input|hCard for input]] into forms for enabling [[hcard-parsing-brainstorming#forms_auto-fill|hCard forms auto-fill]] and [[hCard]] copy + paste.

{{stub}}

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

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

Details:
* how to markup <code><select></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]])

== see also ==
* [[hcard-input]]
* [[hcard-input-examples]]
* [[hcard-input-formats]]