> On Jun 25, 2014, at 10:15, slush <sl...@centrum.cz> wrote:
> Good standard must be explicit as much as possible. Having million optional 
> fields with ambiguous meaning is even worse than not having these fields.

+1. BIP70 is important. We want to keep it very simple and generalized, or 
there is a very real risk that implementers will either not bother with it or 
implement it in buggy, poorly standardized ways. 

Any information not required by the machine should only exist in human-oriented 
fields (namely, the memo field). 

Let's try to avoid ending up with another horrendously complicated, 
edge-case-oriented protocol like we programmers frequently complain about. 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development

Reply via email to