summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuke Dashjr <luke-jr+git@utopios.org>2017-03-05 05:49:02 +0000
committerLuke Dashjr <luke-jr+git@utopios.org>2017-03-05 05:49:02 +0000
commitee90b8c525311a354257ef03cd8f5bfa7ed4e751 (patch)
tree256e1b5f6a3461924a458c6d6b71681ba06c28b7
parentf33738655061a0f4a8949ca018b53994ace1a1c1 (diff)
downloadbips-ee90b8c525311a354257ef03cd8f5bfa7ed4e751.tar.xz
bip-xchgrate: Drop HTML longdesc
-rw-r--r--bip-xchgrate.mediawiki4
1 files changed, 2 insertions, 2 deletions
diff --git a/bip-xchgrate.mediawiki b/bip-xchgrate.mediawiki
index 86f7cfc..6d79b4c 100644
--- a/bip-xchgrate.mediawiki
+++ b/bip-xchgrate.mediawiki
@@ -69,7 +69,7 @@ Each currency-pair will receive a separate result, a JSON Object, with the follo
* ''quote'' - The currency code for the quote currency.
* ''base'' - The currency code for the base currency.
* ''desc'' - Optional description. For example, it could be "Based on Florida BTM prices." or any other short String that provides information useful to the user. SHOULD be shorter than 45 characters.
-* ''longdesc'' - Optional description, but may be longer and formatted using HTML.
+* ''longdesc'' - Optional description, but may be longer and include newlines.
* ''symbol'' - An Array of prefix and suffix for the quote currency. Each may be either a fixed String, an Array of two Strings (negative and positive), or null. Any positive or negative symbols must be included in this prefix/suffix; it MUST NOT be implied otherwise.
* ''digits'' - The type of digits to use for the quote currency's numbers. "arabic" should be used for common 0-9 digits.
* ''grouping'' - An Array alternating between Numbers representing a series of digits, and Strings used as delimiters. If terminated by a zero, the final grouping is to be repeated continually. For example, the common US locale thousands grouping would be <code>[3, ",", 0]</code>
@@ -127,7 +127,7 @@ Why are multiple results separated by a line-feed rather than using a JSON Array
What if long descriptions require line and paragraph breaks?
-* Long descriptions support HTML, which has entities for paragraphs and line breaks that do not require literal line-feeds in the data.
+* Clients should word-wrap long lines, and JSON escapes newlines as "\n" which can be used doubly ("\n\n") for paragraph breaks.
==Backwards compatibility==