Microformats Wiki - User contributions [en]

events/2008-london-microformats-vevent

2007-12-12T10:24:16Z

JamesDarling: /* Attending */

= London Microformats vEvent =

This is a social [[events|event]] planned for the first quarter of 2008 in London.

__TOC__

== Details ==

TBC

This page will be filled as details are decided.

== Summary ==
We hope to put on a small social event in London in the first quarter of 2008. It'll feature a couple of speakers on the topic of microformats and the semantic web and hopefully some drinks too.

== Organisers ==
*[[User:Phae|Frances Berriman]] - http://fberriman.com
*[[User:DrewMcLellan|Drew McLellan]] - http://allinthehead.com

== Attending ==
Please put yourself down if you're interested in attending an event in the first part of 2008. We're currently using this page to gauge interest right now.

* PJ Barry
* James Darling
* Add your name
* ..

== Blog Posts ==

== Photos ==

== Additional Links / Information ==

item-examples

2006-11-18T19:55:03Z

JamesDarling: Added Amazon Wishlist, British Library and Fresh Arrival

= Thing Examples =
This page is for documenting real world examples of how "things" are actually marked up and represented on the web.

= In Existing Microformats =

[[hreview|hReview]] and [[hlisting|hListing]] are applicable to things (as well as people marked up as hCards).

== EdgeIO (hListing) ==

Note that EdgeIO using [hlisting|hListing] for individual items but not for the lists of itens.

* Main URI: http://www.edgeio.com/
* Merchandise: http://www.edgeio.com/tt/merchandise
** Example: http://www.edgeio.com/item/1814754-Motorola-RAZR-north%20america
** class="summary": the title of the listed item
** class="description": the description of the listed item
** class="lister vcard": the lister
* Housing: http://www.edgeio.com/tt/housing
* Autos: http://www.edgeio.com/tt/autos

== Deal Tagger (hListing) ==

* URI: http://www.dealtagger.com/

== Cork'd (hReview) ==

* URI: http://corkd.com/
* Example: http://corkd.com/wine/view/13482
* class="item": the item being reviewed
* class="fn": the name of the item being reviewed
* Note that class="description" are not part of the item, they're part of the review!
* [[hreview|hReview]] used for each user review: <pre><nowiki>
<div id="review_9285" class="hreview">
<h5 class="item"><span class="fn">Cellarium Bisencii 2005 Muškát moravský</span></h5>
<abbr class="dtreviewed" title="20061118">
(about 2 hours ago)</abbr>
<span class="reviewer vcard">
<img class="photo" src="/img/icon-user-64.gif" height="48" width="48" alt="buddy icon" />
<a class="url fn" href="/people/cruster">cruster</a>

</span>
<abbr class="rating" title="2"><img src="/img/icon-rate2.gif" alt="**" /></abbr>
<blockquote class="description">When ... scent.</blockquote>
<p class="tags">Tasting Tags:
<a href="/tags/light" rel="tag" class="rel-tag" title="view all wines with this tag">light</a>
</p>
</div>
</nowiki></pre>
* Note:
** "vcard" is used to represent the wine, even though it isn't a person or an organization
** there is no photo of wine

== Yahoo Local (hReview) ==

* URI: http://local.yahoo.com/
* attempts to download pages outside of a browser are blocked, which is not very friendly to analysis!

== Yahoo UK Movie Reviews ==

Not sure if this is within scope (i.e. is a movie a thing?)

* URI: http://uk.movies.yahoo.com/movie-reviews/

= In Google Base =

Attributes in Google Base are open ended. For each of the following Item Types, we're identifying the attributes that Google Base displays when one attempts to edit an entry; there's also a broader list of applicable attributes, and then there's the open to add anything to a listing.

== Housing ==

Primary Attribute Types (see [http://base.google.com/base/housing.html for all]):

* [http://base.google.com/base/housing.html#title title] - listing title
* description (text)
* photos
* [http://base.google.com/base/housing.html#price price] - US dollars per item
* price type - "fixed", "negotiable" (doesn't seem to have a formal definition)
* [http://base.google.com/base/housing.html#listing_type listing type] - e.g. "for sale"...
* [http://base.google.com/base/housing.html#property_type property type] - apartment, land, farm...
* [http://base.google.com/base/housing.html#bedrooms bedrooms] - number
* [http://base.google.com/base/housing.html#area square footage] - number and unit
* [http://base.google.com/base/housing.html#bathrooms bathrooms] - number

== Products ==

Primary Attribute Types (see [http://base.google.com/base/products.html for all]):

* [http://base.google.com/base/products.html#title title] - listing title
* description (text)
* photos
* [http://base.google.com/base/products.html#price price]
* price type
* [http://base.google.com/base/products.html#quanity quanity] - number (e.g. 1)
* [http://base.google.com/base/products.html#product_type product type] - e.g. "jewlery"
* [http://base.google.com/base/products.html#condition condition] - e.g. "used"
* [http://base.google.com/base/products.html#brand brand] - e.g. "cartier"

== Vehicles ==

Primary Attribute Types (see [http://base.google.com/base/vehicles.html for all]):

* [http://base.google.com/base/vehicles.html#title title] - listing title
* description (text)
* photos
* [http://base.google.com/base/vehicles.html#price price] - US dollars per
* price type - "fixed", "negotiable" (doesn't seem to have a formal definition)
* [http://base.google.com/base/vehicles.html#quantity quantity] - a number
* [http://base.google.com/base/vehicles.html#year year]
* [http://base.google.com/base/vehicles.html#make make] - e.g. ford
* [http://base.google.com/base/vehicles.html#vehicle_type vehicle type] - e.g. car
* [http://base.google.com/base/vehicles.html#condition condition] - e.g. used

== Want Ads ==

This Item Type may not be totally applicable, but it is about "things" for sale. Primary Attribute Types (see [http://base.google.com/base/wanted.html for all]):

Primary Attribute Types (see [http://base.google.com/base/wanted.html for all]):

* [http://base.google.com/base/wanted.html#title title] - listing title
* description (text)
* photos

Google expects users of its Want Ads system to define all the appropriate attributes themselves. Further research needed here to see this actually in use.

= Other Sites =
== Craigslist ==

These examples are taken from [[listing-examples]]

* [http://www.craigslist.org/sss/ For Sale]
** email
** duration (implied)
** date
** category
** title
** description
** location
** condition
** images
** price
** availability
* [http://www.craigslist.org/wan/ Wanted]
** email
** duration
** date
** category
** title
** description
** location
** condition
** images
** price
* [http://www.craigslist.org/hhh/ Housing]
** category (rent, sale, temp)
** date
** duration (implied)
** contact info
** location
** title
** description
** size
*** bedrooms
** rent
** photos
** pet policy
** fee/no-fee
** broker/non-broker

== MLS.ca (housing) ==

* URI: http://www.mls.ca/

Attributes:

* (no title)
* MLS listing number
* description
* photos
* address (including a "district")
* sales people
* property type
* category
* house style
* age
* bedrooms
* bathrooms
* fireplace
* central a/c
* pool
* waterfront
* workshop
* house size
* lot size

== AutoTrader (vehicles) ==

== Amazon Wish-list ==

* URI: http://www.amazon.co.uk/gp/registry/registry.html/202-9388504-4042203?ie=UTF8&type=wishlist&id=21R1WHKA4PXVC

Attributes
* Image
* Title
* Author/Designer/Creator/Manufacturer
* Status (stock availability)
* Price
* Link
* Quantity Desired
* Quantity Received
* Priority (Ranking?)
* Comment

== British Library Search Results ==

* URI: http://catalogue.bl.uk

Attributes
* Number
* Author
* Title
* Year
* Shelfmarks (Subcategory Unique ID?)

== Fresh Arrival ==

Fresh Arrival post about a 'thing' that they like every day

* URI: http://www.fresharrival.com/blog/archives/2006/11/13/corner-step-can/

Attributes
* Title
* Image
* Detail
* Link

== Need ... ==
Books, ...?
What tables/fields Amazon use to catalogue their wide selection of items?

= See Also =
{{item-see-also}}

User:JamesDarling

2006-11-16T23:29:52Z

JamesDarling:

[http://abscond.org abscond.org]

item-brainstorming

2006-11-16T23:24:45Z

JamesDarling: hItems and hCards

= Item Brainstorming =

This page is to collect ideas about an "item" microformat or design pattern, for representing things that physically exist. At this point, [[DavidJanes|my]] thinking is to aim for understanding the intersection not the union of attribute of things!

== Editors ==

* [http://www.blogmatrix.com David Janes]

== Authors ==

* [http://www.blogmatrix.com David Janes]
* [http://abscond.org James Darling]
* your name here...

= Introduction to the idea =
== Rationale ==

* items/things are used in other micrformats
** [[hlisting|hListing]]
** [[hreview|hReview]]
* unlike people and places, items do not currently get a "container"; thus, attributes being associated with a (say) Review actually should be attached the thing itself
* to cut down on the work required to create new microformats about things (wine, houses, cars, ...)

== Notes ==

This is very much analogous to [[hcard|hCard]] and there is no reason that this shouldn't reuse as much as possible of this. In particular:
* fn - the name of an item
* url - the web address of an item
* photo - a photo of an item
* adr - the address of an item (for example, a house)
* geo - likewise

More of this will be discovered in the [[item-examples|examples]] discovery.

= hItem-based microformats =

== Representation ==

This may just be a design pattern -- that is, a template for create new microformats in the future. If it is a microformat, how we identify the ''type'' of thing is an open question -- we could do it like phone number types in hCard or it could be a new class element (or both). I.e. do we create a top-level class "hWine" or do we do <span class="type">wine</a>

== New Attributes ==

One can see that there are many common properties that can be shared about different types of things. Manufactor, brand name, generic name, color.... The base item microformat may avoid trying to define this and instead allow new/future microformats to do the discovery.

* Quantity - can be assumed to be 1 unless specified.

== hItem and hCard ==

Immediately the idea of a hItem demands the idea of the option for a contained hCard for the owner, but what about a large qauntity of items owned by a single owner. Would a hCard be required in each hItem, or would it be possible to wrap all the hItems in a hCard?

= See Also =

* http://microformats.org/discuss/mail/microformats-discuss/2006-November/007139.html

item-brainstorming

2006-11-16T23:12:57Z

JamesDarling: added quantity

= Item Brainstorming =

This page is to collect ideas about an "item" microformat or design pattern, for representing things that physically exist. At this point, [[DavidJanes|my]] thinking is to aim for understanding the intersection not the union of attribute of things!

== Editors ==

* [http://www.blogmatrix.com David Janes]

== Authors ==

* [http://www.blogmatrix.com David Janes]
* [http://abscond.org James Darling]
* your name here...

= Introduction to the idea =
== Rationale ==

* items/things are used in other micrformats
** [[hlisting|hListing]]
** [[hreview|hReview]]
* unlike people and places, items do not currently get a "container"; thus, attributes being associated with a (say) Review actually should be attached the thing itself
* to cut down on the work required to create new microformats about things (wine, houses, cars, ...)

== Notes ==

This is very much analogous to [[hcard|hCard]] and there is no reason that this shouldn't reuse as much as possible of this. In particular:
* fn - the name of an item
* url - the web address of an item
* photo - a photo of an item
* adr - the address of an item (for example, a house)
* geo - likewise

More of this will be discovered in the [[item-examples|examples]] discovery.

= hItem-based microformats =

== Representation ==

This may just be a design pattern -- that is, a template for create new microformats in the future. If it is a microformat, how we identify the ''type'' of thing is an open question -- we could do it like phone number types in hCard or it could be a new class element (or both). I.e. do we create a top-level class "hWine" or do we do <span class="type">wine</a>

== New Attributes ==

One can see that there are many common properties that can be shared about different types of things. Manufactor, brand name, generic name, color.... The base item microformat may avoid trying to define this and instead allow new/future microformats to do the discovery.

* Quantity - can be assumed to be 1 unless specified.

= See Also =

* http://microformats.org/discuss/mail/microformats-discuss/2006-November/007139.html