Development:Planning:Microformats - Revision history

Sardisson: /* Links */ who needs built-in support when you have this bookmarklet :P

2006-09-26T09:40:45Z

Links: who needs built-in support when you have this bookmarklet :P

ChrisCasciano: /* Links */

2006-09-16T04:45:20Z

Links

Maxr: /* Links */

2006-08-30T05:50:41Z

Links

ChrisCasciano: link to firefox newsgroup discussion for reference

2006-08-02T14:11:50Z

link to firefox newsgroup discussion for reference

Froodian at 09:01, 1 August 2006

2006-08-01T09:01:01Z

Maxr: My thoughts (and some typo fixes)

2006-08-01T06:34:20Z

My thoughts (and some typo fixes)

Maxr: Page styling

2006-08-01T05:58:24Z

Page styling

Maxr: /* Background */ typos

2006-08-01T05:56:15Z

Background: typos

Maxr: Microformats moved to Development:Planning:Microformats: It's a planning doc.

2006-08-01T05:44:08Z

Microformats moved to Development:Planning:Microformats: It's a planning doc.

ChrisCasciano: created page documenting some links and thoughts

2006-06-24T00:05:03Z

created page documenting some links and thoughts

New page

== Microformat Discovery ==

=== Background ===

[http://microformats.org/ Microformats] are a collection of standards or conventions for marking up data with XHTML to allow that data to be more findable and reusable. Examples include [http://microformats.org/wiki/hcard hcard] for marking up contact information and [http://microformats.org/wiki/hcalendar hcalendar] for marking up events. That data can then be extracted from the HTML document via XSL, dom manipulation or other method and repurposed or exported into other applications (like iCal or AddressBool.app) or saved in some intermediate format.

Microformats aren't a new technology or other datatype embedded via XL nsamespaces or other method. All the magic is done via XHTML attributes (class, rel, title). This [http://tantek.com/microformats/hcard-creator.html simple hcard creation tool] provides a good visual example of how this works at the markup level.

Where Camino fits into the picture is up for discussion, but some form of discovery of formats is the first goal followed closely behind by export or hand off to other tools, or in some cases handing inside of Camino itself.

=== Links ===

* [http://www.hicksdesign.co.uk/journal/a-proposal-for-a-safari-microformats-plugin Jon Hicks blog post] on safari plugin ui proposal
* [https://addons.mozilla.org/firefox/2240/ Tails Firefox extension]
* [http://microformats.org/wiki/user-interface Microformats.org wiki UI discussion] -- collection of links to other implementations and discussions

=== Microformats List ===

For starters, here's a list of different accepted and/or proposed microformats. Each type of data should be discssed somewhat independantly in terms of what handling (if any) is done inside camino

==== Specifications ====

* hCalendar
* hCard
* rel-license
* rel-nofollow
* rel-tag
* VoteLinks
* XFN
* XMDP
* XOXO

==== Drafts ====
* adr
* geo
* hAtom
* hResume
* hReview
* rel-directory
* rel-enclosure
* rel-home
* rel-payment
* Robots Exclusion
* xFolk

=== Initial Brain Dump by [[User:ChrisCasciano]] ===

There are a lot of items listed above, all in various states of stability and implementability, but I see them generally breaking down into three categories:

* Data you'd want to hand off to or export to another application (hcard, hatom, hcalendar)
* Data (or data elements) you may want the browser to do something with internally (XFN, rel-tag, rel-license XOXO)
* Data that isn't helpful to a user, but directed more at spiders or other consuming applications (hresume or hreview in whole parts, no-follow)

What I think is essential at this state in planning the Camino support for Microformats is the following:

* Deciding what formats to support
* Nailing detection of the formats chosen
* Deciding what to do with that infomation (e.g. exporting a vcard vs. trying to pass calendar info directly to iCal)
* Developing some clean UI that makes it all work without getting in the way

I think a good place to focus (as the others form the links already have) are with support for detecting and handing off hcard, hcalendar and hatom formats and looking at new UI / context menu items for enhancing the link types like rel-tag, rel-license and XFN

In the end, the process can probably take a lot from the feed discovery bits, though there will surely be some differences in UI both in selection and in handing off the item to other applications.

@@ Line 15: / Line 15: @@
 * [http://www.digital-web.com/articles/the_big_picture_on_microformats/ Digital Web Magazine "The Big Picture on Microformats"]
 * [http://hicksdesign.co.uk/journal/highlight-microformats-with-css Jon Hicks, Highlight Microformats with CSS]  - a sample user style sheet modification for showing microformat content in pages
 == Microformats List ==

@@ Line 14: / Line 14: @@
 * [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/4dc6b2c87c865b94 Thread on firefox support from mozilla.dev.planning]
 * [http://www.digital-web.com/articles/the_big_picture_on_microformats/ Digital Web Magazine "The Big Picture on Microformats"]
 == Microformats List ==

@@ Line 13: / Line 13: @@
 * [http://microformats.org/wiki/user-interface Microformats.org wiki UI discussion] -- collection of links to other implementations and discussions
 * [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/4dc6b2c87c865b94 Thread on firefox support from mozilla.dev.planning]
+* [http://www.digital-web.com/articles/the_big_picture_on_microformats/ Digital Web Magazine "The Big Picture on Microformats"]
 == Microformats List ==

← Older revision		Revision as of 14:11, 2 August 2006
Line 12:		Line 12:
	* [https://addons.mozilla.org/firefox/2240/ Tails Firefox extension]		* [https://addons.mozilla.org/firefox/2240/ Tails Firefox extension]
	* [http://microformats.org/wiki/user-interface Microformats.org wiki UI discussion] -- collection of links to other implementations and discussions		* [http://microformats.org/wiki/user-interface Microformats.org wiki UI discussion] -- collection of links to other implementations and discussions
		+	* [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/4dc6b2c87c865b94 Thread on firefox support from mozilla.dev.planning]

← Older revision		Revision as of 09:01, 1 August 2006
Line 82:		Line 82:

	Thoughts? Comments?		Thoughts? Comments?
		+
		+	----
		+
		+	* I like it the basic UI design. Hwaara and I were talking about making the icons have a "glowing" icon much like the proposed IM mockup [http://wiki.mozilla.org/Image:Fx2-new-theme-concept-glows.png here], which could solve some of the "they're invisible on the status bar" arguments. [[User:Froodian\|Froodian]] 02:01, 1 August 2006 (PDT)

@@ Line 16: / Line 16: @@
 == Microformats List ==
-For starters, here's a list of different accepted and/or proposed microformats. Each type of data should be discssed somewhat independantly in terms of what handling (if any) is done inside camino
+For starters, here's a list of different accepted and/or proposed microformats. Each type of data should be discussed somewhat independently in terms of what handling (if any) is done inside Camino.
 === Specifications ===
@@ Line 56: / Line 56: @@
 * Deciding what formats to support
 * Nailing detection of the formats chosen
-* Deciding what to do with that infomation (e.g. exporting a vcard vs. trying to pass calendar info directly to iCal)
+* Deciding what to do with that information (e.g. exporting a vcard vs. trying to pass calendar info directly to iCal)
 * Developing some clean UI that makes it all work without getting in the way
@@ Line 62: / Line 62: @@
 In the end, the process can probably take a lot from the feed discovery bits, though there will surely be some differences in UI both in selection and in handing off the item to other applications.

@@ Line 1: / Line 1: @@
-== Microformat Discovery ==
+== Background ==
 [http://microformats.org/ Microformats] are a collection of standards or conventions for marking up data with XHTML to allow that data to be more findable and reusable. Examples include [http://microformats.org/wiki/hcard hcard] for marking up contact information and [http://microformats.org/wiki/hcalendar hcalendar] for marking up events. That data can then be extracted from the HTML document via XSL, DOM manipulation or other method and repurposed or exported into other applications (like iCal or AddressBook.app) or saved in some intermediate format.
@@ Line 9: / Line 7: @@
 Where Camino fits into the picture is up for discussion, but some form of discovery of formats is the first goal followed closely behind by export or hand off to other tools, or in some cases handing inside of Camino itself.
-=== Links ===
+== Links ==
 * [http://www.hicksdesign.co.uk/journal/a-proposal-for-a-safari-microformats-plugin Jon Hicks blog post] on safari plugin ui proposal
@@ Line 16: / Line 14: @@
-=== Microformats List ===
+== Microformats List ==
 For starters, here's a list of different accepted and/or proposed microformats. Each type of data should be discssed somewhat independantly in terms of what handling (if any) is done inside camino
-==== Specifications ====
+=== Specifications ===
 * hCalendar
@@ Line 32: / Line 30: @@
 * XOXO
-==== Drafts ====
+=== Drafts ===
 * adr
 * geo
@@ Line 46: / Line 44: @@
-=== Initial Brain Dump by [[User:ChrisCasciano]] ===
+== Initial Brain Dump by [[User:ChrisCasciano]] ==
 There are a lot of items listed above, all in various states of stability and implementability, but I see them generally breaking down into three categories:

← Older revision	Revision as of 05:44, 1 August 2006
(No difference)