Microformats Wiki - User contributions [en]

https://microformats.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=KevinLawver Microformats Wiki - User contributions [en] 2026-05-07T10:03:22Z User contributions MediaWiki 1.38.4 https://microformats.org/wiki/index.php?title=social-network-portability&diff=19194 social-network-portability 2007-08-01T20:34:54Z

<p>KevinLawver: /* Discussion and suggestions */</p> <hr /> <div><h1> Social Network Portability </h1><br /> <div style="float:right">__TOC__</div><br /> One of several [[user-interface]] ideas and suggestions for working with microformats.<br /> <br /> === The Problem ===<br /> Why is it that every single social network community site makes you:<br /> * re-enter all your personal profile info (name, email, birthday, URL etc.)?<br /> * re-add all your friends?<br /> <br /> In addition, why do you have to:<br /> * re-turn off notifications?<br /> * re-specify privacy preferences?<br /> * re-block [http://headrush.typepad.com/creating_passionate_users/2006/04/angrynegative_p.html negative people]?<br /> <br /> AKA "social network fatigue problem" and "social network update/maintenance problem".<br /> <br /> === The Goals ===<br /> When you join a new site, you should be able to ''import'' or preferably ''subscribe'' to<br /> * your profile information<br /> * your social network<br /> from any existing profile of yours. <br /> <br /> In addition it would be nice if preferences around:<br /> * notifications<br /> * privacy<br /> also transferred between profiles.<br /> <br /> AKA a social internetwork, a network of social networks.<br /> <br /> === Design Patterns and Recipes ===<br /> <br /> The "How To" for social network profile sites that want to solve the above problems and achieve the above goals.<br /> <br /> # Publish microformats in your user profiles:<br /> ## implement [[hcard|hCard]] on user profile pages. See [[hcard-supporting-profiles]] for sites that have already done this.<br /> ## implement [[hcard|hCard]]+[[xfn|XFN]] on the list of friends on your user profile pages. See [[hcard-xfn-supporting-friends-lists]] for sites that already do this. (e.g. [[http://twitter.com/ Twitter]]).<br /> # Subscribe to microformats for your user profiles:<br /> ## when signing up a new user:<br /> ### let a user fill out and <em title="Auto-sync is more than just one-time import, check it and sync-up once a day.">"auto-sync"</em> from one of their existing [[hcard-supporting-profiles]], their name, their icon etc. [http://microformats.org/blog/2007/06/21/microformatsorg-turns-2/ Satisfaction Inc already supports this.]<br /> ### let a user fill out and <em title="Auto-sync is more than just one-time import, check it and sync-up once a day.">"auto-sync"</em> their list of friends from one of their existing [[hcard-xfn-supporting-friends-lists|hCard+XFN supporting friends lists]]. [http://microformats.org/blog/2007/06/21/microformatsorg-turns-2/ Dopplr.com already supports this.]<br /> <br /> === Discussion and suggestions ===<br /> * Jeremy Keith: [http://adactio.com/journal/1209/ Twittering]: <blockquote><p>Here’s what I want: when I go to the latest social networking fadsite, I want it to ask for my URL. Then it can go off and fetch my [[hcard|hCard]] and [[xfn|XFN]] list. A pre-filled form for my details and a pre-filled list of potential contacts can then be presented to me.</p></blockquote><br /> * Derek Featherstone: [http://www.boxofchocolates.ca/archives/2006/11/21/solving-problems-with-social-networking Solving problems with social networking]<br /> * Jeremy Keith: [http://adactio.com/journal/1212/ More thoughts on portable social networks]<br /> * Glenn Jones: [http://www.glennjones.net/Post/820/Microformatsandportablesocialnetwork.htm Microformats and portable social network]<br /> * Velvetsarah has [http://www.velvet.id.au/2006/11/23/portable-social-networks/ posted a screenshot and brainstorm] about how a site could handle importing XFN enabled contacts.<br /> [http://www.velvet.id.au/2006/11/23/portable-social-networks/ http://www.velvet.id.au/out/wp-content/uploads/2006/11/picture-9.png]<br /> * Jeremiah Owyang: [http://twitter.com/jowyang/statuses/156097392 Twittering]: <blockquote><p>What if we could port all our friends and family from one social network to another. Why do we have to continue to add people = annoying</p></blockquote><br /> * Brian Oberkirch: [http://urltea.com/10ee Highrise, microformats and portable social networks]<br /> * Kevin Lawver: [http://www.lawver.net/archive/2007/07/17/h12_portable_social_networks_at_mashup_camp.php A Portable Social Network Prototype] - A simple Ruby on Rails app that uses OpenID + XFN to look for users of the site w/ the same homepage as the href value and allows you to add them as contacts.<br /> <br /> === Social Network Portability FAQ ===<br /> *''Doesn't [http://openid.net/ OpenID] address the re-enter all your personal profile info problem?''<br /> ** No it does not. OpenID is fundamentally about proving to one site that you own or control another particular URL. Nothing more. All the profile stuff is extra and even then the specific property set is unspecified in OpenID. That's where [[hcard|hCard]] comes in. hCard specifies a vocabulary of personal profile info (name, email, birthday, URL etc.) based on industry standard vCard. And in fact that's all you need to solve the "re-enter all your personal info" problem for public sites - no need to authenticate public URLs via OpenID, just read them and parse their hCard(s).<br /> <br /> === Issues ===<br /> * For import/subscribe to hCard user profiles, "we need a defined heuristic for picking out the page owner from the friends." - Kevin Marks in IRC.<br /> ** There are some thoughts and proposed heuristics for this in [[hcard-brainstorming#Representative_hCard_discovery|hCard brainstorming: representative hCard discovery]].[[User:Tantek|Tantek]] 14:35, 31 Jul 2007 (PDT)<br /> <br /> == See also ==<br /> <br /> * [[user-interface]]<br /> * [[hcard|hCard]]<br /> * [[xfn]]<br /> <br /> == Notes ==<br /> [[events/2007-07-28-portable-social-networks-meetup|2007-07-28 Meeting]] between Daniel Burka, [[User:Tantek|Tantek Çelik]], Eran Globen, Brian Oberkirch at Ritual Coffee Roasters, San Francsico, CA.<br /> * discussed portable social networks, problem statement, goals, design patterns, recipes</div>

KevinLawver https://microformats.org/wiki/index.php?title=implementations&diff=15578 implementations 2007-04-12T15:17:19Z

<p>KevinLawver: /* Applications / Plugins / Services / Tools */</p> <hr /> <div><h1>Microformats Implementations and Implementers</h1><br /> <br /> <br /> This page lists the applications, plugins, sample code, services, tools that produce or consume microformats as well as companies, developers, and organizations who implement the aforementioned. This is only a partial list. If you know other companies implementing tools for microformats, please add them and list their services/tools and what specific microformats they support.<br /> __TOC__<br /> <br /> == Implementations vs. Examples in the Wild ==<br /> <br /> This page is ''only'' for implementations of tools that publish or consume microformats. Companies simply ''using'' microformats on their pages/sites belong in the "Examples in the wild" sections of those respective microformats, e.g.:<br /> * [[hcard-examples-in-wild|hCard Examples in the wild]]<br /> * [[hcalendar-examples-in-wild|hCalendar Examples in the wild]]<br /> * etc.<br /> <br /> == Editing This Page ==<br /> <br /> This page is primarily composed of two big lists:<br /> * [[implementations#Applications_.2F_Plugins_.2F_Services_.2F_Tools|Applications / Plugins / Services / Tools]]<br /> * [[implementations#Companies_.2F_Developers_.2F_Organizations|Companies / Developers / Organizations]]<br /> <br /> When you find an implementation, first make sure that it is ''actually'' an implementation as opposed to ''just'' an [[hcard-examples-in-wild|example in the wild]] of publishing microformats (see above).<br /> <br /> Second, note the name of the ''tool or service'' separately from the name of the ''developer(s)'' who wrote the tool/service.<br /> <br /> Add a third level heading with the name of the tool/service ( <code>=== Name of Tool ===</code> ) to the Applications / Plugins / Services / Tools section, sorted alphabetically by name of tool/service. Add a top level list item (*) just below the heading with an external link to the tool/service, along with a link to evidence of their support for microformats, and mention (and locally link) each microformat that is supported.<br /> <br /> Add a nested list item <code>* by Name of Developer</code> and local hyperlink the Name of Developer to a fragment identifier in this page, e.g. Apple Computer would be linked like this: <code><nowiki>[[implementations#Apple_Computer|Apple Computer]]</nowiki></code><br /> <br /> Check to see if there is an entry for the developer in the list of Companies / Developers / Organizations, if not add a third level heading with the name of the developer ( <code>=== Name of Developer ===</code> ), alphabetically sorted by name of developer. Add a link to the developer's home page followed by "has implemented microformats in:".<br /> <br /> In the entry for the developer, add a list item <code>* Name of Tool</code> and local hyperlink the Name of Tool to a fragment identifier in this page, e.g. X2V would be linked like this: <code><nowiki>[[implementations#X2V|X2V]]</nowiki></code><br /> <br /> Save the page and make sure that each fragment ID local hyperlink when clicked scrolls you to the right spot (for the developer, and for the tool). Make any fix-up edits as necessary. That's it!<br /> <br /> == Formats ==<br /> <br /> Most microformat specifications have an "implementations" section, e.g.:<br /> *[[rel-tag#Implementations|rel-tag implementations]]<br /> *[[vote-links#Implementations|vote-link implementations]]<br /> *[[xoxo#Implementations|XOXO implementations]]<br /> <br /> In addition, some microformat specifications have separate implementation pages:<br /> *[[hcalendar-implementations|hCalendar implementations]]<br /> *[[hcard-implementations|hCard Implementations]]<br /> *[[xfn-implementations|XFN implementations]]<br /> <br /> == Applications / Plugins / Services / Tools ==<br /> <br /> This is an alphabetical listing of all applications, plugins (grouped with their app/tool), services and tools that implement microformats, along with the list of microformats that are supported, and the company and/or developers responsible for it.<br /> <br /> As a user, the implementations listed below will automatically help you use microformats and help your data portability and interoperability with other apps and services.<br /> <br /> Please help complete this list! If you know of additional apps/plugins/services/tools that support microformats, please add them!<br /> <br /> Note: this section is only for listing specific ''implementations''. The list of ''implementors'' is in the [[implementations#Companies / Developers / Organizations|Companies / Developers / Organizations]] section below.<br /> <br /> <br /> === .Mac Webmail ===<br /> <br /> * The [http://www.mac.com/webmail .Mac Webmail] ''service'' now [http://factoryjoe.com/blog/2006/10/28/apple-embraces-microformats-in-new-mac-webmail/ supports hcard].<br /> ** by [[implementations#Apple_Computer|Apple Computer]]<br /> <br /> === Blinksale ===<br /> * [http://blinksale.com Blinksale] uses [[hcard|hCard]] standard throughout for people and companies.<br /> <br /> === BlogMatrix ===<br /> * [http://www.blogmatrix.com BlogMatrix] - user information marked as [[hcard|hCard]], tag directories in [[xfolk]]/[[rel-tag]], enclosures are marked as [[rel-enclosure]].<br /> ** by [[implementations#David_Janes|David Janes]]<br /> <br /> === Blogmarks.net ===<br /> * [http://www.blogmarks.net Blogmarks.net] publish user bookmarks in [[xfolk]]/[[rel-tag]].<br /> <br /> === Community Server ===<br /> * [http://communityserver.org Community Server] supports tagging posts with [[rel-tag]], implements [[rel-nofollow]] on links in comments, and allows users to create link lists using [http://gmpg.org/xfn/ XFN].<br /> <br /> === Conferenceer ===<br /> <br /> * Built for SXSW 2007, [http://sxsw07.conferenceer.com/ Conferenceer] supports hcalendar and hcard.<br /> <br /> === Citycita===<br /> * [http://www.citycita.org Citycita] supports [[hCal|hCal]] in all event pages for local social groups.<br /> ** by [[implementations#Rubio_Jamin|Rubio Jamin]]<br /> <br /> === Cork'd ===<br /> * [http://corkd.com Cork'd] supports [[hcard|hCard]] for user profiles, [[hreview|hReview]] for wine reviews, along with [[rel-tag]] for tagging wines as announced in [http://www.simplebits.com/notebook/2006/06/10/wineformats.html Pairing Wine and Microformats]<br /> ** by [[implementations#Dan_Cederhold|Dan Cederholm]]<br /> <br /> === Dreamweaver ===<br /> ==== Microformats Extensions ====<br /> * [http://www.webstandards.org/action/dwtf/microformats Dreamweaver Microformats Extensions] ([http://allinthehead.com/beta/microformats.mxp.zip download]) support authoring [[hcard|hCard]], [[hcalendar|hCalendar]], [http://gmpg.org/xfn XFN], [[rel-tag]], [[rel-license]] as [http://allinthehead.com/retro/282/microformats-in-dreamweaver announced by Drew]<br /> ** by [[implementations#Drew_Mclellan|Drew McLellan]]<br /> <br /> === Drupal ===<br /> ==== Upcoming module for Drupal ====<br /> * [http://hybernaut.com/upcoming-module Drupal Upcoming.org syndication module] emits [[hcalendar|hCalendar]]<br /> ** by [[implementations#Brian_Del_Vecchio|Brian Del Vecchio]]<br /> <br /> === Etnies ===<br /> <br /> * [http://etnies.com/extra/calendar/ Etnies Calendar] supports hcalendar. Maybe the [http://thecolab.com/blog/2007/01/22/etniescom-relaunch/ first skate-shop to support microformats].<br /> <br /> === EVDB ===<br /> * [http://evdb.com EVDB] / [http://eventful.com Eventful] supports [[hcalendar|hCalendar]] for over 1,000,000 event listings and [[hcard|hCard]] for venues.<br /> <br /> === Ficlets ===<br /> <br /> * [http://ficlets.com Ficlets] supports [[hcard]] for author data and [[hatom]] for stories and lists of stories.<br /> ** [http://sixtwothree.org Jason Garber] and [http://lawver.net Kevin Lawver] for [http://aol.com AOL]<br /> <br /> === Finetoothcog ===<br /> * [http://finetoothcog.com/site/stolen_bikes Stolen Bikes] now supports [[hcalendar|hCalendar]] for reported stolen bikes. Also provides iCal subscription.<br /> <br /> === Firefox ===<br /> * See [[firefox-extensions]]<br /> <br /> === FunAdvice ===<br /> * [http://funadvice.com FunAdvice] supports using the rel-nofollow tag to prevent users posting content simply for the search engine benefit, to improve teh quality of the advice giving community.<br /> <br /> === Gravatar Commenters as hCards ===<br /> * [http://thedredge.org Andy Hume] added code to his blogging software to automatically mark-up the names and URLs of commenters on his blog with [[hcard|hCard]]. <br /> ** by [[implementations#Andy_Hume|Andy Hume]]<br /> ** Andy - any chance of open sourcing your code to turn Gravatars into hCards?<br /> <br /> === Flickr People ===<br /> * [http://flickr.com/ Flickr]'s profiles on its people pages supports both [[hcard|hCard]] and [http://gmpg.org/xfn XFN].<br /> ** by [[implementations#Cal_Henderson|Cal Henderson]]<br /> **[http://flickr.com/people/tantek example]<br /> <br /> === Flickr Photos ===<br /> * [http://flickr.com/map/ Flickr's geo tagged photos] are marked up with the [[geo]] microformat.<br /> <br /> === Flock Web Browser ===<br /> * The [http://flock.com Flock web browser] supports the [[rel-tag]] microformat.<br /> ** by [[implementations#Flock|Flock]]<br /> <br /> === Google Search ===<br /> * [http://google.com/ Google Search] - supports [[rel-nofollow]]<br /> === Google Creative Commons Search ===<br /> * [http://www.google.com/webhp?as_rights=(cc_publicdomain%7Ccc_attribute%7Ccc_sharealike%7Ccc_noncommercial%7Ccc_nonderived) Google Creative Commons Search] - supports [[rel-license]]<br /> <br /> === Greasemonkey ===<br /> * [http://greasemonkey.makedatamakesense.com/google_hcalendar/ Google hCalendar] - Adds hCalendar data to Google Calendar.<br /> * [http://www.nickpeters.net/?p=35 Social xFolk] - Adds xFolk links to social bookmarking sites del.icio.us and ma.gnolia.<br /> <br /> === hCalendar creator ===<br /> * [http://microformats.org/code/hcalendar/creator hCalendar creator] (originally [http://theryanking.com/microformats/hcalendar-creator.html published by Ryan King]) is a javascript form for creating [[hcalendar|hCalendar]] events.<br /> ** by [[implementations#Ryan_King|Ryan King]]<br /> <br /> === hCard creator ===<br /> * The open source [http://microformats.org/code/hcard/creator hCard creator] (originally [http://tantek.com/microformats/hcard-creator.html published by Tantek]) is a very simple, yet illustrative, open source user interface / form / script which creates an [[hcard|hCard]] in real-time as you type in a set of contact information.<br /> ** by [[implementations#Tantek_Çelik|Tantek Çelik]]<br /> <br /> === hKit Microformats Toolkit for PHP5 ===<br /> * [http://allinthehead.com/hkit hKit Microformats Toolkit for PHP5] as [http://allinthehead.com/retro/291/hkit-microformats-toolkit-for-php announced by Drew McLellan]<br /> <br /> === hReview creator ===<br /> * [http://microformats.org/code/hcalendar/creator hReview creator] (originally [http://theryanking.com/microformats/hreview-creator.html published by Ryan King]) is a javascript form for creating [[hreview|hReviews]].<br /> ** by [[implementations#Ryan_King|Ryan King]]<br /> <br /> === Ice Rocket ===<br /> * [http://icerocket.com] - [http://blogs.icerocket.com/tag/ supports] [[rel-tag]]<br /> <br /> === iChat buddy list to hCards ===<br /> * [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards.<br /> ** by [[implementations#Tantek_Çelik|Tantek Çelik]]<br /> <br /> === JSCalendar ===<br /> * [http://web.mit.edu/glasser/www/JSCalendar/ JSCalendar] parses [[hcalendar|hCalendar]] and produces a displayable HTML table/CSS-based calendar.<br /> <br /> === Konqueror ===<br /> * [http://www.konqueror.org/ Konqueror] - [http://flickr.com/photos/factoryjoe/68755089/ supports] [[hcard|hCard]]<br /> <br /> === Last.fm ===<br /> * [http://last.fm Last.fm] - [http://factoryjoe.com/blog/2006/10/31/lastfm-adds-support-for-hcalendar/ Last.fm supports] [[hcalendar|hCalendar]] <br /> <br /> === Laughing Squid Calendar ===<br /> * The [http://laughingsquid.com/squidlist/calendar/ Laughing Squid Calendar] events listings support [[hcalendar|hCalendar]].<br /> ** by [http://laughingsquid.com/ Laughing Squid]<br /> <br /> ===LinkedIn ===<br /> * [http://www.linkedin.com LinkedIn] - LinkedIn includes [[hcard|hCard]] and [[xfn|XFN]] on contacts, [[hresume|hResume]] for public profiles and [[hreview|hReview]] on service provider recommendations<br /> <br /> === LiveJournal ===<br /> * [http://www.livejournal.com LiveJournal] - LiveJournal supports tagging posts with [[rel-tag]].<br /> <br /> === LJFind ===<br /> * [http://www.ljfind.com LJ-Find] - LJFind supports tagging posts with [[rel-tag]].<br /> <br /> === Ma.gnolia ===<br /> <br /> * [http://ma.gnolia.com Ma.gnolia] has wide [http://wiki.ma.gnolia.com/Ma.gnolia_Feeds_Guide#Microformats support for a variety of microformats] including [[rel-tag]], [[xfolk]], [[hreview]], [[xfn]] and [[hcard]].<br /> <br /> === Microformat Base ===<br /> * [http://randomchaos.com/microformats/base/ Microformat Base]<br /> ** by [[implementations#Scott Reynen|Scott Reynen]]<br /> <br /> === Microformat Bookmarklet Overlay ===<br /> * [http://leftlogic.com/info/articles/microformats_bookmarklet Microformats Bookmarklet] for Safari, Firefox and Camino, supports [[hcard|hCard]] and [[hcalendar|hCalendar]] and allows the user to import individual microformats on the fly.<br /> ** by [[implementations#Remy_Sharp|Remy Sharp]]<br /> <br /> === Microformat Parser for Ruby ===<br /> * [http://blog.labnotes.org/2005/11/20/microformat-parser-for-ruby/ Microformat Parser for Ruby]<br /> ** by [[implementations#Assaf Arkin|Assaf Arkin]]<br /> <br /> === Nature Network Boston ===<br /> * [http://network.nature.com/boston/ Nature Network Boston], a social networking community for scientists, supports [[reltag|rel-tag]], [[hcard|hCard]] for user profiles and [[hcalendar|hCalendar]] for marking up events across the site.<br /> ** by [[implementations#Nature Publishing Group|Nature Publishing Group]]<br /> <br /> === Nature Protocols ===<br /> * [http://www.nature.com/nprot/ Nature Protocols], a forum for scientists to upload and comment on protocols, supports [[hcard|hCard]] and [[XOXO]].<br /> ** by [[implementations#Nature Publishing Group|Nature Publishing Group]]<br /> <br /> === Nutch ===<br /> * [http://www.mail-archive.com/nutch-dev@lucene.apache.org/msg01295.html rel-nofollow support added]<br /> * [http://www.mail-archive.com/nutch-commits@lucene.apache.org/msg01014.html rel-tag support checked in]<br /> <br /> === ODEO ===<br /> * [http://odeo.com/ ODEO] [http://odeo.com/blog/2005/07/adding-microformats-to-odeo.html noted] that they support microformats: [[rel-tag]], [[rel-enclosure]], [http://gmpg.org/xfn XFN].<br /> <br /> === phpMicroformats ===<br /> * [http://enarion.net/phpmicroformats/ phpMicroformats] is a PHP class library that generates microformat entries for [[hcalendar|hCalendar]] and [[hcard|hCard]]. It is released under GPL.<br /> <br /> === PostNuke ===<br /> ''[http://www.postnuke.com PostNuke] is an Application Framework/Content Management Systeme''<br /> * [http://www.pagesetter.net/index.php?module=pagesetter&func=viewpub&tid=4&pid=96 hCards4Pagesetter] - hCards Publication Type for the PostNuke module "Pagesetter"<br /> * [http://www.pagesetter.net/index.php?module=pagesetter&func=viewpub&tid=4&pid=97 hCalendar4Pagesetter] - hCalendar Publication Type for the PostNuke module "Pagesetter"<br /> * [http://www.pagesetter.net/index.php?module=pagesetter&func=viewpub&tid=4&pid=98 hReview4Pagesetter] - hReview Publication Type for the PostNuke module "Pagesetter"<br /> * [http://noc.postnuke.com/frs/?group_id=256&release_id=477 Blogroll] - XFN Block/Modul<br /> * [http://noc.postnuke.com/frs/?group_id=256&release_id=628 nofollow] - nofollow Hook<br /> <br /> === Profiler ===<br /> * [http://microformat.makedatamakesense.com/profiler/ Profiler] works as a proxy service adding microformat profiles to documents that appear to contain microformats.<br /> <br /> === RFC2629.xslt ===<br /> * [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate [[hcard|hCard]] information ([http://ietf.org/rfc/rfc2629 RFC2629] in an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])<br /> <br /> === Salesforce ===<br /> * [http://salesforce.com Salesforce] [http://flickr.com/photos/kingsleyj/175689109/ supports] [[hcard|hCard]]<br /> ** by [http://flickr.com/people/kingsleyj/ Kingsley Joseph]<br /> ==== Spanning Salesforce ====<br /> * [http://spanningsalesforce.com/ Spanning Salesforce] supports [[hcalendar|hCalendar]].<br /> <br /> === Sivitools ===<br /> <blockquote><br /> Sivitols is a Java library for microformats. Currently only the xFolk RC1 standard is implemented, but additional microformat support is planned. This library is being written and maintained for a tag sharing project undertaken by Video Vertigo.<br /> </blockquote><br /> [http://blog.blip.tv/blog/microformats/ Annoucement], [http://pokkari.com/microformat/javadoc/ Docs]<br /> <br /> === SPRACI ===<br /> * [http://www.spraci.com SPRACI] - nightlife/events - [[hcalendar|hCalendar]] published in events listings, aggregator can read hCalendar<br /> <br /> === Sunnyvale House Concerts ===<br /> * [http://concerts.shrub.ca/shows Sunnyvale House Concerts] supports [[hcard|hCard]] and [[hcalendar|hCalendar]].<br /> <br /> === Technorati Contacts Feed Service ===<br /> * [http://feeds.technorati.com/contacts/ Technorati Contacts Feed Service] is a deployment of [[implementations#X2V|X2V]] to convert [[hcard|hCards]] to vCard (.vcf) format.<br /> <br /> === Technorati Events Feed Service ===<br /> * [http://feeds.technorati.com/events/ Technorati Events Feed Service] is a deployment of [[implementations#X2V|X2V]] to convert [[hcalendar|hCalendar]] events to iCalendar (.ics) format.<br /> <br /> === Technorati Microformats Search ===<br /> * Technorati [http://kitchen.technorati.com/search/ Microformats Search]. Search for contacts ([[hcard|hCard]]), events ([[hcalendar|hCalendar]]), or reviews ([[hreview|hReview]]) published on blogs and other web sites.<br /> ** by [#implementations#Tantek_Çelik|Tantek Çelik]], [[implementations#Ryan_King|Ryan King]], [[implementations|Kevin_Marks|Kevin Marks]], [[implementations#Josh_Smith|Josh Smith]]<br /> <br /> === Technorati Search ===<br /> * [http://technorati.com/ Technorati] [http://technorati.com/search Search] supports and handles both [[vote-links]] and [[rel-nofollow]] for indicating whether a link should have any/positive/negative weighting towards the destination.<br /> ** by [http://technorati.com/about/staff.html Technorati Staff]<br /> === Technorati Tags ===<br /> * [http://technorati.com/tags/ Technorati Tags] pages aggregate blog posts tagged with the [[rel-tag]] open tagging standard, in addition to recent tagged photos and links.<br /> <br /> === Textpattern ===<br /> ==== Microformats Plugin ====<br /> * [http://placenamehere.com/TXP/pnh_mf/ Textpattern Microformats Plugin] supports authoring [[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [http://gmpg.org/xfn XFN], [[rel-tag]], [[rel-license]] in the [http://www.textpattern.com/ Textpattern] CMS/blogging tool <br /> ** by [http://placenamehere.com/ Chris Casciano]<br /> <br /> === TYPO3 ===<br /> * [http://www.typo3.com TYPO3], [http://typo3.org TYPO3 Developer Ressource]<br /> ==== tt_address extension====<br /> * [http://typo3.org/extensions/repository/view/tt_address/2.0.1/ tt_address] - hCard support with the tt_address extension version 2.0.0<br /> ** by [[implementations#Ingo_Renner|Ingo Renner]]<br /> ==== TIMTAB extension====<br /> * [http://typo3.org/extensions/repository/view/timtab/0.5.11/ TIMTAB] - XFN support for blogrolls with the TIMTAB weblog extension for TYPO3<br /> ** by [[implementations#Ingo_Renner|Ingo Renner]]<br /> <br /> === Upcoming.org ===<br /> * [http://upcoming.org Upcoming.org] - hCalendar support in events listings and individual events.<br /> ** by [[implementations#Andy_Baio|Andy Baio]], [[implementations#Leonard_Lin|Leonard Lin]], [[implementations#Gordon_Luk|Gordon Luk]]<br /> <br /> === vCardExplorer ===<br /> * [http://vcardexplorer.corefault.de/ vCardExplorer for MacOSX] - browses local vcards and converts hcards from URLs.<br /> <br /> === WordPress ===<br /> * [http://wordpress.org WordPress] supports [http://gmpg.org/xfn/ XFN] blogrolls through a very nice built-in user interface. (cf. [[xfn-implementations]])<br /> ** by [[implementations#Matt_Mullenweg|Matt Mullenweg]] and friends<br /> <br /> ==== WP Microformatted Blogroll ====<br /> * The [http://factorycity.net/projects/wp-microformatted-blogroll/ WP Microformatted Blogroll 0.2] Wordpress plugin by [[implementations#Chris_Messina|Chris Messina]] supports [[hcard|hCard]] and [http://gmpg.org/xfn/ XFN].<br /> <br /> ==== VoteBack Plugin ====<br /> * [http://redmonk.net/archives/2006/12/21/voteback/ VoteBack plugin for Wordpress] - checks incoming pingbacks and trackbacks for [[votelinks]].<br /> <br /> ==== WP Themes ====<br /> * [http://www.plaintxt.org/themes/sandbox/ Sandbox] is a theme for Wordpress that uses [[hatom|hAtom]]. <br /> ** The theme is also available to accounts on the <username>.wordpress.com hosting service.<br /> * [http://www.jesuscarrera.info/proyectos/startpoint/ StartPoint] A theme for theme developers. A good start point to make your own templates. It supports multiple languages, widgets, contains semantic hAtom microformats, and more.<br /> * [http://www.whump.com/dropbox/Strangelove.zip Strangelove] is a modification of the default Wordpress theme (Kubrick) with [[hatom|hAtom]] support. <br /> ** It points to the hAtom2Atom proxy service as the link for syndication feeds.<br /> <br /> === X2V ===<br /> * Brian Suda has created several XSLT files to extract microformats from HTML. From that the [http://suda.co.uk/projects/X2V/ X2V] webservice/favelet emerged. The XSLT and favelet extracts [[hcard|hCard]] and to produces .vcf (vCard) files and [[hcalendar|hCalendar]] to produce .ics (iCal) files. Also in the labs is a universal XMDP validator and a site-wide search spider that recognizes 'no-follow', 'license' and other microformats so they can be used in a more semantic way when displaying search results.<br /> ** by [[implementations#Brian_Suda|Brian Suda]]<br /> <br /> === Yahoo Creative Commons Search ===<br /> * [http://search.yahoo.com/cc/ Yahoo Creative Commons Search] - supports [[rel-license]] specifically to search for Creative Commons licensed content.<br /> <br /> === Yahoo Local ===<br /> * [http://local.yahoo.com Yahoo local] supports [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]].<br /> <br /> === Yahoo Tech ===<br /> * [http://tech.yahoo.com Yahoo! Tech] supports [[hreview|hReview]].<br /> <br /> === Yahoo UK Movies ===<br /> * [http://movies.yahoo.co.uk Yahoo! UK Movies] supports [[hreview|hReview]].<br /> ** by Mark Norman Francis<br /> <br /> === Yedda ===<br /> * [http://yedda.com Yedda] supports [[hcard|hCard]] for exposing users information, [[hatom|hAtom]] for exposing data that is already exposed via feeds (like list of questions and answers) and [[rel-tag|rel-tag]] for every tag used to tag questions and users.<br /> <br /> == Validators ==<br /> This is an alphabetical listing of tools that have been created to validate implementations, and which formats they support.<br /> <br /> Please add to this section if you have a validator/checker, no matter which or how many microformats you test for.<br /> <br /> === rel-lint ===<br /> * [http://tools.microformatic.com/help/xhtml/rel-lint/ rel-lint] supports validation of [[rel-tag|rel-tag]] and [[xfn|XFN]] <br /> * by [[implementations#Drew_McLellan|Drew McLellan]]<br /> <br /> == Companies / Developers / Organizations ==<br /> <br /> (Considering moving all of these to an [[implementors]] page of its own).<br /> <br /> Thanks to all of the hardworking developers and innovative companies and organizations for supporting microformats.<br /> <br /> This is an alphabetical listing of all companies, developers (by last name) and organizations who have built and shipped at least one implementation (see above for details of each implementation) that users can use.<br /> <br /> Please help complete this list! If you have coded support for microformats and don't see your name, add it! If your company supports microformats in its applications, add it!<br /> <br /> Note: please add direct links to specific applications, plugins, services, or tools to the list of [[implementations#Applications / Plugins / Services / Tools|Applications / Plugins / Services / Tools]] and then link to those from their implementor with a fragment identifier link, e.g. to link to the "Cork'd" wine review community:<br /> * <nowiki>[[implementations#Cork'd|Cork'd]]</nowiki><br /> Similarly, for additional sites, put direct links to them in the [[implementations#Additional Sites|Additional Sites]] section and then link to them from their implementor with a fragment identifier link.<br /> <br /> === Apple Computer ===<br /> [http://apple.com/ Apple Computer] has implemented microformats in:<br /> * [[implementations#.Mac_Webmail|.Mac Webmail]]<br /> <br /> === Andy Hume ===<br /> * [[implementations#Andy_Hume_Blog|Andy Hume Blog]]<br /> <br /> === Andy Baio ===<br /> * [[implementations#upcoming.org|Upcoming.org]]<br /> <br /> === Assaf Arkin ===<br /> * [[implementations#Microformat_Parser_for_Ruby|Microformat Parser for Ruby]] <br /> <br /> === Brian Del Vecchio ===<br /> * [[implementations#upcoming_module_for_drupal| Upcoming module for Drupal]]<br /> <br /> === Brian Suda ===<br /> * [[implementations#X2V|X2V]]<br /> <br /> === Chris Casciano ===<br /> * [[implementations#Microformats_Plugin|Textpattern Microformats Plugin]]<br /> <br /> === Chris Messina ===<br /> [[implementations#WP_Microformatted_Blogroll|WP Microformatted Blogroll]]<br /> <br /> === Chris Saccheri ===<br /> * [[implementations#LinkedIn|LinkedIn]]<br /> <br /> === Calvin Yu ===<br /> * [http://blog.codeeg.com/ Calvin Yu blog: Don't Forget to Plant It!] has the [http://blog.codeeg.com/tails-firefox-extension-03/ Tails Firefox Extension]<br /> * [http://microformats.org/wiki/implementations#Firefox Tails Firefox Extension]<br /> <br /> === Dan Cederholm ===<br /> * [[implementations#Cork'd|Cork'd]]<br /> <br /> === David Janes ===<br /> * [[implementations#BlogMatrix|BlogMatrix]]<br /> <br /> === David Long and James Myers ===<br /> * [[implementations##ZDNet_UK|ZDNet]]<br /> <br /> === Drew McLellan ===<br /> * [[implementations#Microformats_Extensions|Microformats Extensions]]<br /> * [[implementations#hKit_Microformats_Toolkit_for_PHP5|hKit Microformats Toolkit for PHP5]]<br /> * [[implementations#rel-lint|rel-lint Validator Tool]]<br /> <br /> === enarion.net ===<br /> * [[implementations#phpMicroformats|phpMicroformats]]<br /> <br /> === Flock ===<br /> * [[implementations#Flock Web Browser|Flock Web Browser]]<br /> <br /> === FunAdvice ===<br /> * [[implementations#FunAdvice|FunAdvice]]<br /> <br /> === Google ===<br /> * [[implementations#Google_Search|Google Search]]<br /> * [[implementations#Google_Creative_Commons_Search|Google Creative Commons Search]]<br /> <br /> === Gordon Luk ===<br /> [[implementations#upcoming.org|Upcoming.org]]<br /> <br /> === Ingo Renner ===<br /> [http://www.ingo-renner.com Ingo Renner] has implemented hCard and XFN in:<br /> * [[implementations#TYPO3|TYPO3]]<br /> <br /> === Josh Smith ===<br /> * [[implementations#Technorati_Microformats_Search|Technorati Microformats Search]]<br /> <br /> === Kent Brewster ===<br /> * [http://www.mindsack.com/?page_id=39 Extensible friends] -- JSON + XFN and bookmarklet<br /> <br /> === Kevin Marks ===<br /> * [[implementations#Technorati_Microformats_Search|Technorati Microformats Search]]<br /> <br /> === Kingsley Joseph ===<br /> [http://flickr.com/people/kingsleyj/ Kingsley Joseph]:<br /> * [[implementations#Salesforce|Salesforce]]<br /> <br /> === Laughing Squid ===<br /> * [[implementations#Laughing_Squid_Calendar|Laughing Squid Calendar]]<br /> <br /> === Leonard Lin ===<br /> * [[implementations#upcoming.org|Upcoming.org]]<br /> <br /> === Mark West ===<br /> * [[implementations#PostNuke|PostNuke Blogroll]]<br /> * [[implementations#PostNuke|PostNuke nofollow]]<br /> <br /> === Nature Publishing Group ===<br /> * Nature Publishing Group are steadily rolling out microformats across their sites and titles. Current implementations include the following online services:<br /> ** [[implementations#Nature Network Boston|Nature Network Boston]]<br /> ** [[implementations#Nature Protocols|Nature Protocols]]<br /> * as well the following additional site(s):<br /> ** [[implementations#Nature Home Page|Nature Home Page]]<br /> <br /> === Remy Sharp ===<br /> <br /> * [[implementations#Microformats_Bookmarklet|Microformats Bookmarklet]]<br /> <br /> === Robert de Bruin ===<br /> * [http://bordewolf.blogspot.com/ Robert de Bruin' s blog: Bor de Wolf]<br /> * [[implementations#Tails_Export_Firefox_Extension|Tails Export Firefox Extension]]<br /> <br /> === Ryan King ===<br /> * [[implementations#hCalendar_creator|hCalendar Creator]]<br /> * [[implementations#hReview_creator|hReview Creator]]<br /> * [[implementations#Technorati_Microformats_Search|Technorati Microformats Search]]<br /> <br /> === Scott Allan Wallick ===<br /> * [[implementations#WP_Themes|Sandbox Wordpress Theme w/hAtom Support]]<br /> <br /> === Scott Reynen ===<br /> * [[implementations#Microformat_Base|Microformat Base]]<br /> <br /> === SixApart ===<br /> * [[implementations#LiveJournal|LiveJournal]]<br /> <br /> === Steffen Voß ===<br /> <br /> * [[implementations#PostNuke|PostNuke hCards]]<br /> * [[implementations#PostNuke|PostNuke hCalendar]]<br /> * [[implementations#PostNuke|PostNuke hReview]]<br /> <br /> === Steve Ivy ===<br /> * [[implementations#VoteBack_Plugin|Wordpress VoteBack Plugin]]<br /> <br /> === Tantek Çelik ===<br /> * [[implementations#hCard_creator|hCard Creator]]<br /> * [[implementations#iChat_buddy_list_to_hCards|iChat Buddy List to hCard]]<br /> * [[implementations#Technorati_Microformats_Search|Technorati Microformats Search]]<br /> <br /> === Technorati ===<br /> * [[implementations#Technorati_Contacts_Feed_Service|Technorati Contacts Feed Service]]<br /> * [[implementations#Technorati_Events_Feed_Service|Technorati Events Feed Service]]<br /> * [[implementations#Technorati_Microformats_Search|Technorati Microformats Search]]<br /> * [[implementations#Technorati_Search|Technorati Search]]<br /> * [[implementations#Technorati_Tags|Technorati Tags]]<br /> <br /> === Yahoo ===<br /> * [[implementations#Flickr_People|Flickr People]]<br /> * [[implementations#Upcoming.org|Upcoming]]<br /> * [[implementations#Yahoo_Creative_Commons_Search|Yahoo Creative Commons Search]]<br /> * [[implementations#Yahoo_Local|Yahoo Local]]<br /> * [[implementations#Yahoo_Tech|Yahoo Tech]]<br /> * [[implementations#Yahoo_UK_Movies|Yahoo UK Movies]]<br /> <br /> === Yedda ===<br /> * [[implementations#Yedda|Yedda]]<br /> <br /> == Needs Fixing ==<br /> <br /> * Re-format author names and links to display Surname Firstname - for better indexing, and complete cross-linking [[User:Phae|Frances Berriman]]<br /> <br /> The following have been moved from the sections above due to problems, stated below:<br /> <br /> === Web Essentials ===<br /> * [http://we05.com/ Web Essentials] - supports [[hcard|hCard]] and [[hcalendar|hCalendar]], e.g. in their [http://we05.com/presenters.cfm list of presenters] and [http://we05.com/program.cfm program schedule].<br /> ** John McKerrell tried to look at the site on 24th October 2006 but could not access the site, server didn't seem to be up.<br /> <br /> == Other ==<br /> Some notes on initial thoughts around [[implementation-guidelines|Guidelines and Strategies for Implementing Microformats]]</div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-brainstorming&diff=19574 widget-brainstorming 2006-07-17T13:12:01Z

<p>KevinLawver: /* Specification Proposal */</p> <hr /> <div>__TOC__<br /> <br /> = Widget Brainstorming =<br /> <br /> == Contributors ==<br /> <br /> * [http://lawver.net Kevin Lawver], [http://aol.com America Online]<br /> * Shawn Carnell, [http://aol.com America Online]<br /> <br /> == Problem ==<br /> <br /> There are currently a million ways to embed distinct snippets of content and functionality on web pages. The most common two are probably iframes and some form of javascript syndication (you put this script on the page, we'll document.write some stuff on your page). In the XML world, there's RSS, Atom, and the WSRP Portlet spec for exchanging small pieces of data (although it could be said that neither RSS or Atom are meant for this sort of thing). WSRP is the only spec that's specifically meant for exchanging widgets (or modules or portlets), and it's extremely complex.<br /> <br /> I ([[User:KevinLawver]]) think this is a perfect opportunity to create a microformat for creating, delivering and discovery of small (micro, even) content on the web.<br /> <br /> See the examples on [[widget-examples]] for current implementations.<br /> <br /> == Meta Data == <br /> <br /> There are several things that need to be known about a widget, including:<br /> <br /> * License<br /> * Any configuration options that need to be set.<br /> * Dimensions<br /> * Associated files<br /> <br /> == Use Cases ==<br /> <br /> === Remotely Hosted Tools ===<br /> <br /> * User had pictures hosted on photo-sharing site.<br /> * Their blogging tool would to surface a tool provided by the photo-sharing site in that tool.<br /> * Blogging tool sends request to photo-sharing site, and photo-sharing site returns the tool in an XHTML document marked up so the blogging tool knows what pieces apply to editing data with the tool, and what pieces are used in display, and associated linked resources (CSS, Javascript, etc).<br /> <br /> == Specification Proposal ==<br /> <br /> A proposal is currently hosted at http://developer.iamalpha.com/profile. We are eager to receive feedback on [http://microformats.org/mailman/listinfo/microformats-discuss microformat-discuss] or [http://listserv.aol.com/archives/modulet-discuss.html modulet-discuss@listserv.aol.com]. It's a work in progress; please lend your voice.<br /> <br /> This proposal has now been prototyped for people to play with. See here:<br /> * [http://www.lawver.net/archive/2006/05/10/h13_aim_pages.php AIM Pages announcement] (and [http://journals.aol.com/drdzoe/ModuleMania/entries/1285 another blogpost]).<br /> * [http://www.aimpages.com/ AIM Pages site]<br /> * [http://developer.iamalpha.com/profile AOL ModuleT: A Module Transport Microformat Profile]<br /> * [http://developer.iamalpha.com/ documentation]<br /> <br /> == Related Microformats ==<br /> <br /> * [[xoxo]] - to hold configuration or meta data about the widget.<br /> * [[rel-license]] - link to license for widget.</div>

KevinLawver https://microformats.org/wiki/index.php?title=events/2006-03-14-sxsw-modulet&diff=5448 events/2006-03-14-sxsw-modulet 2006-03-06T18:05:14Z

<p>KevinLawver: </p> <hr /> <div><h1> How to Convince Your Company to Embrace Web Standards - SxSW Interactive 2006 </h1><br /> <br /> One of several microformats [[events]].<br /> <br /> We'll be presenting the [http://iamalpha.com/.developer/profile ModuleT] microformat as part of our panel at [http://2006.sxsw.com/ SXSWi 2006]. It's not clear how much time we'll have to talk about it, but we'll definitely show off the demo and the format.<br /> <br /> __TOC__<br /> <br /> == Session Details ==<br /> <br /> * What: [http://2006.sxsw.com/interactive/programming/panels/?action=show&id=IAP060065 How to Convince Your Company to Embrace Standards] (will point to presentation material when it's online)<br /> * Who (confirmed presenters): [http://kimberlyblessing.com Kimberly Blessing], [http://slayeroffice.com Steve Chipman], Alla Gringaus, [http://lawver.net Kevin Lawver] and Arun Ranganathan<br /> * When: Tuesday, March 14, 10:00AM - 11:00AM<br /> * Where: Room 18ABC, Austin Convention Center, Austin, TX<br /> <br /> == Attending ==<br /> <br /> Please add your name here if you are attending SXSW Interactive (whether you are speaking or not), and plan on attending the panel. See [2006-03-13-sxsw-microformats Tantek's panel page] for a list of folks attending the conference.<br /> <br /> * <br /> <br /> == Short Summary ==<br /> <br /> Web developers the world over understand the benefits that standards-based development provide, but how do you get management or a client to understand as well? A small band of committed geeks got AOL and Time Inc. to embrace Web standards, not only in the Development organization, but throughout the company -- including Design and Senior Management. Come learn how they did it, and how you can do it too.<br /> <br /> We'll also be showing some new stuff that shows the progress we've made at AOL since the geeks started taking over, including the use of Microformats and our efforts to develop our own.</div>

KevinLawver https://microformats.org/wiki/index.php?title=events/2006-03-14-sxsw-modulet&diff=5310 events/2006-03-14-sxsw-modulet 2006-03-06T17:56:24Z

<p>KevinLawver: </p> <hr /> <div><h1> How to Convince Your Company to Embrace Web Standards - SxSW Interactive 2006 </h1><br /> <br /> One of several microformats [[events]].<br /> <br /> We'll be presenting the [[http://iamalpha.com/.developer/profile|ModuleT]] microformat as part of our panel at [http://2006.sxsw.com/ SXSWi 2006]. It's not clear how much time we'll have to talk about it, but we'll definitely show off the demo and the format.<br /> <br /> __TOC__<br /> <br /> == Session Details ==<br /> <br /> * What: [[http://2006.sxsw.com/interactive/programming/panels/?action=show&id=IAP060065|How to Convince Your Company to Embrace Standards]] (will point to presentation material when it's online)<br /> * Who (confirmed presenters): [[Kimberly Blessing|http://kimberlyblessing.com]], [[http://slayeroffice.com|Steve Chipman]], Alla Gringaus, [[http://lawver.net|Kevin Lawver]] and Arun Ranganathan<br /> * When: Tuesday, March 14, 10:00AM - 11:00AM<br /> * Where: Room 18ABC, Austin Convention Center, Austin, TX<br /> <br /> == Attending ==<br /> <br /> Please add your name here if you are attending SXSW Interactive (whether you are speaking or not), alphabetically sorted by last name.<br /> * <br /> <br /> == Short Summary ==<br /> <br /> Web developers the world over understand the benefits that standards-based development provide, but how do you get management or a client to understand as well? A small band of committed geeks got AOL and Time Inc. to embrace Web standards, not only in the Development organization, but throughout the company -- including Design and Senior Management. Come learn how they did it, and how you can do it too.<br /> <br /> We'll also be showing some the new stuff that shows the progress we've made at AOL since the geeks started taking over, including the use of Microformats and our efforts to develop our own.</div>

KevinLawver https://microformats.org/wiki/index.php?title=events&diff=5446 events 2006-03-06T17:47:53Z

<p>KevinLawver: /* Microformats related Events */</p> <hr /> <div>= Microformats related Events =<br /> <br /> Please add any microformats related events (specifically, events where there will be talks on microformats) you find here, and we'll add them to the hCalendar on the home page. Thanks! -[http://tantek.com/ Tantek]<br /> <br /> * 2006-03-01: [[events/2006-03-01-w3c-plenary-microformats|Microformats panel at W3C Plenary Day]]<br /> * 2006-03-02: [http://esw.w3.org/topic/SwigAtTp2006 Semantic Web Interest Group meeting at W3C Technical Plenary], specifically, 1.30-3.30pm Dan Connolly on using "GRDDL" to parse microformats<br /> * 2006-03-07: [[events/2006-03-07-etech-microformats|Microformats at O'Reilly ETech]]<br /> * 2006-03-13: [[events/2006-03-13-sxsw-microformats|Microformats at SXSW Interactive]]<br /> * 2006-03-14: [[events/2006-03-14-sxsw-modulet|Convincing Your Company to Embrace Web Standards at SxSW Interactive]]<br /> * 2006-05-16 - 2006-05-19 [http://xtech.org/ XTech 2006 Conference] : [http://times.usefulinc.com/2006/02/15-xtech Microformats tutorial announced]<br /> * 2006-05-23: [http://www.blogpulse.com/www2006-workshop/ WWE 2006 | 3rd Annual Workshop on the Weblogging Ecosystem] - call for papers is now open, and explicitly includes "microformats".<br /> * 2006-05-30 - 2006-05-31 [http://netsquared.org/conference/ NetSquared]: Ryan King has been asked to present on microformats.<br /> * ...<br /> <br /> <br /> == Quicktime Broadcaster Notes ==<br /> <br /> For setting up a mac laptop with an iSight and QT Broadcaster in order to publish live audio/video from events.<br /> <br /> # Make sure you have the necessary equipment and software installed<br /> #* A Macintosh running OSX 10.3.9 or later<br /> #* Quicktime 7 - get it from http://www.apple.com/quicktime/<br /> #* Quicktime Broadcaster - get it from http://www.apple.com/quicktime/broadcaster/<br /> #* An iSight or digital video camera with firewire connection<br /> # Get a broadcast template document from someone (see KevinMarks for example)<br /> # Open that, then change the info in the 'Network' pane that has his name etc in it.<br /> # Check the video and audio panes are using your iSight<br /> # Another tip is that the standalone thingy for the iSight can be more useful than the screen-top one if you have a desk, as that way it picks up less typing noise and wobbles<br /> # I find plugging in headphones is a good idea, as you can then monitor and not get howlround<br /> <br /> http://microformats.org/media/broadcast.mov</div>

KevinLawver https://microformats.org/wiki/index.php?title=s5-tools&diff=4319 s5-tools 2006-01-19T23:11:09Z

<p>KevinLawver: </p> <hr /> <div>* [http://www.lawver.net/archive/2005/03/18/h15_s5_instiki_happy_geek.php S5 + Instiki] - A little out of date. Will replace with the instructions for .10 in the near future.</div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-examples&diff=2666 widget-examples 2005-11-02T06:49:34Z

<p>KevinLawver: Added Microsoft Gadgets</p> <hr /> <div>= widget examples =<br /> <br /> == Contributor(s) ==<br /> <br /> * [http://lawver.net Kevin Lawver]<br /> * [http://changelog.ca Charles Iliya Krempeaux]<br /> * ...<br /> <br /> == Apple's Dashboard ==<br /> <br /> * Uses an XML Manifest file to specify data about the "widget" (width, height, thumbnail image, title and version).<br /> * No requirements for markup around widgets.<br /> <br /> === Dashboard Example (plist) ===<br /> <br /> <pre>&lt;?xml version=&#34;1.0&#34; encoding=&#34;UTF-8&#34;?&gt;<br /> &lt;!DOCTYPE plist PUBLIC &#34;-//Apple Computer//DTD PLIST 1.0//EN&#34; &#34;http://www.apple.com/DTDs/PropertyList-1.0.dtd&#34;&gt;<br /> &lt;plist version=&#34;1.0&#34;&gt;<br /> &lt;dict&gt;<br /> &lt;key&gt;AllowNetworkAccess&lt;/key&gt;<br /> &lt;true/&gt;<br /> &lt;key&gt;CFBundleDisplayName&lt;/key&gt;<br /> &lt;string&gt;AIM Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleIdentifier&lt;/key&gt;<br /> &lt;string&gt;com.aimfight.widget&lt;/string&gt;<br /> &lt;key&gt;CFBundleName&lt;/key&gt;<br /> &lt;string&gt;AOL Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleShortVersionString&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CFBundleVersion&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CloseBoxInsetX&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;CloseBoxInsetY&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;MainHTML&lt;/key&gt;<br /> &lt;string&gt;fight.html&lt;/string&gt;<br /> &lt;/dict&gt;<br /> &lt;/plist&gt;</pre><br /> <br /> == AOL's Channel Content Modules - [http://sports.aol.com AOL Sports example] ==<br /> <br /> * Each module (widget) has a markup envelope and some required elements that make it a module and allow for consistent styles across products.<br /> <br /> === Example ===<br /> <br /> <pre>&lt;div class=&#34;module themedList&#34;&gt;<br /> &lt;div class=&#34;header&#34;&gt;&lt;h3&gt;Kevin&#39;s List Of Fruit&lt;/h3&gt;&lt;/div&gt;<br /> &lt;div class=&#34;body&#34;&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Apples&lt;/li&gt;<br /> &lt;li&gt;Oranges&lt;/li&gt;<br /> &lt;/ul&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;</pre><br /> <br /> == Konfabulator ==<br /> <br /> * (need someone else to fill this in, have never built one or taken them apart)<br /> <br /> == WSRP ==<br /> <br /> * [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp|WSRP Spec]<br /> * SOAP envelopes to transport modules, but there is no specific formatting required for the actual content of the "portlet" (module or widget).<br /> <br /> === Module Response Example ===<br /> <br /> <pre>&lt;urn:getMarkupResponse xmlns:urn=&#34;urn:oasis:names:tc:wsrp:v1:types&#34;&gt;<br /> &lt;urn:markupContext&gt; <br /> &lt;urn:mimeType&gt;text/html; charset=UTF-8&lt;/urn:mimeType&gt;<br /> &lt;urn:markupString&gt;&lt;![CDATA[ <br /> &lt;form method=&#34;post&#34; <br /> action=&#34;wsrp_rewrite?wsrp-urlType=blockingAction/wsrp_rewrite&#34;<br /> id=&#34;wsrp_rewrite_stockForm&#34;&gt;<br /> &lt;table border=&#34;0&#34; width=&#34;100%&#34;&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;Enter Stock Symbol&lt;/td&gt;<br /> &lt;td&gt;&lt;input name=&#34;symbol&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;input type=&#34;submit&#34; value=&#34;Submit&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;/table&gt;<br /> &lt;/form&gt; <br /> ]]&gt;&lt;/urn:markupString&gt;<br /> &lt;urn:locale&gt;en-US&lt;/urn:locale&gt;<br /> &lt;urn:requiresUrlRewriting&gt;true&lt;/urn:requiresUrlRewriting&gt;<br /> &lt;urn:preferredTitle&gt;Portfolio Manager&lt;/urn:preferredTitle&gt;<br /> &lt;/urn:markupContext&gt; <br /> &lt;urn:sessionContext&gt; <br /> &lt;urn:sessionID&gt;sessionID_1&lt;/urn:sessionID&gt; <br /> &lt;urn:expires&gt;300&lt;/urn:expires&gt; <br /> &lt;/urn:sessionContext&gt; <br /> &lt;/urn:getMarkupResponse&gt;</pre><br /> <br /> <br /> == XBL ==<br /> '''XBL''' ('''Extensible Binding Language''') is technology developed [http://mozilla.org Mozilla]. Although often used with XUL for making widgets, it can also be used with HTML. XBL somewhat serves the same role as CSS or XSL, but much much more powerful!<br /> <br /> For example, I could create a new HTML (or XUL or whatever) element/tag; let's say I create the new element: '''<shake>'''. The way the new '''<shake>''' element would work is that what the user puts the mouse over the element (on the page) it shakes whatever is in it. So for example, we might have the following HTML snipped with the '''<shake>''' element:<br /> <br /> <nowiki><br /> <html><br /> <head><br /> <style type="text/css"><br /> <br /> </style><br /> </head><br /> <br /> <body><br /> I want you to </nowiki>'''<nowiki><shake>shake this</shake>.</nowiki>'''<nowiki><br /> </body><br /> <br /> </html><br /> </nowiki><br /> <br /> Note the '''-moz-binding''' CSS code. This is NOT standard CSS but a Mozilla extension. (CSS extensions have a prepending hyphen.)<br /> <br /> Also note that the '''-moz-binding''' refers to an XBL file named "myxbl.xml". Here's how it could look:<br /> <br /> <nowiki><br /> <?xml version="1.0"?><br /> <br /> <bindings xmlns="http://www.mozilla.org/xbl"><br /> <binding id="shake-it-baby"><br /> <content><br /> <children /><br /> </content><br /> <handlers><br /> <handler event="mouseover" action="a_javascript_function_that_shakes_it();" /><br /> </handlers><br /> </binding><br /> </bindings><br /> </nowiki><br /> <br /> Here's another example. I'll create a new element/tag that draws a circle around the text inside of it. I'll call the new element/tag <incircle>. For, this we might have the HTML code:<br /> <br /> <nowiki><br /> <html><br /> <head><br /> <style type="text/css"><br /> <br /> </style><br /> </head><br /> <br /> <body><br /> </nowiki>'''<nowiki><incircle>I'm in a circle</incircle></nowiki>'''<nowiki><br /> </body><br /> <br /> </html><br /> </nowiki><br /> <br /> For this example, the "somexbl.xml" file could look like:<br /> <br /> <nowiki><br /> <?xml version="1.0"?><br /> <br /> <bindings xmlns="http://www.mozilla.org/xbl"<br /> xmlns:svg="http://www.w3.org/2000/svg"<br /> ><br /> <binding id="put-it-in-a-circle"><br /> <content><br /> <svg:circle cx="100" cy="50" r="40" stroke="black" stroke-width="2" fill="red"/><br /> <children /><br /> </content><br /> </binding><br /> </bindings><br /> </nowiki><br /> <br /> Notice that I used SVG to draw circle. (OK, that SVG code is probably really bad. And if you use that XBL code it won't look good. In real life, I'd want to use JavaScript to figure out the radius of the circle, where the x and y coordinates of the circle should be, etc. But this is just an example to show you how the XBL <content> element could be used. I could have probably use the HTML <canvas> element to do this too.)<br /> <br /> == Microsoft "Gadgets" ==<br /> <br /> * Look a little like Dashboard Widgets, all proprietary XML and Javascript. <br /> * XML Manifest much like Dashboard's plist file.<br /> * All functionality and appearance is controlled by javascript.<br /> * [http://microsoftgadgets.com/ More info]</div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-examples&diff=2548 widget-examples 2005-10-30T03:11:56Z

<p>KevinLawver: /* AOL's Channel Content Modules - [http://sports.aol.com|AOL Sports example] */</p> <hr /> <div>= widget examples =<br /> <br /> == Contributor(s) ==<br /> <br /> * [http://lawver.net Kevin Lawver]<br /> * [http://changelog.ca Charles Iliya Krempeaux]<br /> * ...<br /> <br /> == Apple's Dashboard ==<br /> <br /> * Uses an XML Manifest file to specify data about the "widget" (width, height, thumbnail image, title and version).<br /> * No requirements for markup around widgets.<br /> <br /> === Dashboard Example (plist) ===<br /> <br /> <pre>&lt;?xml version=&#34;1.0&#34; encoding=&#34;UTF-8&#34;?&gt;<br /> &lt;!DOCTYPE plist PUBLIC &#34;-//Apple Computer//DTD PLIST 1.0//EN&#34; &#34;http://www.apple.com/DTDs/PropertyList-1.0.dtd&#34;&gt;<br /> &lt;plist version=&#34;1.0&#34;&gt;<br /> &lt;dict&gt;<br /> &lt;key&gt;AllowNetworkAccess&lt;/key&gt;<br /> &lt;true/&gt;<br /> &lt;key&gt;CFBundleDisplayName&lt;/key&gt;<br /> &lt;string&gt;AIM Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleIdentifier&lt;/key&gt;<br /> &lt;string&gt;com.aimfight.widget&lt;/string&gt;<br /> &lt;key&gt;CFBundleName&lt;/key&gt;<br /> &lt;string&gt;AOL Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleShortVersionString&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CFBundleVersion&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CloseBoxInsetX&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;CloseBoxInsetY&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;MainHTML&lt;/key&gt;<br /> &lt;string&gt;fight.html&lt;/string&gt;<br /> &lt;/dict&gt;<br /> &lt;/plist&gt;</pre><br /> <br /> == AOL's Channel Content Modules - [http://sports.aol.com AOL Sports example] ==<br /> <br /> * Each module (widget) has a markup envelope and some required elements that make it a module and allow for consistent styles across products.<br /> <br /> === Example ===<br /> <br /> <pre>&lt;div class=&#34;module themedList&#34;&gt;<br /> &lt;div class=&#34;header&#34;&gt;&lt;h3&gt;Kevin&#39;s List Of Fruit&lt;/h3&gt;&lt;/div&gt;<br /> &lt;div class=&#34;body&#34;&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Apples&lt;/li&gt;<br /> &lt;li&gt;Oranges&lt;/li&gt;<br /> &lt;/ul&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;</pre><br /> <br /> == Konfabulator ==<br /> <br /> * (need someone else to fill this in, have never built one or taken them apart)<br /> <br /> == WSRP ==<br /> <br /> * [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp|WSRP Spec]<br /> * SOAP envelopes to transport modules, but there is no specific formatting required for the actual content of the "portlet" (module or widget).<br /> <br /> === Module Response Example ===<br /> <br /> <pre>&lt;urn:getMarkupResponse xmlns:urn=&#34;urn:oasis:names:tc:wsrp:v1:types&#34;&gt;<br /> &lt;urn:markupContext&gt; <br /> &lt;urn:mimeType&gt;text/html; charset=UTF-8&lt;/urn:mimeType&gt;<br /> &lt;urn:markupString&gt;&lt;![CDATA[ <br /> &lt;form method=&#34;post&#34; <br /> action=&#34;wsrp_rewrite?wsrp-urlType=blockingAction/wsrp_rewrite&#34;<br /> id=&#34;wsrp_rewrite_stockForm&#34;&gt;<br /> &lt;table border=&#34;0&#34; width=&#34;100%&#34;&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;Enter Stock Symbol&lt;/td&gt;<br /> &lt;td&gt;&lt;input name=&#34;symbol&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;input type=&#34;submit&#34; value=&#34;Submit&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;/table&gt;<br /> &lt;/form&gt; <br /> ]]&gt;&lt;/urn:markupString&gt;<br /> &lt;urn:locale&gt;en-US&lt;/urn:locale&gt;<br /> &lt;urn:requiresUrlRewriting&gt;true&lt;/urn:requiresUrlRewriting&gt;<br /> &lt;urn:preferredTitle&gt;Portfolio Manager&lt;/urn:preferredTitle&gt;<br /> &lt;/urn:markupContext&gt; <br /> &lt;urn:sessionContext&gt; <br /> &lt;urn:sessionID&gt;sessionID_1&lt;/urn:sessionID&gt; <br /> &lt;urn:expires&gt;300&lt;/urn:expires&gt; <br /> &lt;/urn:sessionContext&gt; <br /> &lt;/urn:getMarkupResponse&gt;</pre><br /> <br /> <br /> == XBL ==<br /> '''XBL''' ('''Extensible Binding Language''') is technology developed [http://mozilla.org Mozilla]. Although often used with XUL for making widgets, it can also be used with HTML. XBL somewhat serves the same role as CSS or XSL, but much much more powerful!<br /> <br /> For example, I could create a new HTML (or XUL or whatever) element/tag; let's say I create the new element: '''<shake>'''. The way the new '''<shake>''' element would work is that what the user puts the mouse over the element (on the page) it shakes whatever is in it. So for example, we might have the following HTML snipped with the '''<shake>''' element:<br /> <br /> <nowiki><br /> <html><br /> <head><br /> <style type="text/css"><br /> <br /> </style><br /> </head><br /> <br /> <body><br /> I want you to </nowiki>'''<nowiki><shake>shake this</shake>.</nowiki>'''<nowiki><br /> </body><br /> <br /> </html><br /> </nowiki><br /> <br /> Note the '''-moz-binding''' CSS code. This is NOT standard CSS but a Mozilla extension. (CSS extensions have a prepending hyphen.)<br /> <br /> Also note that the '''-moz-binding''' refers to an XBL file named "myxbl.xml". Here's how it could look:<br /> <br /> <nowiki><br /> <?xml version="1.0"?><br /> <br /> <bindings xmlns="http://www.mozilla.org/xbl"><br /> <binding id="shake-it-baby"><br /> <content><br /> <children /><br /> </content><br /> <handlers><br /> <handler event="mouseover" action="a_javascript_function_that_shakes_it();" /><br /> </handlers><br /> </binding><br /> </bindings><br /> </nowiki><br /> <br /> Here's another example. I'll create a new element/tag that draws a circle around the text inside of it. I'll call the new element/tag <incircle>. For, this we might have the HTML code:<br /> <br /> <nowiki><br /> <html><br /> <head><br /> <style type="text/css"><br /> <br /> </style><br /> </head><br /> <br /> <body><br /> </nowiki>'''<nowiki><incircle>I'm in a circle</incircle></nowiki>'''<nowiki><br /> </body><br /> <br /> </html><br /> </nowiki><br /> <br /> For this example, the "somexbl.xml" file could look like:<br /> <br /> <nowiki><br /> <?xml version="1.0"?><br /> <br /> <bindings xmlns="http://www.mozilla.org/xbl"<br /> xmlns:svg="http://www.w3.org/2000/svg"<br /> ><br /> <binding id="put-it-in-a-circle"><br /> <content><br /> <svg:circle cx="100" cy="50" r="40" stroke="black" stroke-width="2" fill="red"/><br /> <children /><br /> </content><br /> </binding><br /> </bindings><br /> </nowiki><br /> <br /> Notice that I used SVG to draw circle. (OK, that SVG code is probably really bad. And if you use that XBL code it won't look good. In real life, I'd want to use JavaScript to figure out the radius of the circle, where the x and y coordinates of the circle should be, etc. But this is just an example to show you how the XBL <content> element could be used. I could have probably use the HTML <canvas> element to do this too.)</div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-brainstorming&diff=6389 widget-brainstorming 2005-10-28T19:54:36Z

<p>KevinLawver: /* Use Cases */</p> <hr /> <div>__TOC__<br /> <br /> = Widget Brainstorming =<br /> <br /> == Contributors ==<br /> <br /> * [http://lawver.net Kevin Lawver], [http://aol.com America Online]<br /> * Shawn Carnell, [http://aol.com America Online]<br /> <br /> == Problem ==<br /> <br /> There are currently a million ways to embed distinct snippets of content and functionality on web pages. The most common two are probably iframes and some form of javascript syndication (you put this script on the page, we'll document.write some stuff on your page). In the XML world, there's RSS, Atom, and the WSRP Portlet spec for exchanging small pieces of data (although it could be said that neither RSS or Atom are meant for this sort of thing). WSRP is the only spec that's specifically meant for exchanging widgets (or modules or portlets), and it's extremely complex.<br /> <br /> I ([[User:KevinLawver]]) think this is a perfect opportunity to create a microformat for creating, delivering and discovery of small (micro, even) content on the web.<br /> <br /> See the examples on [[widget-examples]] for current implementations.<br /> <br /> == Meta Data == <br /> <br /> There are several things that need to be known about a widget, including:<br /> <br /> * License<br /> * Any configuration options that need to be set.<br /> * Dimensions<br /> * Associated files<br /> <br /> == Use Cases ==<br /> <br /> === Remotely Hosted Tools ===<br /> <br /> * User had pictures hosted on photo-sharing site.<br /> * Their blogging tool would to surface a tool provided by the photo-sharing site in that tool.<br /> * Blogging tool sends request to photo-sharing site, and photo-sharing site returns the tool in an XHTML document marked up so the blogging tool knows what pieces apply to editing data with the tool, and what pieces are used in display, and associated linked resources (CSS, Javascript, etc).<br /> <br /> == Specification Proposal ==<br /> <br /> A proposal is currently hosted at http://dev.lawver.net/modulet/profile/. We are eager to receive feedback on [http://microformats.org/mailman/listinfo/microformats-discuss microformat-discuss] or [http://listserv.aol.com/archives/modulet-discuss.html modulet-discuss@listserv.aol.com]. It's a work in progress; please lend your voice.<br /> <br /> == Related Microformats ==<br /> <br /> * [[xoxo]] - to hold configuration or meta data about the widget.<br /> * [[rel-license]] - link to license for widget.</div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-brainstorming&diff=2476 widget-brainstorming 2005-10-12T19:27:36Z

<p>KevinLawver: </p> <hr /> <div>__TOC__<br /> <br /> = Widget Brainstorming =<br /> <br /> == Contributors ==<br /> <br /> * [http://lawver.net Kevin Lawver], [http://aol.com America Online]<br /> <br /> == Problem ==<br /> <br /> There are currently a million ways to embed distinct snippets of content and functionality on web pages. The most common two are probably iframes and some form of javascript syndication (you put this script on the page, we'll document.write some stuff on your page). In the XML world, there's RSS, Atom, and the WSRP Portlet spec for exchanging small pieces of data (although it could be said that neither RSS or Atom are meant for this sort of thing). WSRP is the only spec that's specifically meant for exchanging widgets (or modules or portlets), and it's extremely complex.<br /> <br /> I ([[User:KevinLawver]]) think this is a perfect opportunity to create a microformat for creating, delivering and discovery of small (micro, even) content on the web.<br /> <br /> See the examples on [[widget-examples]] for current implementations.<br /> <br /> == Meta Data == <br /> <br /> There are several things that need to be known about a widget, including:<br /> <br /> * License<br /> * Any configuration options that need to be set.<br /> * Dimensions<br /> * Associated files<br /> <br /> == Use Cases ==<br /> <br /> === Tools ===<br /> <br /> === Games ===<br /> <br /> == Related Microformats ==<br /> <br /> * [[xoxo]] - to hold configuration or meta data about the widget.<br /> * [[rel-license]] - link to license for widget.</div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-brainstorming&diff=2104 widget-brainstorming 2005-10-12T19:05:11Z

<p>KevinLawver: /* Problem */</p> <hr /> <div>__TOC__<br /> <br /> = Widget Brainstorming =<br /> <br /> == Problem ==<br /> <br /> There are currently a million ways to embed distinct snippets of content and functionality on web pages. The most common two are probably iframes and some form of javascript syndication (you put this script on the page, we'll document.write some stuff on your page). In the XML world, there's RSS, Atom, and the WSRP Portlet spec for exchanging small pieces of data (although it could be said that neither RSS or Atom are meant for this sort of thing). WSRP is the only spec that's specifically meant for exchanging widgets (or modules or portlets), and it's extremely complex.<br /> <br /> I ([[User:KevinLawver]]) think this is a perfect opportunity to create a microformat for creating, delivering and discovery of small (micro, even) content on the web.<br /> <br /> See the examples on [[widget-examples]] for current implementations.<br /> <br /> == Meta Data == <br /> <br /> There are several things that need to be known about a widget, including:<br /> <br /> * License<br /> * Any configuration options that need to be set.<br /> * Dimensions<br /> * Associated files<br /> <br /> == Use Cases ==<br /> <br /> === Tools ===<br /> <br /> === Games ===<br /> <br /> == Related Microformats ==<br /> <br /> * [[xoxo]] - to hold configuration or meta data about the widget.<br /> * [[rel-license]] - link to license for widget.</div>

KevinLawver https://microformats.org/wiki/index.php?title=User:KevinLawver&diff=23632 User:KevinLawver 2005-10-12T19:02:30Z

<p>KevinLawver: </p> <hr /> <div>Ooops... I probably should have create my user page here.<br /> <br /> I'm a guy with a [http://lawver.net website] who works for a [http://aol.com big company], and who loves all things web standardsy.</div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-brainstorming&diff=2103 widget-brainstorming 2005-10-12T19:00:58Z

<p>KevinLawver: /* Problem */</p> <hr /> <div>__TOC__<br /> <br /> = Widget Brainstorming =<br /> <br /> == Problem ==<br /> <br /> There are currently a million ways to embed distinct snippets of content and functionality on web pages. The most common two are probably iframes and some form of javascript syndication (you put this script on the page, we'll document.write some stuff on your page). In the XML world, there's RSS, Atom, and the WSRP Portlet spec for exchanging small pieces of data (although it could be said that neither RSS or Atom are meant for this sort of thing). WSRP is the only spec that's specifically meant for exchanging widgets (or modules or portlets), and it's extremely complex.<br /> <br /> I [[KevinLawver]] think this is a perfect opportunity to create a microformat for creating, delivering and discovery of small (micro, even) content on the web.<br /> <br /> See the examples on [[widget-examples]] for current implementations.<br /> <br /> == Meta Data == <br /> <br /> There are several things that need to be known about a widget, including:<br /> <br /> * License<br /> * Any configuration options that need to be set.<br /> * Dimensions<br /> * Associated files<br /> <br /> == Use Cases ==<br /> <br /> === Tools ===<br /> <br /> === Games ===<br /> <br /> == Related Microformats ==<br /> <br /> * [[xoxo]] - to hold configuration or meta data about the widget.<br /> * [[rel-license]] - link to license for widget.</div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-brainstorming&diff=2100 widget-brainstorming 2005-10-12T19:00:47Z

<p>KevinLawver: </p> <hr /> <div>__TOC__<br /> <br /> = Widget Brainstorming =<br /> <br /> == Problem ==<br /> <br /> There are currently a million ways to embed distinct snippets of content and functionality on web pages. The most common two are probably iframes and some form of javascript syndication (you put this script on the page, we'll document.write some stuff on your page). In the XML world, there's RSS, Atom, and the WSRP Portlet spec for exchanging small pieces of data (although it could be said that neither RSS or Atom are meant for this sort of thing). WSRP is the only spec that's specifically meant for exchanging widgets (or modules or portlets), and it's extremely complex.<br /> <br /> I (KevinLawver) think this is a perfect opportunity to create a microformat for creating, delivering and discovery of small (micro, even) content on the web.<br /> <br /> See the examples on [[widget-examples]] for current implementations.<br /> <br /> == Meta Data == <br /> <br /> There are several things that need to be known about a widget, including:<br /> <br /> * License<br /> * Any configuration options that need to be set.<br /> * Dimensions<br /> * Associated files<br /> <br /> == Use Cases ==<br /> <br /> === Tools ===<br /> <br /> === Games ===<br /> <br /> == Related Microformats ==<br /> <br /> * [[xoxo]] - to hold configuration or meta data about the widget.<br /> * [[rel-license]] - link to license for widget.</div>

KevinLawver https://microformats.org/wiki/index.php?title=Main_Page&diff=29040 Main Page 2005-10-12T18:47:36Z

<p>KevinLawver: /* Exploratory discussions */</p> <hr /> <div>__NOTOC__<br /> = Microformats Wiki =<br /> Welcome to the microformats wiki. There's a lot going on around here, but feel free to jump in and offer your assistance.<br /> <br /> But First: <br /> <br /> '''Please read [[how-to-play]] before making any edits.'''<br /> <br /> '''Please read [[process]] before proposing any new microformats.'''<br /> <br /> == Introduction ==<br /> <br /> What are microformats? See the [http://microformats.org/about/ about page] for an overview, and the [[introduction]] page for more info. Recent [[press]] and [[presentations]] are also a good place for some background reading as well. <br /> <br /> One popular definition from our mailing list is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br /> :simple conventions<br /> :for embedding semantic markup<br /> ::for a specific problem domain<br /> :in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br /> ::that normalize existing content usage patterns<br /> ::using brief, descriptive class names <br /> ::often based on existing interoperable standards<br /> :to enable decentralized development<br /> ::of resources, tools, and services<br /> <br /> "Or do you just use your browser to browse? That's so 20th century." -- [http://diveintomark.org Mark Pilgrim]<br /> <br /> == Specifications ==<br /> [[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br /> * [[hcalendar|hCalendar]]<br /> * [[hcard|hCard]]<br /> * [[rel-license|RelLicense]]<br /> * [[rel-nofollow|RelNoFollow]]<br /> * [[rel-tag|RelTag]]<br /> * [[vote-links|VoteLinks]]<br /> * [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br /> * [http://gmpg.org/xmdp/ XMDP]<br /> * [[xoxo|XOXO]]<br /> <br /> == Drafts ==<br /> * [[adr|adr]] (new!)<br /> * [[geo|geo]] (new!)<br /> * [[hreview|hReview]]<br /> * [[rel-directory]]<br /> * [[rel-enclosure]]<br /> * [[relpayment-research | rel-payment]]<br /> * [[robots-exclusion|Robots Exclusion]]<br /> * [[xfolk]]<br /> <br /> == Design Patterns ==<br /> <br /> Design patterns give microformat authors a vocabulary for expressing their ideas consistently with what has already been done. ''If you're tempted to try your hand at writing a microformat '''[[process|read this first]]'''!''<br /> <br /> * [[datetime-design-pattern]]<br /> * [[class-design-pattern]]<br /> * [[rel-design-pattern]]<br /> * [[abbr-design-pattern]]<br /> <br /> == Exploratory discussions ==<br /> Focused on real-world [[examples]] to motivate the microformat.<br /> *[[blog-post-examples]], [[blog-post-formats]], [[blog-post-brainstorming]]<br /> *[[blog-description-format]]<br /> *[[chat-examples]]<br /> *[[citation-brainstorming]]<br /> *[[cite|Planning pages for a citation microformat]]<br /> *[[comments-formats]]<br /> *[[directory-inclusion-examples]], [[directory-inclusion-formats]]. (see also [[rel-directory]])<br /> *[[forms-examples]]<br /> *[[genealogy-formats]]<br /> *[[last-modified-examples]]<br /> *[[listing-examples]], [[listing-formats]], [[listing-brainstorming]]<br /> *[[location-formats]]. (see also [[adr]] and [[geo]])<br /> *[[media-metadata-examples]]<br /> *[[other-formats]]<br /> *[[requirements-testing]]<br /> *[[resume-brainstorming]], [[resume-formats]]<br /> *[[table-examples]]<br /> *[[wiki-formats]]<br /> *[[xmdp-brainstorming]] (see also [[xmdp-faq]])<br /> *[[widget-brainstorming]]<br /> *[[widget-examples]]<br /> <br /> == Tools & Test Cases & Additional Research ==<br /> <br /> The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br /> <br /> *[[selected-test-cases-from-the-web]]<br /> *[[vcard-implementations]]<br /> <br /> == shared work areas ==<br /> * [[buttons]] (new!)<br /> * [[to-do]]<br /> * [[marked-for-deletion]]<br /> <br /> == microformats wiki in other languages ==<br /> <br /> You may read and edit microformats articles in <del>many different languages</del> at least one more language:<br /> <br /> === microformats wiki languages with over 2 articles ===<br /> <br /> [[Main_Page-fr|Français (French)]] (Thanks to neuro`!)</div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-examples&diff=2444 widget-examples 2005-09-30T13:35:14Z

<p>KevinLawver: /* Contributor(s) */</p> <hr /> <div>= widget examples =<br /> <br /> == Contributor(s) ==<br /> <br /> * [http://lawver.net Kevin Lawver]<br /> * ...<br /> <br /> == Apple's Dashboard ==<br /> <br /> * Uses an XML Manifest file to specify data about the "widget" (width, height, thumbnail image, title and version).<br /> * No requirements for markup around widgets.<br /> <br /> === Dashboard Example (plist) ===<br /> <br /> <pre>&lt;?xml version=&#34;1.0&#34; encoding=&#34;UTF-8&#34;?&gt;<br /> &lt;!DOCTYPE plist PUBLIC &#34;-//Apple Computer//DTD PLIST 1.0//EN&#34; &#34;http://www.apple.com/DTDs/PropertyList-1.0.dtd&#34;&gt;<br /> &lt;plist version=&#34;1.0&#34;&gt;<br /> &lt;dict&gt;<br /> &lt;key&gt;AllowNetworkAccess&lt;/key&gt;<br /> &lt;true/&gt;<br /> &lt;key&gt;CFBundleDisplayName&lt;/key&gt;<br /> &lt;string&gt;AIM Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleIdentifier&lt;/key&gt;<br /> &lt;string&gt;com.aimfight.widget&lt;/string&gt;<br /> &lt;key&gt;CFBundleName&lt;/key&gt;<br /> &lt;string&gt;AOL Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleShortVersionString&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CFBundleVersion&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CloseBoxInsetX&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;CloseBoxInsetY&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;MainHTML&lt;/key&gt;<br /> &lt;string&gt;fight.html&lt;/string&gt;<br /> &lt;/dict&gt;<br /> &lt;/plist&gt;</pre><br /> <br /> == AOL's Channel Content Modules - [http://sports.aol.com|AOL Sports example] ==<br /> <br /> * Each module (widget) has a markup envelope and some required elements that make it a module and allow for consistent styles across products.<br /> <br /> === Example ===<br /> <br /> <pre>&lt;div class=&#34;module themedList&#34;&gt;<br /> &lt;div class=&#34;header&#34;&gt;&lt;h3&gt;Kevin&#39;s List Of Fruit&lt;/h3&gt;&lt;/div&gt;<br /> &lt;div class=&#34;body&#34;&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Apples&lt;/li&gt;<br /> &lt;li&gt;Oranges&lt;/li&gt;<br /> &lt;/ul&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;</pre><br /> <br /> == Konfabulator ==<br /> <br /> * (need someone else to fill this in, have never built one or taken them apart)<br /> <br /> == WSRP ==<br /> <br /> * [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp|WSRP Spec]<br /> * SOAP envelopes to transport modules, but there is no specific formatting required for the actual content of the "portlet" (module or widget).<br /> <br /> === Module Response Example ===<br /> <br /> <pre>&lt;urn:getMarkupResponse xmlns:urn=&#34;urn:oasis:names:tc:wsrp:v1:types&#34;&gt;<br /> &lt;urn:markupContext&gt; <br /> &lt;urn:mimeType&gt;text/html; charset=UTF-8&lt;/urn:mimeType&gt;<br /> &lt;urn:markupString&gt;&lt;![CDATA[ <br /> &lt;form method=&#34;post&#34; <br /> action=&#34;wsrp_rewrite?wsrp-urlType=blockingAction/wsrp_rewrite&#34;<br /> id=&#34;wsrp_rewrite_stockForm&#34;&gt;<br /> &lt;table border=&#34;0&#34; width=&#34;100%&#34;&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;Enter Stock Symbol&lt;/td&gt;<br /> &lt;td&gt;&lt;input name=&#34;symbol&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;input type=&#34;submit&#34; value=&#34;Submit&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;/table&gt;<br /> &lt;/form&gt; <br /> ]]&gt;&lt;/urn:markupString&gt;<br /> &lt;urn:locale&gt;en-US&lt;/urn:locale&gt;<br /> &lt;urn:requiresUrlRewriting&gt;true&lt;/urn:requiresUrlRewriting&gt;<br /> &lt;urn:preferredTitle&gt;Portfolio Manager&lt;/urn:preferredTitle&gt;<br /> &lt;/urn:markupContext&gt; <br /> &lt;urn:sessionContext&gt; <br /> &lt;urn:sessionID&gt;sessionID_1&lt;/urn:sessionID&gt; <br /> &lt;urn:expires&gt;300&lt;/urn:expires&gt; <br /> &lt;/urn:sessionContext&gt; <br /> &lt;/urn:getMarkupResponse&gt;</pre></div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-examples&diff=1809 widget-examples 2005-09-30T13:35:02Z

<p>KevinLawver: added my url... I'm vain that way.</p> <hr /> <div>= widget examples =<br /> <br /> == Contributor(s) ==<br /> <br /> * [[http://lawver.net | Kevin Lawver]]<br /> * ...<br /> <br /> == Apple's Dashboard ==<br /> <br /> * Uses an XML Manifest file to specify data about the "widget" (width, height, thumbnail image, title and version).<br /> * No requirements for markup around widgets.<br /> <br /> === Dashboard Example (plist) ===<br /> <br /> <pre>&lt;?xml version=&#34;1.0&#34; encoding=&#34;UTF-8&#34;?&gt;<br /> &lt;!DOCTYPE plist PUBLIC &#34;-//Apple Computer//DTD PLIST 1.0//EN&#34; &#34;http://www.apple.com/DTDs/PropertyList-1.0.dtd&#34;&gt;<br /> &lt;plist version=&#34;1.0&#34;&gt;<br /> &lt;dict&gt;<br /> &lt;key&gt;AllowNetworkAccess&lt;/key&gt;<br /> &lt;true/&gt;<br /> &lt;key&gt;CFBundleDisplayName&lt;/key&gt;<br /> &lt;string&gt;AIM Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleIdentifier&lt;/key&gt;<br /> &lt;string&gt;com.aimfight.widget&lt;/string&gt;<br /> &lt;key&gt;CFBundleName&lt;/key&gt;<br /> &lt;string&gt;AOL Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleShortVersionString&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CFBundleVersion&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CloseBoxInsetX&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;CloseBoxInsetY&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;MainHTML&lt;/key&gt;<br /> &lt;string&gt;fight.html&lt;/string&gt;<br /> &lt;/dict&gt;<br /> &lt;/plist&gt;</pre><br /> <br /> == AOL's Channel Content Modules - [http://sports.aol.com|AOL Sports example] ==<br /> <br /> * Each module (widget) has a markup envelope and some required elements that make it a module and allow for consistent styles across products.<br /> <br /> === Example ===<br /> <br /> <pre>&lt;div class=&#34;module themedList&#34;&gt;<br /> &lt;div class=&#34;header&#34;&gt;&lt;h3&gt;Kevin&#39;s List Of Fruit&lt;/h3&gt;&lt;/div&gt;<br /> &lt;div class=&#34;body&#34;&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Apples&lt;/li&gt;<br /> &lt;li&gt;Oranges&lt;/li&gt;<br /> &lt;/ul&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;</pre><br /> <br /> == Konfabulator ==<br /> <br /> * (need someone else to fill this in, have never built one or taken them apart)<br /> <br /> == WSRP ==<br /> <br /> * [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp|WSRP Spec]<br /> * SOAP envelopes to transport modules, but there is no specific formatting required for the actual content of the "portlet" (module or widget).<br /> <br /> === Module Response Example ===<br /> <br /> <pre>&lt;urn:getMarkupResponse xmlns:urn=&#34;urn:oasis:names:tc:wsrp:v1:types&#34;&gt;<br /> &lt;urn:markupContext&gt; <br /> &lt;urn:mimeType&gt;text/html; charset=UTF-8&lt;/urn:mimeType&gt;<br /> &lt;urn:markupString&gt;&lt;![CDATA[ <br /> &lt;form method=&#34;post&#34; <br /> action=&#34;wsrp_rewrite?wsrp-urlType=blockingAction/wsrp_rewrite&#34;<br /> id=&#34;wsrp_rewrite_stockForm&#34;&gt;<br /> &lt;table border=&#34;0&#34; width=&#34;100%&#34;&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;Enter Stock Symbol&lt;/td&gt;<br /> &lt;td&gt;&lt;input name=&#34;symbol&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;input type=&#34;submit&#34; value=&#34;Submit&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;/table&gt;<br /> &lt;/form&gt; <br /> ]]&gt;&lt;/urn:markupString&gt;<br /> &lt;urn:locale&gt;en-US&lt;/urn:locale&gt;<br /> &lt;urn:requiresUrlRewriting&gt;true&lt;/urn:requiresUrlRewriting&gt;<br /> &lt;urn:preferredTitle&gt;Portfolio Manager&lt;/urn:preferredTitle&gt;<br /> &lt;/urn:markupContext&gt; <br /> &lt;urn:sessionContext&gt; <br /> &lt;urn:sessionID&gt;sessionID_1&lt;/urn:sessionID&gt; <br /> &lt;urn:expires&gt;300&lt;/urn:expires&gt; <br /> &lt;/urn:sessionContext&gt; <br /> &lt;/urn:getMarkupResponse&gt;</pre></div>

KevinLawver https://microformats.org/wiki/index.php?title=Main_Page&diff=29010 Main Page 2005-09-27T16:33:17Z

<p>KevinLawver: /* Exploratory discussions */</p> <hr /> <div>__NOTOC__<br /> = Microformats Wiki =<br /> Welcome to the microformats wiki. There's a lot going on around here, but feel free to jump in and offer your assistance.<br /> <br /> But First: <br /> <br /> '''Please read [[how-to-play]] before making any edits.'''<br /> <br /> '''Please read [[process]] before proposing any new microformats.'''<br /> <br /> == Introduction ==<br /> <br /> What are microformats? See the [http://microformats.org/about/ about page] for an overview, and the [[introduction]] page for more info. Recent [[press]] and [[presentations]] are also a good place for some background reading as well. <br /> <br /> One popular definition from our mailing list is "simple conventions for embedding semantics in HTML to enable decentralized development." More precisely, microformats can be defined as:<br /> :simple conventions<br /> :for embedding semantic markup<br /> ::for a specific problem domain<br /> :in human-readable (X)HTML/XML documents, Atom/RSS feeds, and "plain" XML<br /> ::that normalize existing content usage patterns<br /> ::using brief, descriptive class names <br /> ::often based on existing interoperable standards<br /> :to enable decentralized development<br /> ::of resources, tools, and services<br /> <br /> == Specifications ==<br /> [[microformats|Microformats]] open standards specifications (see also: [[implementations]])<br /> * [[hcalendar|hCalendar]]<br /> * [[hcard|hCard]]<br /> * [[rel-license|RelLicense]]<br /> * [[rel-nofollow|RelNoFollow]]<br /> * [[rel-tag|RelTag]]<br /> * [[vote-links|VoteLinks]]<br /> * [http://gmpg.org/xfn/ XFN] (see also: [[xfn-implementations]])<br /> * [http://gmpg.org/xmdp/ XMDP]<br /> * [[xoxo|XOXO]]<br /> <br /> == Drafts ==<br /> * [[adr|adr]] (new!)<br /> * [[geo|geo]] (new!)<br /> * [[hreview|hReview]]<br /> * [[rel-directory]]<br /> * [[rel-enclosure]]<br /> * [[relpayment-research | rel-payment]]<br /> * [[robots-exclusion|Robots Exclusion]]<br /> * [[xfolk]]<br /> <br /> == Design Patterns ==<br /> <br /> * [[datetime-design-pattern]]<br /> <br /> == Exploratory discussions ==<br /> *[[blog-description-format]]<br /> *[[blog-post-formats]]<br /> *[[blog-post-brainstorming]]<br /> *[[chat-examples]]<br /> *[[citation-brainstorming]]<br /> *[[cite|Planning pages for a citation microformat]]<br /> *[[comments-formats]]<br /> *[[directory-inclusion-examples]] (see also [[directory-inclusion-formats]])<br /> *[[genealogy-formats]]<br /> *[[last-modified-examples]]<br /> *[[listing-examples]] (see also [[listing-formats]], [[listing-brainstorming]])<br /> *[[location-formats]]<br /> *[[media-metadata-examples]]<br /> *[[other-formats]]<br /> *[[requirements-testing]]<br /> *[[resume-brainstorming]]<br /> *[[resume-formats]]<br /> *[[wiki-formats]]<br /> *[[xmdp-brainstorming]] (see also [[xmdp-faq]])<br /> * [[widget-examples]]<br /> <br /> == Tools & Test Cases & Additional Research ==<br /> <br /> The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting tools and services that need to process more than one microformat. This section is intended for editors, parsers, validators, test cases, and other information relevant across multiple microformats.<br /> <br /> *[[selected-test-cases-from-the-web]]<br /> *[[vcard-implementations]]<br /> <br /> == shared work areas ==<br /> * [[buttons]] (new!)<br /> * [[to-do]]<br /> * [[marked-for-deletion]]</div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-examples&diff=1801 widget-examples 2005-09-27T16:30:49Z

<p>KevinLawver: /* Dashboard Example (plist) */</p> <hr /> <div>== Apple's Dashboard ==<br /> <br /> * Uses an XML Manifest file to specify data about the "widget" (width, height, thumbnail image, title and version).<br /> * No requirements for markup around widgets.<br /> <br /> === Dashboard Example (plist) ===<br /> <br /> <pre>&lt;?xml version=&#34;1.0&#34; encoding=&#34;UTF-8&#34;?&gt;<br /> &lt;!DOCTYPE plist PUBLIC &#34;-//Apple Computer//DTD PLIST 1.0//EN&#34; &#34;http://www.apple.com/DTDs/PropertyList-1.0.dtd&#34;&gt;<br /> &lt;plist version=&#34;1.0&#34;&gt;<br /> &lt;dict&gt;<br /> &lt;key&gt;AllowNetworkAccess&lt;/key&gt;<br /> &lt;true/&gt;<br /> &lt;key&gt;CFBundleDisplayName&lt;/key&gt;<br /> &lt;string&gt;AIM Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleIdentifier&lt;/key&gt;<br /> &lt;string&gt;com.aimfight.widget&lt;/string&gt;<br /> &lt;key&gt;CFBundleName&lt;/key&gt;<br /> &lt;string&gt;AOL Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleShortVersionString&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CFBundleVersion&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CloseBoxInsetX&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;CloseBoxInsetY&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;MainHTML&lt;/key&gt;<br /> &lt;string&gt;fight.html&lt;/string&gt;<br /> &lt;/dict&gt;<br /> &lt;/plist&gt;</pre><br /> <br /> == AOL's Channel Content Modules - [http://sports.aol.com|AOL Sports example] ==<br /> <br /> * Each module (widget) has a markup envelope and some required elements that make it a module and allow for consistent styles across products.<br /> <br /> === Example ===<br /> <br /> <pre>&lt;div class=&#34;module themedList&#34;&gt;<br /> &lt;div class=&#34;header&#34;&gt;&lt;h3&gt;Kevin&#39;s List Of Fruit&lt;/h3&gt;&lt;/div&gt;<br /> &lt;div class=&#34;body&#34;&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Apples&lt;/li&gt;<br /> &lt;li&gt;Oranges&lt;/li&gt;<br /> &lt;/ul&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;</pre><br /> <br /> == Konfabulator ==<br /> <br /> * (need someone else to fill this in, have never built one or taken them apart)<br /> <br /> == WSRP ==<br /> <br /> * [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp|WSRP Spec]<br /> * SOAP envelopes to transport modules, but there is no specific formatting required for the actual content of the "portlet" (module or widget).<br /> <br /> === Module Response Example ===<br /> <br /> <pre>&lt;urn:getMarkupResponse xmlns:urn=&#34;urn:oasis:names:tc:wsrp:v1:types&#34;&gt;<br /> &lt;urn:markupContext&gt; <br /> &lt;urn:mimeType&gt;text/html; charset=UTF-8&lt;/urn:mimeType&gt;<br /> &lt;urn:markupString&gt;&lt;![CDATA[ <br /> &lt;form method=&#34;post&#34; <br /> action=&#34;wsrp_rewrite?wsrp-urlType=blockingAction/wsrp_rewrite&#34;<br /> id=&#34;wsrp_rewrite_stockForm&#34;&gt;<br /> &lt;table border=&#34;0&#34; width=&#34;100%&#34;&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;Enter Stock Symbol&lt;/td&gt;<br /> &lt;td&gt;&lt;input name=&#34;symbol&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;input type=&#34;submit&#34; value=&#34;Submit&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;/table&gt;<br /> &lt;/form&gt; <br /> ]]&gt;&lt;/urn:markupString&gt;<br /> &lt;urn:locale&gt;en-US&lt;/urn:locale&gt;<br /> &lt;urn:requiresUrlRewriting&gt;true&lt;/urn:requiresUrlRewriting&gt;<br /> &lt;urn:preferredTitle&gt;Portfolio Manager&lt;/urn:preferredTitle&gt;<br /> &lt;/urn:markupContext&gt; <br /> &lt;urn:sessionContext&gt; <br /> &lt;urn:sessionID&gt;sessionID_1&lt;/urn:sessionID&gt; <br /> &lt;urn:expires&gt;300&lt;/urn:expires&gt; <br /> &lt;/urn:sessionContext&gt; <br /> &lt;/urn:getMarkupResponse&gt;</pre></div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-examples&diff=1788 widget-examples 2005-09-27T16:25:42Z

<p>KevinLawver: /* WSRP */</p> <hr /> <div>== Apple's Dashboard ==<br /> <br /> * Uses an XML Manifest file to specify data about the "widget" (width, height, thumbnail image, title and version).<br /> * No requirements for markup around widgets.<br /> <br /> === Dashboard Example (plist) ===<br /> <br /> <pre><code>&lt;?xml version=&#34;1.0&#34; encoding=&#34;UTF-8&#34;?&gt;<br /> &lt;!DOCTYPE plist PUBLIC &#34;-//Apple Computer//DTD PLIST 1.0//EN&#34; &#34;http://www.apple.com/DTDs/PropertyList-1.0.dtd&#34;&gt;<br /> &lt;plist version=&#34;1.0&#34;&gt;<br /> &lt;dict&gt;<br /> &lt;key&gt;AllowNetworkAccess&lt;/key&gt;<br /> &lt;true/&gt;<br /> &lt;key&gt;CFBundleDisplayName&lt;/key&gt;<br /> &lt;string&gt;AIM Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleIdentifier&lt;/key&gt;<br /> &lt;string&gt;com.aimfight.widget&lt;/string&gt;<br /> &lt;key&gt;CFBundleName&lt;/key&gt;<br /> &lt;string&gt;AOL Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleShortVersionString&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CFBundleVersion&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CloseBoxInsetX&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;CloseBoxInsetY&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;MainHTML&lt;/key&gt;<br /> &lt;string&gt;fight.html&lt;/string&gt;<br /> &lt;/dict&gt;<br /> &lt;/plist&gt;</code></pre><br /> <br /> == AOL's Channel Content Modules - [http://sports.aol.com|AOL Sports example] ==<br /> <br /> * Each module (widget) has a markup envelope and some required elements that make it a module and allow for consistent styles across products.<br /> <br /> === Example ===<br /> <br /> <pre>&lt;div class=&#34;module themedList&#34;&gt;<br /> &lt;div class=&#34;header&#34;&gt;&lt;h3&gt;Kevin&#39;s List Of Fruit&lt;/h3&gt;&lt;/div&gt;<br /> &lt;div class=&#34;body&#34;&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Apples&lt;/li&gt;<br /> &lt;li&gt;Oranges&lt;/li&gt;<br /> &lt;/ul&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;</pre><br /> <br /> == Konfabulator ==<br /> <br /> * (need someone else to fill this in, have never built one or taken them apart)<br /> <br /> == WSRP ==<br /> <br /> * [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp|WSRP Spec]<br /> * SOAP envelopes to transport modules, but there is no specific formatting required for the actual content of the "portlet" (module or widget).<br /> <br /> === Module Response Example ===<br /> <br /> <pre>&lt;urn:getMarkupResponse xmlns:urn=&#34;urn:oasis:names:tc:wsrp:v1:types&#34;&gt;<br /> &lt;urn:markupContext&gt; <br /> &lt;urn:mimeType&gt;text/html; charset=UTF-8&lt;/urn:mimeType&gt;<br /> &lt;urn:markupString&gt;&lt;![CDATA[ <br /> &lt;form method=&#34;post&#34; <br /> action=&#34;wsrp_rewrite?wsrp-urlType=blockingAction/wsrp_rewrite&#34;<br /> id=&#34;wsrp_rewrite_stockForm&#34;&gt;<br /> &lt;table border=&#34;0&#34; width=&#34;100%&#34;&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;Enter Stock Symbol&lt;/td&gt;<br /> &lt;td&gt;&lt;input name=&#34;symbol&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;input type=&#34;submit&#34; value=&#34;Submit&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;/table&gt;<br /> &lt;/form&gt; <br /> ]]&gt;&lt;/urn:markupString&gt;<br /> &lt;urn:locale&gt;en-US&lt;/urn:locale&gt;<br /> &lt;urn:requiresUrlRewriting&gt;true&lt;/urn:requiresUrlRewriting&gt;<br /> &lt;urn:preferredTitle&gt;Portfolio Manager&lt;/urn:preferredTitle&gt;<br /> &lt;/urn:markupContext&gt; <br /> &lt;urn:sessionContext&gt; <br /> &lt;urn:sessionID&gt;sessionID_1&lt;/urn:sessionID&gt; <br /> &lt;urn:expires&gt;300&lt;/urn:expires&gt; <br /> &lt;/urn:sessionContext&gt; <br /> &lt;/urn:getMarkupResponse&gt;</pre></div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-examples&diff=1787 widget-examples 2005-09-27T16:25:17Z

<p>KevinLawver: /* AOL's Channel Content Modules - AOL Sports example */</p> <hr /> <div>== Apple's Dashboard ==<br /> <br /> * Uses an XML Manifest file to specify data about the "widget" (width, height, thumbnail image, title and version).<br /> * No requirements for markup around widgets.<br /> <br /> === Dashboard Example (plist) ===<br /> <br /> <pre><code>&lt;?xml version=&#34;1.0&#34; encoding=&#34;UTF-8&#34;?&gt;<br /> &lt;!DOCTYPE plist PUBLIC &#34;-//Apple Computer//DTD PLIST 1.0//EN&#34; &#34;http://www.apple.com/DTDs/PropertyList-1.0.dtd&#34;&gt;<br /> &lt;plist version=&#34;1.0&#34;&gt;<br /> &lt;dict&gt;<br /> &lt;key&gt;AllowNetworkAccess&lt;/key&gt;<br /> &lt;true/&gt;<br /> &lt;key&gt;CFBundleDisplayName&lt;/key&gt;<br /> &lt;string&gt;AIM Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleIdentifier&lt;/key&gt;<br /> &lt;string&gt;com.aimfight.widget&lt;/string&gt;<br /> &lt;key&gt;CFBundleName&lt;/key&gt;<br /> &lt;string&gt;AOL Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleShortVersionString&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CFBundleVersion&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CloseBoxInsetX&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;CloseBoxInsetY&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;MainHTML&lt;/key&gt;<br /> &lt;string&gt;fight.html&lt;/string&gt;<br /> &lt;/dict&gt;<br /> &lt;/plist&gt;</code></pre><br /> <br /> == AOL's Channel Content Modules - [http://sports.aol.com|AOL Sports example] ==<br /> <br /> * Each module (widget) has a markup envelope and some required elements that make it a module and allow for consistent styles across products.<br /> <br /> === Example ===<br /> <br /> <pre>&lt;div class=&#34;module themedList&#34;&gt;<br /> &lt;div class=&#34;header&#34;&gt;&lt;h3&gt;Kevin&#39;s List Of Fruit&lt;/h3&gt;&lt;/div&gt;<br /> &lt;div class=&#34;body&#34;&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Apples&lt;/li&gt;<br /> &lt;li&gt;Oranges&lt;/li&gt;<br /> &lt;/ul&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;</pre><br /> <br /> == Konfabulator ==<br /> <br /> * (need someone else to fill this in, have never built one or taken them apart)<br /> <br /> == WSRP ==<br /> <br /> * [[http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp|Homepage]]<br /> * SOAP envelopes to transport modules, but there is no specific formatting required for the actual content of the "portlet" (module or widget).<br /> <br /> === Module Response Example ===<br /> <br /> <pre>&lt;urn:getMarkupResponse xmlns:urn=&#34;urn:oasis:names:tc:wsrp:v1:types&#34;&gt;<br /> &lt;urn:markupContext&gt; <br /> &lt;urn:mimeType&gt;text/html; charset=UTF-8&lt;/urn:mimeType&gt;<br /> &lt;urn:markupString&gt;&lt;![CDATA[ <br /> &lt;form method=&#34;post&#34; <br /> action=&#34;wsrp_rewrite?wsrp-urlType=blockingAction/wsrp_rewrite&#34;<br /> id=&#34;wsrp_rewrite_stockForm&#34;&gt;<br /> &lt;table border=&#34;0&#34; width=&#34;100%&#34;&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;Enter Stock Symbol&lt;/td&gt;<br /> &lt;td&gt;&lt;input name=&#34;symbol&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;input type=&#34;submit&#34; value=&#34;Submit&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;/table&gt;<br /> &lt;/form&gt; <br /> ]]&gt;&lt;/urn:markupString&gt;<br /> &lt;urn:locale&gt;en-US&lt;/urn:locale&gt;<br /> &lt;urn:requiresUrlRewriting&gt;true&lt;/urn:requiresUrlRewriting&gt;<br /> &lt;urn:preferredTitle&gt;Portfolio Manager&lt;/urn:preferredTitle&gt;<br /> &lt;/urn:markupContext&gt; <br /> &lt;urn:sessionContext&gt; <br /> &lt;urn:sessionID&gt;sessionID_1&lt;/urn:sessionID&gt; <br /> &lt;urn:expires&gt;300&lt;/urn:expires&gt; <br /> &lt;/urn:sessionContext&gt; <br /> &lt;/urn:getMarkupResponse&gt;</pre></div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-examples&diff=1786 widget-examples 2005-09-27T16:01:39Z

<p>KevinLawver: /* Example */</p> <hr /> <div>== Apple's Dashboard ==<br /> <br /> * Uses an XML Manifest file to specify data about the "widget" (width, height, thumbnail image, title and version).<br /> * No requirements for markup around widgets.<br /> <br /> === Dashboard Example (plist) ===<br /> <br /> <pre><code>&lt;?xml version=&#34;1.0&#34; encoding=&#34;UTF-8&#34;?&gt;<br /> &lt;!DOCTYPE plist PUBLIC &#34;-//Apple Computer//DTD PLIST 1.0//EN&#34; &#34;http://www.apple.com/DTDs/PropertyList-1.0.dtd&#34;&gt;<br /> &lt;plist version=&#34;1.0&#34;&gt;<br /> &lt;dict&gt;<br /> &lt;key&gt;AllowNetworkAccess&lt;/key&gt;<br /> &lt;true/&gt;<br /> &lt;key&gt;CFBundleDisplayName&lt;/key&gt;<br /> &lt;string&gt;AIM Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleIdentifier&lt;/key&gt;<br /> &lt;string&gt;com.aimfight.widget&lt;/string&gt;<br /> &lt;key&gt;CFBundleName&lt;/key&gt;<br /> &lt;string&gt;AOL Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleShortVersionString&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CFBundleVersion&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CloseBoxInsetX&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;CloseBoxInsetY&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;MainHTML&lt;/key&gt;<br /> &lt;string&gt;fight.html&lt;/string&gt;<br /> &lt;/dict&gt;<br /> &lt;/plist&gt;</code></pre><br /> <br /> == AOL's Channel Content Modules - [[http://sports.aol.com|AOL Sports example]] ==<br /> <br /> * Each module (widget) has a markup envelope and some required elements that make it a module and allow for consistent styles across products.<br /> <br /> === Example ===<br /> <br /> <pre>&lt;div class=&#34;module themedList&#34;&gt;<br /> &lt;div class=&#34;header&#34;&gt;&lt;h3&gt;Kevin&#39;s List Of Fruit&lt;/h3&gt;&lt;/div&gt;<br /> &lt;div class=&#34;body&#34;&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Apples&lt;/li&gt;<br /> &lt;li&gt;Oranges&lt;/li&gt;<br /> &lt;/ul&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;</pre><br /> <br /> == Konfabulator ==<br /> <br /> * (need someone else to fill this in, have never built one or taken them apart)<br /> <br /> == WSRP ==<br /> <br /> * [[http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp|Homepage]]<br /> * SOAP envelopes to transport modules, but there is no specific formatting required for the actual content of the "portlet" (module or widget).<br /> <br /> === Module Response Example ===<br /> <br /> <pre>&lt;urn:getMarkupResponse xmlns:urn=&#34;urn:oasis:names:tc:wsrp:v1:types&#34;&gt;<br /> &lt;urn:markupContext&gt; <br /> &lt;urn:mimeType&gt;text/html; charset=UTF-8&lt;/urn:mimeType&gt;<br /> &lt;urn:markupString&gt;&lt;![CDATA[ <br /> &lt;form method=&#34;post&#34; <br /> action=&#34;wsrp_rewrite?wsrp-urlType=blockingAction/wsrp_rewrite&#34;<br /> id=&#34;wsrp_rewrite_stockForm&#34;&gt;<br /> &lt;table border=&#34;0&#34; width=&#34;100%&#34;&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;Enter Stock Symbol&lt;/td&gt;<br /> &lt;td&gt;&lt;input name=&#34;symbol&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;input type=&#34;submit&#34; value=&#34;Submit&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;/table&gt;<br /> &lt;/form&gt; <br /> ]]&gt;&lt;/urn:markupString&gt;<br /> &lt;urn:locale&gt;en-US&lt;/urn:locale&gt;<br /> &lt;urn:requiresUrlRewriting&gt;true&lt;/urn:requiresUrlRewriting&gt;<br /> &lt;urn:preferredTitle&gt;Portfolio Manager&lt;/urn:preferredTitle&gt;<br /> &lt;/urn:markupContext&gt; <br /> &lt;urn:sessionContext&gt; <br /> &lt;urn:sessionID&gt;sessionID_1&lt;/urn:sessionID&gt; <br /> &lt;urn:expires&gt;300&lt;/urn:expires&gt; <br /> &lt;/urn:sessionContext&gt; <br /> &lt;/urn:getMarkupResponse&gt;</pre></div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-examples&diff=1785 widget-examples 2005-09-27T16:01:20Z

<p>KevinLawver: /* WSRP */</p> <hr /> <div>== Apple's Dashboard ==<br /> <br /> * Uses an XML Manifest file to specify data about the "widget" (width, height, thumbnail image, title and version).<br /> * No requirements for markup around widgets.<br /> <br /> === Dashboard Example (plist) ===<br /> <br /> <pre><code>&lt;?xml version=&#34;1.0&#34; encoding=&#34;UTF-8&#34;?&gt;<br /> &lt;!DOCTYPE plist PUBLIC &#34;-//Apple Computer//DTD PLIST 1.0//EN&#34; &#34;http://www.apple.com/DTDs/PropertyList-1.0.dtd&#34;&gt;<br /> &lt;plist version=&#34;1.0&#34;&gt;<br /> &lt;dict&gt;<br /> &lt;key&gt;AllowNetworkAccess&lt;/key&gt;<br /> &lt;true/&gt;<br /> &lt;key&gt;CFBundleDisplayName&lt;/key&gt;<br /> &lt;string&gt;AIM Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleIdentifier&lt;/key&gt;<br /> &lt;string&gt;com.aimfight.widget&lt;/string&gt;<br /> &lt;key&gt;CFBundleName&lt;/key&gt;<br /> &lt;string&gt;AOL Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleShortVersionString&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CFBundleVersion&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CloseBoxInsetX&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;CloseBoxInsetY&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;MainHTML&lt;/key&gt;<br /> &lt;string&gt;fight.html&lt;/string&gt;<br /> &lt;/dict&gt;<br /> &lt;/plist&gt;</code></pre><br /> <br /> == AOL's Channel Content Modules - [[http://sports.aol.com|AOL Sports example]] ==<br /> <br /> * Each module (widget) has a markup envelope and some required elements that make it a module and allow for consistent styles across products.<br /> <br /> === Example ===<br /> <br /> <pre>&lt;div class=&#34;module themedList&#34;&gt;<br /> &lt;div class=&#34;header&#34;&gt;&lt;h3&gt;Kevin&#39;s List Of Fruit&lt;/h3&gt;&lt;/div&gt;<br /> &lt;div class=&#34;body&#34;&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Apples&lt;/li&gt;<br /> &lt;li&gt;Oranges&lt;/li&gt;<br /> &lt;/ul&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;</pre><br /> <br /> == Konfabulator ==<br /> <br /> * (need someone else to fill this in, have never built one or taken them apart)<br /> <br /> == WSRP ==<br /> <br /> * [[http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp|Homepage]]<br /> * SOAP envelopes to transport modules, but there is no specific formatting required for the actual content of the "portlet" (module or widget).<br /> <br /> === Example ===<br /> <br /> <pre>&lt;urn:getMarkupResponse xmlns:urn=&#34;urn:oasis:names:tc:wsrp:v1:types&#34;&gt;<br /> &lt;urn:markupContext&gt; <br /> &lt;urn:mimeType&gt;text/html; charset=UTF-8&lt;/urn:mimeType&gt;<br /> &lt;urn:markupString&gt;&lt;![CDATA[ <br /> &lt;form method=&#34;post&#34; <br /> action=&#34;wsrp_rewrite?wsrp-urlType=blockingAction/wsrp_rewrite&#34;<br /> id=&#34;wsrp_rewrite_stockForm&#34;&gt;<br /> &lt;table border=&#34;0&#34; width=&#34;100%&#34;&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;Enter Stock Symbol&lt;/td&gt;<br /> &lt;td&gt;&lt;input name=&#34;symbol&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;tr&gt;<br /> &lt;td&gt;&lt;input type=&#34;submit&#34; value=&#34;Submit&#34;&gt;&lt;/td&gt;<br /> &lt;/tr&gt; <br /> &lt;/table&gt;<br /> &lt;/form&gt; <br /> ]]&gt;&lt;/urn:markupString&gt;<br /> &lt;urn:locale&gt;en-US&lt;/urn:locale&gt;<br /> &lt;urn:requiresUrlRewriting&gt;true&lt;/urn:requiresUrlRewriting&gt;<br /> &lt;urn:preferredTitle&gt;Portfolio Manager&lt;/urn:preferredTitle&gt;<br /> &lt;/urn:markupContext&gt; <br /> &lt;urn:sessionContext&gt; <br /> &lt;urn:sessionID&gt;sessionID_1&lt;/urn:sessionID&gt; <br /> &lt;urn:expires&gt;300&lt;/urn:expires&gt; <br /> &lt;/urn:sessionContext&gt; <br /> &lt;/urn:getMarkupResponse&gt;</pre></div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-examples&diff=1784 widget-examples 2005-09-27T15:59:51Z

<p>KevinLawver: /* Example */</p> <hr /> <div>== Apple's Dashboard ==<br /> <br /> * Uses an XML Manifest file to specify data about the "widget" (width, height, thumbnail image, title and version).<br /> * No requirements for markup around widgets.<br /> <br /> === Dashboard Example (plist) ===<br /> <br /> <pre><code>&lt;?xml version=&#34;1.0&#34; encoding=&#34;UTF-8&#34;?&gt;<br /> &lt;!DOCTYPE plist PUBLIC &#34;-//Apple Computer//DTD PLIST 1.0//EN&#34; &#34;http://www.apple.com/DTDs/PropertyList-1.0.dtd&#34;&gt;<br /> &lt;plist version=&#34;1.0&#34;&gt;<br /> &lt;dict&gt;<br /> &lt;key&gt;AllowNetworkAccess&lt;/key&gt;<br /> &lt;true/&gt;<br /> &lt;key&gt;CFBundleDisplayName&lt;/key&gt;<br /> &lt;string&gt;AIM Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleIdentifier&lt;/key&gt;<br /> &lt;string&gt;com.aimfight.widget&lt;/string&gt;<br /> &lt;key&gt;CFBundleName&lt;/key&gt;<br /> &lt;string&gt;AOL Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleShortVersionString&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CFBundleVersion&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CloseBoxInsetX&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;CloseBoxInsetY&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;MainHTML&lt;/key&gt;<br /> &lt;string&gt;fight.html&lt;/string&gt;<br /> &lt;/dict&gt;<br /> &lt;/plist&gt;</code></pre><br /> <br /> == AOL's Channel Content Modules - [[http://sports.aol.com|AOL Sports example]] ==<br /> <br /> * Each module (widget) has a markup envelope and some required elements that make it a module and allow for consistent styles across products.<br /> <br /> === Example ===<br /> <br /> <pre>&lt;div class=&#34;module themedList&#34;&gt;<br /> &lt;div class=&#34;header&#34;&gt;&lt;h3&gt;Kevin&#39;s List Of Fruit&lt;/h3&gt;&lt;/div&gt;<br /> &lt;div class=&#34;body&#34;&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Apples&lt;/li&gt;<br /> &lt;li&gt;Oranges&lt;/li&gt;<br /> &lt;/ul&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;</pre><br /> <br /> == Konfabulator ==<br /> <br /> * (need someone else to fill this in, have never built one or taken them apart)<br /> <br /> == WSRP ==<br /> <br /> * SOAP envelopes to transport modules, but there is no specific formatting required for the actual content of the "portlet" (module or widget).</div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-examples&diff=1783 widget-examples 2005-09-27T15:59:32Z

<p>KevinLawver: /* Example */</p> <hr /> <div>== Apple's Dashboard ==<br /> <br /> * Uses an XML Manifest file to specify data about the "widget" (width, height, thumbnail image, title and version).<br /> * No requirements for markup around widgets.<br /> <br /> === Dashboard Example (plist) ===<br /> <br /> <pre><code>&lt;?xml version=&#34;1.0&#34; encoding=&#34;UTF-8&#34;?&gt;<br /> &lt;!DOCTYPE plist PUBLIC &#34;-//Apple Computer//DTD PLIST 1.0//EN&#34; &#34;http://www.apple.com/DTDs/PropertyList-1.0.dtd&#34;&gt;<br /> &lt;plist version=&#34;1.0&#34;&gt;<br /> &lt;dict&gt;<br /> &lt;key&gt;AllowNetworkAccess&lt;/key&gt;<br /> &lt;true/&gt;<br /> &lt;key&gt;CFBundleDisplayName&lt;/key&gt;<br /> &lt;string&gt;AIM Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleIdentifier&lt;/key&gt;<br /> &lt;string&gt;com.aimfight.widget&lt;/string&gt;<br /> &lt;key&gt;CFBundleName&lt;/key&gt;<br /> &lt;string&gt;AOL Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleShortVersionString&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CFBundleVersion&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CloseBoxInsetX&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;CloseBoxInsetY&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;MainHTML&lt;/key&gt;<br /> &lt;string&gt;fight.html&lt;/string&gt;<br /> &lt;/dict&gt;<br /> &lt;/plist&gt;</code></pre><br /> <br /> == AOL's Channel Content Modules - [[http://sports.aol.com|AOL Sports example]] ==<br /> <br /> * Each module (widget) has a markup envelope and some required elements that make it a module and allow for consistent styles across products.<br /> <br /> === Example ===<br /> <br /> <pre><code>&lt;div class=&#34;module themedList&#34;&gt;<br /> &lt;div class=&#34;header&#34;&gt;&lt;h3&gt;Kevin&#39;s List Of Fruit&lt;/h3&gt;&lt;/div&gt;<br /> &lt;div class=&#34;body&#34;&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Apples&lt;/li&gt;<br /> &lt;li&gt;Oranges&lt;/li&gt;<br /> &lt;/ul&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;</code></pre><br /> <br /> == Konfabulator ==<br /> <br /> * (need someone else to fill this in, have never built one or taken them apart)<br /> <br /> == WSRP ==<br /> <br /> * SOAP envelopes to transport modules, but there is no specific formatting required for the actual content of the "portlet" (module or widget).</div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-examples&diff=1782 widget-examples 2005-09-27T15:58:20Z

<p>KevinLawver: /* AOL's Channel Content Modules - AOL Sports example */</p> <hr /> <div>== Apple's Dashboard ==<br /> <br /> * Uses an XML Manifest file to specify data about the "widget" (width, height, thumbnail image, title and version).<br /> * No requirements for markup around widgets.<br /> <br /> === Dashboard Example (plist) ===<br /> <br /> <pre><code>&lt;?xml version=&#34;1.0&#34; encoding=&#34;UTF-8&#34;?&gt;<br /> &lt;!DOCTYPE plist PUBLIC &#34;-//Apple Computer//DTD PLIST 1.0//EN&#34; &#34;http://www.apple.com/DTDs/PropertyList-1.0.dtd&#34;&gt;<br /> &lt;plist version=&#34;1.0&#34;&gt;<br /> &lt;dict&gt;<br /> &lt;key&gt;AllowNetworkAccess&lt;/key&gt;<br /> &lt;true/&gt;<br /> &lt;key&gt;CFBundleDisplayName&lt;/key&gt;<br /> &lt;string&gt;AIM Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleIdentifier&lt;/key&gt;<br /> &lt;string&gt;com.aimfight.widget&lt;/string&gt;<br /> &lt;key&gt;CFBundleName&lt;/key&gt;<br /> &lt;string&gt;AOL Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleShortVersionString&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CFBundleVersion&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CloseBoxInsetX&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;CloseBoxInsetY&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;MainHTML&lt;/key&gt;<br /> &lt;string&gt;fight.html&lt;/string&gt;<br /> &lt;/dict&gt;<br /> &lt;/plist&gt;</code></pre><br /> <br /> == AOL's Channel Content Modules - [[http://sports.aol.com|AOL Sports example]] ==<br /> <br /> * Each module (widget) has a markup envelope and some required elements that make it a module and allow for consistent styles across products.<br /> <br /> === Example ===<br /> <br /> <nowiki><pre><code>&lt;div class=&#34;module themedList&#34;&gt;<br /> &lt;div class=&#34;header&#34;&gt;&lt;h3&gt;Kevin&#39;s List Of Fruit&lt;/h3&gt;&lt;/div&gt;<br /> &lt;div class=&#34;body&#34;&gt;<br /> &lt;ul&gt;<br /> &lt;li&gt;Apples&lt;/li&gt;<br /> &lt;li&gt;Oranges&lt;/li&gt;<br /> &lt;/ul&gt;<br /> &lt;/div&gt;<br /> &lt;/div&gt;</code></pre></nowiki><br /> <br /> == Konfabulator ==<br /> <br /> * (need someone else to fill this in, have never built one or taken them apart)<br /> <br /> == WSRP ==<br /> <br /> * SOAP envelopes to transport modules, but there is no specific formatting required for the actual content of the "portlet" (module or widget).</div>

KevinLawver https://microformats.org/wiki/index.php?title=widget-examples&diff=1781 widget-examples 2005-09-27T15:56:32Z

<p>KevinLawver: /* Apple's Dashboard */</p> <hr /> <div>== Apple's Dashboard ==<br /> <br /> * Uses an XML Manifest file to specify data about the "widget" (width, height, thumbnail image, title and version).<br /> * No requirements for markup around widgets.<br /> <br /> === Dashboard Example (plist) ===<br /> <br /> <pre><code>&lt;?xml version=&#34;1.0&#34; encoding=&#34;UTF-8&#34;?&gt;<br /> &lt;!DOCTYPE plist PUBLIC &#34;-//Apple Computer//DTD PLIST 1.0//EN&#34; &#34;http://www.apple.com/DTDs/PropertyList-1.0.dtd&#34;&gt;<br /> &lt;plist version=&#34;1.0&#34;&gt;<br /> &lt;dict&gt;<br /> &lt;key&gt;AllowNetworkAccess&lt;/key&gt;<br /> &lt;true/&gt;<br /> &lt;key&gt;CFBundleDisplayName&lt;/key&gt;<br /> &lt;string&gt;AIM Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleIdentifier&lt;/key&gt;<br /> &lt;string&gt;com.aimfight.widget&lt;/string&gt;<br /> &lt;key&gt;CFBundleName&lt;/key&gt;<br /> &lt;string&gt;AOL Fighter&lt;/string&gt;<br /> &lt;key&gt;CFBundleShortVersionString&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CFBundleVersion&lt;/key&gt;<br /> &lt;string&gt;2.0&lt;/string&gt;<br /> &lt;key&gt;CloseBoxInsetX&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;CloseBoxInsetY&lt;/key&gt;<br /> &lt;integer&gt;5&lt;/integer&gt;<br /> &lt;key&gt;MainHTML&lt;/key&gt;<br /> &lt;string&gt;fight.html&lt;/string&gt;<br /> &lt;/dict&gt;<br /> &lt;/plist&gt;</code></pre><br /> <br /> == AOL's Channel Content Modules - [[http://sports.aol.com|AOL Sports example]] ==<br /> <br /> * Each module (widget) has a markup envelope and some required elements that make it a module and allow for consistent styles across products.<br /> <br /> == Konfabulator ==<br /> <br /> * (need someone else to fill this in, have never built one or taken them apart)<br /> <br /> == WSRP ==<br /> <br /> * SOAP envelopes to transport modules, but there is no specific formatting required for the actual content of the "portlet" (module or widget).</div>

KevinLawver