trade-brainstorming - Revision history

Lkonkiel: /* Root Class Name */

2007-08-21T14:29:34Z

Root Class Name

← Older revision		Revision as of 14:29, 21 August 2007
Line 15:		Line 15:

	=== Root Class Name ===		=== 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.		The root class name could be "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 ===		=== Properties and Sub-properties ===

ClayNewton: /* Singular vs. Plural Properties */

2007-08-07T03:52:21Z

Singular vs. Plural Properties

← Older revision		Revision as of 03:52, 7 August 2007
Line 42:		Line 42:
	=== Singular vs. Plural Properties ===		=== Singular vs. Plural Properties ===
	Singular 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.		'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.		All other properties can be plural. Each class instance of such properties creates a new instance of that property.

ClayNewton: /* Property List */

2007-08-07T03:51:50Z

Property List

← Older revision		Revision as of 03:51, 7 August 2007
Line 24:		Line 24:

	'''Required:'''		'''Required:'''
	* '''post-date''' ~~(date-type)~~		* '''post-date'''
	* '''to-account''' (to-account-number, to-account-holder)		* '''to-account''' (to-account-number, to-account-holder)
	* '''amount-posted'''		* '''amount-posted'''

ClayNewton: /* Property List */

2007-08-07T03:51:19Z

Property List

← Older revision		Revision as of 03:51, 7 August 2007
Line 24:		Line 24:

	'''Required:'''		'''Required:'''
	* '''date''' (date-type)		* '''post-date''' (date-type)
	* '''to-account''' (to-account-number, to-account-holder)		* '''to-account''' (to-account-number, to-account-holder)
	* '''amount-posted'''		* '''amount-posted'''
	Optional:		Optional:
			* date (date-type)
	* from-account (from-account-number, from-account-holder)		* from-account (from-account-number, from-account-holder)
	* date-hold-start (date-hold-end, amount-held)		* date-hold-start (date-hold-end, amount-held)

ClayNewton: /* Property List */

2007-08-03T20:02:30Z

Property List

← Older revision		Revision as of 20:02, 3 August 2007
Line 35:		Line 35:
	* fee-amount (fee-type, fee-description)		* fee-amount (fee-type, fee-description)
	* category-name (category-id, category-amount)		* category-name (category-id, category-amount)
	* image-type (image-front-~~uri~~, image-back-~~uri~~)		* image-type (image-front-url, image-back-url)
	* tax-flag (tax-flag-type, tax-flag-amount)		* tax-flag (tax-flag-type, tax-flag-amount)
			* return-url (return-description)

	=== Singular vs. Plural Properties ===		=== Singular vs. Plural Properties ===

ClayNewton: /* See Also */

2007-08-03T18:06:57Z

ClayNewton at 18:06, 3 August 2007

2007-08-03T18:06:42Z

← Older revision		Revision as of 18:06, 3 August 2007
Line 43:		Line 43:

	All other properties can be plural. Each class instance of such properties creates a new instance of that property.		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]

ClayNewton at 18:05, 3 August 2007

2007-08-03T18:05:51Z

← Older revision		Revision as of 18:05, 3 August 2007
Line 24:		Line 24:

	'''Required:'''		'''Required:'''
	* '''date~~-posted~~''' (date-~~transacted, date-created, date-scheduled~~)		* '''date''' (date-type)
	* '''to-account''' (to-account-number, to-account-holder)		* '''to-account''' (to-account-number, to-account-holder)
	* '''amount-posted'''		* '''amount-posted'''
Line 40:		Line 40:
	=== Singular vs. Plural Properties ===		=== Singular vs. Plural Properties ===
	Singular 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.		'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.		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.

ClayNewton at 16:04, 3 August 2007

2007-08-03T16:04:01Z

New page

[[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.

← Older revision		Revision as of 18:06, 3 August 2007
Line 45:		Line 45:

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