hTrade: Difference between revisions
ClayNewton (talk | contribs) No edit summary |
ClayNewton (talk | contribs) mNo edit summary |
||
| Line 2: | Line 2: | ||
hTrade is a proposed new [[microformats | microformat]] that would provide a common means of representing financial transactions. | hTrade is a proposed new [[microformats | microformat]] that would provide a common means of representing financial transactions. | ||
__TOC__ | __TOC__ | ||
| Line 11: | Line 9: | ||
== Introduction == | == 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. | 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. | |||
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. | |||
== To Dos == | == To Dos == | ||
* Complete survey of [[financial transaction attributes]] | * Complete survey of [[financial transaction attributes]] | ||
* Draft | * Draft | ||
Revision as of 05:31, 3 August 2007
hTrade
hTrade is a proposed new microformat that would provide a common means of representing financial transactions.
Specification
Introduction
There are many examples of financial transactions across the web and in desktop applications, including bank statements, purchase receipts, wishlists, 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.
A simple semantic format using (like hCard) object/property names in lower-case for class names. Financial transaction attributes would be mapped to nested XHTML elements.
To Dos
- Complete survey of financial transaction attributes
- Draft