Microformats Wiki - User contributions [en]

trade-examples

2007-08-24T21:24:19Z

ClayNewton: /* Trade Examples */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

:The first part of this page (up to the examples) may fit better on a page simply named "trade". [[User:Lastorset|Leif Arne Storset]] 11:40, 17 Aug 2007 (PDT)

__TOC__

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

=== Example ===

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]
* [[Lkonkiel | Lyle Konkiel]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* All of which create collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===
[http://www.ing.com ING]

enter notes here

=== Amazon.com ===
[http://www.amazon.com Amazon.com]

enter notes here

=== eBay ===
[http://www.ebay.com Ebay]

enter notes here

=== Paypal ===
[http://www.paypal.com Paypal]

enter notes here

=== Quicken ===
[http://www.quicken.com Quicken]
==== Deposits Accounts ====
* post date (PostDt)
* transaction description (TrDesc)
* transaction amount (TrAmt)
* type (TT)
* running balance (RunningBal)

'''Markup:'''
<pre><nowiki><Item>
<PostDt>12/27/2005</PostDt>
<TrDesc>FIREWOOD CAFE-METREON 12/22 CARD #0265 PURCHASE #24388945357670320615609 SAN FRANCISCO, CA</TrDesc>
<TrAmt>-$10.95</TrAmt>
<TT>D</TT>
<RunningBal>$2,916.63</RunningBal>
</Item></nowiki></pre>

=== Quickbooks ===
enter notes here

=== Wesabe ===
[http://www.wesabe.com Wesabe]
<pre><nowiki>
<div id="TRANSACTION-ID" class="txaction_display" >
<div class="merchant_info">
<div class="date"> Friday, March 23rd </div>
<div class="merchant" id="TRANSACTION-ID">
<span class="name"><a href="MERCH-ID">Mojo JOJO</a></span>
<div class="tags">
<span class="rating_text">Rating: <span class="user">User</span></span>
Tags: <a href="TAG-URL">groceries</a>
</div>
</div>
</div>
<div class="balance">
<span class="credit">$988.56</span>
</div>
<div class="amount">
<span class="nowrap">-$7.56</span>
</div>
</div>
</nowiki></pre>

=== Yodlee ===
enter notes here

=== Paper Check Example===
Hard copy

==== Consumer Account ====
* Account Holder
** Name
** Street Address 1
** Street Address 2
** City
** State Abbr
** Zip
** Phone [optional]
** ID [optional]
* Issuing Bank
** Org Name
** Branch Name
** Branch Street Address 1
** Branch Street Address 2
** City
** State Abbr
** Zip
** Phone
* Check Front
** Check Metadata
*** Check Number
*** Checking Account Number
*** Routing Number
** Date
** Pay to the Order of
** Amount [$]
** Amount [dollars desc]
** For
** Signature
* Check Back
** Endorsement

== See Also ==
* [[trade-brainstorming | Brainstorming trade]]

to-do

2007-08-07T04:10:01Z

ClayNewton:

<h1>To Do</h1>

This page is for posting [[microformats]] related shared to do items. If you want to use this page for your microformats related to-do items, create a section with your name on it. The reason we are keeping these all on the same page is to make it easier to tell when people are working on similar things, and to make it more obvious when people help out with other people's tasks. In theory this probably won't scale, but let's first see how it does in practice. :) - [http://tantek.com Tantek]

__TOC__

== Lazyweb ==

Just some nice things, feel free to do any of these.

=== for all microformats ===
* We have recently added a new mailing list called microformats-new. There may be some confusion surrounding this change, so it would be helpful to:
** Draft a message to be added to the confirm message sent when someone subscribes to any list including a welcome message, ground rules, topic for the subscribed list, and the topics for nearby lists.
** Add a faq entry somewhere on why the new list was created.
** Double check the wiki pages to make sure advice on mailing lists is accurate.
* quick and easy "how to" pages for each microformat. [[use]] is a good overall start.
* brief summary statements for each microformat that explain why it matters, what does it accomplish for the publisher.
* write up [http://microformats.org/discuss/ mailing-list] questions and answers in the appropriate [[faq]] pages.
* validators. See the hReview section below as there has been a request for an hReview validator in particular. See [http://norman.walsh.name/2006/04/13/validatingMicroformats Norman Walsh's blog post "Validating microformats"] for some valuable analysis and validation pseudo-code (prose description), which are useful steps towards building microformat validators.
* Add [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to Microformats Blog.
* Submit definitions of "mcroformat", and individual examples, to the [http://foldoc.org Free On-line Dictionary of Computing], acording to [http://foldoc.org/editing.html the Free On-line Dictionary of Computing guidelines]

=== hCard ===
* microformatted versions of conference pages
** Wait for confirmation from O'Reilly webmaster on revision of the [http://conferences.oreillynet.com/etel2006/ ETel] [http://conferences.oreillynet.com/pub/w/44/speakers.html speaker's page] with all the speakers marked up with [[hcard|hCard]] and links to "Add hCards to Address Book" etc., similar to the [http://tantek.com/microformats/2005/web2/speakers.html Web 2.0 speakers page which Tantek did a revision of last fall].
* vcard to hcard converter
** would be nice to have a web upload UI that would take one or more vCards from apple's address book and give them back to you as hCards
** [[User:RobertBachmann | RobertBachmann]] suggests starting points:
*** For Ruby: http://vpim.rubyforge.org/
*** For C: http://freshmeat.net/projects/libvc/
*** For Python: http://www.nongnu.org/python-pdi/
*** For PHP: http://pear.php.net/package/Contact_Vcard_Parse/
* add export support for microformats to [http://www.turingart.com/abForWeb_lan__en.htm AB to Web]
* A mash-up with google maps that will take any url with a hcard (or hcard's) and map the location(s) on a map (similar to [http://austin.adactio.com/ austin.adactio.com])

=== hCalendar ===
==== Add support to open source calendar projects ====
These are open source projects that could be potentially enhanced to support hCalendar.

* [http://www.k5n.us/webcalendar.php?topic=About WebCalendar]
* [http://phpicalendar.net/documentation/index.php?title=Main_Page PHP iCalendar]
* [http://www.vcalendar.org VCalendar]
* Investigation: [http://wiki.mozilla.org/Calendar_Talk:Lightning#hCalendar_publish_and_subscribe_support Mozilla Calendar / Lightning / Sunbird hCalendar support discussion]

=== hReview ===
* [[hreview|hReview]] support in Ecto (hey Adriaan!), requested by Andy Smith
* an [[hreview|hReview]] validator.
* a semantic, clean css star rating picker (e.g. a UI widget to rate from 1-5 stars)
** both [http://komodomedia.com/blog/index.php/2005/08/24/creating-a-star-rater-using-css/ this] and [http://factorycity.net/demos/drupal/rating/default.html this] have some flaws. Ask [[User:RyanKing|Ryan King]] for an explanation.

=== hCalendar/hCard/hReview editor ===
* onblur in the URL field (e.g. on hCalendar), goes out and tries to retrieve an object of same time (e.g. an hCalendar vevent) from that URL and uses it to autofill the form, same thing if the creator is loaded with that URL prefilled (e.g. due to a ?url=http://example.com/ in the URL that loads the creator).

=== WordPress patches for microformats ===
* submit patches for WordPress code/templates for microformats improvement
** <address class="vcard"> improvement in post author publication (e.g. home page of http://microformats.org/ )
* Wordpress plugin for microformats, specifically hReview and hCalendar
** See [http://www.surfarama.com/index.php?p=227 lazyweb request]

=== Yahoo Open Source Library Patches ===
Several of these could very much be improved with a little microformats markup. Do we just make patches and submit them? Contact Nate Koechley at Yahoo (see Tantek for contact info) to follow-up.

* [http://developer.yahoo.net/yui/ Yahoo! User Interface Library]
* [http://developer.yahoo.net/ypatterns/ Yahoo! Design Patterns Library]
* [http://www.yuiblog.com Yahoo! User Interface Blog]

=== Drupal patches for microformats ===
* [http://groups.drupal.org/microformats-in-drupal Microformat Module for Drupal] A group discussing ways to implement microformats in Drupal. Currently looking to support hAtom, hCard and hCalendar to start with. Contact digitalspaghetti at gmail dot com if you are interested in contributing to the project.

=== Adding Microformats to Existing Pages ===
* See [[advocacy#Adding_Microformats_to_Existing_Sites|advocacy: Adding microformats to existing sites]].

===rel-tagging on Wikipedia===
Somebody familiar with the "rel-tag" microformat might want to add details, and a link to the relevant page on this Wiki, to the [http://en.wikipedia.org/wiki/Tag_%28metadata%29 Wikipedia page on tagging]. [[User:AndyMabbett|Andy Mabbett]] 14:07, 3 Jan 2007 (PST)

== Admins ==
This section is for any admins to keep track of current to-do items for admins and/or for folks to suggest to-do items for admins, in particular, having to do with suggestions for improvements to microformats.org infrastructure such as the wiki. If you do add an item to this list, please sign your username with four tildas: <nowiki>~~~~</nowiki>.

=== Wiki improvements ===
* OpenID login, on behalf of a request a while ago from [[User:DanC]]. [[User:Tantek|Tantek]] 20:50, 20 Jul 2007 (PDT)
* Install creation template extension(s)(see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle) [[User:RobManson]] 14:00, 20 Jul 2007 (AEST)

== Tantek ==
I'm keeping a few microformats related to-do items here both for my own convenience, and for folks looking to help out with small tasks. If so, just create a new section with your name, and and maybe copy the item there, and put your name next to the item in my list. We'll figure this out as we go along. Thanks, [http://tantek.com Tantek].

=== overall priority ordering ===
# Protect the community from threats (wiki damage, mailing list pain or noise), repair damage, add measures to reduce future damage
# Help publishers with established microformats: [[hcard|hCard]], [[xfn]], [[rel-tag]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]
# Help implementers with established microformats
# Iterate on existing established microformats, resolve issues/feedback etc.
# Wiki cleanup/gardening for existing established microformats
# Site usability of microformats.org top-down as an entry point
# Community dynamics, [[process]] and [[principles]] improvements to help guide new microformats developments
# Emerging in-demand microformats: [[hresume|hResume]], [[hlisting|hListing]], [[citation]], [[media-info]] using abovementioned process and principles improvements.
# New microformat requests
# Document microformats [[history]].
# Other

=== protect the community ===
* Analyze [[Special:Recentchanges]] and [http://microformats.org/discuss mailing-lists] and:
** add to [[mailing-lists]] policies/guidelines accordingly.
** redirect and resolve threads accordingly per guidelines
** privately email violaters kindly asking them to improve their behavior
** work with admins on next steps for individuals negatively impacting the community
** recognize noisy/distracting threads on the email list, document responses/answers to such subjects on the appropriate page(s) on the wiki, and reply to those threads with the URLs to the documentation on the wiki. Putting the responses/answers on the wiki helps by hopefully providing preemptive answers to some who might reraise the subjects on the list in the future, and helps the community quickly terminate such threads by using the answers on the wiki.

=== help publishers ===
==== social network portability ====
Iterate on:
* [[social-network-portability]]
* [[hcard-supporting-user-profiles]]
* [[hcard-xfn-supporting-friends-lists]]

Brainstorm updates to the [[pocket-cheat-sheet]] to better enable [[social-network-portability]], or perhaps design a new '''social network portability pocket cheat sheet''' that specifically documents:
* how to author/publish hCard user profiles - write this up in [[hcard-authoring]] first (see below) and then use that content.
* how to author/publish hCard+XFN friends lists - write this up in [[hcard-xfn-authoring]] (see below) and then use that content.
* how to parse/subscribe to hCard user profiles - write this up by updating: [[hcard-parsing]], and writing [[hcard-supporting-user-profile-parsing]] (collect this into parsing/developers tasks below)
* how to parse/subscribe to hCard+XFN friends lists - write this up by writing: [[xfn-parsing]], [[hcard-xfn-supporting-friends-list-parsing]] (collect these into parsing/developers tasks below)
** notes/thoughts on hCard+XFN supporting friends list parsing captured here for now:
*** do a full rel="me" bidirectional crawling within the domain - some sites' hCard supporting user profiles simply link to their hCard+XFN supporting friends lists with rel="me", and thus you will discover more pages with friends lists.
**** E.g. Flickr's /people/username pages have hCard for the user and link to their /people/username/contacts page with rel="me" (on the "More..." link, though they could also add rel="me" to the number inside "Your contacts (592)"). Need to get them to support hCard+XFN on the contacts themselves.
*** consider parsing within a friends list page, any links that are rel="next" and rel="prev" to iterate over the whole list.

==== foldup cheatsheet ====
'''next actions''':
* gather feedback on current foldup [[pocket-cheat-sheet|pocket cheatsheet]]
* document the [[pocket-cheat-sheet-feedback|feedback on the pocket cheatsheet]]
* give feedback to Erin, iterate, print more to have on hand, fold, distribute.
* provide printing recommendations for anyone to download and print their own
** Perhaps [http://www.visibone.com/ Visibone] can be of some use? I can recommend their current products. --[[User:Gazza|Gazza]] 06:41, 7 Apr 2007 (PDT)

==== *-authoring microformats wiki pages ====
* [[hcard-authoring]] - '''next-actions''': add tips/instructions noted below.
** instructions for each property that is in [http://microformats.org/code/hcard/creator hCard creator] to begin with
** instructions for all other hCard properties
** a tutorial on creating an hCard for your site
*** specific instructions for common blogging platforms
** reference [[hcard-examples]] for more specific uses, and add to them accordingly
*** add an extended example to [[hcard-examples#Authors_of_Pages_and_Posts|contact info for a page]] with postal address, phone numbers, email address.
* [[hcard-xfn-authoring]] - '''next-action''': draft by starting from hCard+XFN instructions in [[hcard-examples]].
* [[hreview-authoring]] - '''next-action''': create a first draft minimal tutorial on how to author hReviews (e.g. at least for common properties) to blog reviews so that they'll be aggregated.
* [[hcalendar-authoring]] - '''next-action''': add tips/instructions for each property that is in [http://microformats.org/code/hcalendar/creator hCalendar creator].
* *-authoring for other reasonably well established microformats:
** [[xfolk-authoring]], [[hatom-authoring]]

==== help with microformat examples in the wild ====
Using the above updated [[authoring]] pages, get the community to help go over all "common" pages (both logged out and logged in states) of the following sites which have some microformats already, and verify each page is as microformatted as it can be with high fidelity [[hcalendar|hCalendar]] and [[hcard|hCard]] etc. Document full support of each implementation's microformats on the implementations page (perhaps create a separate page for each implementation, e.g. [[flickr]], [[upcoming]], [[eventful]] etc.) Document any exceptions as needed. In no particular order:
* Flickr.com (3.5m hCards)
* Upcoming.org (100k hCalendar events, 100k hCard venues)
** home page
* Eventful.com (100k hCalendar events, 100k hCard venues)
* Yahoo! Tech (300k products with hReviews)
* JudysBook.com (???k hReviews)
* ... lots more, get from "Implementations" and "Examples in the Wild" sections of specs.

==== advocacy for obvious sites ====
* [[advocacy]] - add pages/sites that obviously (no pun intended) could use microformats, update them with sample markup, find contacts for those pages to get them updated, and send requests to update their sites with microformats including sample markup. '''next-actions''': markup both twitter.com sample pages and dodgeball.com sample pages, post the changes publicly, and see which one is able to update first ;)
** dodgeball.com (hCard + XFN + hAtom for profiles, hCard + hReview for venues)
** write essay on [[open-data-more-important-than-open-source]] - and a shorthand URL too.
*** obviously doing both is ideal, however, open data is a higher priority and given limited resources, open data should be implemented before open source.
*** open data > open source
*** "open information" vs "open source"
*** i.e. please focus first on open data rather than open source, e.g. start with [[hcard|hCards]] for all organizations returned from http://wiserearth.org/organization
*** if the data is open you can always export it and consume it in any number of open source systems
*** that's why open data is MUCH more important than open source
*** adding open data (e.g. microformats) can be done by any HTML author (yes, you), whereas open sourcing requires programming expertise, resouces, support. do the simpler easier thing first (open data thru microformats) that will benefit more people sooner.
*** if the data was open, anyone could rebuild an accessible version
*** faqs / misconceptions:
**** eschipul: @tantek - creating microformats is easier. consuming microformats is unfortunately not easier.
***** A: If you think consuming microformats is not easier or hard etc., it may just be that you don't know how to do so easily, don't assume that you are an expert in something that you think is hard. Rather, if you think something is hard, then assume others may know easier methods, and ''ask'' the community how one can do it more easily. parsing in particular is something which is becoming easier and easier thanks to open source libraries like [[hkit|hKit]].
** write essay on [[open-data-more-important-than-open-apis]] - and a shorthand URL too
*** obviously doing both is ideal, however, open data is a higher priority and given limited resources, open data should be implemented before open APIs.
*** publishing/providing open data (e.g. microformats) can be done by any HTML author (yes, you), whereas providing/publishing open APIs requires programming expertise, resouces, and support. do the simpler easier thing first (open data thru microformats) that will benefit more people sooner.

=== help implementers ===
* wordpress improvements
** WP admin for new profiles
*** should simply read blog URL - '''next-action''': make sure a bug/feature request is filed with wordpress.org
*** look for hcards and parse them

* [http://gmpg.org/xfn/creator XFN Creator] localizations
** Get someone to verify the [http://gmpg.org/xfn/creator-ru XFN Creator Russian localization].
** Add it to the [http://gmpg.org/xfn/tools XFN Tools] page.
** Add rel="alternate" href="creator-ru" <link>s to the other XFN Creators.

* Conference Schedule Creator
** '''next-actions''': Review Dmitry Baranovskiy's [http://dmitry.baranovskiy.com/work/csc/ Conference Schedule Creator] and give him feedback per how well it:
*** Makes it *trivial* for conference organizers to build/edit/publish an [[hcalendar|hCalendar]] schedule for their conference, including auto-generated "Subscribe..." link which produces the proper "webcal:..." link with X2V. Note: see the "axis" and "header" attributes in HTML4, specifically in the section on Tables.

=== iterate on current microformats ===
==== [[hcard|hCard]] ====
Combined next-actions for iteration on [[hcard|hCard]], and derived/subsetted microformats [[adr]] and [[geo]]
* [[hcard-examples]] '''next-actions''': update with examples described below
** add examples of [[hcard|hCard]]s with work telephone, mailing address etc.
** add examples of marking up an organization vs. a person, then link to it from [http://microformats.org/wiki/hcard#Organization_Contact_Info hCard spec section on Organization Contact Info].
** add example of organization-name and organization-unit usage.
* [[hcard-issues]] and [[hcard-feedback]]. '''next-actions''': resolve all issues and incorporate all feedback.
* [[hcard-brainstorming]] '''next-actions''': determine which brainstorms proposals to resolve in April, and which later
** need property for gender (see [[hcard-faq#How_is_gender_represented|proposal in hCard FAQ]] and discussion in [[hcard-issues]]) - use tags for now, add to hCard creator
** solve [[hcard-brainstorming#Auto-Discovery|autodiscovery]] of more canonical/thorough hCard
* [[hcard-examples-in-wild]]
** help dglazkov markup: http://glazkov.com/blog/archive/2003/12/17/147.aspx
* analyze [[hcard-cheatsheet]], [[adr-cheatsheet]], [[geo-cheatsheet]] for any assertions above and beyond what the specification itself says, take into account [[hcard-brainstorming]] along similar lines, and incorporate into the spec or remove as necessary and sync-up as a result. add clarification on the cheatsheets that they are '''informative''' and reference the specification for normative requirements.

==== [[hcalendar|hCalendar]] ====
'''Next-actions''':
* itemize a list of properties similar to the [[hcard#Property_List|hCard property list]], drawing upon hCalendar experience, iCal-BASIC draft(s), ietf-calsify mailing list and other sources to derive the precise list.
* formalize [http://microformats.org/wiki/hcalendar- brainstorming#Tabular_event_calendars]
* flesh out [[hcalendar-examples]] and do a once over on markup/presentation of what RFC2445 examples would look like
* need spec details and then [[hcalendar-examples]] of multi-instance [[hcalendar|hCalendar]] events
* need spec details and then [[hcalendar-examples]] of repeating events
* add explicit explanation and examples for LOCATION [[hcard|hCards]] and ATTENDEE [[hcard|hCards]], perhaps on a separate [[hcalendar-examples]] page.
* need to resolve all outstanding [[hcalendar-issues]] to-do items.
* create [[hcalendar-profile]] and have folks verify it. Note that it will likely need reconciliation with the [[hcard-profile]], especially since [[hcalendar|hCalendar]] normatively depends on [[hcard|hCard]]. Probably makes sense to have a combined profile which hCalendar would use.
* analyze [[hcalendar-cheatsheet]] for any assertions above and beyond what the specification itself says, take into account [[hcalendar-brainstorming]] along similar lines, and incorporate into the spec or remove as necessary and sync-up as a result. add clarification on the cheatsheets that they are '''informative''' and reference the specification for normative requirements.

==== [[hreview|hReview]] ====
'''Next-actions''':
* Write hReview 0.3 XMDP profile, and reconcile with [[hcalendar-profile]] and [[hcard-profile]]. Makes sense to have a combined profile of all three for hReview, since hReview normatively depends on hCard and hCalendar.
* Resolve all outstanding [[hreview-issues]] and [[hreview-feedback]] to-do items.

==== [[rel-tag]] ====
'''Next-actions''':
* Write [[rel-tag]] XMDP profile ([[rel-tag-profile]]) and send to [http://dbaron.org/ David Baron].
* Resolve all outstanding [[rel-tag-issues]] and [[rel-tag-feedback]] to-do items.

==== summary Examples in the Wild page ====
* need to create a summary / overall [[examples-in-the-wild]] page
** parallel the summary/overall [[implementations]] page.
** use newly reoganized content from the above "reoganizing Examples in the Wild" task

==== parsing ====
'''Next-actions''':
* Draft *-parsing for all reasonably well adopted microformats: [[hcalendar-parsing]], [[hreview-parsing]], [[xfolk-parsing]], [[hatom-parsing]]

=== wiki cleanup ===
==== for all microformat specs ====
'''Next-actions''':
* modularize any specs which are > 30K in order to avoid loss/corruption like [http://microformats.org/wiki?title=Special:Contributions&target=Evan Evan's 14 June edits] to [[hcard|hCard]], [[rel-tag]], and [[xoxo|XOXO]].
** [[hcard|hCard]] -
*** [[hcard-examples-in-the-wild]] group/sort by individuals, organizations, and hosting sites. Consider moving largest subsection to its own page as well.
** [[rel-tag]]
** [[xoxo]]

==== update specification section organization ====
'''Next-action''': work with Ryan, Ernie, Erin, and others who have made concrete helpful suggestions for reorganizing the information architecture / content-order / layout of specs for greater approachability/readability by a broader audience, to design an interative update to spec organizations, in particular, the introduction/boilerplate/headers. See below notes on hResume experiment in progress.

[[hresume|hResume]] has an experimental abbreviated intro/headers section, and links to more details further below, based on some ideas that Ryan King and I had for improving the readability of the microformats specifications. [[hreview|hReview]] has some similar improvements, but different. We need to:
# Figure out if the new intro/headers structure in [[hresume|hResume]] and/or [[hreview|hReview]] is an improvement, and if it could be better. Perhaps figure out the requirements for an intro/header section
#* Shorter tends to be better
#* Must be comprehensive enough to "print and read"
#* Must detail authorship/editorship
#* Must detail copyright/patent statements
# Write up a template - make it self-documenting per the requirements
# Update existing specifications with the new intro/headers structure.
## [[hcard|hCard]]
## [[hcalendar|hCalendar]]
## [[hreview|hReview]]

==== reorganizing Implementations sections ====
* sort implementations by authoring/creating/publishing, browsing/viewing, converting/importing, indexing/searching.

Hmmm... I like: '''A'''uthoring, '''B'''rowsing, '''C'''onverting, '''I'''ndexing, '''L'''ibraries (for developers), and '''P'''otential (for open source projects we want to add support to). Anybody have alternative suggestions for this vocabulary? I don't have a particularly strong preference so I'm going to go with these four until I find examples that don't fit, or someone suggests something better.

See: [http://microformats.org/wiki/hcalendar#Implementations hCalendar Implementations] for a first attempt at this. Assuming folks like that, we can go ahead with categorizing the implementations sections of other microformats specifications.

'''Next-actions''':
* [[hcard-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
* [[hreview-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
* [[hatom-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].
* [[xfolk-implementations]] - re-organize by same subsections as [[hcalendar-implementations]].

==== reorg Examples in the Wild sections ====
Work with community to:
* include more *key* details per example, e.g. precise or estimates of counts for services
* collate/sort examples in the wild by
** hosting services - where users/people actively contribute to the growth (e.g. Flickr profile hCards)
** publishing services - where lots of data is published from some datasource/database (e.g. Yahoo! Local)
** companies/groups/organizations member pages (and their own) - pages for a group's site where they list members or employees (e.g. Technorati staff page)
** individiual companies/organizations contact info pages
** individual people's contact info pages
* of course at some point this won't scale, but that will be a very good problem to have, and by then I'm sure we'll have services to point to that provide queries and search results for all this data.

=== site usability ===
* figure out how to get wordpress to autopost blog posts to the microformats-announce list
** ideally use the from address of the author of the blog post
** maybe photomatt knows how to do this.

=== introduction / community ===

* microformats-discuss *
** introductory email template for new subscribers needs to direct people to [[process]] and [[how-to-play]]
* Need to add more to the [[naming-principles]], to cover in particular:
** avoid using the same name to mean two things
** avoid using two names to mean the same thing
** seek to keep the microformats vocabulary minimal, memorable, and usable.
* update and add details/simplifications to [[process]] given the past several months of experience. in particular:
** clarify requirement (MUST rather than SHOULD) of *-examples, *-formats, before any *-brainstorming.
** Add details of encouragement to experiment with simple semantic class names from *-brainstorming proposals to gain real world experience with real world content.
** note SHOULD prerequisite of use of all relevant microformats on real world web pages, along with documenting such use in respective "Examples in the Wild" sections, before proposing any new microformats.

==== posh improvement ====
* Create a page to answer the question "[[how-should-i-markup]]"
* consider creating a process/encouragement for collecting individual [[posh]] practices and examples, like a folksonomy of semantic HTML and semantic class names.

==== principles and process ====
Create the following pages and document/fill them with content from other pages, email lists, and [[presentations]].
* [[principles]] - mostly [[microformats#the_microformats_principles|documented in the microformats]] page.
* clearer statement of both copyright and patents both in specific specs and in general

==== profiles ====
* update [[XMDP]] with new required features:
** ability for one profile to include/import another (rel="import" ?)
** ability to reference an XMDP via rel="profile" (similar to XHTML2 rel value by same name)
*** add rel="profile" to the [[xmdp-profile]].
** ability/suggestion to reference an XMDP using <a href> in addition to <link>

==== community mark ====
* Can we make "microformat" and "microformats" into [http://factoryjoe.com/blog/2006/01/14/the-case-for-community-marks/ Community Marks]?

==== document issue resolutions ====
* Prefixing has already been considered and rejected for microformats in general. Note [[naming-conventions]], limited vocabulary, and exceptions made for [[hatom|hAtom]] and how we went about doing so.

=== emerging microformats ===
* [[directions]]
* [[citation]]
* [[hlisting|hListing]]
* [[media-info]]
* [[licensing]]
'''Next-actions''' for each emerging microformat (one at a time)
* review all microformats-email on the new microformat
* determine where new microformats is "stuck" in the process
* brainstorm about how to improve process (or documentation thereof) to get the effort unstuck
* work with community to move the microformat forward through the process, iterating/clarifying the [[process]] as necessary

=== new microformat requests ===
* expense reports (really just a list of "expense" items), [http://flickr.com/photos/edyson/56774178/ requested by ED], should look at UBL as a pre-existing format
* photo-notes microformat
** clean up Subethaedit notes from working session with Greg Elin, Ryan King, Kevin Marks, Suw Charman and email to folks and figure out next steps
** iterate on [[photo-note-examples]] and start [[photo-note-formats]] and [[photo-note-brainstorming]].

=== document microformats history ===
Document microformats [[history]], including:
* dates and origins of microformats, names, terms
* examples and formats for established microformats like [[hcard|hCard]], [[hcalendar|hCalendar]], [[xfn]], [[rel-license]], [[xoxo]]

=== other ===
* Add XPath equivalents where appropriate in [[hcard-parsing]]

==Ryan==
=== wiki cleanup ===
* possibly move dead proposals off of homepage?

=== hCalendar/hCard/hReview creator improvements ===
* get all creators working in IE/Win, IE/Mac, Safari/OSX.3

=== other ===
* add an example of how to use DURATION in hcalendar see http://www.policyawareweb.org/2005/ftf2/paw-mtg#item15) -> verify http://svn.lifelint.com/hcalendar_tests/calendar-todo-multiple-attendees-and-alarm.xml

=== rel-payment ===
* update rel-payment to reference the IANA registry [http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg02055.html]

=== hcalendar ===
* make sure we explicitly disallow 'vjournal'

== Dimitri Glazkov ==

* Figure out REST/Microformats thing
* Work on result set idea
* Implement h-creators using Web Forms 2.0

== Chris Messina ==

=== General ===

* Work on a microformat for play-lists (is it just a XOXO ordererd list of play-items?)
* Work on a microformat for play-item (take a look at [[media-info-examples]])
* Work on microformats tutorial for designers
* Add support for OpenID to micformats wiki
* Add support for [http://verselogic.net/projects/wordpress/wordpress-openid-plugin/ OpenID] to the microformats blog.
* Read GTD (at least the first two chapters).

=== Campaigns ===

* Get Blogger to support hAtom and hCard
* <strike>Get LinkedIn to support hCard, hResume, hCalendar</strike> and XFN
* Get XING to support <strike>hCard</strike>, hCalendar, hResume and XFN
* Get Digg to support microformats.

=== Wishlist ===

* Microformat for "buyable items" (see [[listing-examples]] and related documents)
* Location MF -- right click "map this" (see [[geo]] and [[adr]])
* Better hCard support in the browser -- right click "IM this person...", "Add to contacts" (see [http://factoryjoe.com/blog/2006/03/20/flocktails-for-flock/ Flocktails])
* Better hCal support -- support many views of same hCal data on one page using XSLT
* We need something that a designer/web programmer can come to and leave w/ 2 examples of each microformat that they can apply right away... a "microformats styleguide for designers", if you will.
* invoicing microformat
* better microformats wiki theme
* Define flow for OpenID + XFN + hcard

== Robert Bachmann ==
[[User:RobertBachmann|Robert Bachmann]]

=== XSLTs ===
<ul>
<li><strong>Test scripts</strong>
<ul>
<li>Do some refactoring, split Perl code into smaller modules</li>
<li>Provide test results as HTML pages (similar to http://www.w3.org/2003/08/owl-systems/test-results-out)</li>
<li>Provide some documentation for using the test scripts</li>
</ul>
</li>
<li><strong>hAtom2Atom</strong>
<ul>
<li>
Join all hfeed's inside a page (or a fragment thereof) into one feed using [http://greenbytes.de/tech/webdav/rfc4287.html#element.source atom:source] semantics.
</li>
<li>
Extraction of <code>atom:content</code>, <code>atom:summary</code> and <code>atom:title</code>:
* <code>atom:content</code> and <code>atom:summary</code> as HTML
* <code>atom:content</code> and <code>atom:summary</code> as plain-text
* <code>atom:title</code> as XHTML
* <code>atom:title</code> as HTML
</li>
<li>Support for other XSLT engines:
* .Net System.Xml
* hAtom2Atom written using XSL 2.0?
** Do you think this would be useful? I have created a barebones version, doesn't yet take in all the parsing rules yet, but I'd be happy to share. Moving to XSL 2.0 does make things a bit cleaner and more efficient. - Matt Dertinger.
</li>
<li>Support for other output formats: (hAtom2<i>xyz</i>.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl]) -- <i>+1 Matt Dertinger</i>
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt]) -- <i>+1 Matt Dertinger</i>
** My opinion at the moment, I neither want to produce nor to consume RSS. Atom is nicer (and should be supported by most good feed readers available today), RSS should fade away. -- Robert Bachmann
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])-- <i>+1 Matt Dertinger</i>
** Having the possibility of GRDDL-ing hAtom to AtomOWL seems definitly interessting. I realy should implement this some day. - Robert Bachmann
* JSON?
** Does it make sense to consider a canonical representation of microformats (either case by case, or in general) in JSON? E.g. so that a JSON API that returned contact information could return an hCard-equivalent chunk of JSON. - Tantek.
*** This could enable some nice JavaScript hacks. I should give hAtom2JSON a try. - Robert Bachmann
</li>
</ul>

([[User:Singpolyma|singpolyma]] 01:02, 9 May 2006 (PDT) -- Not XSLT, but see http://xoxotools.ning.com/hatom2rss.php for hatom to RSS2.0 conversion)
</li>
</ul>

== Brian Suda ==
=== Citation Microformats ===
* Add all my notes to the Wiki
* Start the process of naming the properties using existing names

=== X2V ===
Make changes and update site (almost stable)
Get ATTENDEE and other strange attributes working
==== WARNINGS and ERROR ====
work on the warnings and error output for the pre-check in X2V

=== FAQ ===
* clean-up the MF FAQs
* clean-up FAQs from the major microformats
* pull Questions from the mailing list and document them to the FAQs and example

=== Microformats History ===
* get early work from developer.technorati site
** issues with MoinMoin full history: http://moinmoin.wikiwikiweb.de/MoinMoinQuestions/UsingTheWiki#head-9d1b1d6beedde40b92cc6c13962b5a6f5b289d10

=== additions to the wiki ===

* better explain why NOT infinitely scaling is a good thing
* better explain why microformats do NOT use namespacing

== Mark Rickerby ==

=== Current Tasks ===

* Follow up on usability review
** Edits to homepage feature box text
** Draft of [[getting-started]] page
* Review content for new pages - [[start-simple]], [[modularity]], [[reuse]], [[humans-first]]
* xoxo datatype examples
** test case lists
** transmitting key/value lists
* practical feedback on hresume

=== Wishlist ===

* hmmm

== Ernest Prabhakar ==
=== Wiki-Thon Proposal ===
Set aside several hours (probably a Friday night US PST) for focused work on the Wiki, including both physical (e.g., a room in the Bay Area) and virtual (IRC/iChat) participants.

==== Goals ====
# Improve understanding of what needs to be done for Wiki
#* IMHO - this should be done here, in [[to-do]] incrementally. -Tantek
# Tackle larger projects (~1-2 hours) than people usually have time for
#* I'd like to see these projects *documented* first on [[to-do]] before we spend 1-2 hours of a bunch of folk's collective time to go through them. -Tantek
# Motivate community to have fun with otherwise tedious "housecleaning" chores

==== Agenda (Wishlist) ====
In parallel:
* Coalesce/prioritize existing To-Do items (above)
* Review/revise desired pathways for:
** New users learning about microformats
*** e.g., intro, about, explore, tutorials, etc.
*** cf. [http://www.rubyonrails.com/ Rails] front page
****Get Excited (Why, background, motivation)
****Get Started (What, downloads, getting started)
****Get Better (How, tutorials, )
****Get Involved (Who)
** Microformat lifecycle
*** e.g., research->brainstorm->proposal->spec->maintain
*** see http://theryanking.com/microformats/method.txt --[[User:RyanKing|RyanKing]] 15:35, 22 Feb 2006 (PST)
*** ensure information easy to find, follow, and up-to-date
* Review existing specs for completeness and consistency
* Identify areas of 'bitrot' or 'hole-filling'
* Do it!

== Dan Connolly ==

[[User:DanC|DanC]] hopes to sync up on these tasks in [[irc]] roughly
weekly, during Wednesday afternoon (Chicago time) "office hours". See also my [http://esw.w3.org/topic/DanConnolly esw todo list and someday pile].

* from SxSW in Austin
** build a combined hcalendar/hcard profile; resolve issues in [[profile-uris]].
*** with XSLT transformation to RDF
** finish [[hcard-tests]]
*** figure out [[include-pattern]] boundaries

* Medium term
** sync [[hcalendar-tests]] and [http://www.w3.org/2002/12/cal/ RDF calendar] tests and CALSIFY
*** reconsider RDF calendar naming conventions
** update my CV/resume using [[hResume]] and [[citation-formats]]
*** get an answer from the CALSIFY WG re [http://lists.w3.org/Archives/Public/www-rdf-calendar/2006Apr/0006.html dtstart and date vs datetime ] 21 Apr 2006
*** refine [[hatom]] so that it's suitable for the workflow around the W3C homepage.

* from WWW2006
** follow up on GRDDL as escape valve for microformats proposals, much like CSS was an escape valve for HTML tag proposals.

* Someday pile
** set up a timezone registry based on wikipedia and semantic mediawiki. As discussed in [[datetime-design-pattern]], iCalendar's by-value timezone passing is broken. see [http://lists.w3.org/Archives/Public/www-rdf-calendar/2006Apr/0002.html reconsidering timezones in light of hCalendar and CALSIFY] and [http://dig.csail.mit.edu/breadcrumbs/node/91 Toward Semantic Web data from Wikipedia]
** noodle on a playlist format and some of the media RSS stuff like [[media-info-brainstorming]], [[media-metadata-examples]] (re playlists: XSPF, SMIL, RDF, and microformats 9 Sep 2005)
** check out that hReview bug stuff...
** noodle on [[meeting-minutes-brainstorming]] and [http://esw.w3.org/topic/MeetingRecords MeetingRecords in the esw wiki].
** noodle on clipboard scenarios, esp how RDFa works in the general case but isn't as author-friendly as domain-specific syntaxes.

[[User:DanC|DanC]] 15:39, 31 May 2006 (PDT)

== Chris Casciano ==

[[User:ChrisCasciano|ChrisCasciano]]

* get around to updating [[hatom-issues]] with some multi feed rules/exceptions.
* <del>Update textpattern plugin with simple hreview support and get a new release out</del>
* Redesign placenamehere.com and include hatom
* Follow up with technorati folks on pingerati reviews getting lost (note: this will require publishing more reviews and theen watching them through the update process)
* <del>prototype a NetNewsWire microformat extractor (CSS+AppleScript)</del>

== Drew McLellan ==

[[User:DrewMcLellan|DrewMcLellan]]

* Build an hReview profile for [http://allinthehead.com/hkit/ hKit] and test
* Update the [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver extensions] to mirror recent changes in the online builders
* <del>Publish an hCard to JSON service on [http://tools.microformatic.com/ tools.microformatic.com] using hKit.</del>
* Further develop blog comment form hCard collection ideas.
* Version of hReview creator using hKit to import business details from an hCard

== Christophe Ducamp (french localization) ==

[[Christophe Ducamp]]
* seed "microformateurs group" and invite them to update http://microformateurs.org
** write a process for newbies in order to make them write [[posh-fr|CHIC]] posts on a public blog-governed-by-wiki ([http://socialsynergyweb.net/cgi-bin/wiki/MicroFormateurs/Blog]) before publication.
** find experts for peer-reviewing
** find french CSS gurus to setup a nice Sandbox-CSS template on Wordpress
* translating the wiki
** translate red links on [[Main_Page-fr]] and synchronize
** find out microformateurs at ease on "the-wiki-way-translation", and ready to help on semi-anonymous-synchro
* community-marketing -> pinko-marketing
** public-relations towards french journalists and complete [[advocacy-fr|advocacy]] (especially [[hcard-advocacy-fr]] towards organizations.
** help to build events, workshops like barcamps and explorcamps
** update [http://fr.wikipedia.org/wiki/Microformats French-wikipedia:Microformats] and subpages via cowriting [http://fr.wikipedia.org/wiki/Discuter:Microformats on discussion page] (directly originated from the english article) + french examples to be found + local resources.
** open discussion with french wikipediens about implementing some of the english existing templates
** small gifts: accessories and free gifts ? t-shirts, localized cheat-sheet, id-hcard-openid-providing, etc.
*** create hCard, hCalendar... and all red link pages on french wikipedia
* localize [[species-fr]] and related pages
* move all contents remaining on elanceur.org -> microformateurs.org
* wiki and uf:
** write and talk with "aboutus.org" to invite them to make experiences with uf -> talk with Mark Dilley
** maintain/update http://www.communitywiki.org/MicroFormats and talk with LionKimbro
** XWiki : awaiting beta-test of new platform
*** Follow-up LudovicDubost et LaurentLunati
* setup real-life links with european [[governance-fr|governance]] members ;) may be joining dconstruct-microformats-workshop - find solution (registering fees and travel expenses -> talk with Arnaud Fontaine or search french sponsors)

== Frances Berriman ==

[[User:Phae|Frances Berriman]]

* Work on styles for [[zen-garden]] project.
* Style HTML cheatsheet to match Brian Suda's PDF.
* Write simplified help/implementation documents (how tos) for all finalised Microformats.
* Re-organise general FAQ and simplify
** (Feel free to add suggested tasks to my list below:)
*** Help converge on organization efforts ~bewest :-)

== Ben West (bewest) ==

[[User:BenWest|bewest]]
* fight spam
* help tend wiki
* documentation of semantic authoring techniques
* researching the social problems relating to authorship and publishing on the web
* development of new microformats in response to failing to meet the needs of the second with the first.

=== Expore Microformat Deployment Issues ===
How does who determine the status of work going through some stage of the process? When does a format move from draft to "full spec"? Who decides? What are the qualitative and quantitative features that characterize work in different stages, especially as a spec nears deployment as "full spec". What makes this pronouncement more than a mythical blessing? What quantitative analyses can be provided to validate deployment? Today, we have powerful agents capable of processing huge amounts of information on the web. Should we be using these to measure published marketshare? What role should tools and test suites play in deploying microformats?

=== Vocabulary ===
A lot of knowledge work is about maintaining sets of vocabulary. Now that the vocabulary is emerging, it may be time start making sure everyone is "on the same page," especially since some of the language is highly symbolic.
Terms:
* "boil the ocean" A huge task. "A phrase used in the industry to describe an attempt at something that is way too ambitious. For example, "They're trying to get their site launched by COMDEX. They could easier boil the ocean." from <http://www.netlingo.com/right.cfm?term=boil%20the%20ocean>
* microformats: more than one microformat
* microformat: see my definition on http://microformats.org/wiki/what-are-microformats#BenWest
* data fidelity: the extent to which a data format might be considered lossy. eg HTML is often seen as a lossy format because the information parsed out of a resource may not fully match the information orginally encoded. Non-lossy formats have a very high data fidelity, while lossy formats have low data fidelity. Microformats seek to increase data fidelity of html.
* market: the locus of economic forces

: See [[glossary]]. [[User:AndyMabbett|Andy Mabbett]] 13:57, 7 Dec 2006 (PST)

=== Creators ===
_Concession_: my plans involve reuse of code, which would involve non-compatible changes with the current inline model. This is a nice feature, so maybe I should be branching instead.
* <strike>Start hatom creator.</strike> http://dichotomize.com/uf/hatom/creator.html
* Code Reuse. These creators are downright handy, and I’ve reimplemented the vcard one on my own site. Instead, let’s make these widgetized. Let’s decide on a more or less canonical html structure and create some javascript that will create the desired microformat. Something as easy to use as new Microformat.hCard($('mycontainer')); would be awesome. Right now, if someone makes an improvement to the hCard creator, the other creators don’t get the benefit. Spec this out!
* About Section. Is there an official creator page? If so, let’s point to that. The about paragraph is getting longer and longer with phrases like “which is based on…” repeated over and over.
* Default all dates to “right now”. Provide an easy to use calendar type widget to change dates.
* hAtom creator: Add multiple. It’d be nice to add an arbitrary number of entries.
* hAtom creator: Optional feed enclosure. Check box to wrap the entry/entries in an hfeed.
* Edit URI: Allow someone to enter a URI and edit whatever microformat is found on the page.
* Optionals. If the format requires, say, a vcard, the creator can defer to an external URI or can trust the user to fill it in later.
* Common stylesheet. I suppose this goes with the reuseable code idea… we have many great coders, we should be reusing eachothers’ work.
* Use Amazon's ECS to pull in information about products when there is an ASIN in the item URI.

=== Information Architecture ===
'''Help Welcomed! Please leave your name'''
Add complaints to [[wiki-feedback]]!
Helping to make the wiki easier to use. I'd like to see the main page more towards a format like http://simile.mit.edu/solvent/ with the big questions right out front:
* What Is This?
* What can I do here?
* Is there a demo?
* Where can I learn more?
I'd like to change the front page to this kind of design.
==== Support Pages ====
There are several categories of things in the wiki. Can we enumerate them?
* About the Community
** Where to find information.
** Who are the stake holders?
** FAQs
* Web/Architectural Philosophy
** Community Principles
** Why are we doing this?
** XML and Namespaces
** Semantic XHTML
** Common Misconceptions
** Concession and Disposition of Criticism
** FAQs
* Specs
** Examples
** Discussion
** Exploration
** Use Cases
** Implementations
** The spec itself.

* Tips and Tricks for Authoring ([[User:BenWest|BenWest]] 15:00, 9 Dec 2006 (PST))
** how to author semantic html
** choosing class names
** using HTML's general extension mechanisms
** advocating use
** collaborating/reusing HTML
** debugging HTML: use pastebin, separate out the relevant bits.
** getting help from the community
** applying Microformats.

Can others agree and or refine this list? Should I take it to the -discuss list? How do we create consensus on how the wiki should be organized in order to make it more usable? And how can we turn that consensus into actionable changes?

The wiki should also capture wisdom that stems from discussions that don't produce microformats. For example, Chris Messina suggests a "Best Of" page suitable for capturing this kind of wisdom. I think we can think of a given microformat as being at a place in a spectrum that ranges from "not yet thought of", to "interesting but needs work," or even "rejected", and of course including all the stages familiar to the microformats processes (eg examples, brainstorming, etc...).
If there were such a page would it:
* Belong to a microformat? (eg hcard-bestof)
* or to the global namespace? (eg /wiki/wisdom/foobar-format)
(I think Chris Messina suggests that it belongs to a given microformat, but then how do we collect wisdom from non-microformats?)

Considering that the wiki page named with the microformat (i.e. /wiki/hcard) is the one that people will mostly likely look to first for learning about a particular format, I'd think it'd make more sense and create a more welcoming feel to convert these pages to an intro page introducing the format for the beginner and linking to resources like tutorials and creators. Spec pages would then be relocated to wiki/*-spec -- [[User:Cgriego|Cgriego]] 13:25, 16 Oct 2006 (PDT)

====Mike Schinkel's Comments====

My suggestion on the list was for us to use a convention that the entry page (i.e.
http://microformats.org/wiki/hcard) would be an index into a list of
(psuedo) standardized sub pages so that it would be very people to
find what is important to them. For example, is a list of potential sub pages:

* Microformat
** Specification
** Tutorial
** Examples
** Use cases
** Reference
** Discussion
** Brainstorming (might be combined w/Discussion)
** Implementations
** Related Pages
** Further Reading
** All (Uses Mediawiki's "includes" to create a page including all sub pages; very useful for printing & reading offline)

These pages would be located respectively at

* http://microformats.org/wiki/hcard/
** http://microformats.org/wiki/hcard/Specification
** http://microformats.org/wiki/hcard/Tutorial
** http://microformats.org/wiki/hcard/Examples
** http://microformats.org/wiki/hcard/Use_cases
** http://microformats.org/wiki/hcard/Reference
** http://microformats.org/wiki/hcard/Discussion
** http://microformats.org/wiki/hcard/Brainstorming
** http://microformats.org/wiki/hcard/Implementations
** http://microformats.org/wiki/hcard/Related_Pages
** http://microformats.org/wiki/hcard/Further_Reading
** http://microformats.org/wiki/hcard/All

Please note I am suggesting an architecture not a specific list of sub pages. The list of sub pages should be defined by both reviewing existing information during site reorganization, and then via discussion on the list in an attempt to discover and extract which sub pages are needed for most/all microformats.

'''NOTE''': This differs from above in that the spec if not viewed as a top level structure but instead the microformat itself and the spec would be under the microformat. In this context "microformat" is a more abstract concept and "spec" is a more concrete thing. Another way to think about it would be that each microformat would have it's own mini home page and then things like "spec" are the pages listed on its home page.

== Matt Dertinger (Thewhoo) ==

[[User:Thewhoo]]

=== hAtom2Atom ===
<ul>
<li>Support for other XSLT engines:
* hAtom2Atom written using XSL 2.0
</li>
<li>Support for other output formats: (hAtom2<i>xyz</i>.xsl)
* RSS 2.0 (meanwhile use hAtom2Atom.xsl and [http://atom.geekhood.net/ atom2rss.xsl])
* RSS 1.0 (meanwhile use hAtom2Atom.xsl and [http://cvs.4suite.org/viewcvs/uogbuji/atom2rss.xslt atom2rss.xslt])
* AtomOWL (meanwhile use hAtom2Atom.xsl and [http://dannyayers.com/2005/11/22/atomowl-xslt-progress/ atom2rdfxml.xsl])
</li>
</ul>

=== Microformats Proposals ===
<ul>
<li>rel="disclaimer":
* Purpose: to create a semantic linkage (relationship) between a foot-note or end-note marker and the actual location of the text that the marker refers to.</li>
<li>rel="external":
* Purpose: to formalize what is already in existence in the wild. The use of rel="external" to refer to a document that is external or outside of the current domain.</li>
</ul>

== Henri Bergius ==

[[User:HenriBergius|Henri Bergius]]

* Add hKit support for automatically populating contact details into [http://www.openpsa.org/version2/openpsa/contacts.html OpenPsa Contacts] CRM
* Implement Tail scripts for adding things into Midgard

== Justin Thorp ==
* Start researching examples for a To-do microformat

== [[User:MarkLentczner|Mark Lentczner]] ==

* Get Second Life's event web pages to have proper event microformats data
** Add [[hcard|hCard]] to profile pages
** Add [[hcalendar|hCalendar]] to events listings
* Start pinging pingerati.net/ping/$url when pages are updated
* Collaborate on designing how to integrate microformats, metadata and objects in [http://secondlife.com/ Second Life].

== [[User:DerrickPallas|Derrick Pallas]] ==
=== microformat proposal: dependancy ===
* looking for examples of directed graphs on the web
* applications in
** software engineering
*** automatically build library dependency trees
*** distribute security alerts to people that link to your code
** any directed, acyclic graph
*** getting dressed in the morning
*** cooking
* orthogonal to xfn
** people don't have versions
*** libfoo requires libbar-2.0 or later
** people don't have optional relationships
*** ex: at build time, compile in SSL support if present
** people don't have exclusive-or relationships
*** ex: in Gentoo, syslog, syslog-ng, and metalog satisfy virtual/syslog
*** ex: the Ruby library RMagick requires ImageMagick xor GraphicsMagick

== [[User:PaulDowney|Paul Downey]] ==
* building a generic Javascript parser
* bundling parser as a [http://tiddlywiki.org TidlyWiki] plugin for hCards
* documenting how best to microformat TiddlyWiki pages

== [[User:RobManson | Rob Manson]] ==
* chase the admins to get some creation template extensions installed for wiki (see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle)

== [[User:ClayNewton | Clay Newton]] ==
* Work on getting others involved in [[trade-examples]]
** Need examples from major online banking sites
** Need examples from major ecommerce sites
* Continue working on: [[trade-brainstorming]]

trade-examples

2007-08-07T04:05:17Z

ClayNewton: /* Wesabe */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

__TOC__

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

=== Example ===

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* All of which create collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===
[http://www.ing.com ING]

enter notes here

=== Amazon.com ===
[http://www.amazon.com Amazon.com]

enter notes here

=== eBay ===
[http://www.ebay.com Ebay]

enter notes here

=== Paypal ===
[http://www.paypal.com Paypal]

enter notes here

=== Quicken ===
[http://www.quicken.com Quicken]
==== Deposits Accounts ====
* post date (PostDt)
* transaction description (TrDesc)
* transaction amount (TrAmt)
* type (TT)
* running balance (RunningBal)

'''Markup:'''
<pre><nowiki><Item>
<PostDt>12/27/2005</PostDt>
<TrDesc>FIREWOOD CAFE-METREON 12/22 CARD #0265 PURCHASE #24388945357670320615609 SAN FRANCISCO, CA</TrDesc>
<TrAmt>-$10.95</TrAmt>
<TT>D</TT>
<RunningBal>$2,916.63</RunningBal>
</Item></nowiki></pre>

=== Quickbooks ===
enter notes here

=== Wesabe ===
[http://www.wesabe.com Wesabe]
<pre><nowiki>
<div id="TRANSACTION-ID" class="txaction_display" >
<div class="merchant_info">
<div class="date"> Friday, March 23rd </div>
<div class="merchant" id="TRANSACTION-ID">
<span class="name"><a href="MERCH-ID">Mojo JOJO</a></span>
<div class="tags">
<span class="rating_text">Rating: <span class="user">User</span></span>
Tags: <a href="TAG-URL">groceries</a>
</div>
</div>
</div>
<div class="balance">
<span class="credit">$988.56</span>
</div>
<div class="amount">
<span class="nowrap">-$7.56</span>
</div>
</div>
</nowiki></pre>

=== Yodlee ===
enter notes here

== See Also ==
* [[trade-brainstorming | Brainstorming trade]]

trade-examples

2007-08-07T04:04:47Z

ClayNewton: /* Wesabe */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

__TOC__

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

=== Example ===

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* All of which create collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===
[http://www.ing.com ING]

enter notes here

=== Amazon.com ===
[http://www.amazon.com Amazon.com]

enter notes here

=== eBay ===
[http://www.ebay.com Ebay]

enter notes here

=== Paypal ===
[http://www.paypal.com Paypal]

enter notes here

=== Quicken ===
[http://www.quicken.com Quicken]
==== Deposits Accounts ====
* post date (PostDt)
* transaction description (TrDesc)
* transaction amount (TrAmt)
* type (TT)
* running balance (RunningBal)

'''Markup:'''
<pre><nowiki><Item>
<PostDt>12/27/2005</PostDt>
<TrDesc>FIREWOOD CAFE-METREON 12/22 CARD #0265 PURCHASE #24388945357670320615609 SAN FRANCISCO, CA</TrDesc>
<TrAmt>-$10.95</TrAmt>
<TT>D</TT>
<RunningBal>$2,916.63</RunningBal>
</Item></nowiki></pre>

=== Quickbooks ===
enter notes here

=== Wesabe ===
[http://www.wesabe.com Wesabe]
<pre>
<nowiki>
<div id="TRANSACTION-ID" class="txaction_display" >
<div class="merchant_info">
<div class="date"> Friday, March 23rd </div>
<div class="merchant" id="TRANSACTION-ID">
<span class="name"><a href="MERCH-ID">Mojo JOJO</a></span>
<div class="tags">
<span class="rating_text">Rating: <span class="user">User</span></span>
Tags: <a href="TAG-URL">groceries</a>
</div>
</div>
</div>
<div class="balance">
<span class="credit">$988.56</span>
</div>
<div class="amount">
<span class="nowrap">-$7.56</span>
</div>
</div>
</nowiki>
</pre>

=== Yodlee ===
enter notes here

== See Also ==
* [[trade-brainstorming | Brainstorming trade]]

trade-brainstorming

2007-08-07T03:52:21Z

ClayNewton: /* Singular vs. Plural Properties */

[[trade-examples | See examples of trade]].

__TOC__

== Specification ==

== Introduction ==
There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

== Format ==
There are many data formats used in financial systems to represent transactions. The vast majority of these are proprietary, typically resulting from an evolution from paper-based accounting to mainframe computing to electronic interchange networks to the web and now to mobile systems.

=== In General ===
A simple semantic format using (like [[hcard | hCard]]) object/property names in lower-case for class names. Financial transaction attributes would be mapped to nested XHTML elements.

=== Root Class Name ===
The root class name could "record". "Record" is a common financial industry term. Records map to all data collected in the form of a "transaction". The expression of a record is itself considered a transaction.

=== Properties and Sub-properties ===
The properties of a trade are represented by elements inside the trade root. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
properties (sub-properties in parentheses like this)

'''Required:'''
* '''post-date'''
* '''to-account''' (to-account-number, to-account-holder)
* '''amount-posted'''
Optional:
* date (date-type)
* from-account (from-account-number, from-account-holder)
* date-hold-start (date-hold-end, amount-held)
* status
* type
* reference-number (card-type, periodic-rate)
* fee-amount (fee-type, fee-description)
* category-name (category-id, category-amount)
* image-type (image-front-url, image-back-url)
* tax-flag (tax-flag-type, tax-flag-amount)
* return-url (return-description)

=== Singular vs. Plural Properties ===
Singular properties:
'post-date', 'from-account', 'from-account-number', 'from-account-holder', 'to-account', 'to-account-number', 'to-account-holder', 'amount-posted status', 'type', 'card-type', 'periodic-rate'. For properties which are singular, the first descendant element with that class should take effect, any others being ignored.

All other properties can be plural. Each class instance of such properties creates a new instance of that property.

== See Also ==
* [[trade-examples | trade examples]]

trade-brainstorming

2007-08-07T03:51:50Z

ClayNewton: /* Property List */

[[trade-examples | See examples of trade]].

__TOC__

== Specification ==

== Introduction ==
There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

== Format ==
There are many data formats used in financial systems to represent transactions. The vast majority of these are proprietary, typically resulting from an evolution from paper-based accounting to mainframe computing to electronic interchange networks to the web and now to mobile systems.

=== In General ===
A simple semantic format using (like [[hcard | hCard]]) object/property names in lower-case for class names. Financial transaction attributes would be mapped to nested XHTML elements.

=== Root Class Name ===
The root class name could "record". "Record" is a common financial industry term. Records map to all data collected in the form of a "transaction". The expression of a record is itself considered a transaction.

=== Properties and Sub-properties ===
The properties of a trade are represented by elements inside the trade root. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
properties (sub-properties in parentheses like this)

'''Required:'''
* '''post-date'''
* '''to-account''' (to-account-number, to-account-holder)
* '''amount-posted'''
Optional:
* date (date-type)
* from-account (from-account-number, from-account-holder)
* date-hold-start (date-hold-end, amount-held)
* status
* type
* reference-number (card-type, periodic-rate)
* fee-amount (fee-type, fee-description)
* category-name (category-id, category-amount)
* image-type (image-front-url, image-back-url)
* tax-flag (tax-flag-type, tax-flag-amount)
* return-url (return-description)

=== Singular vs. Plural Properties ===
Singular properties:
'from-account', 'from-account-number', 'from-account-holder', 'to-account', 'to-account-number', 'to-account-holder', 'amount-posted status', 'type', 'card-type', 'periodic-rate'. For properties which are singular, the first descendant element with that class should take effect, any others being ignored.

All other properties can be plural. Each class instance of such properties creates a new instance of that property.

== See Also ==
* [[trade-examples | trade examples]]

trade-brainstorming

2007-08-07T03:51:19Z

ClayNewton: /* Property List */

[[trade-examples | See examples of trade]].

__TOC__

== Specification ==

== Introduction ==
There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

== Format ==
There are many data formats used in financial systems to represent transactions. The vast majority of these are proprietary, typically resulting from an evolution from paper-based accounting to mainframe computing to electronic interchange networks to the web and now to mobile systems.

=== In General ===
A simple semantic format using (like [[hcard | hCard]]) object/property names in lower-case for class names. Financial transaction attributes would be mapped to nested XHTML elements.

=== Root Class Name ===
The root class name could "record". "Record" is a common financial industry term. Records map to all data collected in the form of a "transaction". The expression of a record is itself considered a transaction.

=== Properties and Sub-properties ===
The properties of a trade are represented by elements inside the trade root. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
properties (sub-properties in parentheses like this)

'''Required:'''
* '''post-date''' (date-type)
* '''to-account''' (to-account-number, to-account-holder)
* '''amount-posted'''
Optional:
* date (date-type)
* from-account (from-account-number, from-account-holder)
* date-hold-start (date-hold-end, amount-held)
* status
* type
* reference-number (card-type, periodic-rate)
* fee-amount (fee-type, fee-description)
* category-name (category-id, category-amount)
* image-type (image-front-url, image-back-url)
* tax-flag (tax-flag-type, tax-flag-amount)
* return-url (return-description)

=== Singular vs. Plural Properties ===
Singular properties:
'from-account', 'from-account-number', 'from-account-holder', 'to-account', 'to-account-number', 'to-account-holder', 'amount-posted status', 'type', 'card-type', 'periodic-rate'. For properties which are singular, the first descendant element with that class should take effect, any others being ignored.

All other properties can be plural. Each class instance of such properties creates a new instance of that property.

== See Also ==
* [[trade-examples | trade examples]]

trade-brainstorming

2007-08-03T20:02:30Z

ClayNewton: /* Property List */

[[trade-examples | See examples of trade]].

__TOC__

== Specification ==

== Introduction ==
There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

== Format ==
There are many data formats used in financial systems to represent transactions. The vast majority of these are proprietary, typically resulting from an evolution from paper-based accounting to mainframe computing to electronic interchange networks to the web and now to mobile systems.

=== In General ===
A simple semantic format using (like [[hcard | hCard]]) object/property names in lower-case for class names. Financial transaction attributes would be mapped to nested XHTML elements.

=== Root Class Name ===
The root class name could "record". "Record" is a common financial industry term. Records map to all data collected in the form of a "transaction". The expression of a record is itself considered a transaction.

=== Properties and Sub-properties ===
The properties of a trade are represented by elements inside the trade root. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
properties (sub-properties in parentheses like this)

'''Required:'''
* '''date''' (date-type)
* '''to-account''' (to-account-number, to-account-holder)
* '''amount-posted'''
Optional:
* from-account (from-account-number, from-account-holder)
* date-hold-start (date-hold-end, amount-held)
* status
* type
* reference-number (card-type, periodic-rate)
* fee-amount (fee-type, fee-description)
* category-name (category-id, category-amount)
* image-type (image-front-url, image-back-url)
* tax-flag (tax-flag-type, tax-flag-amount)
* return-url (return-description)

=== Singular vs. Plural Properties ===
Singular properties:
'from-account', 'from-account-number', 'from-account-holder', 'to-account', 'to-account-number', 'to-account-holder', 'amount-posted status', 'type', 'card-type', 'periodic-rate'. For properties which are singular, the first descendant element with that class should take effect, any others being ignored.

All other properties can be plural. Each class instance of such properties creates a new instance of that property.

== See Also ==
* [[trade-examples | trade examples]]

trade-examples

2007-08-03T19:48:07Z

ClayNewton: /* See Also */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

__TOC__

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

=== Example ===

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* All of which create collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===
[http://www.ing.com ING]

enter notes here

=== Amazon.com ===
[http://www.amazon.com Amazon.com]

enter notes here

=== eBay ===
[http://www.ebay.com Ebay]

enter notes here

=== Paypal ===
[http://www.paypal.com Paypal]

enter notes here

=== Quicken ===
[http://www.quicken.com Quicken]
==== Deposits Accounts ====
* post date (PostDt)
* transaction description (TrDesc)
* transaction amount (TrAmt)
* type (TT)
* running balance (RunningBal)

'''Markup:'''
<pre><nowiki><Item>
<PostDt>12/27/2005</PostDt>
<TrDesc>FIREWOOD CAFE-METREON 12/22 CARD #0265 PURCHASE #24388945357670320615609 SAN FRANCISCO, CA</TrDesc>
<TrAmt>-$10.95</TrAmt>
<TT>D</TT>
<RunningBal>$2,916.63</RunningBal>
</Item></nowiki></pre>

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

=== Yodlee ===
enter notes here

== See Also ==
* [[trade-brainstorming | Brainstorming trade]]

trade-examples

2007-08-03T19:46:13Z

ClayNewton: /* See Also */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

__TOC__

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

=== Example ===

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* All of which create collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===
[http://www.ing.com ING]

enter notes here

=== Amazon.com ===
[http://www.amazon.com Amazon.com]

enter notes here

=== eBay ===
[http://www.ebay.com Ebay]

enter notes here

=== Paypal ===
[http://www.paypal.com Paypal]

enter notes here

=== Quicken ===
[http://www.quicken.com Quicken]
==== Deposits Accounts ====
* post date (PostDt)
* transaction description (TrDesc)
* transaction amount (TrAmt)
* type (TT)
* running balance (RunningBal)

'''Markup:'''
<pre><nowiki><Item>
<PostDt>12/27/2005</PostDt>
<TrDesc>FIREWOOD CAFE-METREON 12/22 CARD #0265 PURCHASE #24388945357670320615609 SAN FRANCISCO, CA</TrDesc>
<TrAmt>-$10.95</TrAmt>
<TT>D</TT>
<RunningBal>$2,916.63</RunningBal>
</Item></nowiki></pre>

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

=== Yodlee ===
enter notes here

== See Also ==
* [[trade-branstorm| Brainstorming trade]]

trade-examples

2007-08-03T19:40:26Z

ClayNewton: /* Example:' */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

__TOC__

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

=== Example ===

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* All of which create collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===
[http://www.ing.com ING]

enter notes here

=== Amazon.com ===
[http://www.amazon.com Amazon.com]

enter notes here

=== eBay ===
[http://www.ebay.com Ebay]

enter notes here

=== Paypal ===
[http://www.paypal.com Paypal]

enter notes here

=== Quicken ===
[http://www.quicken.com Quicken]
==== Deposits Accounts ====
* post date (PostDt)
* transaction description (TrDesc)
* transaction amount (TrAmt)
* type (TT)
* running balance (RunningBal)

'''Markup:'''
<pre><nowiki><Item>
<PostDt>12/27/2005</PostDt>
<TrDesc>FIREWOOD CAFE-METREON 12/22 CARD #0265 PURCHASE #24388945357670320615609 SAN FRANCISCO, CA</TrDesc>
<TrAmt>-$10.95</TrAmt>
<TT>D</TT>
<RunningBal>$2,916.63</RunningBal>
</Item></nowiki></pre>

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

=== Yodlee ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-examples

2007-08-03T19:40:14Z

ClayNewton: /* Why do we need a trade microformat? */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

__TOC__

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

=== Example:' ===

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* All of which create collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===
[http://www.ing.com ING]

enter notes here

=== Amazon.com ===
[http://www.amazon.com Amazon.com]

enter notes here

=== eBay ===
[http://www.ebay.com Ebay]

enter notes here

=== Paypal ===
[http://www.paypal.com Paypal]

enter notes here

=== Quicken ===
[http://www.quicken.com Quicken]
==== Deposits Accounts ====
* post date (PostDt)
* transaction description (TrDesc)
* transaction amount (TrAmt)
* type (TT)
* running balance (RunningBal)

'''Markup:'''
<pre><nowiki><Item>
<PostDt>12/27/2005</PostDt>
<TrDesc>FIREWOOD CAFE-METREON 12/22 CARD #0265 PURCHASE #24388945357670320615609 SAN FRANCISCO, CA</TrDesc>
<TrAmt>-$10.95</TrAmt>
<TT>D</TT>
<RunningBal>$2,916.63</RunningBal>
</Item></nowiki></pre>

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

=== Yodlee ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-examples

2007-08-03T18:18:53Z

ClayNewton: /* Current */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

__TOC__

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

'''Example:'''

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* All of which create collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===
[http://www.ing.com ING]

enter notes here

=== Amazon.com ===
[http://www.amazon.com Amazon.com]

enter notes here

=== eBay ===
[http://www.ebay.com Ebay]

enter notes here

=== Paypal ===
[http://www.paypal.com Paypal]

enter notes here

=== Quicken ===
[http://www.quicken.com Quicken]
==== Deposits Accounts ====
* post date (PostDt)
* transaction description (TrDesc)
* transaction amount (TrAmt)
* type (TT)
* running balance (RunningBal)

'''Markup:'''
<pre><nowiki><Item>
<PostDt>12/27/2005</PostDt>
<TrDesc>FIREWOOD CAFE-METREON 12/22 CARD #0265 PURCHASE #24388945357670320615609 SAN FRANCISCO, CA</TrDesc>
<TrAmt>-$10.95</TrAmt>
<TT>D</TT>
<RunningBal>$2,916.63</RunningBal>
</Item></nowiki></pre>

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

=== Yodlee ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-examples

2007-08-03T18:17:08Z

ClayNewton:

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

__TOC__

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

'''Example:'''

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* Types of collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===
[http://www.ing.com ING]

enter notes here

=== Amazon.com ===
[http://www.amazon.com Amazon.com]

enter notes here

=== eBay ===
[http://www.ebay.com Ebay]

enter notes here

=== Paypal ===
[http://www.paypal.com Paypal]

enter notes here

=== Quicken ===
[http://www.quicken.com Quicken]
==== Deposits Accounts ====
* post date (PostDt)
* transaction description (TrDesc)
* transaction amount (TrAmt)
* type (TT)
* running balance (RunningBal)

'''Markup:'''
<pre><nowiki><Item>
<PostDt>12/27/2005</PostDt>
<TrDesc>FIREWOOD CAFE-METREON 12/22 CARD #0265 PURCHASE #24388945357670320615609 SAN FRANCISCO, CA</TrDesc>
<TrAmt>-$10.95</TrAmt>
<TT>D</TT>
<RunningBal>$2,916.63</RunningBal>
</Item></nowiki></pre>

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

=== Yodlee ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-examples

2007-08-03T18:07:39Z

ClayNewton:

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

__TOC__

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

'''Example:'''

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* Types of collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===
[http://www.ing.com ING]

enter notes here

=== Amazon.com ===
[http://www.amazon.com Amazon.com]

enter notes here

=== eBay ===
[http://www.ebay.com Ebay]

enter notes here

=== Paypal ===
[http://www.paypal.com Paypal]

enter notes here

=== Quicken ===
[http://www.quicken.com Quicken]
==== Deposits Accounts ====
* post date (PostDt)
* transaction description (TrDesc)
* transaction amount (TrAmt)
* type (TT)
* running balance (RunningBal)

'''Markup:'''
<pre><nowiki><Item>
<PostDt>12/27/2005</PostDt>
<TrDesc>FIREWOOD CAFE-METREON 12/22 CARD #0265 PURCHASE #24388945357670320615609 SAN FRANCISCO, CA</TrDesc>
<TrAmt>-$10.95</TrAmt>
<TT>D</TT>
<RunningBal>$2,916.63</RunningBal>
</Item></nowiki></pre>

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-brainstorming

2007-08-03T18:06:57Z

ClayNewton: /* See Also */

[[trade-examples | See examples of trade]].

__TOC__

== Specification ==

== Introduction ==
There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

== Format ==
There are many data formats used in financial systems to represent transactions. The vast majority of these are proprietary, typically resulting from an evolution from paper-based accounting to mainframe computing to electronic interchange networks to the web and now to mobile systems.

=== In General ===
A simple semantic format using (like [[hcard | hCard]]) object/property names in lower-case for class names. Financial transaction attributes would be mapped to nested XHTML elements.

=== Root Class Name ===
The root class name could "record". "Record" is a common financial industry term. Records map to all data collected in the form of a "transaction". The expression of a record is itself considered a transaction.

=== Properties and Sub-properties ===
The properties of a trade are represented by elements inside the trade root. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
properties (sub-properties in parentheses like this)

'''Required:'''
* '''date''' (date-type)
* '''to-account''' (to-account-number, to-account-holder)
* '''amount-posted'''
Optional:
* from-account (from-account-number, from-account-holder)
* date-hold-start (date-hold-end, amount-held)
* status
* type
* reference-number (card-type, periodic-rate)
* fee-amount (fee-type, fee-description)
* category-name (category-id, category-amount)
* image-type (image-front-uri, image-back-uri)
* tax-flag (tax-flag-type, tax-flag-amount)

=== Singular vs. Plural Properties ===
Singular properties:
'from-account', 'from-account-number', 'from-account-holder', 'to-account', 'to-account-number', 'to-account-holder', 'amount-posted status', 'type', 'card-type', 'periodic-rate'. For properties which are singular, the first descendant element with that class should take effect, any others being ignored.

All other properties can be plural. Each class instance of such properties creates a new instance of that property.

== See Also ==
* [[trade-examples | trade examples]]

trade-brainstorming

2007-08-03T18:06:42Z

ClayNewton:

[[trade-examples | See examples of trade]].

__TOC__

== Specification ==

== Introduction ==
There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

== Format ==
There are many data formats used in financial systems to represent transactions. The vast majority of these are proprietary, typically resulting from an evolution from paper-based accounting to mainframe computing to electronic interchange networks to the web and now to mobile systems.

=== In General ===
A simple semantic format using (like [[hcard | hCard]]) object/property names in lower-case for class names. Financial transaction attributes would be mapped to nested XHTML elements.

=== Root Class Name ===
The root class name could "record". "Record" is a common financial industry term. Records map to all data collected in the form of a "transaction". The expression of a record is itself considered a transaction.

=== Properties and Sub-properties ===
The properties of a trade are represented by elements inside the trade root. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
properties (sub-properties in parentheses like this)

'''Required:'''
* '''date''' (date-type)
* '''to-account''' (to-account-number, to-account-holder)
* '''amount-posted'''
Optional:
* from-account (from-account-number, from-account-holder)
* date-hold-start (date-hold-end, amount-held)
* status
* type
* reference-number (card-type, periodic-rate)
* fee-amount (fee-type, fee-description)
* category-name (category-id, category-amount)
* image-type (image-front-uri, image-back-uri)
* tax-flag (tax-flag-type, tax-flag-amount)

=== Singular vs. Plural Properties ===
Singular properties:
'from-account', 'from-account-number', 'from-account-holder', 'to-account', 'to-account-number', 'to-account-holder', 'amount-posted status', 'type', 'card-type', 'periodic-rate'. For properties which are singular, the first descendant element with that class should take effect, any others being ignored.

All other properties can be plural. Each class instance of such properties creates a new instance of that property.

== See Also ==
* [trade-examples | trade examples]

trade-brainstorming

2007-08-03T18:05:51Z

ClayNewton:

[[trade-examples | See examples of trade]].

__TOC__

== Specification ==

== Introduction ==
There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

== Format ==
There are many data formats used in financial systems to represent transactions. The vast majority of these are proprietary, typically resulting from an evolution from paper-based accounting to mainframe computing to electronic interchange networks to the web and now to mobile systems.

=== In General ===
A simple semantic format using (like [[hcard | hCard]]) object/property names in lower-case for class names. Financial transaction attributes would be mapped to nested XHTML elements.

=== Root Class Name ===
The root class name could "record". "Record" is a common financial industry term. Records map to all data collected in the form of a "transaction". The expression of a record is itself considered a transaction.

=== Properties and Sub-properties ===
The properties of a trade are represented by elements inside the trade root. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
properties (sub-properties in parentheses like this)

'''Required:'''
* '''date''' (date-type)
* '''to-account''' (to-account-number, to-account-holder)
* '''amount-posted'''
Optional:
* from-account (from-account-number, from-account-holder)
* date-hold-start (date-hold-end, amount-held)
* status
* type
* reference-number (card-type, periodic-rate)
* fee-amount (fee-type, fee-description)
* category-name (category-id, category-amount)
* image-type (image-front-uri, image-back-uri)
* tax-flag (tax-flag-type, tax-flag-amount)

=== Singular vs. Plural Properties ===
Singular properties:
'from-account', 'from-account-number', 'from-account-holder', 'to-account', 'to-account-number', 'to-account-holder', 'amount-posted status', 'type', 'card-type', 'periodic-rate'. For properties which are singular, the first descendant element with that class should take effect, any others being ignored.

All other properties can be plural. Each class instance of such properties creates a new instance of that property.

trade-examples

2007-08-03T18:03:32Z

ClayNewton: /* Deposits Accounts */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

'''Example:'''

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* Types of collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===
[http://www.ing.com ING]

enter notes here

=== Amazon.com ===
[http://www.amazon.com Amazon.com]

enter notes here

=== eBay ===
[http://www.ebay.com Ebay]

enter notes here

=== Paypal ===
[http://www.paypal.com Paypal]

enter notes here

=== Quicken ===
[http://www.quicken.com Quicken]
==== Deposits Accounts ====
* post date (PostDt)
* transaction description (TrDesc)
* transaction amount (TrAmt)
* type (TT)
* running balance (RunningBal)

'''Markup:'''
<pre><nowiki><Item>
<PostDt>12/27/2005</PostDt>
<TrDesc>FIREWOOD CAFE-METREON 12/22 CARD #0265 PURCHASE #24388945357670320615609 SAN FRANCISCO, CA</TrDesc>
<TrAmt>-$10.95</TrAmt>
<TT>D</TT>
<RunningBal>$2,916.63</RunningBal>
</Item></nowiki></pre>

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-examples

2007-08-03T18:03:02Z

ClayNewton: /* Quicken */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

'''Example:'''

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* Types of collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===
[http://www.ing.com ING]

enter notes here

=== Amazon.com ===
[http://www.amazon.com Amazon.com]

enter notes here

=== eBay ===
[http://www.ebay.com Ebay]

enter notes here

=== Paypal ===
[http://www.paypal.com Paypal]

enter notes here

=== Quicken ===
[http://www.quicken.com Quicken]
==== Deposits Accounts ====
* post date (PostDt)
* transaction description (TrDesc)
* transaction amount (TrAmt)
* type (TT)
* running balance (RunningBal)

'''Markup:'''
<pre><nowiki><Item>
<PostDt>12/27/2005</PostDt>
<TrDesc>FIREWOOD CAFE-METREON 12/22 CARD #0265 PURCHASE #24388945357670320615609 SAN FRANCISCO, CA</TrDesc>
<TrAmt>-$10.95</TrAmt>
<TT>D</TT>
<RunningBal>$2,916.63</RunningBal>
</Item></nowiki></pre>
enter notes here

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-examples

2007-08-03T17:56:33Z

ClayNewton: /* Paypal */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

'''Example:'''

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* Types of collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===
[http://www.ing.com ING]

enter notes here

=== Amazon.com ===
[http://www.amazon.com Amazon.com]

enter notes here

=== eBay ===
[http://www.ebay.com Ebay]

enter notes here

=== Paypal ===
[http://www.paypal.com Paypal]

enter notes here

=== Quicken ===
enter notes here

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-examples

2007-08-03T17:56:13Z

ClayNewton: /* eBay */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

'''Example:'''

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* Types of collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===
[http://www.ing.com ING]

enter notes here

=== Amazon.com ===
[http://www.amazon.com Amazon.com]

enter notes here

=== eBay ===
[http://www.ebay.com Ebay]

enter notes here

=== Paypal ===
enter notes here

=== Quicken ===
enter notes here

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-examples

2007-08-03T17:55:55Z

ClayNewton: /* Amazon.com */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

'''Example:'''

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* Types of collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===
[http://www.ing.com ING]

enter notes here

=== Amazon.com ===
[http://www.amazon.com Amazon.com]

enter notes here

=== eBay ===
enter notes here

=== Paypal ===
enter notes here

=== Quicken ===
enter notes here

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-examples

2007-08-03T17:55:31Z

ClayNewton: /* ING */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

'''Example:'''

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* Types of collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===
[http://www.ing.com ING]

enter notes here

=== Amazon.com ===
enter notes here

=== eBay ===
enter notes here

=== Paypal ===
enter notes here

=== Quicken ===
enter notes here

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-examples

2007-08-03T17:55:10Z

ClayNewton: /* Citibank */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

'''Example:'''

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* Types of collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
[http://www.citibank.com Citibank]

enter notes here

=== ING ===

=== Amazon.com ===
enter notes here

=== eBay ===
enter notes here

=== Paypal ===
enter notes here

=== Quicken ===
enter notes here

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-examples

2007-08-03T17:54:45Z

ClayNewton: /* Wells Fargo */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

'''Example:'''

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* Types of collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]

enter notes here

=== Citibank ===
enter notes here

=== ING ===

=== Amazon.com ===
enter notes here

=== eBay ===
enter notes here

=== Paypal ===
enter notes here

=== Quicken ===
enter notes here

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-examples

2007-08-03T17:54:33Z

ClayNewton: /* Wells Fargo */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

'''Example:'''

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* Types of collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
[http://www.wellsfargo.com Wells Fargo]
enter notes here

=== Citibank ===
enter notes here

=== ING ===

=== Amazon.com ===
enter notes here

=== eBay ===
enter notes here

=== Paypal ===
enter notes here

=== Quicken ===
enter notes here

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-examples

2007-08-03T17:53:10Z

ClayNewton: /* Deposit Accounts */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

'''Example:'''

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* Types of collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img
src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url"
onclick="some-js()" class="linknormal" id="di17"><img
id="rtImg17" src="expand-image-url" alt="Expand this
form to view and enter additional details for this
transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK
OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO
ID:1042472499 PPD REF:000478766385121108250007211
00301576107073122" onclick="some-js()">BANK OF
AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img
src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url"
class="linknormal2" title=""><img id="stat_17"
src="status-image-url" alt="Cleared. Select this
link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap"
width="75">
<div class="statementcolmn2"><span
class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img
src="spacer-image-url" alt="" height="1"
width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2">
<span class="textn2">$8,910.11</span>
</div>
</td>
<td width="10"><img src="spacer-image-url"
alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
enter notes here

=== Citibank ===
enter notes here

=== ING ===

=== Amazon.com ===
enter notes here

=== eBay ===
enter notes here

=== Paypal ===
enter notes here

=== Quicken ===
enter notes here

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-examples

2007-08-03T17:51:06Z

ClayNewton: /* Deposit Accounts */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

'''Example:'''

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* Types of collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url" onclick="some-js()" class="linknormal" id="di17"><img id="rtImg17" src="expand-image-url" alt="Expand this form to view and enter additional details for this transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO ID:1042472499 PPD REF:00047876638512110825000721100301576107073122" onclick="some-js()">BANK OF AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url" class="linknormal2" title=""><img id="stat_17" src="status-image-url" alt="Cleared. Select this link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap" width="75">
<div class="statementcolmn2"><span class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img src="spacer-image-url" alt="" height="1" width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2"><span class="textn2">$8,910.11</span></div>
</td>
<td width="10"><img src="spacer-image-url" alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
enter notes here

=== Citibank ===
enter notes here

=== ING ===

=== Amazon.com ===
enter notes here

=== eBay ===
enter notes here

=== Paypal ===
enter notes here

=== Quicken ===
enter notes here

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-examples

2007-08-03T17:49:25Z

ClayNewton: /* Deposit Accounts */

= What trade is all about =

'''Trade''' is the act of transacting goods between two parties. Transactions may or may not involve the actual exchange of goods, as they may simply represent an order for goods.

This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

== Why do we need a trade microformat? ==

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

There is no published standard means of communicating trade. As such there are many different implementations, and much parsing occurs at both ends of the equation.

'''Example:'''

* A bank stores structured transactional metadata in a mainframe.
* A consumer references this information in an online banking web application.
* A consumer tracks their finances using mobile banking.
* A consumer deposits their cash using an ATM.
* A consumer uses their mobile device and NFC technology to purchase items at a storefront.
* A consumer manages their personal goals using an online toolkit.
* A consumer also manages their budget using Quicken.
* A consumer purchases items with their credit card on an e-commerce portal.
* A consumer maintains a list of items they wish to purchase at a future date.
* A small business supplies services to a consumer, emails them an invoice and uses an e-check as payment.

Each of these platforms uses a proprietary means of displaying, structuring and storing the same data. A microformat devoted to trade would provide for easy interoperability between services and applications, facilitating further trade, and simplifying the means of transferring data.

== Participants ==
* [[ClayNewton | Clay Newton]]

== How people trade today ==

=== Current ===
* People transact through a number of electronic forms
** card transactions
** ACH (Automatic Clearing House)
** POS (Point of Sale)
** Check (e-checks)
** Transfers
*** Interbank
*** Intrabank
*** P2P
** ATM
*** Deposits
*** Transfers
*** Withdrawals
*** Purchases
* People use records of these transactions to
** Plan their finances
** Manage their expenses
** Report their PNL
* Types of collections of records
** Bank statements
** Purchase orders
** wishlists
** Financial Management suites
** Account aggregators
** Budgets
*** Personal
*** Business / Enterprise

=== Human ===
People use a number of means to track their finances in meatspace.

Consumers use their check registers to track finances. Many times consumers will use a spreadsheet for budgeting, or Quicken / MS Money to track expenditures. Many people track their finances using envelopes to represent discretionary spending within specific categories. People are beginning to use tools like Mvelopes and Wesabe to do an electronic equivalent.

Business use robust financial software to manage their finances. Spreadsheets are common, as is the use of financial ledgers.

=== Behavior ===
* TODO: '''notes below are from the behavior boilerplate'''
* What people actually '''do'''. Think empirical evidence, much as in the same way that the scientific method requires gathering of empirical data.
* not:
** what they ''might'' do
** ''should have'' done
** ''would'' do
** Intention/Desire/Want. A common mistake done by folks researching background for formats is to explicitly *ask* folks what they *want* or *prefer*, as opposed to *studying* what they *do*. It is well known among behavioral researchers/surveyors that *asking* people what they *want*, or even *asking* people what they *do*, will give you very different (and worse / less accurate) answers than actually *studying* what they *do* in the real world.
** Formats. Formats are prescriptions for behavior, not behavior itself. For documenting formats, create a *-formats page.

=== Web ===
* TODO: '''notes below are from the WEB boilerplate'''
* The examples MUST focus on examples actually published on the Web, at a publicly available URL, which should be documented along with the example itself on the wiki page.
* Non-web examples are ok *only* for secondary/tertiary consideration, and by no means outweight (no matter what their quantity etc.) the Web examples.
** private files
** paper
** etc.

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held

'''Markup:'''
<pre><nowiki>
<tr class="module1bkgd3" id="row17">
<td class="mi" width="6"><a name="skip17"></a><img src="spacer-image-url" alt="" border="0" width="6"></td>
<td class="mi" width="6">
<div id="fdi17" class="inline"><a href="some-url" onclick="some-js()" class="linknormal" id="di17"><img id="rtImg17" src="expand-image-url" alt="Expand this form to view and enter additional details for this transaction" align="absmiddle" border="0"></a></div>
</td>
<td class="tp" align="left" width="15%">07/31/2007</td>
<td class="t2" width="36%">
<div id="dld17" class="inline">
<a href="some-url" class="linknormal4" title="BANK OF AMERICA DES:PAYROLL ID: INDN:NEWTON CLAY CO ID:1042472499 PPD REF:00047876638512110825000721100301576107073122" onclick="some-js()">BANK OF AMERICA DES:PAYROLL ID: INDN:NEWT...</a>
</div>
</td>
<td class="mi" align="center" width="10%"><img src="deposit-image-url" alt="Deposit"></td>
<td class="mi" align="center" width="10%">
<a onclick="some-js()" href="some-url" class="linknormal2" title="">
<img id="stat_17" src="status-image-url" alt="Cleared. Select this link to mark transaction as reconciled." border="0"></a>
</td>
<td class="mi" align="right" nowrap="nowrap" width="75">
<div class="statementcolmn2"><span class="textn2">$1,234.56</span></div>
</td>
<td class="module1bkgd4" width="1"><img src="spacer-image-url" alt="" height="1" width="1"></td>
<td class="mi" nowrap="nowrap" width="11%">
<div class="statementcolmn2"><span class="textn2">$8,910.11</span></div>
</td>
<td width="10"><img src="spacer-image-url" alt="" border="0" width="10"></td>
</tr>
</nowiki></pre>

==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
enter notes here

=== Citibank ===
enter notes here

=== ING ===

=== Amazon.com ===
enter notes here

=== eBay ===
enter notes here

=== Paypal ===
enter notes here

=== Quicken ===
enter notes here

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-examples

2007-08-03T17:38:55Z

ClayNewton: /* How people trade today */

trade-examples

2007-08-03T17:38:10Z

ClayNewton: First update that actually conforms to examples example.

trade-examples

2007-08-03T16:06:41Z

ClayNewton:

__TOC__
== Introduction ==
This is an exploratory page to document trade examples currently published around the web. Typically, the metadata associated with this content is stored in non-semantic markup and proprietary formats. The purpose of the studies on this page is to serve as background for the design of a simple distributed trade microformat.

There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

== Authors ==
* [[ClayNewton | Clay Newton]]

== Trade Examples ==
=== Bank of America ===
[http://www.bankofamerica.com Bank of America]
==== Deposit Accounts ====
Grouped by Account
* date
** posted
** scheduled
* payee Name
* type
** check image url (front)
** check image url (back)
* status
* amount
* running balance
* fee info
* amount held
* date held
==== Keep the Change ====
* date posted
* # of transactions
** transaction description
** transaction url
** is matched?
** transaction amount
* amount you keep
* to account
* no transfer
==== Card Accounts ====
* date
** transaction
** posted
* description
* amount
* running balance
* card type
* transaction type
* periodic rate
* reference number
* reward
** reward type
** reward url

=== Wells Fargo ===
enter notes here

=== Citibank ===
enter notes here

=== ING ===

=== Amazon.com ===
enter notes here

=== eBay ===
enter notes here

=== Paypal ===
enter notes here

=== Quicken ===
enter notes here

=== Quickbooks ===
enter notes here

=== Wesabe ===
enter notes here

== See Also ==
* [[trade-branstorming | Brainstorming trade]]

trade-brainstorming

2007-08-03T16:04:01Z

ClayNewton:

[[trade-examples | See examples of trade]].

__TOC__

== Specification ==

== Introduction ==
There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

== Format ==
There are many data formats used in financial systems to represent transactions. The vast majority of these are proprietary, typically resulting from an evolution from paper-based accounting to mainframe computing to electronic interchange networks to the web and now to mobile systems.

=== In General ===
A simple semantic format using (like [[hcard | hCard]]) object/property names in lower-case for class names. Financial transaction attributes would be mapped to nested XHTML elements.

=== Root Class Name ===
The root class name could "record". "Record" is a common financial industry term. Records map to all data collected in the form of a "transaction". The expression of a record is itself considered a transaction.

=== Properties and Sub-properties ===
The properties of a trade are represented by elements inside the trade root. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
properties (sub-properties in parentheses like this)

'''Required:'''
* '''date-posted''' (date-transacted, date-created, date-scheduled)
* '''to-account''' (to-account-number, to-account-holder)
* '''amount-posted'''
Optional:
* from-account (from-account-number, from-account-holder)
* date-hold-start (date-hold-end, amount-held)
* status
* type
* reference-number (card-type, periodic-rate)
* fee-amount (fee-type, fee-description)
* category-name (category-id, category-amount)
* image-type (image-front-uri, image-back-uri)
* tax-flag (tax-flag-type, tax-flag-amount)

=== Singular vs. Plural Properties ===
Singular properties:
'date-posted', 'date-transacted', 'dated-created', 'date-scheduled', 'from-account', 'from-account-number', 'from-account-holder', 'to-account', 'to-account-number', 'to-account-holder', 'amount-posted status', 'type', 'card-type', 'periodic-rate'. For properties which are singular, the first descendant element with that class should take effect, any others being ignored.

All other properties can be plural. Each class instance of such properties creates a new instance of that property.

== Copyright ==
Per the public domain release on the author's user page ([[User:ClayNewton|Clay Newton]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== To Dos ==
* Complete survey of [[financial transaction attributes]]
* Discuss each of the elements and attributes in the property list
* Determine, to the degree possible, if this is folly.

trade-examples

2007-08-03T15:59:11Z

ClayNewton:

trade-examples

2007-08-03T15:57:13Z

ClayNewton:

trade-examples

2007-08-03T15:53:55Z

ClayNewton:

trade-examples

2007-08-03T15:53:03Z

ClayNewton: added Keep the Change

trade-examples

2007-08-03T15:48:51Z

ClayNewton: /* DDA/SDA Accounts */

trade-examples

2007-08-03T15:47:59Z

ClayNewton:

hTrade

2007-08-03T15:47:52Z

ClayNewton:

'''Creation of a draft or even naming a proposed microformat for trade is premature per the [[process]]. Please see the [[process]] page for how to go about first doing research with collecting examples etc. and then move these thoughts, once reconsidered in light of research, to a [[trade-brainstorming]] page. Thanks.''' [[User:Tantek|Tantek]] 00:54, 3 Aug 2007 (PDT)

Tantek, you answered my question re: folly. Moving notes into appropriate process. Added [[trade-examples]] --[[User:ClayNewton|ClayNewton]] 08:37, 3 Aug 2007 (PDT)

hTrade

2007-08-03T15:37:51Z

ClayNewton:

'''Creation of a draft or even naming a proposed microformat for trade is premature per the [[process]]. Please see the [[process]] page for how to go about first doing research with collecting examples etc. and then move these thoughts, once reconsidered in light of research, to a [[trade-brainstorming]] page. Thanks.''' [[User:Tantek|Tantek]] 00:54, 3 Aug 2007 (PDT)

Tantek, you answered my question re: folly. Moving notes into appropriate process. --[[User:ClayNewton|ClayNewton]] 08:37, 3 Aug 2007 (PDT)

hTrade

2007-08-03T05:59:37Z

ClayNewton:

<h1>hTrade</h1>

hTrade is a proposed new [[microformats | microformat]] that would provide a common means of representing financial transactions.

'''Please note that this in a draft spec'''--[[User:ClayNewton|ClayNewton]] 22:52, 2 Aug 2007 (PDT)

__TOC__

== Specification ==

== Introduction ==
There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

== Format ==
There are many data formats used in financial systems to represent transactions. The vast majority of these are proprietary, typically resulting from an evolution from paper-based accounting to mainframe computing to electronic interchange networks to the web and now to mobile systems.

=== In General ===
A simple semantic format using (like [[hcard | hCard]]) object/property names in lower-case for class names. Financial transaction attributes would be mapped to nested XHTML elements.

=== Root Class Name ===
The root class name for an hTrade is "record". An element with a class name of "record" is itself called an ''hTrade''.

=== Properties and Sub-properties ===
The properties of an hTrade are represented by elements inside the hTrade. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
hTrade properties (sub-properties in parentheses like this)

'''Required:'''
* '''date-posted''' (date-transacted, date-created, date-scheduled)
* '''to-account''' (to-account-number, to-account-holder)
* '''amount-posted'''
Optional:
* from-account (from-account-number, from-account-holder)
* date-hold-start (date-hold-end, amount-held)
* status
* type
* reference-number (card-type, periodic-rate)
* fee-amount (fee-type, fee-description)
* category-name (category-id, category-amount)
* image-type (image-front-uri, image-back-uri)
* tax-flag (tax-flag-type, tax-flag-amount)

=== Singular vs. Plural Properties ===
Singular properties:
'date-posted', 'date-transacted', 'dated-created', 'date-scheduled', 'from-account', 'from-account-number', 'from-account-holder', 'to-account', 'to-account-number', 'to-account-holder', 'amount-posted status', 'type', 'card-type', 'periodic-rate'. For properties which are singular, the first descendant element with that class should take effect, any others being ignored.

All other properties can be plural. Each class instance of such properties creates a new instance of that property.

== Copyright ==
Per the public domain release on the author's user page ([[User:ClayNewton|Clay Newton]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== To Dos ==
* Complete survey of [[financial transaction attributes]]
* Discuss each of the elements and attributes in the property list
* Determine, to the degree possible, if this is folly.

hTrade

2007-08-03T05:55:21Z

ClayNewton: /* Copyright */

hTrade

2007-08-03T05:54:57Z

ClayNewton: /* Property List */

<h1>hTrade</h1>

hTrade is a proposed new [[microformats | microformat]] that would provide a common means of representing financial transactions.

'''Please note that this in a draft spec'''--[[User:ClayNewton|ClayNewton]] 22:52, 2 Aug 2007 (PDT)

__TOC__

== Specification ==

== Introduction ==
There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

== Format ==
There are many data formats used in financial systems to represent transactions. The vast majority of these are proprietary, typically resulting from an evolution from paper-based accounting to mainframe computing to electronic interchange networks to the web and now to mobile systems.

=== In General ===
A simple semantic format using (like [[hcard | hCard]]) object/property names in lower-case for class names. Financial transaction attributes would be mapped to nested XHTML elements.

=== Root Class Name ===
The root class name for an hTrade is "record". An element with a class name of "record" is itself called an ''hTrade''.

=== Properties and Sub-properties ===
The properties of an hTrade are represented by elements inside the hTrade. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
hTrade properties (sub-properties in parentheses like this)

'''Required:'''
* '''date-posted''' (date-transacted, date-created, date-scheduled)
* '''to-account''' (to-account-number, to-account-holder)
* '''amount-posted'''
Optional:
* from-account (from-account-number, from-account-holder)
* date-hold-start (date-hold-end, amount-held)
* status
* type
* reference-number (card-type, periodic-rate)
* fee-amount (fee-type, fee-description)
* category-name (category-id, category-amount)
* image-type (image-front-uri, image-back-uri)
* tax-flag (tax-flag-type, tax-flag-amount)

=== Singular vs. Plural Properties ===
Singular properties:
'date-posted', 'date-transacted', 'dated-created', 'date-scheduled', 'from-account', 'from-account-number', 'from-account-holder', 'to-account', 'to-account-number', 'to-account-holder', 'amount-posted status', 'type', 'card-type', 'periodic-rate'. For properties which are singular, the first descendant element with that class should take effect, any others being ignored.

All other properties can be plural. Each class instance of such properties creates a new instance of that property.

== Copyright ==
Per the public domain release on the authors' user pages ([[User:ClayNewton|Clay Newton]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== To Dos ==
* Complete survey of [[financial transaction attributes]]
* Draft

hTrade

2007-08-03T05:53:23Z

ClayNewton: /* Property List */

<h1>hTrade</h1>

hTrade is a proposed new [[microformats | microformat]] that would provide a common means of representing financial transactions.

'''Please note that this in a draft spec'''--[[User:ClayNewton|ClayNewton]] 22:52, 2 Aug 2007 (PDT)

__TOC__

== Specification ==

== Introduction ==
There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

== Format ==
There are many data formats used in financial systems to represent transactions. The vast majority of these are proprietary, typically resulting from an evolution from paper-based accounting to mainframe computing to electronic interchange networks to the web and now to mobile systems.

=== In General ===
A simple semantic format using (like [[hcard | hCard]]) object/property names in lower-case for class names. Financial transaction attributes would be mapped to nested XHTML elements.

=== Root Class Name ===
The root class name for an hTrade is "record". An element with a class name of "record" is itself called an ''hTrade''.

=== Properties and Sub-properties ===
The properties of an hTrade are represented by elements inside the hTrade. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
hTrade properties (sub-properties in parentheses like this)

'''Required:'''
* '''date-posted''' (date-transacted, date-created, date-scheduled)
* '''to-account''' (to-account-number, to-account-holder)
* '''amount-posted'''
Optional:
* from-account (from-account-number, from-account-holder)
* date-hold-start (date-hold-end, amount-held)
* status
* type
* reference-number (card-type, periodic-rate)
* fee-amount (fee-type, fee-description)
* category-name (category-id, category-amount)
* image-type (image-front-url, image-back-url)
* tax-flag (tax-flag-type, tax-flag-amount)

=== Singular vs. Plural Properties ===
Singular properties:
'date-posted', 'date-transacted', 'dated-created', 'date-scheduled', 'from-account', 'from-account-number', 'from-account-holder', 'to-account', 'to-account-number', 'to-account-holder', 'amount-posted status', 'type', 'card-type', 'periodic-rate'. For properties which are singular, the first descendant element with that class should take effect, any others being ignored.

All other properties can be plural. Each class instance of such properties creates a new instance of that property.

== Copyright ==
Per the public domain release on the authors' user pages ([[User:ClayNewton|Clay Newton]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== To Dos ==
* Complete survey of [[financial transaction attributes]]
* Draft

hTrade

2007-08-03T05:52:40Z

ClayNewton: /* Property List */

<h1>hTrade</h1>

hTrade is a proposed new [[microformats | microformat]] that would provide a common means of representing financial transactions.

'''Please note that this in a draft spec'''--[[User:ClayNewton|ClayNewton]] 22:52, 2 Aug 2007 (PDT)

__TOC__

== Specification ==

== Introduction ==
There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

== Format ==
There are many data formats used in financial systems to represent transactions. The vast majority of these are proprietary, typically resulting from an evolution from paper-based accounting to mainframe computing to electronic interchange networks to the web and now to mobile systems.

=== In General ===
A simple semantic format using (like [[hcard | hCard]]) object/property names in lower-case for class names. Financial transaction attributes would be mapped to nested XHTML elements.

=== Root Class Name ===
The root class name for an hTrade is "record". An element with a class name of "record" is itself called an ''hTrade''.

=== Properties and Sub-properties ===
The properties of an hTrade are represented by elements inside the hTrade. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
hTrade properties (sub-properties in parentheses like this)

'''Required:'''
* '''date-posted''' (date-transacted, dated-created, date-scheduled)
* '''to-account''' (to-account-number, to-account-holder)
* '''amount-posted'''
Optional:
* from-account (from-account-number, from-account-holder)
* date-hold-start (date-hold-end, amount-held)
* status
* type
* reference-number (card-type, periodic-rate)
* fee-amount (fee-type, fee-description)
* category-name (category-id, category-amount)
* image-type (image-front-url, image-back-url)
* tax-flag (tax-flag-type, tax-flag-amount)

=== Singular vs. Plural Properties ===
Singular properties:
'date-posted', 'date-transacted', 'dated-created', 'date-scheduled', 'from-account', 'from-account-number', 'from-account-holder', 'to-account', 'to-account-number', 'to-account-holder', 'amount-posted status', 'type', 'card-type', 'periodic-rate'. For properties which are singular, the first descendant element with that class should take effect, any others being ignored.

All other properties can be plural. Each class instance of such properties creates a new instance of that property.

== Copyright ==
Per the public domain release on the authors' user pages ([[User:ClayNewton|Clay Newton]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== To Dos ==
* Complete survey of [[financial transaction attributes]]
* Draft

hTrade

2007-08-03T05:52:03Z

ClayNewton:

<h1>hTrade</h1>

hTrade is a proposed new [[microformats | microformat]] that would provide a common means of representing financial transactions.

'''Please note that this in a draft spec'''--[[User:ClayNewton|ClayNewton]] 22:52, 2 Aug 2007 (PDT)

__TOC__

== Specification ==

== Introduction ==
There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

== Format ==
There are many data formats used in financial systems to represent transactions. The vast majority of these are proprietary, typically resulting from an evolution from paper-based accounting to mainframe computing to electronic interchange networks to the web and now to mobile systems.

=== In General ===
A simple semantic format using (like [[hcard | hCard]]) object/property names in lower-case for class names. Financial transaction attributes would be mapped to nested XHTML elements.

=== Root Class Name ===
The root class name for an hTrade is "record". An element with a class name of "record" is itself called an ''hTrade''.

=== Properties and Sub-properties ===
The properties of an hTrade are represented by elements inside the hTrade. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
hTrade properties (sub-properties in parentheses like this)

'''Required:'''
* '''date-posted''' (date-transacted, dated-created, date-scheduled)
* '''to-account to-account-number''' (to-account-holder)
* '''amount-posted'''
Optional:
* from-account (from-account-number, from-account-holder)
* date-hold-start (date-hold-end, amount-held)
* status
* type
* reference-number (card-type, periodic-rate)
* fee-amount (fee-type, fee-description)
* category-name (category-id, category-amount)
* image-type (image-front-url, image-back-url)
* tax-flag (tax-flag-type, tax-flag-amount)

=== Singular vs. Plural Properties ===
Singular properties:
'date-posted', 'date-transacted', 'dated-created', 'date-scheduled', 'from-account', 'from-account-number', 'from-account-holder', 'to-account', 'to-account-number', 'to-account-holder', 'amount-posted status', 'type', 'card-type', 'periodic-rate'. For properties which are singular, the first descendant element with that class should take effect, any others being ignored.

All other properties can be plural. Each class instance of such properties creates a new instance of that property.

== Copyright ==
Per the public domain release on the authors' user pages ([[User:ClayNewton|Clay Newton]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== To Dos ==
* Complete survey of [[financial transaction attributes]]
* Draft

hTrade

2007-08-03T05:51:13Z

ClayNewton:

<h1>hTrade</h1>

hTrade is a proposed new [[microformats | microformat]] that would provide a common means of representing financial transactions.

__TOC__

== Specification ==

== Introduction ==
There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, [[PersonalFinanceManager | PFM]] applications, etc. A standardized format would facilitate integration between vendors, financial institutions and applications to provide for far more robust financial accounting integration.

== Format ==
There are many data formats used in financial systems to represent transactions. The vast majority of these are proprietary, typically resulting from an evolution from paper-based accounting to mainframe computing to electronic interchange networks to the web and now to mobile systems.

=== In General ===
A simple semantic format using (like [[hcard | hCard]]) object/property names in lower-case for class names. Financial transaction attributes would be mapped to nested XHTML elements.

=== Root Class Name ===
The root class name for an hTrade is "record". An element with a class name of "record" is itself called an ''hTrade''.

=== Properties and Sub-properties ===
The properties of an hTrade are represented by elements inside the hTrade. Elements with class names of the listed properties represent the values of those properties. Some properties have sub-properties, and those are represented by elements inside the elements for properties.

=== Property List ===
hTrade properties (sub-properties in parentheses like this)

'''Required:'''
* '''date-posted''' (date-transacted, dated-created, date-scheduled)
* '''to-account to-account-number''' (to-account-holder)
* '''amount-posted'''
Optional:
* from-account (from-account-number, from-account-holder)
* date-hold-start (date-hold-end, amount-held)
* status
* type
* reference-number (card-type, periodic-rate)
* fee-amount (fee-type, fee-description)
* category-name (category-id, category-amount)
* image-type (image-front-url, image-back-url)
* tax-flag (tax-flag-type, tax-flag-amount)

=== Singular vs. Plural Properties ===
Singular properties:
'date-posted', 'date-transacted', 'dated-created', 'date-scheduled', 'from-account', 'from-account-number', 'from-account-holder', 'to-account', 'to-account-number', 'to-account-holder', 'amount-posted status', 'type', 'card-type', 'periodic-rate'. For properties which are singular, the first descendant element with that class should take effect, any others being ignored.

All other properties can be plural. Each class instance of such properties creates a new instance of that property.

== Copyright ==
Per the public domain release on the authors' user pages ([[User:ClayNewton|Clay Newton]]) this specification is released into the public domain.

{{MicroFormatPublicDomainContributionStatement}}

== To Dos ==
* Complete survey of [[financial transaction attributes]]
* Draft

hTrade

2007-08-03T05:31:57Z

ClayNewton: