mobile

2008-09-12T12:16:35Z

LanceW: /* iPhone */

<h1>mobile</h1>

'''This page is a stub and would benefit from your contributions!'''

{{TOC-right}}
Mobile and microformats make for a particularly powerful combination. Microformats help users complete more tasks with fewer steps, and requiring fewer steps is especially important in mobile applications. This page lists current known mobile support of microformats, and ideas/suggestions for mobile applications that could use microformats.

== mobile support ==
=== Treo ===
The Treo browser has good integration with the Treo address book and calendar.

* '''[[hCard]] support.''' Clicking on a "Add to Address Book" link (e.g. on [http://technorati.com/about/contact.html Technorati's contact page]) will prompt the user to add that [[hCard]] directly to their Treo address book.

* '''[[hCalendar]] support.''' Clicking on an "Add to Calendar" link (e.g. like on the [[events]] page) will prompt the user to add [[hCalendar]] events directly to their Treo calendar. (Note: the "Subscribe to" links that use <code>webcal:</code> do not appear to currently work on the Treo.)

=== BlackBerry ===
No support for hCard/vCard/hCalendar/iCalendar in BlackBerry 8700, 81xx, 88xx models. Anybody have experience either way with BlackBerry 9000?
* see [[mobile-advocacy]]

=== iPhone ===
No support for hCard/vCard/hCalendar/iCalendar in first generation iPhone / Safari / Webkit.
No support on iPhone 3G software v2.0.2(5C1), clicking the "add to address book" link as above results in a message saying "Safari can't download this file".

* see [[mobile-advocacy]]

== mobile application thoughts ==
If this section gets too big, we can move it to a separate page like [[mobile-user-interface]].

=== browser address book integration ===
Every mobile browser should auto-detect [[hCards]] and provide the user a simple/unobtrusive user interface to add them to their mobile address book.

Example: you are browsing a business site, or business listings (e.g. on Google Maps) which list business name, telephone number, address, URL etc. With a simple click or two, it should be possible to save those listings in your address book for future reference or navigation (see below).

=== browser calendar integration ===
Every mobile browser should auto-detect [[hCalendar]] events and provide the user a simple/unobtrusive user interface to add (or subscribe to) them to their mobile address book.

Example: you are browsing an event site (e.g. Upcoming.org), or event listings on a business site, and see event names, start/end times, locations, etc. With a simple click or two, it should be possible to save those events in your calendar for future reference / alarms etc.

=== mapping and navigation ===
[[adr]] and [[geo]] microformats are useful for mobile mapping and navigation applications. (from tweet: [http://twitter.com/microformats/statuses/916437155]).

The most obvious thing to do is extending support for [[geo]] so you can get directions to places from browsers, so you could, for example, get off the train, go to Upcoming.org on your mobile, click the address and have the mobile mapping applications walk you there. (from tweets [http://twitter.com/markng/statuses/916433126], [http://twitter.com/markng/statuses/916436304]).

=== url dialing ===
Most phones have a way of invoking a call from the browser or from applications built in the native languages (JavaME, Python etc.) - it'd be useful if you could have a really simple way of putting in a URI, and it finding the relevant hCard on the page and auto-dials it. I can remember "companyname.com" but not some long phone number. I'm thinking of building something broadly on this line using JavaME, backed by a web service to get the numbers and return them to the device (favouring hCards, but regexing for things that look like phone numbers if it doesn't find any). This came to me a while back when I was walking around London trying to find a shop - I knew their URL but had no idea of their phone number. --[[User:TomMorris|TomMorris]] 05:07, 12 Sep 2008 (PDT)

== thanks ==
* [http://twitter.com/bryanrieger @bryanrieger] for [http://twitter.com/bryanrieger/statuses/916416344 asking the question] on Twitter.
* [http://twitter.com/markng @markng] for providing some ideas with user scenarios.

== see also ==
* [[advocacy]]
* [[mobile-advocacy]]
* [[user-interface]]

product-brainstorming

2007-12-10T11:45:47Z

LanceW: /* Random Thoughts */

<h1> product microformat brainstorming </h1>
This is brainstorming for a [[product]] microformat per the [[process]]. See also [[product-examples]], and [[product-formats]].

{{TOC-right}}

== Contributors ==
* Aaron Gustafson, [http://easy-designs.net/ Easy! Designs]
* Craig Cook, [http://focalcurve.com/ Focal Curve]

== The Problem ==

There are numerous ways to publish product information on the web, but nothing is stanardized. It would be useful to have standardized product information on the web for creating mash-up applications which could

* allow aggregated product details to be linked to from hListings or hReviews
* match hListings to hReviews
* aggregate product-specific information from across the web
* aggregate and compare like products based on features

== To be incorporated ==
The following pages should be incorporated into this page:
* [[rel-product-brainstorming]]
* [[hproduct-feedback]]
And then those pages should simply redirect to this one via: <nowiki>#redirect [[product-brainstorming]]</nowiki>

== Elements that come up often in practice ==

Examples of elements that might be included because they seem to come up often in user- and CMS-generated product publishing, include the following:

=== Base Elements ===

* name (or fn)
* image (could be sub-categorized)
** thumb (for thumbnail)
** full (for full size image)
** photo (for a photograph)
** illo (for an illustration).
* description (could be sub-categorized)
** summary
** extended
* brand
* uri (or url) - URI for the product at its brand website; not to be confused with the hListing 'permalink'.
* msrp

=== Extensibility ===
Being that so many products in the world have specific charachteristics or properties, we thought it might be wise to create a means of standardizing the listing of that information, setting the stage for possible subformats of a product microformat. This could be done by setting up property value pairs or groups using a <code>CLASS</code> of "p-v". It would be possible to offer a few means of doing this.

==== Natural language property-value association ====

<pre><nowiki><p class="p-v">The <span class="property">dimensions</span> of this book are
<span class="value">6½"(<abbr title="width">W</abbr>) ×
12"(<abbr title="height">H</abbr>) ×
1¾"(<abbr title="depth">D</abbr>)</span></p></nowiki></pre>

==== List property-value association (pairs) ====

<pre><nowiki><ul>
<li class="p-v">
<span class="property">Mileage</span>:
<em class="value">34,787</em>
</li>
<li class="p-v">
<span class="property">Year</span>:
<em class="value">2006</em>
</li>
<li class="p-v">
<span class="property">Exterior Color</span>:
<em class="value">Burgundy</em>
</li>
<li class="p-v">
<span class="property">Body Style</span>:
<em class="value">Hatchback</em>
</li>
</ul></nowiki></pre>

==== List property-value association (groups) ====

Note: as a <code>DL</code> contains semantic property-value pairs/groups, setting a <code>CLASS</code> of "p-v" should be enough (reducing extra markup).

<pre><nowiki><dl class="p-v">
<dt>Mileage</dt>
<dd>34,787</dd>
<dt>Color</dt>
<dd>Burgundy (Exterior)</dd>
<dd>Tan (Interior)</dd>
</dl></nowiki></pre>

==== Non-visible property names ====

We have considered the possibility of allowing property names to be invisible to users by allowing the addition of the property name as a class immediately following the "propery" <code>CLASS</code> keyword:

<pre><nowiki><ul class="p-v">
<li class="property mileage">34,787</li>
<li class="property year">2006</li>
<li class="property color-exterior">Burgundy</li>
<li class="property body-style>Hatchback</li>
</ul></nowiki></pre>

Parsing would be a bit trickier, but from the perspective of someone marking up the document, it is pretty simple and straightforward.

=== Suggested Additions ===

* image sub-categorization (could make use of [[media-info|Media microformat]]?):
** thumb (for thumbnail)
** full (for full size image)
** photo (for a photograph)
** illo (for an illustration).
* description sub-categorization:
** summary
** extended
* uri (or url) - URI for the product at its brand website; not to be confused with the hListing 'permalink'.

== Isn't this duplicating hListing and hReview? ==

No, a product microformat would not seek to compete with [[hlisting|hListing]] or [[hreview|hReview]], it simply aims to enhance them. In either of these microformats, the <em>item</em> could easily contain the product. Also, a product microformat is the more appropriate place for Manufacturer's Suggested Retail Price (MSRP), which is not likely to be the final price of the product being listed. The actual price/sale price/final price should be solely in the domain of hListing.

== Random Thoughts ==

Please add your thoughts & feelings below. If you are interested in getting involved in the development of this microformat. Please contact aaron [at] easy-designs [dot] net and/or join the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats mailing list].

===Ronnos===

Wouldn't the release date of the product be a good addition? I'm writing product re- and previews. I use hReviews to give my opinion about the product, but there's now way to indicate that the product is or is not in stores yet. As far as i can see, the release date is a usefull product attribute, not only usefull in combination with other Microformats, but also for indicating the "age" of a product.

* Release date is a good idea but how to specify it? Is it the date on which the product first becomes available in shops? Would you have a per-region release date (certainly applicable to DVDs, CDs and at least some electronic devices such as gaming consoles) --[[User:SMulcahy|SMulcahy]] 13:38, 15 Feb 2007 (PST)

===Aaron Gustafson===

Actual price, savings, discounts, etc. should be part of hListing instead of a product microformat. MSRP (suggested retail price) should be part of the product microformat, however.
*Not all products have a MSRP. [[User:AndyMabbett|Andy Mabbett]] 09:08, 19 Nov 2006 (PST)
**I agree, they don't which is why it should not be required. [[User:AaronGustafson|Aaron Gustafson]] 16:60, 20 Nov 2006 (MST)

===Andy Mabbett===
Please see my [http://microformats.org/discuss/mail/microformats-discuss/2006-November/007281.html proposal, on the mailing list] -- [[User:AndyMabbett|Andy Mabbett]] 09:08, 19 Nov 2006 (PST)
* I agree with the idea of enabling sub-product formats, but am not sure I like the idea of a "wrapper" for hReview or hListing, I think the item should exist ''within'' an instance of one of those microformats. [[User:AaronGustafson|Aaron Gustafson]] 16:60, 20 Nov 2006 (MST)
**There may be more than one review of a product, on one page e.g. [http://www.amazon.co.uk/o/ASIN/B000I0SGSA/ref=pd_rvi_gw_1/026-5782158-8338825] [[User:AndyMabbett|Andy Mabbett]] 00:54, 21 Nov 2006 (PST)

===Adam Craven===

A product microformat will definitely be one of the largest microformats.

What about specifications of products, which is important for data aggregation. To categories every type and variation of a product would be mad. So how should the hurdle be crossed, if at all?

The nearest related uF is the citation format, although it isn't overly suited.

===Stephen Mulcahy===

As with microformats in general maybe the approach to take to specifications of products is to let people who need/want them start specifying the ones they are interested in - we don't need an exhaustive universe of potential things categorised. See my posting for some other comments here - http://microformats.org/discuss/mail/microformats-discuss/2007-January/008379.html , in particular note that I think the hard part of this is defining the specifications of individual products. I'm happy to start on the laptop one ... it would be good to have some laptop vendor on board but maybe its too soon for anyone to be interested.

* Some potential subformats (what kind of naming scheme do we want to use here)
** hNotebook (or hProductNotebook ?) - for products like laptops, notebooks, tablets
*** os
*** bundledSoftware
*** size (height, width, depth)
*** weight (units?)
*** processor
*** display
**** size
**** resolution
*** video (for video card)
*** embeddedVideo (boolean)
*** hard drive (maybe manufacturer,model,size? .. eeek is hard drive a hProduct subformat itself?)
*** memory (type and size?)
*** optical drive (types?)
*** battery
*** warranty
*** videoOut (types supported - is it acceptable have a bunch of boolean options for laptop features that may or may not exist on a particular model?)
** hDesktop - for desktop PCs and similar
** hConsole - for gaming consoles such as the Wii, PS3 and XBox360
** hMobilePhone (or hMobileDevice .. not sure we generally want generic subcategory since the whole point of subformats is to give a concrete set of characteristics, or do we want to have nesting of subformats to capture general characteristics at higher levels?).
** hPda (maybe a hMobileDevice .. it starts getting a bit fuzzy here)

Maybe we should talk to some projects like the Linux on Laptops [http://www.linux-laptop.net/] project and get them to encourage contributors to mark-up their laptop reviews in hProductNotebook? --[[User:SMulcahy|SMulcahy]] 07:51, 20 Feb 2007 (PST)

Attempting to create a taxonomy of product subformats is a really bad idea. There are too many different kinds of products. Large e-commerce sites keep many employees busy with product taxonomy work, not something a standard should attempt to do. [[User:Tantek|Tantek]] 23:04, 21 Aug 2007 (PDT)

===Robbie van der Blom===
What about unique identifiers for products like ISBN nr. and the UPC codes for a product? My gut feeling is that they should be part of a product microformat.

With respect to the above, do we really need to talk about hProductNotebook etc. this seems odd.

===Adam Craven===

In relation to the p-v and general property values. The [[abbr-design-pattern]] could be used over the hidden class variable. So
<pre><nowiki>
<h1 class="name">Breitling SuperOcean Chrono</h1>
Water resistant up to <span class="p-v"><abbr class="property value" title="water-resistance">1500m</abbr></span></nowiki></pre>

In this second example, the color is embedded within the name of the shirt itself.
<pre><nowiki><h1 class="name"><span class="p-v"><abbr class="property value" title="color">White</abbr> Coxmoor shirt</h1>
<img src="white-coxmoor-shirt.jpg" rel="image thumb" /></nowiki></pre>

For items such as books, whereby authors sometimes aren't explicitly denoted visibly (http://www.thebookpeople.co.uk/webapp/wcs/stores/servlet/product_10001_10051_47517_100_10014_10013_category_10013), rather inferred by convention. Could arguably still use the abbr pattern:

<pre><nowiki><h1><span class="name">Great Tales From English History</span> - 3 Books</h1>
by <span class="p-v"><abbr class="property value" title="author">Robert Lacey</abbr></span></nowiki></pre>

Or even
<pre><nowiki><h1><span class="name">Great Tales From English History</span> - 3 Books</h1>
<span class="p-v"><abbr class="property" title="author">by</abbr> <span class="value">Robert Lacey</span></span></nowiki></pre>

A final thought to throw in. If the property and values are within the same HTML tag, it might be possible to remove the property & value class, as the p-v indicates a property value relationship itself.

<pre><nowiki><abbr class="p-v" title="author">Robert Lacey</abbr></nowiki></pre>
What do you think?

===LanceW===

A product microformat would I think be useful for corporate sites.
For example, my employers site lists the products and services we work with, I am able to (and have) used microformats to contact details, but would like to microformat products and services. At present I have as a start added rel="product" to links to our individual product pages, but to be able to do it in a better manner would be good, also so I could microformat the product page itself so that one could find say all the products from a specific manufacturer.

== naming ==
Here are candidate names for a product microformat:
* hProduct

== proposal ==
The above brainstorming, based on [[product-examples]] and [[product-formats]] (TO BE DONE) research, should go into a proposal:
* [[hproduct-proposal|hProduct proposal]]
Currently this is premature, as the [[product-formats]] page has not yet even been created, much less researched. Per the [[process]], research on formats must be done before brainstorming or drafting a separate proposal.

== related ==
* [[product]]
* [[product-examples]]
* [[product-formats]]
* [[product-brainstorming]]

== see also ==
* [[hReview]]
* [[hListing]]

Microformats Wiki - User contributions [en]

mobile

product-brainstorming