Microformats Wiki - User contributions [en]

bill-brainstorming

2011-04-24T16:36:04Z

MovGP0: /* Schema */ highlighted recommended

<entry-title>hBill 0.1</entry-title>
{{Template:DraftSpecification}}

hBill is a microformat that allows to provide metainformation on a bill, so that customers can do transactions more easily.
__TOC__
== Draft Specification ==
<div class="vcard">
;Editor/Author
:Johann Dirry
</div>

[[#Copyright|copyright]] and [[#Patents|patents]] statements apply.

== Status ==
hBill 0.1 is a microformats.org draft specification. Public discussion on hBill takes place on [[hbill-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss mailing list].

=== Available languages ===
The English version of this specification is the only normative version.

=== Errata and Updates ===
Known errors and issues in this specification are corrected in [[hbill-issues-resolved|resolved]] and [[hbill-issues-closed|closed]] issues. Please check there before reporting [[hbill-issues|issues]].

== Introduction ==
hBill is a [[microformat]] for identifying semantic information in electronic bills. hBill content is easily added to bills that are available in xHTML or HTML format.

{{rfc-2119-intro}}

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles}}

=== Schema ===
Schema elements follow the microformat pattern of prefixing a unique identifier (in this case, '<code>h</code>') on the outermost container element. The parts of this microformat are based on analysis of bills from online shops.

The hBill schema consists of the following:

* '''<code>hbill</code>'''. ''optional''.
** '''<code>iban</code>'''. '''required'''. IBAN code as specified in [[iso-13616-1|ISO 13616-1:2007 Part 1]].
** '''<code>bic</code>'''. '''required'''. BIC/SWIFT code as specified in [[iso-9362|ISO 9362]].
** '''<code>accountnumber</code>'''. ''optional''. Country specific banking account number.
** '''<code>bankcode</code>'''. ''optional''. Country specific bank code.
** '''<code>billingsum</code>'''. '''required'''. [http://www.w3.org/TR/xmlschema-2/#double xs:double]. Ammout of money the customer has to submit to the selling party.
** '''<code>currency</code>'''. '''required'''. [[iso-4217|ISO 4217]].
** '''<code>receiver</code>'''. '''required'''. [[hcard]] information of the money receiver.
** '''<code>receivingbank</code>'''. ''recommended''. [[hcard]] information of the money receiving bank.
** '''<code>billnumber</code>'''. ''recommended''. [http://www.w3.org/TR/xmlschema-2/#string xs:string]. May be required by the selling party to identify the bill.
** '''<code>billingdate</code>'''. '''required'''. [http://www.w3.org/TR/xmlschema-2/#date xs:date] or [http://www.w3.org/TR/xmlschema-2/#dateTime xs:dateTime]. Date when the bill was created.

=== Field and Element Details ===

==== hbill ====
* a Bill element is identified by the class <code>hbill</code>
* a document may have multiple bill elements
* if there is only bill in the document, the <code>hbill</code> element ''may'' be missing.
** if the <code>hbill</code> element is missing, it is assumed to be the document

==== iban ====
* the IBAN code of the account the money has to get transfered to
* the <code>hbill</code> element ''requires'' the IBAN code

==== bic ====
* the BIC/SWIFT code the money has to get transfered to
* the <code>hbill</code> element ''requires'' the BIC/SWIFT code, because the user ''may'' need it

==== accountnumber ====
* a country specific banking account number
* the <code>accountnumber</code> element is ''optional''
* ''may'' be provided for national transactions

==== bankcode ====
* a country specific bank code
* the <code>bankcode</code> element is ''optional''
* ''may'' be provided for national transactions

==== billingsum ====
* the ammout of money the customer has to submit to the selling party
* the <code>hbill</code> element ''requires'' the <code>billingsum</code> element

==== currency ====
* the currency of the ammount of money the customer has to submit to the selling party
* the <code>hbill</code> element ''requires'' the <code>currency</code> element

==== receiver ====
* [[hcard]] information of the money receiver
* the <code>hbill</code> element ''requires'' the <code>receiver</code> element

==== receivingbank ====
* [[hcard]] information of the money receiving bank
* it is ''recommended'' to use the <code>receivingbank</code> element, because the customer ''may not'' be able to get this information based on the IBAN or BIC/SWIFT code

==== billnumber ====
* it is ''recommended'' to provide this information, so its possible to identify the bill correctly
* some parties ''may'' ''require'' the customer to provide this information in another way (ie. manually filling the 'purpose' or 'customer data' field), which ''should not'' be done
* the <code>hbill</code> element ''requires'' the <code>billnumber</code> element

==== billingdate ====
* date when the bill was created
* ''may'' also provide time and timezone information
* the <code>hbill</code> element ''requires'' the <code>billdate</code> element

== Examples ==
''todo''

== Copyright ==
{{MicroFormatPublicDomainContributionStatement}}.

== Patents ==
{{MicroFormatPatentStatement}}

== References ==
=== Normative References ===
; ISO
* [[iso-13616-1|ISO 13616-1]]
* [[iso-9362|ISO 9362]]
* [[iso-4217|ISO 4217]]
* [[iso-8601|ISO 8601]]

; W3C
* [http://www.w3.org/TR/xmlschema-2/#double xmls:double]
* [http://www.w3.org/TR/xmlschema-2/#date xs:date]

; microformats
* [[hcard]]
* [[adr]]

[[Category:Draft Specifications]]

bill-issues

2011-04-24T16:31:13Z

MovGP0: /* Net, Gross and Tara */ +hProduct, +hListing

<entry-title>hBill issues</entry-title>

== closed issues ==
See: [[hbill-issues-closed]]

== resolved issues ==
See: [[hbill-issues-resolved]]

== open issues ==
=== Net, Gross and Tara ===
{{OpenIssue}} submitted by [[User:MovGP0|MovGP0]] 16:17, 24 April 2011 (UTC)

hBill shema ''should'' allow to address
* net price (price without tax)
* tara price (tax)
* gross price (price including tax)
It ''may'' do so for every <code>item</code> on the bill using [[hProduct]] and [[hListing]] standards. 
-- [[User:MovGP0|MovGP0]] 16:17, 24 April 2011 (UTC)

=== Shipping ===
{{OpenIssue}} submitted by [[User:MovGP0|MovGP0]] 16:17, 24 April 2011 (UTC)

hBill ''may'' get extended for
* shipping address based on [[hcard]] and [[adr]]
* customer name and address based on [[hcard]]
-- [[User:MovGP0|MovGP0]] 16:17, 24 April 2011 (UTC)

bill-issues

2011-04-24T16:26:23Z

MovGP0: /* open issues */ empty line

<entry-title>hBill issues</entry-title>

== closed issues ==
See: [[hbill-issues-closed]]

== resolved issues ==
See: [[hbill-issues-resolved]]

== open issues ==
=== Net, Gross and Tara ===
{{OpenIssue}} submitted by [[User:MovGP0|MovGP0]] 16:17, 24 April 2011 (UTC)

hBill shema ''should'' allow to address
* net price (price without tax)
* tara price (tax)
* gross price (price including tax)
It ''may'' do so for every <code>item</code> on the bill. 
-- [[User:MovGP0|MovGP0]] 16:17, 24 April 2011 (UTC)

=== Shipping ===
{{OpenIssue}} submitted by [[User:MovGP0|MovGP0]] 16:17, 24 April 2011 (UTC)

hBill ''may'' get extended for
* shipping address based on [[hcard]] and [[adr]]
* customer name and address based on [[hcard]]
-- [[User:MovGP0|MovGP0]] 16:17, 24 April 2011 (UTC)

bill-brainstorming

2011-04-24T16:22:10Z

MovGP0: /* Status */ no translations (yet)

<entry-title>hBill 0.1</entry-title>
{{Template:DraftSpecification}}

hBill is a microformat that allows to provide metainformation on a bill, so that customers can do transactions more easily.
__TOC__
== Draft Specification ==
<div class="vcard">
;Editor/Author
:Johann Dirry
</div>

[[#Copyright|copyright]] and [[#Patents|patents]] statements apply.

== Status ==
hBill 0.1 is a microformats.org draft specification. Public discussion on hBill takes place on [[hbill-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss mailing list].

=== Available languages ===
The English version of this specification is the only normative version.

=== Errata and Updates ===
Known errors and issues in this specification are corrected in [[hbill-issues-resolved|resolved]] and [[hbill-issues-closed|closed]] issues. Please check there before reporting [[hbill-issues|issues]].

== Introduction ==
hBill is a [[microformat]] for identifying semantic information in electronic bills. hBill content is easily added to bills that are available in xHTML or HTML format.

{{rfc-2119-intro}}

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles}}

=== Schema ===
Schema elements follow the microformat pattern of prefixing a unique identifier (in this case, '<code>h</code>') on the outermost container element. The parts of this microformat are based on analysis of bills from online shops.

The hBill schema consists of the following:

* '''<code>hbill</code>'''. optional.
** '''<code>iban</code>'''. required. IBAN code as specified in [[iso-13616-1|ISO 13616-1:2007 Part 1]].
** '''<code>bic</code>'''. required. BIC/SWIFT code as specified in [[iso-9362|ISO 9362]].
** '''<code>accountnumber</code>'''. optional. Country specific banking account number.
** '''<code>bankcode</code>'''. optional. Country specific bank code.
** '''<code>billingsum</code>'''. required. [http://www.w3.org/TR/xmlschema-2/#double xs:double]. Ammout of money the customer has to submit to the selling party.
** '''<code>currency</code>'''. required. [[iso-4217|ISO 4217]].
** '''<code>receiver</code>'''. required. [[hcard]] information of the money receiver.
** '''<code>receivingbank</code>'''. recommended. [[hcard]] information of the money receiving bank.
** '''<code>billnumber</code>'''. recommended. [http://www.w3.org/TR/xmlschema-2/#string xs:string]. May be required by the selling party to identify the bill.
** '''<code>billingdate</code>'''. required. [http://www.w3.org/TR/xmlschema-2/#date xs:date] or [http://www.w3.org/TR/xmlschema-2/#dateTime xs:dateTime]. Date when the bill was created.

=== Field and Element Details ===

==== hbill ====
* a Bill element is identified by the class <code>hbill</code>
* a document may have multiple bill elements
* if there is only bill in the document, the <code>hbill</code> element ''may'' be missing.
** if the <code>hbill</code> element is missing, it is assumed to be the document

==== iban ====
* the IBAN code of the account the money has to get transfered to
* the <code>hbill</code> element ''requires'' the IBAN code

==== bic ====
* the BIC/SWIFT code the money has to get transfered to
* the <code>hbill</code> element ''requires'' the BIC/SWIFT code, because the user ''may'' need it

==== accountnumber ====
* a country specific banking account number
* the <code>accountnumber</code> element is ''optional''
* ''may'' be provided for national transactions

==== bankcode ====
* a country specific bank code
* the <code>bankcode</code> element is ''optional''
* ''may'' be provided for national transactions

==== billingsum ====
* the ammout of money the customer has to submit to the selling party
* the <code>hbill</code> element ''requires'' the <code>billingsum</code> element

==== currency ====
* the currency of the ammount of money the customer has to submit to the selling party
* the <code>hbill</code> element ''requires'' the <code>currency</code> element

==== receiver ====
* [[hcard]] information of the money receiver
* the <code>hbill</code> element ''requires'' the <code>receiver</code> element

==== receivingbank ====
* [[hcard]] information of the money receiving bank
* it is ''recommended'' to use the <code>receivingbank</code> element, because the customer ''may not'' be able to get this information based on the IBAN or BIC/SWIFT code

==== billnumber ====
* it is ''recommended'' to provide this information, so its possible to identify the bill correctly
* some parties ''may'' ''require'' the customer to provide this information in another way (ie. manually filling the 'purpose' or 'customer data' field), which ''should not'' be done
* the <code>hbill</code> element ''requires'' the <code>billnumber</code> element

==== billingdate ====
* date when the bill was created
* ''may'' also provide time and timezone information
* the <code>hbill</code> element ''requires'' the <code>billdate</code> element

== Examples ==
''todo''

== Copyright ==
{{MicroFormatPublicDomainContributionStatement}}.

== Patents ==
{{MicroFormatPatentStatement}}

== References ==
=== Normative References ===
; ISO
* [[iso-13616-1|ISO 13616-1]]
* [[iso-9362|ISO 9362]]
* [[iso-4217|ISO 4217]]
* [[iso-8601|ISO 8601]]

; W3C
* [http://www.w3.org/TR/xmlschema-2/#double xmls:double]
* [http://www.w3.org/TR/xmlschema-2/#date xs:date]

; microformats
* [[hcard]]
* [[adr]]

[[Category:Draft Specifications]]

bill-issues

2011-04-24T16:19:15Z

MovGP0: /* open issues */

<entry-title>hBill issues</entry-title>

== closed issues ==
See: [[hbill-issues-closed]]

== resolved issues ==
See: [[hbill-issues-resolved]]

== open issues ==
=== Net, Gross and Tara ===
{{OpenIssue}} submitted by [[User:MovGP0|MovGP0]] 16:17, 24 April 2011 (UTC)
hBill shema ''should'' allow to address
* net price (price without tax)
* tara price (tax)
* gross price (price including tax)
It ''may'' do so for every <code>item</code> on the bill. 
-- [[User:MovGP0|MovGP0]] 16:17, 24 April 2011 (UTC)

=== Shipping ===
{{OpenIssue}} submitted by [[User:MovGP0|MovGP0]] 16:17, 24 April 2011 (UTC)
hBill ''may'' get extended for
* shipping address based on [[hcard]] and [[adr]]
* customer name and address based on [[hcard]]
-- [[User:MovGP0|MovGP0]] 16:17, 24 April 2011 (UTC)

bill-issues

2011-04-24T16:17:03Z

MovGP0: New page: <entry-title>hBill issues</entry-title> == closed issues == See: hbill-issues-closed == resolved issues == See: hbill-issues-resolved == open issues == === Net, Gross and Tara =...

<entry-title>hBill issues</entry-title>

== closed issues ==
See: [[hbill-issues-closed]]

== resolved issues ==
See: [[hbill-issues-resolved]]

== open issues ==
=== Net, Gross and Tara ===
hBill shema ''should'' allow to address
* net price (price without tax)
* tara price (tax)
* gross price (price including tax)

It ''may'' do so for every <code>item</code> on the bill. 
-- [[User:MovGP0|MovGP0]] 16:17, 24 April 2011 (UTC)

=== Shipping ===
hBill ''may'' get extended for
* shipping address based on [[hcard]] and [[adr]]
* customer name and address based on [[hcard]]
-- [[User:MovGP0|MovGP0]] 16:17, 24 April 2011 (UTC)

Main Page

2011-04-24T16:08:45Z

MovGP0: /* Drafts */ typo.

<entry-title>Welcome to the microformats wiki!</entry-title>
__TOC__
Please start with the [[introduction]] page and read [[how-to-play]] before making any edits.

==Introduction==
This wiki is the central resource of the microformats community. You'll find current versions of published microformat specifications, specification drafts and publishing patterns. The wiki also hosts development resources, such as brainstorming pages for new formats and issue tracking pages for all current and in-development microformats.

== Get Started==
To get started with microformats:

* First, be familiar writing your pages and applications with semantically rich, descriptive, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.
* Learn about microformats from the [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] pages.
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.
* Want to learn more in person? Check out microformats [[events]].

==Definition==
Microformats are small patterns of HTML to represent commonly published things like [[hcard|people]], [[hcalendar|events]], [[hatom|blog posts]], [[hreview|reviews]] and [[rel-tag|tags]] in web pages.

Microformats enable the publishing of higher fidelity information on the Web; the fastest and simplest way to provide feeds and APIs for the information in your website.

* Read more explanations of [[what-are-microformats|what microformats are]], and [[what-can-you-do-with-microformats|what you can do with them]].

== How to contribute ==
Do you want to help take microformats to the next level? You can:

* [[get-started|Get started]] by adding microformats to your website, services, and products.
* [[advocacy|Advocate]] the use of microformats on other web sites, especially those you use.
* Write a [[testimonial]].
* Do something on the [[to-do|to do list]].
* Join the [[irc|IRC Channel]] and [[mail|mailing lists]] to learn and help answer questions (read the [[mailing-lists#General_guidelines|general guidelines]] before posting).
* [[Main_Page#microformats_wiki_translations|Translate this microformats wiki into other languages]] to make microformats more accessible to readers of languages around the world.
* Before proposing any new microformats, make sure your website is [[POSH]], [[get-started|uses existing microformats]], and then read the [[process]].

This wiki has a number of enhancements to assist development and contributions to microformats. Before you start editing, see the [[wiki-2|wiki introduction page]] for instructions.

== Specifications ==
The list of current, stable [[microformats|Microformats]] open standard specifications.

* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]
* [[XMDP]]
* [[xoxo|XOXO]]

''If you're tempted to try your hand at writing a microformat please read '''[[process|the process]]''' page first!''

== Drafts ==
Drafts are newer microformats, for which the specifications haven't been completed yet. Drafts are somewhat mature in the development [[process]] (see [[exploratory-discussions]] for additional efforts that are not as far along in the process). The stability of these documents cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Please watch the wiki pages for updates.

* [[adr|adr]] - for marking up address information
* [[geo|geo]] - for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude)
* [[hatom|hAtom]] - syndicating episodic content (e.g. weblog postings)
* [[haudio|hAudio]]
* [[hbill|hBill]] - electronic bills
* [[hlisting|hListing]] - open, distributed listings
* [[hmedia|hMedia]] - A single media publishing format that relates to Images, Video and Audio.
* [[hnews|hNews]]
* [[hproduct|hProduct]]
* [[hrecipe|hRecipe]] - for cooking+baking recipes
* [[hresume|hResume]] - for publishing resumes and CVs
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page
* [[rel-enclosure]] - for indicating attachments (e.g. files) to download and cache
* [[rel-home]] - indicate a hyperlink to the homepage of the site
* [[rel-payment]] - indicate a payment mechanism
* [[robots-exclusion|robots exclusion]]

* [[xfolk|xFolk]]

== Design Patterns ==
{{design_patterns}} 

== Exploratory Discussions ==
See: [[exploratory-discussions]] for details of research and analysis of real-world [[examples]], existing formats, and brainstorming of possible new microformats, per the microformats [[process]].

== Examples ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== Resources ==
See [[resources]].

== User centric development ==
*[[user-interface]]
*[[data-portability]]
*[[social-network-portability]]

== Shared work areas ==
* [[to-do]]
* [[templates]]
* [http://microformats.org/wiki/delete pages for deletion] 
* [[Special:Specialpages|"Special" wiki pages]]
* [[year-in-review]]

== Tools, test cases, additional research ==
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting [[tools|tools and services]] that need to process more than one microformat. That section is intended for editors, [[parsers]], [[validators]], test cases, and other information relevant across multiple microformats.

== Microformats wiki translations ==
You may read and edit microformats articles in many other languages:

* languages with over 100 articles
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}
* languages with over 10 articles
** [[Main_Page-pt-br|Português (Brazilian Portuguese)]]
** [[Main_Page-ja|日本語 (Japanese)]]
** [[Main_Page-ru|Русский (Russian)]]
* languages with over 2 articles
** [[Main_Page-cs|Česky (Czech)]] {{NewMarker}}
** [[Main_Page-de|Deutsch (German)]]
** [[Main_Page-es|Español (Spanish)]]
** [[Main_Page-gl|Galego (Galician)]] {{NewMarker}}
** [[Main_Page-pl|Polski (Polish)]]
** [[Main_Page-ro|Română (Romanian)]] {{NewMarker}}
** [[Main_Page-zh|汉语 (Chinese)]]
** [[Main_Page-id|Indonesia (Bahasa Indonesia)]] {{NewMarker}}
* languages just started
** [[Main_Page-fa|پارسی (Farsi)]] {{NewMarker}}
** [[Main_Page-ar|العربية (Arabic)]]
** [[Main_Page-th|ภาษาไทย (Thai)]]
** [[Main_Page-it|Italiano (Italian)]] {{NewMarker}}
** [[Main_Page-ko|한국어 (Korean)]] {{NewMarker}}
* elsewhere
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.

See also [[other-languages]], and [[how-to-start-new-translation|how-to-start-a-new-translation]].

Main Page

2011-04-24T16:08:24Z

MovGP0: /* Drafts */ +hBill

<entry-title>Welcome to the microformats wiki!</entry-title>
__TOC__
Please start with the [[introduction]] page and read [[how-to-play]] before making any edits.

==Introduction==
This wiki is the central resource of the microformats community. You'll find current versions of published microformat specifications, specification drafts and publishing patterns. The wiki also hosts development resources, such as brainstorming pages for new formats and issue tracking pages for all current and in-development microformats.

== Get Started==
To get started with microformats:

* First, be familiar writing your pages and applications with semantically rich, descriptive, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.
* Learn about microformats from the [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] pages.
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.
* Want to learn more in person? Check out microformats [[events]].

==Definition==
Microformats are small patterns of HTML to represent commonly published things like [[hcard|people]], [[hcalendar|events]], [[hatom|blog posts]], [[hreview|reviews]] and [[rel-tag|tags]] in web pages.

Microformats enable the publishing of higher fidelity information on the Web; the fastest and simplest way to provide feeds and APIs for the information in your website.

* Read more explanations of [[what-are-microformats|what microformats are]], and [[what-can-you-do-with-microformats|what you can do with them]].

== How to contribute ==
Do you want to help take microformats to the next level? You can:

* [[get-started|Get started]] by adding microformats to your website, services, and products.
* [[advocacy|Advocate]] the use of microformats on other web sites, especially those you use.
* Write a [[testimonial]].
* Do something on the [[to-do|to do list]].
* Join the [[irc|IRC Channel]] and [[mail|mailing lists]] to learn and help answer questions (read the [[mailing-lists#General_guidelines|general guidelines]] before posting).
* [[Main_Page#microformats_wiki_translations|Translate this microformats wiki into other languages]] to make microformats more accessible to readers of languages around the world.
* Before proposing any new microformats, make sure your website is [[POSH]], [[get-started|uses existing microformats]], and then read the [[process]].

This wiki has a number of enhancements to assist development and contributions to microformats. Before you start editing, see the [[wiki-2|wiki introduction page]] for instructions.

== Specifications ==
The list of current, stable [[microformats|Microformats]] open standard specifications.

* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]
* [[XMDP]]
* [[xoxo|XOXO]]

''If you're tempted to try your hand at writing a microformat please read '''[[process|the process]]''' page first!''

== Drafts ==
Drafts are newer microformats, for which the specifications haven't been completed yet. Drafts are somewhat mature in the development [[process]] (see [[exploratory-discussions]] for additional efforts that are not as far along in the process). The stability of these documents cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Please watch the wiki pages for updates.

* [[adr|adr]] - for marking up address information
* [[geo|geo]] - for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude)
* [[hatom|hAtom]] - syndicating episodic content (e.g. weblog postings)
* [[haudio|hAudio]]
* [hbill|hBill]] - electronic bills
* [[hlisting|hListing]] - open, distributed listings
* [[hmedia|hMedia]] - A single media publishing format that relates to Images, Video and Audio.
* [[hnews|hNews]]
* [[hproduct|hProduct]]
* [[hrecipe|hRecipe]] - for cooking+baking recipes
* [[hresume|hResume]] - for publishing resumes and CVs
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page
* [[rel-enclosure]] - for indicating attachments (e.g. files) to download and cache
* [[rel-home]] - indicate a hyperlink to the homepage of the site
* [[rel-payment]] - indicate a payment mechanism
* [[robots-exclusion|robots exclusion]]

* [[xfolk|xFolk]]

== Design Patterns ==
{{design_patterns}} 

== Exploratory Discussions ==
See: [[exploratory-discussions]] for details of research and analysis of real-world [[examples]], existing formats, and brainstorming of possible new microformats, per the microformats [[process]].

== Examples ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== Resources ==
See [[resources]].

== User centric development ==
*[[user-interface]]
*[[data-portability]]
*[[social-network-portability]]

== Shared work areas ==
* [[to-do]]
* [[templates]]
* [http://microformats.org/wiki/delete pages for deletion] 
* [[Special:Specialpages|"Special" wiki pages]]
* [[year-in-review]]

== Tools, test cases, additional research ==
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting [[tools|tools and services]] that need to process more than one microformat. That section is intended for editors, [[parsers]], [[validators]], test cases, and other information relevant across multiple microformats.

== Microformats wiki translations ==
You may read and edit microformats articles in many other languages:

* languages with over 100 articles
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}
* languages with over 10 articles
** [[Main_Page-pt-br|Português (Brazilian Portuguese)]]
** [[Main_Page-ja|日本語 (Japanese)]]
** [[Main_Page-ru|Русский (Russian)]]
* languages with over 2 articles
** [[Main_Page-cs|Česky (Czech)]] {{NewMarker}}
** [[Main_Page-de|Deutsch (German)]]
** [[Main_Page-es|Español (Spanish)]]
** [[Main_Page-gl|Galego (Galician)]] {{NewMarker}}
** [[Main_Page-pl|Polski (Polish)]]
** [[Main_Page-ro|Română (Romanian)]] {{NewMarker}}
** [[Main_Page-zh|汉语 (Chinese)]]
** [[Main_Page-id|Indonesia (Bahasa Indonesia)]] {{NewMarker}}
* languages just started
** [[Main_Page-fa|پارسی (Farsi)]] {{NewMarker}}
** [[Main_Page-ar|العربية (Arabic)]]
** [[Main_Page-th|ภาษาไทย (Thai)]]
** [[Main_Page-it|Italiano (Italian)]] {{NewMarker}}
** [[Main_Page-ko|한국어 (Korean)]] {{NewMarker}}
* elsewhere
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.

See also [[other-languages]], and [[how-to-start-new-translation|how-to-start-a-new-translation]].

bill-brainstorming

2011-04-24T16:01:57Z

MovGP0: /* Field and Element Details */

<entry-title>hBill 0.1</entry-title>
{{Template:DraftSpecification}}

hBill is a microformat that allows to provide metainformation on a bill, so that customers can do transactions more easily.
__TOC__
== Draft Specification ==
<div class="vcard">
;Editor/Author
:Johann Dirry
</div>

[[#Copyright|copyright]] and [[#Patents|patents]] statements apply.

== Status ==
hBill 0.1 is a microformats.org draft specification. Public discussion on hBill takes place on [[hbill-feedback]], the #microformats [[irc]] channel on irc.freenode.net, and [http://microformats.org/discuss/mail/microformats-discuss/ microformats-discuss mailing list].

=== Available languages ===
The English version of this specification is the only normative version. For translations of this document see the [[#translations]] section.

=== Errata and Updates ===
Known errors and issues in this specification are corrected in [[hbill-issues-resolved|resolved]] and [[hbill-issues-closed|closed]] issues. Please check there before reporting [[hbill-issues|issues]].

== Introduction ==
hBill is a [[microformat]] for identifying semantic information in electronic bills. hBill content is easily added to bills that are available in xHTML or HTML format.

{{rfc-2119-intro}}

== Semantic XHTML Design Principles ==
{{semantic-xhtml-design-principles}}

=== Schema ===
Schema elements follow the microformat pattern of prefixing a unique identifier (in this case, '<code>h</code>') on the outermost container element. The parts of this microformat are based on analysis of bills from online shops.

The hBill schema consists of the following:

* '''<code>hbill</code>'''. optional.
** '''<code>iban</code>'''. required. IBAN code as specified in [[iso-13616-1|ISO 13616-1:2007 Part 1]].
** '''<code>bic</code>'''. required. BIC/SWIFT code as specified in [[iso-9362|ISO 9362]].
** '''<code>accountnumber</code>'''. optional. Country specific banking account number.
** '''<code>bankcode</code>'''. optional. Country specific bank code.
** '''<code>billingsum</code>'''. required. [http://www.w3.org/TR/xmlschema-2/#double xs:double]. Ammout of money the customer has to submit to the selling party.
** '''<code>currency</code>'''. required. [[iso-4217|ISO 4217]].
** '''<code>receiver</code>'''. required. [[hcard]] information of the money receiver.
** '''<code>receivingbank</code>'''. recommended. [[hcard]] information of the money receiving bank.
** '''<code>billnumber</code>'''. recommended. [http://www.w3.org/TR/xmlschema-2/#string xs:string]. May be required by the selling party to identify the bill.
** '''<code>billingdate</code>'''. required. [http://www.w3.org/TR/xmlschema-2/#date xs:date] or [http://www.w3.org/TR/xmlschema-2/#dateTime xs:dateTime]. Date when the bill was created.

=== Field and Element Details ===

==== hbill ====
* a Bill element is identified by the class <code>hbill</code>
* a document may have multiple bill elements
* if there is only bill in the document, the <code>hbill</code> element ''may'' be missing.
** if the <code>hbill</code> element is missing, it is assumed to be the document

==== iban ====
* the IBAN code of the account the money has to get transfered to
* the <code>hbill</code> element ''requires'' the IBAN code

==== bic ====
* the BIC/SWIFT code the money has to get transfered to
* the <code>hbill</code> element ''requires'' the BIC/SWIFT code, because the user ''may'' need it

==== accountnumber ====
* a country specific banking account number
* the <code>accountnumber</code> element is ''optional''
* ''may'' be provided for national transactions

==== bankcode ====
* a country specific bank code
* the <code>bankcode</code> element is ''optional''
* ''may'' be provided for national transactions

==== billingsum ====
* the ammout of money the customer has to submit to the selling party
* the <code>hbill</code> element ''requires'' the <code>billingsum</code> element

==== currency ====
* the currency of the ammount of money the customer has to submit to the selling party
* the <code>hbill</code> element ''requires'' the <code>currency</code> element

==== receiver ====
* [[hcard]] information of the money receiver
* the <code>hbill</code> element ''requires'' the <code>receiver</code> element

==== receivingbank ====
* [[hcard]] information of the money receiving bank
* it is ''recommended'' to use the <code>receivingbank</code> element, because the customer ''may not'' be able to get this information based on the IBAN or BIC/SWIFT code

==== billnumber ====
* it is ''recommended'' to provide this information, so its possible to identify the bill correctly
* some parties ''may'' ''require'' the customer to provide this information in another way (ie. manually filling the 'purpose' or 'customer data' field), which ''should not'' be done
* the <code>hbill</code> element ''requires'' the <code>billnumber</code> element

==== billingdate ====
* date when the bill was created
* ''may'' also provide time and timezone information
* the <code>hbill</code> element ''requires'' the <code>billdate</code> element

== Examples ==
''todo''

== Copyright ==
{{MicroFormatPublicDomainContributionStatement}}.

== Patents ==
{{MicroFormatPatentStatement}}

== References ==
=== Normative References ===
; ISO
* [[iso-13616-1|ISO 13616-1]]
* [[iso-9362|ISO 9362]]
* [[iso-4217|ISO 4217]]
* [[iso-8601|ISO 8601]]

; W3C
* [http://www.w3.org/TR/xmlschema-2/#double xmls:double]
* [http://www.w3.org/TR/xmlschema-2/#date xs:date]

; microformats
* [[hcard]]
* [[adr]]

[[Category:Draft Specifications]]

bill-brainstorming

2011-04-24T15:17:44Z

MovGP0: /* Schema */ renamed some elements

bill-brainstorming

2011-04-24T15:08:30Z

MovGP0: /* Schema */ typo.

bill-brainstorming

2011-04-24T15:07:03Z

MovGP0: created a first draft for billing information